Skip to content

DOC · Timetable

How the line works.

Agents

The Depot · useful agents and optional token launches

The Depot at /app/depot starts with a Scout: a real mainnet DLMM pool report with exact probe amounts, observed liquidity, fees, gaps and read contexts. Optional AI commentary references deterministic facts and remains qualitative. An agent can publish reports without launching a token. Reports run on request; this release has no autonomous hosted financial agent.

Connect a Solana wallet and sign a short, expiring message to open its private Depot workspace. No email or password is required. Wallet sessions last up to twelve hours; disconnecting hides the workspace. Each agent then needs a separate single-use proof bound to the domain, agent and controller purpose. Publishing the passport is explicit and exposes its wallet and whitelisted launch identity. Choosing public reports exposes the agent's retained report history. Wallet sign-in does not automatically bind an agent or approve a financial transaction.

Token metadata and PNG/JPEG/WebP images are immutable, hash-addressed public content served from studioloco.cfd. Each publication is atomic and agent-specific, limited to twenty versions per hour and one hundred permanent versions per account. A draft may select an earlier version; published content remains resolvable even after deleting the draft. Launch preparation verifies the exact public metadata bytes, so the source must be deployed on the metadata domain first.

Two versioned standard-SPL/SOL presets build one atomic Meteora DBC config and token/pool transaction with no initial buy. DBC graduates to DAMM v2. The review discloses supply, allocation, permanent LP lock, owner recipients, trading fee split, network fee, upfront account funding and SOL caps. The protocol takes twenty percent of DBC trading fees; these presets assign the remaining share to the creator. The separate 0.2% protocol liquidity migration charge reduces migrated deposits. Fees depend on real trading activity and are not guaranteed operating revenue.

Every launch, graduation, curve fee claim, DAMM position fee claim and optional SOL operating-reserve transfer uses the shared wallet runner. Twenty-second reviews bind wallet, network, connection generation, agent revision, metadata, recipients, costs and operation intent. Simulation and cost checks run before signing and again after approval. Existing WSOL accounts are preserved; claimed SOL-denominated fees remain WSOL. Reserve transfers are separate SOL actions and do not prove that the agent controls or automatically spends the destination wallet.

A durable device ledger saves signature, message digest and launch metadata intent before broadcast. Unknown results block another operation; Check status never resends. Release applies only to an unsigned reservation. A confirmed launch is attached to its passport only after server reconstruction of the exact original transaction and independent pool/config/mint identity checks. Flight Recorder captures the review and wallet timeline. Financial records require working device storage.

Holder-only reports require wallet sign-in, a recent viewer-wallet proof and a fresh confirmed server SPL balance meeting the raw-unit threshold. The report query rechecks current passport visibility, policy and revision atomically after the balance read. Changing the connected wallet clears protected browser content and drops late responses. Wallet-funded launch, graduation, claims and real-holder browser acceptance remain pending; unsigned mainnet launch simulation has passed. The public SDK and MCP remain read-only and do not expose Depot private reports or launch execution.

Observatory

The Journey · follow a strategy after confirmation

The Journey at /app/journey tracks confirmed Foundry accounts or explicitly entered public positions and native orders. Confirmed local runner receipts are candidates, not proof: the chain transaction must bind the expected signer, writable target and exact DLMM pool; successful metadata and a fresh verified account are required. The saved blueprint revision and SHA-256 digest identify local configuration, not onchain strategy metadata. Imports and cloud claims cannot automatically link a Foundry origin.

Each mainnet read checks genesis, DLMM program/discriminators, pool/owner binding, initialized token mints and decimals. The SDK derives holdings and fees across several confirmed RPC reads; a final account byte check corroborates identity. Identity and corroboration slots disclose that window. These are not atomic same-slot holdings. Token amounts retain integer base-unit precision; fractional LP pro-rata values are floored. Mint extensions are observed only, not executed by Journey.

LP views show X/Y holdings, per-bin liquidity shares, active bin and range health, current unclaimed fees and account-lifetime claimed counters. Order views distinguish deposited input, resting input, fulfilled input, swapped output and current withdrawable holdings. Current order fees are unclaimed; lifetime claimed counters are unavailable. Removed/reset levels are an observed account change, not proof of cancellation. An absent account is unavailable, never presumed filled or closed.

