Overview
JellyPons is a bot that turns a post on X into a transaction on Pons V2, the AMM on Robinhood Chain. You reply to it in plain English; it checks who sent the post, builds the transaction, signs it with the wallet mapped to your handle and answers in the thread with the hash.
It is not a new chain and not a new token standard. Tokens deployed through it are ordinary ERC-20s, pools are ordinary Pons V2 pools, and any wallet or explorer on the chain can read both without knowing JellyPons exists.
Status: live, and unaudited. The bot launches tokens from posts on X and $JELLY is trading on Pons V2. What is not ours is not listed above: we operate no factory, no fee splitter and no liquidity lock - launches go through the Pons V2 factory and its fee split, and those rows stay empty rather than borrow someone else's addresses. Nothing here has been reviewed by anyone.
Getting started
Two steps, both on X.
1. Sign in with X
The handle is the account. One OAuth hop tells the terminal who is posting. The scope is read-only: your handle, and the posts that mention the bot. The bot never posts as you and never opens a DM first.
2. Claim a wallet
Reply once and the bot creates a wallet and maps it to your handle:
@Jellyponsbot claim my wallet
→ 0x… is yours. Reply "export my key" whenever you want it.
You can also point the handle at an address you already control by signing a message from MetaMask or a Ledger. Binding is a signature, never an approval and never a transfer.
Wallets and keys
- A bot wallet is generated on claim and its private key is exportable on request
- An owned wallet is bound by signature; the bot can read it but cannot move funds from it
- Unbind, rebind or swap the address at any time from the same reply box
- Revoking the X app removes the link entirely
Treat a bot wallet like a hot wallet on a phone: convenient, and not where a serious balance should live. Move anything you care about to hardware.
Command reference
Every command is a reply that mentions the bot. Case does not matter and the phrasing is forgiving - these are the canonical forms.
| Command | What it does |
|---|---|
| claim my wallet | Creates a wallet and maps it to your handle |
| what’s my wallet? | Returns the address and per-token balances |
| buy $25 of $FROG | Swaps into the token at the pool price |
| sell 40% of $FROG | Swaps out, by percentage or amount |
| send 10 $FROG to @friend | Resolves the handle and transfers |
| burn 1000 $FROG | Sends to the zero address, confirmed twice |
| launch Name ticker $TICKER | Deploys the token and opens its pool |
| claim my fees | Claims the creator fees accrued on your launches |
| export my key | Sends the private key by DM, once |
Launching a token
One line deploys the token, opens the Pons V2 pool and sets the fee route to the sender, in a single transaction:
@Jellyponsbot launch Jelly Frog ticker $FROG, website frog.xyz
→ token 0x… pool opened creator fees routed to @yourhandle
The factory locks the initial liquidity at creation, and the token it deploys has no mint, pause or blacklist function - there is nothing left to call afterwards, by anyone.
Launching costs gas and nothing else. There is no listing fee and no ticket.
Trading
Buys and sells route through the Pons V2 pool for that token. The bot checks the chain id and the slippage bound before it signs, and replies with the transaction hash so you can read the result on the explorer rather than trusting the reply.
- Amounts can be given in dollars or in tokens
- Percentages work for sells: sell half of $FROG
- Every command is idempotent per post - re-reading a post never re-sends it
Fees and the split
There is one fee. It is taken on swaps, in the pool’s own asset, and the contract splits it at claim time. No emissions, no subscription, and no cut of what you bring with you.
| Share | Goes to |
|---|---|
| Pool fee | The Uniswap V3 fee tier of the token’s own pool, fixed when the pool is created |
| 70% | The token’s creator, claimable for as long as it trades |
| 30% | Pons protocol - of which Pons puts 80% into TWAP buybacks and 20% into operations |
These shares are constants in the splitter contract, not settings on a dashboard. If nobody trades a token, its creator earns nothing - the fee only exists where volume does.
Contracts
Three pieces: a factory that deploys tokens and opens pools, a splitter that holds and divides fees, and a lock that holds the initial liquidity.
| Contract | Address |
|---|---|
| Factory | soon |
| Fee splitter | soon |
| Liquidity lock | soon |
| $JELLY | 0x14F7FBCdb883AEa0E6c1AdAd8EBa023e4CD0f412 |
Source is verified on the explorer at deploy. Solidity is pinned, and the build targets the
paris EVM version because Robinhood Chain does not carry PUSH0.
Security
Nothing here has been audited. We will not describe this project as safe, secure or risk-free, and when contracts are finished we will say plainly who - if anyone - reviewed them.
- The bot never DMs you first and never asks for a seed phrase. Anything that does is not us
- The only handle we operate is @Jellyponsbot
- Verify a contract address on the explorer before you interact with it, every time
- Launching and trading tokens carries smart-contract and market risk, including total loss