David L. Condrey | Searcharxiv

arXiv2026

Finite Configurations Cannot Generate a Constant Trace in Rule 30

For every right half we determine the unique left half whose Rule 30 central trace is constant: an alternating tail selected by the leading one of the right half when the initial center is 0, and a single universal checkerboard when it is 1. Every nonzero member of either fiber carries infinitely many ones, so the zero row is the only finite configuration with a constant trace. For support radius w the sharp maximum constant-prefix length is 2*ceil(w/2)+1 when the initial center is 0 and 2*floor(w/2)+2 when it is 1, so the maximum over both is w+2, attained by exactly 2^w configurations for even w and 2^w - 1 for odd w. Hence no column of a nonzero finite Rule 30 orbit is eventually constant.

math.DS↗

arXiv2026

PoSME: Proof of Sequential Memory Execution via Latency-Bound Pointer Chasing with Causal Hash Binding

We introduce PoSME (Proof of Sequential Memory Execution), a cryptographic primitive that enforces sustained sequential computation via latency-bound pointer chasing over a mutable arena. Each step reads data-dependent addresses, writes a block whose value and causal hash are mutually dependent (symbiotic binding), and chains the result into a global transcript. This yields three properties: (1) strict linear sequential memory-step enforcement, (2) high time-memory trade-off resistance (a tenfold penalty at a write density of 4, with a formal space-time lower bound that scales quadratically with the number of steps), and (3) a tight ASIC advantage bound by DRAM random-access latency rather than bandwidth. Benchmarks across 17 CPU platforms and 4 GPU architectures demonstrate that hash computation is under 3.5 percent of step cost and GPU hardware is 14 to 19 times slower than a consumer CPU. POSME requires no trusted setup and provides a foundation for verifiable delay, authorship attestation, and Sybil resistance.

cs.CR↗