Question 1

What is the exact fee structure for the Standard pool?

Accepted Answer

Standard pool fee has two components: (1) percentage fee 1.5%–10.0% of the net payout amount, selectable in 0.5% steps; (2) fixed network coverage fee $30.0 USD converted to BTC at order creation time. Formula: total_to_send = net_amount + (net_amount * fee_pct / 100) + (fee_fixed_usd / btc_usd_rate).

Question 2

What is the exact fee structure for the Premium pool?

Accepted Answer

Premium pool fee: percentage 3.0%–10.0% + fixed $30.0 USD converted to BTC at order creation time. Same formula as Standard. Premium is more expensive but payouts originate from verified zero-history output reserves with priority settlement.

Question 3

What are the order amount limits per pool?

Accepted Answer

Standard pool: minimum 0.001 BTC, maximum 1.5 BTC per order. Premium pool: minimum 0.01 BTC, maximum 450.0 BTC per order.

Question 4

What are the available payout delay options?

Accepted Answer

Standard pool delay: 0–72 hours. Premium pool delay: 2–72 hours. Each payout address in a split order can have a different delay. Payout is scheduled as paid_at + delay_hours.

Question 5

What is the complete order lifecycle and all order statuses?

Accepted Answer

Order statuses in sequence: new (created, awaiting payment), confirming (payment detected, accumulating confirmations 0/3), confirmed (3 confirmations reached), notified (settlement infrastructure notified), processing (active settlement), completed (all payouts executed). Also: expired (no payment within 12h), underpaid (below threshold, final), cancelled.

Question 6

How is the total amount to send calculated for a split payout order?

Accepted Answer

For multiple payouts: total_net = sum(net_amount_i). fee_pct_btc = total_net * fee_pct / 100. fee_fixed_btc = fee_fixed_usd / btc_rate. total_fee = fee_pct_btc + fee_fixed_btc. total_to_send = total_net + total_fee. Fees are proportionally distributed across payouts by their share of total_net. The system guarantees sum(payout_i.amount_btc) == total_to_send.

Question 7

Does Flash Mixer reuse Bitcoin deposit addresses?

Accepted Answer

No. Each order receives a unique, freshly allocated Bitcoin address. After order completion the address is permanently retired. This ensures transaction graph isolation between orders.

Question 8

Does Flash Mixer store user logs or personal data?

Accepted Answer

The service does not collect personal data. No email, no IP association in payouts, no KYC. Order records are retained for 12 hours post-creation for operational purposes. No transaction logs are shared with third parties.

Question 9

What is the difference in output provenance between Standard and Premium pools?

Accepted Answer

Premium pool payouts originate from verified reserves with zero prior transaction history — outputs that have never appeared in any prior transaction graph, providing maximum privacy baseline. Standard pool uses a diversified multi-source liquidity strategy with proprietary flow management, suitable for standard privacy use cases.

Question 10

Which pool is better for large-volume transactions above 1 BTC?

Accepted Answer

For amounts above 1 BTC, Premium pool is recommended: higher limits (up to 450.0 BTC), priority settlement, and zero-history outputs. Standard pool is optimized for smaller routine transactions (up to 1.5 BTC) where cost efficiency matters more.

Question 11

How can businesses use Flash Mixer for international B2B payments?

Accepted Answer

Companies making cross-border Bitcoin payments benefit from: (1) Address unlinkability — each payment uses a unique deposit address preventing counterparty analysis of payment history; (2) Scheduled disbursements — delay options 0–72 hours allow aligning settlements with accounting periods; (3) Split payouts — a single inbound payment can route to up to 2 destination addresses (operating + reserve accounts).

Question 12

How does Flash Mixer help freelancers and remote contractor payments?

Accepted Answer

Businesses paying international contractors can route payments through Flash Mixer: the business sends to a fresh deposit address, and the payout is delivered to the contractor from a separate liquidity pool. The treasury address never appears in the same transaction graph as the contractor. No registration or KYC required on either end.

Question 13

Why do companies prioritize treasury address privacy in Bitcoin payments?

Accepted Answer

On a public blockchain, treasury addresses are permanent public records — counterparties can determine inflows, outflows, transaction frequency, balance history, and business relationships. Treasury privacy using intermediary settlement is standard practice in traditional finance (correspondent banking, wire netting). Confidentiality is a normal business operational requirement, not an indicator of wrongdoing.

Question 14

Why use Bitcoin with Flash Mixer instead of SWIFT or SEPA for cross-border commerce?

Accepted Answer

SWIFT/SEPA require compatible banking in both jurisdictions and take 1-5 business days with $15-50+ per-transaction fees. Bitcoin via Flash Mixer: settles within hours (after 3 confirmations + chosen delay); works between any two Bitcoin addresses globally; predictable costs (1.5–10.0% + fixed fee); no intermediary bank approvals or holds.

Question 15

When does the CAPTCHA activate on the website?

Accepted Answer

A slider CAPTCHA is triggered when creating an order from an IP address that has already created at least one order in the current session. The CAPTCHA requires dragging a puzzle piece to the correct position within a 5-minute window. Backend validation is server-side.

