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

BOLT 0: fix ordering of chain_hash

Browse source
This commit is contained in:
ueno 2018-04-17 05:25:30 +09:00 • committed by Olaoluwa Osuntokun
parent 71630b4766
commit f5f123c02c
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
07-routing-gossip.md
View file

@ -123,7 +123,7 @@ The origin node:
- MUST set `chain_hash` to the 32-byte hash that uniquely identifies the chain - MUST set `chain_hash` to the 32-byte hash that uniquely identifies the chain
that the channel was opened within: that the channel was opened within:
- for the _Bitcoin blockchain_: - for the _Bitcoin blockchain_:
- MUST set `chain_hash` value (encoded in hex) equal to `000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f`. - MUST set `chain_hash` value (encoded in hex) equal to `6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d6190000000000`.
- MUST set `short_channel_id` to refer to the confirmed funding transaction, - MUST set `short_channel_id` to refer to the confirmed funding transaction,
as specified in [BOLT #2](02-peer-protocol.md#the-funding_locked-message). as specified in [BOLT #2](02-peer-protocol.md#the-funding_locked-message).
- Note: the corresponding output MUST be a P2WSH, as described in [BOLT #3](03-transactions.md#funding-transaction-output). - Note: the corresponding output MUST be a P2WSH, as described in [BOLT #3](03-transactions.md#funding-transaction-output).