Firewallet

Documentation

Shield Balance Payout

How does the remaining shield balance

When a deposit hits your trigger threshold, Firewallet converts it to XMR and routes it through your shield address. This doc explains what happens to that XMR on the way out — and why you have two related controls (payout % and trigger threshold) instead of one.

The short version

Each conversion does not send 100% of its XMR to your exit wallets immediately. You choose a payout % (typically 85–90%). The remainder stays in your shield wallet until it adds up enough to trigger a balance sweep — a separate exit that sends accumulated shield XMR to your payout destinations.

Think of it like birthdays: each time you get a cake, you eat most of it — but a small slice is set aside. Those slices pile up; once you have enough for a full cake, you eat that whole batch on its own, separate from any single birthday.

Payout % per conversion

Deposit-linked flow runs tie a specific inbound deposit to an outbound path. If every conversion paid out 100% of its XMR right away, the amount leaving your wallet would often match the amount that just arrived — making it easier for an observer to link “this deposit” to “this payout.”

Payout % is the privacy knob for that link. At 90%, roughly nine tenths of each conversion’s XMR continues through your normal outbound routing (delay, batching, destination split). The other 10% is deliberately not sent on that run. It stays as XMR in your shield wallet.

That retained slice is usually small per conversion — often a few euros to a few tens of euros, depending on deposit size and your threshold. Over several conversions it accumulates.

Balance sweep — when the rest leaves

Retained XMR is not lost or stuck in a separate account. It is normal shield balance, visible on your Monero wallet page.

Firewallet periodically checks whether that balance should exit via a balance sweep:

  1. No withdrawal activity in progress — no deposit-linked run or outbound swap is already using the shield wallet.
  2. Available shield XMR reaches your trigger threshold — the same slider you use for inbound routing.

When both are true, Firewallet sweeps all available shield XMR to your payout destinations. This is a direct XMR exit; it does not start another inbound swap (e.g. TRX→XMR).

You will see sweeps in withdrawal activity as Balance sweep (XMR → payout (balance sweep)). On the shield address card, the line under “Hidden for your security” shows how much EUR is left until the next sweep when one is pending.

How the two settings work together

Setting What it controls
Payout % How much XMR leaves with each deposit-linked conversion vs. how much is held back in shield
Trigger threshold (€) When accumulated shield XMR is large enough to sweep (and when inbound deposits start converting)
Payout destinations Where swept XMR — and routine outbound XMR — is split on exit

Example: Trigger €500, payout 90%. A €500 TRX deposit converts to ~€500 of XMR. About €450 continues on the deposit-linked outbound path; ~€50 stays in shield. After several conversions (or one large one with a lower payout %), shield balance crosses €500 while idle → balance sweep sends the accumulated XMR out.

Lowering payout % retains more per conversion (stronger unlinking per deposit, slower sweeps). Raising it pushes more out per run (faster exits, less retained per conversion).

What to expect

  • Shield balance growing between sweeps is normal when payout % is below 100%.
  • A sweep will not run while another withdrawal is in progress, even if shield balance is above threshold — you may see “Withdrawal activity in progress” on the shield card.
  • Set payout % below 100% for balance sweeps to be possible; at 100% nothing is retained in shield for this mechanism.

Related