Parano1d

PARANO1D

NOID

Proof-native Layer 1 using Poseidon2b proof of work to order recursively proven live UTXO transitions. Signatureless authorization proves knowledge of a spending secret; public addresses, amounts and transactions are not concealed. V2 adds bounded proof-native contracts. Protocol claims are project-reported, not an independent audit.SourcesREADMESecurity model

EVERY CLAIM IS SOURCE-LINKED · “—” MEANS NOT VERIFIED, NOT ZERO · METHODOLOGY · REVISIONS

[OVERVIEW]

Mission

Authenticate current live value and programmable spending rights without replaying all historical execution. Wallets prove authorization, producers prove state transitions and recursive ancestry, and PoW chooses canonical order. Nodes retain current State and bounded recent block bodies; compact headers persist. Pruning is not anonymity.SourcesREADMEHardware

Founders

  • Ignotus Nemo (public pseudonym; project-attributed designer/developer)

Team

Built by the public pseudonym Ignotus Nemo, credited in the README as designer and developer; source headers name the copyright holder "Paranoid Zero". The GitHub contributors API lists two contributors: ignotusnemo with 733 commits and getrigeos with 1, so development is effectively a single-maintainer project with high key-person risk. No investors, venture funding, foundation or registered legal entity were disclosed or verified. The protocol provides a development allocation inside consensus: for the first three target-time years, 5% of each block subsidy goes to the O(1) Network Fund and 5% to ParanO(1)d Lab, paid to fixed addresses hard-coded in the allocation module.SourcesREADMEDevelopment allocation.rsContributors

