Solution: LP-0005 — Private Balance Attestation #74
Open
dubzn wants to merge 1 commit into
Open
Conversation
✅ Validation passedA reviewer will assess against the prize criteria. Automated check. See solution template and TERMS. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Submission for LP-0005: Private Token Balance Attestation.
Implementation repo:
https://github.com/dubzn/logos-private-balance-attestation
This solution includes:
getProofForCommitment.demo.sh, SPEL-style IDL JSON, Basecampmodule.json, CI, local benchmark docs, and clean-room runner.Validation command:
With local LEZ sequencer/wallet/private account:
Important on-chain note:
The repo includes two local on-chain candidates:
Workable public LEZ gate:
The host verifies the RISC Zero proof envelope before submitting the LEZ gate transaction; the LEZ program records/deduplicates the context nullifier.
PPE-native LEZ gate:
LEZ private execution checks
balance >= thresholdand writes public gate/nullifier state. This passed locally withRISC0_DEV_MODE=0, including duplicate and insufficient-balance rejection.Open evaluator question:
For LP-0005, should the final on-chain path be the PPE-native private execution gate, or is there a supported public LEZ pattern for verifying an externally submitted RISC Zero receipt inside a LEZ program?
Relevant docs:
docs/SUBMISSION_STATUS.mddocs/ONCHAIN_PATH_DECISION.mddocs/PRIZE_CHECKLIST.mddocs/EVALUATOR_GUIDE.md