ProvadoPRV

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

  1. Executive summary
  2. The problem
  3. The solution
  4. How the protocol works
  5. The PRV token
  6. Tokenomics
  7. Technical architecture
  8. Governance
  9. Security and risks
  10. Regulatory considerations
  11. Roadmap
  12. Team and treasury
  13. Step-by-step execution plan
  14. 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:

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

  1. Record before outcome. A call only counts if it is registered on-chain with a hash and timestamp before the predicted event.
  2. 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).
  3. Objective resolution. Calls are resolved by price oracles (e.g. "BTC above X by date Y"), not by opinion.
  4. 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

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:

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


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

5.3 Status as of 2026-11-06


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

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


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

7.4 Recommended stack


8. Governance


9. Security and risks

Technical risks

Economic risks

Market risks


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)

United States / EU

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:

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)

  1. Interview 20 analysts and 30 signal-group followers. Core question: "would you register your calls with money at risk?"
  2. Build a landing page with a waitlist. (Done: provado.markets.)
  3. 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.)
  4. Go/no-go criterion: at least 15 analysts willing to join the beta.

Stage 2 — Structure (weeks 5–8)

  1. Consult a crypto lawyer on structure (foundation + company) and token classification.
  2. Define cap table and shareholders' agreement.
  3. Close the core team (at least the senior Solidity dev).
  4. Finalize the whitepaper with pilot feedback.

Stage 3 — Build (weeks 9–20)

  1. Write contracts with Foundry; test coverage above 90%.
  2. Deploy to testnet (Base Sepolia). (Done on 2026-10-22.)
  3. Minimal frontend: connect wallet, create call, view score, subscribe to analyst.
  4. Closed beta with pilot analysts using test tokens.
  5. Iterate the score formula with real beta data.

Stage 4 — Fund (in parallel with stage 3)

  1. Prepare pitch deck and data room.
  2. Raise from funds and angels, in the format the legal opinion indicates.
  3. Fallback if no round: fair launch with reduced scope and a smaller team.

Stage 5 — Security (weeks 21–28)

  1. Engage two audits (e.g. one boutique + one major firm).
  2. Fix everything critical and high; publish the reports.
  3. Open a bug bounty.

Stage 6 — Launch (weeks 29–32)

  1. 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.)
  2. Any circulation of the token (liquidity, sale or distribution) only after a legal opinion and a published audit; no date.
  3. Airdrop to beta testers.
  4. Open the protocol with low stake caps, raising them weekly.

Stage 7 — Grow (month 9 onward)

  1. Ambassador program: high-score analysts earn extra PRV for bringing followers.
  2. Publish weekly leaderboards — the leaderboard itself is marketing.
  3. TradingView and Telegram integrations (a bot that registers a call on-chain from a message).

What to avoid


14. Glossary