Repository navigation
Testnet v0.3.1 — network upgrade 1, more seeds, crash fix
·
2 commits
to main
since this release
MoneroUSD Wallet 0.3.1 — testnet
Reliability
- getrandom is an every-platform dependency of the ledger, not a Unix-only one
- the wallet's lockfile records getrandom, which the node it links now uses
- the lockfile records getrandom as a direct dependency of the node and the ledger
- OS randomness is read without a file descriptor, so running out of descriptors can no longer crash a node
Releases
- wallet 0.3.1 — the testnet's NETWORK UPGRADE 1 build, the 5-peer seed list and the fd-free randomness
- quicker wallet builds — one shared target dir for the node and the wallet, rust-cache and npm cache between runs
Consensus
- NETWORK UPGRADE 1 — the grind and ASERT take effect at a height (testnet 7,000; rig from genesis; mainnet unset), so the testnet upgrades without a reset
- production is the grind and the DAA is ASERT, so chain weight follows hash
- PowMiner::mine_paced — the grind at a duty share of one thread, stoppable on a new tip
Network
- the wallet's compiled testnet seed list carries the chain's 5 dialable peers, not only the origin
- the rig network — its own genesis ("MUSDRIG!"), no compiled launch, the faucet open as on the testnet
- a node whose peers are offline no longer restarts itself — the wedge ladder first asks whether this client reaches its own onion
- the fair-share line says when the DAG's producer figure appears or changes, not only when the count does
Network safety
- the hash arm judges a full DAA window only, so a young chain's settling difficulty does not read degraded
- the heal weigh print holds its node guard across the read (E0716 on ef8b5a1c)
- the recovery pin prints each party's tip blue score, blue work and blocks held at the heal and every slice
- the view verdict reads the hash arriving per unit of time, so a paced eclipse still reads degraded
Finality
- the deferred-vote pool holds a fixed share per voter, so one key cannot evict honest early votes
- the open finality tally is bounded by its own vote frontier, so it no longer grows while finality does not move
Joining
- a completed adopted prefix marks its proven rows chain-bound, as a replayer holds them
- a re-adopt records its own base, so its adopted prefix completes as a first adopt's does
- the anticone carry leaves out a block the frozen state does not count; the joiner-side re-fold is reverted (measured worse)
- the server names which carried anticone block its frozen state counts (covered), so the adopter re-folds only one born after the freeze
- a carried block the frozen join state does not count is re-folded by an exact past test, never judged by its score
Explorer
- the explorer reads the block target from the node instead of stating 0.5 s
Node
- the bond-tree route serves founding_seated beside validators, so a rig's checks read their own seats
Wallet
- an accepted payment is handed to the node again until the chain carries it
- the update fetch retries a failed Tor exit on a fresh circuit (3 tries)
Speed
- Kaspa's spendability — a note spends once folded, anchored 2 steps under the newest fold, no vote read
Upgrade before testnet block 7,000: from that height the network runs NETWORK UPGRADE 1 (blocks are found by the hash search; difficulty adjusts every block). A wallet still on 0.3.0 at that height will leave the chain.
Source: 02d7a1b1f6c74019b326e300abb8a3a1b6601b78