How it works
Five short chapters, four of them built around something you can play with. Each is about a thing you can check: the bytes in a token, the transactions on an account, and the records the hooks wrote.
The short version
A moeba is grown from 32 bytes. The genome is not a seed for a picture and not a list of looks: it is read through a fixed developmental process — how many segments, where limbs attach, how the head and tail form, how it moves — that builds one canonical body. The renderer draws that body afterwards and never decides it. Because looks follow from the genome step by step, a child resembles its parents for reasons you can trace.
On the ledger a moeba is a URIToken issued by one account, the Xahmoeba issuer. Its URI holds its identity — kind, generation, the ledger it was born in, when it matures; three sealed records hold its genome with its parents and who asked for it, the randomness used, and the hash of the rules. To make a new moeba, a keeper sends one payment naming two parents. From then on nobody signs anything: hooks on the account wait for a ledger a few seconds ahead, take its hash as the birth’s chance, combine the parents’ genomes, apply the mutation rules, mint the child and deliver it. The child’s genome is a pure function of the parents and that hash. This site recomputes it on every moeba page. The source is not published.
Five chapters, the practical part, the whitepaper and the protocol
- 01
The genome
32 bytes, 36 loci, two copies of each. What each part decides, and how a body is read from it.
Try it Turn the dials on a real moeba and watch the body change - 02
A birth
Two parents, one draw of randomness, one child. Recombination, mutation, and what could have been.
Try it Watch a child’s genome being read from its parents, byte by byte - 03
The randomness
A future ledger hash that nobody can pick, bound to this request, captured while it is still readable.
Try it A model ledger to ask for a birth in, and a hash to try to predict - 04
The hooks
Five programs on one account. What each does, in what order, and what it refuses.
Try it Drive a birth through its nine stages yourself; burn a parent midway - 05
Keeping moebas
Owning, selling, giving, opening to others, and burning. What each does to a breeding permission.
Try it Read what each tool on a moeba page does before you sign anything - 06
Getting started
An account, a first moeba, what a birth costs and how to ask for one. Every step is one transaction any Xahau wallet can sign.
The practical part, after the reading - 07
The whitepaper
The whole design in one document: what a moeba carries, why nothing about its appearance is on the ledger, the money, the rules, what the issuer can and cannot do, and what the rehearsal means.
One long read, for when you want all of it - 08
The protocol
For builders: the bytes of the identity URI, the six records and the genome locus by locus, the rules of expression, the request codes, the API — and a decoder that takes a real moeba apart.
Read a moeba without this site