Clear rules.
Clear boundaries.

What works today

My Oath lets you set allowed pairs and optional pool addresses, capital and per-action limits, pool exposure, slippage, minimum pool liquidity, distribution, range, and approval preference. It saves only in this browser and supports validated JSON import/export.

Meteora pools reads public DLMM pool data from Meteora's API. Search, pagination, details, and links are read-only. If the service fails, a separately labeled demo option is available.

Shadow Mode deterministically checks your proposal against every Oath rule. An eligible decision requiring approval waits for an explicit simulated approval. The journal records local decisions and their reasons. No historic performance or investment returns are modeled.

Understand the boundaries

• No wallet connection, private-key collection, signing, or on-chain transaction.
• No server-side policy enforcement, agent automation, or autonomous trading.
• No Telegram notification, LLM narration, NVIDIA sandbox, or deployed OpenShell integration.
• Illustrative inputs are not a historical backtest. Swap fees are not guaranteed; an out-of-range DLMM position stops earning swap fees until price returns or it is rebalanced.

A possible path forward

1. Browser console and local policy — available now.
2. Authenticated API with durable policy and journal.
3. Deterministic server-side policy gate.
4. Meteora SDK unsigned transaction simulation.
5. Explicit user-wallet approval for every submitted transaction.
6. Optional sandboxed scoped signing service and Telegram notifications.

These later steps are research directions, not current integrations or commitments. Never share your private keys with a website.

Further reading

Meteora: What is DLMM? ↗ · Meteora getting started ↗

0ath is independent and is not affiliated with Meteora, NVIDIA, or the original agent reference stacks that inspired this category.