points counting starts at Arc mainnet

There is no points database.

Your score is a function of chain events — RouteExecuted from the routers and Deposito / Saque from the vault. The script that computes it is public, it takes no key, it writes no ledger, and running it twice on the same block gives the same number. You do not have to trust a scoreboard of ours, because there isn't one.

Counting starts when Arc mainnet opens. Testnet activity never counts: that volume is made by a bot of ours, and counting our own money as someone's merit would be a lie. Codes can be handed out before, and redeemed from the open. There is no conversion number yet — no supply, no ratio, no date. Nothing on this page is an allocation, a promise of one, or an offer.

the formula

Published before counting begins, and not changed after. Changing the rule once people have spent fees is the classic betrayal of this mechanism, and it is the reason almost nobody believes a points program.

source	points	read from
Spot volume	1 per USDC of notional	RouteExecuted — the USDC leg of the trade, net of the router fee
Vault liquidity	1 per USDC-day	Deposito / Saque — principal, integrated over time
Referral	10% of the base points of who you referred	ReferralPaid — one level, first referrer wins
Code	2× multiplier on the total	Resgatado — the on-chain redemption
Perp	nothing	the engine charges no fee, so perp volume would be free to fabricate

Order of operations: (volume + liquidity + referral) × multiplier, every division truncated down. A stock-for-stock route has no USDC leg: it counts as a trade and adds no points, instead of being priced with today's number for yesterday's trade. Referral is additive — it takes nothing from the person who was referred.

why farming does not pay

Fabricated volume costs 0.40% of every USDC it scores — the router fee plus the pool fee — and that fee is protocol revenue. So while a point is worth less than the fee that produced it, farming loses money and pays the house on the way out. That is the whole anti-sybil design: no captcha, no KYC, no blocklist.

The honest limit of it: a redeemed code pays zero router fee, so inside the stamped set the economic defence is weaker — only the pool fee is left, and the 2× multiplier buys two points with it. Per point, that is 0.15% against 0.40%: farming is 2.7× cheaper for someone holding a code. That is why the stamped set is capped at 1,000 addresses and why the invite tree has a depth limit.

your score

address

Connect a wallet or paste an address. The lookup reads the published snapshot below.

since the snapshot, read live from the chain

—

the snapshot

show our wallets

#	address	points	volume	liquidity	referral	×
reading the snapshot…

codes

cap

1,000 addresses

codes per stamped address

3

multiplier

2×

router fee, stamped

zero, permanent

referral cut, stamped

50% of the fee

registry

not deployed yet

A code does not gate anything. The venue is open: without a code you trade the same way, pay the fee and score 1×. Redemption is one on-chain transaction and takes two steps a block apart — you commit to the code with your address first, then reveal — so that nobody can copy the secret out of the mempool and take your slot. The published list is hashes, never the codes, so the list cannot be farmed before it is handed out.

conversion

Points convert into a token. The ratio does not exist yet, and it will not be invented on this page: it depends on decisions nobody has made — whether there is a supply, what fraction goes to points, whether there is a lock. What is fixed today is the score formula and the fact that the ratio is published before any distribution. We do not promise a number that does not exist.