Leash.

Roadmap

Done

Before any mainnet use

  1. Independent audit of the five contracts (audit package), then a bug bounty.
  2. Chain support: pqcVerify and the key registry active on mainnet. This is out of our hands.
  3. Owner key custody: hardware-backed storage for the ML-DSA-87 key, and a signing flow people can use (wallet support for signing arbitrary messages, or a small signer app).
  4. A keeper for window renewals, holding the agent account's ML-DSA-87 key off the agent's machine.
  5. A deployed monitor with a stop-only freezer key and alerts someone answers.
  6. Real routers and tokens (the QoreSwap router address is not published yet).
  7. A migration plan: the guard is immutable, so a fix means a new guard.
  8. Staged rollout: tiny caps, short expiries, one real route.

Ideas

Questions for the QoreChain team

  1. When will pqcVerify (0x…0a01) and pqcKeyStatus (0x…0a02) be active on mainnet, and is the gas cost stable?
  2. What is the QoreSwap router address on testnet, and will it be on mainnet?
  3. Is a precompile for the native AMM (x/amm) planned, so a contract can swap there?
  4. Will QoreX sign arbitrary messages with the ML-DSA-87 key, so an owner can sign a mandate from a wallet?
  5. Are EVM windows going to stay capped at about 6 hours?
  6. Is there a published list of audited or recommended routers and vaults?

View this page on GitHub · raw markdown