Blockchain Verification

Social RV uses the blockchain to prove sessions are truly double-blind. Blockchain sessions are precognitive, meaning the target is assigned after the session is submitted. This means no human could have known which target would be assigned beforehand, making it cryptographically impossible for anyone to have influenced or predicted the outcome.

📋How Our Blockchain Verification Works

Understanding the lifecycle that makes sessions provably blind

1
Target Pool Creation

We store a list of target image fingerprints (SHA-256 hashes) on the Solana blockchain for our target pool, and we lock the set so it can't be modified further. This creates a permanent, immutable list of possible targets that will later be assigned to sessions via our Solana program.

2
Session Submission

You complete your remote viewing session and upload it. We submit a transaction to the Solana blockchain which includes a fingerprint of the session files, and a list of up to the last 50 targets you've done (so you don't get duplicate targets too frequently). At this point no one, not even Social RV, knows which target will be assigned yet.

3
Target Assignment

The Solana blockchain finalizes our submitted transaction by including it in a new block. We retrieve the blockhash generated by the Solana validators for this new block, and use it as the random seed to select a target from our target pool. This blockhash is cryptographically unpredictable and cannot be influenced by us or anyone else.

We submit a second transaction which includes the blockhash from the first transaction, so our blockchain program can use it to select a target from the target pool and assign it to the session.

🔐
Why This Guarantees Blindness

The target is selected using randomness that didn't exist when the session was submitted. The pool is sealed so targets can't be changed. All data is on-chain and independently verifiable.

Below, you can verify each step yourself.

🔍

Verify a Blockchain Session

To verify any blockchain session, click the Blockchain Verified button in the header of a session page.

Want to see how it works? We've loaded a sample blockchain-verified session below. Follow each step to see how every piece of data can be independently verified on the blockchain.

Verifing a Specific Session

Follow each step below to independently verify that a session was recorded on the Solana blockchain and the target was randomly assigned after submission.

Session Metadata

Session ID:6152f372-d919-48ff-b58e-cc3cd3d292b2
Session Image(s) Fingerprint (SHA-256 Hash):04ab1165539ccdf18c3a6bb2b6b86577a3bdcfb02e80f5060d19f83412bf4fe2
Target Image Fingerprint (SHA-256 Hash):98bbd3a6bd9b32900e715c08f4a685728755ee65aaeb29db5e961a5c86a4aec1
Target Pool ID:pool_1754450745059
Target Pool Index #:76
Submit Transaction Blockhash:2BvLRMxrXZiGiPQZHLrtcSzqv8XXFcQYGyLsVSQht86Z
Solana Explorer Page:
Assigned Target Image:
Target

Right-click to save the image for hash verification

Session Images:

Files

Preview