You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to introduce complex spend policies more information must be given to participants retrieving the spend.
Usecase
Give information about the output recipient address and make it simpler for watchtowers to derive internal descriptors and check scripts matching.
Change detection (derivation index of the deposit descriptor to check with)
DLC oracle (give the oracle label and contract descriptor and derivation index)
Enterprise information (invoice ids to check amount with the enterprise services)
...
How to store this information
1. Share a psbt instead of simple bitcoin transaction
pros:
A well known format, with the output bip32_derivation fields for usecase 1 and proprietary fields for usecase 2
Format is used across signing devices
cons:
may be limited for long term usage, lot of unused bytes, psbt may be huge if client and server are not careful to lighten it to only the necessary fields
2. Introduce a new field metadata
The text was updated successfully, but these errors were encountered:
In order to introduce complex spend policies more information must be given to participants retrieving the spend.
Usecase
Give information about the output recipient address and make it simpler for watchtowers to derive internal descriptors and check scripts matching.
How to store this information
1. Share a psbt instead of simple bitcoin transaction
pros:
cons:
2. Introduce a new field
metadata
The text was updated successfully, but these errors were encountered: