Account and worker foundation
Wallet authorization, revocable worker credentials, challenge issuance, native proof verification and durable contribution records.
RELEASE STATUS / EVIDENCE & NEXT STEPSSoftware evidence.
Software evidence.
Deployment milestones.
A software test, a running web container, a GPU inference run and a funded contract claim answer different questions. This page keeps their scopes explicit.
THIS DEPLOYMENT · COORDINATOR SNAPSHOT
Refresh statusService configuration
- Contribution storage
- Available
- Work admission
- Paused
- Verifier configuration
- Configuration present
- Reward network
- Chain 46630
Snapshot: 2026-10-24 15:13:09 UTC. Configuration presence does not establish verifier health or GPU validation. Work requests make the native verifier health check before a job is issued.
What the existing test record covers.
| Area | Recorded checks | Scope |
|---|---|---|
| Native mining integration | 25 checks | Real Pearl Rust/PyO3 verification and TCP bridge, with CPU-generated test proofs. |
| Persistent VPS ledger | 6 checks | Migrations, uniqueness, rollback, reopen persistence and consistent backups. |
| Production web flow | 7 checks | HTTP routes, wallet registration, process restart, canonical HTTPS origin and Secure cookies. |
| Protected inference boundary | 12 checks | Authorization, request limits and server-side provider credentials. |
| Funded reward contracts | 10 checks | Local EVM funding, immutable roots, recipient binding and claim replay rejection. |
The baseline records 60 passed behavioral checks and a production Next.js build on Node.js 24.19.0. Mining fixtures were generated on CPU and checked by the actual pinned native verifier. Contract checks used a local EVM. These are a recorded software validation scope, not live GPU or mainnet measurements.
Download the baseline validation recordWhat must happen before broader participation.
GPU inference to accepted share
Build on supported hardware, load the reference checkpoint, run an actual AI request and verify its proof-to-ledger path. Web container uptime does not complete this gate.
Reachable mining service
Deploy the authenticated HTTPS verifier, validate its health and capacity, then enable admission on the intended participant endpoint.
Funded epoch and real claim
Deploy the test token and distributor on Robinhood Testnet, publish and fund the allocation root, activate the matching epoch and confirm a claim.
Security and mainnet decisions
Independent review, token distribution rules and any Pons launch require their own validation and publication. No mainnet date or allocation is set here.
What is not a published measurement.
No Perla GPU throughput, energy-efficiency comparison, earnings estimate or customer-demand figure has been established by the baseline test record.
No independent external audit or EVM-native Pearl ZK verifier is claimed. Operators remain trusted to run the offchain verifier and publish a complete allocation.