Skip to content

feat: NitroRPC app implementation #1

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

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open

Conversation

philanton
Copy link

No description provided.

@philanton philanton force-pushed the feat/nitro-rpc-app branch from 849e85a to baae394 Compare March 11, 2025 16:20
Comment on lines +47 to +50
PayloadSigned memory payloadSigned = abi.decode(candidate.variablePart.appData, (PayloadSigned));
requireValidPayload(fixedPart, payloadSigned);

return (true, "");

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have any other checks pertaining to Payload? Should payloads be chained, in which case we should introduce proof checks?

philanton and others added 3 commits March 18, 2025 15:09
* feat: nitro-rpc proto and golang draft implementation

* feat: add compatibility tests for signing

* forge install: openzeppelin-contracts

v5.2.0

* import openzeppelin contracts

* fix: packing and signing

* add questions

* Update README.md

* Update README.md

* Descriptiong NitroRPC convention

* Fixed todolist

* Update headers

* nitro client api overview

---------

Co-authored-by: Louis <mod@yellow.org>
Funding, and Finalize
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

Successfully merging this pull request may close these issues.

3 participants