Tracking: combined tapret/opret bundles in one transfer

[dr-orlovsky]

affects: [ v0.11.0-beta.6, v0.11.0-beta.7, v0.11.0-beta.8 ]
status: Fix proposed
layers: [ bp-dbc, bp-seals, rgb-core, rgb-std, rgb-wallet ]

Transfers involving combinations of simultaneous opret and tapret commitments remain unstable

Related issues

• fail spending opret and tapret allocations together rgb-std#246
• State transition bundle to witness transaction relation ambiguity rgb-std#247
• receiver fails to accept a transfer which spends opret and tapret allocations together rgb-std#271
• fail spending allocations received with an opret+tapret transfer rgb-std#275

Proposed fixes

Round 1

• Allow multiple witnesses per bundle rgb-std#248
• Support spending mixed opret/tapret outputs rgb-std#252
• Allow to pay from both tapret and opret inputs rgb-std#256

Round 2

• Always add opret anchors when preset to a consignment rgb-std#272

Round 3

• Do not keep explicit data on seal close method in DBC anchor BP-WG/bp-core#105
• Use new DBC method APIs BP-WG/bp-std#50
• Improve handling of anchor and bundle close method mismatch in validator rgb-core#271
• Fix use of anchor/bundle opret/tapret dichotomies rgb-std#277

Tests

• tapret_wlt_receiving_opret: de-ignore to show bug rgb-tests#6 (original test revealing initial issue, later updated to expose further issues)
• tapret_wlt_receiving_opret 100 times rgb-tests#16
• Fix for multiple tapret/opret cross-interaction issues rgb-tests#18
• Pre-beta 9 updates rgb-tests#19 (combined fix for this and other issues)