Studio Loco: Liquidity in motion. Create strategies, trade smarter, and ride the rails of the DLMM Locomotive.
BDrr8vBvEggLZNVsxYvYmR31YEEBCky71KZNHufJwoco
GM. It's day 3 of Studio Loco.
Three new upgrades are live in our Solana + Meteora DLMM toolkit:
🚂 The Replay Room
Replay real historical Meteora candles and watch liquidity rules respond, one candle at a time. Inspect rebalance proposals, compare modeled ranges and export the decisions. No wallet required.
🔎 Wallet Checks
Verify the network and rehearse the signing flow on devnet with no token transfer. Get familiar with the review, approval and confirmation process before committing capital.
🚦 Transaction safeguards
Changing wallets or networks invalidates stale approvals. Competing actions are blocked within the app, and unresolved signatures must be reconciled before fresh transactions proceed.
209 tests passing. Desktop and mobile verified. A funded devnet rehearsal confirmed.
We’re building liquidity management you can understand and control - from inspecting an agent’s proposal to approving its execution.
Inspect. Rehearse. Approve.
The Observatory keeps growing. 🌌
The train has arrived. The Observatory is LIVE on mainnet. 🚂🔭
Studio Loco brings active liquidity tools to Solana × Meteora DLMM: watch real positions, set rules for price moves and range exits, and review native rebalance proposals.
You define the strategy. Your wallet approves every move.
Six funded devnet cases passed. 27 confirmed transactions. 172 tests passing.
We’re building a control room for liquidity that moves with the market - and a world worth exploring while you do it.
The line is open. This is only the first stop.
Next for Studio Loco: funded-wallet testing, live native rebalance validation, then The Observatory’s public release.
Beyond that: richer rules, deeper LP analytics and persistent monitoring.
Agents propose. You approve.
Your capital. Your route.
Studio Loco’s new Liquidity Agents update is in.
We call it The Observatory: a rule engine for monitoring Meteora DLMM positions on Solana, turning changes in market conditions into proposals you can inspect, simulate and approve through your wallet.
The architecture is straightforward:
verified position data → explicit rules → proposal → fresh transaction build → exact-message simulation → wallet approval → confirmed receipt.
Here’s what happens underneath.
1/ Range management starts with the actual bins.
Arming a rule fetches a fresh on-chain baseline. Price-move thresholds stay anchored to that baseline rather than drifting with every poll. DLMM’s bin relationship is P₂/P₁ = (1 + binStep/10,000)^Δbin, so the engine can translate a percentage move into bin movement.
You can set edge buffers, leaving-range triggers, observed time out of range, partial-withdrawal thresholds and cooldowns. Supported plain-language commands become explicit, editable parameters: “prepare a 50% withdrawal after 15 minutes out of range,” for example. Ambiguous instructions are rejected.
2/ Risk checks use observed data.
Volatility is the standard deviation of close-to-close log returns from real mainnet OHLCV, using each position’s configured candle count and 5m or 1h interval. N returns require N+1 closes. Missing, stale, duplicate, future or gapped candles produce “unavailable.” Risk-reduction triggers take priority over rebalancing, including during their cooldown.
Monitoring currently runs every 30 seconds in the visible open tab. Pausing, hiding the tab or editing rules resets the observed out-of-range clock. A disconnected interval cannot quietly count towards your 15-minute trigger.
3/ Capital comparisons respect what you actually own.
The Observatory reads raw token holdings by bin and separates active-bin liquidity from the rest of your range. Those other bins provide intentional coverage.
Alternative pools must share the exact token mints, including reversed X/Y orientation. TVL, volume, fee/TVL and bin step support comparison; historical fees are not forecasts. A staged move verifies destination mints and discloses its range before withdrawal. Withdraw → fresh add remains non-atomic, with separate approvals.
4/ Execution is a tightly bound review.
A review freezes the rule revision, wallet, network, RPC, position, target and slippage for 20 seconds. The guard runs before and after wallet approval. Single-flight jobs track timed-out SDK/RPC work until it settles, preventing overlap with a newer build. Unknown balances or costs, failed simulation, and unresolved signatures block further actions; pending settlement survives reloads.
Fees come from the exact transaction message. Upfront account rent is accounted for without double-counting fees or treating withdrawn WSOL as wallet-funded rent. Existing WSOL accounts stay intact. Native rebalance checks require zero net wallet input and show gross redeposit separately.
The SDK’s native rebalance path is wired, but live validation is still outstanding: even-width ranges that gain an extra bin are rejected, and the odd-width mainnet build timed out. Agents also blocks percentage withdrawals needing multiple transactions.
Validation so far: 165 passing tests, clean TypeScript and production build, plus a successful unsigned mainnet 25% withdrawal simulation: 751 bytes, 297,759 compute units, a 5,000-lamport network fee. No funds moved.
This is the preview update. Funded execution acceptance and publication remain ahead. Today’s agents are deterministic, operate in-tab and require wallet approval; volatility checks do not predict price or eliminate impermanent loss.
Adaptive liquidity workflows, with rules you can understand and transactions you can verify.
Your capital. Your route.
We’ve almost completed this whole stack - head down all day. We’ve encountered some interesting twists in terms of directions we could take things.
Update OTW!
solana:BDrr8vBvEggLZNVsxYvYmR31YEEBCky71KZNHufJwoco
Gm.
Day 2 and we're kicking things off as we arrive at our at out first station.
Agentic-managed liquidity pools are the promise: positions that watch the market so you don't have to.
In DeFi's short but transformative history, liquidity has always been king. The depth and stability of markets rely directly on liquidity provision, traditionally done by individuals or institutions manually adjusting their positions. But manual management has limitations - inefficient, error-prone, and often slow to respond to fast-moving markets. The next frontier, already emerging in pockets of crypto, is turning liquidity pools into fully autonomous, AI-driven systems that manage themselves, adapt intelligently, and evolve in real-time.
Studio Loco's latest update steps toward that honestly: exit thresholds that flag a position the moment it drifts out of range, and a Fee Weather attention score that ranks pools by live activity.
No auto-signing, no custody... the signal finds you, you keep the keys. 🚂
Live now.
https://t.co/TTqddGjrmP
Next on Studio Loco’s roadmap: liquidity agents that work around your strategy. 🚂
Building on Dispatch, we’re planning to bring agent-assisted management to Meteora DLMM positions:
• Range rules: monitor price movement and propose rebalancing when your chosen thresholds are reached.
• Capital checks: identify liquidity outside the active range and compare redeployment options, accounting for costs and risk.
• Risk alerts: flag changing conditions and propose reducing exposure or withdrawing when your limits are hit.
• Plain-language setup: “Review my range after a 5% price move” becomes explicit settings you can inspect and edit.
The workflow: monitor → propose → simulate → wallet approval.
Each proposal should explain why it was triggered, what changes and what it costs. Moving capital more often isn’t the goal; making informed decisions with less manual monitoring is.
Your capital. Your route.
Gm.
Day 2 and we're kicking things off as we arrive at our at out first station.
Agentic-managed liquidity pools are the promise: positions that watch the market so you don't have to.
In DeFi's short but transformative history, liquidity has always been king. The depth and stability of markets rely directly on liquidity provision, traditionally done by individuals or institutions manually adjusting their positions. But manual management has limitations - inefficient, error-prone, and often slow to respond to fast-moving markets. The next frontier, already emerging in pockets of crypto, is turning liquidity pools into fully autonomous, AI-driven systems that manage themselves, adapt intelligently, and evolve in real-time.
Studio Loco's latest update steps toward that honestly: exit thresholds that flag a position the moment it drifts out of range, and a Fee Weather attention score that ranks pools by live activity.
No auto-signing, no custody... the signal finds you, you keep the keys. 🚂
Live now.
https://t.co/TTqddGjrmP
Analyzing this
Phantom dev follows
In one of my private groups the guy told me they are a Meteora Hackathon project however i don’t see proof yet? @StudioLocoDBC
BDrr8vBvEggLZNVsxYvYmR31YEEBCky71KZNHufJwoco
🌍 https://t.co/3uBDyjB6eV 🔍
Studio Loco: Liquidity in motion. Create strategies, trade smarter, and ride the rails of the DLMM Locomotive.
https://t.co/MIdeTAxWjt
DLMM Pro is coming
The culmination of all @MeteoraAG’s hard work, consolidating everything they’ve built into a single platform.
The most powerful AMM on Solana
This is a clip from when I first started teaching @doinksOG to LP on @MeteoraAG
Since then, he has aggressively run up a 5 sol port to over 20 sol in less than a month.
If you are getting rinsed trying to trade new pairs and tokens spot, you NEED to open your first LP.
You will learn very quickly how much safer it is to profit on Meteora DLMMs
FOMO has taken the industry by storm, but it is necessary for your growth to learn how to become the Market Maker and earn yield on memecoins.
A huge fairness shaped void is about to be filled.
Bots along flatlined liquidity & fees have created an ugly home over at @Pumpfun and their ecosystem.
Study what @MeteoraAG is doing with their new DLMM pro and you’ll soon release how early you are if you decide to act NOW.
Day 2 of $LOCO is about to get crazy, what we dare to experiment with TODAY will be the new normal tomorrow.
Let that sink in.
Dispatch is one of the few arbitrage implementations I’ve seen that treats user approval and atomic execution as non-negotiable design constraints rather than optional features.
That alone puts it in a different category from most of what’s currently deployed.
@StudioLocoDBC