Parano1d ① Proof-native Layer 1 ordered by PoW

[Arttemkaaa]

lets do a reset. weird launch actually

No need for a reboot. Why reset everything when some disgruntled person comes along?! The network must work.

Many people didn't sleep last night and got nothing. I went to the fork almost immediately and got almost nothing on my second try. But why restart the network?! There will always be dissatisfied people.

[alt_x]

I’m waiting for the new version. With the current release, the client cannot stay at the chain tip reliably. It receives blocks in batches instead of following them continuously, occasionally stops completely and requires a restart, and sometimes even crashes.

[minerminer3456]

fair launch pls

[alt_x]

The node successfully applies block 2753, but fails to advance to block 2754. It continues seeing later blocks (2755–2761) from peers and repeatedly requests linked headers, but the local chain tip remains stuck at 2753. This points to a problem resolving or validating block 2754, causing all subsequent blocks to remain pending.

Shouldn’t the client automatically detect that it has ended up on a fork and reorganize back to the canonical chain?

In this case, the node successfully accepts block 2753, but then fails to advance to 2754. Meanwhile, peers are already at 2755, 2756, 2757 and beyond. The node clearly knows that newer blocks exist, because it repeatedly requests the linked headers, but its own tip remains stuck at 2753.

If 2753 is part of a losing fork, the client should be able to recognize that the peer chain is the valid/canonical continuation, abandon the forked chain, and continue from the common ancestor onto the correct chain.

There is currently no CLI command to manually invalidate 2753, so the node appears to have no recovery path once it gets into this state. This suggests the automatic fork detection/reorg logic is not working as intended.

[alt_x]

The new client is definitely an improvement and stays much closer to the chain tip, but the logs show that the main problem is still the mining/network gate.

The miner repeatedly reaches 2/2 authenticated peers and becomes ready, then shortly afterwards drops to 0/2 and goes back to waiting. This happens over and over again. In some cases the miner is already preparing a block when the quorum disappears, causing the prepared block to be discarded.

At the same time, block propagation is still not truly real-time. The node frequently has to catch up using multi-block compact suffixes, and there are also cases where it detects a recent gap and has to re-request headers because the next block is not immediately available.

This means the miner is not continuously receiving a fresh tip/template and is losing mining time between blocks. With a 15-second block time, these delays are especially significant: by the time the miner becomes ready again, the network may already be several seconds or even multiple blocks ahead.

The reorg logic appears to work when a competing chain is actually detected, so the remaining critical issue seems to be the unstable authenticated-peer quorum and the delayed/fragmented propagation of new blocks. The miner needs to stay connected and ready continuously, and each new block needs to propagate fast enough that miners have a realistic opportunity to mine the next block.

Combined with delayed block propagation and blocks arriving in batches, this means miners often miss entire blocks before they even get a chance to work on them.

