Firewallet

Documentation

Getting started

Overview of how to use FireWallet

Getting started

How to move funds from your current wallet into Firewallet — safely, in order, without cutting corners.

Firewallet is designed to sit between your old, exposed wallet and your new, clean wallet. The goal is simple: every coin you care about passes through Firewallet for conversion and routing, while your personal wallet ends up empty and disconnected.

Take your time. Rushing migration is how links get created between old and new identities.

Before you begin

  • You have a Firewallet account and can log in to the dashboard.
  • You understand that withdrawal routing only runs when your subscription is active.
  • You have a plan for where clean coins should land (payout destinations in Payment settings).
  • You are prepared to treat this as a one-way migration, not a temporary experiment.

Tip: Read the Security rules at the bottom before sending anything meaningful.

Step 1 — Activate your account

Send a small amount of any supported crypto to one of your Firewallet deposit addresses — enough to activate billing and confirm everything works.

Example: ~€20 in LTC.

This serves two purposes:

  1. Confirms deposits arrive and balances update correctly.
  2. Covers your subscription once enough balance is available (Firewallet bills automatically from incoming funds).

Wait until the deposit is visible in your dashboard before continuing.

Step 2 — Pause automated routing during migration

Open Payment → Withdrawal routing and set your Trigger threshold high — for example €1,000 — so no inbound conversion or payout runs while you are still moving funds in.

Why this matters:

  • Thresholds are evaluated per deposit address, not across your whole account.
  • A low threshold during migration could trigger conversions before you have finished depositing.
  • You want full control over when Firewallet starts processing your stack.

You will lower this to a comfortable level in Step 6.

Step 3 — Migrate your actual funds

Begin sending your real holdings to your Firewallet deposit addresses — receive addresses and/or payment links, depending on how you receive income.

Objective: your old personal wallet should hold nothing when you are done.

Practical notes:

  • You can spread deposits across multiple addresses and assets; Firewallet tracks each slot independently.
  • Use payment links where possible instead of handing out raw addresses — links survive address rotation.
  • Do not rush large transfers in a single block if your operational security calls for spacing them out.
  • Keep a private record of what you sent, when, and to which Firewallet address — not on a blockchain explorer (see Security rules).
  • When migration is done, retire the addresses you used: enable Rotation on BTC/LTC/XMR receive slots, or add a new receive address on other assets and stop sharing the old one. Delete old slots only if they are empty and unused — this tidies your wallet list; it does not remove on-chain history.

Step 4 — Burn the bridge: create a new personal wallet

Once your old wallet is empty, create a completely new personal wallet that has no provable connection to the old one.

Recommended separation:

Area What to change
Seed / keys New seed phrase — never reuse or derive from the old wallet
Device & network New IP / network path where practical
Funding No direct transaction from old wallet → new wallet
Storage Write down new credentials offline; store them securely

Your new wallet is for receiving clean payouts from Firewallet — not for receiving raw deposits from your old sources.

Step 5 — Disconnect your old wallet entirely

Fully remove ties between you and the wallet you are abandoning:

  • Unpair or wipe Ledger, Trezor, or other hardware devices tied to the old seed.
  • Log out and remove wallet apps (browser extensions, mobile apps, dApps).
  • Delete saved seed backups from cloud drives, notes apps, and password managers if they lived there.
  • Revoke any API keys, exchange deposit addresses, or invoicing tools still pointing at the old wallet.

If an app or device still has access to the old wallet, treat the migration as incomplete.

Step 6 — Configure routing for real use

When migration is done and only Firewallet holds your inbound funds, return to Payment settings:

  1. Trigger threshold — set a level that matches how much you want converted per batch (remember: per address, per coin rules apply).
  2. Payout destinations — where clean coins should be sent after conversion.
  3. Slicing, delay, and payout percent — tune how aggressively Firewallet moves value out.

Each enabled payout coin needs at least the platform minimum (currently €15 of the threshold allocation) to execute a trade.

Save only when settings pass validation — Firewallet will block unsafe combinations.

Step 7 — Let Firewallet work

With funds on Firewallet addresses and routing configured:

  1. Deposits accumulate on your receive/API slots.
  2. When a single address balance hits your threshold, Firewallet converts it (typically to Monero, per your pipeline).
  3. Outbound routing delivers clean coins to your configured destinations.

You do not need to babysit every transaction. Monitor the dashboard periodically, keep your subscription active, and adjust thresholds as your volume changes.

Sit back. Let the pipeline run.

Security rules

These are not suggestions. Breaking them can undo the entire point of using Firewallet.

1. Never look up your Firewallet addresses on public blockchain explorers

Explorers log queries and metadata. Law enforcement and commercial analytics firms have used honeypot explorers to correlate which IP checked which address with who likely controls those coins.

Use your Firewallet dashboard for balances and history — not third-party block explorers.

2. Never link your old wallet directly to your new wallet

No test transactions. No “just once” transfers. No shared exchange accounts funding both. Any direct on-chain or custodial link can chain your old identity to your new one.

Firewallet exists precisely to break that link.

3. Never receive coins directly to your new private addresses

Only Firewallet should convert inbound funds. Your new wallet receives output from Firewallet’s routing — not raw deposits from clients, employers, or exchanges.

If someone pays your new address directly, you have re-exposed it.

4. Never share your private wallet addresses

Your old addresses are already burned. Your new addresses should be known only to you and configured inside Firewallet as payout destinations.

Do not paste them into chats, invoices, support tickets, or explorer search bars.

Quick checklist

  • Account activated with a small test deposit
  • Trigger threshold raised during migration (e.g. €1,000)
  • All meaningful funds moved to Firewallet
  • Old wallet empty and disconnected from apps/devices
  • New wallet created with no link to the old one
  • Routing threshold and payout settings configured
  • No explorer lookups of Firewallet deposit addresses

Need help?

  • Dashboard → Support for account-specific questions
  • Footer links for Telegram and email

Welcome to Firewallet. Migrate once, migrate cleanly.