From 04cf90635ce1c8945c491f18f1392bb6b7e57930 Mon Sep 17 00:00:00 2001 From: Christian Decker Date: Thu, 17 Nov 2016 12:27:15 +0100 Subject: [PATCH] routing: Added a lower bound of 6 confirmations Otherwise the short `channel-id` may change in a reorg, and double-spending would allow multiple announcements without added cost. It also slightly favours resilient channels for transfer forwarding. Thanks @pm47 for pointing this out. --- 07-routing-gossip.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/07-routing-gossip.md b/07-routing-gossip.md index 19c4bb187..d16805a44 100644 --- a/07-routing-gossip.md +++ b/07-routing-gossip.md @@ -87,7 +87,7 @@ Upon receiving an announcement the nodes verifies the validity of the announceme In order to be valid the following conditions MUST be satisfied: - The timestamp MUST be larger than the last valid announcement from the announcing node. - - The anchor transactions for each channel, identified by the (`blockheight`, `blockindex`)-tuple must have reached at least the configurable minimum number of confirmations. + - The anchor transactions for each channel, identified by the (`blockheight`, `blockindex`)-tuple must have reached at least a minimum number of 6 confirmations. The node MAY require more confirmations before processing and/or forwarding the announcement. - The signature in the announcement MUST be a valid signature from the public key in the `node_id` field for the message up to the signature itself. - The announcement MUST have at least on valid channel. The validity of the channel can be verified by inspecting the anchor transaction specified in the announcement. - If the `expiry` field of any channel is set to `0xFF` then it MUST be the only channel in the announcement.