How many times have you watched a crypto position go red because you stepped away from the screen for an hour?
That question sits at the center of one of DeFi's most persistent problems. Centralized exchanges have had stop-loss and take-profit orders for years. Binance has them. Coinbase has them. Every retail brokerage in traditional finance has them. Decentralized exchanges, where you actually control your own assets, largely do not. Until now, on Berachain, they do.
https://x.com/orbs_network/status/2031382432784482683?embedable=true
On March 10, 2026, Orbs announced that Kodiak Finance has integrated its dSLTP protocol, making Kodiak the first decentralized exchange on Berachain to offer fully onchain stop-loss and take-profit execution. The integration runs without centralized servers or off-chain executors, meaning execution stays inside the decentralized infrastructure rather than routing through a third party.
What Stop-Loss and Take-Profit Actually Mean, And Why DeFi Has Struggled With Them
Before getting into the architecture, it is worth being precise about what these order types do, because the gap they fill is significant.
A stop-loss order automatically sells a token when its price falls below a level you set. If you bought an asset at $100 and you do not want to lose more than 10%, you set a stop-loss at $90. The moment the price hits $90, the order executes and you exit the position. You do not need to be watching. You do not need a bot running on a server you control. The instruction is set and the system executes it.
A take-profit order works in reverse. If you want to lock in gains at $130, you set the instruction and the order triggers automatically when the price reaches your target. Used together, these two tools define a risk and reward boundary around any trade. They are standard in every traditional financial market for a reason: markets move when traders are asleep, distracted, or simply unable to watch.
In DeFi, replicating this has been technically difficult because most smart contracts on base-layer blockchains cannot independently monitor price conditions and trigger delayed execution. The logic required is more complex than what a standard smart contract handles natively. As a result, most DEX users have either accepted the limitation or moved positions to centralized exchanges when they wanted risk management tools, which defeats the purpose of self-custody.
How Orbs Built the Infrastructure to Make It Work
Orbs is a Layer-3 blockchain built specifically for advanced onchain trading. The distinction matters. A Layer-1 is the base chain. A Layer-2 sits on top and handles scaling. A Layer-3, in Orbs' architecture, is a supplementary execution layer that sits above the smart contract environment and handles logic that base-layer contracts cannot run natively.
Think of it this way. A standard smart contract is like a vending machine: it accepts inputs, follows pre-set rules, and delivers outputs. It cannot watch the market and decide to act. Orbs' Layer-3 infrastructure acts as a scheduler sitting above that vending machine, monitoring conditions and triggering the machine when the conditions you defined are met. The execution still happens onchain. The intelligence behind the timing runs through Orbs' decentralized Proof-of-Stake network.
dSLTP is the third major protocol in Orbs' trading suite. dLIMIT, released earlier, allows traders to set limit orders on DEXs. dTWAP enables time-weighted average price execution, which splits large orders into smaller pieces over time to reduce price impact. dSLTP completes the basic risk management toolkit: stop-market orders that execute immediately when a trigger price is hit, and stop-limit orders that execute only at or above a defined minimum price, protecting against slippage in fast-moving markets.
The protocol is fully permissionless. Any DEX can integrate it without relying on Orbs as a centralized executor. The execution logic runs through Orbs' validator network, not through a company-controlled server. That is the design distinction that separates dSLTP from centralized solutions that simply move the custody problem to a different intermediary.
Ran Hammer, VP of Business Development at Orbs, said:
"Kodiak's integration of dSLTP reflects growing demand for advanced risk management tools for onchain traders. Bringing decentralized stop-order automation to Berachain means that traders can access the same powerful execution tools they expect from centralized platforms, while preserving the transparency and self-custody benefits of DeFi."
Why Berachain and Why Kodiak
Berachain is a Layer-1 blockchain built around a consensus mechanism called Proof-of-Liquidity, which ties block validation to liquidity provision rather than pure token staking. At its peak in early 2025, Berachain's TVL reached $3.5 billion within weeks of mainnet launch, briefly surpassing both Arbitrum and Base. The network has since stabilized at lower figures as incentive programs wound down and the broader market shifted.
Kodiak is Berachain's native liquidity platform. At its height, Kodiak held over $1.12 billion in TVL on Berachain, making it the second-largest protocol on the network. It had previously integrated Orbs' dTWAP and dLIMIT protocols, and the dSLTP integration now completes that suite on a single platform. Kodiak is also the first DEX on Berachain to deploy all three Orbs protocols together.
https://x.com/OrderlyNetwork/status/2031356917436789013?embedable=true
The sequencing matters. Kodiak is not experimenting with Orbs. It has now committed to the full trading infrastructure stack, which signals a different kind of relationship than a one-off integration. For Berachain, which has worked to rebuild activity after the TVL contraction of mid-2025, having a DEX that offers institutional-grade execution logic is a credible differentiator. The networks that are gaining ground in DeFi are not doing so on token economics alone. Infrastructure quality is what retains active traders.
The Broader Significance: DeFi Closing the CeFi Gap
The integration reflects a trend that has been building in decentralized finance for the past two years. Over the past two years, DeFi developers have steadily introduced execution layers designed to support sophisticated trading behavior, from algorithmic strategies to advanced order routing. The question driving that development is whether DEXs can match the functionality of centralized platforms without sacrificing the properties that make decentralization valuable: self-custody, transparency, and permissionless access.
Stop-loss and take-profit orders are not exotic features. They are basic tools in any active trader's workflow. The fact that they have been absent from most DEX environments has been a genuine barrier to adoption among traders who manage risk seriously. Moving a position from a DEX to a CEX to use a stop-loss order means giving up custody of assets, trusting a centralized entity with execution, and accepting the counterparty risk that comes with that. That is a real cost that many traders have quietly absorbed because there was no alternative.
dSLTP makes these capabilities available in a fully decentralized form, allowing trades to automatically execute when predefined price conditions are met. The protocol supports trigger price, optional limit price, expiry, and customizable execution settings. That parameter set is comparable to what centralized platforms offer, with the addition of full onchain transparency and no custodial dependency.
Final Thoughts
The Kodiak and Orbs integration is not a headline event for its novelty. It is significant because it is the right infrastructure addition at the right point in DeFi's development. The networks and exchanges that are going to retain serious traders are the ones that make active risk management possible without routing through centralized infrastructure.
Berachain has had liquidity. What it has needed is depth in execution tooling. Kodiak now has that, and it arrived at a moment when the competition between DEX ecosystems is increasingly about infrastructure quality rather than incentive programs. If the adoption curve follows, this will be the kind of integration that looks obvious in retrospect.
Don’t forget to like and share the story!