Oath

Right sure we went to 300k with active users because we’re a shell. Clearly you didn’t use the app nor have the understanding to even fuel your curiosity. Your donation? What did you do? You’re claiming to call us out when we’re already at 4k. Not sure who takes your account serious. Wisemen - more like Jokemen. Thank goodness we had 4% transaction fees and over 1mil total volume or the couple grand you think we made would have been a devastating blow to devs who put so much effort into bringing our vision to life.

Another account with 100 assumptions. Just because we entered the hackathon doesn’t mean we’re affiliated with either @MeteoraAG or @colosseum in an official capacity. Anyone could have entered. We’ve had plenty of deliveries and worked from day 1 of release, we just kept building and adding - as active teams are supposed to. Shows you know nothing about us nor did you use the app. You’re not good for the space.

For everyone’s information we aren’t ’celebrating’ a negative PnL from an investor - rather highlighting how loyal they are to hold. We’re still here and building, this is an attention economy and as soon as the @MeteoraAG @colosseum hackathon finished - investors took their attention and money elsewhere. Most hackathon projects are down and half of them have gone for good. No-one is here for the real tech - 0ath works and it works well. A tenth of investors even bothered using our stack vs the amount of traders and holders we had. An empty shell would probably have done just as well maybe even better depending on the team’s connections to the treacherous KOL’s of our space.

You took an Oath. We’ll keep the promise.

GM ☀️ There’s been some serious brainstorming behind the scenes at 0ath. We’ve been questioning the architecture, challenging our assumptions and mapping what would make this a tool teams depend on every day. The ambition is to make 0ath a household name within the @MeteoraAG ecosystem. That means earning a place in how builders, treasuries and LPs manage their liquidity. We’re making progress on the next round of updates. Evidence Lab laid the measurement foundation. Something bigger is taking shape around turning liquidity objectives into plans, with explicit budgets, boundaries and evidence of delivery. And a candid word to holders: some of you are judging a long-term build with a five-minute attention span. Zoom out. Judge the releases, the utility and whether we keep delivering. We’re putting the hours into something worth using for years. More soon. Your capital. A promise kept.

Happy Sunday. Evidence Lab v1 is live. The question we keep coming back to: what should “healthy liquidity” actually mean? TVL, fee income, or the trade size a pool can quote at an acceptable price impact? What would you measure first on @MeteoraAG?

🫡

He took the 0ath

First roadmap milestone checked: Evidence Lab v1 is live. ✅ 0ath now has a read-only workspace for inspecting supported @MeteoraAG DLMM pools approved by your Oath. Capture slot-tagged pool state. Quote exact trade sizes in both directions. Inspect price impact and swap fees. Save, replay and compare captures. Then model 25% and 50% depth reductions to examine how quoted capacity changes under thinner liquidity. 1,124 tests passed across the suite. Signed-in live-capture validation remains pending. This is the measurement foundation for Market Mandates: giving agents clear objectives, then building the evidence needed to assess their work. Next on the roadmap: Mandate Compiler. The stack keeps getting deeper. Your capital. A promise kept.

The next direction for 0ath: Market Mandates. 🗺️ Let teams define the trading capacity they need, then have agents plan, execute and document delivery within explicit capital limits. Our proposed roadmap: 01 - Evidence Lab Measure executable depth, price impact, inventory exposure and costs. Test proposed strategies against recorded conditions. 02 - Mandate Compiler Translate market objectives into bin allocations. Show what available capital can support, where coverage falls short and why. 03 - Mandate Vaults Introduce opt-in vaults with program-enforced permissions, budgets and defined owner recovery controls. 04 - Liquidity Commitments Extend Missions into delivery periods, with recorded observations and attributable contributions. Later, add capped sponsor rewards for accepted delivery. 05 - Agent Delivery Market Let agents compete with independently validated plans, supported by transparent costs and delivery histories. In parallel: a verified DLMM Pro adapter, gated on official artifacts and funded validation. The first milestone is Evidence Lab and a read-only compiler preview. We’re building toward a deeper role for agents within the @MeteoraAG ecosystem. Here for the long haul. Your capital. A promise kept.

GM ☀️ A new 0ath roadmap is on the way. We’ve been thinking carefully about where this stack can take us next, and a bigger direction is taking shape. Agents coordinating fees, inventory and pool depth around shared market objectives. Each with defined authority, bounded capital and a record of what its actions actually achieved. That’s the next chapter we’re mapping out within the @MeteoraAG ecosystem. We’ll share the milestones, dependencies and reasoning behind it soon. We’re building 0ath for the long haul, and this roadmap will show what that commitment looks like in practice. Your capital. A promise kept.

GM ☀️ 0ath’s latest build is now in preview. This update is for the moments when capital has several jobs to do, but your agent has a finite budget. Fee routing becomes especially useful when compounding, Inventory orders and Mission repairs compete for daily limits. You set the priority before budget is reserved. Every route remains bound to your Oath and its permissions. For token treasuries managing inventory drift, Inventory compares the target mix with observed holdings across wallets, positions, order escrow and with-drawable proceeds - counting each source once. For teams coordinating liquidity support, Missions gives two agents under one owner a clearer record of their work toward a fixed pool-depth target. Confirmed transactions, proven contributions and later depth observations are recorded separately. 1,073 tests passed. We’ve also added the DLMM Pro verification foundation, with execution gated until official artifacts and the adapter are verified. We’re dedicated to building 0ath for the long haul. Our aim is to become an unstoppable name within the @MeteoraAG ecosystem through useful technology, accountable execution and a stack we keep improving. Your capital. A promise kept.

🤝

