- Network fee
- ~$0.00012
- Simulation
- Will succeed
- After this tx
- 4.32 SOL remaining · $805.78
Praxis is a conversational agent for Solana you can safely hand signing power to. An on-chain policy — not a backend promise — decides what it can do. Say what you want in plain English; every action is checked against your limits before you sign, and you can revoke it in one transaction.
And that's the whole problem. A bug, a bad parse, a prompt injection, a compromised backend — any one of them, and an agent holding your keys can drain you. So far the only answers have been bad ones.
Approve each one by hand. Safe — and now it's just a slower wallet. The agent was supposed to save you the clicks.
Let it sign whatever it wants. Useful — until the day a bug, a bad parse, or an attacker turns that power against you.
Ask it to send 50 SOL when your cap is 5, and the transaction simply fails. Not because our server said no — because the Solana program won't sign it.
The agent proposes. The chain disposes.
Praxis is built around one input field. Whatever you'd do on Solana, you can ask for in a sentence — and Praxis turns supported intents into signable actions, while blocking anything it cannot enforce.
Aliases, .sol domains, or pasted addresses. Praxis remembers who you've transacted with and surfaces them by name.
Swap intents are parsed and policy-checked against verified mints. Jupiter execution is documented as the next phase, not hidden behind a fake sign flow.
On-chain volume, price action, holder concentration. No "ape now" calls — just the data you'd dig for, summarized.
Cross-chain routing is intentionally outside v0.1. It belongs after wallet auth, durable state, and enforceable transfer flows are solid.
Scheduled actions need a reliable crank and the same Aegis envelope. They are a product direction, not a demo feature.
Praxis builds an address book from your transaction history and explicit saves. Ambiguity always asks before acting.
One conversation per intent. Supported actions end in a policy verdict before signing; unsupported routes stay blocked. No surprises, no hidden steps, no “trust me.”
Natural language. Misspellings, slang, half-formed thoughts. Praxis parses intent the way a senior trader skims a Telegram message — not the way SQL parses a query. Ambiguity prompts a follow-up; certainty proceeds.
Every action is simulated against live chain state before you see it. If a transaction will fail, slip, or pay fees that don't feel right, Praxis tells you — and explains why. The agent is the interpreter. The safety layer is the executor.
In the live demo, the scoped agent key can only sign Aegis instructions from the policy vault. Owner/admin actions are the production wallet-signed path; the agent never gets unrestricted wallet authority.
Multi-turn conversation memory. Aliases, fuzzy token matching, multi-step actions chained in a single line.
Every transaction simulated against live state. Slippage caps, fee bounds, and outcome previews — all enforced.
Swap intents are parsed and checked against verified-mint policy. Executable Jupiter routing is the next implementation phase.
Aegis uses a program-owned vault and a revocable agent key for the demo. Owner-signed wallet admin is the production path.
Auto-suggested from your transaction history. Explicit saves. Ambiguity resolved through clarifying questions.
On-chain volume, price action, holder concentration, and liquidity context. Data surfaced — never financial advice.
Conditional and scheduled actions within session-key limits you set. DCA, rebalancing, conditional trades.
Future bridge work must stay owner-signed or gain a real far-side enforcement story. It is not part of the agent path today.
Keyboard-first interface. Command palette. Saved prompts. Custom slippage and gas defaults per asset.
Conversational interfaces in crypto are easy to build badly and dangerous when built carelessly. These are the lines we draw and won't cross — even when it would be convenient.
The demo uses a program-owned Aegis vault and a scoped agent key. Production owner actions must be wallet-signed, and any autonomous agent authority must stay inside an on-chain envelope it cannot cross.
If your intent is ambiguous, Praxis asks. Two Toms in your contacts? It asks which. Token symbol collides? It asks which. Better one extra question than one wrong transaction. The agent is the interpreter; you remain the decider.
Verified tokens only by default. Unverified mints require an eyes-open override and a second confirmation. The agent is conservative by construction. Memecoin sniping is not the product. Not yet, perhaps not ever.
Praxis surfaces data and executes verified actions. It does not tell you to buy, sell, or hold. Markets are markets; decisions remain yours. The product is a sharper tool, not a louder voice.
Network fees and product fees must be surfaced before you sign. No hidden spreads, no "convenience markups," and no pretend swap execution path until the program can enforce it.
The send flow already proves the thesis: an agent can hold signing power without being able to misuse it. Everything next widens what it can do — without ever leaving the envelope.
DCA, subscriptions, payroll, treasury sweeps. This is the first thing you genuinely can't do safely any other way — the agent acts while you're asleep, inside caps it still can't exceed. The envelope is what makes “set it and forget it” sane instead of reckless.
Live Jupiter routing — but only once mint, program, and value limits live inside the swap instruction itself. A swap that could slip outside the envelope would break the whole promise, so it ships when the program can police it, not a day sooner.
Open the same Aegis envelope to other autonomous agents. Anything that needs to pay, rebalance, or transact on-chain can borrow Praxis's scoped, revocable authority instead of a naked private key. Praxis becomes the safe hands the agent economy moves through.
One rule never changes: new power has to make the safety stronger — it never opens an escape hatch.
Walk the core flow: ask for a SOL send, preview the Aegis verdict, confirm an allowed transfer, reject an over-limit request, and revoke the agent key.