Prove a Wallet

Connect the wallet you want to prove. Its address is the wallet in the report, you never type it. The chain is read, never written to, until you choose to publish. Sign the short ownership challenge so a lender trusts the report, only the owner of the key could have made it. Once you sign, your wallet snapshot is fetched automatically. Publishing in step 4 is a transaction from the same wallet.

Connect wallet

Not connected. Meteor and MyNearWallet are supported.

Prove my connected wallet instead

Sign ownership challenge

Fetch the onchain snapshot for the wallet from step 1, then set the policy and evaluate. Leave a policy field blank to skip that claim. Thresholds are in NEAR. Windows are in days. A minimum tx count or volume needs its window.

Optional. Your recent transactions are detected automatically when the snapshot is fetched, so you do not need to paste anything. Use this box only for older transactions, or for incoming transfers sent by someone else. A bare hash is assumed to be yours; use hash,senderId for incoming transfers. Hashes that cannot be verified onchain are skipped.

Linking more wallets aggregates their balances, volume and activity into one report, an agent's treasury is usually spread across wallets. Each linked wallet proves ownership in one of two ways: a small transfer to the primary address (below), or, no transfer, no gas, by signing a short link statement. Leave the hash blank for a wallet you will link by signature instead.

Sampling reads the balance at past block heights, so the report can prove a balance was HELD, not just deposited an hour ago. Type any number of days, there is no limit. The account must be older than the window you pick.

Fetch snapshot

Aggregate claims sum across every linked wallet (a transfer between two of your own wallets is counted once). Sustained and time weighted claims need balance sampling above.

Evaluate claims

Choose which evaluated claims go into the public report. Claims you leave out are simply absent from the report, the verifier never sees them unless you disclose them another way.

Underwrite with NEAR AI Build report

The underwriting judgment is advisory: NEAR AI Cloud reads the deterministic score and claim facts (never your address) and gives a lend / lend with limits / decline verdict with a suggested limit. The score itself is the verifiable fact, any app can recompute it from the disclosure package.

AI analysis not run yet. The report will say "not analysed" unless you run it.

Download report JSON Download disclosure package JSON

Verifier bound disclosure (P4): paste one verifier's encryption public key (Curve25519, base64, they generate it with the "Generate verifier key" tool on the verify page) and the disclosure package is sealed so only that verifier can open it. The sealed package expires with the report.

Verifier encryption public key (base64)

Encrypt disclosure for this verifier Download encrypted disclosure JSON