MemeTagCashTags for memecoins
A trading interface at the point of discovery. The architecture and scope of MemeTag.
Abstract
Memecoin discovery often starts with a post. Execution usually happens elsewhere: a copied address, a separate trading interface, and a wallet confirmation removed from the original conversation.
MemeTag places the trading entry point beside the cashtag or contract address on X. A browser extension connects that entry point to token selection, executable quotes, and a wallet that signs locally.
This paper describes extension version 1.4.7, including its current Solana and Robinhood Chain integrations. Its scope is the software, its data flow, and the boundaries of its transaction checks.
Product principles
- Keep discovery and execution close. The trade panel opens beside the post that led to the token.
- Resolve identity before execution. A ticker is a search term. The selected contract and network identify the traded asset.
- Keep signing with the user. Use a connected Solana wallet, or sign in the extension with keys held in an encrypted local vault.
- Make speed a deliberate choice. Reviewed orders are the default. Quick buy requires explicit settings, approved contracts, and per-network limits.
- Show the order’s boundaries. Quotes have an expiry, a defined input amount, a minimum output, and a network cost reserve.
System architecture
| Component | Responsibility |
|---|---|
| X content script | Detect rendered cashtags and addresses, add Buy controls, and display token and order state. |
| Extension wallet | Create and import accounts, handle backup, show balances, and provide trusted approval screens. |
| Background service worker | Restrict message permissions, manage the vault session, prepare orders, and track submission state. |
| Market discovery | Resolve token candidates and pool information using public market APIs. |
| Routing and RPC | Prepare supported routes, read chain state, simulate or estimate transactions, broadcast, and check confirmation. |
| Website | Provide installation, documentation, source downloads, and an interactive product preview. |
The extension uses Manifest V3. Runtime code is bundled with the release. Market and routing providers return data or transaction material; they do not provide executable scripts for the extension to run.
From cashtag to transaction
- Detect. The content script inspects rendered post text for a cashtag or contract address.
- Resolve. The user selects the exact token and network. Ambiguous symbols require a contract choice.
- Prepare. The selected amount and settings are used to request or construct a supported route.
- Check. The proposed transaction is compared with the order and checked using the relevant chain connection.
- Authorize. The user confirms in the extension, or an enabled quick-buy preset authorizes an approved contract within its allowance.
- Sign and submit. The selected wallet signs. MemeTag verifies externally signed transaction bytes before sending them to the network RPC.
- Reconcile. Activity tracks submission and confirmation separately, retaining the transaction identifier for follow-up.
Solana quotes expire after 30 seconds; Robinhood Chain quotes expire after 60 seconds. Quotes are consumed before signing. Closing the panel does not revoke a transaction already broadcast.
Network execution
Solana
Raydium routes use its quote and transaction services. Pump.fun and PumpSwap routes can be constructed locally with their official SDKs and RPC state. PumpPortal’s local transaction service provides an additional fallback.
Checks include the supported swap instruction, selected input, minimum output, payer, relevant account changes, and token permissions. Unknown instructions are rejected. A transaction is simulated again before signing.
Robinhood Chain
Transactions target mainnet chain ID 4663. MemeTag discovers supported Uniswap v2, v3, and v4 pools, quotes against chain state, and builds transaction data locally. Supported direct and two-pool paths depend on available liquidity.
Orders bind the wallet, amount, minimum output, deadline, chain, and router. Token sells may need separate approvals. New approvals are amount-limited; a quote that expires while approvals complete requires another review.
RPC responses and simulations represent a point in time. Pool state and prices can change before a transaction is included.
Wallet and trust model
Connected Solana wallets prove ownership with a signed connection message. Each transaction is prepared and simulated by the extension, reviewed and signed in Phantom, Solflare, or Backpack, then checked against the exact prepared message before broadcast. Private keys remain with the external wallet. Connection state and pending requests are held only for the browser session and clear on lock.
The persistent vault uses AES-256-GCM with a password-derived key from PBKDF2-SHA-256 at 600,000 iterations. Wallet creation uses fresh randomness; public addresses are authenticated alongside the encrypted payload.
A recovery phrase derives separate Solana and EVM accounts. Importing a single private key creates a new key for the other network, which must be backed up separately. Unlocked secrets live in trusted extension session storage and are cleared on lock.
The X content script can request quotes and open the approval window, but cannot export keys, unlock the vault, edit settings, or approve a reviewed trade. Quick buy uses a separate, explicit authorization path with an unlocked wallet, backup confirmation, approved contract, and daily allowance.
Data and transaction costs
Wallet configuration, token selections, recent activity, and position records remain in local extension storage. Solana positions use confirmed trade receipts to calculate weighted average cost and PnL in SOL. Incoming transfers or missing history leave the cost basis unknown. Market APIs receive relevant token queries; routing services may receive public wallet and order details. RPCs receive chain reads, simulations, and signed transactions. Blockchain records are public.
MemeTag adds no platform fee in version 1.4.7. Pool fees, route-provider fees, network transaction fees, approvals, and account-creation costs can still apply. The Networks & fees page explains these costs; the Privacy notice explains data handling.
Current scope and limitations
The release supports desktop Chrome, Brave, and Edge, with manual installation and updates. It does not run within the X mobile apps. Network selection does not bridge assets between chains.
Route availability is determined by the token, pool, input size, and current chain state. Unsupported instructions, token extensions, hooks, or transaction structures may be rejected. Market search, quotes, simulations, and RPC services can fail or become stale.
Automated checks and unsigned transaction simulations help validate specific behavior. They are not independent audit results or a guarantee of execution. This document describes the current implementation rather than committing to future functionality.
Download source code