XE Network¶
XE is a block-lattice cryptocurrency where every account maintains its own blockchain. Cross-chain references between accounts form a directed acyclic graph (DAG), enabling parallel transaction processing with no global bottleneck.
Alice Bob Carol
┌─────────┐ ┌────────┐ ┌─────────┐
│ claim │ │ recv │ │ claim │
│ bal: 10 │ │ bal: 5 │ │ bal: 10 │
└───┬─────┘ └───┬────┘ └───┬─────┘
│ │ │
┌───▼─────┐ ┌───▼────┐ ┌───▼─────┐
│ send │─────▶│ recv │ │ send │
│ to: Bob │ │ src: │ │ to: Bob │
│ amt: 5 │ │ bal: 10│ │ amt: 3 │
│ bal: 5 │ └───┬────┘ │ bal: 7 │
└─────────┘ │ └─────────┘
┌───▼────┐
│ recv │◀── from Carol
│ bal: 13│
└────────┘
The network supports two native assets — XE and XUSD — and extends the block lattice with compute leasing, DAO governance, peer-to-peer messaging, and an account directory.
Core Properties¶
Account-chain architecture. Each account has its own chain of blocks. Sends debit the sender's chain; receives credit the recipient's chain. No miners, no global ordering.
Dual assets. XE is emitted as a reward for compute providers. XUSD is used to pay for compute leases and confers voting weight for consensus.
Compute leasing. Consumers lease virtual machines from providers. Resource costs are denominated in XUSD; providers stake collateral and earn XE emissions upon settlement.
DAO governance. A deterministic state chain allows the network to evolve parameters through signed proposals without hard forks.
P2P messaging and directory. Nodes exchange messages and register in a decentralised account directory.
Components¶
| Component | Stack | Description |
|---|---|---|
| Core node | Go, libp2p, BadgerDB | Block lattice, consensus, networking, API |
| Explorer | SvelteKit 2, Svelte 5, Tailwind | Block explorer and network dashboard |
| Web Wallet | SvelteKit 2, Svelte 5, Tailwind | Browser wallet for sending, receiving, leasing |
| Proof of Uptime | Node.js | Verifiable uptime proofs for compute providers |
Documentation¶
Concepts¶
- Overview — what XE is, how it works
- Quick Start — build and run a node
- Architecture — package breakdown and startup sequence
- Block Lattice — the DAG structure
- Accounts and Keys — ed25519 key pairs and addresses
- Block Types — all eight block types with field-level detail
- Assets — the dual-asset model (XE and XUSD)
Protocol¶
- Consensus — delegation, conflict detection, voting, quorum resolution
- Networking — libp2p, gossip, frontier sync, DHT, messaging
- Compute Leasing — lease lifecycle, cost model, attestations, VM management
- State Chain — DAO governance via deterministic state machine
- Proof of Uptime — heartbeat chains, merkle epochs, production design
Interfaces¶
- API Reference — HTTP REST API for accounts, blocks, leases, chat, and more
- Node CLI — interactive node commands
- Client CLI — standalone HTTP client for offline signing
- Explorer — block explorer pages and features
- Web Wallet — browser wallet with multi-wallet, chat, compute, DAO
Reference¶
- Binary Encoding — block and vote wire formats
- Storage — store interfaces and BadgerDB key layout
- Proof of Work — blake2b PoW algorithm
- Cryptography — ed25519, SHA-256, signing contexts
- Constants — all system constants in one place
- Deployment — Docker, configuration, production setup