SECURITY & RECOVERY

Keep the keys. Limit the damage.

Use working funds, verify every network and address, and resolve uncertain transactions before trying again.

Before using funds

  1. Use your own connected hardware or browser wallet for a free launch. HOODLABS never needs its seed phrase.
  2. Use a dedicated browser profile with minimal extensions and only working funds.
  3. Verify the chain, full address, amount, fee and contract before approving anything.
  4. Lock generated wallets when finished. Locking prevents new actions; it cannot reverse a sent transaction.

Back up generated wallets first

Node wallets are generated and unlocked in the browser. The workspace requires a restore-verified encrypted backup before use.

  • Save the backup offline and keep its password separately.
  • Anyone with both can spend every wallet derived from that root.
  • HOODLABS cannot recover a lost backup or password. A lost backup does not refund an accepted generation attempt.
  • The browser still trusts the website code, device and extensions while keys are unlocked.

Recover before retrying

A pending or unknown transaction may already have been sent. Check its recorded status and explorer receipt before any new action.

  1. Keep the original browser profile and recovery record.
  2. Resolve every pending action on the relevant chain or provider.
  3. Do not clear history or resend merely because a request timed out.
  4. Moving a backup to another device or domain does not move transaction history or coordinate actions between devices.

Accounts, billing and holder access

Account sign-in and subscriptions

A wallet ownership message or email code authenticates your account when that sign-in method is available. Wallet accounts and email accounts stay separate; use your original method for an existing subscription. HttpOnly session cookies expire after one hour. Signing out revokes the session and locks the workspace. Stripe handles card details; use Manage subscription for billing.

HOODRICH verification

A short-lived message proves control of one standard wallet for this site and account session. It is not a transaction or approval and sends no private key.

Holder verification details

At least 666,666 $RICH must remain in one wallet on Robinhood Chain; balances across wallets are not combined. The service stores the linked public address, challenge and session proof. One wallet can link to one account. Unlinking removes the link and invalidates outstanding proofs.

Smart contract and delegated wallets are unsupported for this proof. Managed services check again; the workspace rechecks about every minute and on focus. Account changes or losing Pro eligibility lock the current wallet session without deleting backup files. Free accounts can restore any valid backup. An active subscription can still grant access.

Browser code can be inspected and copied. Pro provides a hosted service and supported workflow; it does not prevent access to wallets elsewhere.

Know what becomes public

  • Blockchain transactions and wallet addresses are public.
  • IPFS artwork is public and may persist after unpinning. Never upload private files.
  • RPC, Relay and IPFS providers can observe browser requests.
  • The authentication provider handles email or your public sign-in address and signed ownership message; Stripe handles billing records.
  • Exchange credentials and wallet keys never belong in account settings or Token Lab plans.

Live launching and billing remain off until configured and release-checked. A simulation or explorer response cannot guarantee execution, finality, value or protocol safety.