Section 04
Proposed Blockchain Solution
Seven architectural pillars working as one system
Pim Protocol's response to the gaps identified in Sections 2 and 3 is organised around seven architectural pillars. None of these stands alone — each is designed to depend on, and reinforce, the others.
Pillar I
Embedded Ledger Architecture
A Minima-inspired combination of Transaction Proof-of-Work, a Cascading Chain, and Merkle Mountain Range proofs, giving full validation and chain construction on devices with as little as 1.5–3 GB of RAM.
Pillar II
Hybrid Sharded Consensus
Proof of Entropy Minima combined with Cross-Shard Merged Mining (CSMM), deterministic finality, and a GHOST fork-choice rule, across 100 dynamically rebalanced shards, targeting 100,000 transactions per second.
Pillar III
Adaptive Dual-Token Monetary System
QOL, a demand-responsive energy-backed currency, alongside PYM, a fixed-supply governance token. Governed jointly by the seven-stage EQCF calibration pipeline and the four-state ADTMS circuit breaker.
Pillar IV
Quantum-Resistant Cryptography
The complete set of NIST post-quantum cryptographic standards, deployed from the very first block — nine years ahead of the 2035 transition deadline.
Pillar V
PIM-VM Hybrid Virtual Machine
A single Rust-based runtime combining a lightweight interpreted mode and a full WebAssembly mode, automatically selected by hardware capability, sharing one interface that guarantees identical results across both.
Pillar VI
Optional Cash Mode Privacy
Opt-in privacy combining stealth addresses, fixed transaction denominations, light mixing, and gossip-layer origin hiding — with fees that strengthen, rather than drain, the currency's stability.
Pillar VII
Sovereign Edge Layer
Full coin ownership sovereignty on devices with 256 KB of RAM and no hardware security module, using physically unclonable function-based attestation and a compressed local inference model.
4.1How the Pillars Work Together
The relationship between these pillars is not additive — it is structural. The embedded ledger architecture (Pillar I) makes the Sovereign Edge Layer (Pillar VII) possible, because a self-contained Merkle proof is what lets a $3 device verify its own coins without trusting anyone else. The hybrid virtual machine (Pillar V) is what allows the same consensus rules (Pillar II) to be enforced identically whether the validating node is a microcontroller or a GPU server. The monetary system (Pillar III) depends on verifiable energy reporting from every tier, which in turn depends on the graduated participation model that the Sovereign Edge Layer makes possible for the cheapest devices. Removing any one pillar would force a compromise in at least two of the others.
4.2Headline Performance Targets
| Metric | Target / Specification |
|---|---|
| Throughput (theoretical maximum) | 100,000 TPS (100 shards × 1,000 parallel transactions) |
| Throughput (sustained, heterogeneous fleet) | 60,000–80,000+ TPS |
| Confirmation latency | 0.3–0.5 s intra-shard · ~8–10 ms for owned-object fast path |
| Cross-shard finality | ~8 s |
| Energy per transaction | 0.00034 kWh |
| QOL daily volatility target | 1–2% |
| Lightweight VM footprint | <64 KB interpreter |
| Node hardware tiers | 5, from 256 KB RAM to GPU server |
| Sovereign Edge Layer minimum hardware | 256 KB RAM, ~$3 retail cost |
| Quantum resistance | From the genesis block |
| Monetary policy states | 4 — Stable, Tightening, Transition, Critical |
| Native ledger object registry | 16 entries (the Pim Cell Type Standard) |