Key milestones

  • 2026-08-21Mainnet genesis (v1.0.0)Genesis at 16:00:00 UTC (timestamp 1787328000), with 50 NOID per 20-second block and no premine.SourcesParametersRelease v1.0.0README
  • 2026-08-23v1.0.1: P2P memory-growth fixFixed P2P memory growth observed under sustained public mainnet traffic; gossip is now forwarded only after local admission.SourceRelease v1.0.1
  • 2026-08-24ASERT difficulty bug reportedIssue #20 showed the fractional ASERT polynomial understated the BCH reference by up to about 15.2%. Fixing it required a coordinated consensus change.SourceIssue #20
  • 2026-09-14v1.1 activation at height 95,125Mandatory v1.1.0 rules activated at block 95,125 (block timestamp 2026-09-14 13:46 UTC): corrected ASERT, compressed HistoryStep terminals and a 1,100,000-byte terminal cap.SourcesRelease v1.1.0parano1d-pool.fun · Block 95,125
  • 2026-09-26v2.0.0 published, then supersededv2 source release with proof-native contracts, 30-second blocks and height-based issuance. Superseded by mandatory v2.0.1 before activation (difficulty target derived from the parent header); v2.0.0 assets were removed.SourcesRelease v2.0.0Release v2.0.1
  • 2026-10-08v2.0.3: database-growth fixFixed mdbx.dat growing about 3,500 MB per day (issue #50, reported and fixed the same day).SourcesRelease v2.0.3Issue #50
  • 2026-10-11V2 activation at height 210,537Block 210,537 is stamped 2026-10-11 06:48:53 UTC, versus an estimated 06:59 UTC. Issuance dropped from 50 NOID per 20 s to 16 NOID per 30 s, a 78.67% cut in the gross issuance rate.Sourcesparano1d-pool.fun · Block 210,537Release v2.0.1Economics
  • 2026-10-14v2.0.4: optional performance releaseNo consensus changes. Reported 72% lower average P2P CPU and 1.66x faster HistoryStep verification under live peer load; legacy proof matrices retired via certificates.SourceRelease v2.0.4

[TECHNOLOGY]

CONSENSUS_MECHANISM
Proof of work (Poseidon2b); recursive HistoryStep validates state transitions
BLOCKCHAIN_TYPE
Proof-native Layer 1
BLOCK_TIME
30s
SMART_CONTRACT_SUPPORT
✓ YES
PROGRAMMING_LANGUAGES
Rust

Scalability & architecture

  • Recursive History proofs authenticate state transitions and ancestry; block producers must construct a valid proof before searching a nonce. External workers search nonce templates, not arbitrary transaction sets.SourceREADME
  • Sparse live UTXO slots are reused after spends; historical bodies are pruned after 42 blocks. Storage still grows with current live State, headers, proof material and snapshot staging.SourcesREADMEHardware
  • V2 Small: 63 pages, 504 inputs, 63 calls. Large: 206 pages, 504 inputs, 63 calls. Budgets apply together; multi-page payments consume multiple pages. These are capacity limits, not measured TPS.SourceParameters
  • Contracts share a bounded integer core: 16 instructions, two persistent u64 counters, two scratch registers, no loops or cross-contract calls. They are not an EVM compatibility claim.SourceREADME
  • Source code is published under Apache License 2.0; this is a software license, not regulatory permission or an audit.SourceLicense

[TOKENOMICS]

CIRCULATING_SUPPLY
10.67M
MAX_SUPPLY
No Cap
EMISSION_SCHEDULE

No cap. Pre-V2 (heights 1–210,536): 50 NOID per 20-second block. Sampled headers at heights 1, 95,125, 210,537 and 220,804 all show State level 24, so no State-triggered halving occurred: 10,526,800 NOID gross. V2 (from height 210,537, 2026-10-11): 16 → 11.30 → 8 → 5.65 → 4 → 2.83 → 2 → 1.41 NOID per 30-second block, one step per 1,051,200 blocks (a nominal year), then a permanent 1 NOID tail (1,051,200 NOID a year). CryptoIA arithmetic from the published constants: about 27.35M NOID gross by the end of tier 0 (nominal Oct 2027), 39.22M by the end of tier 1 (Oct 2028), 46.51M when the development allocation ends at height 3,223,778 (nominal 2029-08-20), and 64.34M when the tail begins at height 8,620,137 (nominal Oct 2034). The numeric circulating-supply tile is the explorer’s live-State value, not a verified liquid float; gross scheduled issuance is not total supply. Snapshot at height 220,804: gross scheduled issuance 10,691,088 NOID; the explorer reports 10,672,338.5625 NOID of live supply. The 18,749 NOID gap reconciles almost exactly to the schedule rules: 15,880 NOID from the incomplete legacy fund day that was never paid, plus 2,604.8 NOID of V2 fund accrual not yet paid out. That leaves about 265 NOID unexplained, consistent with (but not proven to be) state-growth fee burns. Current pace: the network is under two months old, so there is no year-over-year history. V2 already cut issuance from 216,000 to 46,080 NOID a day (−78.67%). At the current tier that is about 1.38M NOID per 30 days and 16.82M over the next nominal year, with each later tier issuing less (11.88M, then 8.41M, then 5.94M). Distribution is front-loaded: about 10.5M of today's ~10.67M NOID were mined in the first 51 days at the pre-V2 rate.SourcesEconomicsLegacy profilesParametersparano1d-pool.fun · Explorerparano1d-pool.fun · Block 220,804parano1d-pool.fun · Block 210,537parano1d-pool.fun · Block 95,125Observed 2026-10-14 20:00 UTC

TOKEN_DISTRIBUTION
Miners
90%
Share of each block subsidy until height 3,223,778 (three target-time years from genesis), then 100%. Transaction fees, after the state-growth burn, also go to the miner.SourcesDevelopment allocation.rsEconomics
O(1) Network Fund
5%
Mandatory daily payout to a fixed consensus address (2,304 NOID per full day at the 16 NOID tier). About 0.52M NOID were paid pre-V2; the maximum to the end of the allocation is roughly 2.3M NOID by CryptoIA arithmetic.SourcesDevelopment allocation.rsEconomics
ParanO(1)d Lab
5%
Same mechanics and size as the Network Fund. Together, the two funds receive at most about 4.6M NOID, roughly 10% of gross issuance through height 3,223,778.SourcesDevelopment allocation.rsEconomics
Premine / sale
0%
The README states no premine; no ICO or token sale is documented.SourceREADME
TOKEN_UTILITY

Native coin pays transfers and proof-native contract funding/calls and rewards mining. Fees comprise 5,000 microNOID per logical transaction, 100 per input, 700 per output and 2,500 times occupancy pressure per net-new live slot. Growth fees are burned; other components and tips are miner-claimable. Pressure multipliers are 1/2/4/8 at the documented occupancy bands; relay floors are separate local policy.SourceEconomics

[CHART]

No verified TradingView market for Parano1d NOID yet. Trading venues and source links are listed under Economics.

[MARKET_DATA]

Exchange listings

SafeTrade (NOID/USDT)Sourcelivecoinwatch.com · Parano1d NOID

Last updated: Oct 14, 2026, 5:59 PM UTC

[ECONOMICS]

Trading pairs

PairExchangeSource
NOID/USDTSafeTradeLiveCoinWatch ↗
Only listed pair. On 2026-10-14 ~20:00 UTC, LiveCoinWatch showed ~$0.330 and $193.7K of 24h volume, but $0 in ±2% depth and no market cap. Multiplying that price by explorer live supply gives about $3.5M; that is CryptoIA arithmetic, not a reported market cap. Quotes are volatile, and single-venue volume is not liquidity.

[ECOSYSTEM]

Integrations

Parano1d CoreFirst-party node and CLI

Core contains parano1d, parano1d-cli and parano1d-miner. The GUI wallet is distributed separately.SourceCore

Native GUI walletFirst-party wallet

Linux, Windows and macOS wallet with a supervised node and contract tooling. This is not evidence of independent application adoption.SourceREADME

Contract templatesFirst-party developer tooling

Refundable payments, timelocked vaults, allowance wallets, period budgets, recurring payments and gradual release. Scheduled actions require authorized calls; templates are not autonomous agents.SourceREADME

parano1d-pool.funThird-party pool + explorer

3% fee, stratum main.parano1d-pool.fun:3784. Lifetime 7,185 blocks and 322,992.88 NOID mined. At the snapshot it had 124 MH/s, 0 of the last 60 chain blocks, and 27 of its own last 60 found blocks orphaned. It also runs the read-only explorer used for chain data here.Sourcesparano1d-pool.funparano1d-pool.fun · ExplorerObserved 2026-10-14 20:00 UTC

AriaPoolThird-party pool

PPLNS with a 1% fee, advertising NVIDIA RTX 30–50 GPU and x86-64 CPU mining. Its stats API reports 112 block candidates, 68 won and 39 orphaned, with 0 H/s pool hashrate at the snapshot. The page still lists a 20 s block target, which is outdated since the V2 30 s target.Sourcespool.ariabrain.com · Noidpool.ariabrain.com · StatsObserved 2026-10-14 20:00 UTC

noidexplorer.spaceCommunity explorer

Independent dashboard for mempool, fees, hashrate history and blocks. CryptoIA did not use it for the numbers in this dossier.Sourcenoidexplorer.space

noid.network AutoResearchFirst-party research platform

Public, signed-in research tasks that attack or reproduce the soundness accounting; accepted results move a published frontier.Sourcenoid.network · Evidence

dApps

NO ONEGame (in development)

Proof-native social deduction game built on V2 contracts and portable receipts; concept-stage website and repository only.SourcesGitHub · ignotusnemo/noonenoone.parano1d.org

Agent CoreAgent tooling

Read-only verifier of live rights and receipts for AI agents, running its own node.SourceGitHub · ignotusnemo/agcore

Developer metrics

GitHub Stars: 40
Forks: 21
Contributors: 2
30d Commits: 27

Community metrics

Discord: 448

[UNIQUE_VALUE_PROPOSITION]

Core value proposition

Project thesis: current live value and spending rights carry proof of valid ancestry, separating validity from PoW ordering without requiring full historical execution replay.SourceREADME

Key differentiators

1

Signatureless secret-knowledge authorization rather than a public-key transaction signature; transparent public ledger data remains.SourceREADME

2

Live UTXO reuse and bounded historical body retention; portable payment/contract evidence remains useful after pruning.SourcesREADMEContracts

3

Bounded contract programs share the recursive proving core rather than requiring a custom circuit per application.SourcesContractsREADME

Competitive edge

Analytical interpretation, not a market-share claim: reducing dependence on replayed historical execution can benefit state verification and portable receipts. This exchanges historical storage burden for proof construction, verification and authenticated-material complexity.SourcesREADMEHardware

Target audience

Documented interfaces target node operators, miners, wallet users and developers building bounded programmable payments. This describes available tooling, not measured adoption.SourcesCoreContracts

[COMPARATIVE]

Competitive positioning

Parano1d competes on verification architecture, not on throughput or liquidity. Like Mina, it gives new nodes a succinct proof of the current state instead of a history replay. Unlike Mina, it keeps Bitcoin-style proof-of-work ordering and makes the proving full node, not the hash worker, the unit of block production. Against PoW peers it trades raw throughput and maturity for proof-based bootstrap and signatureless, post-quantum-oriented authorization. Its block capacity is about 63–206 one-page payments per 30 s. As of the 2026-10-14 snapshot it is a two-month-old, single-maintainer network with one thin third-party spot market and no independent audit. The architecture is the thesis; adoption is not yet evidenced.Sourcesparano1d.orgMiningParametersdocs.minaprotocol.comparano1d-pool.fun · ExplorerObserved 2026-10-14 20:00 UTC

Strengths

  • New nodes bootstrap from the live UTXO State, a terminal proof and an 18-block suffix, not a history replay, and the procedure is the same in year one and year ten. Storage tracks live outputs (90,375 live slots at height 220,804), not chain age.Sourcesparano1d.orgparano1d-pool.fun · Block 220,804Observed 2026-10-14 20:00 UTC
  • Signatureless ownership: wallets prove knowledge of a 256-bit secret in zero knowledge, with no public key or signature on the wire. The stack is a transparent hash-based proof system with no trusted setup.Sourcesparano1d.orgRelease v1.0.0
  • Issuance is legible: a fixed height schedule with published integer constants and a 1 NOID tail. The explorer's live supply reconciles to the schedule within about 265 NOID.SourcesEconomicsparano1d-pool.fun · ExplorerObserved 2026-10-14 20:00 UTC
  • Fast, documented incident response. The defects in the record (ASERT, P2P memory, database growth, v2.0.0 targets) were fixed within hours to days, with public issues and release notes.SourcesIssue #20Issue #50Release v2.0.1Release v1.0.1
  • Source-pinned security accounting with public reproduction (noid.network) and a funded bug bounty of up to 10,000 NOID.Sourcesnoid.network · EvidenceSecurity

Weaknesses

  • Front-loaded issuance. About 10.5M NOID were mined in the first 51 days at the original 50-NOID-per-20 s rate, so early miners hold most of today's supply. After the V2 cut, issuance continues at about 46,080 NOID a day (~1.38M per 30 days) and steps down each nominal year.SourcesEconomicsLegacy profilesparano1d-pool.fun · ExplorerObserved 2026-10-14 20:00 UTC
  • Single-maintainer development (733 of 734 commits), with two mandatory hard forks and one withdrawn release in the first 51 days. There is high key-person and upgrade-coordination risk.SourcesContributorsRelease v1.1.0Release v2.0.1
  • Thin, unverified market. There is one listed spot pair (SafeTrade NOID/USDT). LiveCoinWatch reported about $193.7K in 24-hour volume but $0 in ±2% depth and no market cap. Volume on a single small exchange is not evidence of liquidity.Sourcelivecoinwatch.com · Parano1d NOIDObserved 2026-10-14 20:00 UTC
  • No third-party audit. The NIST Category 1 claim is a conditional, self-published assessment, and SECURITY.md is stale (it lists 1.0.x as the supported line).SourcesSecurity modelSecurity
  • Pools are marginal and orphan-prone: parano1d-pool.fun found 0 of the last 60 chain blocks, with 27 of its own last 60 orphaned; AriaPool showed 39 orphans out of 112 candidates. Small miners face high variance and stale-work loss.Sourcesparano1d-pool.funpool.ariabrain.com · StatsObserved 2026-10-14 20:00 UTC

Similar projects

Mina ProtocolZcashMoneroBitcoinKaspaPearl 2

[ROADMAP]

Roadmap

V1 mainnet (heights 1–210,536)COMPLETED

V2 (active from height 210,537, 2026-10-11)COMPLETED

NO ONE: proof-native social deduction gameIN PROGRESS

  • First game from the founder, announced 2026-10-11 at noone.parano1d.org. Players receive contracts that set their rights, budgets and permitted actions, and they present receipts as evidence. A traitor can show a genuine receipt while telling a misleading story. The README places it at concept stage: detailed rules, secret roles and the link between contract transitions and in-game station events are still being designed. No release date has been published.SourcesGitHub · ignotusnemo/noonenoone.parano1d.org

Live Agents / Agent CoreIN PROGRESS

  • Agent Core (agcore, first published 2026-09-30) gives an AI agent its own Parano1d node for checking contract rights and receipts. The first version is read-only: it never holds spending keys or broadcasts transactions. A recorded demo shows three agents sharing a contract allowance across separate nodes.SourcesGitHub · ignotusnemo/agcorelab.parano1d.org · Live Agents

Open security obligationsIN PROGRESS

  • The full adaptive all-root composition embedding is still an explicit premise, not a proven result, on noid.network.Sourcenoid.network · Evidence

Upcoming milestones

  • 2027-10 (nominal)Issuance tier 1: 11.30 NOID per blockHeight 1,261,737; the date depends on actual block production.SourceEconomics
  • 2028-10 (nominal)Issuance tier 2: 8 NOID per blockHeight 2,312,937.SourceEconomics
  • 2029-08-20 (nominal)Development allocation endsAfter height 3,223,778, 100% of the subsidy goes to miners and the two 5% fund payouts stop.SourcesEconomicsDevelopment allocation.rs
  • 2034-10 (nominal)Permanent 1 NOID tailHeight 8,620,137; afterwards 1,051,200 NOID per nominal year.SourceEconomics

Risk factors

Outlook

Verdict: a technically serious, high-risk early network. Bull case: a coherent, documented design (proof-based bootstrap, signatureless post-quantum-oriented authorization, legible issuance), fast and transparent fixes, a public research and bounty program, and supply that reconciles to its schedule. If the premises hold and builders adopt the contract model, Parano1d is one of the few PoW chains whose verification cost does not grow with age. Bear case: front-loaded issuance (about 10.5M NOID mined in the first 51 days, ~46K a day now); one maintainer; no audit; one thin exchange with no measurable depth; and pools that rarely win blocks. What would change the view: an independent audit, a second maintainer, deeper multi-venue liquidity, and sustained real transaction volume. Treat it as experimental infrastructure, not an established asset. Not financial advice.SourcesEconomicsparano1d-pool.fun · ExplorerContributorslivecoinwatch.com · Parano1d NOIDSecurity modelObserved 2026-10-14 20:00 UTC

[GOVERNANCE]

Governance model

Consensus software upgrades; formal voting process not verified

Voting mechanism

The reviewed protocol describes PoW ordering and fixed consensus rules, not a verified token-holder ballot. Do not infer a DAO, delegated voting, voting participation or a treasury balance from mining.SourcesREADMEParameters

Proposal process

In practice, protocol change is maintainer-led: releases are published by the single principal developer and activate at a fixed block height. Within the first 51 days there were two mandatory forks: v1.1 at height 95,125 and V2 at height 210,537. A third mandatory release, v2.0.1, replaced v2.0.0 before activation. Operators accept a change by upgrading, and nodes that do not upgrade cannot validate the new blocks. No on-chain voting, signalling threshold or formal improvement-proposal process was found. The economics document states that changing the monetary rules again would require another consensus upgrade.SourcesRelease v1.1.0Release v2.0.1Economics

[SECURITY]

Bug bounty program

Parano1d Bug Hunt (scope updated 2026-08-27): 500 NOID for a confirmed non-critical mainnet bug with material impact, and 10,000 NOID for a critical one. Critical means accepting an invalid State or proof, unauthorized spending or issuance, wallet-secret disclosure, remote code execution, or a deterministic network split or halt. The scope covers protocol, consensus, State, P2P, the proof stack, the wallet/GUI and built-in mining. External mining, pool integration and parano1d-miner are excluded. Rewards are paid in NOID with no fiat equivalent, and reports go through GitHub private vulnerability reporting. SECURITY.md still lists only the 1.0.x line as supported even though mainnet runs 2.0.x, so the documentation is stale.SourceSecurity

Security incidents

  • Aug 12, 2026Pre-launch v0.1.0 nodes could not sync from height 0: a HistoryStep matrix whitelist drift was reproduced on multiple x86-64 machines.Impact: Fresh nodes were rejected during HistoryStep verification (labelled a historical testnet issue).Response: Closed 2026-08-16, before the 2026-08-21 genesis.SourceIssue #5
  • Aug 23, 2026P2P memory growth under sustained public mainnet traffic two days after genesis.Impact: Node resource exhaustion risk; invalid or stale gossip was being amplified.Response: v1.0.1 forwards transactions only after local admission and bounds GossipSub queues.SourceRelease v1.0.1
  • Aug 24, 2026The ASERT difficulty polynomial diverged from the BCH reference it claimed to match; the cubic term was always zero.Impact: Difficulty targets were understated by up to about 15.2%, a consensus-critical defect.Response: Fixed through the mandatory v1.1.0 fork at height 95,125, preserving the legacy calculation for earlier blocks.SourcesIssue #20Release v1.1.0
  • Oct 5, 2026v2.0.0 was withdrawn before activation: V2 blocks must derive their difficulty target from the parent header.Impact: Competing blocks with the same parent could have had different targets; the fix landed before any V2 block existed.Response: Mandatory v2.0.1 superseded v2.0.0, and its assets were removed.SourcesRelease v2.0.1Release v2.0.0
  • Oct 8, 2026mdbx.dat grew about 3,500 MB per day on v2.0.x even though the database held only ~0.35 GB of data.Impact: Disk exhaustion risk for nodes and GUI wallets; one reported wallet folder reached about 34 GB in under a week.Response: Fixed in v2.0.3 the same day by bounding the MDBX free-extent search.SourcesIssue #50Release v2.0.3
  • Oct 11, 2026After V2 activation, getBlockDetails reported "class unavailable" for some blocks applied inside multi-block suffixes or short reorgs.Impact: RPC reporting gap only; bodies, transactions and rewards were intact.Response: Closed 2026-10-12.SourceIssue #51

Security practices

  • Validity and chain ordering are separate: a valid nonce cannot repair an invalid proof. State transfer is checked against authenticated roots rather than trusted because a seed supplied it.SourceSecurity model
  • The project publishes a conditional NIST PQC Category 1 resource assessment, not NIST certification, an independent audit, or proof-assistant verification of the whole implementation. Assumptions include honest preprocessing and fixed-hash/resource-price premises.SourceSecurity model
  • Zero knowledge hides the spending witness, not public amounts, owners, programs or relayed transactions. Third parties may archive data; pruning does not promise privacy.SourceSecurity model
  • Protect the 256-bit master secret and local wallet files; the built-in key is not password-encrypted. Back up contract terms and receipts because the secret alone cannot reconstruct them.SourcesREADMEContracts
  • Verify release SHA-256 sums before extraction, run hardware preflight and keep owner RPC local. Peer Ed25519 identity authenticates transport, not spending authority.SourcesCoreSecurity model
  • No independently verified audit report, bounty reward schedule or comprehensive incident history was established in this review; those structured fields are deliberately unpopulated.
  • No independent third-party audit firm report was found. The external evidence is public AutoResearch: noid.network lists accepted independent reproductions and negative attack-search results against the pinned soundness calculator. That is useful, but it is not an audit.Sourcenoid.network · Evidence
  • The V2 ancestry accounting reports a conditional NIST PQC Category 1 assessment (log2 dominant gate-depth floor 173.3897612554174) under explicit all-root composition, ideal-compiler, fixed-Poseidon2b, response-price and honest-preprocessing premises. These are stated assumptions, not proofs of the whole implementation.SourcesSecurity modelV2 retirement

[REGULATORY]

Regulatory classification

Not established by reviewed sources; not a legal determination

Compliance status

Unverified; software publication or exchange listing is not regulatory approval

[COMMUNITY]

[SOCIAL_MEDIA]

X
@ignotus_nemo
Discord

[TECHNICAL_DETAILS]

Node requirements

Minimum Hardware
Production x86-64 requires SSE4.1 and PCLMULQDQ; ARM64 requires NEON and PMULL. Run parano1d --check-hardware on the actual host/guest; scalar mode is not a production fallback.SourceHardware
Network Requirements
P2P TCP 9600; local administrative JSON-RPC TCP 9601. Keep owner RPC on loopback or authenticated private transport. Documentation suggests an unmetered 100 Mbit/s baseline.SourceHardware
Recommended Hardware
Published receiver qualification used four cores and 8 GiB RAM with no swap; this is a tested scenario, not a universal minimum or miner sizing guarantee. Measure producer memory and latency separately.SourceHardware
Storage Requirements
SSD/NVMe; no fixed lifetime disk claim. Retain current sparse State, compact headers, 42 bodies, 36 undo blocks and proof/wallet material. Reserve space for a staged replacement snapshot.SourceHardware

Technical specifications

Ports
P2P 9600; local RPC 127.0.0.1:9601. A local interface is not a hosted public RPC endpoint.SourceCore
State
Domain 2^24 through 2^32 slots, segments of 2^16; expansion requires at least 75% occupancy in 10 of 18 finalized headers.SourceParameters
Mining
Built-in miner and external nonce worker; transaction selection and proof preparation remain in the full node. GPU miners on a pool only search nonces; the pool’s node does the proving. A solo miner needs to run its own proving node.SourceREADME
Vs Mina
Both offer succinct verification: Mina advertises a 22 KB blockchain and zero-knowledge zkApps. Parano1d orders blocks by PoW instead and keeps transparent, hash-based proofs over binary fields.Sourcesdocs.minaprotocol.comparano1d.org
Genesis
2026-08-21 16:00:00 UTC; genesis ID 860e70453390bf815718e933aa4927167a13d098b0151391eefd722ee1add610SourceREADME
Vs Kaspa
Kaspa runs a PoW blockDAG at 10 blocks per second for throughput. Parano1d targets one proven block per 30 s; it optimizes verification cost, not block rate.Sourceskaspa.org · FeaturesParameters
Vs Pearl
Pearl is another novel-PoW Layer 1 tracked on CryptoIA, using proof of useful work. Both are young, thinly traded, mining-led networks; compare the two dossiers before treating either as established.Sourcecryptoia.ai · Pearl 2
Vs Zcash
Both are PoW chains with zero-knowledge proofs. Zcash uses ZK for shielded transfers on a replayed chain; Parano1d uses ZK for authorization and whole-state validity, and its ledger data is transparent rather than private.Sourceszips.z.cash · Protocolparano1d.org
Finality
Hard-finality boundary 18 blocks; maximum permitted reorganization 17 blocks. This is a consensus policy, not an unconditional economic safety guarantee.SourcesParametersSecurity model
Vs Monero
Both have perpetual tail emission: Monero 0.6 XMR per block, Parano1d 1 NOID per block after year eight. Monero mines with CPU RandomX; Parano1d mining is bound by proof construction plus Poseidon2b nonce search.Sourcesgetmonero.org · Tail Emissiongetmonero.org · RandomxEconomics
Vs Bitcoin
Both use PoW plus cumulative-work fork choice. Bitcoin full nodes validate history from genesis; Parano1d nodes verify a recursive proof of the live State. Bitcoin's hash worker can mine with a header template; Parano1d's work requires a proving node.Sourcesbitcoin.org · BitcoinMining
Difficulty
30-second target; ASERT reference epoch 6 blocks, half-life 180 seconds. Actual block intervals vary.SourceParameters
Proof Stack
GF(2^128) traces; GF(2^256) challenges; Poseidon2b, FROST-GKR and FRI-Binius. Category 1 assessment is conditional on the published composition, compiler, preprocessing and resource assumptions.SourcesREADMESecurity model
Contract ABI
ABI 3; 16 instructions; two persistent and two scratch u64 registers. Six supplied policy templates plus custom bounded programs. Back up public terms and receipts as well as the spending secret.SourcesParametersContracts
Live Network
Height 220,804 (block timestamp 2026-10-14 19:59:36 UTC), difficulty 43-bit, 11 explorer peers, mempool 2. Average block interval since V2 activation is 29.87 s over 10,267 blocks; legacy blocks averaged 20.77 s against the 20 s target.Sourcesparano1d-pool.fun · Explorerparano1d-pool.fun · Block 220,804parano1d-pool.fun · Block 210,537Observed 2026-10-14 20:00 UTC
Proving Cost
Isolated construction (Intel i7-1365U, 12 threads): Small 63 payments 17.6 s, Large 206 payments 42.6 s; verification 0.8–2.5 s. On the full daemon the producer needed 20.8–67.3 s, and a receiver capped at 4 CPUs/8 GiB verified in 2.7–8.4 s, peaking at 1.65 GiB. Context: these are developer benchmarks on a low-power laptop CPU. The proof is built once per block by the node (solo miner or pool), while GPUs only search nonces against the finished template, so pool GPU miners never run this step. Small blocks are the default; Large is opt-in.SourcePerformance
Address And Unit
bech32m o1 addresses; 1 NOID = 1,000,000 microNOID; consensus amounts use integer microNOID. Native coin, not an EVM token contract.SourcesREADMEEconomics
Evidence Limits
No live hashrate, node count, measured sustained TPS, token-holder count or current supply was independently measured for this snapshot.
Source Snapshot
Protocol docs pinned at commit 3ea1221ac09c45342419081d96acc54f5aa4b972; live chain, pool, market and community figures observed 2026-10-14 20:00 UTC. Not a live node attestation.
State Occupancy
90,375 live slots in a 2^24-slot domain (≈0.54%) at height 220,804. The state-growth fee multiplier is 1× (below 50% occupancy); expansion requires ≥75% occupancy.Sourcesparano1d-pool.fun · Block 220,804EconomicsObserved 2026-10-14 20:00 UTC
Network Hashrate
About 286 GH/s, per AriaPool's network estimate (difficulty 8.28e12 hashes per block). parano1d-pool.fun shows a 430 GH/s 'network floor' using a different method. Treat both as third-party estimates.Sourcespool.ariabrain.com · Statsparano1d-pool.funObserved 2026-10-14 20:00 UTC
Throughput Ceiling
Consensus capacity per 30 s block: 63 one-page payments (Small) or 206 (Large, server opt-in), i.e. a ceiling of roughly 2.1–6.9 one-page payments per second. That is capacity, not measured throughput; no sustained public TPS was measured.SourcesParametersPerformance
Miner Concentration
Blocks 220,208–220,804 (597 blocks, ~5 h): 9 payout addresses. Top shares: 26.8%, 19.9%, 16.1%, 12.9%, 11.9%, 6.0%, 5.0%, 1.2%, 0.2%. This is typical of PoW networks, where a handful of pools or large operators produce most blocks. The two public pools identified here (parano1d-pool.fun and AriaPool) won few recent blocks, so the producing addresses look like solo/private operators or unlisted pools; their identities were not verified.Sourcesparano1d-pool.fun · Explorerparano1d-pool.funpool.ariabrain.com · StatsObserved 2026-10-14 20:00 UTC
Issuance Reconciliation
Gross schedule to height 220,804 = 10,526,800 (legacy) + 164,288 (V2) = 10,691,088 NOID. Explorer live supply is 10,672,338.5625. 15,880 is the unpaid legacy fund day and 2,604.8 is unpaid V2 fund accrual; the ~265 NOID residual is unexplained.SourcesEconomicsDevelopment allocation.rsparano1d-pool.fun · ExplorerObserved 2026-10-14 20:00 UTC