mirror of
https://github.com/lightningnetwork/lnd.git
synced 2025-01-18 21:35:24 +01:00
f7daa307dd
Initially in lnd, we didn't store the extra TLV data that could be
dangling off of gossip messages. This was fixed initially in lnd v0.5
with this PR: https://github.com/lightningnetwork/lnd/pull/1825.
Within the PR, we incorrect set the `ExtraOpaqueData` (extra TLV blob)
of the `ChannelAnnouncement` to the value stored in `edge`, which is
actually our channel update. As 6-ish years ago we didn't yet have
anything that used the TLV gossip fields, this went unnoticed.
Fast forward to 2024, we shipped an experimental version of inbounbd
fees. This starts to store additional data in the `ExtraOpaqueData`
field, the TLV for the inbound fee. Initially, everything is valid when
the first `ChannelAnnouncement` is sent, but as soon as a user attempts
to set an inbound fee policy, we'd incorrectly swap in that new
serialized TLV for the _channel announcement_:
|
||
|---|---|---|
| .. | ||
| bootstrapper.go | ||
| chan_series.go | ||
| gossiper_test.go | ||
| gossiper.go | ||
| log.go | ||
| message_store_test.go | ||
| message_store.go | ||
| mock_test.go | ||
| reliable_sender_test.go | ||
| reliable_sender.go | ||
| sync_manager_test.go | ||
| sync_manager.go | ||
| syncer_test.go | ||
| syncer.go | ||