Monthly flow
USD purchased · ALEPH convertedDistribution runs are batched: credits accumulate in the processor and are converted in discrete on-chain runs, so purchase months and conversion months don't line up one-to-one.
On-chain processing runs
| Date | Paid in | Amount in | ALEPH out | → Network | Type | Proof |
|---|
Latest credit purchases
| Date | Chain | Paid in | USD paid | Proof |
|---|
Contract. AlephPaymentProcessor on Ethereum mainnet,
0x6b55F32Ea969910838defd03746Ced5E2AE8cB8B
(Etherscan).
On-chain figures are decoded from TokenPaymentsProcessed events — one event per processing
run, carrying the swap, burn and distribution amounts. Nothing here is self-reported.
Credits. Purchase data comes from the public Credit API
(credit.aleph.im/api/v0/payment).
Credits are denominated at 1,000,000 credits = $1; USD-paid figures count what buyers
actually paid — bonus credits are excluded, failed payments are excluded.
Burn. The burn percentage is a governance-controlled parameter, currently 0%. When activated, burned amounts will appear here from the same events — the lever above flips, nothing else changes.
Mechanism. Full tokenomics: tokenomics.aleph.cloud. This page refreshes hourly from a static cache; it holds no database and makes no projections. These are small numbers presented honestly — the point is the mechanism, and that you can check it.