Skip to main content

Epic Cash

Developer's Hub

Documentation, Guidelines and Code Examples.

Proof of WorkOpen SourcePrivate

If you have worked with other blockchains

Four things that work differently here

  1. There are no addresses in the ledger. An epicbox address routes a message between wallets. No output is paid to it, so there is no balance to query and no history to read.
  2. A transfer needs both parties. The sender builds a partial transaction called a slate, the receiver adds their half, the sender finalises. Delivery, not consensus, is where transfers fail.
  3. Sending reserves your outputs. They stay unavailable until the transfer confirms or you cancel it. Nothing releases them on a timer.
  4. A seed phrase restores funds, not history. There is no public record to rebuild from, so a recovered wallet has a correct balance and an empty transaction log.

It completes. Step 1 of 5. The sender asks the node for the chain tip, builds a slate, and reserves the inputs it will spend.

The developer journey

Learn Epic in eight stages

From how the ledger works to driving a wallet from code. Each stage is one page.

read
  1. Understand the ledger
  2. Understand the exchange
  3. Build the binaries
  4. Run a private chain
  5. Complete a transfer
  6. Connect to mainnet
  7. Operate a wallet
  8. Build an integration
Start at stage 01Progress is measured by how far you read and stays in this browser.

Everything else