-
Notifications
You must be signed in to change notification settings - Fork 117
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 proof courier address field to Tap address #434
Comments
PR for adding TLV field: #450 |
This was referenced Aug 8, 2023
ffranr
changed the title
Add optional proof courier address to Tap address
Add mandatory proof courier address to Tap address
Aug 9, 2023
ffranr
changed the title
Add mandatory proof courier address to Tap address
Add proof courier address field to Tap address
Aug 9, 2023
Fixed by #450. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A Tap address should include a mandetory proof courier address.
The receiving node during the asset send procedure could use this new field to contact a proof courier service and retrieve proof(s) associated with then send event.
In other words: In order to receive and asset, the receiver generates a tap address. That tap address will contain a proof courier address. The sender submits the transfer proof to that proof courier. Which the receiver can then retrieve.
This new field should support multiple proof courier protocols:
This is a prerequisite to #344
The text was updated successfully, but these errors were encountered: