Risk disclosure

Plain-language description of how PROVE works and what can go wrong. This is a draft for counsel. It is not investment advice and not a guarantee of any outcome.

Tokens launched through PROVE can fall to zero. Buyers can lose the SOL they spend. Past volume, social attention, or a PROVEN label do not imply future price.

While a bonding curve is open, liquidity is the curve vault and configured virtual reserves — not a deep open-market book. After graduation, liquidity depends on whatever external pool (if any) was actually created and verified. Thin markets can mean large price impact and failed exits.

Teams can abandon work, miss milestones, ship broken software, or never graduate. Listing on PROVE is not a diligence certificate.

A verified proof means a trusted verifier accepted specific evidence under PROVE's rules and recorded a hash on-chain. It does not mean the product is profitable, safe, complete, or a good investment.

Repository metrics and activity snapshots are factual inputs when collected. They do not prove identity, honesty, exclusive ownership of code, or future delivery. Public GitHub can be spoofed, forked, or abandoned.

PROVE does not guarantee project marketing claims beyond the specific verified evidence tied to a proof record. Unverified text on a project page is creator-supplied. Off-chain rows can be wrong or delayed relative to the chain.

Buys and sells use integer constant-product math with virtual and real reserves. Price moves with every trade. There is no floating-point rounding in the protocol path; small inputs can still be economically meaningless after fees.

Each buy/sell can charge a protocol trade fee in basis points from on-chain PlatformConfig. Creating a project may charge a launch fee in lamports. Current values are summarized on /fees. Fees reduce what you receive.

Trades require an explicit minimum-out (slippage) bound. If the market moves before confirmation, the transaction can fail. Setting slippage too wide increases the chance you accept a worse price; setting it too tight increases failed transactions.

A project becomes eligible for PROVEN only when both the market threshold and the proof threshold are met on-chain. Eligibility closes the curve; it is not itself an external pool. Finalization and any DEX migration are separate steps. Mock adapters never invent a real pool address. A graduated pool can still be illiquid or risky.

Creators may reserve a capped allocation (default often 0%, protocol max typically 5%) minted into a vesting vault. Tokens unlock over time after a cliff. Allocation is public at launch and is not instantly liquid inventory for the creator.

The on-chain admin can update bounded platform parameters, rotate verifier and fee recipient, pause or unpause, and transfer admin via a two-step process. Admin cannot seize curve reserves, mint extra supply after launch, or reverse user transfers. Off-chain moderators can only change catalog visibility.

If the program upgrade authority is not revoked, the program can be upgraded by whoever holds that authority (ideally a multisig on mainnet). Upgrades can change behavior. See /protocol and readiness docs for how authority is intended to be controlled.

On-chain proof verification is authorized by the configured verifier authority. You are trusting that authority (and any off-chain verifier service that signs for it) to evaluate evidence honestly and to keep keys secure. A compromised or malicious verifier can approve false proofs or fail to approve true ones until governance rotates it.

Do not read this product as: safe investment, good investment, investment score, trust score, guaranteed, or low risk.