Verifiable, not just stated.
ArcadeUnion is intended to be community-run, and that only means anything if the money can be checked by the community rather than taken on trust. This page sets out exactly what will be published, what can be independently verified, and what cannot.
Two kinds of number.
Most projects publish one list of figures and let readers assume they are all equally solid. They are not, and pretending otherwise is how trust gets lost. ArcadeUnion separates them.
Verifiable on-chain
Every movement of $ARCU and USDC happens on a public blockchain. Once the wallet addresses below are published, anyone can open a block explorer and check every balance and every transaction for themselves — without asking us, and without trusting anything on this website.
This covers node sale income, the treasury, the liquidity pool, tokens burned, and the monthly operating draw.
Reported by ArcadeUnion
Game purchases are proposed to be paid in USDC or $ARCU, with no card processing at all, so the money itself would arrive on-chain and be as checkable as everything else here. What a block explorer still cannot show you is what it was then SPENT on: a payment leaving an operating wallet is visible, but whether it bought server capacity or a holiday is not.
So this category does not disappear, it narrows: headcount, contractor invoices, hosting bills and anything else denominated in the real world are published on a stated schedule with their source named — but they are a statement by us, not a proof. They will always be labelled as such, and never presented in a way that implies they were verified on-chain.
What you still have to trust us on.
The two categories above cover money. There is a third thing that is neither independently verifiable nor merely reported, and it is the most important one to be honest about: who decides what each node operator is owed.
The reward engine is run by us
Node rewards are calculated off-chain and settled on-chain against a published cryptographic summary. Whoever runs that calculation decides what every operator receives.
The contract cannot tell a correct calculation from a fabricated one. It checks that a claim matches the published summary; it has no way to know whether the summary itself was produced honestly.
At the start, that calculation is run by ArcadeUnion. That is a real point of centralisation and we would rather state it than let someone discover it.
What limits it
Three things, none of which amount to trustlessness:
Reconciliation and reproducibility mean a dishonest calculation should be detectable by anyone who cares to check. Detectable is not the same as impossible, and we are not going to claim otherwise.
Checked by your browser, not typed in by us.
Every figure below was fetched from a public Avalanche RPC by the browser you are reading this in. No ArcadeUnion server sits in the path, and nothing here is cached by us — reload and it is read again. Each one links to a block explorer so you can confirm it independently.
| Figure | Now | Source |
|---|---|---|
| Reading the chain… | ||
—
What will always be on show.
The intention is a permanent, continuously updated view of every income stream and every outflow — not a quarterly report that has to be asked for.
| Figure | Where it comes from | Status |
|---|---|---|
| USDC raised from node licence sales | Sale wallet, on-chain | Independently verifiable |
| Licences sold, and price band reached | Licence contract, on-chain | Independently verifiable |
| Treasury balance | Treasury wallet, on-chain | Independently verifiable |
| Liquidity pool depth | DEX pair, on-chain | Independently verifiable |
| $ARCU burned to date | Burn address, on-chain | Independently verifiable |
| Operating draw taken to date | Operating wallet, on-chain | Independently verifiable |
| Node rewards distributed | Distribution contract, on-chain | Independently verifiable |
| Game revenue | Paid in USDC or $ARCU, on-chain | Independently verifiable |
| What operating spend was used for | Invoices and contracts, off-chain | Reported by ArcadeUnion |
Live figures are intended to be read from the blockchain by your own browser when you load the page, rather than served from our database. That matters: it means the numbers you see are not numbers we typed in.
Concentration, shown rather than hidden.
Founder Node licences are transferable tokens on a public chain, so who holds how many is already a matter of record. These figures publish it plainly rather than leaving people to dig for it — and they will be published whether or not they are flattering.
| Figure | Status |
|---|---|
| Licences sold, and price band reached | Independently verifiable |
| Wallets holding at least one licence | Independently verifiable |
| Largest single holding | Independently verifiable |
| Share held by the ten largest holders | Independently verifiable |
| Median holding | Independently verifiable |
| Reserved licences still unissued | Independently verifiable |
Why there is no per-wallet limit
A cap of, say, ten licences per wallet is a reasonable-sounding request, and it does not survive contact with the arithmetic. Wallets are free to create, so routing around such a cap would cost a large buyer roughly fifty dollars in fees on a multi-million-dollar purchase. That is a formality, not a deterrent.
Worse, it would make concentration invisible. The same buyer would hold the same number of licences spread across many addresses, and the table beside this would look healthy while nothing had actually changed. A figure that looks good because it was forced to fragment is worse than one that can be read honestly.
The price ladder is the real limit, and it cannot be split. Price is set by the total number of licences sold, not by any one wallet — so buying five thousand costs roughly nineteen times as much per licence as the first hundred, however many addresses they are bought from.
Every wallet, named in advance.
Publishing addresses before there is anything in them is the point. It means the accounts cannot be quietly swapped later, and anyone can watch them from the first transaction onwards. The one exception is the treasury: its allocation is minted in the same transaction that creates the token, so it could not be published beforehand and was published on the day of deployment instead.
| Wallet | What it holds | Address |
|---|---|---|
| $ARCU token contract | The token itself — source verified | 0x1048D02787fB3304B9694C3a9f172549E58e77Bd |
| Node sale receipts | USDC paid for licences | Not yet created |
| Treasury | Genesis allocation and liquidity funding | 0xE447d0C086CD7cAc33cEbBAC913b1732053260AE |
| Liquidity pool | The $ARCU / USDC trading pair | Not yet created |
| Burn address | $ARCU permanently removed from supply | Not yet created |
| Operating draw | Monthly working costs | Not yet created |
| Reward distribution | Node reward claims | Not yet created |
Rules the project holds itself to.
These are proposed constraints on what the project can do with its own money, published so that breaking one would be visible.
The cap is enforced by the contract
The 20 billion maximum is enforced in code. It is set once in the constructor of the deployed contract and there is no function anywhere that can raise it — which you can check in the verified source rather than take on trust.
Capped, and tied to actual sales
The monthly operating draw is proposed to be the lower of $5,000 or 20% of that month's node sale income — so it scales down when sales are slow and can never take the whole of a thin month.
A disclosed allocation of ten nodes
Ten licences from the reserved pool are allocated to the founder, roughly a tenth of one per cent of lifetime node rewards. Operating costs for those nodes are paid by the founder like anyone else.
No quiet selling
The treasury allocation exists to provide liquidity. It is not intended to be sold into the pool it funds, and any change to that would be published before it happened, not after.
Visible, not claimed
$ARCU taken as payment for node licences is burned. Burns go to a published address, so the amount removed from supply is checkable rather than asserted.
A published route back
An operator whose rewards are wrongly withheld can appeal, within a stated window and to a stated deadline, and every outcome is published — refusals included. The process is set out on the Founder Node page.
Documented before they take effect
Material changes to emission, node scoring, treasury policy or the operating draw would be written up and published before they start, not explained afterwards.
What is deliberately not published
Individual node operators are not named, and their wallets are not listed or linked to people. Aggregate figures show what the network earns; they do not expose who earns it.
Contributors paid from the operating budget are not named individually either. The total is published; personal details are not.
How often
On-chain figures are continuous — they update as the chain does, and can be checked at any moment without waiting for us.
Reported figures, meaning game revenue and any off-chain cost, are intended to be published monthly, with the period and the source stated each time.
The numbers behind all this.
Supply, emission, distribution and the licence structure are set out in full on the token and Founder Node pages.