From CSV to a verifiable sample
- The buyer creates a room, saves both private links and sends the seller link to the seller.
- The seller accepts the terms, selects the CSV locally, saves the private recovery JSON and registers the commitment.
- The buyer creates a quote for their own sending wallet. They send the exact native USDC total on Base and submit the transaction hash once.
- DataPeek checks both providers and automatically retries pending confirmation for up to 24 hours. Do not pay again while waiting.
- Once paid, the buyer selects record numbers once. The seller makes the sample JSON locally and sends it directly to the buyer.
- The buyer selects that sample JSON and verifies it locally. Reloading the page does not retain the local verification result; choose the same file to verify it again.
Supported CSV
UTF-8; comma, semicolon or tab delimiter; up to 50 MiB, 100,000 records and 100 columns. Choose between 10 and 1,000 sample records; the dataset must contain more rows than the sample. Do not use this release with personal, medical, sensitive or unlawfully obtained data.
Private files and links
Keep the buyer link, seller link and seller recovery file private. Send only the sample JSON to the buyer. Access links are bearer credentials: anyone holding one can use its role. There is no account-based recovery. The room lasts 72 hours.
A payment is pending
Keep the original transaction hash. A successful transaction in an explorer may still be waiting for both RPC providers to report finality. A completed transfer must not be repeated. When automatic checks stop, use “Check existing payment” or contact support. The invoice send-by deadline limits the transfer’s block time, not how long you can wait for confirmation.