Accounts & Wallets

1. Account Model

XE uses a block-lattice architecture where every account maintains its own blockchain. Each block's Previous field points to the hash of the preceding block. The first block has Previous = "0".

Transfers require two blocks: a send (debits the sender's chain) and a receive (credits the recipient's chain, referencing the send hash). This cross-chain referencing creates a directed acyclic graph (DAG).

2. Ed25519 Key Pairs

Every account is an ed25519 key pair. The account address is the hex-encoded 32-byte public key – 64 lowercase hex characters. No base32, bech32, or checksum encoding.

• Public key: 32 bytes – used as the account address;
• Private key: 64 bytes – used for signing blocks;
• Seed: 32 bytes – stored in {dataDir}/node.key;
• Signing: ed25519 signatures on SHA-256 block hashes.

3. Create a Wallet

Use the xe CLI to generate a new wallet.

# Generate a new wallet (ed25519 key pair)
xe wallet create

# Output:
# Wallet created
# Address: 3b66f35ce20c29e383dab3570d8fe9c2b3220058...
# Seed saved to ~/.xe/wallet.key

4. Fund Your Account

On testnet, claim 100 XUSD from the faucet (once per 24 hours per account). XUSD is used to pay for compute leases and confers voting weight for consensus.

# Claim 100 XUSD from the faucet (once per 24 hours)
xe fund

# Then receive the pending claim
xe receive

# Check your balances (XE and XUSD)
xe wallet balance

# Output:
# XE:   0
# XUSD: 0

5. Send & Receive

Transfers require a send block (debiting the sender) and a receive block (crediting the recipient). The recipient must explicitly receive pending sends.

# Send XUSD to another account
xe send <recipient_address> 50 --asset XUSD

# Recipient must run 'xe receive' to credit their chain

6. REST API

The core node exposes an HTTP REST API on port 8080. Rate limited: 100 req/s sustained, 500 burst per IP. JSON encoding. Hex-encoded hashes and keys. Unix nanosecond timestamps.

# Query account via REST API
curl https://ldn.test.network/api/accounts/<address>

# Submit a block via REST API
curl -X POST https://ldn.test.network/api/blocks \
  -H "Content-Type: application/json" \
  -d '{"type":"send","account":"...","previous":"...","balance":...}'

# Compute PoW server-side (for constrained devices)
curl -X POST https://ldn.test.network/api/pow \
  -H "Content-Type: application/json" \
  -d '{"hash":"..."}'

7. Block Types

XE supports eight block types. Each is signed with ed25519 and includes a blake2b proof-of-work nonce for anti-spam.

• send (0x01) — transfer XE or XUSD to another account (162 bytes);
• receive (0x02) — accept an incoming transfer (154 bytes);
• claim (0x03) — mint 100 XUSD from the faucet, once per 24 hours (122 bytes);
• lease (0x04) — request a compute lease, specifying resources and duration (226 bytes);
• lease_accept (0x05) — provider accepts a lease, staking collateral (162 bytes);
• lease_settle (0x06) — settle an expired lease, minting XE emission (162 bytes);
• multisig_open (0x08) — create an M-of-N multisig account (variable size);
• multisig_update (0x09) — rotate a multisig keyset (variable size).

8. Key Points

• Every account has its own chain of blocks – block-lattice architecture;
• Account address = hex-encoded ed25519 public key (64 hex characters);
• Transfers require two blocks: send (debit) and receive (credit);
• Instant finality for non-conflicting transactions;
• No transaction fees – anti-spam via blake2b PoW (~1 second);
• Two native assets: XE (emission rewards) and XUSD (lease payment / voting);
• XUSD faucet: 100 XUSD per 24 hours on testnet;
• CLI: xe unified binary with 15+ commands.