Check any supported public address, then publish a balance snapshot backed by a confirmed payment from that same address.
PUBLIC ADDRESS LOOKUP / NO SEED PHRASES / NO CUSTODY
0
Verified proofs
$0
Total proven
4
Supported assets
0
Duels settled
01 / The evidence
Leaderboard
Public balance reads. Same-address payments. Real balances.
#
Account
Asset
Balance
Status
SERVER VERIFIED / Proofs appear only after a same-address on-chain payment of at least $0.15 is confirmed.
02 / Put it to the test
Duels
Your balance against theirs. No screenshots needed.
Share a 24-hour invite and compare verified balance snapshots. No duel funds are staked or transferred.
03 / A simpler kind of proof
How it works
Four steps. No keys shared. No custody taken.
STEP 01
Choose how to sign in
Use Discord, Telegram, or a temporary anonymous alias. Sign-in is separate from address lookup; we never ask for your password.
STEP 02
Enter a public address
Paste any supported mainnet address. We read its public balance directly from the chain, without Phantom, MetaMask, or a wallet connection.
STEP 03
Pay at least $0.15
Send the displayed BTC, ETH, SOL, or LTC minimum within 15 minutes. Anything above it is a donation; network fees are separate.
STEP 04
Get verified
The backend keeps checking after you close the page. A confirmed transfer of at least $0.15 from the address you entered can create a proof.
The verification addresses
Small transfer. Real evidence.
Start a request before sending. Use only the native asset on its mainnet.
Send at least the request’s displayed crypto minimum, worth $0.15 at creation and rounded to the nearest smallest on-chain unit. Prices can change afterward. Any excess is a donation and is not refundable; network fees are separate. Receiving addresses and transactions are public. Exchange withdrawals cannot verify your wallet.
Sign in
Use Discord or Telegram, or continue anonymously. Public address lookup comes next.
We request basic profile information only, never your Discord or Telegram password. We do not post on your behalf.
Your profile
Your account is ready.
U
@
3–20 letters, numbers, dots, or underscores. Must be unique.
Get your proof
Choose a chain, paste any public address, preview its balance, then send the 15¢ proof payment from that same address.
PUBLIC LOOKUP
No wallet extension is required for lookup. Never paste a seed phrase or private key. The payment must still come from the address you enter.
Minimum $0.15 in crypto, converted when your request is created. Send at least the displayed amount from the public address above. Any excess is kept as a donation; network fees are separate.
live payment request
Waiting for payment
Bitcoin mainnet
Your private payment window is ready.
$0.15
Calculating amount…
1Send from your wallet
2Watch for confirmation
3Mint your proof
Receiving address
Watching for your payment
Balance checked
Same-address transfer confirmed
Payment sender matched the public address you entered. Balance was read from public chain data.
This is a server-checked balance snapshot, not a certified financial statement or proof of exclusive control. A transaction ID can reveal the sender on a public explorer.
Start a duel
Create a shareable challenge from a balance you have checked.
This 24-hour invite compares verified balance snapshots. No duel funds are staked or transferred.
Privacy policy
Last updated / 1 November 2026
1. Sign-in and public addresses
Discord and Telegram use their official authorization pages. You can also continue anonymously with a generated alias; no email or social profile is collected for that session. Balance preview reads public blockchain data for the address you enter. It does not connect to a wallet or prove that you control the address. Never enter a seed phrase or private key.
2. Server records and sessions
The backend stores payment requests, the public address entered for each request, proof records, transaction IDs, balance snapshots, and duel records on its configured persistent disk. Sessions are held in server memory for up to 24 hours and are lost if the server restarts. Provider access tokens are not saved. Anonymous accounts have a random alias and no recovery method. Payment requests expire after 15 minutes; shared receiving addresses and blockchain transfers remain public.
3. Public proof visibility
The leaderboard displays your chosen username, profile photo when available, sign-in provider, asset, balance, and verification time. Receipts include a transaction ID. An anonymous alias does not hide the payment or wallet on the public blockchain. A transaction ID can reveal your wallet address. Receiving addresses, amounts, and transfers are public and traceable. We cannot erase on-chain records.
4. External providers
Discord or Telegram processes your sign-in under its own policy. Balance and payment checks send public addresses and transaction IDs to blockchain explorer and RPC services, including mempool.space, Blockstream, Litecoin Space, Litecoin Explorer, BlockCypher, Routescan, PublicNode, and Cloudflare. Payment request creation also reads market prices from CoinGecko or Coinbase. Those services receive the server’s network information and the data needed for each lookup. Your browser requests fonts from Google Fonts, which may receive your IP address. The hosting provider may keep access logs and backups. These providers may retain their own records.
5. Essential cookies, not tracking
This version uses an HttpOnly session cookie for sign-in and a short-lived OAuth state cookie to secure authorization. They use SameSite protection and Secure on HTTPS. They are necessary for authentication, not advertising. No analytics, tracking pixels, or ads are included. New authorization and proofs are not stored in localStorage; older versions may have left legacy local records.
6. Your choices
You can decline social authorization, sign out, and clear legacy local records below. Signing out removes your current session but does not delete public proofs, pending backend payment checks, provider accounts, hosting logs, or blockchain transfers. Revoke social permissions using Discord or Telegram settings. Requests to access or remove off-chain records must be directed to the site operator once their contact is configured.
7. Payment and financial risks
Requests convert a minimum of $0.15 to native crypto at creation, rounded to the nearest smallest blockchain unit. Payments at or above the displayed minimum can verify; any excess is a donation to the site operator and is not automatically refunded. Fiat value can change with market prices; network fees are separate and may exceed $0.15. Transfers are irreversible. A balance snapshot is not financial advice, an audit, or proof of exclusive control. This service is intended for adults.
8. Before public launch
The site operator must configure official OAuth credentials, HTTPS hosting and durable private storage, and publish their identity, contact details, retention policy, applicable legal rights, and hosting-provider details. No operator contact is configured in this development build. Server-side checks improve verification but do not make this an independent audit or guarantee future balances. Duels compare verified balance snapshots only. No duel funds are staked, transferred, or paid out.
Server proofs, pending payment checks, and on-chain records remain unchanged.