Yes. Meet Storm V3.
Two years ago, we started working toward a pretty simple idea: trading on a DEX shouldn't mean constantly switching between the terminal, your wallet, and yet another transaction.
Open a position β sign.
Set a stop β sign.
Add a take profit β you get the idea.
For swapping tokens once a day, that's manageable. For an actual trading terminal, where the price can move while you're still dealing with wallet pop-ups β not so much.
That idea became Storm V3.
We removed unnecessary steps from the trading flow while keeping the one thing DEXs were built for in the first place:
You stay in control of your funds. Trades execute at CEX-like speed.
Because V2 wasn't limited by a slow interface. It was limited by the execution architecture itself.
One important detail: V2 didn't need to wait for a new block to get an oracle price. The bottleneck happened earlier β before an order could be executed, it first had to appear on-chain.
The flow looked roughly like this:
action β wallet signature β order goes on-chain β execution
You can optimize the interface around that flow as much as you want, but the underlying constraint stays the same: every new action has to go through the chain first.
For active trading, that was the ceiling of V2.
With V3, we didn't remove the blockchain. We removed the need for every trading action to hit the blockchain before execution could begin.
Doing that required us to rethink several core parts of the protocol.
Let's start with the change you'll notice first.
V3 introduces Quick Wallet β a personal smart account linked to your primary TON wallet.
And no, it's not another wallet you have to hand control over to. When you connect for the first time, Storm creates a separate trading key for that specific device. Your primary wallet authorizes it once to perform trading actions.
From there, things get much simpler:
connect wallet β deposit β trade
Going Long no longer opens your primary wallet.
Going Short doesn't either.
Neither do Limit orders, Stop Loss, or Take Profit.
You click a button in the terminal, your trading key signs the action inside Storm, and the order is sent for execution.
You can also open a position together with attached Stop Loss and Take Profit orders in a single action.
No more:
open position β confirm β go back β set stop β confirm β go back β set take profit β confirm again
But getting rid of wallet pop-ups isn't even the most important part of Quick Wallet.
There's something much more important underneath.
In V2, your primary wallet authorized both trading actions and operations involving your funds. In V3, those permissions are separated.
A trading key on a specific device can:
β open and modify positions;
β create and cancel orders;
β manage Stop Loss and Take Profit.
But there is one thing it cannot do: withdraw your funds.
Withdrawal rights remain exclusively with your primary wallet.
The primary wallet also handles deposits, connects new devices, revokes trading keys, and terminates other sessions. Withdrawals always go back to its address β neither a trading session nor the execution layer can replace the recipient.
This is where V3 gets really interesting:
Storm gets permission to execute an authorized trade. It does not get permission to control your assets.
Your funds are never handed over to an exchange for custody. They remain on-chain, while withdrawal rights are enforced by a public smart contract.
Faster trading β giving up control of your funds.
That's fundamental to how we built V3.
Lost your phone? Revoke its trading key. Your account, collateral, and other sessions remain untouched.
A single account can support up to 255 trading keys, so your phone, desktop, and other devices can operate independently.
Now let's go one layer deeper.
In V3, trading actions are represented as signed instructions called intents.
Sounds technical. The idea itself is pretty straightforward.
Say Bob wants to open a $100 BTC long with 15x leverage. For the protocol, that becomes an instruction. Each instruction contains specific parameters: market, direction, size, leverage, price, orders, and expiration.
The trading key signs that exact instruction.
Not a blanket authorization to control the account.
Not \"wallet access.\"
One specific action with specific parameters.
Once signed, those parameters cannot be changed. Change even one of them and the signature is no longer valid.
And this is the key difference from the old model:
An intent does not have to appear on-chain before Storm can start executing it.
That one change reshapes almost the entire trading flow.
Storm already had a Sequencer in V2. In V3, its role becomes much bigger.
It is now a full execution layer.
It receives user intents, validates the signature, trading key, and replay protection, places them into the execution queue, accounts for market risk parameters and the latest oracle price, and then executes the order.
It also protects the queue against MEV.
Tracks settlement results.
And handles errors and rollbacks.
Strip away the technical details, and the new order flow looks roughly like this:
your instruction β permission checks β queue β price & risk β execution β on-chain record β finalization
And this is the architecture V3 was built around.
Off-chain handles execution speed.
On-chain handles recording and finalization.
You keep control of your funds.
We didn't choose one over the other.
We separated responsibilities so each layer could do what it does best.
The new execution model comes with another very practical benefit. Pending orders in V3 exist as signed instructions.
That means creating, modifying, or cancelling Limit orders, Stop Loss, and Take Profit no longer requires a separate on-chain transaction.
You can finally manage risk as often as the market demands instead of asking yourself every time whether changing an order is even worth the transaction.
There is one important technical caveat, though.
Gas for actual order execution still applies.
When an order is triggered and the result needs to be recorded on-chain, the corresponding network fee is still there.
We didn't rewrite the laws of blockchain physics. We just stopped dragging them into every single position adjustment.
V2: action β wallet β signature β order on-chain β execution
V3: action β execution
Of course, there's a lot more happening under the hood.
But this is one of those rare cases where the protocol became more complex so the product could become simpler.
V2 | V3 | |
|---|---|---|
Account model | Wallet + separate transactions | Personal smart account |
Trading actions | Signed by the primary wallet | Signed by a trading key |
New order | Must appear on-chain before execution | Sent to the Sequencer as an intent |
Entry + SL + TP | Multiple separate confirmations | One action |
Limit / SL / TP | Changes require on-chain actions | Create, modify, and cancel without separate gas fees |
Gas on execution | Yes | Yes |
Trading & withdrawals | Same permission layer | Permissions are separated |
Multiple devices | Requires reconnecting | Up to 255 independent trading keys |
Fund custody | On-chain | On-chain |
Settlement | On-chain | On-chain |
Execution speed | Limited by the order's on-chain path | CEX-like |
So no β V3 isn't simply a faster version of V2.
We didn't make the old road faster. We built a new one.
There's still one obvious piece of blockchain mechanics that users have to deal with more than we'd like.
Deposits.
Right now, before you can start trading on Storm, your assets first need to make their way to TON.
The next step is funding Storm directly from other networks.
We're working toward a unified flow that will let users fund their smart account with assets from other chains without having to manually figure out the route themselves.
It's the natural continuation of V3.
And the direction for Storm is now pretty simple:
remove everything from the trader's path that exists only because "that's how blockchain works" β unless it gives them more control or security.
Two years ago, the goal sounded pretty modest: get rid of constant wallet confirmations.
It turned out that doing that properly meant rebuilding the account model, separating permissions, moving to intents, and fundamentally changing the execution layer.
Now, trades no longer have to wait for an on-chain transaction before execution can begin.
β Limit orders, SL, and TP can be adjusted without paying a separate fee for every change.
β A trading key can trade β but it can never withdraw your funds.
β Final settlement remains on-chain.
β You remain in control of your funds.
Today, we're building a product where you don't have to think about the blockchain at all β until you need it to protect what belongs to you.
π₯ We've cut trading fees in half. Open Storm, enable Quick Wallet, fund your account, and make one trade β that's all it takes to feel the difference.
For those who want to dive deeper into the technical side β check out our documentation.
Got questions? Ask them in ourΒ vibrant community.
And if youβre already a proud owner of Market Makers NFTs, joinΒ our private chatΒ for exclusive discussions.
WebsiteΒ |Β NewsΒ |Β XΒ |Β Docs

