How Ore works
Ore is a standard token plus a distribution engine.
The ORE token is fixed-supply, deployed through pons: token and locked trading pool created in a single transaction. No transfer tax, no wallet caps, no special transfer logic — it trades like any ordinary token, and sells can never be blocked.
The distribution engine has two parts working together: the Ore Distributor contract (holds the PAXG reserve, verifies claims, records the hold toggle) and the keeper (snapshots balances each cycle, delivers gold, and commits a Merkle record of accrued entitlements on-chain).
The loop
- 1. Trading generates fees
Trading in the pons pool generates fees; the creator share flows to the Ore treasury.
- 2. The treasury funds the reserve
The treasury converts revenue to PAXG. Deposits into the reserve are labeled public events.
- 3. The keeper snapshots each cycle
Every fifteen minutes the keeper snapshots holder balances (pool and protocol addresses excluded) and splits the cycle's gold pro-rata.
- 4. Delivery
Holders in default mode receive PAXG directly in their wallets. Holders in hold mode accrue instead — their entitlement is committed to an on-chain Merkle root and grows a bonus of +5% per cycle, capped at +30%, payable when they claim on the dashboard.
What the contracts guarantee
- Gold leaves the distributor only through valid holder claims.
- Per-address payouts are strictly monotonic — nothing paid twice.
- Base entitlements always pay in full or the claim reverts.
- Pool liquidity is locked by pons.
What the team operates
Stated plainly:
- Reserve funding is an operational commitment, visible on-chain at every deposit.
- The snapshot keeper computes balances off-chain — the protocol's main trust assumption, made verifiable by publishing the keeper's source and every cycle's snapshot data so anyone can recompute any distribution, while the contract independently bounds what can ever be paid.
See Risks for the full disclosure.