Have an asset on Kaspa and want to use it on another network?
That's what KatBridge is for.
Why would you need a bridge?
Imagine two different networks.
Each has its own transactions, wallets, and apps.
An asset on one network doesn't automatically show up on the other.
But what if you want to use that asset there too?
KatBridge helps connect the two.
How does it work?
Say Emma has tokens on Kaspa.
She wants to use them in an app on another network.
Instead of dealing with every technical step herself, she uses KatBridge.
1. Emma chooses her asset and destination network.
2. KatBridge coordinates the process between the two networks.
3. A matching representation of the asset becomes available to her on the destination network, where it can be used.
That's the basic idea of a bridge.
Does the asset actually jump between networks?
Not exactly.
The two networks are still separate.
The bridge handles the asset on the starting network according to the route's rules, and makes the corresponding representation available on the other network.
That lets an asset be used across networks without turning those networks into one.
What can KatBridge connect?
KatBridge has routes for supported assets. What's actually available depends on the asset and destination network:
KAS - Kaspa's native coin.
Tokens - other assets created on the network.
The available route depends on the asset and destination network you choose.
What does it have to do with Nacho?
KatBridge is part of the wider K.A.T. ecosystem, alongside Nacho and other projects.
They share a simple goal:
Build useful things around Kaspa.
KatBridge opens up more ways for assets connected to Kaspa to be used across networks, apps, and communities.
What about transparency?
KatBridge publishes documentation explaining its routes and the mechanisms behind them, along with information people can check.
A published security audit is also available for parts of the system operated by K.A.T.
It's not just about using a bridge. It's about being able to understand and examine how it works.
The main idea
KatBridge connects separate networks.
It provides routes that make it possible to use representations of assets on another network.
One more way builders around Kaspa are expanding what the ecosystem can do.