Learn & Resources

Everything you need to understand how 4EverFile protects your documents β€” from upload to permanent proof.

πŸ”— Platform Overview

4EverFile is a document management platform built on distributed ledger technology. When you upload a document, we generate a unique mathematical fingerprint (SHA-256 hash) and write it permanently to a public, tamper-proof ledger. This creates an irrefutable, timestamped record that the document existed in its exact form at that moment.

No central authority can alter or delete this proof. Anyone with the original file can independently verify it against the ledger β€” without needing an account, without seeing any private data, and without trusting a third party.

πŸ›‘οΈ Zero-Knowledge Architecture
We never read or analyze the contents of your documents. Only the cryptographic hash β€” a fixed-length string of characters β€” is recorded on the ledger. Your files remain completely private.

πŸš€ Getting Started

01
πŸ“€

Upload & Anchor

Navigate to Upload and drag-and-drop your file. A SHA-256 hash is computed instantly in your browser β€” before the file ever leaves your device. The hash is then queued for ledger anchoring, and you'll receive a transaction receipt once confirmed.

02
πŸ“

Manage Documents

Access all your anchored files in the Documents section. View anchoring status, organize files, request signatures, generate verification certificates, and track version history β€” all from a single dashboard.

03
πŸ”

Verify Authenticity

Use the Verify tool to check any document against the ledger. Drop a file into the verification zone β€” if it matches a previously anchored hash, the system mathematically proves its authenticity and original timestamp.

βš“ Document Anchoring

What is anchoring?

Anchoring is the process of permanently recording your document's cryptographic fingerprint on a distributed public ledger. Once written, this record is immutable β€” it cannot be altered, backdated, or deleted by anyone, including 4EverFile.

How does it work?

  1. Your browser computes a SHA-256 hash of the file β€” a unique 64-character string derived from the file's binary content.
  2. The hash is submitted to 4EverFile's anchoring service, which writes it to our on-chain smart contract on a high-throughput Layer-2 network.
  3. Once the transaction is confirmed (typically under 10 seconds), you receive a transaction hash β€” a permanent receipt linking to the public ledger record.
πŸ“ Why SHA-256?
SHA-256 produces a 256-bit hash that is computationally irreversible. Even a single byte change in the original file produces a completely different hash. This is the same standard used in banking, defense, and federal record-keeping.
πŸ” What can be verified?
Anyone with the original file can re-compute its hash and check it against the public ledger. If it matches, it proves the file existed in that exact form at the recorded timestamp β€” no trust required.

πŸ›οΈ Permanent Vault

Standard anchoring records the proof of your document on the ledger, but the file itself is stored on 4EverFile's encrypted cloud infrastructure. The Permanent Vault goes further β€” it stores the actual file on a decentralized, permanent storage network.

How is this different?

StandardPermanent Vault
Hash on ledgerβœ“βœ“
File on 4EverFile serversβœ“βœ“
File on permanent networkβ€”βœ“
Survives if 4EverFile shuts downHash onlyHash + File
♾️ True Permanence
Files stored in the Permanent Vault are written to a decentralized storage layer with a pay-once, store-forever model. Once uploaded, the file is replicated across a global network of nodes and can never be removed β€” even by us.

πŸ” Encryption & Key Management

4EverFile offers client-side encryption using a three-envelope key architecture. Your document is encrypted before it ever reaches our servers, and the decryption key is split across multiple independent recovery paths.

1

Platform Envelope

Managed automatically by 4EverFile. Used for seamless access when you're logged in. You never need to think about this key.

2

Recovery File

Protected by your personal passphrase. You download a .4evervault recovery file that works independently β€” even if 4EverFile ceases to exist.

3

Ledger Backup

The same passphrase-protected key is stored alongside your document on the permanent storage network. A last-resort recovery path that lives forever.

⚠️ Important
Your passphrase is never sent to our servers. If you lose both your passphrase and your recovery file, the encrypted document cannot be decrypted β€” by anyone, including 4EverFile. Keep your recovery materials safe.

✍️ Digital Signatures

4EverFile supports three types of digital signatures, each recorded in a tamper-proof hash chain attached to the document.

πŸ”‘

Cryptographic Signature

Paste your RSA private key to produce a mathematically verifiable signature. The strongest form of non-repudiation β€” proves the signer possessed the private key.

✏️

E-Signature

Draw your signature on a canvas pad. The drawn image is hashed and chained to the document record. Simple, fast, and legally recognized in most jurisdictions.

🌐

Wallet Signature

Connect a Web3 wallet to sign with your blockchain identity. The wallet address becomes a permanent, publicly verifiable part of the signature chain.

πŸ”— Hash Chain Integrity
Each signature is added to a sequential hash chain β€” every new entry includes the hash of the previous one. This means any tampering with earlier signatures would break the chain, making forgery mathematically detectable.

πŸ“‹ Approval Workflows

Send documents for multi-party review and approval. Each step in the workflow generates a unique, secure link for the reviewer.

