Burnbit Experimental Work ((install)) -

BurnBit Experimental Work: Turning the Web into a Swarm

Back in the late 2000s, a fascinating experiment emerged that blurred the line between the static, centralized web and the decentralized torrenting universe. That experiment was BurnBit.

For those who missed the era of scrappy web utilities, BurnBit (burnbit.com) was a simple but radical tool. You gave it a URL—an MP3, a software ISO, a video file—and it returned a .torrent file. That’s it. But underneath that simple interface lay a powerful, experimental idea: What if every file on the web could be a peer-to-peer download?

Let’s dig into why this was such interesting experimental work, what it taught us about distributed systems, and why it (sadly) faded into the digital twilight.

Limitations and ethical notes

Next steps for development

  1. Build minimal prototype: local TEE, simple keeper, Merkle log.
  2. Test deletion attestations against multiple backends (S3, IPFS).
  3. Formal threat-model review and third-party security audit.
  4. Usability testing and policy templates for compliance teams.
  5. Explore legal frameworks and multi-jurisdiction keeper deployments.

If you want, I can expand any section into code examples, a threat-model matrix, or a prototype architecture diagram. burnbit experimental work

Core components

  1. Secure enclave module

    • Runs within TEEs (e.g., Intel SGX, AMD SEV, or ARM TrustZone) to manage keys and execute deletion operations securely.
    • Holds ephemeral encryption keys; plaintext only exists inside enclave memory.
    • Provides attestations that it performed deletion commands.

  2. Data encryption and sharding

    • Client-side encryption with per-object ephemeral keys.
    • Keys are split using threshold secret sharing across multiple keepers (M-of-N) to avoid single-point compromise.
    • Encrypted shards stored across decentralized and centralized backends for redundancy.

  3. Deletion protocols

    • Key destruction: primary mechanism—delete ephemeral keys from all enclaves and key-holders; without keys, ciphertext is unrecoverable.
    • Shred-and-forget: overwrite or re-encrypt stored shards where possible.
    • Hardware-backed wipe: for devices or nodes with secure erase primitives, trigger vendor API to cryptographically erase storage.

  4. Verifiable attestations and audit trail

    • When deletion occurs, the TEE produces a signed attestation stating which key IDs and shards were destroyed and at what time.
    • Attestations are anchored on a public ledger (blockchain or append-only log) to prevent repudiation and enable third-party verification.
    • Retention policy manifests (signed by owner) describe deletion criteria and are stored with attestations.

  5. Governance and quorum

    • Key-holder network enforces quorum for deletion requests and for recovery operations.
    • Policies can require multiple independent or jurisdictionally diverse operators to prevent coerced mass-deletion.

  6. Compliance and legal considerations

    • Support for configurable retention windows to meet regulatory needs (e.g., GDPR erasure vs. legal holds).
    • Provides audit logs and attestations for compliance officers, while acknowledging limits when data has been backed up by third parties.

Tools Needed:

Part 1: What Was Burnbit? A Technical Archaeology

Burnbit launched around 2009 as a free web tool. Here’s how it worked:

  1. Input a direct URL to a file (e.g., http://example.com/video.mp4).
  2. Burnbit’s server would download that file once.
  3. It would generate a .torrent metadata file and a magnet link.
  4. Users could then download the file via BitTorrent clients, sharing the load.

Crucially, Burnbit acted as a hybrid seed. The original HTTP source remained the single initial seed. But as more peers downloaded via torrent, bandwidth costs shifted from the original host to the swarm.

3. Legal and Ethical Blowback

Several experimenters used BurnBit to "preserve" copyrighted material under the guise of research. This led to cease-and-desist letters sent to universities hosting P2P research labs. The EFF (Electronic Frontier Foundation) later published a cautionary note stating that "storing a file's fingerprint in the DHT may still constitute distribution in some jurisdictions." BurnBit Experimental Work: Turning the Web into a

Key Players

The Spiritual Successors

BurnBit is gone, but the experiment lives on in: