THE HOODLABS GUIDE

Account. Token. Wallets.

Start with account access, configure the token using live PONS terms, then add verified wallets when needed.

1. Connect your account

Sign in with a wallet message or your existing email account. Account sign-in and HOODRICH holder proof use separate messages. Neither sends a transaction or token approval.

Signed-in Free accounts receive five managed image-upload attempts per day and one wallet creation every 24 hours when available. Pro raises these to 50 daily uploads and up to 50 wallets per attempt. Pro still requires server-verified subscription access or a current proof for one wallet holding at least 666,666 $RICH.

2. Create the token

InputMeaning
Name / tickerPublic display values. Tickers are not unique; verify the contract address.
ImageSigned-in Free and Pro accounts can upload a still PNG, JPEG or WebP up to 4MB. An existing public IPFS or HTTPS URI works without an account.
Description / linksA public description up to 280 characters, website, and optional social links.
PairNative ETH or a PONS-approved ERC-20 that passes factory, decimals, and economics checks.
ConfigurationAn enabled PONS configuration. Review supply, graduation threshold, and current fees.
Developer buyOptional ETH for an ETH pair. Custom pairs force this to zero.
AdvancedSupported PONS plan, fee recipient, creator tax, 0–2% slippage, buyback, socials, and tax exemptions.
  1. Connect the creating wallet on Robinhood Chain and keep native ETH for the launch fee and gas.
  2. Complete the essentials, choose the pair and an enabled configuration.
  3. Open advanced settings only when you need supported PONS plan or fee controls.
  4. Review the simulation and exact values before approving the wallet transaction.
Custom-pair rules

The asset must be approved by PONS and pass factory, decimals, and economics checks. A custom pair is fixed at creation, forces developer buy to zero, and still needs native ETH for fees and gas. Later trading uses PONS; generated-node trading supports ETH pairs.

3. Prepare wallets

  1. Choose a count and a 12–128 character backup password.
  2. Generate wallets and save the encrypted root backup.
  3. Restore that file to verify the addresses before funding or trading.
  4. Use Import for existing encrypted HOODLABS or original-app keystores. Import and restore do not consume generation allowance.

Keys stay in this tab and lock after 15 minutes without activity. Keep backups offline and passwords separate. Multiple wallets create more gas, records, and recovery work.

Funding and bridging

Fund Ethereum ETH, then use a reviewed Relay quote from Ethereum chain 1 to Robinhood Chain 4663. Check the full recipient, native assets, minimum received, and costs. Keep ETH for gas on both chains. Recover an unknown submitted bridge instead of sending again.

Trade an ETH-paired token

  1. Enter and verify the full PONS token address, or use the address from a verified launch receipt.
  2. Use one node’s 5%, 10%, 25%, 50%, Max, or custom action, or the overall Max All controls.
  3. Each node submits separately. Exact approvals may require a fresh Sell action after confirmation.
  4. Pending and unknown statuses update automatically while this page is visible. Use Refresh all transactions & nodes to check them and update balances manually.

Buy percentages use spendable ETH after gas. Max Buy also retains an ETH buffer for later approvals and selling. Sell percentages use token holdings. The 2% slippage cap does not remove price impact, fees, gas, or partial-fill risk.

Stop and recover when status is unclear

  • Pending or unknown: preserve the transaction hash and refresh its recorded status. Do not resubmit.
  • Expired quote: request a fresh quote only when nothing was submitted.
  • Wallets locked: restore the verified encrypted backup. Submitted transactions continue onchain.
  • Image rejected: use a still PNG, JPEG, or WebP under 4MB, or an existing public image URI.
  • Account verification paused: retry account verification. A temporary outage keeps loaded wallets visible and stops financial actions. After recovery, start a new action for any nodes that were not submitted.
  • Pro unavailable: refresh account access and repeat holder proof after a new sign-in.

Read the full security and recovery limits before using significant funds.