docs: add Kusama grant milestone-3 evidence - #315
Draft
benceharomi wants to merge 19 commits into
Draft
Conversation
Contributor
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
benceharomi
marked this pull request as draft
August 4, 2026 14:14
benceharomi
force-pushed
the
kusama-grant
branch
from
August 4, 2026 19:40
a29c810 to
1ac3d28
Compare
benceharomi
force-pushed
the
kusama-grant
branch
from
August 5, 2026 09:38
adf78a0 to
fefce10
Compare
benceharomi
force-pushed
the
kusama-grant
branch
from
August 5, 2026 09:41
fefce10 to
1636a6f
Compare
benceharomi
force-pushed
the
kusama-grant
branch
from
August 5, 2026 09:44
1636a6f to
bbc19de
Compare
benceharomi
force-pushed
the
kusama-grant
branch
from
August 5, 2026 09:50
bbc19de to
5012bb4
Compare
…entation) Documents deliverable 5 from the submitted grant proposal: chain selection in blueprint creation, on-chain proof verification UI, chain-aware block explorer links, and a fix so manually selected ZK frameworks are respected instead of being overridden.
Points the doc at tests/kusama/ (moved from the flat tests/ dir, now against the current-pipeline kusama_grant_paseo_e2e blueprint instead of the pre-existing test_0001_2) and weaves each test's coverage into the relevant Implementation Notes subsection: chain selector, on-chain verification, and explorer links. Replaces the TBD CI placeholder with a real passing run.
"Not X, which predates it" is reasoning about our own process, not a fact a curator needs about this blueprint. State what it is, not what it isn't.
Not part of the submitted deliverable text ("target chain selection and
on-chain proof verification"). It's a real fix, but it's about which
proving system gets used, unrelated to chain selection or on-chain
verification. Same call already made for sdk-js's Noir v2 item.
Step-by-step walkthrough with screenshots covering blueprint creation, setting Paseo as the target chain, proof generation, and both local and on-chain verification through the registry frontend.
Reproduces a blueprint's deployed verifier contract bytecode from its downloadable circuit.zip and compares the hash against the on-chain code, since PolkaVM deployments have no source-verification service yet. Verified independently on two clean rebuilds.
These links were off by one level from the start (predates the docs/ directory reorg in the other repos), pointing at docs/src/... instead of the repo's actual src/... Found while auditing all kusama-grant docs across repos for dead links, prompted by a curator flagging milestone 2.
Extends the bytecode-verification methodology already used for the wrapper to the Groth16Verifier it calls: reads GROTH16_VERIFIER() off the deployed wrapper rather than just stating the address, and compares its runtime bytecode against a clean rebuild from the same circuit.zip bundle. Both match. Answers Reza's follow-up ask for this same evidence pattern to cover the verifier, not just the wrapper.
Closes out Reza's remaining bytecode-verification ask: the sdk-images generator commit, circuit.zip and zkey hashes, alongside the wrapper and Groth16Verifier runtime hashes already documented above. Compiler settings point back at the bundle's own hardhat.config.ts rather than restating them, since that's already reproducible by anyone who downloads the bundle.
Demonstrates the same real proof succeeding while its DKIM key is valid in the M1 registry, then failing after that exact key is revoked, using 4 real on-chain transactions (revoke, failed verify, restore, succeeding verify) against the real deployed contracts. No new proof generated - the deployed wrapper's domain check is a compile-time constant, so a separate test domain would need an entirely new deployment; revoking and immediately re-registering the existing key demonstrates the actual state transition with a window of a few seconds and no lasting effect. Answers Reza's follow-up on this point, and distinguishes it from the existing bit-flip negative control in milestone 2's 06_e2e_demo.md, which hits the same InvalidPublicKey() error but for a fabricated hash rather than a real registry state transition.
…c 05 Adds the new verifyTamperedProofOnChain.ts test to the coverage table and updates the example passing CI run to today's, which includes it.
…nance table Was a placeholder in the reproduce command; now a real, independently checkable value (the blueprint's own updated_at via its public API), with its own table row and reproduce command.
…tations Centralizes the wrapper/Groth16Verifier addresses, deployment and proof-verify txs, the revocation demo's 4 txs, and CI run links - facts previously repeated across multiple docs (wrapper address alone was cited 16 times across all three repos' docs). Docs link to it by line range instead of restating values inline. Not touching doc 07's own Deployment Manifest table (canonical source) or literal values inside reproduce command blocks.
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
2 participants
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.
Summary
docs/kusama-grant/tracking delivery evidence for this repository's Milestone 3 deliverable (deliverable 5, verbatim from the submitted proposal)05_frontend_integration_and_documentation.md: implementation notes for chain selection, the on-chain verification UI, and dynamic block explorer links, citing the real Playwright test suite attests/kusama/, which runs in CI on every push tostaging/main06_public_howto.md: step-by-step public walkthrough with screenshots - create a blueprint, set Paseo as the target chain, upload an email, generate a proof, and verify it both locally and on-chain through the UI07_bytecode_verification.md: reproduces a blueprint's deployed verifier contract bytecode from its downloadablecircuit.zipand confirms it matches on-chain, since PolkaVM deployments have no source-verification service yet