Canton Coin Gets a 24-Hour Signing Window for End-User Transactions Under CIP-0107
The change replaces a 10-minute window between preparing and executing a CC transaction, so institutions with multi-person approvals can sign CC transfers like other Canton tokens.
The Canton Foundation approved CIP-0107 on 10 March 2026. The proposal gives Canton Coin (CC) end-user transactions a 24-hour submission delay, the time allowed between preparing a transaction and executing it, instead of the roughly 10 minutes that applied until then. The CIP was written by Simon Meier and Moritz Kiefer and created on 21 January 2026.
The problem it solves
On Canton, a transaction submitted by an external party is first prepared and must then be signed with the keys registered for that party before it is executed. The CIP notes that signing often needs explicit human approval, sometimes from several people. Completing that inside 10 minutes, it says, can be disruptive and does not match what users expect from other networks or from other assets on Canton's Global Synchronizer.
The short window came from CC's design: its transactions relied on the current mining round, a contract that changes every 10 minutes or so. Other tokens built on the CIP-0056 token standard did not have that limit.
What changes
- A new 24-hour configuration contract. A new contract, active for 48 hours and replaced every 24 hours, copies the CC price, the round number, holding fees and transaction limits from the latest mining round. CC's token standard operations use it instead of the mining round.
- Scope. The 24-hour delay covers all token standard operations, plus creating, renewing and archiving transfer preapprovals, buying traffic, and tapping funds on DevNet.
- Full token standard compliance. Once live on MainNet, the "Canton Coin Limitations" section of CIP-0056 is to be removed.
- Older endpoints deprecated. The non-standard TransferCommand template and two related validator endpoints are marked for later removal.
Trade-offs and limits
Because the configuration contract lives longer, changes to its values take up to 48 hours to propagate. The CIP says this barely matters for holding fees but has a bigger effect on traffic purchases, where a price change is more significant. Reward minting still runs on the 10-minute window; the CIP points to minting delegation as a short-term workaround and to traffic-based rewards as a longer-term fix.
For developers, apps using the token standard APIs need no changes. Apps that parse CC-specific choices directly, or that use the old unlock and lock expiry choices, will need updates when they recompile.
Why it matters
Custodians and institutions often run approval workflows that take longer than 10 minutes. Removing that constraint lets CC move through the same signing processes as stablecoins and tokenized assets on Canton, which matters for exchanges, custodians and hardware wallets that support CC.
