Tracking: v0.11 known bugs

[zoedberg]

Currently v0.11 has the following known bugs:

• Calling update_witnesses in a lightning wallet may disrupt channel operations rgb-std#292
• bugs related to retrying an aborted transfer rgb-std#287
• bitcoin reorgs are not handled BP-WG/bp-wallet#80
• update_witnesses is not enough to handle reorgs rgb-std#296
• error updating wallet caused by esplora rate limit  BP-WG/bp-wallet#70

[dr-orlovsky]

Thank you. I assume the first 4 are just different aspects of the same issue?

[zoedberg]

Thank you. I assume the first 4 are just different aspects of the same issue?

I wouldn't say so.

• 1st one: related to the fact that a call to update_witnesses sets all TXs made in LN to Archived, so if this call is made before the creation of an HTLC or during channel opening it may disrupt operations
• 2nd one: when trying to do the same transfer
  • if the sender calls update_witnesses, the sender fails the payment re-attempt
  • if the sender doesn't call update_witnesses the 2nd consignment that he creates has duplicated bundles spending the same input
  • if the receiver accepts the consignment from the previous point, inflation happens (more assets than were issued can be spent and accepted)
• 3rd one: at the bitcoin level the bp-wallet is unable to handle re-orgs (if a TX disappears, balances and UTXO list are not updated)
• 4th one: the method that handles re-orgs affecting RGB allocations (update_witnesses) isn't doing all that's needed to update them (it needs to handle children bundles of updated witnesses as well)