Start your Epic developer journey
Eight stages. By the end you will have built the binaries, mined your own chain, moved coins across it, and driven a wallet from code.
Stages 03 to 05 run on a private chain you create yourself, with coins you mint. It behaves exactly like mainnet and touches nothing on it.
The route
- Understand the ledger
You know why Epic has no on-chain receiving addresses and no public transaction history.
- Understand the exchange
You can describe a slate, its two rounds, and why delivery can fail without losing funds.
- Build the binaries
You have working epic, epic-wallet and epic-miner binaries for your platform.
- Run a private chain
A node is producing blocks on usernet and one of your two wallets holds spendable coins.
- Complete a transfer
You have moved coins between your own wallets and seen what each transport changes.
- Connect to mainnet
A synced mainnet node and a wallet you have backed up, with real value at stake.
- Operate a wallet
You can receive, send, read what the wallet reports, recover it, and clear a stuck transfer.
- Build an integration
You can drive the node and wallet APIs and handle Epic’s Ok/Err response envelope.
Already know the subject
Skip the sequence and go straight to the reference:
- Configuration and CLI for commands and persistent settings.
- API reference and code examples for programmatic work.
- Mining and consensus for node and protocol work.
- What changed in v4 if you are returning from the 3.x documentation.
What this version does not cover
Tor. Release archives do not include the tor binary the wallet's onion listener requires, and
use_tor_listener defaults to true, so a plain epic-wallet listen can fail in a background
thread. Turn off the Tor listener has the change.
The Tor configuration keys are listed in the wallet and
node references.