Native launches and trades use Solana Devnet test assets. Mainnet execution is not enabled; external market data is read-only.
Verification confirms defined factual evidence. It is not an investment rating, endorsement, or guarantee.
A project-specific challenge validates control of the configured domain. It does not establish product legitimacy, usefulness or economic value.
A bounded HTTP check tests the configured website against its response rules. Availability at one observation does not establish meaningful product functionality or continuous uptime.
The connected GitHub identity must meet the repository access rules (personal ownership, administration or maintenance). This proves the access relationship, not code quality, originality or business viability.
The current evaluator requires a positive recent commit count or repository activity within the trailing 30-day window. Activity is evidence of repository changes; it does not measure their quality or usefulness.
One configured request checks HTTP status and optional response assertions. Method, expected status, observation time and assertion result belong to the evidence. A successful check is not an uptime measurement.
Observed samples are evaluated against configured minimum successful checks, window duration and availability. Defaults are 24 successful checks across at least 24 hours and 99% observed availability. Sampling cadence depends on the configured worker; this is sampled availability, not continuous monitoring. Inspect actual sample dates and configured thresholds.
The GitHub evaluator checks recorded release availability. A release record does not prove installed software works or has been independently reviewed.
Configured product metrics and event evidence are evaluated against the project's requirement. An integration reporting events does not independently prove unique humans, revenue or organic adoption.
Commitments retain original deadlines and recorded changes. Submitted evidence requires authorized verification; a builder marking a task done is not verification. Overdue/cancelled states describe commitments, not investment conclusions.
A configured requirement and authorized review describe a specific factual claim. Custom evidence has no universal automated assurance; inspect the claim, evidence and verifier history.
Evidence → Verification → Normalization → Canonical representation → SHA-256 → Onchain attestation
Source material, normalized results and verification history remain in the application database. Deterministic evidence serialization produces a SHA-256 digest. An authorized verifier can attest that digest in a program ProofRecord; the chain stores the digest and attestation state, not the full source material. A stored database verification and an onchain attestation are separate steps. A hash proves a commitment to particular bytes, not that their factual claims are true.
Inspect the timestamp, current state, hash and explorer link where present. Failed checks, expiration and revocation must be read in the history. Reverification creates a new observation; an old attestation does not establish current availability. Automatic stale handling varies by proof type and worker configuration, so do not assume every proof is continuously rechecked.
Verified proof counts describe recorded requirements. Evidence categories summarize Domain, GitHub, API, Release and Usage; they are not a count of individual attestations. The protocol separately adds configured verified milestone weights toward the project’s BUILD threshold. These weighted points are not a quality score. MARKET uses the configured reserve threshold. PROVEN requires the supported lifecycle checks and recorded graduation; an external token has no PROVE curve or formal PROVEN graduation.