-
Notifications
You must be signed in to change notification settings - Fork 3
feat(dekuIntegration): add sign_payload and key #46
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
Conversation
ed3aa7b to
e28d82f
Compare
e28d82f to
bbe64b2
Compare
lib/pnode/pnode.mli
Outdated
| val init : | ||
| ?preprocess:(Message.t -> Message.t) -> | ||
| msg_handler:(Message.t -> bytes) -> | ||
| msg_handler:(Message.t -> bytes * bytes option) -> |
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.
I though a lot (too much) about this, I think making msg_handler returning a bytes * bytes option (where payload:bytes and payload_signature:bytes option) is the best option.
What do you think @rosalogia?
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.
Since responses will become optional as well, it will probably be bytes option * bytes option. I think that's fine!
|
Can we merge #33 first? 😅 I don't mind being the one to rebase this PR after that. |
Of course 😉 |
8870703 to
595d99c
Compare
595d99c to
788e99d
Compare
|
Closing in favor of #48 |
Context
For some messages, Deku needs to sign the payload
Proposal
Make
msg_handlerreturning a tuple(payload, payload_signature)of typebytes * bytes option