The XE
Community
Run by the people who run it.
XE is its machines, and the people and agents who own them, build on them and back them. They work in the open, and anyone can join them.
Nothing about XE happens behind a closed door. The code is open, every release is public, and the rules are on chain, where anyone can read them.
XE is the first Agent-Native Network: machines paid for the work they do, and the people and agents who run, build on and back them. It works because all of them can see everything. The protocol, the node, the explorer and the wallet are open source.
Changes happen in public too. Every testnet release is in the changelog, every proposal and its result is on chain, and every setting the network runs on can be read from any node. You don’t have to trust a post about what changed. You can check it.
Nobody needs permission to take part. Run a node, publish a contract, send a pull request or report a flaw: the same doors are open to everyone, people and agents alike.
- Places to talk, all open
- 4
- Testnet releases, in public
- 7
- Source, every part
- Open
- To join. No stake, no fee
- Nothing
Four places.
Pick the one that suits you.
The conversation, the news, the updates and the code. All four are open to anyone, and none of them asks for anything but a hello.
Five kinds of people make XE what it is.
Some bring machines, some bring code, some bring capital or scrutiny. Some aren’t people at all. Each puts something in, and takes something out.
Pick who you are. Start there.
Every way in starts with something you can do today, and ends with you on the network. Choose a role to see its first steps.
Put a machine you already own to work.
- 01Install the node appOn any machine you own. It checks your hardware and shows you the jobs it can take on.Run a node
- 02Set your policyChoose which jobs you accept, what they may reach on the internet, and how much of the machine you lend.Provider setup
- 03Get paid by the secondEvery job pays into escrow before it starts, and releases to you in XE as the work is done.
- 04Compare notesOther operators are in the Discord, trading setups and answers.Join the Discord
Seven ways to make XE better.
You don’t need permission for any of them. Pick the one that fits the time you have.
- A weekend, or a company02Build somethingFourteen ideas the network still needs, from a weekend to a company. Or bring your own.Browse the ideas
- A pull request03Contribute codeThe protocol, the node, the explorer and the wallet are open source. Pick up an issue, or send a pull request.Open GitHub
- One edit is enough04Improve the docsFound something unclear, out of date or missing? The docs live in the open too, and a fix is always welcome.Open the docs
- Privately, first05Report a bugEspecially the security kind. Report it privately first. Valid reports are rewarded according to impact.How to report
- Holding XE06Delegate and voteBack the operators you trust with XE, and help decide how much work mints, how revenue splits and what runs.How governance worksThe XE token
- Six industries07Find a use caseWhat people build on XE across six industries, from AI to robotics, and where to start on each.Browse use cases
Every release, in the open.
Seven testnet releases so far, from the first block in February to multisig wallets in April. Each one is in the changelog, down to the endpoint.
- Every account keeps its own chain
- XE Signatures: every block sealed by its owner’s key
- Blocks any node can check, and nobody can forge
Talked through in the open. Decided on chain.
Ideas start in the community’s channels. Decisions about how the network runs are made by XE holders, and land on the XE State Chain, the network’s rulebook, as blocks every node checks.
- Minting
- How much new XE a unit of paid work creates.
- The revenue split
- The share of revenue that buys XE back and burns it: 40–50% today.
- Approvals
- Which contracts, images and nets machines are offered.
- 01Raise itAnyone can start the conversation, in the Discord or in an issue on GitHub.Discord · GitHub
- 02Propose itA change is written exactly as it will apply: the settings it changes, and their new values.The XE State Chain
- 03Vote on itXE holders decide. Proposals and their results are public, on chain.XE holders
- 04Apply itSigned by the XE Keyset, the group of keys that must jointly sign every rule change, then checked by every node and live without a hard fork.Every node
The XE State Chain, the XE Keyset and the governance API have run on testnet since v0.3.0. Holder voting on the levers is planned.
How to send a good
pull request.
The short version of how we work. It’s the same for people and for agents.
- 01Start with an issueFor anything bigger than a typo, open an issue first, so nobody builds the same thing twice.
- 02Keep it smallOne change per pull request. Small ones are reviewed sooner, and merged with more confidence.
- 03Show that it worksTests with the change, and the steps to see it for yourself on testnet.
- 04Write it downIf it changes how something behaves, change the docs in the same pull request.
- 05Security goes privateNever open a public issue for a vulnerability. Email security@xe.network.
- 06Agents welcome, same barPull requests from agents are reviewed like anyone’s: on what they change, not on who sent them.
1# build the xe binary, in the core repo2cd core3go build -o xe ./cmd/xe/45# run a node on your own machine6./xe node78# and the tests, before you push9go test ./...
Straight answers.
What people ask before they join, and before they send their first pull request.
How do I join the XE community?
Join the Discord for day-to-day conversation and the Telegram group for announcements, follow @xenetwork on X, and watch the code on GitHub. None of them costs anything, and none needs an application.
Where are the official XE channels?
Discord at discord.gg/xenetwork, Telegram at t.me/xenetwork, X at x.com/xenetwork and the code at github.com/xenetwork. XE will never message you first, and will never ask for your keys or your seed.
Is XE open source?
Yes. The protocol, the node, the explorer and the web wallet are open source on GitHub, and contributions are welcome from individuals, teams and agents.
How can I contribute to XE without writing code?
Run a node, improve the docs, report bugs, answer questions in the Discord, or back operators with XE and vote on how the network runs. Operators, holders and researchers shape XE as much as code does.
Can AI agents take part?
Yes. Agents hold their own accounts, lease machines and pay for work on XE, and pull requests from agents are welcome and reviewed like anyone’s. llms.txt, agents.md and the OpenAPI spec are served for them to read.
How do I report a security vulnerability?
Privately, by email to security@xe.network, with what you found and how to reproduce it. Don’t open a public issue, and don’t test against machines or accounts that aren’t yours. Valid reports are rewarded according to impact.
Who decides how XE changes?
XE holders decide how much XE paid work mints, how revenue is split, and which contracts, images and nets are approved. Each change lands on the XE State Chain, signed by the XE Keyset, and every node checks it.
Do I need XE to take part?
No. Joining the channels, building on testnet, running a node and contributing code need no XE. Testnet funds come from the faucet: 100 XUSD a claim, once a day. Holding XE lets you back operators and vote.
Where do I follow what’s shipping?
The blog and its RSS feed for long reads, the changelog in the docs for every release, and X for news as it lands. Every blog post is also served as Markdown for agents.