Roadmap

What you can build on today, what is coming, and what is only being explored. Updated 27 September 2026.

Build today: Commit, proofs, auctions, x402, and Private Links on Sepolia. Next phase: a committee key from a DKG, with no trusted dealer. Coming next, no ETA: webhooks, invite-list rounds, currency conversion and short-link claiming. Exploring: MCP, typed SDKs, and Private Links on mainnet.

Not live yet

What each item will add, what to do today, and whether it will change existing behaviour. The committee key from a DKG is the next phase; the rest of "coming next" is intent without a committed date or order.

  • coming nextWebhooks A call to your URL when a round opens. Planned, not started, no ETA. Today: poll GET /v1/rounds/{id} with If-None-Match, which answers 304 until something changes. Additive: polling keeps working. Event schema not decided.
  • coming nextInvite-list rounds Only listed participants may seal to a round. Planned, not started, no ETA. Today: any valid ciphertext can be sealed, so check membership in your own app before submitting. Additive: an optional field on POST /v1/rounds; rounds created without it behave exactly as now.
  • exploringMCP tool seal_until(payload, unlockAt) for agents without an SDK. Not scheduled. Today: the agent skill, peal.js, or plain HTTP. Additive.
  • exploringTyped SDKs TypeScript, Python and Go. Not scheduled. Today: peal.js and plain HTTP. Additive.
  • coming nextCurrency conversion Bidders pay in another currency. Planned, not started, no ETA. Today: convert in the client and seal bids in the auction currency. Additive: bids stay integer minor units in the auction currency. Input format not decided.
  • next phaseCommittee key from a DKG Next phase. The committee key comes from a distributed key generation, so no single machine ever holds it and there is no trusted dealer. It uses the scheme from DKG Is All You Need (Commonware): no fixed batch size (up to 4,095 seals per round), every ciphertext carries a proof and is bound to its round, and the DKG raises today's 3-of-5 threshold to 4-of-5. Built and tested, including five separate operators running a key generation and a reveal end to end; not deployed yet. Today: the hosted committee was dealt by a single ceremony. No change for peal.js callers; code that builds ciphertexts itself will have to bind each seal to its round.

Shipped

  • 2026-09-27One-command verify (curl -fsSL https://peal.network/skill/verify.sh | sh), browser, Node and agent paths in Get started, and real 404s for dead links
  • 2026-09-17Peal Private Links hosted on Sepolia
  • 2026-09-04The v1 API: rounds and seals, seal until a time with its proof, sealed-bid auctions, short-link availability, currencies, metered calls over x402, peal.js, and the coding-agent skill