mirrors/lightning-bolts
1
0
Fork 0
mirror of https://github.com/lightning/bolts.git synced 2024-11-19 01:50:03 +01:00
Code Issues Projects Releases Wiki Activity

routing gossip: attempt to make timestamping mechanism for

Browse Source 
channel_announcement clearer
This commit is contained in:
lisa neigut 2018-09-12 09:21:05 -07:00 committed by Rusty Russell
parent bae8f9c2c6
commit b4be990550
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
07-routing-gossip.md
View File

@ -682,11 +682,11 @@ one. If there's no `channel_update` then it is not sent at all, which is most
likely in the case of pruned channels.
Otherwise the `channel_announcement` is usually followed immediately by a
`channel_update`, which serves as a fairly good timestamp for new channels.
Ideally we would specify that the first `channel_update` is to be used, but
new nodes on the network wouldn't know that, and would require that timestamp
to be stored. Instead, we allow any update to be used, which is simple to
implement.
`channel_update`. Ideally we would specify that the first (oldest) `channel_update`'s
timestamp is to be used as the time of the `channel_announcement`, but new nodes on
the network will not have this, and further would require the first `channel_update`
timestamp to be stored. Instead, we allow any update to be used, which
is simple to implement.
In the case where the `channel_announcement` is nonetheless missed,
`query_short_channel_ids` can be used to retrieve it.