GM from 0ath ☀️ We started with a simple idea: let an agent manage liquidity inside rules you define. That idea has grown into a much deeper stack: • Independent agents with their own wallets, Oaths, limits and exit rules. • Position health, recorded value history, claim thresholds and fee compounding. • Fee Reserve, verified fee receipts and an execution layer that validates, simulates and reserves before signing. • Lifecycle hooks, Shared Budgets, Shadow Lab and depth reviews. • Inventory and fee-vault mandate tooling, alongside the Guard contract prototype. The latest milestone is Missions: two agents coordinating toward one liquidity objective on Meteora DLMM, while keeping their individual authority intact. One pool. One fixed bin band. A soft depth goal inside hard spending limits. The Missions build and database installation are complete. Next comes funded Devnet validation before publishing - testing the full path from genuine fee receipts to a bounded repair and transaction recovery. Beyond that: deeper Inventory and fee-routing integration, then a verified DLMM Pro adapter. The direction is bigger than automating individual positions. We’re building toward agents that coordinate measurable market objectives, show their work and remain accountable to your rules. Still building. Here for the long haul. Your capital. A promise kept.

Gm and Happy Sunday! 0ath Missions is a milestone for the stack: we’re moving from individual liquidity agents to coordination under one owner-defined objective. Two agents. One Meteora DLMM pool. Separate wallets, Oaths and limits. A mission defines a fixed bin band and a quote-token depth goal. The goal is soft; spending limits are hard. Each agent operates within its own Oath, position mandate and the mission’s caps. Repairs use verified, finalized fee receipts earned after arming. Both agents get an unsigned candidate. The lowest actual transaction cost wins, with deterministic tie-breaks—and only the selected agent’s own run can sign. The execution path matters: Validate → simulate → recheck fresh state and authority → reserve receipts → sign → persist the original signature → broadcast. If the outcome is uncertain, capital stays reserved while 0ath reconciles that original transaction. No blind resend. No timer quietly freeing funds that may already have moved. Implementation and database installation are complete. The build reached 934 passing app tests and 221 isolated PostgreSQL checks; regenerated types and the production build also pass. Funded Devnet validation is next, before publishing. The demo illustrates the flow; it isn’t a live execution. From individual autopilot to coordinated liquidity - with every Oath still binding. Your capital. A promise kept.

Shape it. Stretch it. Give it an Oath. Our DLMM Pro plan: 0ath Missions coordinating depth, inventory and repairs funded by earned fees, within your limits. The team designs the curve. The agents get a mandate for managing liquidity as the market evolves.

It's better if we show you. Meet 0ath Missions - the next layer we're designing for liquidity agents on Meteora. A shared liquidity objective. Separate wallets. Every agent bound by its own Oath. An owner defines the approved pool, depth target, fee share and spending cap. A coordinator turns that mandate into bounded proposals, compares eligible plans and holds overlapping repairs before they reserve capital or sign. This simulation follows a 1,800 USDC depth repair using 30% of the selected agent’s verified fees. Another 4,200 USDC stays protected. The overlapping proposal produces zero sends. Around that sits the deeper architecture: • Versioned mandates and explicit arming. • Inventory accounting that includes positions and order escrow. • Unsigned simulation and fresh authority checks before signing. • Receipts linking decisions, costs and outcomes to the original transaction. • A proposed SDK for token teams to integrate mission controls. Two agents. One owner. One approved pool to start. This is a concept demonstration of the proposed upgrade. Programmable liquidity. Coordinated by agents. Bound by your Oath.

Gm 👀

0ath’s latest build is complete. We’ve taken fee automation deeper into Meteora’s stack. Verified DLMM fee receipts can now fund an owner-linked Dynamic Fee Sharing vault through an explicitly armed mandate. You choose the source pools, funding share and caps. Saving the rules and granting execution authority are separate steps. Most of this build went into authority, accounting and recovery: • One receipt ledger across compounding, Fee Waterfall, Inventory and vault funding. • Exact transaction validation, unsigned simulation and receipt reservation before signing. • Retained fees protected from other wallet-funded actions. • Fresh, mint-matched Mainnet pricing for USD checks. Unknown pricing holds funding. • Recovery that follows the original stored signature after a restart, without automatically creating another send. Inventory also verifies actual pool accounts, token mints and native limit-order eligibility before arming. 842 tests passed. 397 isolated PostgreSQL checks passed. Typecheck and production build passed. A stronger foundation for agents to route earned fees under precise authority, protect reserved capital and recover when execution gets uncertain. Validated draft complete. Database migrations and publishing are next. Your capital. A promise kept.

Next on 0ath: fees become strategy. We’re working on an Inventory Engine designed to turn a capped share of verified claimed fees into passive orders inside eligible Meteora DLMM pools. You define the pairs, price bands, exposure limits and cancellation rules. The agent works through that mandate. The technical work goes well beyond placing an order: reserving capital before execution, counting escrowed funds toward exposure, tracking partial fills, reconciling uncertain transactions, and confirming what’s actually available before redeploying it. Every proposed action still has to pass the Oath, depth, execution-cost and simulation checks. Alongside the engine, we’re designing: • Position Mandates - explicit boundaries between position ownership, management permissions and fee destinations. • Fee-sharing vaults - fixed recipient splits funded from verified claim proceeds. • A Pro capability adapter - checking program versions, pool features and supported instructions before enabling an execution path. We’re preparing for DLMM Pro, with Pro execution dependent on verified SDK and permission compatibility. The goal is an agent that can coordinate liquidity, inventory and earned fees under one reviewable mandate, with a clear account of every decision and movement of capital. Another substantial layer of the 0ath stack taking shape. Your capital. A promise kept.

Or get a liquidity agent to do it for you in your sleep 😴