A first snapshot starts the observed timeline. Later changes occurred between two successful reads; exact fill times and missed transitions are unknown. Selected accounts refresh every 60 seconds while the page is visible; evidence is stale after 150 seconds or any failed read. Device IndexedDB stores up to 100 accounts, 48 recent snapshots and 200 changes per account with truncation counts, strict validation and concurrent-write protection. Export retains this bounded evidence; there is no import-to-execution path.

Accounting separates the fees of independently verified, deduplicated linked Foundry transactions from current account SOL and its rent minimum. Other transaction fees, bin-array rent, funding and close refunds are not included. Rent recovery requires an eligible account closure and recipient verification. Counters can predate the Journey; token changes and collected fees are not investment performance or PnL.

Sign in to Signal Box to enable hosted LP range or native order-level alerts. Server reads reverify identities; watches are private, checked every five minutes and expire after seven days within the five-watch account cap. Read errors, pause/resume and observation gaps reset order continuity. Alert handoffs reload the current private watch and then require a fresh chain read. Rebalance Planner and pool order controls remain separate wallet-reviewed actions. Journey has no signer or background trading keeper; DLMM Pro stays gated.

Observatory

Strategy Foundry · versioned liquidity blueprints

Verify an ordinary mainnet DLMM pool in /app/foundry. Shape X/Y budgets across up to 69 bins using a preset or custom basis-point weights; add up to 12 buy levels below active and sell levels above active. LP and ladder budgets are separate capital with separate approvals. A level is a native resting order, not a simulated fill.

Save an immutable device revision before execution. Export JSON contains only exact pool/mint identity, bin step, public strategy configuration and action guards; no wallet, RPC credentials or transaction. Imports create a local copy and grant no signing permission. SHA-256 identifies configuration, not authenticity. Concurrent stale-parent saves are refused.

Each action loads fresh genesis, pool program/discriminator, mints, activation clock, fee settings and order eligibility. Current fee ceilings are pool-selection guards, not deposit charges or forecasts. Native instructions compose one atomic transaction, and simulation verifies position bounds or order levels, side and raw amounts. Network fee, token balances, wrapping and upfront rent must be known and affordable. Existing WSOL is preserved.

Wallet reviews expire after 20 seconds, starting after preparation and Recorder persistence. Edits, wallet/connection changes, unresolved signatures and pool changes invalidate approval. The shared runner simulates, obtains explicit wallet approval and reports confirmation. Recorder links the blueprint digest/revision to reviews, signatures and separately verified wallet deltas; it does not infer PnL or order fills.

Blueprint SDK helpers and two MCP tools inspect caller-supplied configuration without chain execution or private library access. Ordinary DLMM is supported. DLMM Pro remains gated until its program/IDL/SDK and position model are verified. Transfer/authority mint extensions beyond passive metadata are refused by this release. There is no background Foundry keeper.

Developers

Build with the Loco SDK, API and MCP

Developer Station at /developers includes a versioned downloadable npm package, TypeScript examples, OpenAPI specification, actual API explorer and both hosted and stdio MCP configuration. The package is distributed by Loco, not published to the npm registry.

API v1 distinguishes Meteora-index metadata from confirmed Solana snapshots. Every response carries source, mainnet cluster, version and observed time. Positions verify mainnet genesis, DLMM program, PositionV2 and LbPair discriminators, pool binding, mint programs and initialized decimals. Pool and position bounds share one confirmed slot; mints are read at or above it. Unavailable metrics remain null; invalid rows are counted and request caps are explicit.

The SDK's range helper is exact-width geometry only, not the app's native Rebalance Planner or a cost/profit forecast. Recorder export analysis uses the same strict schema as the app and returns aggregate evidence-consistency counts locally. Exports remain user-supplied claims; their confirmations are not independently checked on chain.

