Technical Deep-dives

Menu

</aside>

Executive Summary

The Problem

Proof of Storage & Validator Consensus

Blocknode uses event sourcing with quorum signatures to validate and record all storage events (PUT, GET, DELETE). Validator nodes operate as a distributed quorum, verifying ECDSA signatures and issuing periodic Proof-of-Storage (PoS) challenges. Non-compliant providers are penalized via slashing of staked LMWR. Validators initially run under Blocknode control but will transition to a DAO structure.

Encryption & Key Management

Blocknode Storage Providers offer encryption at-rest. For full End-to-End encryption, as Blocknode is fully S3 compatible, the official AWS “S3 Encryption Client” can be used to transparently encrypt and decrypt all data sent to/from Blocknode.

Performance Benchmarks

Preliminary synthetic benchmarks show Blocknode can achieve upload (PUT) rates exceeding 10 Gbit/s and comparable GET latency to MinIO baseline (~25 ms).

Service Level Objectives (SLOs)

Durability: ≥ 99.999999999% (11 nines)
Regional availability: ≥ 99.95%
Validator-enforced replication across providers, with automatic slashing and reassignment for SLA violations.