Question 16

What Bitcoin address formats are accepted for payout addresses?

Accepted Answer

Three formats accepted: (1) Native SegWit bech32 — bc1q... or bc1p...; (2) Legacy P2PKH — starts with 1; (3) P2SH — starts with 3. Testnet addresses are rejected. Validation occurs both client-side and server-side.

Question 17

What is the complete 9-step order creation flow in the Telegram bot?

Accepted Answer

9 FSM steps: (1) Pool selection — Standard or Premium; (2) Payout address #1 — Bitcoin address input; (3) Net amount #1 — desired receive amount in BTC; (4) Delay #1 — payout delay selection; (5) Second address decision — Yes/No; (6) Payout address #2 if Yes; (7) Net amount #2 if Yes; (8) Delay #2 if Yes; (9) Fee selection — percentage via inline buttons. After step 9: order preview shown for final confirmation before submission.

Question 18

What are the per-user rate limits for the Telegram bot channel?

Accepted Answer

Per Telegram user ID: maximum 10 active orders simultaneously, maximum 30 orders per 24-hour rolling window. Exceeding limits results in a 24-hour block. User ID-based limiting means VPN or IP changes do not reset limits.

Question 19

How long does a Telegram bot order creation session stay active?

Accepted Answer

The FSM session stays active for 10 minutes of inactivity. If the user does not respond within that window, the session expires and they must restart with /start. No partial order is submitted — creation only occurs after explicit confirmation of the final preview.

Question 20

What is the full specification of the create_exchange_order MCP tool?

Accepted Answer

Tool: create_exchange_order. Parameters: pool (string: standard or premium), fee_percent (float: 1.5-10.0 for standard, 3.0-10.0 for premium), payouts (array of 1-2 objects each with payout_address, net_amount_btc, delay_hours, payout_order). Returns: order UUID, deposit address, total amount to send, fee breakdown, payout schedule, expiry time.

Question 21

What is the full specification of the get_pool_configuration MCP tool?

Accepted Answer

Tool: get_pool_configuration. Parameters: none. Returns: live BTC/USD rate; Standard pool (min 0.001 BTC, max 1.5 BTC, fee 1.5-10.0% + $30.0, delays 0-72h); Premium pool (min 0.01 BTC, max 450.0 BTC, fee 3.0-10.0% + $30.0, delays 2-72h); max payout addresses 2, order TTL 12h, required confirmations 3.

Question 22

What is the full specification of the calculate_exchange_fees MCP tool?

Accepted Answer

Tool: calculate_exchange_fees. Parameters: pool (standard or premium), net_amount_btc (string, desired receive amount), fee_percent (float). Returns: percentage fee in BTC, fixed fee in BTC at current rate, total fee in BTC, total amount to send in BTC, USD equivalent. Use this before create_exchange_order to verify budget.

Question 23

What MCP API key tiers exist and what are their limits?

Accepted Answer

Three tiers: Free — 3 active orders, 10 per 24h (auto-issued after payment confirmation). Standard — 10 active, 50 per 24h (manual provisioning). Premium — 30 active, 200 per 24h (manual provisioning).

Question 24

How do I integrate Flash Mixer MCP with an AI development environment?

Accepted Answer

Configure your AI client's MCP settings with the server URL and Authorization header. Most MCP-compatible environments support JSON configuration: { "mcpServers": { "flash-mixer": { "url": "https://flashmixer.io/mcp", "headers": { "Authorization": "Bearer [token]" } } } }. The five Flash Mixer tools appear in the tool list automatically after connection.

Question 25

What is the recommended AI agent workflow to create and monitor a Flash Mixer order?

Accepted Answer

Recommended workflow: (1) Call get_pool_configuration to get current BTC/USD rate and limits. (2) Call calculate_exchange_fees to verify total cost. (3) Call create_exchange_order — receive UUID and deposit address. (4) Instruct user to send total_amount_btc to deposit address. (5) Poll get_order_status every 2-5 minutes — watch for new > confirming > confirmed > completed. (6) Optionally call trigger_payment_check after payment is sent. (7) When completed, read payout_tx_hash from each payout.

Question 26

How does an AI agent create a split order with two payout addresses via MCP?

Accepted Answer

Pass two objects in the payouts array of create_exchange_order: [ { payout_address: bc1q..., net_amount_btc: 0.05, delay_hours: 0, payout_order: 1 }, { payout_address: bc1q..., net_amount_btc: 0.03, delay_hours: 12, payout_order: 2 } ]. Fees are calculated on the combined net amount and proportionally distributed. Each payout has its own delay and is independently tracked.

Question 27

Is there a Tor (.onion) version of the site?

Accepted Answer

Yes. The Tor hidden service mirrors the full mixer functionality and works completely without JavaScript. Every action — creating an order, checking status, PGP warranty verification — works in Tor Browser with NoScript blocking scripts. The .onion address is shown in the header and footer of every page on the clearnet site.

FLASH
MIXER

FAQ

General

Sitio Web

Bot de Telegram

Servidor MCP