V2 ON-CHAIN ESCROW · CANARY LIVE
ZCD's first trading venue
Peer-to-peer OTC for Zycord (ZCD), settled with a non-custodial on-chain escrow: the seller locks ZCD against a hashlock, the buyer verifies every cell on-chain before paying the external leg, and the secret releases the funds. This site holds no key, posts no quotes, runs no order book and arbitrates nothing.
To our knowledge this is the only trading venue operating on the Zycord mainnet today (2026-11). Deals are arranged peer-to-peer in community channels; this page and its tools only make settlement verifiable.
—
Global locked (escrow)
—
Contract balance
—
Chain height
—
Contract epoch (moves daily)
Live from the public read-only RPC (
/rpc/status · /rpc/balance · /rpc/storage) — same data any node gives you. On-chain escrow — HashlockEscrow
0x052a29446468cfc75299c5161e4047c232c904319c9b57cd39343a5a66a23892
- Canary caps: 20 ZCD per deal · 60 per opener · 200 global. Guards check pre-certificate state, so the worst case overshoots by one deal (global ≤ 220, per-opener ≤ 80) — bounded, never compounding. Caps stay until the external audit passes.
- Lock window 24–48 h at minimum (refund height must cross the next epoch boundary; max ≈ 30 days). After expiry anyone can trigger the refund — funds go back to the seller.
- Canary record: a 1.0 ZCD deal ran end-to-end (open → six on-chain cell checks → four negative tests → an exact claim to the drop); a 0.1 ZCD timeout-refund test is in flight and auto-fires on 2026-11-10.
How a deal works — five steps
- Agree terms peer-to-peer (size, price, refund window). No quotes come from this site.
- Seller generates a 32-byte secret S, shares only sha256(S) and locks the ZCD on-chain naming the buyer as claimant.
- Buyer runs all seven checks below — BEFORE paying the external leg.
- Buyer pays the external leg; seller confirms receipt and hands over S (seller self-checks sha256(S) first).
- Buyer (or any S holder) claims on-chain; funds move to the registered claimant. If the window lapses, anyone can trigger the refund to the seller.
- The external payment leg (fiat, USDT, …) has no on-chain protection. Caps bind the ZCD leg only — size the external leg to the trust you place in the counterparty.
- The contract guarantees the ZCD is really locked and the secret really releases it — not that the seller delivers. A seller can refuse to hand over S and eventually refund themselves. Small test trades first; keep evidence.
- The buyer's payout wallet must have made at least one on-chain transaction before the deal (its 20-byte name is bound); the seller should be a plain wallet too — a contract-opener can strand its own refund.
- Actual refund unlock happens at the first epoch boundary at or after refund_height — up to one full epoch (~24 h) later than the nominal height. Do not wait until the last moment to claim.
Verify a deal in your browser
Paste the seller's shared deal record (the output of zcd-escrow share — it contains no secret). This page re-derives the deal id and checks every cell straight from the public RPC, the same seven checks the CLI does. The record itself never leaves your browser — the page only asks this site's public RPC for chain state, the same reads any node would serve.
Handover check — after the seller gives you S:
All seven rows must read OK before you pay anything. A single MISMATCH means do not pay. The checks prove the lock is real and matches the shared record — they say nothing about the counterparty.
OTC bulletin (v1) — plain peer-to-peer
For sizes under the escrow caps — or while you wait for a lock — plain OTC works without any contract. Deals are arranged in the community Discord (#pools) or direct messages; this site runs no listing, no matching, no escrow arbitration.
- Agree the price peer-to-peer — this page never quotes.
- With a stranger, small test trades first on the external leg.
- Seller sends ZCD on-chain and shares the certificate id.
- Trust on-chain confirmations only — never chat screenshots.
- Large sizes: use the escrow above; 20 ZCD per deal until the audit raises the caps.
—
On-chain supply, all funded addresses (ZCD)
—
Addresses with balance
—
Top-10 concentration
—
Rich-list snapshot height
Note: top rows include pool aggregation addresses — one address is not one owner; concentration is a network metric only. More fundamentals on the dashboard (hashrate, emission, pool share) and the full rich list on /leaderboard.
Roadmap — and what will never be built
T1 · Live nowThis page + the OTC guide + network fundamentals. Zero custody, zero quotes. The 3D dashboard carries the same venue in-world.
T2 · Non-custodial escrow — canary liveHashlockEscrow deployed (20 per deal / 60 per opener / 200 global ZCD). Full 1.0 ZCD canary passed end-to-end; 0.1 ZCD timeout-refund test in flight. Next: external audit, then raising the caps.
T3 · AMM infrastructure (only if)Prerequisites: a fungible token standard on-chain + zero operator LP (pool wallets never provide liquidity) + community-seeded liquidity — plus a fair-ordering answer to the operator mining 16–20% of blocks.
NeverCustodial order books, CEX-style custody, operator market-making, and any mechanism where block data decides a money outcome. The right path to an exchange listing is third-party platforms adding ZCD.
- The operator of this site is a mining-pool operator and mines ~16–20% of all ZCD blocks. The escrow contract has no operator key that can move a deal.
- Transactions are submitted only through your own zcd CLI and wallet — this site relays no signatures and holds no funds.
- Canary caps stay in force until an external audit passes; an open audit invitation with the full source, byte-level deploy proof and every disclosure lives in the manual (/otc/escrow.html).
- Nothing on this page is a price quote, an offer, or investment advice.