gaspersic/solana
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Apply review feedback

Browse Source
This commit is contained in:
Greg Fitzgerald
2018-12-05 10:51:50 -07:00
committed by Grimes
parent 6ecb00a1d8
commit bf2658cee0
2 changed files with 16 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
book/src/programs.md
View File

@@ -30,9 +30,9 @@ instruction is invalid, any changes made within the transaction are discarded.
If the program needs to store state between transactions, it does so using If the program needs to store state between transactions, it does so using
*accounts*. Accounts are similar to files in operating systems such as Linux. *accounts*. Accounts are similar to files in operating systems such as Linux.
Like files, an account may hold arbitrary data and that data persists beyond Like a file, an account may hold arbitrary data and that data persists beyond
the lifetime of a program. Also like files, an account includes metadata that the lifetime of a program. Also like a file, an account includes metadata that
tells the runtime who is allowed to access the data and how. Unlike files, the tells the runtime who is allowed to access the data and how. Unlike a file, the
account includes metadata for the lifetime of the file. That lifetime is account includes metadata for the lifetime of the file. That lifetime is
expressed in "tokens", which is a number of fractional native tokens, called expressed in "tokens", which is a number of fractional native tokens, called
*lamports*. Accounts are held in validator memory and pay "rent" to stay there. *lamports*. Accounts are held in validator memory and pay "rent" to stay there.
@@ -40,23 +40,23 @@ Each fullnode periodically scan all accounts and collects rent. Any account
that drops to zero lamports is purged. that drops to zero lamports is purged.
If an account is marked "executable", it will only be used by a *loader* to run If an account is marked "executable", it will only be used by a *loader* to run
programs. For example, programs compiled to BPF are marked executable and programs. For example, a BPF-compiled program is marked executable and loaded
loaded by the BPF loader. No program is allowed to modify the contents of an by the BPF loader. No program is allowed to modify the contents of an
executable account. executable account.
Accounts also include "owner" metadata. The owner is a program ID. The runtime An account also includes "owner" metadata. The owner is a program ID. The
grants the program write access to the account if its ID matches the owner. If runtime grants the program write access to the account if its ID matches the
an account is not owned by a program, the program is permitted to read its data owner. If an account is not owned by a program, the program is permitted to
and credit the account. read its data and credit the account.
In the same way that a Linux user uses a path to look up a file, a Solana In the same way that a Linux user uses a path to look up a file, a Solana
client uses public keys to look up accounts. To create an account, the client client uses public keys to look up accounts. To create an account, the client
generates a *keypair* and registers its public key using the CreateAccount generates a *keypair* and registers its public key using the CreateAccount
instruction. Once registered, transactions reference account keys to grant instruction. Once registered, transactions reference account keys to grant
programs access to accounts. The runtime grants programs read access by programs access to accounts. The runtime grants programs read access by
default. To grant write access, the client must either assign the account default. To grant write access, the client must either assign the account to a
to a program ID or sign the transaction using the keypair's *secret key*. Since program or sign the transaction using the keypair's *secret key*. Since only
only the owner of the secret key can produce valid signatures matching the the holder of the secret key can produce valid signatures matching the
account's public key, the runtime recognizes the signature as authorization to account's public key, the runtime recognizes the signature as authorization to
modify account data or debit the account. modify account data or debit the account.

8
book/src/terminology.md
View File

@@ -96,8 +96,8 @@ the [ledger](#ledger).
#### leader schedule #### leader schedule
A sequence of [fullnode](#fullnode) [public keys](#public-key). The cluster A sequence of [fullnode](#fullnode) [public keys](#public-key). The cluster
uses the leader schedule to determine which fullnode is in the uses the leader schedule to determine which fullnode is the [leader](#leader)
[leader](#leader) at any moment in time. at any moment in time.
#### ledger #### ledger
@@ -111,7 +111,7 @@ height](#tick-height).
#### lockout #### lockout
The duration of time in which a [fullnode](#fullnode) is unable to The duration of time for which a [fullnode](#fullnode) is unable to
[vote](#vote) on another [fork](#fork). [vote](#vote) on another [fork](#fork).
#### native token #### native token
@@ -208,7 +208,7 @@ A scarce, non-fungible member of a set of curios.
#### epoch #### epoch
The time in which a [leader schedule](#leader-schedule) is valid. The time for which a [leader schedule](#leader-schedule) is valid.
#### light client #### light client