Temple v2 Lightspeed: Market Orders and Under 10ms Matching Now Live on Canton Network
Temple Digital Group launched v2 Lightspeed, bringing market orders, real time orderbooks, and under 10ms matching to the Canton Network trading platform for institutions, market makers, and prop desks.
Temple Digital Group shipped a major infrastructure upgrade today. Temple v2, branded Lightspeed, goes live on April 22, 2026, adding market orders, a real time orderbook, under 10ms order matching, and a new SDK with WebSocket support to what was already the most technically sophisticated trading platform built natively on Canton Network.
The release matters beyond the feature list. Temple is not a crypto native exchange running on a general purpose public chain. It is a compliant, privacy preserving trading and asset issuance platform built specifically for the financial institutions that run Canton, the same network where Goldman Sachs, JPMorgan, DTCC, and BNY Mellon settle $350 billion in assets daily. When Temple upgrades its execution infrastructure, the Canton DeFi stack upgrades with it.
What Is Temple Digital Group on Canton Network?
Temple Digital Group describes itself as "a compliant and privacy focused trading, liquidity, and asset issuance platform powered by the Canton Network." In practice, that means a central limit orderbook operating on Canton's Global Synchronizer with atomic settlement: trades execute and settle in the same transaction, with no counterparty risk window between match and finality.
The asset scope is broad: equities, tokens, commodities, and private equity. Temple supports noncustodial wallets, meaning institutions retain direct custody of their assets onchain rather than depositing with an exchange custodian. Native compliance is built into the platform rather than bolted on; Canton's Daml smart contract model enforces permission rules at the contract level, so only authorized counterparties can see or interact with a given position.
Temple has operated with limit orders only since launch. v1 required traders to specify a maximum price they were willing to pay (or minimum price to accept) for every order. Market orders (fill at the best available price immediately) were not supported. For institutional desks accustomed to executing at market in any liquid product, this was a friction point. Lightspeed removes it.
What Types of Traders Use Temple?
Temple's design (compliant onboarding, noncustodial wallets, atomic settlement, Daml enforced privacy) defines a specific participant profile. The v2 Lightspeed upgrade does not expand that profile so much as make Temple viable for strategies those participants already run elsewhere.
Institutional asset managers and prop desks. The institutions that already run Canton nodes for settlement (Goldman Sachs, JPMorgan via Kinexys, DTCC, Broadridge) are Temple's target counterparty base. They hold tokenized assets on Canton and need a matching venue with price discovery. Temple gives them a central limit orderbook with the settlement guarantees they already trust: atomic finality, no counterparty risk between match and clearing, privacy enforced at the contract level so trade terms stay between counterparties. For a desk that already settles on Canton, adding trading activity through Temple is an incremental operation, not a new infrastructure commitment.
Market makers. The v2 Post Only order type and zero cancellation fees were built for market makers. Active quoting (entering quotes, canceling and re-entering as markets move, collecting the spread) requires fast, free cancellations. Temple v2 delivers both, along with under 10ms matching and real time orderbook data that let desks run tighter strategies than v1 allowed.
Quantitative and systematic trading desks. The new SDK and WebSocket API unlock systematic strategies that were not viable on v1. Quantitative strategies need live book state: mean reversion, statistical arbitrage, and execution algorithms all depend on real time price and depth data. REST polling introduces latency that destroys any strategy with a sub second alpha window. WebSocket subscriptions deliver orderbook events as they happen. Temple v2 is now instrumentable for systematic execution in a way v1 was not, making it accessible to the prop trading desks and quant funds that run similar infrastructure on traditional venues.
RWA issuers and asset owners. Temple supports tokens, private equity instruments, and commodities alongside traditional equity. Asset issuers who tokenize on Canton (and there are hundreds across the 800+ Canton participant institutions) can list and trade those assets on Temple with institutional settlement. For a private equity manager who tokenizes fund shares on Canton, Temple provides the liquidity venue without a separate exchange listing or third party custodian relationship.
Temple v2 Lightspeed Features: Market Orders, Orderbook, and Under 10ms Matching
The headline feature is market orders. Temple v2 adds the ability to submit a buy or sell order that executes immediately at the best available price without specifying a limit price. For active traders, this is fundamental: it means you can exit a position or enter on a catalyst without waiting for your limit to be touched. Temple v1's limit only model required more active order management and introduced execution uncertainty when markets moved fast.
Alongside market orders, Temple v2 ships a real time orderbook. v1 orderbook updates were not instantaneous; traders saw a snapshot that refreshed at intervals. v2 delivers live depth of book with every change reflected as it happens. Combined with the new WebSocket API, algorithmic and quantitative strategies can now subscribe to orderbook events directly rather than polling REST endpoints.
Order matching in v2 runs at under 10ms latency. For context, traditional equities exchanges like NYSE and Nasdaq operate at microsecond latency for high frequency trading, but institutional RFQ and block trading platforms (the closer analog to Temple) typically target single digit to tens of milliseconds for their execution SLA. Under 10ms positions Temple competitively for the institutional block trading use case it is designed for, where speed matters but microsecond colocation is not the product.
The v2 release also adds Post Only as a new time in force option. Post Only orders cancel rather than match against resting orders; they only execute by adding liquidity to the book, never taking it. This is the standard mechanism for market makers who want to earn the spread on every fill rather than pay it. Temple v1 had no native market maker mode; v2 adds the time in force option that makes market making viable.
Two friction reducing changes ship alongside the new order types. First, collar requirements and open order limits are removed entirely. v1 imposed price collars (orders beyond a set percentage from mid market were rejected) and capped the number of resting orders a participant could hold. Both constraints were designed to limit market disruption but in practice limited sophisticated trading strategies. v2 removes them. Second, instant order placement and cancellation now carries no fees. Placing a limit, canceling it before fill, and re-entering at a new price is zero cost, a prerequisite for any high frequency or algorithmic workflow.
The new deposit and withdrawal system is the infrastructure layer that makes v2 practical. Faster, more reliable onchain asset movement into and out of Temple positions reduces the operational friction that previously made rapid strategy deployment cumbersome. No specific throughput numbers are published in the changelog, but the system is described as a complete replacement of the v1 mechanism.
Three additional v2 features round out the release. First, Temple now offers an "Earn CC per Settled Transaction" program; participants earn Canton Coin on each completed trade settlement, adding a yield component to active trading activity on the platform. Second, the v2 interface ships with native Light Mode and Dark Mode support, a quality of life improvement for traders who spend extended sessions in the platform. Third, the CBTC/USDCx trading pair is newly enabled in v2, a meaningful addition for traders seeking exposure to Bitcoin backed assets settled with institutional guarantees on Canton.
One feature announced in v2 is not yet live: leaderboard volume based rewards. Temple will launch a trading competition and rewards program on May 1, 2026, where volume ranked participants earn volume based rewards based on their activity. The mechanics are not fully detailed ahead of launch, but the structure ties reward allocations to verifiable onchain trading volume, a model that has driven liquidity bootstrapping across multiple DeFi platforms.
Why This Matters for Canton DeFi
Canton Network processes $8 trillion in monthly RWA volume and $350 billion+ in daily onchain asset movement. The vast majority of that activity is institutional settlement infrastructure: repos, collateral transfers, tokenized Treasuries. It is not retail trading. Temple is the Canton native platform building the trading layer on top of that settlement infrastructure, and Lightspeed is the first release that brings Temple's execution quality to the standard institutional trading desks expect.
Market orders matter specifically for Canton's DeFi ambitions. A platform where you can only trade with limit orders is a venue for patient, price sensitive order flow, not active markets. Adding market orders on Canton opens Temple to execution sensitive flow: traders responding to macro events, institutions executing at market as part of a broader strategy, and desks that need certainty of fill over certainty of price. That is the order flow that creates volume.
Under 10ms matching and real time orderbooks enable market maker participation at institutional standards. Tighter execution latency lets market makers narrow spreads without pricing in the adverse selection risk that slower venues impose, and tighter spreads lower transaction costs for every institutional participant on Canton.
For institutions that already operate on Canton for settlement (repos, collateral transfers, tokenized Treasuries), Temple Lightspeed lowers the incremental cost of adding active trading to existing infrastructure. The settlement guarantees are already in place. v2 removes the execution gap.
Temple vs Trading on Public DeFi: Privacy, Compliance, and Settlement
The comparison most traders make is against Uniswap, Curve, or other public DeFi protocols. The differences are structural, not incremental, and they determine which participant types each venue can legally and operationally serve.
Privacy. On any public blockchain protocol, every trade is visible to every participant. Position size, entry price, and counterparty address are in the public mempool before the transaction confirms, and permanently onchain after. This is not a design flaw that can be patched; it is inherent to public chain architecture. Canton Network enforces subtransaction privacy at the protocol level via Daml. Only the counterparties to a Temple trade see its terms. Validators confirm a valid transaction occurred without seeing what traded or at what price. For institutions running regulated strategies where front running is an existential risk, public DeFi is disqualifying on this point alone.
Compliance. Uniswap has no onboarding; any wallet can trade. Temple requires identity verification consistent with its compliance model, and Canton's Daml smart contracts enforce access rules at execution time. This narrows participant count but eliminates compliance exposure. For a regulated institution, trading on a permissioned platform with KYC'd counterparties is the difference between an approved activity and a regulatory violation. Institutional DeFi trading on Canton operates inside the compliance perimeter; public DeFi generally does not.
Settlement finality. Public DeFi protocols settle in blocks. Ethereum's probabilistic finality means your trade is effectively final after 1-2 blocks, but the protocol can theoretically reorganize under extreme conditions, and there is always a window between trade execution and settlement where counterparty exposure exists. Canton's Global Synchronizer provides atomic settlement: trade execution and final settlement occur in the same transaction. There is no gap, no counterparty risk window, and no T+1 or T+2 waiting period. For institutions that must report positions at end of day with certainty, atomic finality is not a luxury feature.
Execution model. Public DeFi AMMs are not orderbooks; you trade against a liquidity pool at a price set by a bonding curve, with slippage determined by pool depth and your trade size. Temple is a CLOB (central limit orderbook) with price time priority matching. You interact with other traders' resting orders, not an algorithm. For institutions executing in size, the CLOB model provides price discovery, market depth transparency, and execution quality control that AMMs structurally cannot offer. The canton network orderbook model is the institutional standard for a reason.
How to Access Temple Digital Group on Canton Network
Temple operates at templedigitalgroup.com. Access to the platform requires identity verification consistent with Temple's compliance model; the platform is designed for institutions and qualified participants, not open retail onboarding. The v2 interface is live as of today, April 22, 2026, with the full feature set described above except the leaderboard rewards program, which launches May 1.
The new SDK and REST API with WebSocket support are available for institutional counterparties that want to integrate directly rather than use the web interface. WebSocket subscription enables real time orderbook and trade event streaming, a significant capability upgrade for systematic strategies that previously had to poll the Temple API for state updates.
Temple's changelog is maintained at help.templedigitalgroup.com and includes the full v2 Lightspeed feature set with technical detail beyond what the interface surfaces. Institutional counterparties evaluating a Temple integration should read the changelog alongside the API documentation.
Canton Network Trading Infrastructure: Temple's Role
Temple is not the only liquidity venue on Canton, but it is the most complete. Canton's ecosystem includes OTC protocols, tokenized asset issuance platforms, and bilateral settlement workflows built by the 800+ institutions running Canton nodes. What Temple adds is a centralized limit orderbook with transparent price discovery, the structure that allows anonymous counterparties to trade without prenegotiated relationships.
LayerZero's integration with Canton, live as of March 26, 2026, connects Canton to 165+ public blockchains. In theory, this opens the possibility of cross chain liquidity flowing into Temple, with assets bridged from public chains into Canton available to trade on a CLOB with institutional settlement guarantees. The infrastructure plumbing for that flow exists. Whether it materializes depends on demand from institutions who operate across both Canton and public chain environments.
For the institutions already operating on Canton (which now include participants settling $8 trillion monthly), Temple v2 Lightspeed represents the DeFi layer becoming usable at their execution standards. Market orders, under 10ms matching, real time books, and zero cancel fees are not exotic features. They are the baseline expectation for any venue institutional desks take seriously. Temple now meets that baseline.