From preview to execution.
The web workflow comes first. Real execution and Telegram follow the same quote, permission and receipt system.
Available now
Verified launch snapshots, exact-address market checks, wallet reads, paper buys and sells, manual limit fills, positions and trade history.
Next: executable quotes
Index launch events and graduation state. Resolve the exact quote asset, router, curve or pool. Show service fees, protocol and creator charges, price impact, minimum output and expiry. Reject stale or incomplete routes.
Then: bounded execution
Add explicit user authorization, transaction simulation, reviewed spender permissions and receipt reconciliation. Limit supported assets and deployments until each route has passed buy/sell and failure tests.
Record submitted, pending, confirmed, reverted and expired states. Never retry a timed-out trade blindly.
Finally: automation and Telegram
Build user-defined exits on the same execution service. Enforce amount, recipient and expiry limits outside the language model. Users can revoke future authority. A trigger may fail or fill worse than expected when markets move.
Telegram starts as alerts and links to reviewed actions. Do not collect private keys in chat. No Telegram bot is connected today.