Current status
Updated: 2026-09-07. All blockchain activity described here is Solana Devnet test activity.
Local build readiness
Rust/Cargo and Solana tools are restored in shared locations outside /workspace, with shell startup configuration for other chats using this same environment. On 2026-09-07, all eight Rust tests passed and a fresh SBF build exactly matched the saved 33,104-byte v0.3.0 executable. This confirms local compilation readiness; no new deployment or live-chain validation was performed as part of the installation. See Development for paths, versions and reinstall checks.
Read reliability
User-confirmed working: jpc confirmed the published retry/refresh fix works on 2026-09-07. The shared fix covers the homepage, Moves and Moments. The intermittent “decoding” stall was supported by a logged 12-second account-read timeout among otherwise fast successful reads; caching was not established as the cause. This confirmation is user feedback, not a completed cloud-browser verification.
The 2026-09-07 incident check found all 100 V3 records intact and the deployed executable matching the saved release. A CLI full-gallery read over public Devnet completed in 24.6 seconds; production logs showed repeated browser cancellations near the former 18-second limit. This was not missing-state recovery.
Consumer reads now use request-owned cancellation, a 35-second total server budget and a 40-second browser budget. No unfinished promise is shared between Worker requests. Independent checks run concurrently, optional unavailable history is flagged/omitted, and polling normally waits 30 seconds after completion. Read-only RPC attempts now retry transient failures once with a 5-second per-attempt deadline. Failed refreshes retain the last verified same-query view with its timestamp, and the first transient page failure retries after 1.5 seconds. The separate footer retains only its completed 30-second status cache. Program bytes, minted records and evolution clocks are unchanged.
Program and minting
Program v0.3.0 is compiled and deployed. Program address: 3tQdNmR9ArfHm2SELZR5iWHMFoytJComvzJ7UvKdRP7C. Retained executable: discovery_registry-v0.3.0.so, 33,104 bytes. SHA-256: 95d4912eee6ab92bd19ab50760fe4a917b4ad17d7eff77c0f0bf9d792ee14437. The confirmed deployment's on-chain bytes match the locally compiled executable; source hashes are retained in the artifact manifest.
The 216-byte V3 format enforces platform-only issuance, evolution-dominant multi-factor birth terms and immutable reward/access inputs. V1/V2 remain readable under their original formulas. See Minting for exact rules. This remains a custom encrypted-record protocol, not a standard marketplace NFT mint.
Active experience
The Flex, Moves and Moments use a refreshed 100-record generation with eight Stashes. Public pages use real program quotes, authenticated temporary images, current ownership, original claimant, reference prices, listings and controlled transaction receipts. Hidden inventory is excluded before public serialization. Three type-selected games use actual encoded records and server-validated puzzles. Paid checkout, discounts, clipping membership/rewards and event-driven videos are not enabled. The standalone /reel concept-video page is live and accepted as a first pass; it now includes an exploratory watch Look Shift and remains separate while content is refined.
Evidence and limits
| Evidence | Scope |
|---|---|
evidence/toolchain-installation.json |
Shared tool locations/versions, eight passing Rust tests, exact saved-release rebuild and default SBF compiler smoke build; no chain writes |
evidence/deployment.json |
Current program transaction, byte-for-byte executable match and finalization |
evidence/gallery-v3-seed.json |
Refreshed 100-record batch, cadence counts and confirmed controlled activity |
evidence/mint-v3-verification.json |
All-record authentication, program quotes, signed authorization/reward simulations, pagination/privacy and legacy compatibility |
evidence/chase-v3-hosted.json |
Published HTTP/API verification of each type-selected game and reveal-only play, current gallery reads, issuer-only preparation and rejection of an unsigned claim |
evidence/chase-claim.json |
Actual published wallet-signed claim of the original sample, owner/finder preservation, public Moment and idempotent receipt resolution |
Focused Rust tests cover authorization, claim policy, evolution dominance, legacy behavior and calendar/price rules. JavaScript checks cover formula inputs, authenticated recipe tampering and game-profile dispatch. TypeScript validation and the Sites build cover the consumer integration. The standalone legacy rendered-metadata test needs the Cloudflare runtime and does not run through plain Node; it is not live API verification.
The claim test used a locally controlled test wallet, not a Phantom UI automation. No internal preview browser is used for this work. No future calendar date or destructive Devnet reset is induced; calendar boundaries and reset guards have focused tests and recovery logic. No production supply cap, market valuation, automated abuse resistance or final asset category is claimed.
Next
Brainstorm actual assets. Their structure, media and behavior will refine minting, evolution and games. The secondary behavior factor is a deliberately small authored starting factor, not a measured complexity metric. Production quotas, economic terms, wallet onboarding and asset-specific rarity commitments remain open.