How workflows operate

  1. From a document's detail page, click Request Signatures and add one or more reviewers (name, email, role).
  2. Each reviewer receives a unique, one-time approval link β€” no 4EverFile account required.
  3. Reviewers can Approve, Decline, or Request Changes, with an optional written response.
  4. All actions are recorded with timestamps and visible on the document's workflow panel.
πŸ”’ Secure by Design
Approval links are single-use, cryptographically random tokens. They cannot be guessed, reused, or transferred. Once a reviewer acts, the token is consumed.

πŸ… Verification Certificates

Generate a public, shareable certificate page for any anchored document. Certificates serve as self-contained proof β€” usable in courts, mediations, audits, or any setting requiring independent verification.

What a certificate contains

  • Document title and file metadata
  • SHA-256 content hash
  • Ledger transaction ID with link to the public record
  • Block number and confirmation timestamp
  • Permanent Vault status (if activated)
  • Verification badge showing current anchoring state
🌍 Always Live
Certificate pages always reflect the current, real-time status of the document. They are not static snapshots β€” they re-verify against the live ledger every time the page is loaded.

πŸ—ƒοΈ Document Archiving

Keep your active workspace clean by archiving documents you no longer need day-to-day. Archiving is non-destructive β€” the document's ledger proof and all associated data remain fully intact.

How archiving works

  1. From any document's detail page, click the Archive button and confirm.
  2. The document moves from your active Documents list to the Archive section.
  3. To restore, open the Archive, find the document, and click Restore.
βœ“ Blockchain proof is unaffected
Archiving only changes the document's organizational status within 4EverFile. The on-chain anchor, transaction hash, and verification certificate remain fully valid and accessible.

πŸ›‘οΈ Security Architecture

4EverFile implements enterprise-grade, multi-layer security across every stage of the document lifecycle.

πŸ”’ Encryption at Rest

All stored files are protected with AES-256 server-side encryption, managed automatically by our infrastructure. Data is encrypted the moment it arrives and remains encrypted on disk.

πŸ” Encryption in Transit

All connections use TLS 1.3 with modern cipher suites. Data moving between your browser, our servers, and storage backends is always encrypted end-to-end.

🧬 File Validation

Every upload undergoes multi-layer validation: magic byte verification, extension whitelisting, ZIP bomb detection, and SVG XSS prevention. Malicious files are rejected before processing.

🧱 Content Security Policy

Strict CSP headers prevent cross-site scripting, code injection, and unauthorized resource loading. All scripts and styles are authorized via nonce-based enforcement.

πŸ—‚οΈ Path Sanitization

Filenames are sanitized to prevent path traversal and shell injection. Downloads are served with nosniff and attachment headers to block browser-based execution.

πŸ”‘ Access Control

JWT-based authentication with HttpOnly cookies. Every API call verifies organization membership before returning any document data. No document is ever served without an authorization check.

πŸ“œ Version History

Every time you upload a new version of an existing document, 4EverFile preserves the full chain of prior versions. Each version gets its own independent ledger anchor and hash.

πŸ”— Complete Audit Trail
The version timeline on each document's detail page shows every iteration with its hash, anchor status, and timestamp β€” creating a complete, tamper-proof audit trail of how the document evolved over time.

❓ Frequently Asked Questions

What type of ledger does 4EverFile use? βž•
4EverFile anchors document proofs on a high-throughput Layer-2 blockchain network. This provides enterprise-grade security inherited from a major proof-of-stake chain while maintaining fast confirmation times (under 10 seconds) and negligible transaction costs.
What happens if I lose my original file? βž•
If you used standard storage, a copy of your file is kept on 4EverFile's encrypted servers and can be re-downloaded at any time. If you activated the Permanent Vault, the file also exists on a permanent decentralized network and can be retrieved independently β€” even if 4EverFile ceases to operate. The on-chain hash proof always remains, regardless of storage tier.
Can a verified document be altered or deleted? βž•
No. The anchored record on the distributed ledger is immutable. The cryptographic proof exists permanently. Even if the file is deleted from our servers, the proof of its existence at that specific timestamp remains verifiable by anyone, forever.
How are digital signatures linked to a document? βž•
Each signature (cryptographic, e-signature, or wallet-based) is combined with the document's existing hash chain to produce a new chain entry. This creates a sequential, tamper-evident record β€” any modification to an earlier entry would break the chain, making forgery mathematically impossible.
Does the verifier require a 4EverFile account? βž•
No. The public verifier at /verify is completely open. Anyone can drop a file to check its hash against the ledger β€” no account, login, or payment required. This is by design: verification must be trustless and independent.
What file types are supported? βž•
4EverFile supports all common document and media formats: PDF, DOCX, XLSX, images (PNG, JPG, GIF, WebP), videos, audio files, and compressed archives (ZIP, TAR). Executable files and scripts are blocked for security. Maximum file size is 100MB per upload.
Is my data private? βž•
Yes. 4EverFile operates on a zero-knowledge model. The only information written to the public ledger is the document's SHA-256 hash β€” a 64-character string that cannot be reversed to reveal any file content. Your files are stored encrypted on our servers and are never shared, analyzed, or accessible to unauthorized parties.