LP-0023: Program Registry — Verified Builds for LEZ Programs - #127
Draft
fryorcraken wants to merge 5 commits into
Draft
LP-0023: Program Registry — Verified Builds for LEZ Programs#127fryorcraken wants to merge 5 commits into
fryorcraken wants to merge 5 commits into
Conversation
Adds a draft prize for an on-chain LEZ program registry: register/update of program metadata with IDLs on Logos Storage, enumeration and search, a claim-authorisation model, and reproducible-build bytecode-to-source verification. Adoption criteria follow the LP-0021/LP-0022 wallet pattern, with a separate count for entries carrying verified source claims. Refs logos-co/ecosystem#196 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
✅ Validation passedA reviewer will assess against the prize criteria. Automated check. See solution template and TERMS. |
Compares against otter-verify, program-metadata, solana-verify and the Explorer's verification UI, and tightens the criteria accordingly: - Replace the open-ended claim model with the canonical/non-canonical PDA pattern from solana-program/program-metadata. - Four verification states rather than three, adding the "claim present but hash mismatched" case the Explorer treats separately. - Require an answer to the build.rs provenance attack, where a matching hash was produced from an attacker-controlled repository. - Require a documented staleness window and last-verified point. - Require the signer behind a claim to be surfaced, not a bare badge, and a "verified is not audited" caveat. Adds a prior-art comparison table and Solana references. Refs logos-co/ecosystem#196 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
fryorcraken
added a commit
that referenced
this pull request
Aug 24, 2026
LP-0023 (Program Registry — Verified Builds for LEZ Programs, PR #127) is now open and follows the LP-0021/LP-0022 adoption pattern. Firm up the prior speculative "not yet written" placeholder into a real dependency: add LP-0023 to both files' dependencies: frontmatter, and change the approval-prompt criterion from optional ("MAY use... not required") to required ("must show the registry's verified source status") for programs registered in it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Rewrite Success Criteria to specify product-level requirements instead of prescribing implementation mechanisms (PDA derivation, singleton accounts, host-timestamp handling). Rename canonical/third-party split to deployer/third-party with a simpler authorization model. Make off-chain storage of source and IDL on Logos Storage an explicit requirement rather than a design choice left to the submitter. Trim FURPS bullets already covered by the Adoption bars, and tighten prose throughout (overstated claims, em-dash density, unrelated citations).
The registry points to both the IDL and source code; the Overview only named the IDL.
Replace prose em-dashes with commas/colons/periods per sentence context. Keep the [text](url) — description convention in reference lists, which reads as normal markdown-list style, not an AI tell. Revert an unnecessary "per the standard adoption evaluation policy" addition from the prior pass.
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
1 participant
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.
Drafts LP-0023, an on-chain program registry for LEZ with verified builds.
Fixes logos-co/ecosystem#196
Number choice
LP-0023. LP-0000–0017 are merged; 0018–0020 are in open PRs (#90, #75, #71, #36, #83, #82); 0021–0022 are in #122.
Shape
Modelled on the existing prior art —
jimmy-claw/spelbook(Rust core, on-chain SPEL program, CLI, FFI) andjimmy-claw/logos-lez-registry-module(Qt6 Logos Core module) — extended to cover what that prototype does not yet do.Working in the prior art: register, author-gated update, lookup by program ID, IDL upload/download to Logos Storage, CLI, browse/detail/register GUI.
Not implemented there, and therefore where this prize puts the work:
lez_registry_listreturns only a count, andget_by_nameis a hardcoded stub; both are marked "requires an off-chain indexer in v1".registered_atis hardcoded to0(zkVM guests have no clock).e2e_testscrate is a placeholder.Adoption criteria
Follow the LP-0021/LP-0022 pattern (#122): 5 third-party integrations, 75 stars, 100 registered programs from ≥40 distinct authors, sustained ≥2 months at ≥20/month, 30 Discord + 30 Twitter/X testimonials, same anti-Sybil framing. 20 entries carrying verified source claims is counted separately — registering metadata is cheap, so the count that signals trustworthiness deserves its own line.
Open points for review
$Xper template.dependencies:entry.dependencies:is currently[].🤖 Generated with Claude Code