ignotusnemo/parano1d
1
0
Fork 0
Code Issues Pull requests Releases 6 Activity
6 releases 6 tags
  • v1.0.3 6349f5f215

    Parano1d v1.0.3 Stable

    ignotusnemo released this 2026-08-27 14:41:04 +00:00 | 30 commits to main since this release

    External-mining credentials are now restricted to getBlockTemplate and submitBlock. A worker token can no longer authorize wallet operations, node control or any other RPC method. Existing pool and worker commands using --mining-key TOKEN and --key TOKEN remain compatible. Operators can keep the credential out of process arguments with the new protected key-file options:

    parano1d --mode extminer --mining-key-file /secure/parano1d-mining.key
parano1d-miner --key-file /secure/parano1d-mining.key

    Synchronization now switches to an authenticated snapshot once a node falls beyond the 18-block recent suffix, while retaining one bounded exact-object tail after a verified snapshot is installed. Snapshot selection and rebasing remain bound to the HeaderDAG-selected ancestry. Direct header responses must match the requested range, and direct header windows are capped so competing branches fit within the bounded HeaderDAG. This prevents long sequential catch-up, stale snapshot loops and arrival-order pressure on the header control plane. The existing 512-header direct window and 4,096-header disk-staged snapshot batches are unchanged.

    Wallet receipts now survive a chain-data purge and snapshot bootstrap until their permanent headers arrive. Outgoing transactions that reappear on a replacement branch are confirmed by logical transaction ID, and reorg duplicate removal releases the corresponding mempool slot reservations.

    The obsolete first-mainnet-run testnet cleanup has been removed. Starting a current release never deletes an existing data directory or wallet key as part of that retired migration.

    The GUI adds a clipboard button to the recipient field, estimates network hashrate over 30 blocks for a steadier display, and labels explorer transaction fees explicitly in NOID.

    There are no consensus-rule, wire-protocol, proof-profile, matrix, port or storage-format changes. v1.0.2 and v1.0.3 nodes remain network-compatible, and no data reset or configuration change is required. Wallet users, node operators, pools and miners should update.

    Downloads