xenoth
Browser-native AI entities for the open web. One identity, one memory, one reputation: on every site the entity lives on.
ENTITY PASSPORT · ERC-8004 SHAPED
XENOTH #----
ENTITY CONTRACT
loading...
One entity. Three sites. Same memory.
These are three fake products. The agent in each corner is one real Xenoth entity, the same web component three times. Open it on the dex, tell it your name, then ask the one on the forum what it remembers. It syncs live, survives reloads, and its passport grows with every exchange.
VOLT DEX
XEN / WETH · $0.0042 +12.4%
AGORA FORUM
governance: fee switch vote opens friday
anyone else's entity remembered them from the dex?
weekly alpha thread, post your finds
codex docs feedback megathread
CODEX DOCS
docs / getting-started / embed
Drop the script tag before </body> and place the element anywhere. The entity inherits its identity from the network, not from your page.
Attributes: site labels the location in its memory, accent tints the shell.
Try: open the dex agent, say "call me neo", ask it about gas. Then open the docs agent and ask "what do you remember?". Same entity, no tricks: the brain is a prototype intent engine (it says so itself), the chain answers and the shared memory are real.
What an entity carries
Each card says what works today in the prototype and what arrives with mainnet. No card lies.
ON-CHAIN IDENTITY
TODAY · deterministic passport shaped after the ERC-8004 identity registry entry.
MAINNET · registered ERC-721 handle in the identity registry, resolvable by any site.
PERSISTENT MEMORY
TODAY · real: name, wallet, history shared across every embed and reload, synced live.
MAINNET · encrypted memory vault the entity carries between domains and devices.
REPUTATION
TODAY · grows with interactions and breadth of sites, shown in the passport.
MAINNET · posted to the ERC-8004 reputation registry, readable by anyone.
WALLET
TODAY · read-only: the entity checks balances and gas through public RPC.
MAINNET · its own signer with allowances you grant and revoke.
The network under it
An entity does not belong to a website. It belongs to the Xenoth network, and websites borrow it. That is why the three corners above hold one character: identity, memory and reputation live with the entity, not with the page.
The identity layer targets ERC-8004, the Trustless Agents standard (live on mainnet since January 2026): an ERC-721 identity handle, a reputation registry for bounded feedback scores, and a validation registry for proofs of work done. The passports you see here are already shaped to fit it.
Until the registry integration ships, everything on this page runs client-side and says so: the honest prototype is the pitch, not a paper promise.
$XENOTH
The token is a stake in the network's story, not a key to it. Embedding stays free, talking stays free, the registry will read and write for everyone.
Struck on clanker, on Base. The address appears in every entity's passport the moment it exists, including the ones in the corners above.