About the AloKadoE network
AloKadoE is an independent layer-one blockchain with its own coin, written from scratch. It is not a fork and it is not a token on somebody else's chain: it has its own consensus, its own virtual machines, its own fee market and its own economics. This page explains what it does differently, and why.
The coin
The network's native coin is AloKadoE, written AKE. It has 18 decimal places, the same precision the EVM uses, so amounts carry over to existing tooling without conversion. AKE pays transaction fees, secures the network through staking, and pays the state rent that contracts owe.
Finality in seconds, not hours
Bitcoin's confirmations are probabilistic: after an hour a block is very unlikely to be reversed, but never impossible. Ethereum settles in about thirteen minutes. AloKadoE runs a proof-of-stake finality gadget over block production, so once validators have voted a block final it can never be reorganised away, whatever work a competing branch carries. The explorer marks the finalised height on every block and transaction, because "probably settled" and "settled" are different things and a person moving money deserves to be told which one they have.
A fair launch
The permissionless network allocates nothing at genesis. There is no premine, no founder allocation and no presale: every coin in existence enters circulation by being mined, and anyone who runs the software competes on the same terms from the first block. Rewards halve on a fixed schedule, so the supply curve is knowable in advance rather than a matter of trust.
Two virtual machines
Contracts can be written in Solidity and run on an EVM, which means the existing ecosystem of languages, tools and audited contract patterns applies here unchanged — you can compile and deploy one from this website. The chain also runs WebAssembly, with gas metering, for contracts that need to be faster than bytecode interpretation allows. Most chains make you choose; this one does not.
Every account is a smart account
On most chains an account is a key, and if you lose the key you lose everything. Here, account abstraction is part of the transaction format rather than a contract standard bolted on top: an account's own code decides what makes a transaction from it valid. That allows social recovery, spending limits, session keys, batched transactions and paying fees in a token rather than the native coin — without the extra infrastructure and extra cost that retrofitting the same idea onto Ethereum requires.
Transactions that run at the same time
Bitcoin and Ethereum both execute transactions one after another, on one core, however many the machine has. AloKadoE requires every transaction to declare the state it will touch, then runs provably non-interfering transactions side by side on separate cores. The declaration is binding: a transaction that touches something it did not declare fails. That strictness is what makes the schedule trustworthy — Ethereum's optional access lists cannot be used for scheduling precisely because they are optional.
Storage that keeps being paid for
Every chain that charges once for storage held forever accumulates data no one will ever pay to keep. It is Ethereum's most-discussed unsolved problem. Here an account pays for the room it occupies for as long as it occupies it. When a contract stops paying it stops working — but nothing is confiscated, the arrears can be paid by anyone, and it comes straight back. Holding coins costs nothing: rent is charged on storage and code, never on a balance.
Predictable fees
Fees follow EIP-1559 from the first block: a base fee that the protocol sets and burns, plus a tip you choose. You name a ceiling, and anything above what the block actually charged is left alone rather than spent. This was in the format from the start because it cannot be added later without breaking every transaction already signed.
Your keys, and standard ones
Wallets use BIP-39 recovery phrases derived at the standard path, so a phrase created here restores the same addresses in MetaMask, on a Ledger or in any other standard wallet. Your money is not locked to our software. The wallet on this site runs entirely in your browser: no key, no phrase and no password is ever sent to the server.
This explorer
Everything shown here is read from a node over its public interface — the same one any wallet uses — so the explorer can never show you something the network would deny. It holds no coins, has no accounts and can change nothing.
How it compares
| Feature | Bitcoin | Ethereum | AloKadoE |
|---|---|---|---|
| Finality | Probabilistic, ~60 min | ~13 min | Seconds, and absolute |
| Smart contracts | Very limited | EVM | EVM and WebAssembly |
| Execution | Single-threaded | Single-threaded | Parallel, on all cores |
| Account abstraction | None | Added on, at extra cost | Built in from genesis |
| Storage cost | Paid once | Paid once, grows forever | Rented, so it is sustainable |
| Launch | Fair | Presale | Fair, no premine |
What is still being built
This is a young network and it is better to say so. Staking penalties are detected and queued but not yet applied to balances, staking reward distribution is not finished, and the network has not had an external security audit. Treat it as a testnet: run it, deploy on it, break it and tell us — but do not put money on it that you cannot afford to lose.
Getting started
Generate a recovery phrase in your browser and write it down. It takes a minute and nothing leaves your device.
Look aroundEvery block, transaction and account on the network is here, and every page is a link somebody else can open.
Build somethingWrite a contract in Solidity and deploy it from the browser, or create a token from a form without writing any code.