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

NEAR: Verifiable RPC replies #76

Open
VictoQ opened this issue Feb 24, 2023 · 0 comments · May be fixed by #343, #387, #389 or #508
Open

NEAR: Verifiable RPC replies #76

VictoQ opened this issue Feb 24, 2023 · 0 comments · May be fixed by #343, #387, #389 or #508

Comments

@VictoQ
Copy link
Collaborator

VictoQ commented Feb 24, 2023

Description 📃

This bounty can be split into sub-bounties by each individual RPC request type (e.g. view access key, view access keys list, transaction in the block, view state, etc). Each sub-bounty can be implemented by a different team. In order to benefit from having Near light client integrated into near-api-js, we need the RPC interface of Near node to return proofs for most of the RPC replies (e.g. have an option to do it when “proof” parameter is passed). For example, the proof of a transaction being included into the block would consist of: merkle path towards transaction in a shard, merkle path towards shard hash. For access keys and viewing state you would need to provide the path in merkle patricia trie. We have already implemented proof for Transaction Status, which you can use as an example: https://docs.near.org/api/rpc/transactions#transaction-status.

Acceptance Criteria 🏁

Please complete your bounties in the form of pull-requests to https://github.com/near/nearcore

Reward Pool 💸

USDC 16000

@epociask epociask linked a pull request Apr 3, 2023 that will close this issue
@anupsv anupsv linked a pull request Apr 3, 2023 that will close this issue
@blocks3k blocks3k linked a pull request Apr 3, 2023 that will close this issue
@antojoseph antojoseph linked a pull request Apr 25, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment