Security

01Connected wallets

Phantom, Solflare, and Backpack keep their own signing keys. A signed, short-lived connection message proves control of your Solana address. Each trade requires approval in that wallet; quick buy is disabled.

The extension accepts connection messages only from the MemeTag connection page. It checks the exact prepared transaction message and the wallet signature before broadcasting. Requests expire and cannot be completed again after use or cancellation.

02The local wallet

Persistent wallet secrets are encrypted with AES-256-GCM. The encryption key is derived from the password using PBKDF2-SHA-256 with 600,000 iterations and a random salt. The wallet uses a random encryption IV and binds the public addresses to the encrypted vault.

Unlocked signing material is held in extension session storage restricted to trusted extension pages. Locking clears the unlocked session. Browser restart also clears session storage.

Encryption protects the stored vault. It does not make a compromised browser, malicious update, or infected device safe.

03What the X page can do

The content script detects tokens in rendered posts, requests quotes, and opens the extension’s approval window. It cannot unlock the vault, reveal recovery information, change wallet settings, or approve a normal reviewed order.

Quick buy is an explicit exception for approved token contracts while the wallet is unlocked, with backup confirmation and remaining daily allowance. Keep it disabled if you want to review each order.

04Transaction checks

For Solana, MemeTag checks supported swap instructions, the payer, input amount, output limit, relevant writable accounts, and token permissions. Transactions are simulated before signing. Unrecognized instructions are rejected.

For Robinhood Chain, orders are built locally and checked against the selected wallet, chain, amount, minimum output, deadline, router, and approvals. New token approvals are amount-limited, and Permit2 authorizations also expire.

Quotes expire and are consumed before signing to prevent ordinary reuse. These checks reduce specific transaction risks; they do not establish that a token is trustworthy.

05Release status

Source tests cover wallet derivation, encrypted-vault tampering, sender permissions, quick-buy limits, quote expiry, and transaction checks. Local checks and unsigned network simulations do not amount to an audit or a guarantee of successful mainnet execution.

Token issuers, pools, RPC services, and blockchain programs remain separate sources of risk.

06Practical wallet care

• Install from the MemeTag download page and keep the recovery information private.
• Verify the complete contract address and network before trading.
• Lock the wallet when you finish and keep your browser and device updated.
• If an order’s status is unclear, inspect Activity and the explorer before submitting another order.
• If you suspect the device is compromised, stop using that installation. Use a trusted device and your backup to regain control of the wallet.

If you share a bug report, include the extension version, browser version, steps, and the visible error. Remove passwords, recovery phrases, private keys, and RPC access tokens from any screenshot or log.