Hosted MCP registers seven read-only tools with actual read-only handlers. No wallet signing, transaction submission, generic RPC, devnet, custom RPC URLs, private cloud history or DLMM Pro is exposed. An optional eighth Recorder analysis tool is local stdio only, explicitly enabled with --local-evidence. The hosted connection cannot receive or browse private Recorder exports.

Getting started

Connecting a wallet

Studio Loco uses the standard Solana wallet adapter. Phantom and other Wallet Standard wallets are detected automatically; Solflare is registered explicitly. Click Connect wallet in the terminal header and approve the connection in your wallet.

We never ask for a seed phrase or private key and never store keys. Every transaction is simulated against your RPC first, then sent to your wallet for approval. Nothing is signed automatically.

Settings let you switch between mainnet and devnet and set a custom HTTPS RPC endpoint. The public mainnet RPC is rate-limited and may refuse large account scans (used for portfolios); a dedicated RPC provider is recommended.

Wallet Checks verifies the RPC's genesis hash and offers a devnet-only memo rehearsal. It transfers no tokens and creates no accounts, but its reviewed network fee is real devnet SOL. A frozen review lasts 20 seconds after exact simulation. Approve or decline in your own wallet; only a confirmed receipt means it passed. Network, wallet or page changes discard unsent approvals. A shared transaction slot prevents concurrent wallet actions, and unresolved signatures survive reload for Check status without automatic resend.

DLMM

Bins, bin step and the active bin

DLMM divides price into discrete bins. The bin step (in basis points) is the price distance between neighbouring bins. Trades within a bin execute at a fixed price; when a bin is exhausted the active bin moves.

Bins above the active bin hold token X, bins below hold token Y. The active bin can hold both. Your position only earns swap fees while the active bin lies inside your range.

DLMM

Base fees and dynamic fees

Each pool has a base fee derived from its bin step and base factor, plus a dynamic (variable) fee that rises with volatility as price crosses bins. The terminal shows both as reported by the Meteora API.

DLMM fee income is swap-fee revenue for liquidity providers. It is not lending yield and is not guaranteed. Fee/TVL is a backward-looking ratio, not a forecast.

DLMM

Spot, Curve and BidAsk strategies

Spot distributes evenly, Curve concentrates near the active bin, BidAsk weights toward the edges. Studio Loco passes your selected strategy and integer bin range to the official SDK's initializePositionAndAddLiquidityByStrategy, which computes exact per-bin amounts.

New positions in this interface are capped at 69 bins, the tested default position width. The DLMM program supports wider, resizable positions; that flow is not enabled here yet.

One-sided liquidity (only X above price, or only Y below) is not a native limit order. Pools in Limit Order function mode support a distinct native order instruction; the Orders tab checks the onchain mode before showing anything.

Trading

Direct pool swaps

The Swap tab trades directly against one DLMM pool, not through an aggregator. A quote is computed by the SDK from fresh bin arrays and shows the expected output, minimum received at your slippage setting, fee and price impact.

Quotes expire after 20 seconds and must be refreshed before signing. Success is shown only after the transaction is confirmed against its blockhash and last valid block height, with an explorer link.

Risk

Range risk and impermanent loss

Concentrated liquidity amplifies both fee income and inventory risk. If price moves through your range, your position converts entirely into the token that lost value relative to the other, and stops earning fees once out of range.

Smart-contract risk, token risk (freeze authorities, transfer fees, blacklisted tokens) and RPC/wallet risk also apply. Blacklisted pools are flagged in the terminal. Never deposit more than you can afford to lose.

Tools

Signals and two-step rebalancing

The Signals page watches positions while the tab is open and compares each range with the pool's actual active bin. You set a local alert buffer in bins for each position. Signal Box is the separate hosted watch service for observations while the tab is closed.

The Signals page offers a two-step rebalance plan: withdraw/close, then add, each requiring wallet approval. The Observatory can also prepare a native rebalance when supported. Every action uses a fresh review, simulation and your own wallet approval.

Tools

Liquidity Agents (The Observatory)

Liquidity Agents evaluate rules you arm on your verified DLMM positions: a % price move from an explicit baseline, leaving the range, approaching an edge buffer, observed time out of range, and observed volatility from real mainnet candles. Missing or stale price history is reported as unknown, never as low risk.

