MiniUni
A constant-product pool in 712 bytesETH against one token, on Uniswap V2's curve
Every trade pays a 0.3% fee, in ETH, to whoever seeded the pool.
- ETH in the pool
- –
- Tokens in the pool
- –
Deposit ETH, deploy contracts, call them, withdraw. The contracts live in the chain's own state and run in an interpreter, so every transaction on a MiniChain is an Ethereum transaction. There is no token, no sequencer and no bridge.
The chain on the right is real and running on a local Ethereum fork. MiniChain is not yet deployed to mainnet and has not been externally audited.
The first MiniChain. Its token is a gemstone drawn on-chain from the chain's own state.
Contracts on a MiniChain are guests. They are not Ethereum contracts: their code and storage sit in the MiniChain's state, and an interpreter built into the chain runs them when you call it.
depositdeploycreatetransactwithdrawexecuteexecuteBatchwithdrawForreadETH is the only asset. Every internal wei is backed one to one by ETH the contract holds.
Guests hold and move internal ETH too. Fees are a transfer inside the same ledger, so the two bars always match.
Code and storage kept in the chain's state, at their own addresses.
Execution is bounded by a step budget you set per call, separate from gas.
Each operation commits one block: it is hashed into head and height goes up by one.
head = hash(previous head, height, operation)
These are the real commands, using Foundry's cast against the chain shown above. The guest is the 20-byte counter from the repository's examples.
Send ETH to the chain. The contract keeps it and credits the same amount to your account inside. Deposits pay no chain fee.
$ cast send $MINICHAIN "deposit(address)" $ME --value 1ether
Store a program in the chain at its own address. Kind 1 is MiniVM, kind 2 is EVM runtime bytecode; create runs a Solidity constructor instead.
$ cast send $MINICHAIN "deploy(uint8,bytes,bytes32)" 1 \ 0x130100001602000003020201170002001a020000 $(cast keccak counter)
Call the guest with a value, calldata and a step budget. A failure rolls the whole call back. read runs the same guest without a transaction.
$ cast send $MINICHAIN "transact(address,uint256,bytes,uint256)" \ $COUNTER 0 $(cast abi-encode "f(uint256)" 7) 100000 $ cast call $MINICHAIN "read(address,bytes,uint256)(bytes)" \ $COUNTER $(cast abi-encode "f(uint256)" 0) 100000
Turn internal ETH back into ETH on Ethereum, to any recipient, in the same transaction. No waiting period and no chain fee.
$ cast send $MINICHAIN "withdraw(uint256,address)" 0.25ether $ME
Two programs written for MiniVM that ship with the code. Anyone can deploy a copy to any chain. The figures here are examples.
ETH against one token, on Uniswap V2's curve
Every trade pays a 0.3% fee, in ETH, to whoever seeded the pool.
One storage slot per item: its owner
Its creator sets a price and a supply cap once. Mints and transfers are logged as ERC-721 transfers, which is how an explorer knows who holds what.
A MiniChain transaction is executed in full by Ethereum and pays Ethereum's base fee, which is burned. The chain's own fee is a tenth of that again, paid in ETH to two owners.
One user transaction is one Ethereum transaction. Ethereum burns the base fee on all of its gas.
Many user transactions are compressed into one posting, so each pays Ethereum almost nothing.
An L2 exists to scale. A MiniChain does the opposite of batching, and running a guest in an interpreter costs more gas than running the same code natively. What it gives you instead is your own ledger, your own fee stream and outright ownership, with nothing between you and Ethereum.
Enter a transaction's gas and Ethereum's base fee.
The exact fee is (gas measured in the call + 37,700) × base fee ÷ 10, which came to between 88% and 100% of a tenth in every measured case, so the two fees shown are upper bounds. Priority tips are not counted. The sender pays the fee in internal ETH; deposits, withdrawals and fee claims pay none. On MiniChain #1 both halves go to the same owner.
An event, a season, a sale: some chains have a natural last day. A MiniChain can be launched with an end date, fixed and public from its first block. Chains created without one never end.
The end date is chosen when the chain is minted and must be at least 30 days away. Nobody can move it afterwards, the owner included.
From the end date the chain accepts nothing: no deposits, no calls, no withdrawals. Anyone can then sweep it, which sends all remaining ETH to the token's owner, other users' balances included.
The token is not destroyed and the chain's history stays readable. Its gemstone turns grey and still, at the size and cut it had when the chain stopped.
Every MiniChain is an ERC-721 token in one registry. Whoever holds the token owns the chain. Its picture is an SVG built entirely on-chain from the chain's live state, with no server behind it.
One more row of facets at 10, 100, 1,000 and 10,000 operations. Every operation also moves the light.
A new chain starts with one row.
The stone is 35% of full size when empty, half at 5 ETH and full at 1,000 ETH, on a logarithmic curve.
Size follows the ETH the chain holds.
One glint to begin with, and one more each time the fees earned double from 0.01 ETH, up to ten.
Glints follow the fees a chain has earned.
Fourteen stones and eleven cuts, chosen by the chain's id and address. Diamond and onyx are rarer. Swatches here are approximate.
The registry itself refuses a 513th, whatever rule mints them. The default minter allows one more MiniChain for every 0.01 ETH of fees MiniChain #1 has collected, free apart from gas and open to anyone once the owner of MiniChain #1 opens minting. The owner of MiniChain #1 can also give tokens away.
0.01 ETH of fees is 0.1 ETH of gas spent on MiniChain #1.
Chains appear here when the node is reachable.