Skip to content
Blind
Two iridescent hands holding a luminous eye whose pupil is a camera aperture
Privacy payments · Beldextestnet · signer live

Blind

Send · claim · settle

Send and receive payments with absolute privacy.

Protect your financial history. Send and receive digital cash on Beldex without exposing your balances or transaction records. The recipient is never handed your wallet address; you are never handed theirs.

Google, X, or a Beldex wallet signature. Blind asks for no seed phrase, no view key and no private key — it has no field for one.

bp_9Qx2

12.5 BDX

link created

br_4mT7

180 BDX

deposit confirmed

bp_1kJ8

0.75 BDX

settled · 11 conf

br_7Zp3

42 BDX

waiting to be paid

bp_5Vn1

3.2 BDX

expired, refunded

bp_2Hs6

950 BDX

claim in progress

bp_9Qx2

12.5 BDX

link created

br_4mT7

180 BDX

deposit confirmed

bp_1kJ8

0.75 BDX

settled · 11 conf

br_7Zp3

42 BDX

waiting to be paid

bp_5Vn1

3.2 BDX

expired, refunded

bp_2Hs6

950 BDX

claim in progress

No address exchange

The payer never receives the recipient's wallet address, and the recipient never receives the payer's. A link carries a reference, not a wallet.

No seed phrase, ever

Blind has no field for a seed phrase, a view key or a private key. Signing in is a signature from your own wallet, not a secret handed over.

Custody in the open

A link anyone can claim needs somebody to hold a key while the payment is in flight. Blind names that custodian in writing before you use it.

Blind Pay

Fund it now, hand it over later.

You pick an amount and Blind creates a one-time deposit address. Your wallet sends the money; Blind sees it arrive, counts confirmations, and hands you a link with the claim secret in the URL fragment: the part a browser never sends to a server.

  1. 1. Deposit lands on a fresh escrow subaddress.
  2. 2. The recipient opens the link and connects a Beldex wallet.
  3. 3. Their wallet approves a payout to their own address.
  4. 4. Blind verifies the payout against the chain and issues both receipts.
Blind Request

Ask to be paid without publishing your address.

The request link carries an amount and a description, not your address. Whoever pays sends to a one-time escrow address; the money is forwarded to your wallet. The payer’s wallet never learns where it went, and you never learn where it came from.

  1. 1. You name an amount and a payout address Blind verifies.
  2. 2. You share a link or QR code built from the request reference.
  3. 3. The payer approves one transaction, to the escrow.
  4. 4. Blind forwards it and records the settlement hash.

What Blind can see, written down before you use it.

Blind does not get
  • the payer's wallet address or balance
  • the recipient's balance or transaction history
  • the identity behind either wallet beyond the address itself
  • your seed phrase, spend key or view key: there is no code path that could accept them
Blind does get
  • the amount and time of each deposit
  • the payout address chosen by the recipient
  • which claim link was opened (unless the fragment is never loaded)
  • a sealed copy of each claim secret, so you can re-copy a link you own
The custody, named

Deposits sit in a Blind-controlled escrow wallet until claimed, refunded or expired.

Beldex has no on-chain scripts, so a claimable link cannot be trustless. Blind makes the window explicit: one fresh address per payment, a payout only to the destination the claim recorded, and a hot balance cap checked before every send.

Right now, on this deployment
Databaseconnected
Verification nodenot configured
Escrow signerconfigured
Confirmations required10

Blind prints its own missing pieces. When the escrow signer is absent, the funding buttons say so instead of pretending a payment exists.

Ready when you are

Send your first private payment.

Create a link that waits for whoever you send it to, or ask to be paid without publishing your address. Neither side ends up holding the other’s wallet history.