top of page
Tanssi_Logo - White - 1300x400.png
  • Tanssi Network - Community Channel_X Twitter
  • Tanssi Network - Community Channel_Telegram
  • Tanssi Network - Community Channel_Discord
  • Tanssi Network - Community Channel_GitHub
  • Tanssi Network - Community Channel_YouTube
  • Tanssi Network - Community Channel_LinkedIn

Canopy Network Acquires Tanssi’s Core Appchain-as-a-Service Technology

The technology behind Tanssi finds its next chapter.



Today we’re sharing that Canopy Network has acquired core intellectual property and the technology developed by the core contributors of Tanssi. The transaction covers the infrastructure at the heart of what we built: the Tanssi dApp for appchain deployment and management, our sequencer-assignment and block-production orchestration logic, and our trust-minimized Snowbridge-based Ethereum bridge.

This isn’t an ending for the technology, it’s a continuation in the hands of a team that wants to scale it.


What we set out to build

When we began Tanssi, the premise was straightforward. Launching a sovereign blockchain was slow, expensive, and was effectively reserved for teams with deep protocol expertise. We wanted to dramatically improve the developer experience around that process - to make spinning up a secure, sovereign and customizable appchain take minutes rather than months, without asking builders to give up control of their own network.


Delivering on that meant solving infrastructure problems that don’t have shortcuts: a deployment experience clean enough that launching a chain feels like shipping software, orchestration that assigns and manages block production reliably across many chains at once, and a dependable bridge connecting that ecosystem to Ethereum.


What Canopy is Acquiring

Three pieces of technology sit at the core of this transfer. Each one solved a distinct problem.


The Deployment dApp

The Tanssi dApp was the front door to the whole system - the console that let any team launch and run a sovereign appchain in minutes instead of months. From a single interface, builders could register and configure a new chain, fund and pay for its block-production services, manage tokens and on-chain governance, and bring a network live without ever touching the low-level plumbing: validators, economic security, sequencers, RPC endpoints, block explorers, indexers or wallets. If the rest of the stack was the engine, the dApp was the cockpit - the layer that made “launch a chain” feel like shipping software rather than standing up infrastructure.


Sequencer Selection and Block-Production Orchestration

Underneath that simplicity sat the hardest part of the system. Tanssi ran a decentralized, permissionless pool of sequencers - the nodes that produce blocks - and orchestrated them across many appchains at once. Think of it as a Kubernetes for block production: the protocol selected sequencers from the pool by stake (alongside a prioritized set that kept production stable), shuffled them, and assigned a subset to each active chain for a fixed session before rotating and reassigning them on a rolling basis. Assignments were computed a session ahead, so incoming sequencers could pre-sync the chain they were about to serve; the protocol tracked exactly which sequencers were authorized to produce blocks for which chain, verified authorship, and rewarded accordingly. The result was the thing that is genuinely hard to build: reliable, censorship-resistant, fairly distributed block production across a fleet of sovereign chains, with liveness guaranteed by design rather than by any single operator.


The Trust-Minimized Ethereum Bridge

Finally, the bridge - our Snowbridge-based connection between the Tanssi ecosystem and Ethereum. It was built to be trust-minimized in the strict sense: each chain runs an onchain light client of the other, with no multisig and no custodian standing in between. Tanssi used BEEFY consensus which produced compact proofs that an Ethereum-side client could verify, and Ethereum’s beacon-chain light client did the same in reverse; relayers only carried proofs and could never forge a message or move funds on their own. Beyond moving assets and liquidity in and out of Ethereum, the bridge carried the rewards for validators, stakers, and slashing messages that underpinned the appchains’ Ethereum-grade, restaked security. It was, in short, the connective tissue between a sovereign appchain ecosystem and the largest settlement layer in crypto.


Why Canopy

Canopy Network is building a framework for launching sovereign Layer-1 appchains with shared security: a root chain secured by validators, with new chains inheriting that same security as validators restake to extend it. It is the same problem space we spent years inside — many sovereign chains, each needing reliable block production, straightforward deployment, and connectivity beyond their own borders — and the technology we built maps almost one-to-one onto how Canopy’s model works.

It also matters who is carrying it forward. Canopy’s team are crypto natives: they are core contributors to Pocket Network, one of the earliest decentralized infrastructure (DePIN) networks, which at its peak served over a billion data relays a day. Co-founder and CEO Adam Liposky helped scale Pocket Network into a top-200 project by market cap; co-founder and CTO Andrew Nguyen authored much of its original protocol. These are web3 contributors who have built, shipped, and operated decentralized infrastructure at scale.


What this means

This is a transfer of intellectual property and technology. Canopy will speak to its own roadmap and how it intends to integrate and develop what it has acquired - for that, follow Canopy Network directly on their channels .


The standalone Tanssi network and its operations are expected to be phased out throughout the next 30 days - a separate announcement will be published shortly by the Foundation regarding what actions to take.


To the engineers who built this, the developers who deployed on Tanssi, and the community that backed us along the way: thank you. 


Follow what's next at Canopy

Tanssi's chapter is closing, but the technology's story continues, and Canopy is where it gets written from here. If you want to see where this work goes next, follow Canopy Network directly and join their community:


They'll speak to their own roadmap, releases, and how the acquired technology gets put to work. Please follow their channels to be in the loop for what comes next.

 
 
 

Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
bottom of page