What can I do with it?
Draft one of a substrate. The question we are asking is whether it works.
Evolver gives mutually distrusting parties one agreed order of events, plus identities, groups, credit and data availability. Everything below is built from those few pieces.
Today, from your MCP client
After the one-command install, your agent has tools for all of these. Ask it in plain language and approve each signature.
- Chat, in channels you own
- Claim a channel, decide who may write to it, and post and read ordered messages. Subscribe and your own node collects each message for you, in order.
- Groups you own
- Create groups of identities, and add and remove members. Hand ownership over through an explicit consent step.
- Charge for using a group or channel
- Set a toll that every authorised writer pays the owner, per message.
- Transfer credit
- Send credit to another identity, or to many in one transaction.
- Encrypted messages and files
- Encrypt for the members of a group, upload encrypted attachments, and decrypt what was sent to you. The chain orders the ciphertext; only the group can read it.
- Discover and announce services
- The Meerkat registry indexes service announcements on the chain. Your agent can list what others offer and announce its own.
What you could build on it
The chain orders events but does not run your logic. You decide what an event means, so each of these is your own code folding an ordered stream, rather than a contract you deploy. These are possibilities, not finished products.
- Your own state machine, with your own rules
- Define the events and the transition rules, then derive state by replaying the ordered stream. Every participant computes the same answer.
- Distributed applications
- Multi-party apps whose shared history is the ordered stream, with data availability handled for you or self-hosted.
- A bridge for Ethereum tokens
- Lock tokens on Ethereum and represent them here, so other participants can use them, for a fee you set.
- Login and identity
- Use chain identities as the backbone for OAuth or OpenID Connect, or build your own identity solution on keys the chain already verifies.
- Verifiable credentials
- Issue W3C verifiable credentials anchored to on-chain identities.
- Paid services, such as your own LLM
- Run a local model, announce it, and charge other users per use with a toll.
Watch it run
Two public views of the DevNet, open in any browser:
- Explorer
- Browse blocks, transactions, identities and groups, and search for any of them. Look up the identities your install claimed, or the transactions your agent just submitted.
- Monitor
- A live map of the DevNet's nodes and how they connect: the consensus committee, and every other node coloured by how many hops it is from the committee.
Why it is quick to try ideas
Every capability above is a tool in the Model Context Protocol server, so an agent can use the whole substrate from a conversation. Prototyping a new application is mostly describing what you want and letting the agent assemble existing tools. You can even distribute your applications through the chain itself: publish the bundle as content, announce it, and others can find and run it.
Install it and try one of these.