HackCanton Season 1: What 40 Teams Built on Canton Network

HackCanton Season 1 closes submissions on May 15, 2026. With three weeks of building behind them, more than 40 teams have been working against Canton Network's live mainnet infrastructure: the first structured hackathon the Canton Foundation has organized. The event is not a speculative exercise. Teams build with real DeFi rails, real liquidity, and real economic incentives that persist after the competition ends. What they have produced in that window says something specific about where Canton developer activity is headed in 2026.

The hackathon launched April 15, organized by Noders and backed by the Canton Foundation. Four tracks defined the scope: decentralized finance, real world asset infrastructure, core network infrastructure, and identity. Each track maps to a genuine gap in Canton's current application layer: areas where institutional demand exists but builder tooling or product coverage is thin. The track design reflects a deliberate choice by the Canton Foundation to use HackCanton as directed builder capacity, not open ideation.

The Infrastructure Teams Are Building Against

HackCanton participants are not building on a testnet. Canton's mainnet DeFi stack is live and operational: Temple Lightspeed (institutional limit order book with subsecond matching), Helvet Swap (automated market maker for CBTC and CC pairs, backed by BCB Group for institutional liquidity), PerpSwap (total return swaps with CC and CBTC as underlying, up to 10x leverage), and RhoLabs (CBTC lending with verified onchain collateralization). Every application submitted to HackCanton can, in principle, integrate directly against these production systems rather than mock environments.

This is what separates HackCanton from most hackathons in the blockchain space. A team building an AI driven collateral optimization tool can route actual CBTC through RhoLabs. A team building a compliance monitoring layer can observe real settlement flows on the Global Synchronizer. The feedback loop between code and production behavior is immediate. For developers serious about institutional DeFi, that infrastructure access is the argument for building on Canton rather than a public chain where institutional liquidity is absent and privacy is structurally impossible.

Canton's sub-transaction privacy model is the technical foundation that makes the AI track meaningful. On a public chain, an AI agent managing a fixed income portfolio broadcasts its strategy to every other participant before each transaction settles. Front running that agent is trivial. On Canton, the sub-transaction privacy model means parties see only their own data. An AI agent executing a multileg repo trade on Canton does not expose its book to competitors. The settlement data is visible only to the counterparties involved. That privacy is not a configuration option: it is enforced at the protocol level by the Daml smart contract language.

The Economic Incentive That Outlasts the Hackathon

HackCanton prizes are not the endpoint for winning teams. Canton's CIP-0104 traffic based reward system means that any application approved as a Featured App on the network earns a share of Canton's transaction fee reward pool on an ongoing basis. The reward pool is funded by CC transaction fees burned by the Global Synchronizer: approximately $2.4 million per day as of Q1 2026. Applications that drive genuine onchain volume receive a proportional share of that pool, permanently, as long as they remain active.

This creates a different kind of hackathon calculus. A team that ships a working DeFi application to HackCanton and earns Featured App status is not just competing for a one time prize. They are building a business with a recurring protocol revenue stream. The Canton Foundation structured HackCanton around working applications rather than prototypes specifically to maximize the number of teams that cross that threshold. Featured App approval requires real integration with Canton's production infrastructure, not a demo.

The economic context matters because Canton's network activity is growing at a rate that makes the Featured App reward meaningful. Canton processed $8 trillion in monthly real world asset volume as of Q1 2026, with 800+ institutions connected to the network. Daily onchain asset movement exceeds $350 billion, driven by institutional repo, tokenized securities settlement, and structured product trades through venues like Broadridge's Distributed Ledger Repo platform. Applications that route even a small fraction of that volume earn real rewards.

What the Track Choices Reveal

The four HackCanton tracks are not arbitrary. Each maps to a specific institutional workflow that Canton's architecture can serve better than alternatives, and each has an existing market pull from the 800+ institutions already on the network.

The DeFi track targets the layer between Canton's settlement infrastructure and institutional trading desks. The gap is tooling: Canton has institutional liquidity in the form of Temple, Helvet Swap, and PerpSwap, but the portfolio management, yield optimization, and risk aggregation tools that would let a treasury team run a full DeFi strategy on Canton are still nascent. Teams in this track are building exactly those tools, with access to live liquidity and real settlement feedback.

The real world asset track targets the application layer above Canton's existing tokenization infrastructure. Canton already processes $8 trillion monthly in tokenized repo, securities, and fund units: primarily through institutional venues that built custom integrations. The gap is standardized tooling for smaller institutions that want access to Canton's settlement guarantees without building from scratch. A team that ships a working RWA issuance and distribution tool in HackCanton could address a market that Canton's institutional partners have been underserving.

The infrastructure track covers developer tooling, node utilities, and network monitoring. Canton's security architecture and Daml smart contract environment have a steeper learning curve than EVM compatible chains. Any tooling that reduces that curve directly expands the developer addressable market for Canton applications. The Canton Foundation has flagged developer tooling as a 2026 priority: HackCanton is one mechanism for generating that tooling.

The identity track is the most forward looking. Canton's sub-transaction privacy model provides the infrastructure for identity verification without exposing personal data to the full network, but the application layer for onchain identity on Canton is underdeveloped relative to the demand from regulated institutions that need KYC and AML workflows built into their Canton integrations. An identity solution that works natively with Canton's privacy model and integrates with the existing Super Validator governance structure would have immediate demand from the institutional participants already on the network.

The Ecosystem Signal

HackCanton is the first time the Canton Foundation has mobilized independent developer teams at scale. Prior Canton growth came primarily from institutional participants: the 42 active Super Validators, the 800+ connected institutions, and the venue operators running Temple, Helvet Swap, PerpSwap, and RhoLabs. Those are all organizations with legal, compliance, and institutional procurement cycles. HackCanton represents the first attempt to bring independent developer teams into the Canton ecosystem with the same production infrastructure access that institutional participants have had since the Global Synchronizer mainnet launched July 1, 2024.

The signal from 40+ teams building is that the developer pull exists. Canton's architecture has properties that matter to builders who care about institutional finance: sub-transaction privacy, atomic multiparty settlement, subsecond finality, and a live economic reward system through CIP-0104. Whether those properties are compelling enough to attract a sustained developer community, rather than a one time hackathon cohort, is the question that the next six months of Canton ecosystem development will answer. HackCanton Season 1 is the first data point in that answer.

Submissions close May 15. Judging will involve mentors and evaluators from across the Canton ecosystem, including validators, infrastructure providers, and institutional participants. Results and winning projects will determine which teams advance to Featured App status and begin earning from Canton's ongoing reward pool.