Section 03
Why Existing Solutions Fall Short
A comparative look at the architectures Pim Protocol learns from and departs from
Pim Protocol is not built in isolation. Its design draws directly on published research and production systems from six distinct areas of blockchain engineering, and is explicit about where it extends or departs from each one.
3.1Minima — Embedded Blockchain and Node Sovereignty
Minima's three core innovations — Transaction Proof-of-Work, a Cascading Chain structure, and a Merkle Mountain Range (MMR) for compact state proofs — are the direct structural inspiration for this protocol's mobile and edge node tiers. Minima's KISS VM, a stack-based scripting language with covenant primitives, is the foundation for what this protocol calls PIM-VM Lite Mode [1]. Its interpreter footprint is under 64 KB, it has been validated in commercial drone deployments, and it costs only around 2% of daily battery charge on a smartphone.
It is worth being precise about a related but different system: Utreexo [33], an accumulator design proposed for Bitcoin's transaction set. Utreexo still requires "bridge nodes" that maintain the complete transaction history to serve proofs to lighter nodes. Minima's MMR approach eliminates that full-history database at the protocol level entirely — each user holds a proof only for their own coins, and the network as a whole only needs to track the MMR's "peaks." Pim Protocol adopts the Minima model, not the Utreexo model, because it is this self-contained proof structure that makes full sovereignty possible on a $3 device: the proof travels with the transaction and can be checked against public data with no trusted middleman.
3.2Quai Network — Energy-Linked Consensus
Quai Network's Proof of Entropy Minima (PoEM) consensus mechanism, which achieves fork-free block selection in 0.01 milliseconds, and its QI energy-backed currency are the direct foundation for this protocol's consensus mechanism and its QOL currency design [2]. Pim Protocol extends Quai's approach substantially: where Quai's currency issuance responds to a single energy-cost ratio, this protocol's Energy Quotient Calibration Formula (EQCF, detailed in Section 7) combines five independently weighted signals — including a market-liquidity signal that Quai's design does not have — through a seven-stage pipeline with built-in resistance to short-term noise.
3.3WebAssembly Runtime Research
A 2025 academic survey of 103 WebAssembly runtime research papers [5] identifies the runtimes most relevant to this protocol's virtual machine design choice.
| Runtime | Footprint | Execution Model | Best Suited For | Role in PIM-VM |
|---|---|---|---|---|
| wasm3 | <64 KB | Pure interpreter | Ultra-constrained IoT, <256 KB RAM | SEL / Lite Mode backend |
| WAMR | ~200 KB+ | Interpreted + ahead-of-time + JIT | IoT with pre-compilation, smart contracts | Lite Mode pre-compilation on RISC-V |
| wasmtime | ~5 MB | Just-in-time (Cranelift) + AOT | High-performance servers | Full Mode backend |
| WasmEdge | ~1.5 MB | JIT + AOT + plugins | Edge computing, blockchain nodes | Hybrid candidate (evaluated) |
| DTVM | ~3 MB | "Lazy" JIT (staged optimisation) | Deterministic blockchain execution | Compilation-strategy concept adopted |
The empirical findings that matter most for this design [4]: wasm3 runs roughly 30 times slower than native code but is the fastest pure interpreter available, making it the right choice below 256 KB of RAM. Above that threshold, where ahead-of-time compilation becomes feasible, WAMR is preferable. Separately, the DTVM system [3] demonstrates that a staged compilation strategy — start with a fast interpreter, then asynchronously recompile "hot" contracts to optimised code in the background — achieves sub-millisecond invocation latency 23 times faster than a standard JIT compiler on first use. PIM-VM's Full Mode adopts this staged-compilation concept directly.
3.4Privacy System Research
This protocol's optional privacy mode, Cash Mode, is grounded in four independent research streams: stealth address schemes that hide a transaction's recipient using one-time derived addresses with under 1 KB of overhead [11]; fixed-denomination theory, which shows that standardising transaction amounts defeats amount-correlation analysis without needing expensive zero-knowledge proofs; the Dandelion++ protocol, which obscures a transaction's network origin through staged gossip propagation with minimal added messaging [10]; and comparative baselines from MimbleWimble [12] and Quai Network's own privacy design [2]. Cash Mode is engineered to land at roughly 1.5–2x transaction overhead, compared with Quai QI's 3–4x and Monero's 5–10x.
3.5Ledger Object Models — From Bitcoin's UTXO to the Pim Cell Model
| Model | Originating Chain | Core Idea | What Pim Adopts |
|---|---|---|---|
| Classic UTXO | Bitcoin | Discrete, spendable coin records enabling parallelism and privacy | Discrete coin model, MMR-based proofs |
| Extended UTXO | Cardano | Attaching arbitrary data and validator logic to a coin record | Data field, validator-script logic [18] |
| Cell Model | Nervos CKB | A ledger object made of data, a lock script, and a type script | Three-field cell structure [19] |
| Object Model | Sui / Move | Separating objects one party owns from objects many parties share | Owned-versus-shared execution split [20] |
| Strict-Access UTXO | Fuel Network | Declaring all dependencies upfront to enable parallel execution | Upfront input declaration [21] |
This protocol's native ledger object system — the PYM Cell Model, detailed fully in Section 5 — began as three foundational object types for governance and staking, and has since grown into a sixteen-entry registry (the Pim Cell Type Standard, or PCTS) spanning payments, identity, escrow, real-world assets, cooperative finance, delegated agents, and personal security. The "T" in PCTS stands for Type, not Token: each entry is a native ledger classification enforced directly by the consensus rules, not a smart contract deployed to an address.
3.6Hardware-Rooted Identity Without a Security Chip
Physical Unclonable Functions (PUFs) exploit microscopic, unrepeatable manufacturing variation in a chip's silicon to produce a device fingerprint that is unique and cannot be cloned without physically destroying the device [34]. Three variants matter for this protocol's edge-tier design: SRAM PUFs, which use the random power-up pattern of a chip's memory cells and need no extra hardware since every microcontroller already has SRAM; Ring Oscillator PUFs, which measure manufacturing-driven timing differences between oscillator circuits and are less sensitive to temperature swings; and Arbiter PUFs, which use a race condition between signal paths to support a very large number of distinct challenge-response interactions. Research on ARM Cortex-M devices demonstrates stable SRAM PUF responses across a −40°C to 85°C temperature range [34] — the full operating envelope relevant to Sub-Saharan African deployment conditions.
Separately, the IETF's RATS working group has standardised a vendor-neutral attestation framework that does not require a discrete Trusted Platform Module [35], and ARM TrustZone — already present in virtually every smartphone processor — provides a hardware-isolated environment for storing signing keys that survives even a compromised operating system [36]. For RISC-V hardware, equivalent isolation comes from open-source frameworks including Keystone and Penglai [37]. Together, these results establish that meaningful hardware-rooted security does not require the TPM 2.0 chip that most blockchain designs assume.
3.7Tiny Machine Learning at the Edge
Published research on TensorFlow Lite Micro and similar platforms demonstrates that compressed neural network models with 50,000–200,000 parameters can run inference in under 50 milliseconds on a 256 KB ARM Cortex-M4 processor [38]. Federated learning research further establishes that a compressed model under 100,000 parameters can deliver useful local decisions — shard selection, fee estimation, routing — without needing to query a more powerful network for every choice [38][39]. This is the foundation for "Lite DALI," the protocol's compressed local-inference model for edge devices, introduced in Section 5.6.4.
Previous
Problem Statement