PROVADO (PRV) — Whitepaper v0.3
Verifiable reputation for market analysis Discussion draft — October 2026 (v0.3: status updated on 2026-11-06)
Table of contents
- Executive summary
- The problem
- The solution
- How the protocol works
- The PRV token
- Tokenomics
- Technical architecture
- Governance
- Security and risks
- Regulatory considerations
- Roadmap
- Team and treasury
- Step-by-step execution plan
- Glossary
1. Executive summary
Provado is a protocol where market analysts publish predictions ("calls") with stake at risk, and their track record is recorded immutably and auditably on-chain. Analysts who are right build reputation and earn rewards; analysts who are wrong lose part of their stake. Followers pay only for access to analysts with a proven history — not for promises.
The PRV token is what makes the system work: it is used as collateral (stake) on predictions, as the payment currency for subscriptions, and as voting power in governance.
In one sentence: Provado turns "trust me" into "verify my record."
Mission, vision and values
Mission: make the reputation of anyone who calls markets verifiable by anyone, anywhere, without having to trust anyone.
Vision: become the global standard for verified forecasting records. When someone says "this analyst is good", the answer should be "show me their Provado".
Values: proof before promise (nothing is claimed without a record); price is the judge (no human decides who was right); nothing is deleted (the record belongs to the public); product before token (real revenue before any circulation); radical transparency (open code, public statements, known wallets).
2. The problem
The crypto signals and analysis market moves billions but operates with almost no accountability:
- Unverifiable track records. Signal groups show only their wins; losses are deleted or never published.
- Zero skin in the game. The analyst earns the subscription regardless of outcome. The follower is the only one who loses money.
- High cost of discovering good analysts. A trader has to pay for several groups and lose capital to find out who actually delivers.
- Inverted incentives. The more sensational the call, the more subscribers — accuracy is not rewarded.
- No portability. Reputation built on Telegram dies on Telegram; it is not an asset the analyst owns.
None of these failures are fixed by "one more group." They require a neutral record-keeping layer where lying has a cost and being right has a reward.
3. The solution
Provado is a record-keeping and incentive layer with three participants:
| Participant | What they do | What they earn |
|---|---|---|
| Analyst | Publishes calls staked in PRV | Rewards for correct calls + subscriptions |
| Follower | Subscribes to analysts with a track record | Access to calls before resolution |
| Verifier | Runs oracle nodes that resolve calls | Verification fees in PRV |
Design principles
- Record before outcome. A call only counts if it is registered on-chain with a hash and timestamp before the predicted event.
- Stake proportional to confidence. The analyst chooses how much to stake; higher stake means more weight in the reputation score (and a larger loss if wrong).
- Objective resolution. Calls are resolved by price oracles (e.g. "BTC above X by date Y"), not by opinion.
- Reputation as an asset. The analyst's score is a non-transferable (soulbound) NFT they carry to any platform.
4. How the protocol works
4.1 Lifecycle of a call
Analyst → creates call (asset, direction, target, deadline, stake)
→ call is registered on-chain (hash + timestamp)
→ content hidden from non-subscribers until deadline
→ deadline passes → oracle fetches price → call resolved
→ CORRECT: stake returned + reward from pool
→ WRONG: part of stake goes to the reward pool
→ reputation score updated
4.2 Structure of a call
| Field | Example |
|---|---|
| Asset | BTC/USDT |
| Direction | Long |
| Reference price | 71,400 |
| Target | 76,000 |
| Invalidation (stop) | 69,800 |
| Deadline | 14 days |
| Stake | 500 PRV |
| Declared confidence | 70% |
4.3 Resolution
- Target hit before invalidation and within the deadline: correct.
- Invalidation hit first: wrong.
- Deadline passes without touching either: neutral (stake returned, no reward, small network fee).
Prices come from decentralized oracles (Chainlink or Pyth) aggregating multiple sources, which removes manual disputes.
4.4 Reputation score
The score is not a simple hit rate — that would reward easy calls. It combines:
- Stake-weighted hit rate (higher-stake calls weigh more)
- Calibration — if an analyst declares 70% confidence, they should be right on roughly 70% of those calls. Overconfidence is penalized.
- Risk/reward ratio of the calls (distant target with a tight stop is worth more)
- Time decay — older calls weigh less, reflecting current performance
- Minimum volume — the score is only displayed after 5 resolved calls
4.5 Subscriptions
During the pilot the subscription costs R$ 49.90 per month or R$ 499 per year, paid by Pix or card (via Asaas) with a Brazilian CPF; card subscriptions renew automatically and can be cancelled any time, with a 7-day guarantee (right of withdrawal). Crypto payment is not offered. Subscribers receive every call from verified analysts the moment it is registered, with the hash already public. The month's revenue is added up and split as follows: 70% shared among verified analysts, by each one's ranking weight (score multiplied by the number of calls resolved that month), with no guaranteed amount, and 30% to the project (resolution, infrastructure and development). Subscriptions only open once verified analysts are registering calls (goal: January 2027); until then the page shows the waitlist only. In the protocol, later on, PRV may be accepted as a means of payment, and per-analyst pricing (section 6) arrives with the production protocol.
4.6 Penalties and anti-manipulation
- Call spam: minimum stake per call and a cap on simultaneous open calls per analyst.
- Contradictory calls (long and short on the same asset/deadline): detected and voided, with stake forfeited.
- Sybil (multiple accounts): the score requires history; new accounts confer no advantage, and the minimum stake makes the attack expensive.
- Oracle manipulation: multiple sources and a time window, not an instantaneous price.
4.7 Observed scoreboard and claiming (pilot phase)
Before the on-chain protocol, Provado already runs the part that does not depend on a token: the public scoreboard of observed calls. A robot reads, on X, the public calls of analysts who post a numeric target and stop, fixes the Binance reference price at the minute of the post, resolves it under the same rule as the protocol (target before stop = hit; stop before target = miss; neither within 30 days = neutral) and publishes everything at provado.markets/placar, with a link to the original post. These analysts appear as "not yet claimed": they receive nothing, pay nothing and can ask to be removed through the contact e-mail (the record stays; the account is marked as opted out).
Claiming is one word: the analyst replies "claim" in a DM or under one of their calls. The observed record becomes the verified record, new calls keep being read from their posts automatically and, once verified, they enter the revenue share (4.5).
Provado Challenge. Since 2026-11-05 anyone can log calls for free on Telegram with the bot @ProvadoPostBot in 30 seconds; entry is the Binance price at that minute and the calls go into the same scoreboard. Season 1 runs from 2026-11-05 to 2026-12-15. The Founding Verified badge goes to the first 10 people to reach 5 resolved calls with a positive average result (average R > 0). In the protocol, later on, the verified badge will require a minimum score of 60.
Numbers as of 2026-11-06: 22 analysts with valid calls, 145 calls, 112 resolved and 57 hits, out of 76 profiles tracked on X. The scoreboard is updated every 2 days.
5. The PRV token
5.1 Functions
| Function | Description |
|---|---|
| Stake | Mandatory collateral on every call |
| Payment | Analyst subscriptions and protocol fees |
| Governance | Voting on parameters (fees, penalties, oracles, treasury) |
| Verification | Verifiers stake PRV to operate resolution nodes |
5.2 Specification
- Standard: ERC-20
- Network: Base (Coinbase's L2 on Ethereum) — low cost and Ethereum security
- Max supply: 1,000,000,000 PRV (fixed; no inflation beyond scheduled emissions)
- Decimals: 18
5.3 Status as of 2026-11-06
- Contract on Base (mainnet):
0xb4ef6CF51a7509879CD81C126bDb569601a4921E, with verified source. - Supply created at once on deploy: the 1 billion was minted and split across the seven allocations in section 6.1. The team share sits in the vesting contract
0x727bee4BD9b5eb6E3065156DfcbD49aCF614f606and each of the other six sits in its own Safe vault. The contract has no function to mint more. - Not circulating: there is no sale, no liquidity pool, and no tokens have been distributed to third parties. The contract is public for transparency.
- Still missing: a published independent audit and a legal opinion. Sale, liquidity and airdrop (the TGE) only happen after both, and there is no date.
- Checks already done: static analysis with Slither (no high, medium or low severity findings) and 13 automated tests. Report and details at provado.markets/seguranca.html.
- Testnet: the same contracts are also on Base Sepolia for testing.
- Product live: site in three languages, registration tool, FAQ, the Provado Challenge on Telegram and a public scoreboard with 22 analysts with valid calls, 145 calls, 112 resolved by Binance price and 57 hits, out of 76 profiles tracked on X (see 4.7). Subscriptions closed until there are verified analysts (goal: January 2027).
6. Tokenomics
6.1 Initial distribution
| Allocation | % | Tokens | Vesting |
|---|---|---|---|
| Protocol rewards | 35% | 350M | Scheduled emission over 6 years, decreasing |
| DAO treasury | 20% | 200M | Unlocked via governance |
| Team and founder | 15% | 150M | 12-month cliff, 36-month linear vesting |
| Early investors | 12% | 120M | 6-month cliff, 24-month linear vesting |
| Initial DEX liquidity | 8% | 80M | Locked 24 months |
| Public sale (no date; only after a legal opinion) | 6% | 60M | No lock |
| Airdrop / community | 4% | 40M | 50% at TGE, 50% over 6 months |
Rationale: more than half of supply goes to those who use and govern the protocol. Team and investors total 27% with long vesting — below the market average, signaling long-term commitment.
6.2 Value flow
Subscriptions ─┐
Call fees ─────┼──► Protocol fee (10%) ──► 50% burned
Penalties ─────┘ 30% reward pool
20% treasury
- Burn: the burned share leaves circulation permanently, in proportion to real usage.
- Reward pool: fed by penalties and emissions; distributed to analysts with correct calls, weighted by stake and difficulty.
- Treasury: funds development, audits and incentives.
6.3 Emission schedule (rewards)
| Year | Tokens emitted | % of total rewards |
|---|---|---|
| 1 | 105M | 30% |
| 2 | 87.5M | 25% |
| 3 | 70M | 20% |
| 4 | 45.5M | 13% |
| 5 | 28M | 8% |
| 6 | 14M | 4% |
High early emission attracts analysts before subscription volume exists; afterwards the protocol must sustain itself on real fees.
6.4 Staking mechanics
- Minimum stake per call: 100 PRV (adjustable by governance)
- Loss on a wrong call: 30% of stake (adjustable)
- Reward on a correct call: proportional to
stake × (1 − declared confidence)— staking heavily on something you declared unlikely pays more
7. Technical architecture
7.1 Layers
┌──────────────────────────────────────┐
│ Frontend (web + app) │ Next.js, wallet connect
├──────────────────────────────────────┤
│ Indexer / API │ The Graph or Ponder, score cache
├──────────────────────────────────────┤
│ Smart contracts (Base) │ Solidity
│ ├─ PRVToken.sol (ERC-20) │
│ ├─ CallRegistry.sol │ call registration and resolution
│ ├─ Staking.sol │ stake, penalty, reward
│ ├─ Reputation.sol │ soulbound NFT + score
│ ├─ Subscription.sol │ subscriptions and revenue split
│ └─ Governance.sol + Timelock │ OpenZeppelin Governor
├──────────────────────────────────────┤
│ Oracles │ Chainlink Data Feeds / Pyth
└──────────────────────────────────────┘
7.2 Call privacy
Calls use commit-reveal: at registration only the hash goes on-chain (proof of prior existence). The content is stored encrypted on IPFS, with the key released to subscribers. At the deadline the content is revealed publicly so anyone can verify it.
7.3 Why Base
- Transaction fees in the cents — essential for frequent calls
- Inherits Ethereum security
- Active ecosystem, mature tooling (Foundry, Hardhat, OpenZeppelin)
- Alternatives considered: Arbitrum (similar), Solana (cheaper, but Rust tooling and audits are more expensive)
7.4 Recommended stack
- Contracts: Solidity 0.8.x, Foundry for testing, OpenZeppelin as base
- Audits: two independent audits before the TGE (sale, liquidity or distribution)
- Frontend: Next.js + wagmi + viem
- Indexing: Ponder (self-hosted) or The Graph
- Storage: IPFS via Pinata for call content
8. Governance
- Model: DAO with OpenZeppelin Governor + 48h Timelock
- 1 PRV = 1 vote, with a lock-time bonus (veToken, up to 2× for a 2-year lock)
- Quorum: 4% of circulating supply
- Votable parameters: fees, minimum stake, penalty %, accepted oracles, treasury usage, new call types
- Initial phase (12 months): 4-of-7 multisig with emergency veto, dissolved after progressive decentralization
9. Security and risks
Technical risks
- Contract bug: mitigated by audits, a bug bounty (Immunefi) and a gradual launch with stake caps.
- Oracle failure: multiple sources, circuit breaker if sources diverge by more than 2%.
- Front-running: commit-reveal and time-window-based resolution.
Economic risks
- Low analyst adoption: high initial emission + ambassador program.
- Thin liquidity: liquidity locked 24 months, no team sales in year one.
- Score gaming: calibration and time decay make it hard to exploit with easy calls.
Market risks
- PRV volatility changes the real cost of staking. Future fix: allow stablecoin stake with automatic conversion.
10. Regulatory considerations
This section is a map of points to watch, not legal advice. Consult a lawyer specializing in crypto-assets in every jurisdiction where you operate before launch.
Brazil (home jurisdiction)
- Law 14,478/2022 (Crypto-Asset Legal Framework) and Central Bank regulation: virtual asset service providers (VASPs) require authorization. A decentralized protocol may fall outside the scope, but the entity operating the frontend and any custody may not.
- CVM Guidance Opinion 40: if the token is characterized as a security (expectation of profit from the efforts of others), a public offering requires registration. Designing PRV as a utility and governance token — with real use from day one — reduces but does not eliminate this risk. The public sale is the most sensitive point.
- Taxation: crypto gains are taxable (RFB Normative Instruction 1,888/2019 and Law 14,754/2023 for offshore assets). The structure of the issuing foundation/company matters.
- Analysis content: securities analysts in Brazil need CVM accreditation. For pure crypto the rules are looser today, but that may change. The protocol must state clearly that calls are not investment advice.
United States / EU
- US: Howey test exposure; most projects geo-block US participants from token sales.
- EU: MiCA applies to public offerings of crypto-assets and requires a whitepaper filing for certain categories.
Common legal structure: a foundation abroad (Switzerland, Cayman, Panama) holding IP and treasury, with an operating company in Brazil. It adds cost and complexity — a decision to make with counsel.
11. Roadmap
| Phase | Period | Deliverables |
|---|---|---|
| 0 — Foundation | Months 1–2 | Final whitepaper, legal structure, core team, brand identity |
| 1 — Prototype | Months 3–5 | Contracts on Base, mainnet and testnet (done 2026-10-22); site, tool and public scoreboard with observed analysts (done 2026-10-25); 50 invited beta analysts |
| 2 — Audit | Months 6–7 | Two audits, bug bounty, fixes |
| 3 — TGE | No date; only after a legal opinion and an audit | Circulation starts, airdrop to beta testers. The contract has been deployed since 2026-10-22, not circulating |
| 4 — Protocol live | After the TGE | Protocol contracts (stake and score) on mainnet with stake caps, ambassador program |
| 5 — Growth | Months 11–18 | Subscriptions, mobile app, TradingView integration (publish a call from the chart), new call types (stocks, forex) |
| 6 — Decentralization | Months 18–24 | Control transferred to the DAO, multisig dissolved |
12. Team and treasury
Minimum viable team to reach a live protocol:
- 1 founder / product (Estevam Campos Marinho, business administrator and technical analyst)
- 2 Solidity developers (one senior)
- 1 frontend developer
- 1 community / growth lead
- Outsourced lawyer and accountant
- Outsourced audits
Estimated budget to a live protocol: US$250k–500k, with audits as the largest single line (US$60k–150k). This is what the early-investor round needs to cover.
13. Step-by-step execution plan
Stage 1 — Validate the idea (weeks 1–4)
- Interview 20 analysts and 30 signal-group followers. Core question: "would you register your calls with money at risk?"
- Build a landing page with a waitlist. (Done: provado.markets.)
- Run a pilot without blockchain: a public spreadsheet + call hashes posted on X. If nobody joins without a token, nobody will join with one. (In progress: pilot tool and public scoreboard live.)
- Go/no-go criterion: at least 15 analysts willing to join the beta.
Stage 2 — Structure (weeks 5–8)
- Consult a crypto lawyer on structure (foundation + company) and token classification.
- Define cap table and shareholders' agreement.
- Close the core team (at least the senior Solidity dev).
- Finalize the whitepaper with pilot feedback.
Stage 3 — Build (weeks 9–20)
- Write contracts with Foundry; test coverage above 90%.
- Deploy to testnet (Base Sepolia). (Done on 2026-10-22.)
- Minimal frontend: connect wallet, create call, view score, subscribe to analyst.
- Closed beta with pilot analysts using test tokens.
- Iterate the score formula with real beta data.
Stage 4 — Fund (in parallel with stage 3)
- Prepare pitch deck and data room.
- Raise from funds and angels, in the format the legal opinion indicates.
- Fallback if no round: fair launch with reduced scope and a smaller team.
Stage 5 — Security (weeks 21–28)
- Engage two audits (e.g. one boutique + one major firm).
- Fix everything critical and high; publish the reports.
- Open a bug bounty.
Stage 6 — Launch (weeks 29–32)
- Deploy contracts to mainnet. (Token and vesting contracts deployed on 2026-10-22, with allocations held in Safe vaults. The rest of this stage only starts after the audit.)
- Any circulation of the token (liquidity, sale or distribution) only after a legal opinion and a published audit; no date.
- Airdrop to beta testers.
- Open the protocol with low stake caps, raising them weekly.
Stage 7 — Grow (month 9 onward)
- Ambassador program: high-score analysts earn extra PRV for bringing followers.
- Publish weekly leaderboards — the leaderboard itself is marketing.
- TradingView and Telegram integrations (a bot that registers a call on-chain from a message).
What to avoid
- Launching the token before the product. A token with no use becomes pure speculation and attracts the wrong crowd.
- Promising returns. Besides being illegal in many scenarios, it contradicts the project's premise.
- Skimping on audits. It is the one line item where cutting cost can end the project.
- Concentrated distribution. Team + investors above 35% is usually rejected by the community.
14. Glossary
- Call: a price prediction registered in the protocol.
- Stake: tokens deposited as collateral on a call.
- TGE (Token Generation Event): the moment the token starts circulating (liquidity, sale or distribution). The contract can exist before that without circulating, as PRV does today.
- Vesting: gradual release of tokens over time.
- Cliff: initial period with no release at all.
- Oracle: a service that brings external data (prices) on-chain.
- Soulbound NFT: an NFT that cannot be transferred — permanently tied to one wallet.
- Commit-reveal: registering a hash first and revealing the content later, proving it existed beforehand.
- DAO: an organization governed by token-holder voting.
- VASP: virtual asset service provider, the term used in Brazilian regulation.
- Multisig: a wallet that requires several signatures to execute a transaction.