Parano1d mainnet is live #8
Replies: 19 comments 9 replies
|
i don't see discord and x account so please make discord first |
|
When will it be released? |
|
We are waiting! |
|
这是来自QQ邮箱的假期自动回复邮件。
您好,我最近正在休假中,无法亲自回复您的邮件。我将在假期结束后,尽快给您回复。
|
|
The v1.0.0 mainnet release build has started. Binaries for Linux, Windows and macOS should be available within an hour. You can start your nodes as soon as they are published. Mining unlocks automatically at 16:00 UTC. Build progress: https://github.com/ignotusnemo/parano1d/actions |
|
The Parano1d v1.0.0 mainnet release is now available https://github.com/ignotusnemo/parano1d/releases/tag/v1.0.0 Binaries for Linux, Windows and macOS are ready. Mainnet seed nodes online, so you can install and start your node now. |
|
The network started at the scheduled genesis timestamp. In the first six minutes it passed height 50 under much heavier load than our controlled tests, with around 65–70 live peers connected to each seed. Several miners produced competing branches at the first heights. The nodes handled the expected atomic reorganizations and agreed on the same canonical hashes. No consensus, database or synchronization failures so far. P2P queues remain near zero, slower nodes are catching up through exact suffix sync, and difficulty is adjusting from the launch level. One external miner currently dominates the canonical chain. The wider P2P mesh is already starting to form. Seeds carry most of the bootstrap traffic at launch, but as nodes discover each other and begin serving headers, snapshots and exact objects, that load spreads across the network. The topology becomes less seed-centered as the network grows. I am continuing to watch network logs. |
|
I noticed that a handful of miners have mined all the blocks so far. My node keeps toggling between |
|
Is there a Discord or Telegram for the project ? It seems important and interesting for building a community. |
|
When is the exchange listing? |
|
o1y4jgqw0vwhxh6409xaqa40s2ngyhm3h78z2phvz58ctgkv50xjrsre9c9s Gets all the blocks. |
|
This is total nonsense; I have good equipment, but I haven't caught a single block—that shouldn't be possible at this difficulty level. |
|
Everything is working, but yes, it's likely GPU-related. It's not necessarily cheating, we now know it's possible on the GPU. I'm going to work on it. |
|
We need to solve the problem with the video cards and do a new launch. I think a new start and reset is needed. You have already nullified my coins several times, and now the cheater is taking everything. |
|
There is a pool with a community behind it. |
|
Ive been watching the network since launch. It has now crossed 1 GH/s on the short window. Over the last 100 blocks it averaged around 0.79 GH/s, with a 21.2 second average block time and a 19 second median. The target is 20 seconds, so difficulty is tracking the load well. |
|
… On Fri, Aug 21, 2026 at 10:38 PM tapenumbra ***@***.***> wrote:
Please create a group.
—
Reply to this email directly, view it on GitHub
<#8?email_source=notifications&email_token=B6MCBCJEAM2TAHEYL7WUIUD5LCXLFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRGEYDGNJWUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18110356>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/B6MCBCIQ5K43MUXPQEHFZHT5LCXLFAVCNFSNUABJKJSXA33TNF2G64TZHMYTEMRVGAZTIMBVGU5UI2LTMN2XG43JN5XDWMJQGY2TENZYGGQXMAQ>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/B6MCBCP2DULYSV2RCZI5RBD5LCXLFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRGEYDGNJWUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSVGM33PORSXEX3JN5ZQ>
and Android
<https://github.com/notifications/mobile/android/B6MCBCJFETI23MTMF3NDNID5LCXLFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRGEYDGNJWUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>.
Download it today!
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Quick update The network briefly touched almost 3 GH/s today. Across the last 100 blocks, actual accumulated work averaged 1.36 GH/s. The latest 30 blocks averaged 19.5 seconds against the 20 second target. More hashrate means more blocks competing at the same height. That is happening, but every reorg during the last 45 minutes was only one block deep. P2P queues never exceeded five objects, all nodes kept converging and even the slowest four core machine stayed synced. The network has barely noticed the load. |
|
Need discord ? |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Parano1d mainnet launched at the scheduled genesis timestamp on August 21, 2026, at 16:00 UTC.
The v1.0.0 mainnet release provides binaries for Linux, Windows and macOS. Nodes can join the live network immediately.
Mainnet is a separate network with its own genesis. Testnet balances and mining rewards did not carry over.
Thank you to everyone who stress-tested the public testnet. Those tests exposed real peer discovery, synchronization and liveness problems, and the networking layer was redesigned before mainnet.
Mainnet consensus parameters
Genesis timestamp: August 21, 2026, 16:00 UTC (
1787328000)Block target: 20 seconds
ASERT epoch: 6 blocks
ASERT half-life: 120 seconds
Median-time-past window: 11 headers
Maximum future timestamp drift: 120 seconds
Transaction epoch: 144 blocks
Hard finality: 18 blocks
Recent block and reorganization suffix: 18 blocks
Initial State domain:
2^24slotsMaximum State domain:
2^32slotsState segment:
2^16slotsState expansion threshold: 75%, requiring 10 of 18 finalized headers
Default HistoryStep class: B25,
m=22, up to 25 effective page positionsLarge HistoryStep class: B255,
m=24, up to 255 effective page positionsTransaction page: 8 inputs, 2 outputs, 323 bytes
Maximum PagedSpend: 128 pages, 1,020 inputs, 256 outputs
Block body limit: 256 fixed bodies
Maximum ordinary user pages per block: 255
Maximum user inputs per block: 1,020
Maximum user outputs per block: 510
Maximum distinct State segments touched per block: 256
Proof of work: Poseidon2b with a 128-bit nonce
PoW role: canonical ordering of already proof-valid State transitions
Monetary parameters
Unit: 1 NOID = 1,000,000 μNOID
Initial block subsidy: 50 NOID
Launch-period allocation: 90% miners, 5% O(1) Network Fund and 5% Parano1d Lab
Allocation period: first three target-time years
After the allocation period: 100% of the subsidy goes to miners
Reward schedule: halves when the State domain expands
Permanent subsidy floor: 1 NOID
Premine: none
Base transaction fee: 5,000 μNOID
Input fee: 100 μNOID
Output fee: 700 μNOID
Base State-growth fee: 2,500 μNOID per net-new slot
Production proof profile
Committed trace field:
GF(2^128)Wide challenge field:
GF(2^256)Challenge support:
2^255Poseidon2b: width 4,
x^7, 8 full rounds, 58 partial roundsWallet queries: 65
History and BaseFold queries: 133
B25 codeword:
2^19at rate1/4B255 codeword:
2^21at rate1/4Maximum serialized authorization: 92,696 bytes
Target FRI security: 128 bits
Provable Block–Tiwari FS-FRI security: 127 bits
Conjectured Block–Tiwari FS-FRI security: 127 bits
Sequential ideal-QROM half-success boundary: 64.707407428576 bits
End-to-end post-quantum target: NIST PQC Category 1 resource envelope
Dominant Category 1 gate-depth floor: 173.273866314232 bits
Margin over the
2^170reference: 3.273866314232 bitsAll reactions