Problem Statement

2.1Financial Exclusion at Scale

Roughly two billion people worldwide have no access to formal financial services [25]. Bitcoin's 7 transactions per second and Ethereum's 15–30 transactions per second are not capable of serving that population at any meaningful scale, and the transaction fees on both networks frequently exceed what a low-income user can justify for a single payment.

2.2Stablecoins That Aren't Stable, or Aren't Sovereign

The 2022 collapse of TerraUSD demonstrated what happens when an algorithmic currency is backed by insufficient real-world value and responds to stress with an abrupt, all-or-nothing failure mode rather than a graduated one. Meanwhile, the IMF has documented that more than 99% of the $270 billion stablecoin market is denominated in US dollars [22] — a pattern of "stealth dollarisation" in which emerging economies adopting these tokens are, in effect, outsourcing their monetary policy to a foreign central bank.

2.3The Quantum Deadline

NIST has set 2035 as the deadline for migrating cryptographic infrastructure away from algorithms vulnerable to quantum computers [26]. RSA and elliptic-curve cryptography — the signature schemes underpinning essentially every major blockchain today — are both broken by a sufficiently powerful quantum computer running Shor's algorithm. Any protocol that postpones this migration leaves its users' assets exposed to "harvest now, decrypt later" attacks, in which encrypted data captured today is simply held until quantum computers catch up.

2.4Energy Claims Nobody Can Verify

Several blockchain designs claim to be "energy-backed," but without a cryptographic proof of the energy actually expended, that claim is just an assertion. Pim Protocol's answer — Proof-of-Energy Cost (PoEC), introduced fully in Section 6 — requires every node to submit a zero-knowledge proof tied to hardware-level attestation every 12 hours. A network whose reporting compliance drops below 85% is, by definition, working from an unreliable energy signal, and that unreliability itself becomes an input into monetary policy.

2.5Virtual Machines That Exclude the Cheapest Hardware

As described in Section 1.1, no existing base-layer blockchain virtual machine resolves the tension between programmability and hardware accessibility. A protocol that mandates strong cryptographic proof submission with a hardware security module from every participating device automatically excludes ESP32-class hardware from full participation — even though such hardware is technically capable of validating its own coin ownership.

2.6Privacy That Is Either Absent or Prohibitively Expensive

Public blockchains expose transaction data by default. Mandatory privacy schemes like Monero's impose 5–10x transaction overhead, which is incompatible with both high throughput and IoT hardware. MimbleWimble removes programmability entirely. Zero-knowledge proof systems are too computationally demanding for constrained devices. None of these existing approaches link privacy fees back to the health of the base currency.

2.7The Sovereignty Gap and the Binary Circuit Breaker Problem

Two design goals pull in opposite directions. Edge devices should be sovereign, verifying what matters to them independently rather than trusting more powerful nodes. At the same time, mandating strong cryptographic energy proofs with hardware security modules from every device, every 12 hours, creates a computational burden the cheapest target hardware cannot bear. Resolving this tension without compromising either goal requires a formally specified middle path — the Sovereign Edge Layer described in Section 5.

A related problem concerns the monetary circuit breaker itself. A system with only "stable" and "halted" states forces an uncomfortable choice during mild stress: either do nothing and risk a slow drift away from the target price, or impose the maximum possible disruption — a full minting halt — even when the underlying stress is temporary and minor. A single volatile trading session or a brief dip in reporting compliance from a software update does not warrant the same response as a sustained, severe deviation. This is the gap that the four-state ADTMS system, detailed in Section 7, is built to close.