Add auto-verification monitor, upgrade webhooks, and GitHub Action to SCF #44 scope#10
Merged
Merged
Conversation
… SCF #44 scope Extends the SCF #44 submission and architecture doc with the automation layer that made source verification ubiquitous on Ethereum: - Automatic verification: a ledger monitor that verifies new SEP-58 contracts with no submission step (the Sourcify chain-monitor role), forward-only by construction, plus signed upgrade webhooks so consumers learn when a badge drops in real time. - A published GitHub Action that submits verification as a CI deploy step and fails on anything but FULL_MATCH (the forge verify-contract role). - Coverage dashboard and open-data export noted as beyond-the-grant roadmap. Budget raised $85k -> $100k with clean tranche math (10/20/30/40), engineering window extended 16 -> 18 weeks, and a new Tranche #3 deliverable for the monitor and webhooks. Also adds the SCF #44 submission draft and pitch video script.
The submission form (docs/scf-44-submission.md) is a working draft pasted into the SCF Build Award form, not a repo artifact. Remove it from version control and gitignore it; the architecture doc remains the canonical public spec. Paragraphs in the local draft are unwrapped to single lines for clean copy-paste into the form.
The video script (docs/video-script.md) is recording material for the SCF pitch video, not a repo artifact. Remove it from version control and gitignore it alongside the submission draft; the file stays on disk locally.
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.
What
Extends the SCF #44 architecture doc with the automation layer that made source verification ubiquitous on Ethereum, in response to the question of what else the proposal could promise beyond pull-based submission. The submission form and pitch video script are kept as local working drafts and are no longer tracked in the repo (see below).
Scope added (
docs/ARCHITECTURE.md)contractmetav0and verifies any new contract with complete SEP-58 metadata, no submission step (the role Sourcify's chain monitor plays on Ethereum). Forward-only by construction, with the rationale written in (RPC retains ~a week of history; pre-SEP-58 contracts carry no metadata and are covered by the retroactive path).FULL_MATCH(theforge verify-contractrole), with a public example repo.Working drafts untracked
docs/scf-44-submission.md(the SCF Build Award form draft) anddocs/video-script.md(pitch video recording material) are working assets, not repo artifacts. Both are removed from version control and added to.gitignore; they stay on disk locally. The architecture doc remains the canonical public spec. (The submission scope and budget — $85k → $95k total, 10/20/30/40 tranches, 16 → 18 week window, new Tranche Parse SEP-58 metadata fields and surface source mode in read CLI (STE-53) #3 monitor/webhooks deliverable — live in that local draft.)Files in this PR
docs/ARCHITECTURE.md— automatic-verification subsection, integration entries, roadmap updates..gitignore— ignore the local submission and video-script drafts.Note
Submission deadline is June 14, 2026. The local draft still has open
TODOs (video URL, thumbnail, ambassador answer, team SCF accounts).