The Rebalance Planner compares staying put, recentering at the current width, widening to an explicit range (up to 69 bins), and a verified same-mint pool move. Native options build unsigned transactions and show exact first-step simulations, token amounts, SDK rent quotes and fee/SOL requirements. Later staged costs stay unpriced. A pool move leaves fees and rewards in the original open position, withdraws liquidity first and opens a separately approved destination deposit from actual balances. Comparisons, detailed options, selections, fresh reviews and wallet receipts are linked in Flight Recorder. No plan or imported evidence can execute itself. Comparisons expire after two minutes; wallet reviews expire after twenty seconds. Recovery estimates use only your recorded fee-income assumption and complete simulated SOL outflow, never a forecast.

The agent only proposes. Monitoring is read-only, runs only while the tab is open and visible, and pauses during review. Each review freezes the rule revision, wallet, network, RPC, position, target, slippage and costs. Its 20-second approval window starts when preparation and simulation finish, and is re-checked before and after wallet approval. Native rebalances preserve the exact original bin count, including even widths, using the SDK's explicit strategy parameters. They use withdrawn position assets rather than requiring a token top-up; SOL is still needed for network fees and any upfront account rent. When a native move cannot be built or does not fit one transaction, a staged withdraw-then-add is offered instead. Watch-only and practice modes can never transact.

Arming fetches a fresh on-chain baseline. Pausing, hiding the tab or editing rules resets observed out-of-range time. A risk exit keeps precedence during its cooldown; stale proposals are removed. Volatility uses each position's own candle window, and missing, duplicate, gapped or future candles are unavailable rather than low risk.

Agents preserve existing wrapped SOL accounts and return SOL as WSOL. Approval requires a known wallet balance, known exact-message fees and a successful simulation. The SOL requirement includes upfront account rent without counting the network fee twice or treating withdrawn WSOL as rent. Unresolved signatures block new actions even after reloading. Withdrawals that require multiple transactions are blocked in Agents before any signature; review those through the position withdrawal flow. Staged moves verify destination mints on chain and disclose any narrower add range before withdrawal.

Release validation distinguishes an unsigned simulation from a confirmed, funded transaction. Native rebalance passed read-only mainnet simulation with decoded position post-state checks. Funded devnet acceptance passed Spot, Curve and BidAsk at both 20 and 21 bins: six native moves, six exact 25% share withdrawals, WSOL preservation and six position cleanups, with 27 confirmed transactions including setup. Funded mainnet signing and a browser-wallet rehearsal have not been performed. A protocol slippage refusal or unknown balance disables approval. The Observatory uses ordinary Meteora DLMM. Signal Box can observe hosted rules in the background and hand off to a fresh Observatory review; it cannot execute them.

Tools

Signal Box: hosted watches and alerts

Sign in to a private workspace, then add a mainnet position watch or one SOL/USDC arbitrage watch. Position creation verifies the pool, position, owner and token identities and captures a fresh arming baseline. Up to five watches are allowed per account, including at most one arbitrage watch. Watches expire after seven days and can be paused, renewed, edited or deleted.

A server scheduler runs every five minutes, independently of browser tabs. Position watches use the Observatory's deterministic rules, risk precedence and cooldowns. Arbitrage scans run at most once per fifteen-minute cadence and use estimated fees and rent, with no wallet funds or signing access. Each successful observation records a confirmed chain context; failed reads are unavailable. Observation gaps restart continuous out-of-range time.

Alerts are retained in a private inbox. Optional browser notifications require an explicit permission click and a device linked to the current account. A provider accepting a push request does not prove delivery; send a test and check that a notification appears. Email alerts are unavailable. The Scheduler health tab reports recent completed checks; quiet lamps alone do not prove a healthy watch.

Opening an alert carries identifiers only. Load watch rules in the Observatory or Dispatch to verify workspace ownership, current revision and expiry. Then run a fresh chain check or scan and prepare a new wallet-specific review. Edited, paused, expired or deleted watches cannot hand off stale rules. A previous arbitrage opportunity may have passed, and its old payload never becomes a transaction to sign.

