VaultChain

Encrypt a file with AES-256-GCM, build an indexed Merkle tree, upload to a provider, and create a deal on Base Sepolia. All in your browser.

Wallet

not connected

Provider

connect wallet first

Select a provider (discovered from the on-chain directory)

Manual override

Provider URL

Provider address

File

Pick a file to encrypt and store

Encryption passphrase (used for AES-256-GCM key derivation)

Chunk Replication (R)

Each chunk stored on R providers. Lower R = more distributed (torrent-style). Uses ALL healthy providers.

1 provider

Higher = more resilient. Each copy creates a separate on-chain deal (1 VLT each). MetaMask will ask you to confirm each deal individually.

Run

idle

Heal (re-replicate)

If a provider goes down, load your metadata JSON to detect dead providers and re-replicate chunks from survivors to a fresh replacement.

Metadata JSON (from your original upload)

Passphrase (needed to verify chunk integrity)

idle

Restore file

Download chunks from your providers, decrypt, and recover the original file. If a provider is down, the client automatically falls back to the next one.

Metadata JSON (the file you downloaded after uploading)

Passphrase (same one you used to encrypt)

idle

Wallet

Provider

File

Chunk Replication (R)

Run

Heal (re-replicate)

Restore file

Activity log