How to verify crypto ownership without taking custody

Non-custodial verification in four steps

• You create a verification request for a customer and choose the assets (and networks or exchanges) to prove. The customer receives a secure portal link.
• The customer proves ownership from their own wallet (message signing) or exchange (read-only API key).
• Scrya checks balances on-chain via explorers/RPCs or live against the exchange API; wallet proofs enter a 24-hour monitoring window until confirmed or expired.
• You download a tamper-evident PDF certificate that records what was verified, when, and by which method.

Wallet proofs

The customer signs a human-readable message tied to the verification request. Supported schemes are EIP-191 personal_sign on EVM networks, TIP-191 on Tron, ed25519 on Solana, and BIP-137 Bitcoin signed messages for legacy, nested-segwit, and native-segwit addresses. Private keys never leave the customer’s wallet; Scrya cannot move funds. Taproot (BIP-322) message signing is not supported.

Exchange proofs

For exchange-held assets, the customer grants secure, read-only API access. Where an exchange exposes key-permission metadata, keys with trading, transfer, or withdrawal rights are rejected before any balance is read.

Why monitoring matters

A wallet signature proves control of an address; monitoring then confirms the balance through that network’s explorers and RPCs. Scrya’s monitoring window is 24 hours — long enough to complete confirmation, short enough that stale in-progress checks expire cleanly instead of lingering indefinitely.