Documentation
What launches
ALMERU deploys from two templates. Both share a fixed-supply token, one canonical pool and a permanent liquidity lock; they differ in how value is routed back to participants.
Template A — treasury protocol
The treasury template is the default interpretation of a launch request. It produces a token, a market for that token, and a reserve that grows from the market's own activity. Four mechanisms sit on top of that reserve:
- Staking. Holders deposit the token and receive a rebasing or non-rebasing receipt. Rewards are paid out of inventory the protocol already owns.
- Bonds. The protocol sells token at a discount in exchange for assets it wants to hold. Every bond payout is escrowed before its sale window opens.
- Buybacks. The treasury spends part of its free balance in the canonical pool, subject to a price floor and a time-weighted reference price.
- Reserves. The residual. Reserve balances back the token and are accounted separately from operating funds.
All four are covered in detail in Treasury mechanics. The important structural point is that none of them can create supply. The reward budget is finite and set at launch; when it is exhausted, emissions stop rather than dilute.
The reward route
Trading in the canonical pool carries a 1% fee. Seventy percent of that fee goes to the launch creator and thirty percent to the protocol. The protocol's share is then split again along a route chosen at deploy time. A common configuration sends 40% to holder rewards and 60% to reserves:
pool trade
└─ 1.00% fee
├─ 0.70% creator
└─ 0.30% protocol
├─ 40% holder rewards
└─ 60% reserves
The route is configurable per launch, but it is fixed once the deployment transaction lands. There is no governance action, and no agent action, that rewrites it afterwards. The mechanics of the pool itself — fee accrual, the lock, price protection — are in Market integration.
Template B — the Miner
The Miner template replaces staking and bonds with a game. A Miner is a 25-tile board played in discrete rounds. Participants claim tiles, tiles produce over the life of a round, and each round settles into a payout drawn from the same fee routing described above. Rounds are sequential and bounded: a round opens, accepts entries, produces, and closes, and the settlement of one round cannot borrow against the next.
Underneath, a Miner is the same protocol as a treasury launch. Same fixed supply, same single pool, same permanent lock, same 70/30 fee split, same launch fee. What changes is the surface: instead of depositing into a staking contract, participants take positions on tiles, and instead of an epoch-based reward index the protocol runs a round settlement. Round structure, tile economics and settlement order are documented in Miner protocol, and live boards are listed under Miners.
What is identical across both
| Property | Behaviour |
|---|---|
| Supply | 1,000,000,000 units, minted once, no mint path afterwards |
| Pool | Exactly one canonical pool per launch |
| Liquidity | Locked at launch, permanently, never withdrawable |
| Lock yield | Fees on locked liquidity are compounded in place |
| Bootstrap | 0.0001 – 0.07 ETH of seed value |
| Launch fee | 0.0005 ETH, flat, regardless of size |
| Custody | None. ALMERU holds no participant funds at any point |
The bootstrap range
Seed value is bounded at both ends. The floor of 0.0001 ETH exists because a pool with effectively no depth produces meaningless prices and makes the price-protection logic degenerate. The ceiling of 0.07 ETH exists because the agent signs launches autonomously, and an autonomous signer should not be able to commit an unbounded amount of value in a single call. Requests outside the range are rejected at parse time rather than clamped silently — a launch that does not match its instruction is treated as a failure, not as a best-effort approximation.
The launch fee
The 0.0005 ETH launch fee is flat. It does not scale with bootstrap size, with supply, or with the template chosen, and it is charged once, at deployment. It is not a share of the economy: paying it does not entitle the payer to fees, tokens or any position in the launched protocol.
Neither template makes a return likely. A fixed-supply token with a locked pool and a fee-fed reserve is a set of mechanics, not a yield product; a Miner is a game with round settlement, and games have losers. Read the legal notice and verify the deployed addresses in Contracts before you interact with anything.
Choosing between them
The parser picks a template from the wording of the request, and the wording it keys on is listed in Command reference. In broad terms: a request that talks about staking, bonding, reserves or backing resolves to the treasury template; a request that talks about tiles, rounds, mining or a board resolves to a Miner. If a request is ambiguous enough that both readings are plausible, the agent replies asking for a disambiguation instead of guessing. Nothing is deployed on a coin flip.