Fairmint’s toolkit proposal passed on November 10, 2026. Source.
Fairmint’s 3.5 million CC proposal for a Canton Privy toolkit has passed the Development Fund’s technical and operations vote. The November 10 decision moves the project beyond its earlier funding request and into a programme of software delivery and verified adoption.
The aim is to help applications that already use Privy for login and built-in wallets approve transactions on Canton without rebuilding the same connection from scratch.
The problem it is meant to solve
Signing in to an app and approving a blockchain transaction are different tasks. Login establishes who is using the app. A cryptographic signature authorizes a particular action, such as transferring tokens.
Fairmint’s approved plan says teams using Privy currently have to assemble several parts of Canton signing themselves. Those parts connect the wallet key to the correct Canton account and make sure the transaction executed is the one that was approved.
The grant funds an open-source software development kit, or SDK: a reusable library that other developers can add to their own applications. It does not fund a new exchange, a new wallet or a replacement login service.
How the connection would work
- Prepare the action. The application’s Canton connection prepares the transaction.
- Approve that transaction. A Privy-managed key signs it, either after the user approves it in the browser or under a configured server-side policy.
- Execute what was signed. The Canton connection submits the same prepared transaction.
In the browser route, the user approves each operation. The policy-managed route is designed for automated workflows whose signing rules are set by the application. Those are different approval arrangements; the toolkit is intended to support both.
Milestone funding in Fairmint’s approved proposal.
What the 3.5 million CC funds
The programme separates building the software from demonstrating that outside teams use it:
- 900,000 CC: a public stable release, documentation and a working demonstration on DevNet, Canton’s development network.
- 600,000 CC: a Privy signing component for Canton’s Wallet Gateway, a sample integration and an outside developer’s documentation trial.
- Up to 2 million CC: independent MainNet adoption and the start of maintenance. The plan allows 600,000 CC per verified independent integrator, capped at three, plus 200,000 CC for the adoption note and maintenance start.
The last allocation is about 57% of the total. Its purpose is to tie most of the funding to use beyond Fairmint’s own application, rather than treating publication of a software package as the finish line. Unpaid adoption claims expire at the end of the claim window.
What developers should expect next
The first milestone is estimated at two months after approval. The second is estimated two months after that and can begin in parallel. These are development estimates, not a promise that a production-ready package is available today.
The plan calls for public transaction references that another reviewer can check on DevNet. It also includes a contribution to Canton’s Wallet Gateway, which connects applications, signing services and the network. Submission of that contribution is a milestone; the upstream maintainers control whether and when it is merged.
The next evidence to look for is therefore practical: the public package, a reproducible demonstration, and applications outside Fairmint using it on MainNet. The funding decision approves that work, rather than confirming its completion or payment of the entire allocation.
Official records: Vote decision · Deliverables and funding terms · Fairmint on X.
