0g sign

Descripción

🔐 Encrypted Upload

Documents are encrypted with AES-256 on the client side before upload. Encryption keys never leave your browser — only you and authorized signers can decrypt.

✍️ Wallet Signing

Sign with EIP-712 typed data — zero gas fees, cryptographically verifiable. Each signer receives a clear, human-readable confirmation in their wallet.

🌐 Permanent Storage

Files are stored on the decentralized 0G Network with content-addressed root hashes. No single point of failure, no subscription fees.

🔗 Shareable Links

Create a signing request and share the link. Counterparties open it, connect their wallet, and sign — no account required.

✅ On-Chain Verification

Verify document integrity and signer authenticity via root hash. Export cryptographic proof as JSON for auditing.

🎨 Dark Glass UI

Modern dark theme with glassmorphism effects, gradient accents, animated background orbs, and a step-by-step tutorial right on the homepage.

Progreso del hackathon

Built a Web3 document signing DApp on 0G Storage with the following core features:

1. Encrypted Upload — Files are encrypted client-side using AES-256 before uploading

to the 0G decentralized storage network. Keys are managed by the user's wallet — the

server never sees plaintext.

2. Content Addressing — Each file generates a unique Merkle Root Hash, serving as its

decentralized identifier with on-chain integrity verification.

3. EIP-712 Signing — Users sign document hashes on-chain via MetaMask. Signatures are

publicly verifiable and provide a foundation for legal validity.

4. Zero Single Point of Failure — Files are distributed across multiple 0G storage

nodes. No centralized server dependency, no subscription fees.

5. Dual-Mode Architecture — Supports browser-side direct upload (MetaMask signed) and

server-side fallback upload,兼容 both wallet and non-wallet users.

Tech Stack: Next.js, TypeScript, ethers.js, 0G Storage SDK, Wagmi, AES-256 Encryption

Current Status: Core upload and signing flow completed. Debugging testnet node

compatibility issues.