Parano1d ① Proof-native Layer 1 ordered by PoW

[IgnotusNemo]

GREETINGS, CRYPTO PARANOIDS.

I have watched blockchains drift toward the very thing they were meant to destroy.

History grows without end. Verification becomes heavier. People stop determining truth for themselves and borrow it from APIs, explorers, exchanges, foundations and data centers.

This is not decentralization. It is rented verification.

The post-quantum transition will make this worse. Larger signatures and heavier cryptography, appended forever, will turn today's debt into tomorrow's dependency.

You can build post-quantum signatures and other primitives. But they alone do not make a system post-quantum.

Security targets and conjectures are not proofs. Marketing is not soundness.

I wanted a system that ordinary hardware could fully verify today and decades from now. Post-quantum from the first block. Not promised for later. Proven end to end.

That became Parano1d.

Proofs establish validity.
Proof of work establishes canonical order.
State is validated from genesis in O(1).
End-to-end post-quantum soundness meets the NIST PQC Category 1 threshold.

I searched for a blockchain where the present could prove the past without replaying it. I found none.

So I built one ①.

---

https://parano1d.org

https://docs.parano1d.org

https://lab.parano1d.org

---

The Present Must Prove the Past

Can a blockchain validate its current state without replaying the entire execution history from genesis?

https://lab.parano1d.org/research/the-present-must-prove-the-past/

---

This is where it started:

Specter was the first idea. It proved signatureless authorization could work, but the design had major problems and was archived. Parano1d was built from scratch.

A Signatureless Transaction Model and Recursive Proof-Based PQ Blockchain

https://bitcointalk.org/index.php?topic=5578193.0

---

Source code is open: https://github.com/ignotusnemo/parano1d

Release: https://github.com/ignotusnemo/parano1d/releases/

Wallet instructions: https://docs.parano1d.org/wallet

Mining instructions: https://docs.parano1d.org/mining

[zygzag]

discord please

[Sparks60]

i dont see a time when it starts? just a date aug 12th, can we get a update on what time

[IgnotusNemo]

i dont see a time when it starts? just a date aug 12th, can we get a update on what time

around 8 pm utc on august 12, but this is only an estimate. will post here once the release is published.

[IgnotusNemo]

I’ve read through the Specter design, and honestly I think the project needs to answer the **basic questions first**, because right now the documentation gives us a huge amount of technical terminology without making the actual innovation easy to understand.

you are reviewing the old specter idea. it was archived and is not the current protocol https://bitcointalk.org/index.php?topic=5578256.msg66959745#msg66959745

for the current design, start with this https://lab.parano1d.org/research/the-present-must-prove-the-past/

[alt_x]

Was there any info about POW algo?
Is it worth of trying with CPU?

[IgnotusNemo]

Was there any info about POW algo?
Is it worth of trying with CPU?

pow uses poseidon2b. the miner is cpu-only, there is no gpu miner.

block production has two stages: proof construction and pow. the proof is built first, then the cpu searches for a valid nonce.
even if a poseidon2b asic is built in the future, it would solve only the nonce search. block production still requires constructing the proof first, so an asic alone cannot produce blocks.

cpu is the intended way to mine. it is available directly in the gui wallet and in core.


https://docs.parano1d.org/mining

https://docs.parano1d.org/wallet

[alt_x]

==> Generating B25/m22 and B255/m24 matrices at zstd level 19
PARANOID canonical HistoryStep v1 freezer
  pack:          /home/auto/parano1d-artifacts/.history-step-pack-v1.generating.123600/v1
  rayon threads: 4
  witnesses:     real genesis chain + two exact parent checkpoints
  classes:       2 (B25/m22 and B255/m24)

Building and exporting canonical matrices:



takes time..

[IgnotusNemo]

Source code is open: https://github.com/ignotusnemo/parano1d
Release: https://github.com/ignotusnemo/parano1d/releases/

parano1d is a completely new blockchain architecture. things work differently here.

why?

we got rid of one of the biggest debts of existing systems: the need to store and replay the entire transaction history to prove that the present is valid.

this opens the way to real scalability.

the new architecture, together with cryptography without signatures or elliptic curves, made parano1d post-quantum today. the entire verification path, from genesis to any height, is formally proven at the NIST PQC Category 1 Level.

we are only beginning to uncover the practical and product possibilities of this architecture. this will be an exciting journey into a future without the debt accumulated by the past.

the present must prove the past. now it does.

Wallet instructions: https://docs.parano1d.org/wallet

Mining instructions: https://docs.parano1d.org/mining


Genesis

Date and time: 12 August 2026, 20:00:00 UTC
Unix timestamp: 1786564800
Block ID: 6b874fac7385c0e5f85ebf9b6bc8ea82a080db912042d4a8bc1560e794d3854f
State root: 5c7f3712611c836a2c6ab0448d32c271f04e3213560e8a5321331cd6a5c98492
Nonce: 33522
Initial proof-of-work target: 2^238


Mean block target: 15 seconds
ASERT epoch: 6 blocks
ASERT half-life: 90 seconds
Transaction epoch: 144 blocks
Hard finality: 18 blocks
Recent block and reorg suffix: 18 blocks
Initial state domain: 2^24 slots
Maximum state domain: 2^32 slots
State segment: 2^16 slots
State expansion threshold: 75%, with a 10 of 18 finalized-header majority
Default HistoryStep class: B25, m=22, up to 25 effective page positions
Large HistoryStep class: B255, m=24, up to 255 effective page positions
Transaction page: 8 inputs, 2 outputs
Maximum PagedSpend: 128 pages, 1,020 inputs, 256 outputs
Maximum ordinary user pages per block: 255
Initial block subsidy: 50 NOID
Block subsidy floor: 1 NOID
Proof of work: Poseidon2b, 128-bit nonce

Production proof profile

Committed trace field: GF(2^128)
Wide challenge field: GF(2^256)
Challenge support: 2^255
Poseidon2b: width 4, x^7, 8 full rounds, 58 partial rounds
Wallet queries: 65
History and BaseFold queries: 133
B25 codeword: 2^19 at rate 1/4
B255 codeword: 2^21 at rate 1/4
Target FRI security: 128 bits
Provable Block–Tiwari FS-FRI security: 127 bits
Conjectured Block–Tiwari FS-FRI security: 127 bits
Sequential ideal-QROM boundary: 64.707407428576 bits
NIST Post-Quantum Cryptography category: Category 1
Dominant Category 1 gate-depth floor: 173.273866314232 bits

Packages

Choose the GUI package for the Parano1d wallet, its built-in full node and mining from the desktop application. It does not require a separate daemon or terminal.

Core archives are intended for headless node operation, command-line use and external mining. They contain the full node, command-line wallet client and external miner.

Native packages are available for Linux x86-64, Linux ARM64, Windows x86-64, macOS Apple Silicon and macOS Intel.

Installation and operation · Mainnet parameters · Production soundness certificate

[alt_x]

No peers found

[Sparks60]

same 0/2 peers

[makertronic]

not working , cant sync

[garmin]

No peers found

same 0/2 peers

7 peers  
Height 0
Block 6b874fac7385c0e5f85ebf9b6bc8ea82a080db912042d4a8bc1560e794d3854f

 

[IgnotusNemo]

working on it now, please wait

[IgnotusNemo]

! I found the exact cause. This was my deployment mistake.
I deployed the seed nodes using a local build whose embedded HistoryStep matrix whitelist differed from the public v0.1.0 binaries. Public clients correctly rejected the proofs produced by those nodes.
I have stopped the network. I am replacing every seed with the exact published v0.1.0 binary and restarting the chain from genesis.
Please close the client for now. Your downloaded v0.1.0 package is correct, so you will not need to download it again. I will post here when the network is ready; then simply reopen the client.

[garmin]

! I found the exact cause. This was my deployment mistake.
I deployed the seed nodes using a local build whose embedded HistoryStep matrix whitelist differed from the public v0.1.0 binaries. Public clients correctly rejected the proofs produced by those nodes.
I have stopped the network. I am replacing every seed with the exact published v0.1.0 binary and restarting the chain from genesis.
Please close the client for now. Your downloaded v0.1.0 package is correct, so you will not need to download it again. I will post here when the network is ready; then simply reopen the client.

I mined 1 block. do I need to del data dir?

[IgnotusNemo]

! I found the exact cause. This was my deployment mistake.
I deployed the seed nodes using a local build whose embedded HistoryStep matrix whitelist differed from the public v0.1.0 binaries. Public clients correctly rejected the proofs produced by those nodes.
I have stopped the network. I am replacing every seed with the exact published v0.1.0 binary and restarting the chain from genesis.
Please close the client for now. Your downloaded v0.1.0 package is correct, so you will not need to download it again. I will post here when the network is ready; then simply reopen the client.

I mined 1 block. do I need to del data dir?

Yes. Since your client actually mined and accepted a block on the stopped chain, close the application and remove the chain data before restarting.
I will post the exact reset instructions for each OS together with the network-ready notice.

[alt_x]

Got block 1, but it is 45 coins?
Did i fork? a7231432565815816ba54f62013cb9b93fd7ac9437cb5d1ea5b1ccfabacd93e4

[Hashrateoptions]

Got block 1, but it is 45 coins?
Did i fork? a7231432565815816ba54f62013cb9b93fd7ac9437cb5d1ea5b1ccfabacd93e4

Did you read delete data and wait for developer green light 

[tomassamot]

In which directory is the chain data I need to delete located? 
windows