There is also an local RPC error:
local node RPC: error sending request for url (http://127.0.0.1:9401/)


Even if the current synchronization and peer-quorum issues are fixed, I think a longer block time would still be the sensible choice for mainnet. A longer interval may hide some of the current problems by simply giving the network more time to propagate and process each block, so 15 seconds is a useful stress test rather than necessarily a good production target.

If the client can reliably operate at 15 seconds on the testnet after the current issues are fixed, that would be a strong result. But for the mainnet release, I think 1–2 minutes per block should be the minimum. It gives nodes enough time to propagate and validate blocks, update state, and gives miners a realistic opportunity to receive the latest template and mine each block.


Parano1d v1.0.1 Latest
@ignotusnemo ignotusnemo released this 24 minutes ago
v1.0.1
1d3a01f

[Sparks60]

tested new version, will sync, win a block, reorg, poof gona, endless loop, at this point i am gona wish you the best on a 15 second block coin, as all i tried fails at 15 seconds. time for me to move on.

[minerminer3456]

impossıble to mine. alot of problems. after two days of work i am giving up.

[tomassamot]

still doesn't work  peers 5 height 0  with new 1.01 version


23:11:31  INFO manifest snapshot boundary ahead — queueing snapshot candidate from=12D3KooWKbNz4TzReuNp5mpyz38nyKGogqbUVXZiVEU12ayAUoHX our_height=0 snapshot_height=3391 snapshot_gap=3391 force_snapshot=true
23:11:31  INFO connected header probe found deep gap — requesting snapshot manifest peer=12D3KooWA4xTVV3kMmkDFTZoaxbBPawjZ8HY3r5oxumBvD3tveAd our_tip=0 peer_tip=19 retention=18
23:11:32  INFO received state manifest from=12D3KooWA4xTVV3kMmkDFTZoaxbBPawjZ8HY3r5oxumBvD3tveAd tip=3396 segments=1
23:11:32  INFO manifest snapshot boundary ahead — queueing snapshot candidate from=12D3KooWA4xTVV3kMmkDFTZoaxbBPawjZ8HY3r5oxumBvD3tveAd our_height=0 snapshot_height=3396 snapshot_gap=3396 force_snapshot=true
23:11:35  INFO connected header probe found deep gap — requesting snapshot manifest peer=12D3KooWHniog4xyYkVwbFjavbEWXzZT6NGiF1Q7JQ27YsnvKSPG our_tip=0 peer_tip=19 retention=18
23:11:35  INFO snapshot manifest election settled — validating strongest advertised chain from=12D3KooWKc1nxUCCumRwHiv427cKeQ67PhBqpf8PuCWQQsDHxTEZ tip=3396 bridge_tip=3414 responses_considered=5
23:11:35  INFO snapshot: staging exact headers peer=12D3KooWKc1nxUCCumRwHiv427cKeQ67PhBqpf8PuCWQQsDHxTEZ target_height=3396 bridge_tip=3414
23:11:35  INFO snapshot: pipelining exactly correlated headers into disk staging peer=12D3KooWKc1nxUCCumRwHiv427cKeQ67PhBqpf8PuCWQQsDHxTEZ next_height=1 target_height=3396 window=4
23:11:35  INFO received state manifest from=12D3KooWHniog4xyYkVwbFjavbEWXzZT6NGiF1Q7JQ27YsnvKSPG tip=3394 segments=1
23:11:35  INFO manifest snapshot boundary ahead — queueing snapshot candidate from=12D3KooWHniog4xyYkVwbFjavbEWXzZT6NGiF1Q7JQ27YsnvKSPG our_height=0 snapshot_height=3394 snapshot_gap=3394 force_snapshot=false
23:11:37  INFO snapshot: exact headers staged — retrying HistoryStep terminal peer=12D3KooWKc1nxUCCumRwHiv427cKeQ67PhBqpf8PuCWQQsDHxTEZ target_height=3396
23:11:39  INFO snapshot HistoryStep verification started off-thread from=12D3KooWKc1nxUCCumRwHiv427cKeQ67PhBqpf8PuCWQQsDHxTEZ terminal_from=12D3KooWKc1nxUCCumRwHiv427cKeQ67PhBqpf8PuCWQQsDHxTEZ tip=3396
23:11:40  INFO snapshot sync phase measurement phase="history_step_terminal" scaling="O(1)" count=1 bytes=971732 elapsed_ms=1063 timing_basis="active_work" outcome="accepted"
23:11:40  INFO snapshot authority accepted — starting exact state staging from=12D3KooWKc1nxUCCumRwHiv427cKeQ67PhBqpf8PuCWQQsDHxTEZ tip=3396 bridge_tip=3414


after some time 


23:14:30  INFO received state manifest from=12D3KooWHniog4xyYkVwbFjavbEWXzZT6NGiF1Q7JQ27YsnvKSPG tip=3402 segments=1
23:14:30  INFO manifest snapshot boundary ahead — queueing snapshot candidate from=12D3KooWHniog4xyYkVwbFjavbEWXzZT6NGiF1Q7JQ27YsnvKSPG our_height=0 snapshot_height=3402 snapshot_gap=3402 force_snapshot=false
23:14:31  INFO received state manifest from=12D3KooWGBGvUCfRmiux5n6L8CT76iHWbn5j964qnZ2cMDC7mEvv tip=3403 segments=1
23:14:31  INFO manifest snapshot boundary ahead — queueing snapshot candidate from=12D3KooWGBGvUCfRmiux5n6L8CT76iHWbn5j964qnZ2cMDC7mEvv our_height=0 snapshot_height=3403 snapshot_gap=3403 force_snapshot=false
23:14:32  INFO connected header probe found deep gap — requesting snapshot manifest peer=12D3KooWGBGvUCfRmiux5n6L8CT76iHWbn5j964qnZ2cMDC7mEvv our_tip=0 peer_tip=19 retention=18
23:14:32  INFO connected header probe found deep gap — requesting snapshot manifest peer=12D3KooWKc1nxUCCumRwHiv427cKeQ67PhBqpf8PuCWQQsDHxTEZ our_tip=0 peer_tip=19 retention=18
23:14:32  INFO received state manifest from=12D3KooWGBGvUCfRmiux5n6L8CT76iHWbn5j964qnZ2cMDC7mEvv tip=3403 segments=1
23:14:32  INFO manifest snapshot boundary ahead — queueing snapshot candidate from=12D3KooWGBGvUCfRmiux5n6L8CT76iHWbn5j964qnZ2cMDC7mEvv our_height=0 snapshot_height=3403 snapshot_gap=3403 force_snapshot=true
23:14:32  INFO received state manifest from=12D3KooWKc1nxUCCumRwHiv427cKeQ67PhBqpf8PuCWQQsDHxTEZ tip=3404 segments=1
23:14:32  INFO manifest snapshot boundary ahead — queueing snapshot candidate from=12D3KooWKc1nxUCCumRwHiv427cKeQ67PhBqpf8PuCWQQsDHxTEZ our_height=0 snapshot_height=3404 snapshot_gap=3404 force_snapshot=true
23:14:36  INFO snapshot manifest election settled — validating strongest advertised chain from=12D3KooWA4xTVV3kMmkDFTZoaxbBPawjZ8HY3r5oxumBvD3tveAd tip=3404 bridge_tip=3422 responses_considered=5
23:14:36  INFO snapshot: staging exact headers peer=12D3KooWA4xTVV3kMmkDFTZoaxbBPawjZ8HY3r5oxumBvD3tveAd target_height=3404 bridge_tip=3422
23:14:36  INFO snapshot: pipelining exactly correlated headers into disk staging peer=12D3KooWA4xTVV3kMmkDFTZoaxbBPawjZ8HY3r5oxumBvD3tveAd next_height=1 target_height=3404 window=4
23:14:38  INFO snapshot: exact headers staged — retrying HistoryStep terminal peer=12D3KooWA4xTVV3kMmkDFTZoaxbBPawjZ8HY3r5oxumBvD3tveAd target_height=340

[alt_x]

Looks like the dev accidentally created the world’s first 0-second block-time coin.

And with one miner doing most of the work, it gets even more interesting: the miner can keep finding blocks back-to-back while the rest of the network is still trying to catch up. Other nodes receive blocks in batches, mining templates become stale, and smaller miners barely get a chance to work on the latest tip.

[alt_x]

Here is the full-chain miner rich list for Parano1d, covering all 3800 blocks currently analyzed.

The percentage shows each miner’s share of the blocks.
This gives a clear picture of how mining power has been distributed across the chain so far

o1wavhkuxgv5ekr9t0wzz573q6567lmsqxfsr4zxj0ksp2hzjvqspqeyemus               1897           85365.00   49.9211%
o1cu5euacey0kah3n5yjd3h46nfqzlxuva2jue8k9kgrx8lqg9yxgqvzzkcw               1054           47430.00   27.7368%
o10h74vlp42sxanv26qwhk7d327fujzmtzm7l6ehu0rx60enpccexqm02gcm                146            6570.00    3.8421%
o1fnf5fuqsq2cffhh9s30latya9v4qj5scdewyz73p2ad68ec78cws8csj8v                133            5985.00    3.5000%
o1syg7srzklvcyumyp8avlz2vxakygqgrz4twpncz6ae2aa04a9n6skypec4                 88            3960.00    2.3158%
o18p2e6q63y350eu599n3sn3elrldjvwhzvkh2l9cfvr2ejn67wwasjk83fz                 37            1665.00    0.9737%
o19uyx7zs5rnue0u2d77fqgphdnrw3y09nn8edtd7kdhu6vgta7f5qq245qu                 33            1485.00    0.8684%
o1kr90maj55t2mhu4rjfaec2n2kkey6m43hzt64cp4mgz4ndx2m5cq6gj7xn                 30            1350.00    0.7895%
o18e4r7kfegxamyvcl0ussztm26d3vzvsr8csrdwzfmm8hy090kz8s70n2vm                 30            1350.00    0.7895%
o1rpwfdltjjssrc3h4as0l9rfdlfph0kz24hp9fe4m923wsxf0kens456q4k                 27            1215.00    0.7105%
o1jpwqswmyad028hgjml84wzpyy9uxv600t2stzwncp3269d07g3kq6syq5c                 26            1170.00    0.6842%
o13x2g0a7z7xk0667y6vdr79dfx32egdfm6uy9uh7lyvm4lnp9auksnt5anp                 19             855.00    0.5000%
o1xra3mh4xu2yp4ks2ecww6cezjju6v0cm04q929xjx3he74qm8r7ssef44p                 18             810.00    0.4737%
o1hacjjcvsrn6mg4fntekyjwrav9qnuzhj4cfx4rrzduvyx93ckl6s5hrkje                 18             810.00    0.4737%
o1xgdp2nrgfhz73qxp33wlck9r36ckxzgam5p5xd65jz3cga3396qsdsdw06                 16             720.00    0.4211%
o14665vruv5aw5yrkqk85axtxy0t8dy2y2lxdx6gzg6xx9ljrv8whs5ngncz                 15             675.00    0.3947%
o1lu04q856tsg8cta44wmpztwsw9hc780yx8f5dxgq76fkwg8gl8gq7m452l                 14             630.00    0.3684%
o1l3e5z5yn7953txhynt5zz8qwjn7fh36ucu6wmnxzdkx3l2gjq8cslfggnw                 14             630.00    0.3684%
o1x9mnl5pcenf8fmuylthdhtunc3kpkh74rsnejpgfh7gqhp85seqq4xnatw                 12             540.00    0.3158%
o13xh6fnqp2cfxhql9v4vdvfffdxvhtzjzuvsz06hnyjzqup3g5zxqyutshn                 12             540.00    0.3158%
o1zdu5lnsh00n4t7a0f4hnejx4nw3lef2xvdeur7janca6d6ch7fvqu6dkyq                 10             450.00    0.2632%
o1plxv75me0afezzvwyvv4wnjenav0g3ncvgw2jzt3475ajwm64r2qv4g2e9                 10             450.00    0.2632%
o1p965jf3qqlfns44ul3tl9scjgxf6g4y7n7e3q06mpvhapct4z6es0gweu9                 10             450.00    0.2632%
o16xr64rfkzfq6pxs35h93s3h63evv46rtcr8xrnf3h7n57wvcg3jqfukyqg                 10             450.00    0.2632%
o1xajldvp46eh4tvkl2l70lwv65kf3plgphyt53qquyz5gfs9zmv8sa74juc                  9             405.00    0.2368%
o1camxnms7qjc6zs6jkggh5xehgy9r6thvn03d9wduz5vjzfwrf7fsgrg6tr                  9             405.00    0.2368%
o189d72tcej2y5f8rr9mhhu2pjvlg2mjuaa34q5sceexsrpp8ghm3st7s8wa                  9             405.00    0.2368%
o1kmxa7y4gaf94hu46u6jeqwazng6natx0qt4fdawk9lnj2nd5g4xqpvgwfc                  8             360.00    0.2105%
o1za3xxxm3zfxh0ujkemrq3eghdh4x2s9w3sgjcfe3zg8se9mye8jsymzla0                  7             315.00    0.1842%
o1ugydese0h67d65swfhkm749q9rxjwsc4zr2d85drh6pveu4y0h7q38vdzf                  7             315.00    0.1842%
o1cyqdyj6t9944w68qtak2lak7gwfqer8wypex8ukpckyaf8nv60tq0a2pm9                  7             315.00    0.1842%
o1cw3a5wvz89j7hva79pg0csnncvz6c6q7v5syn76e763ddrzc5tkqw7vtxw                  7             315.00    0.1842%
o1c7gucqxw77tc50sz9cdsx2h48gpf5fe8a7wdc7va7zkdpv8yzquslmslsc                  6             270.00    0.1579%
o1ug37eywqs44acym5a30kgkvjjhm3q398z0vqma5867sx79t5fwlqtdg2pt                  5             225.00    0.1316%
o1rlgne5hxa4jcrc4pr7vyf7e4lptemv6upzn6fdukmeudgs2pyrfsj5vxaa                  5             225.00    0.1316%
o1nrkzn4pyvu4mvvpdq8ukqvrmlw3ye3xh6np84x6as722urptqsjskh3y9t                  5             225.00    0.1316%
o1gl46lv2agmd83xwaj87n00vyr4f2ry073vr4dsqakt9yvdzpd2esuyduz6                  5             225.00    0.1316%
o1yfax6tydc3r5cn2s3u6apdfrpa6l8wccj34afwjjt4z0u24zlgqqkheh7k                  4             180.00    0.1053%
o1a8q40kgenjj5slxqcxn672jmlwyyus9mq9m8vu5g9rhz2q02agtspxtge0                  4             180.00    0.1053%
o1qqv8k04ru4fkg0tcgntks3n6jl62gck2v92tfjcck22w56s5qw4qf0hwkc                  3             135.00    0.0789%
o1l5qryk6t7sqf5hnxnt4z2y2wkj2sz6zj2eueuq8afezqmnmesfxs3vspnd                  3             135.00    0.0789%
o1ekmvq83yufzfxtpglvyrkhqz83ef7y3vmh94na6mk0yf0nvqwe5qwyl9rr                  3             135.00    0.0789%
o1e040v4srgsnry3zcw8ckmv7a0qem3qwnqyzatqtc7nazt460smcqjzf5fn                  3             135.00    0.0789%
o15c7pv0wuqlxmsd3qne4lvy0y5l3esex4vgf20ardda2yt997dq6smde7km                  3             135.00    0.0789%
o1h9j6j643yqa3detf5zj87hg9f378ffcka236l9jey5pgdr4mh4lsglhj9t                  2              90.00    0.0526%
o1h7j986q6sa35ujy7qk5xwsldsw4a8585mzqw0r732ghentvfurpqvyk38q                  2              90.00    0.0526%
o1d6rcldkesq765s20j5t6hp6mpkq8xfqyzp5fzyzr2u9lazwsuepq0pe0d8                  2              90.00    0.0526%
o1s9drclh4xwesefc0aechg3wyshs4m2rrpjplsvgdvusrzvc3eqfqhs69ne                  1              45.00    0.0263%
o1kela8r7ytp8vqqa8jteph35ntc3kmh92ztjpsn4qg9ljg6xsdqmq4wrp8p                  1              45.00    0.0263%
o17upr2dzkzxfp3g0htda2zlm08vddu7cuewt23kue0jawdjcejp3q6tx9py                  1              45.00    0.0263%


Note that these are addresses, not necessarily individual miners. A single miner may be operating multiple addresses, so several of the 50 addresses could actually belong to the same miner.

[IgnotusNemo]

Thank you, everyone, for the detailed reports and logs.

This launch gave me a lot of useful information that could only really show up under live stress. I now have a clear picture of what is wrong with the p2p design.

One of the main goals of Parano1d was to remove a major debt of existing systems. the need to store and replay the entire execution history to prove that the present is valid. This opens the way to real scalability.
The new architecture, together with removing signatures and elliptic curves, also made Parano1d post-quantum from its first block. The entire validity path from genesis to any height is backed by an executable end-to-end post-quantum soundness theorem at the NIST PQC Category 1 resource threshold.

Parano1d was written from scratch over more than six months, often working 12+ hours a day. Most of my work has been around cryptography, proof systems and protocol design.
And we can already see that the consensus and cryptography work exactly as intended. We achieved a fantastic result there.

Networking is probably the part I enjoy the least, and of course network decided to test exactly that first

I will redesign the P2P layer rather than keep adding patches. Headers will propagate first, separately from heavy block bodies, proofs and State data. Synchronization will remain fixed to one exact branch while allowing data to come from different peers. Reorgs will verify one recursive terminal at the selected tip instead of one for every block.

This confirms the decision to delay mainnet for a few days. The next launch will start from a new genesis. This is now a technical requirement, not a question of noid distribution among early miners.
Over the next few days I will rebuild and test the networking layer. After the final load tests, we will launch mainnet.

We are only starting to explore what this architecture can make possible in practice. There is a lot ahead.