Hello everyone. I want to begin by expressing my heartfelt gratitude to each and every one of you. Your dedication, passion, and unwavering support have been the driving force behind everything we’ve accomplished in the past.
As we stand on the edge of an exciting milestone—our mainnet rollout—we’re not just launching a network; we’re stepping into a new chapter for the multi-chain future. This is a moment of transformation, not only for TOKI but for the entire blockchain landscape.
Let’s take a moment to reflect on how far we’ve come—on the challenges we’ve overcome, the innovations we’ve built, and the relationships we’ve established. And as we look ahead, let’s envision the extraordinary possibilities we’ll create together in this next era.
Our ultimate vision is to empower billions globally through groundbreaking applications built on our infrastructure. The Internet of Blockchains isn’t just a concept—it’s a future where App-to-App, Mesh Interoperability becomes a common standard, mirroring the seamless connections of today’s Cosmos or the Internet.
This vision sets us apart from others like LayerZero, Wormhole, or Axelar, which follow the Hub-and-Spoke model.
App-to-App vs Hub-and-Spoke
Much like today’s Web2 giants, traditional interoperability protocols risk creating vendor lock-in, where control is concentrated in the hands of a few validators. This model undermines decentralization and opens the door to significant challenges.
Most traditional protocols rely on small validator sets—ranging from a handful to about 20 validators—and often depend on staking mechanisms. This approach either becomes prohibitively expensive or sacrifices security to remain cost-effective.
These validator sets are expected to monitor all state transitions across hundreds of thousands of blockchains—a task that’s simply unachievable. Over time, they will screen chains for their benefit or charge high fees to connect. Even worse, they are developing their proprietary protocols without a strong and open developer community, meaning they can control the code changes as validators and protocols want to and no one is sure if they can be compatible.
And of course, it can be a huge honey pot for the entire ecosystem.
Our approach brings totally different features.