Addresses
epic-wallet address prints several identifiers, each with a different purpose. None of them appears in
the ledger; see why there are no addresses.
| Identifier | Purpose |
|---|---|
| Epicbox address | Route slates to you through a store-and-forward relay |
| Payment proof address | Prove afterwards that you were the intended recipient |
The wallet also prints an onion address, used by the Tor transport.
Epicbox addresses
The format is:
<public_key>@<domain>[:<port>]
optionally prefixed with epicbox://.
The public_key is 52 base58 characters, a compressed secp256k1 public key in base58-check encoding,
with version bytes [1, 0] on mainnet and [1, 136] on floonet.
Two properties follow from that encoding. A corrupted address fails its checksum and the wallet rejects it locally, without contacting the network; what that does and does not protect against is covered in there are no addresses. And mainnet and floonet addresses cannot be confused, because a floonet address will not parse as a mainnet one.
Usernet wallets emit mainnet-prefix addresses ([1, 0]). Only floonet gets a distinct prefix ([1, 136]).
The domain defaults to epicbox.epiccash.com when omitted. Port 443 is the default and is not shown;
other ports are.
Because the identifier is a real public key, a relay can verify you own the address by asking you to sign a challenge, without ever seeing your private key. See epicbox authentication.
Every epicbox derivation uses index 0, so a wallet has one epicbox address for each account it holds.
The epicbox_address_index config key is reserved.
Payment proof addresses
A separate key used to prove afterwards that a specific party was the intended recipient of a specific
transfer. It has to be arranged before the transfer, because the recipient signs the proof as part of
their round. epic-wallet address prints it under this heading.
See payment proofs, and choose the transport accordingly for the routes that carry one.