ignotusnemo/parano1d
1
0
Fork 0
Code Issues Pull requests Releases 9 Activity
9 releases 9 tags
  • v2.0.1 6c96ead36c

    Parano1d v2.0.1 Stable

    ignotusnemo released this 2026-09-29 19:00:35 +00:00 | 7 commits to main since this release

    Mandatory release. Upgrade before mainnet block 210,537.

    V2.0.1 supersedes v2.0.0. Starting at the v2 fork, a block derives its difficulty target from its parent header, so competing blocks with the same parent have the same target regardless of their own timestamps. The activation height is unchanged. If you installed v2.0.0, update to v2.0.1 before the fork. No reset or wallet migration is needed.

    This patch also adds read-only RPC fields for contract indexers: contract_opening_hex in getMempoolEntry and call or close classification in getBlockDetails. The v2 proof matrices and contract rules are unchanged.

    Update nodes, GUI wallets, block-producing pool nodes and exchange infrastructure before activation. Updated software switches rules automatically at that height; v1.1 cannot validate v2 blocks. The existing genesis, live balances and wallet secrets are preserved.

    The estimated activation time is October 10, 2026 at 11:59 PM PDT (October 11 at 06:59 UTC). Block height determines activation; the actual time depends on block production.

    1. Proof-native smart contracts

    From live value to live rights. Contracts add programmable spending rights to live State. Each transition is checked inside the shared recursive block proof, allowing validators to authenticate the current result without retaining or replaying the full interaction history.

    • A shared integer core supports checked arithmetic, conditions, inclusion height and persistent counters: up to 16 instructions, two persistent u64 counters and two scratch registers. Applications use this core without generating a separate matrix for each program.
    • Six ready-made templates cover payment with refund, timelocked vault, allowance wallet, period budget, recurring payment and gradual unlock. Custom programs are available through the editor, CLI and API. Scheduled policies execute when an authorized participant submits a call.
    • The GUI adds F7 Contracts, with Create, My Contracts and Open File workflows; Settings moves to F8. Fourteen contract RPC methods and CLI commands cover terms, funding, balances, reviewed calls, receipts and recovery. Funding and calls become available at v2 activation.
    • The journal displays saved interactions from either party. Importing receipts and contract updates merges evidence while preserving local records. Keep public terms and receipts with wallet backups: shared files carry terms and an optional receipt, and wallets discover locally known successor states after calls and reorgs.

    2. Capacity and consensus

    The target block interval changes from 20 to 30 seconds. ASERT uses a six-block reference epoch and a 180-second half-life, with height-aware timing across the fork. The earlier v1 → v1.1 transition remains unchanged.

    V2 class Matrix User pages Live inputs Contract calls Production
    Small m23 63 504 63 Default
    Large m24 206 504 63 Server opt-in

    Pages, inputs and calls share the same block budget. A call consumes one page and one input. Small holds up to 63 one-page payments or 63 calls; Large holds up to 206 one-page payments, or 63 calls plus 143 one-page payments, within the 504-input limit. The primary coinbase is separate; an additional mandatory system page consumes one of the listed pages.

    Large production requires --v2-large-blocks on the producing server. This permits fee-based selection of Large blocks; all nodes verify both classes. The GUI has no Large-production toggle.

    • Preserve the 1,100,000-byte terminal transport limit for both classes. Admission and block construction enforce the selected class's page, input and call limits together.
    • Retain the 144-block transaction epoch, 18-block finality boundary and 17-block maximum reorg. At the new target, the epoch is about 72 minutes and finality is about nine minutes. Body and undo retention remain 42 and 36 blocks.
    • Bind the first v2 proof to the last pre-v2 block through an authenticated fork origin. Cold synchronization and reorg handling verify this transition. The transition release includes old and new matrix material; verified retirement certificates enable later builds to omit the old matrices.

    3. Tokenomics

    V2 replaces State-triggered reward reductions with an explicit height schedule. The exact gross block subsidy starts at 16 NOID at the fork and follows:

    16 → 11.30 → 8 → 5.65 → 4 → 2.83 → 2 → 1.41 → 1 NOID

    Each step lasts 1,051,200 blocks from activation, nominally one year at 30 seconds per block. After eight reductions, the permanent tail is 1 NOID per block. Existing balances are unchanged.

    Early mainnet operation showed why the original monetary clock needed to change: live State occupancy measures outstanding outputs, and can stay low while payments and contract interactions reuse slots. Tying reductions solely to State expansion left their timing unpredictable. Height now gives issuance a visible schedule.

    State efficiency still has an economic incentive. Occupancy raises the fee for net-new live slots, and that growth component is burned. Consolidation frees slots and avoids the growth charge.

    Other improvements since v1.1.0

    • State processing: cache authenticated segments within a bounded memory budget and update only changed Merkle paths, reducing repeated hashing and copying across segments during synchronization, block application and proving.
    • Proof implementation: reuse matrix-column weights, reduce temporary folding buffers and cache exact previously verified carried matrix claims. This reduces repeated verification work, including on Small blocks following a Large block.
    • RPC and receipt recovery: expose retained block bodies after recursive suffix synchronization even when a block has no standalone proof bundle. Block RPCs and startup receipt recovery use those retained bodies.
    • Wallet reliability and storage: preserve reviewed calls and successor terms across submission failures; store identical proof bytes once across local contract receipts while keeping exported receipts self-contained.
    • Mining tools: align template refresh with fork timing, report active capacity, add configurable external-worker RPC timeouts with a 180-second default, and support finite mining runs through --blocks.
    • Proof accounting: correct response-cost accounting and extend the source-linked analysis to v2, historical ancestry and matrix retirement.
    • Documentation: update the README and English, Russian and Chinese documentation, including the contract core, API, GUI walkthroughs, receipts, network economics and an archive of earlier protocol profiles.
    Downloads