Verification Strategies
Overview
Verification strategies in Wayfinder ensure data integrity and authenticity when fetching content from Arweave through AR.IO gateways. These strategies use cryptographic methods to verify that the data you receive matches what was originally stored on Arweave, protecting against tampering, corruption, or malicious gateways.
Why Verification Matters
- Data Integrity: Ensures content hasn't been corrupted during transmission
- Security: Protects against malicious gateways serving fake data
- Trust: Provides cryptographic proof that data is authentic
- Compliance: Meets security requirements for sensitive applications
Strategy Comparison
← Swipe to see more →
| Strategy | Security Level | Best For | Use Case | Verification Method |
|---|---|---|---|---|
| Hash Verification | High | Fast integrity checks and development | High-throughput applications | SHA-256 hash vs trusted gateway digest |
| Signature Verification | Very High | Authenticity validation and ownership proof | Financial or legal documents | Transaction signature validation |
| Data Root Verification | Highest | Maximum security and critical data | Production applications | Merkle tree data root comparison |
← Swipe to see more →
Important
Verification methods require that the gateway being used has the relevant transaction data indexed locally. Gateways cannot proxy out verification requests to other sources, as this would compromise the security and reliability of the verification process. If a gateway doesn't have the required data indexed, verification will fail.
Related
- Hash Verification: Learn about fast integrity checking
- Signature Verification: Understand authenticity validation
- Data Root Verification: Explore maximum security verification
- Wayfinder Core: See how to configure verification in your application