A rulebook the network runs by
The XE State Chain holds the network’s settings as a chain of its own, changed only by blocks the XE Keyset signs together. Any node can read the rules it runs by.
How XE is governedThe network got a rulebook it runs by, witnesses for when work starts and stops, a way for any account to message another, and leases priced by what a machine really gives.
The XE State Chain holds the network’s settings as a chain of its own, changed only by blocks the XE Keyset signs together. Any node can read the rules it runs by.
How XE is governedXE Timekeepers sign when a lease starts and when it ends. A quorum of them sets the time, so neither side of a lease can say it ran longer or shorter than it did.
About leasesA directory maps every account to the node it lives on, and messages travel straight between them over XE Mesh, signed end to end.
About messagingWith the State Chain in place, the network’s own settings, like who the timekeepers are and how many must agree, stop being config files and become blocks anyone can check.
/xe/msg/1.0.0, and the node binary to xeThe next doors on the roadmap. The week each one ships, it moves from here into the log.
See the whole roadmapPackage a workload once. Anyone boots it in one click, and you earn on every boot.
Operators publish the share they give backers, paid from real, settled work.
Your own network: the same app on your own machines, scheduled by your key alone.
A named operator and a signed contract on the listing, and you can require it.
Every week
One short email a week when something ships: the headline, the highlights, and a link to the rest. Nothing else, and you can leave any time.