Address Generation

Your own addresses (default, non-custodial)#

For each coin, set one or more receiving addresses under Settings → Addresses. That is the whole non-custodial contract: payments detect on-chain and settle to your addresses; the platform never holds funds.

• Enter addresses separated by commas or new lines - several per coin are encouraged
• Web3 names work: ENS, Unstoppable Domains, and FIO names are resolved to the on-chain address at save time, with the name kept for display
• Addresses are format-validated per network at save

Address cycling and reuse#

With 3 or more addresses on a coin, cycling activates automatically: each new checkout gets the address least recently used, past a cooldown.

• Default cooldown: 24 hours per address; presets (Immediate, 1 hour, 24 hours, custom) are on each coin's card
• Set stop reusing addresses to never re-issue an address once used (maximum privacy, needs a healthy pool)
• Cycling pools count as a form of per-checkout addressing without any key material on the platform

Derived and generated addresses#

If you want a fresh address per checkout without pasting dozens, enable a generation path - the platform resolves in this order:

1. Your own node/xpub (Bitcoin) or your ETH node - derivation happens against your infrastructure
2. Custom explorer generator - your explorer's address endpoint (see Custom Explorers)
3. Manual cycling pool - the list you pasted
4. Connected exchange - Gemini or Coinbase deposit addresses

Money-services businesses using generated addresses should record the custodial acknowledgment in settings - generated deposit addresses mean the exchange holds those funds until you withdraw them.

Operating tips#

• Keep static addresses for your highest-volume coins - simplest, fastest, zero dependencies
• Watch the addresses dashboard: each coin card shows the pool, the cycling state, and per-coin confirmation presets
• Rotating a compromised address is instant: remove it from the list and new checkouts stop using it immediately