Tools

The Flight Recorder

The Recorder stores structured proposals, reviews, alert handoffs and shared-runner wallet actions in this browser. Each action has a timeline, reviewed context, per-step phases and public signatures. Reconciliation checks an unresolved signature without sending it again. A confirmation is distinct from a separate transaction metadata read; unavailable receipts do not show verified balance changes.

Wallet balance deltas use confirmed transaction metadata and exact raw token units. Unsafe numeric lamport values are omitted. They include fee and rent effects and are not a profit calculation or a separate position-state verification. Imported files carry their own identities and an import label; their confirmation claims have not been independently verified by this device.

Records contain no RPC URLs, credentials or signed transaction bytes. Export JSON for a portable copy, or sign in and explicitly sync a private cloud copy protected by account ownership. Newer cloud evidence wins over a stale device copy. Wallet actions and unresolved records are not automatically evicted; the latest two thousand other facts are retained. If browser storage fails, session-only records remain visible and can be exported before closing the tab.

Tools

The Replay Room

Replay loads completed mainnet Meteora OHLCV candles: 24 hours at 5-minute resolution or seven days at hourly resolution. It requires pool bin step and both token decimals, refuses malformed or duplicate candles, and reports missing periods. Practice is a separately selected, deterministic fixture and never an API-error fallback. No wallet connection or signing is needed.

History is fetched in sequential windows of at most 96 completed periods because the Data API rejects larger single requests. Inclusive boundary rows are excluded before stitching; missing windows remain gaps. A failed request stops the entire load, and a 40-second overall deadline prevents an indefinite wait. The exported tape records the request windows as well as the final candles.

The same Observatory rules evaluate each completed close using only the history available then. Risk exits retain priority during cooldown. Out-of-range observation time restarts after gaps and volatility requires consecutive closes in the rule's requested frame. Bin IDs are inferred from candle prices and pool metadata; they are not historical on-chain active-bin records.

Coverage means close samples inside a modeled bin range, not continuous time in range. Intrabar high/low excursions are flagged without inventing their order. The first close initializes the range and is excluded from intrabar coverage. Template comparisons vary width and distribution; distribution alone does not change geometric coverage at the same width.

Optional modeled rebalances assume an approval at one close and apply that frozen target before the next observation. The model does not reconstruct execution delay, slippage, token balances, fees, rewards, impermanent loss or profit. Risk withdrawals remain proposals. Playback, a keyboard-accessible observation slider and JSON export let you inspect and reproduce the exact tape, rules, decisions and assumptions.

Tools

Launching a DLMM pool

Launch Station builds the official createLbPair2 transaction from a PresetParameter2 account fetched onchain. Mints are validated onchain to read decimals and token program. The initial price is entered in quote (Y) per base (X) and converted to an active bin using both tokens' decimals.

A duplicate check derives the pool address for the preset and mint pair and refuses to proceed if it exists. Pool creation does not add liquidity; seed it afterwards from the pool page.

The Depot at /app/depot separately implements two fixed DBC token launch presets, graduation to DAMM v2 and creator/position fee claims with wallet reviews and verified receipts. Custom DBC curves and Alpha Vault remain documented handoffs. DBC graduation does not create a DLMM pool.

Privacy

The privacy distinction

Meteora DLMM is fully public: positions, swaps and fees are visible onchain. It provides no private ballots, sealed bids or encrypted order flow.

The Coordination Lab is a local educational simulation of a confidential-coordination lifecycle using Web Crypto. It has no committee, threshold decryption, FHE or zero-knowledge proofs, and is not a deployed protocol.

Development

Development and integration sources

Studio Loco is built with TanStack Start, the official @meteora-ag/dlmm SDK (pinned), @solana/web3.js and the Solana wallet adapter. Pool lists come from the public Meteora data API (dlmm.datapi.meteora.ag). The SDK is loaded lazily on pages that need chain access.

The repository contains docs/RESEARCH.md with capability mapping and src/lib/capabilities.ts, a registry of implemented, simulated and deployment-dependent features.