Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add contextual information in set_spend_tx request and get_spend_tx response #127

Open
edouardparis opened this issue Jun 22, 2022 · 1 comment

Comments

@edouardparis
Copy link
Member

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.

  1. Change detection (derivation index of the deposit descriptor to check with)
  2. DLC oracle (give the oracle label and contract descriptor and derivation index)
  3. Enterprise information (invoice ids to check amount with the enterprise services)
  4. ...

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

@edouardparis
Copy link
Member Author

previous work #102

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant