Parano1d Lab · Technical research

Research for proof-native systems

Cryptographic protocols, verifiable-state architectures and research results produced during the development of Parano1d.

01 · Latest

Latest research

All research

The Present Must Prove the Past

Parano1d has moved the source of current-state validity out of accumulated execution history into the present itself. The entire validity path from genesis is backed by an executable end-to-end post-quantum soundness theorem at the NIST Category 1 resource threshold.

Read the researchParano1d source
Security analysis

Poseidon2b Is Secure!

Security belongs to an exact instance. Fix GF(2^128), width four, the matrices, 8+58 rounds and feed-forward mode, then apply the published attacks.

10 min readRead
Protocol practice

ONETHICS ①

Run your own verifier. Keep the shared State lean. Save the proofs that matter to you.

5 min readRead
Security analysis

Parano1d meets NIST PQC Category 1

An executable end-to-end theorem accounts for the complete recursive State proof, parallel quantum-oracle access, coherent Poseidon2b response cost and every NIST MAXDEPTH point.

19 min readRead
Security analysis

FS-FRI security in Parano1d: a Block–Tiwari analysis

An exact Block–Tiwari analysis of Parano1d's production recursive State proof gives 127 provable and 127 conjectured bits against a 128-bit target.

14 min readRead
Protocol study

Why a block is accepted only with its recursive proof

An early design accepted a block first and produced its recursive proof later in the background. The canonical chain could therefore move ahead of the HistoryStep-proven tip, forcing nodes to persist and recover a second queue. The production design accepts the block and its matching HistoryStep together: one atomic object, one canonical height and no deferred proof backlog.

3 min readRead
Protocol study

Prove the block once, then search the nonce

HistoryStep binds every semantic header field under a nonce-free domain. PoW can vary the nonce without rebuilding the transition proof.

2 min readRead
Systems research

Bootstrapping from proof-carrying State

A joining node validates headers, verifies one recursive transition proof at a finalized boundary, installs exact live State and applies no more than eighteen recent blocks.

4 min readRead
Protocol study

Replacing a consensus quarantine with UTXO incarnations

A monotone creation identifier inside the existing value lane invalidates stale slot openings without a second consensus root or reuse quarantine.

3 min readRead
Engineering study

AuthStream: bounding a block-wide authorization workload

In an earlier 255-authorization layout, streaming compilation bounded 14–16 MiB of private input with 4.7% overhead. Its terminal proof missed the production latency budget.

3 min readRead
Protocol design

One owner, one authorization proof

One owner produces one witness-hiding authorization capsule for a complete logical spend, while HistoryStep proves its transparent State transition.

3 min readRead
Comparative study

Three polynomial-commitment experiments and the bottlenecks they exposed

Ladder FRI exposed proof-byte cost, FRI-Binius exposed source binding, and BaseFold exposed the cost of putting a verifier inside its successor.

4 min readRead

02 · Selected work

Current research record