On-Chain Reputation

Proovly’s trading happens off-chain. It has to: MT5 is not a blockchain, brokers aren’t smart contracts, and trying to shoehorn real market fills onto a chain gives you a worse product, not a better one.

But there’s one thing Proovly puts on-chain, and it’s the thing the old prop firm industry never did: your reputation.

The problem with CRM-trapped credentials

When you pass a challenge at FTMO, what do you get?

• An account in their back office
• An email saying you passed
• A row in their CRM

If FTMO goes bankrupt, or kicks you off, or decides to unilaterally reset your status, that row is gone. There’s no durable credential. No portability. No proof, outside FTMO’s own database, that the thing happened.

This is why every prop firm treats you like inventory. They know that if you leave, you take nothing with you.

The on-chain credential

Proovly deploys one contract: EloRegistry.sol, on Base mainnet. That contract does exactly two things:

1. Emit a ChallengePassed event when a trader passes a challenge
2. Maintain a mapping from wallet address to current ELO rating

When you pass a challenge, our committer wallet calls:

function recordPass(
    address wallet,
    bytes32 challengeId,
    uint8 tier,
    uint16 profitBps,  // e.g. 842 = 8.42% profit
    uint64 ts
) external onlyRole(COMMITTER_ROLE);

This emits:

event ChallengePassed(
    address indexed wallet,
    bytes32 indexed challengeId,
    uint8 tier,
    uint16 profitBps,
    uint64 ts,
    uint32 newElo
);

and bumps your wallet’s ELO using the same formula the Proovly game engine calculates off-chain.

That’s it. No fancy logic on-chain. The heavy work is done off-chain by the rules engine; the on-chain contract is a trust-minimised log + counter.

What you can verify with this

Anyone, anywhere, at any time can query EloRegistry.sol on Base and ask:

• “How many Proovly challenges has 0xABC... passed?”
• “At what tiers?”
• “With what profit percentages?”
• “What’s their current Proovly ELO?”

Every answer comes back as a cryptographic fact. Not a database row that FTMO can delete. Not a support-ticket screenshot. A Base mainnet read.

That means your Proovly track record is:

• Portable. You can show it to the next prop firm. You can show it to a copy-trading platform. You can show it to a fund that wants to pre-qualify allocators by verified edge.
• Non-revocable. We can’t take it away. Not by policy, not by accident, not by malice. The events are immutable once emitted.
• Composable. Any future Proovly product — or third-party product — can read the same registry and gate features, airdrops, or access by on-chain ELO.

What you cannot verify with this

The on-chain event proves you passed a challenge according to our rules engine. It does not prove:

• Which trades you took (those are broker-side, off-chain)
• Which strategy you used
• How much you personally funded the account
• Whether you used a bot or traded manually

If you want to prove any of that, you can — but you do it off-chain, by exporting your broker trade history or sharing your strategy. The on-chain event is the minimum, verifiable core: you passed a Proovly challenge of tier X at profit Y on date Z, and our committer signed off on it with a transaction.

That minimum core is exactly the primitive the prop firm industry lacks.

Trust in the committer wallet

The committer wallet is the Proovly backend key that writes passes to the registry. A malicious committer could, in principle, write fake passes for wallets that didn’t earn them — boosting their ELO artificially. What they cannot do:

• Steal funds (the registry holds no funds)
• Rewrite history (events are immutable)
• Delete passes (no deletion function exists)
• Change other people’s ELO downward (only upward ELO updates from actual passes)

The committer wallet’s attack surface is bounded to “inflate the ELO of wallets that shouldn’t have it.” Mitigations:

• The committer key is rotated quarterly
• The registry is public; anyone can compare emitted events against the public Proovly dashboard and flag inconsistencies
• In Phase 3, the committer role migrates to a multisig or a verifier network

What happens if you fail

Failing a challenge emits a corresponding ChallengeFailed event. This reduces your ELO by a formula amount, same as the game engine calculates off-chain. Failures are also public.

The reason failures are on-chain too: a reputation system that only records wins is a reputation system without context. “10 passes” means a lot more if you also know it’s 10 passes out of 50 attempts, or out of 12. The on-chain record is the full picture, not a selective one.

Can I hide this?

No. Once emitted, events are public on Base forever. You can choose to use a different wallet for future challenges — but your first wallet’s history stays visible against that address.

Can I use my ELO outside Proovly?

Yes. Anyone is welcome to query EloRegistry.sol and gate access by the values it returns. Wanted to build a “top 100 Proovly traders” leaderboard? Fork our view and ship it. Wanted to offer a copy-trade platform that only accepts traders above ELO 1500? Go for it. Wanted to airdrop to every wallet that’s passed a Gold tier challenge? The registry makes that a one-query operation.

This is the point. The reputation is yours, not ours. Our job is to honestly write it; your job is to do whatever you want with it.