Encryption Tool

WHAT IT DOES

Encryption Tool provides client-side symmetric encryption and decryption using AES-256 in GCM or CBC modes. Enter data, a secret key (hex, 32 bytes for AES-256), and an initialization vector (IV), and the tool encrypts or decrypts the data entirely in your browser. It supports AES-256-GCM (authenticated encryption with additional data) and AES-256-CBC (cipher block chaining). The tool also includes random key and IV generation using the Web Crypto API's cryptographically secure random number generator. This is essential for developers testing encryption workflows, securing sensitive data before storing or transmitting it, and understanding cryptographic operations in a blockchain context.

HOW TO USE

Connect your wallet using the BGWallet bridge (MetaMask or any Web3 wallet). Select the mode: "Encrypt" or "Decrypt." Choose the algorithm: AES-256-GCM (recommended, provides authentication) or AES-256-CBC (legacy, padding required). Enter a secret key as a hex string (0x + 64 hex characters for AES-256). You can generate a random key using the "Generate random key" button. Enter the data to encrypt (plaintext) or decrypt (hex-encoded ciphertext). For encryption, an IV will be automatically generated if not provided; for decryption, you must provide the IV (extracted from the encrypted data or entered separately). Optionally, provide an IV manually — 12 bytes for GCM, 16 bytes for CBC. Click "Execute" to perform the operation. Results display the mode, algorithm, status, and the encrypted ciphertext (hex) or decrypted plaintext.

TECHNICAL MECHANISM

The tool uses the Web Crypto API (SubtleCrypto) available in all modern browsers, which provides hardware-accelerated cryptographic operations. For AES-256-GCM, the key is imported using crypto.subtle.importKey() with the AES-GCM algorithm and encrypt/decrypt usages. The IV must be 12 bytes for GCM. For AES-256-CBC, the key is imported with AES-CBC, and the IV must be 16 bytes. Encryption is performed using crypto.subtle.encrypt() with the appropriate algorithm parameters, and decryption uses crypto.subtle.decrypt(). For GCM encryption, the IV is prepended to the ciphertext in the output (IV + ciphertext), allowing the IV to be extracted during decryption. For CBC, the IV must be provided separately or stored with the ciphertext. The tool handles hex encoding/decoding for keys, IVs, and ciphertext. All operations are performed client-side — no data is sent to any server or stored. The random key and IV generation uses crypto.getRandomValues() for cryptographically secure randomness.

WHAT IT CANNOT SEE

The tool cannot decrypt data without the correct key — it has no ability to recover or derive keys from encrypted data. It cannot encrypt data using keys derived from on-chain data without user input — the key must be provided by the user. It cannot guarantee security against quantum attacks — AES-256 is considered quantum-resistant against Grover's algorithm (reducing effective key size to 128 bits), but the tool does not implement post-quantum cryptographic algorithms. It cannot verify the integrity of encrypted data without additional checksums or signatures — GCM provides authentication, but CBC does not. It cannot encrypt data that exceeds reasonable size limits for client-side operations — very large files may cause memory or performance issues in the browser. It cannot decrypt data that was not encrypted with the same algorithm, mode, and key. The tool does not interact with the blockchain for encryption operations.

PLEASE NOTE

This tool works exclusively on EVM-compatible chains for the wallet connection, but the encryption itself is client-side and chain-agnostic. Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported for wallet connection but the encryption tool itself is browser-based and works regardless. AES-256-GCM is the recommended mode as it provides authenticated encryption (AEAD). AES-256-CBC requires padding and does not provide authentication — use with caution. The tool does not store any data — all operations are performed client-side. The tool is provided as-is with no warranty or liability. Never share your encryption keys with anyone. This is not a substitute for professional security audits.