Independent Logos builder — goals, shipped work, honest status
Read this first. I'm one independent builder, new to the Logos stack. This page states my goals, what I've actually shipped, and what is still broken or missing. Nothing here is a prize submission, a claim on anyone's process, or a request for special treatment. Numbers are real or they aren't printed. Assume I'm still learning.

My goals

  1. Ship real, tested tools for Logos builders. Not mockups — things someone else can clone, run, and break. Start with the guest program-ID verification problem I hit myself.
  2. Earn credibility the slow way. Publish failing CI, honest self-assessments and raw logs. Let the code and the test results speak; no fabricated users, testimonials or adoption.
  3. Compete for a λPrize with an actual deployable solution. Focus on LP-0001 (NFT + private proofs) and LP-0021 (wallet + provider SDK). LP-0023 is stood down — an independent implementation is further ahead.

Where we are right now

2released tools
349local passing tests
0on-chain deployments
0users / testimonials

The 349 tests are local and self-verified, including from fresh clones. They are not prize credit, third-party review, or evidence of a working public deployment.

What's actually shipped

📦

proclaim-verify v1.0.0

A CLI for checking RISC Zero guest image IDs from a clean build. Tagged release, cloned fresh from the tag and re-tested there: logic checks pass, SPDX 10/10, known vector correct. Public battle-test kit and 11 recorded adversarial cases.

See the release →

🔐

proclaim-wallet v1.0.0

LP-0021 reference Wallet Provider SDK + CLI. The approval gate is enforced and tested: 23/23 tests pass, 8/8 attack cases held, green CI on the default branch. Mock adapters only — no chain, no keystore, no users.

See the release →

What's built but not shipped

🧪

Local workspaces

Eight local Rust workspaces plus the wallet SDK, 349 passing tests: wallet secure core, consent store, local ledger replay, testimonial model, token ledger, provider protocol, claim-binding demo, a proof statement fixture and the wallet provider SDK. All in-memory or local — no on-chain program.

🔗

Registry code

The proclaim registry program, CLI, HTTP API and JS client exist locally. The E2E lifecycle against a real standalone sequencer now passes end to end, including the HTTP API. The signed Basecamp module installed in an isolated local AppImage (evidence). Nothing has been deployed to a public chain.

🔐

LP-0001 proof work

A real zkVM proof was built locally with measured cycles. It is not published, not on-chain, and worth 0 of 46 criteria.

What's blocking

What's next

  1. Keep the failing→passing E2E evidence and the two bugs it exposed public and reproducible.
  2. Decide whether to deploy the tested program to the live zone — the engineering gate is now satisfied.
  3. Keep shipping small, useful, honest tools that other builders can actually use.

Send a failure case or idea

No form to fill in here. Each button opens a pre-filled GitHub issue in the right repo. You post it from your own GitHub account; nothing is submitted automatically. No keys or secrets, please.

🔍

Guest image IDs

Wrong ID reported, a false pass, or a canonical rebuild that doesn't stabilize the ID.

Open verify issue →

🔐

Wallet approval gate

A call sequence that signs without valid approval, or accepts replay or revoked consent.

Open wallet issue →

🧩

Registry source claim

Where the verification method or evidence is still too weak to mean what it says.

Open registry issue →