0ath’s stack is getting deeper. ⚙️ The next layers on our roadmap: 👥 Shadow: test and benchmark strategies without moving capital. 🌐 Shared budgets: coordinate portfolio risk across every agent. 🎯 Inventory: bounded native orders on compatible Meteora pools. 🛡️ Guard: enforce critical Oath permissions on-chain. 🌊 Depth: treasury-backed liquidity targets for token teams. Measurable performance. Coordinated capital. Revocable authority. We’re building towards agents you can understand, constrain and hold accountable. A deeper stack, with your Oath governing every layer. Your capital. A promise kept.

0ath is getting a serious execution upgrade. ⚙️ Your Meteora DLMM range, inventory and earned fees, coordinated through one Oath-governed plan. Fresh pool reads. Explicit capital budgets. Instruction-level validation. Simulation before signing, with a fresh policy check at the execution boundary. Rebalances preserve your exact range width. Compounding puts finalized, verified fee claims back to work. Every step leaves a receipt. Uncertain transactions enter reconciliation instead of triggering blind retries. The latest build brings the planner and execution history into the Agent page. We’re working through the final checks. More capable agents. Every action accountable to your Oath. Your capital. A promise kept.

Exciting times ahead.

GM 0athers. Lots in store today. Stay tuned.

Something big is on the horizon for 0ath around @MeteoraAG’s new DLMM. 👀 We’re exploring an execution layer that would coordinate bin-level positioning, rebalancing and fee compounding through one policy-controlled plan. Fresh pool state, explicit capital budgets, instruction validation and simulation before signing, with receipts that show exactly what happened. The goal: take autopilot further by coordinating your range, inventory and earned fees, with your Oath governing the entire flow. A bigger chapter for autonomous liquidity is taking shape. More soon.

Next on 0ath’s roadmap: liquidity burns on autopilot. 🔥 The plan: let devs authorise their 0ath agents to permanently commit liquidity from their own eligible positions in chosen token pools. You define the approved pools, amount caps and schedule or trigger. Your agent would verify ownership, enforce the mandate, simulate the transaction and record the on-chain result. For Meteora DAMM v2, this means permanent locking: committed liquidity stays in the pool and remains eligible to earn trading fees, while withdrawal rights are permanently removed. Explicit permission before automation. An irreversible commitment after execution. Your pools. Your policy. A promise the chain can verify.

🫡

🤝

0ath Fee Reserve has reached its next engineering milestone. This update took serious work beneath the interface. Every fee claim needs a traceable origin, every allocation needs exact accounting, and every custody action needs an explicit boundary. The preview now includes transaction-backed fee receipts. Verification checks a successful, finalized Meteora claim_fee2 transaction against the expected pool, position, recipient, token mint and exact transfers. The instruction layout is pinned to our installed Meteora SDK. Incomplete provenance stays unverified and is excluded from allocation calculations. We also built the historical allocation preview around raw token units and integer arithmetic. Contribution caps apply to each claim individually, with excess kept in Hold. The video demonstrates it: two claims of 120 and 80 USDC, a 20% Reserve allocation and a 15 USDC cap produce a combined Reserve illustration of 30 USDC. These are historical examples, not available wallet balances. Underneath that, the custody prototype now compiles for Solana SBF and has passed its local LiteSVM lifecycle test against the compiled program. Deposits credit liability units only after the exact tokens arrive. Direct donations remain surplus. Owner redemptions remain available while new deposits are paused. We tested caps, ownership restrictions and those accounting transitions together. That is the foundation this stage establishes: verifiable claims and explicit custody rules. The video uses labelled simulations. The reserve program remains undeployed, signing stays disabled, and claim-proven funding still needs to connect these layers before lending follows. We’re continuing to build the stack, one enforceable promise at a time. Your capital. A promise kept. 0ath.world/app/reserve

Yes a portion of 0ath's trading fees will be dedicated to buy backs and burns via 0ath's own agent. More to come, we're currently finishing off Fee Reserve.

0ath Fee Reserve, stage one, is now in preview. We’re building opt-in, collateralised credit funded by claimed Meteora LP fees. This first stage is the policy and risk workbench: • Draft Hold / Compound / Reserve allocations and contribution caps. • Review recorded claims, with missing data flagged. • Simulate how interest, debt limits and collateral shocks affect borrowing capacity and recoverable value. Drafts stay separate for each user, agent and network. Saving one moves no funds and grants no signing authority. Understand the mechanics before committing capital. The on-chain lending program comes next.

Builders always win 🔨

👀

Gm 0athers! Day 2 and straight back to work. Today we're building out a new hook concept: 0ath Fee Reserve. We're designing an opt-in reserve where earned Meteora LP fees fund collateralised loans, with borrowing interest shared with contributors. Your Oath sets the allocation and limits. A second job for your fees. Lending carries risk.

0ath has just implemented multiple agents: You can now run up to 5 agents, each with its own wallet, name, Oath, limits, and activity. Keep a conservative mandate and a bolder one side by side, and compare them honestly in the same interface. Different capital deserves different promises.

New at 0ath: Value history chart Your agent's 30-day snapshots are now a line you can read at a glance, not just counts in a table. It plots real recorded values from your own agent's checks. No projected curves, no invented numbers, just your actual history.

Claim threshold settings are now live: You can now decide when fees get claimed, instead of a fixed daily claim. Set a threshold, for example only claim when accumulated fees are worth enough to justify the transaction. Fewer wasted fees, your rules, still enforced by the Oath.

Updates coming thick and fast for 0ath: Suggested pools Your Oath already defines allowed pairs and a minimum liquidity. 0ath now lists Meteora pools that pass those checks, as suggestions only. The agent never opens new pools on its own; you click first. Expanding your reach without expanding your agent's authority.

New 0ath update: Position health view Every position now shows its active bin, how far price is from the edge of its range, current holdings, and unclaimed fees at a glance. You no longer have to wait for the agent to act to learn where you stand. Seeing drift early is the difference between a rebalance and a loss.

0ath started with a simple idea: give liquidity an agent with a clear mandate. It’s grown into a Meteora liquidity stack: position management, fee compounding, performance history, price-history guidance and optional exit rules. What makes 0ath distinctive is how those pieces connect around your Oath: explicit instructions, simulation before signing, recorded activity and range suggestions you choose whether to adopt. Thank you to everyone who has believed in us so far. Your support and feedback help shape what we build. We’re here for the long haul, constantly building out the stack. More updates are on the way. And it’s a big week for @MeteoraAG and their new DLMM, with Solana Summit Singapore on 6 October. We’re watching closely as the next liquidity chapter takes shape. Your capital. A promise kept. 0ath.world/