Explorer guide
Follow rounds, candidates, verification and on-chain settlement evidence.
The Explorer follows public scientific competition and financial evidence. It reads a dedicated public projection through an independent query process. Private candidate bodies, salts, customer requests, archive paths and signing material are outside that projection.
Choose the record you need#
Use the published overview and round/candidate links to follow a task outcome. A round summarizes the competition. Candidate detail shows its claim/order, verification and linked evidence. A funded V3 candidate also links the wallet, grant, permanent unit, temporary Result and finalized payment.
The project Explorer is different from the general Solana Explorer. Use the project page for semantic task/claim relationships, then use its Solana links to inspect the exact on-chain action and cluster.
Read evidence in order#
- Check the task/round and frozen scientific identity.
- Check whether the candidate was eligible and fully submitted.
- Read complete replay evidence and authorized verification scope.
- Read the winner decision and authority receipt sequence.
- Follow the economic unit and original beneficiary.
- Read Result state and finalized payment evidence.
A candidate marked scientifically complete may still have financial reconciliation in progress. A temporary Result may be closed while permanent finalized payment evidence remains available.
Scientific status versus payment status#
| Visible fact | Interpretation |
|---|---|
| Complete/qualified computation | Local work met its numerical criterion |
| Verified candidate | Required authorized replay accepted it |
| Winner | The frozen competition rule selected it |
| Reserved/accepted amount | A finite financial obligation exists |
| Transaction submitted or unknown | Reconciliation is still required |
| Finalized received reward | Actual asset evidence confirms receipt |
| Result closed | Temporary storage was closed under its policy; payment uniqueness remains |
Do not infer a reward from throughput, task completion alone or an unfinalized signature.
Pagination, freshness and faults#
Historical browsing uses stable cursors. Continue with the page's next/previous controls instead of reconstructing ordering from client timestamps. Date fields and receipt sequence are separate values.
Query or RPC failures must not overwrite trusted finalized data with an unsupported negative fact. A missing RPC response is not proof that a payment or account never existed. Check the visible freshness/error state and retry reading; financial reconciliation retains its original business identity.
The public projection can lag the authority or finalized chain. Compare the record's evidence and update state rather than assuming a temporary presentation difference is another payment.
Sharing and privacy#
Share the public round/candidate URL and transaction signature for a question about an outcome. Keep private receipt tokens, salts, raw customer data and session credentials out of public support messages.
For published scientific packages, use Results and reproduction. For fixed program/mint and completed receipts, use FBW Devnet reference. The Explorer presents evidence; reading it does not initiate computation, funding or settlement.
See feature availability for release scope and pending acceptance.