How Does STONfi Handle Partial Liquidity Across Multiple Pools?
I used to just assume a swap hit one pool and that was the whole story, nothing more to it. Then I actually looked into what Omniston sends on-chain when you swap, and realized my order almost never touches just one place — it gets split before it even executes.
🧩 THE PART THAT ACTUALLY SURPRISED ME
- Every route is technically an array of "chunks," each one addressed to its own contract
- ne chunk might route through a STONfi pool, another through DeDust, another through TonCo
- All of it executes as a single confirmation on my end, even though it's several trades stitched together underneath
This isn't some fallback that only kicks in for big orders. It's how the whole system is actually built from the ground up.
📊 WHERE THIS ACTUALLY HITS A CEILING
Splitting a trade across pools doesn't create liquidity that isn't there. If nobody's provided depth for a specific pair anywhere in the connected graph, chunking across empty pools just doesn't help — no amount of clever routing fixes a hole that isn't there.
⚡ WHY ESCROW SWAPS EXIST FOR THAT EXACT GAP
STONfi own team has been honest that this was the real limit of pool-splitting alone. Their answer was a separate path — escrow swaps, tapping private liquidity from professional resolvers instead of relying only on public pools that might just be empty for that pair.
💭 MY HONEST TAKE
I stopped assuming a bigger trade automatically means worse execution. Chunking across STONfi, DeDust, and TonCo covers most of it, and escrow swaps quietly handle the cases where public liquidity genuinely isn't there yet. One request on my end, several moving pieces underneath.
Did you know your last swap might have quietly touched more than one pool at once?
Not investment advice — always research on your own!
$BTC
I used to just assume a swap hit one pool and that was the whole story, nothing more to it. Then I actually looked into what Omniston sends on-chain when you swap, and realized my order almost never touches just one place — it gets split before it even executes.
🧩 THE PART THAT ACTUALLY SURPRISED ME
- Every route is technically an array of "chunks," each one addressed to its own contract
- ne chunk might route through a STONfi pool, another through DeDust, another through TonCo
- All of it executes as a single confirmation on my end, even though it's several trades stitched together underneath
This isn't some fallback that only kicks in for big orders. It's how the whole system is actually built from the ground up.
📊 WHERE THIS ACTUALLY HITS A CEILING
Splitting a trade across pools doesn't create liquidity that isn't there. If nobody's provided depth for a specific pair anywhere in the connected graph, chunking across empty pools just doesn't help — no amount of clever routing fixes a hole that isn't there.
⚡ WHY ESCROW SWAPS EXIST FOR THAT EXACT GAP
STONfi own team has been honest that this was the real limit of pool-splitting alone. Their answer was a separate path — escrow swaps, tapping private liquidity from professional resolvers instead of relying only on public pools that might just be empty for that pair.
💭 MY HONEST TAKE
I stopped assuming a bigger trade automatically means worse execution. Chunking across STONfi, DeDust, and TonCo covers most of it, and escrow swaps quietly handle the cases where public liquidity genuinely isn't there yet. One request on my end, several moving pieces underneath.
Did you know your last swap might have quietly touched more than one pool at once?
Not investment advice — always research on your own!
$BTC