Roadmap

Approvals, activity, your rules, and sessions each have a working backend and no screen in front of it. Bringing all four into the app.

Today · Today you can browse assets, talk to the agent, and approve a plan from the card the agent hands you.

A Uniswap v4 pool can swap and nothing else, so a plain token transfer needs a route of its own. Until it has one, the wallet should not offer it.

Today · A transfer passes the registry, eligibility and policy checks and is then stopped by the risk gate, which reports that no route supports it. Nothing can execute without a route — but you should not have been offered it in the first place.

Export any approval as a file a third party can verify offline — the intent, all four gate results, the frozen quote, your signature, and the proof that the asset was in the signed registry.

Today · All of it is recorded and shown to you in the app. None of it leaves in a form someone else can independently re-check.

Scoped, revocable authority for low-risk work, registered with the on-chain session manager so revoking is a transaction rather than a database write.

Today · Session records exist in the backend and are not yet bound on-chain, so do not rely on them as an on-chain guarantee. Nothing runs without your signature today.

The account, the approval and the submission path are built. The remaining work is proving one operation end to end through a public ERC-4337 bundler.

Today · Core contracts are deployed on Robinhood Chain. The bundler path has not been exercised in production.

The asset registry is signed before it is served, and the client verifies that signature. Moving the signing authority to a multisig with a timelock so no single party can publish a registry.

Today · The registry is signed and independently verifiable. The signer is a single key.

These tokens carry a multiplier the issuer can change by corporate action — a split changes your share count. Showing what changed, when, and what your position was on either side of it.

Today · A quote is already refused when a pending change would land before it expires, because an approval signed at the old multiplier could not execute. You are not shown the change itself.

Adding an independent reference alongside the pool price, marked as reported evidence rather than treated as a check.

Today · A quote is banded against the same pool read a lag window earlier, so the two sides of the comparison are independent. Where a second pool exists it is reported and never gated on — two of the five assets have only one pool, and requiring corroboration would make them unpriceable.

Let a request arm itself for the market open: re-price at the bell, re-run every check against the fresh quote, then ask for your signature.

Today · Outside market hours a request stops at your policy and tells you the market is closed. Nothing is queued, and nothing is ever pre-approved.

A proof that an action fits inside your policy — bound to the exact intent, target, calldata and value — so the chain can enforce your limits without ever learning what they are.

Today · Your policy is encrypted on your device and the server holds only a commitment to it. On-chain enforcement uses a signed attestation; the zero-knowledge verifier is a stub that refuses everything until it is real.