Skip to content

Limits & thresholds

The numbers below are the ones OPALE actually enforces today. They reflect the current configuration and may change as the bot evolves.

AssetConfirmations required to credit
BTC1 confirmation (typically 10–30 minutes)
Universal tokensSame as BTC — 1 confirmation

There’s also a small minimum deposit notification threshold: deposits below 750 sats don’t trigger a notification.

A sell listing must clear a small minimum total value to be valid:

ThresholdValue
Minimum total listing value883 sats

Below this, the listing transaction would fall under Bitcoin’s dust threshold once you account for the small postage that rides with it. Bump the amount or unit price to clear it.

OPALE does not enforce a per-transaction or per-day withdrawal cap today. 📨 Send BTC sweeps your full BTC balance to a destination of your choice.

If you need stricter controls (whitelist, 2FA, daily caps), the recommendation is to reveal your recovery phrase and use a self-custody wallet for amounts that warrant it.

There’s no globally enforced minimum or maximum trade size — those are bounded by:

  • Per-listing minimums on WhiteNode (rare to hit in practice).
  • Bitcoin dust — a transaction with output values too small relative to its size will be rejected.
  • Your own balance.

Practically, very small trades are dominated by network fees (the smallest viable trade size moves with current network conditions). OPALE’s quotes show the absolute fee, so you can decide when a trade is too small to be worth it.

ThresholdValue
Minimum claim$2 USD equivalent in BTC
Payout cadenceContinuous accrual; payout job runs every 30 s when above minimum
Tier 1 shareFirst 50 codes — 35 % of operator fee
Tier 2 shareCodes 51–300 — 30 %
Tier 3 shareBeyond 300 — 25 %
Code length4–32 alphanumeric characters

See referrals for the full program.

OPALE shows the funded home view (with trading actions) only after your balance crosses $2 USD equivalent in BTC. Below that, you see the deposit-first nudge instead. This keeps new users from hitting “insufficient balance” on every action — it’s UX, not a hard restriction.

Telegram-side rate limits are mitigated by anti-rate-limit wrappers in OPALE — you shouldn’t see a “too many requests” toast under normal use. If you do, slow down for a few seconds; the bot will resume normally.

There are no per-command spam limits beyond what Telegram itself enforces.