-
Notifications
You must be signed in to change notification settings - Fork 2
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
Auxiliary data for program evaluation #475
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
933efd8
to
d75ed57
Compare
(I'm gonna take a look at this in a couple of hours, don't merge it in yet 🙏) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few comments, but otherwise looks good.
Can you add an entry to the CHANGELOG
and indicate that this is a breaking change?
(Changed the title since we don't use conventional commits) |
Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
4b66671
to
089c711
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for answering my questions. Still missing a CHANGELOG
entry 😉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just the CHANGELOG thing, but otherwise looks good!
Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
Co-authored-by: Hernando Castano <HCastano@users.noreply.github.com>
* master: Integration test for validator joining network (#493) Add `ENTROPY_NODE` environment variable (#497) Change `SocketAddr` type for `String` (#496) Allow big protocol messages (#495) Add test for `EncryptedConnection` (#494) Use bincode rather than JSON for protocol and subscribe messages (#492) Remark on possible need to address TSS server from the Docker host. (#490) no proactive refresh on private key visibility (#485) Auxiliary data for program evaluation (#475) Validate proactive refresh endpoint (#483)
This allows programs to include an auxiliary data field, which can include data relevant to the evaluation of the program (eg zero knowledge proofs, third party signatures), but data that should not be part of the actual message that will be signed.
@frankiebee @jawndiego This changes the JSON payload body of the
/sign_tx
endpoint as follows:transaction_request
is renamed tomessage
auxilary_data
is a hex encoded string (just likemessage
) of the extra data the user might want to include in their signature request