mirrors/lightning-bolts
1
0
Fork 0
mirror of https://github.com/lightning/bolts.git synced 2025-03-10 17:18:44 +01:00
Code Issues Projects Releases Wiki Activity

BOLT 0: apply updated stylesheet rules

Browse source
This commit is contained in:
Landon Mutch 2017-12-15 22:50:30 -08:00 • committed by Rusty Russell
parent 34eec6ce14
commit eebd7fad6d
1 changed files with 4 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
00-introduction.md
View file

@ -28,9 +28,8 @@ This is version 0.
* *Node*: * *Node*:
* A computer or other device connected to the Bitcoin network. * A computer or other device connected to the Bitcoin network.
* *Peers*: * *Peers*:
* *Nodes* wanting to transact Bitcoins with each other through a *channel*. * *Nodes* transacting bitcoins with one other through a *channel*.
* *MSAT*: * *MSAT*:
* A millisatoshi, often used as a field name. * A millisatoshi, often used as a field name.
@ -39,19 +38,16 @@ This is version 0.
* An irreversible on-chain transaction that pays to both *peers* on a *channel*. * An irreversible on-chain transaction that pays to both *peers* on a *channel*.
It can only be spent by mutual consent. It can only be spent by mutual consent.
* *Channel*: * *Channel*:
* A fast, off-chain method of mutual exchange between two *peers*. * A fast, off-chain method of mutual exchange between two *peers*.
To transact funds, peers exchange signatures to create an updated *commitment transaction*. To transact funds, peers exchange signatures to create an updated *commitment transaction*.
* *Commitment transaction*: * *Commitment transaction*:
* A transaction that spends the *funding transaction*. * A transaction that spends the *funding transaction*.
Each *peer* holds the other peer's signature for this transaction, so that each Each *peer* holds the other peer's signature for this transaction, so that each
always has a commitment transaction that it can spend. After a new always has a commitment transaction that it can spend. After a new
commitment transaction is negotiated, the old one is *revoked*. commitment transaction is negotiated, the old one is *revoked*.
* *HTLC*: Hashed Time Locked Contract. * *HTLC*: Hashed Time Locked Contract.
* A conditional payment between two *peers*: the recipient can spend * A conditional payment between two *peers*: the recipient can spend
the payment by presenting its signature and a *payment preimage*, the payment by presenting its signature and a *payment preimage*,
@ -59,12 +55,10 @@ This is version 0.
a given time. These are implemented as outputs from the a given time. These are implemented as outputs from the
*commitment transaction*. *commitment transaction*.
* *Payment hash*: * *Payment hash*:
* The *HTLC* contains the payment hash, which is the hash of the * The *HTLC* contains the payment hash, which is the hash of the
*payment preimage*. *payment preimage*.
* *Payment preimage*: * *Payment preimage*:
* Proof that payment has been received, held by * Proof that payment has been received, held by
the final recipient, who is the only person who knows this the final recipient, who is the only person who knows this
@ -72,7 +66,6 @@ This is version 0.
release funds. The payment preimage is hashed as the *payment hash* release funds. The payment preimage is hashed as the *payment hash*
in the *HTLC*. in the *HTLC*.
* *Commitment revocation secret key*: * *Commitment revocation secret key*:
* Every *commitment transaction* has a unique *commitment revocation* secret-key * Every *commitment transaction* has a unique *commitment revocation* secret-key
value that allows the other *peer* to spend all outputs value that allows the other *peer* to spend all outputs
@ -80,19 +73,16 @@ This is version 0.
transactions are revoked. To support revocation, each output of the transactions are revoked. To support revocation, each output of the
commitment transaction refers to the commitment revocation public key. commitment transaction refers to the commitment revocation public key.
* *Per-commitment secret*: * *Per-commitment secret*:
* Every *commitment transaction* derives its keys from a per-commitment secret, * Every *commitment transaction* derives its keys from a per-commitment secret,
which is generated such that the series of per-commitment secrets which is generated such that the series of per-commitment secrets
for all previous commitments can be stored compactly. for all previous commitments can be stored compactly.
* *Mutual close*: * *Mutual close*:
* A cooperative close of a *channel*, accomplished by broadcasting an unconditional * A cooperative close of a *channel*, accomplished by broadcasting an unconditional
spend of the *funding transaction* with an output to each *peer* spend of the *funding transaction* with an output to each *peer*
(unless one output is too small, and thus is not included). (unless one output is too small, and thus is not included).
* *Unilateral close*: * *Unilateral close*:
* An uncooperative close of a *channel*, accomplished by broadcasting a * An uncooperative close of a *channel*, accomplished by broadcasting a
*commitment transaction*. This transaction is larger (i.e. less *commitment transaction*. This transaction is larger (i.e. less
@ -100,32 +90,27 @@ This is version 0.
commitment is broadcast cannot access its own outputs for some commitment is broadcast cannot access its own outputs for some
previously-negotiated duration. previously-negotiated duration.
* *Revoked transaction close*: * *Revoked transaction close*:
* An invalid close of a *channel*, accomplished by broadcasting a revoked * An invalid close of a *channel*, accomplished by broadcasting a revoked
*commitment transaction*. Since the other *peer* knows the *commitment transaction*. Since the other *peer* knows the
*commitment revocation secret key*, it can create a *penalty transaction*. *commitment revocation secret key*, it can create a *penalty transaction*.
* *Penalty transaction*: * *Penalty transaction*:
* A transaction that spends all outputs of a revoked *commitment * A transaction that spends all outputs of a revoked *commitment
transaction*, using the *commitment revocation secret key*. A *peer* uses this transaction*, using the *commitment revocation secret key*. A *peer* uses this
if the other peer tries to "cheat" by broadcasting a revoked if the other peer tries to "cheat" by broadcasting a revoked
*commitment transaction*. *commitment transaction*.
* *Commitment number*: * *Commitment number*:
* A 48-bit incrementing counter for each *commitment transaction*; counters * A 48-bit incrementing counter for each *commitment transaction*; counters
are independent for each *peer* in the *channel* and start at 0. are independent for each *peer* in the *channel* and start at 0.
* *It's ok to be odd*: * *It's ok to be odd*:
* A rule applied to some numeric fields that indicates either optional or * A rule applied to some numeric fields that indicates either optional or
compulsory support for features. Even numbers indicate that both endpoints compulsory support for features. Even numbers indicate that both endpoints
MUST support the feature in question, while odd numbers indicate MUST support the feature in question, while odd numbers indicate
that the feature MAY be disregarded by the other endpoint. that the feature MAY be disregarded by the other endpoint.
* `chain_hash`: * `chain_hash`:
* Used in several of the BOLT documents to denote the genesis hash of a * Used in several of the BOLT documents to denote the genesis hash of a
target blockchain. This allows *nodes* to create and reference *channels* on target blockchain. This allows *nodes* to create and reference *channels* on