Feature availability
Published capabilities, finite Devnet scope and remaining acceptance.
This page describes the documented release as of 22 October 2026. It is a capability reference; the live mining page and public configuration determine the currently admitted task and funding state. An older successful acceptance run does not imply that the same task is still open.
Published website capabilities#
| Capability | Documented state | Practical scope |
|---|---|---|
| Documentation and public reading | Available | English and Chinese guides with categories, local search and section links |
| Neuron atlas | Available | 11,751 source types and representative structural views |
| Model preparation and cache reuse | Implemented and deployed | Verified resources, browser persistence and retained chunks |
| Complete-model computation | Implemented and deployed | Frozen model/task rules; explicit user action |
| Pause, resume, saved results and snapshots | Implemented and deployed | Browser storage and declared compatibility boundaries |
| Candidate submission and complete replay | Implemented and deployed | Authorized current scientific policy |
| Public result packages | Available when authorized | Explicit publication, download and reproduction scope |
| Explorer query and evidence pages | Published | Public projection; no private candidate or customer access |
| Private service request tickets | Implemented | Scope, quote, authorization and delivery stages |
Wallet Mining V3 on Devnet#
Wallet Standard UI, origin-bound sign-in, finite grants, durable financial intents, atomic Result creation/payment and history are implemented. Public Devnet acceptance completed two distinct full-model winners under one grant, paying one FBW each.
The initial two-unit acceptance plan is complete. A separate task-supply-20261013-v1 stage now funds two unused, prospectively calibrated full-model targets: one FBW each, two FBW total. Scientific plan revision 3 opened round 32, with the next goal queued. The mining page shows live availability; only the corresponding frozen unit can pay its verified winner. Model preparation, wallet history and applicable unused-principal withdrawal remain usable after a finite stage completes.
The first dedicated Result was closed after archive certification; the second remains readable. Permanent payment evidence prevents a closed Result from causing a second payment or a second rent debit. See FBW Devnet reference for the public receipts.
Evidence that still needs actual acceptance#
| Gate | Current boundary |
|---|---|
| Real extension wallet confirmations | Mock-wallet Chromium and scripted signing checks exist; actual extension confirmation remains pending |
| Physical Android Chrome and GPU devices | Simulated viewport/WebGL checks exist; physical-device acceptance remains pending |
| Low memory, higher concurrency and simultaneous compute/3D | Broader device and capacity acceptance remains pending |
| Validator participation | Voluntary FBW user participation under each task's published admission and evidence policy |
| External biological validation | Authorized observations, calibration/holdout evaluation and review remain pending |
| Full snapshot disaster recovery | Backup/restart records exist; the complete disaster-recovery drill remains pending |
Marketplace and future network features#
The proposed catalog, draft price templates, migrations and read-only catalog API are implemented. Host-tested financial primitives enforce finite allowances, accounting and claims. Native service workers, real Ridge training/export, service SBF/SPL integration, finite paid API usage, settlement/refunds and historical-claim flows remain incomplete.
Validation participation follows task-specific admission and evidence policies. Installation, broader admission and staking have their own release criteria. Network, asset and customer payment activation use their published configuration, approvals and funded budgets. Read the Marketplace roadmap and Economic model for those criteria.
How to interpret status#
A numerical replay confirms the declared model computation. A browser test confirms its tested interaction or layout. A finalized chain receipt confirms that financial action. Physical-device and external-science claims require their respective evidence. Each guide keeps these scopes separate so you can assess what an outcome actually establishes.
Community participation#
Social provides signed-in wallet challenges, X public evidence verification, durable manual review, community points and a real leaderboard. Published budgets are preparation scope: no token transfer or immediate claim is enabled. Official OAuth and actual extension/human X confirmation require separate external acceptance. See the community guide.
See feature availability for release scope and pending acceptance.