Moving Assets On Stacks Blockchain
Stacks is building Bitcoin-native finance. DeFi, stablecoins, payments, lending, trading, and financial applications are all creating new reasons for users to hold and use assets on Stacks.
But there is a problem that sits underneath all of this growth:
The liquidity users need is already distributed across the rest of the crypto ecosystem.
A user may have ETH on Ethereum.
Another has USDC on Base.
Another has SOL on Solana.
Another has BTC.
Another has USDT on Arbitrum.
They may want to use that capital on Stacks.
The question is:
How easily can they get there?
That is the problem we started Hermes Bridge to solve.
The idea is straightforward:
Take assets from where users already have them and make them usable in the Stacks ecosystem.
The liquidity is already there
We don’t believe the answer is asking users to abandon the ecosystems where they already hold their assets.
Ethereum has enormous liquidity.
Base is growing rapidly.
Solana has massive activity.
Bitcoin is the world’s most established crypto asset.
Stablecoins are spread across virtually every major chain.
The opportunity for Stacks is to make that liquidity accessible to the applications and users building on Stacks.
Imagine:
You have 500 USDC on Base and want STX.
You shouldn’t need to figure out a complicated route yourself.
You should be able to open Hermes, select:
From: Base
Asset: USDC
To: Stacks
Receive: STX
Review the amount you’ll receive, the fees, provide your Stacks address, and bridge.
That’s the experience we are building.
What Hermes is becoming
HermesBridge started with a focused goal around bringing USDC liquidity into Stacks.
That first version proved an important point:
There is a real need for a simple gateway between external liquidity and Stacks.
But USDC is only one part of the opportunity.
The larger vision is:
Bitcoin
│
Ethereum
│
Base
│
Solana
│
Avalanche
│
▼
┌─────────────┐
│ HERMES │
│ │
│ Send / │
│ Receive │
└──────┬──────┘
│
▼
STACKS
│
┌─────┼─────┐
▼ ▼ ▼
sBTC STX USDCx
│
▼
Stacks DeFi
And the assets moving through that gateway can be very different.
BTC → sBTC
ETH → STX
SOL → STX
USDC → USDCx
USDC → STX
USDT → USDA
ETH → USDCx
BTC → STX
...
The destination is not limited to one token.The destination is the Stacks ecosystem.
The experience we are building
One of the biggest things we learned from building v1 is that the bridge should explain itself while it works. If someone sends funds, they shouldn’t stare at a spinner wondering what happened.
Hermes is designed around a clear transaction journey.
For example:
1. Quote
100 USDC↓Estimated receive: 98.XX STX
The user sees the expected amount and applicable fees before committing.
2. Send
The user sends the requested asset to the Hermes deposit address.
3. Verification
Hermes detects and independently verifies the blockchain transaction.
4. Processing
The bridge prepares the corresponding destination transaction.
5. Settlement
The destination transaction is broadcast and monitored.
6. Completion
Hermes independently verifies that the recipient received the correct asset. The user gets a transaction ID they can use to follow the entire operation.
The objective is simple:
At every point, the user should know what happened, what is happening, and what happens next.
Security doesn’t disappear behind the UX
The interface may look simple. The infrastructure underneath is deliberately not. Hermes treats every bridge operation as an independent transaction with its own identity and lifecycle.
A user sending 100 USDC today and another user sending 100 USDC tomorrow are not identified by the amount.
They are identified by their actual blockchain transactions.
This allows Hermes to defend against problems such as:
-
replayed transactions
-
duplicate processing
-
incorrect recipients
-
insufficient confirmations
-
blockchain reorganizations
-
duplicate bridge requests
-
payout mismatches
-
ambiguous transaction states
And the system is designed so that seeing a transaction hash is not enough to declare a bridge complete. The destination must be independently verified.
That is particularly important as Hermes expands into higher-value and more diverse cross-chain transfers.
Hermes is also becoming infrastructure for developers
The end-user application is only one part of the vision.
Hermes is being built with APIs that allow other applications to interact with the bridge programmatically.
A wallet could integrate Hermes.
A Stacks DeFi application could integrate Hermes.
A payment application could integrate Hermes.
A trading interface could use Hermes as its cross-chain liquidity layer.
Instead of sending users away to another website, an application could eventually provide:
Send USDC from Base → receive STX on Stacks
directly inside its own experience.
That’s when a bridge starts becoming infrastructure rather than simply a website.
The long-term vision
We see Hermes as a liquidity gateway for Stacks.
Not a place where users go because they have to bridge but Infrastructure that applications can depend on because liquidity needs to move.
The direction looks something like this:
BITCOIN
│
┌───────────┼───────────┐
│ │ │
Ethereum Base Solana
│ │ │
Arbitrum Avalanche Other Chains
│ │ │
└───────────┼───────────┘
│
▼
HERMES BRIDGE
│
┌─────────┼─────────┐
│ │ │
sBTC STX USDCx
│ │ │
USDA USDh ZEST
│ │ │
└─────────┼─────────┘
│
▼
STACKS ECOSYSTEM
The goal is to make the boundary between chains feel much smaller.
A user doesn’t care which infrastructure sits underneath the transaction.
They care that:
their asset arrives where they need it, in the form they need it, with a clear price and a clear transaction status.
Why this matters for Stacks
The future of Stacks shouldn’t depend on users already holding STX or USDCx.
The ecosystem can be much bigger than that. A user should be able to arrive with capital from wherever they already participate. An application should be able to reach users wherever their liquidity currently lives.
And a developer building on Stacks should be able to think about what their application does not how every user is going to acquire the assets required to use it. That’s the opportunity.
Bring the liquidity to the applications.
Bring the users to Stacks.
Make the movement of capital feel native.
That’s what we’re building with Hermes.
Hermes V1 is live today on CTTP and xReserve, and v2 is being built toward a much larger vision:
A simple, secure liquidity gateway connecting the world’s major blockchain ecosystems with Stacks.
Live:
X:
Hermes Bridge — Moving Assets On Stacks Blockchain.