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

tx-abort: port over meaning of the data field from warning

Browse source 
`tx_abort`'s structure comes from the `warning`/`error` messages,
but we failed to port over the rationale/rules for the `data` field.

Suggested-By: @morehouse
This commit is contained in:
niftynei 2023-11-09 22:27:30 -06:00 • committed by neil saitug
parent 71e67e6d46
commit 11dea59504
1 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
02-peer-protocol.md
View file

@ -533,6 +533,10 @@ they may obtain incoming liquidity at no cost).
A sending node: A sending node:
- MUST NOT have already transmitted `tx_signatures` - MUST NOT have already transmitted `tx_signatures`
- SHOULD forget the current negotiation and reset their state. - SHOULD forget the current negotiation and reset their state.
- MAY send an empty `data` field.
- when failure was caused by an invalid signature check:
- SHOULD include the raw, hex-encoded transaction in reply to a
`tx_signatures` or `commitment_signed` message.
A receiving node: A receiving node:
- if they have already sent `tx_signatures` to the peer: - if they have already sent `tx_signatures` to the peer:
@ -542,6 +546,10 @@ A receiving node:
- SHOULD forget the current negotiation and reset their state. - SHOULD forget the current negotiation and reset their state.
- if they have not sent `tx_abort`: - if they have not sent `tx_abort`:
- MUST echo back `tx_abort` - MUST echo back `tx_abort`
- if `data` is not composed solely of printable ASCII characters (For
reference: the printable character set includes byte values 32 through
126, inclusive):
- SHOULD NOT print out `data` verbatim.
#### Rationale #### Rationale