A global permission-less, decentralised DePIN for ultra-flexible, ultra powerful dApps.
Evernode dApps can be written in almost any language, deployed at almost any scale, read and write to disk and web, fetch off-chain data, perform complex computations, and generally perform like a normal App, but in a decentralised way. It is a new vision for ultra-flexible, ultra-powerful dApps.
Anybody, anywhere can download the Evernode software, join the network, and offer dApp hosting services to anybody, anywhere via the Xahau Network.
To join Evernode, Hosts buy a Membership NFT from the Evernode Registry Hook. The NFTs identify the Host, confirms its network membership, and represent its free licence to run the Evernode software. Membership NFTs can be redeemed at any time for 50% of the unrebated registration fee.
An automated account (or Hook) on the Xahau Network maintains the canonical registry of Evernode hosts. Thus, the Xahau Network, rather than a single entity, controls all Evernode registrations.
Hosts mint Hosting NFTs that represent an exclusive lease of a hosting Slot in exchange for hourly hosting fees in Evers. Hosting NFTs trade on the Xahau Network. The purchase price represents the first hour of hosting. Hosts can redeem them at any time to control to whom they supply hosting services.
Evernode is a “network of networks”. Each dApp is a mini-blockchain (or “AppChain”) comprised of the Hosts on which it runs with a consensus engine to maintain a canonical state across all instances.
Evernode’s Three Basic Components
A consensus-as-an-operating-system environment in which your code runs to enable multiple instances to function as a bespoke chain.
A standardised and decentralised way to deploy multiple instances of your executable program code to a range of third party hosts.
A way of doing all this via a secure “layer 1” chain so the network is as secure and decentralised as possible.
Evernode dApps are normal Apps that run inside a UNL consensus engine, called HotPocket.
We call them dApps but really they are bespoke chains (or “AppChains”) that behave as you want. It’s UNL, the files it reads and writes, it’s inputs and outputs etc. are all subject to consensus within your dApp’s UNL. HotPocket provides all this as a sort of consensus-as-an-operating-system solution.
HotPocket clusters wouldn’t be decentralised if Devs had to spin up each Host. Evernode solves this problem with Sashimono.
The Sashimono Daemon allows a host to provide secure hosting services to multiple dApp instances. Each instance is in a jail that keeps it separate from every other instance and from the host itself. So hosts can provide hosting services to multiple dApps without needing to know anything about the dApp or its Devs.
A Hook-enabled Account on the Xahau Network co-ordinates the canonical registry of Evernode Hosts, issuing and redeeming the Registration NFTs. This makes Evernode truly decentralised as the Xahau Network controls the registration of Hosts and the emission of Evers rewards to Hosts.
The Xahau Network is a new secure public “sidechain” of the XRPL that does everything Evernode needs and provides many benefits.
Xahau is built from the same codebase as the XRP Ledger. It is a UNL consensus-based network that is cheap, speedy, and secure. It also has a native DEX and uses URITokens to support NFTs.
Evernode doesn’t need a new, bespoke ecosystem of wallets, browser plug-ins, and explorers. Evernode works with existing Xahau/XRPL ecosystem tools like the Xaman wallet.
Xahau implements Hooks, small pieces of code installed on an account that impose rules on the transactions the account sends or receives before those transactions can be finalised in the Ledger.
Evers are tokens issued on the Xahau Network. Their emission and circulating supply is openly governed by a Hook. They are as secure and persistent as the Xahau Network.
By using Hook-enabled Xahau Accounts to manage its registry of Hosts, its rewards and its reputation scores, Evernode is fully decentralised, despite the registry being a single source of truth.
Hosts and Evernode Labs propose changes to the Evernode Hooks and vote on them through the Governance Hook. Proposals are staked in Evers and accepted or purged by a fixed rule-set on the votes received.
Because Evernode dApps are just normal Apps with a consensus engine Evernode dApps can be programmed in any POSIX-compliant language, including NodeJS, C++, and Rust.
Evernode dApps can be programmed to run only on servers from certain jurisdictions, giving you the flexibility comply with problematic laws like privacy/GDPR and trade embargoes.
Evernode dApps can do in concert anything normal Apps can do solo, including read/write data, perform complex computations, connect to external services, and serve traffic to the open internet.
Evernode dApps can be deployed to as many or as few nodes as you desire to meet competing needs on cost, security, performance, and censorship resistance.
Every instance gets its own network ports and can be reached directly from the open internet. Alongside the user port that clients connect on and the peer port that carries consensus, each instance is given four general purpose ports — two TCP and two UDP — that your dApp can use for anything at all.
Most decentralised compute lets your code talk out. Evernode lets the world talk in.
Every instance a Host leases you comes with its own ports. Two of them are spoken for: clients reach your contract on the user port, and HotPocket carries consensus between nodes on the peer port. The other four are yours. Two TCP and two UDP, open to the internet, doing whatever you tell them to do.
Run a web server on one and your dApp serves its own front end. Run an API, a WebSocket feed, a game server, a DNS responder, a streaming endpoint. Your dApp is reachable at an address, like any other service on the internet, while the consensus engine keeps every instance of it honest.
One per instance. Clients connect over WebSocket to send inputs to your contract and receive its outputs.
One per instance. HotPocket nodes use it to run consensus with each other. Your code never touches it.
Four per instance — two TCP and two UDP. Yours to use for any protocol you like. Hosts allow incoming traffic on all of them.
A dApp that can only answer consensus messages needs a normal web server in front of it, and that server is the part somebody can switch off. A dApp that serves its own traffic on its own ports has no such weak point. This is also what the reputation system tests: peers open each other’s general purpose ports and demand a correct answer, so a Host that blocks them stops earning rewards.
Here’s a taste of some of the ultra-flexible, ultra-powerful dApps possible on Evernode.
A simple contract that spawns itself on a target number of nodes, then randomly shuts down a node and spins up on a new node, making it harder to compromise.
A self-sovereign identity solution where the verified identity documents are encrypted and stored on-chain and shared via single-use keys.
A tool that lets you cut-and-past your solidity contracts and have them run as Evernode dApps on the Evernode network.
A decentralised hotel booking site running on Evernode. Its a hotel booking site without the hotel booking company in the middle charging 30%!!
An Xahau-compatible Wallet (like Xaman) for your Xahau keys so you can access your Evers, Xahau XRP and NFTs. You must have at least enough Evers to pay for your Registration, and enough XAH for account reserves and transaction fees.
A dedicated 64-bit Ubuntu server, physical or virtual. Containers and WSL are not supported. The machine must have enough CPU, RAM, swap and disk to run at least three contract instances at once. The Evernode documentation lists the supported Ubuntu versions and the current per-instance figures.
You can’t be a good host without excellent connectivity. You need IPv4 support, a domain name that resolves to one address, and a valid SSL certificate. Evernode sets up free Let’s Encrypt certificates for you. Hosts that peers cannot reach score badly on reputation and stop earning rewards.
Each instance you offer needs a user port, a peer port, and four general purpose ports — two TCP and two UDP — reachable from the internet. Port 80 must be free for SSL renewal. Evernode adds the rules to the operating system firewall for you, but if your machine sits behind an external firewall you must allow that traffic yourself.
You need enough technical skill to run a reliable host and comply with local hosting laws, like copyright take-down requests.
The rewards schedule favours early adopters, since each new Host is more valuable to the network when it is young and small.
51,609,600 Evers are awarded to Hosts in 10 Epochs of 5,160,960 Evers each. Rewards are paid roughly every hour, and shared equally between all eligible Hosts. Each Epoch, the hourly rewards halve and the duration of the Epoch doubles. On this schedule it takes roughly 118 years to distribute all 51,609,600 Evers to Hosts.
The hourly rate halves at each Epoch, so each Epoch lasts twice as long as the one before it. Every Epoch pays out the same 5,160,960 Evers.
The Evernode Hosting Software divides your machine into equal-sized hosting “Slots”. You mint Lease NFTs for each Slot, specifying the hourly rent in Evers and offer them for sale on the Xahau Network. The Evernode Software handles this for you.
The Lease NFT represents a “best-endeavours” promise to provide exclusive use of that Slot for so long as the hourly rent is paid. At anytime, a Host can revoke a Lease NFT and cancel a Tenant’s instance. This right is necessary because Hosts have no relationship with the Tenant, but may have legal obligations to meet, like copyright takedown requests.
Evernode does not take a Host’s word for it. Hosts test each other, hour by hour, and report the results to a Hook. Only Hosts that pass earn rewards.
Evernode runs on four Hooks on the Xahau Network. The Registry Hook records who the Hosts are. The Heartbeat Hook takes the hourly heartbeat and pays the rewards. The Governance Hook runs the governance game. The Reputation Hook holds every Host’s score and decides who is worth paying.
The score comes from the Evernode Reputation Contract, an ordinary Evernode dApp that Hosts run on themselves. It uses the same pathway a tenant uses: rent a Slot, upload a contract, join a cluster, reach consensus. A Host that cannot do that for the reputation contract cannot do it for anyone else either, and its score says so.
| Range | A Host’s reputation runs from 0 to 255. Run evernode status to see it. |
|---|---|
| Reward Threshold | A Host needs a reputation of 200 or more when its heartbeat is received. Below that it earns nothing, however long it has been on the network. |
| When It Updates | The Heartbeat Hook recalculates reputation from the reported score each time it takes a heartbeat. |
| Reset to Zero | Reputation drops to 0 if a Host has unoffered leases, supports fewer than three instances, charges more than 110% of the average reward per Host, has not opted in to reputation, or has missed its universe for two moments running. |
A Host cannot fake a reputation score. The marks come from 63 strangers reassigned every hour, the work is expensive enough that it cannot be faked cheaply, and the result is written to a Hook on Xahau rather than to a server Evernode Labs controls. Rewards follow real capacity, not claimed capacity.
| Name | Evers |
|---|---|
| Ticker | EVR |
| Maximum Supply | 72,253,440 |
| Issuing Chain | Xahau Network |
| Issuing Network ID | 21337 |
| Issuing Address | rEvernodee8dJLaFsujS6q1EiXvZYmHXr8 |
Evers are issued on the Xahau Network. Any Xahau-compatible wallet will hold Evers. We recommend the Xaman Wallet for its full Xahau support.
All services on Evernode are priced and paid for in Evers. Hosts need Evers to pay for network registration. Tenants (dApps) need Evers to pay for hosting.
Evers trade on the Xahau Network’s native decentralised exchange. Set an Evers trustline in your wallet and trade there.
72,253,440 Evers have been issued from a blackholed Xahau Network Address. The issuing address is rEvernodee8dJLaFsujS6q1EiXvZYmHXr8. No new Evers can ever be issued.
20,643,840 Evers were issued to create the initial supply, in four equal parts of 5,160,960 Evers:
The remaining 51,609,600 Evers are held inside the Evernode Heartbeat Hook and distributed programmatically as rewards to Hosts in 10 Epochs of 5,160,960 Evers over 118 years.
Get Involved & Stay Up-To-Date
Stay up-to-date by following Evernode’s only official social media official account on Twitter/X @EvernodeXRPL.
Follow On TwitterAn independent discord channel run by members of the Evernode community.
View NowDownload the hosting software and start earning Evers, or review the SDK and start building.