dropclaw-store_skill

Overview

This skill provides permanent, encrypted file storage on the Monad blockchain via the DropClaw x402 gateway. It performs client-side AES-256-GCM encryption so servers never see your keys, and uses an x402 HTTP payment flow to record storage on-chain. The service stores compressed, encrypted blobs and returns a skill file you must keep along with your key to retrieve data later.

How this skill works

You encrypt files locally using a randomly generated 32-byte AES key and a 12-byte IV, compress with zlib, and wrap the result as [IV][AuthTag][Ciphertext]. A POST to /vault/store returns a 402 with payment options; after paying on your chosen chain you resend the request with an X-PAYMENT header containing the payment proof. Retrieval uses the saved skill file to request the encrypted blob, which you then decrypt and decompress locally and verify with the original SHA-256 hash.

When to use it

• Permanent archival of important files where long-term availability is required.
• Storing sensitive data that must remain confidential and accessible only with a client-held key.
• Backup of critical project versions, releases, or legal records with on-chain proof of storage.
• Use when you can accept an upfront storage fee (approx. $30 + gas) and free retrieval.

Best practices

• Always save both the returned skill file and your encryption key in multiple secure, offline locations.
• Generate keys and perform encryption/decryption client-side; never share the AES key with the server.
• Compute and record the original SHA-256 hash before storage to verify integrity after retrieval.
• Store payment receipts and transaction hashes for x402 flows to simplify dispute resolution.
• Test retrieval and decryption on non-critical files before committing important archives.

Example use cases

• Archiving open-source project releases so every version is permanently accessible.
• Storing immutable legal contracts or notarized documents with client-side confidentiality.
• Backing up configuration snapshots or database dumps for long-term disaster recovery.
• Preserving academic or research datasets that require integrity proof and permanent hosting.