blockworks-foundation
/
solana
mirror of https://github.com/blockworks-foundation/solana.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

More terms

This commit is contained in:
Greg Fitzgerald 2018-11-28 14:18:21 -07:00 committed by Grimes
parent 36503ead70
commit 8d1ac37734
2 changed files with 14 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
book/src/cluster.md
View File

@ -19,7 +19,7 @@ for the *Bootstrap Leader*. `solana-fullnode-config` is used to pin down what
IP addresses and ports other nodes should use to contact it. Next, the
information from the first two tools are passed to `solana-genesis` to create
the genesis block. The genesis block is then be passed to all initial
fullnodes. The fullnode holding the Bootstrap Leader's private key is
fullnodes. The fullnode holding the Bootstrap Leader's secret key is
responsible for appending the first entries to the ledger. It initializes its
internal state with the Mint's account. That account will hold the number of
fractional native tokens (called lamports) defined in the genesis block. All

20
book/src/terminology.md
View File

@ -5,22 +5,32 @@
The following list contains words commonly used throughout the Solana architecture.
* account - a persistent file addressed by pubkey and with tokens tracking its lifetime
* block - the entries generated within a slot
* bootstrap leader - the first fullnode to take the leader role
* control plane - a gossip network connecting all nodes of a cluster
* client - a node that utilizes the cluster
* cluster - a set of fullnodes maintaining a single ledger
* control plane - a gossip network connecting all nodes of a cluster
* data plane - a multicast network used to efficiently validate entries and gain consensus
* entry - an entry on the ledger - either a tick or a transactions entry
* finality - the wallclock duration between a leader creating a tick entry and recoginizing
* finality - the wallclock duration between a leader creating a tick entry and recognizing
a supermajority of validator votes with a ledger interpretation that matches the leader's
* fork - a ledger derived from common entries but then diverged
* fullnode - a full participant in the cluster - either a leader or validator node
* genesis block - the first entries of the ledger
* instruction - the smallest unit of a program that a client can include in a transaction
* keypair - a public and secret key
* leader - the role of a fullnode when it is appending entries to the ledger
* ledger - a list of entries containing transactions signed by clients
* ledger vote - a hash of the fullnode's state at a given tick height
* lockout - the duration of time in which a fullnode is unable to vote on another fork
* node count - the number of fullnodes participating in a cluster
* program - the code that interprets instructions
* pubkey - the public key of a keypair
* pubkey - a shorthand for public key
* public key - the public key of a keypair
* replicator - a type of client that stores copies of segments of the ledger
* secret key - the private key of a keypair
* slot - the time in which a single leader may produce entries
* stake - tokens forfeit to the cluster if malicious fullnode behavior can be proven
* tick - a ledger entry that estimates wallclock duration
* tick height - the Nth tick in the ledger
* tps - transactions per second
@ -35,11 +45,7 @@ The following keywords do not have any functionality but are reserved by Solana
for potential future use.
* blob - a fraction of a block; the smallest unit sent between validators
* block - the entries generated within a slot
* epoch - the time in which a leader schedule is valid
* light client - a type of client that can verify it's pointing to a valid cluster
* mips - millions of instructions per second
* public key - We currently use `pubkey`
* secret key - Users currently only use `keypair`
* slot - the time in which a single leader may produce entries
* thin client - a type of client that trusts it is communicating with a valid cluster