Hi all,
Aurumcoin (AU) is a small SHA-256 chain that has been running since 2014. Its old client was based on Bitcoin Core 0.12. The developers have now released a new client rebased on Bitcoin Core v32.1. Now it's time to introduce the new version to the public and put it through the hard test of reality, which is why I'd appreciate independent review.
Release v32.1.0: https://github.com/aurumcoin-au/Aurumcoin-AU/releases/tag/v32.1.0Binaries: Windows (Qt + daemon), Linux x86_64, Linux ARM64. SHA256SUMS is signed. Signing key fingerprint:
8BC8 2533 58BD 3BB6 4675 7A84 B051 CC2E 2F85 9675
What the release notes claim:- The consensus rules are unchanged from 0.12 ("Version A"), so v32.1 and 0.12 nodes run on the same network. The existing chain is said to validate fully, and blocks have been mined in both directions since height 1,348,396.
- Only legacy P2PKH addresses. SegWit/Taproot are not active on this chain, so bech32 addresses are rejected everywhere.
- Transactions are version 1 and blocks contain no witness commitment.
- assumevalid / nMinimumChainWork are set at block 1,348,395, and -maxtipage is 365 days because blocks can be days apart.
- Fees: 100 sat/kvB minimum. During the transition, 0.12 nodes still require 1000 sat/kvB.
- Old wallet.dat files are converted with migratewallet.
- Known limitations: some inherited tests fail by design (SegWit assumptions), CI is disabled, there are no macOS builds, and mainnet still uses Bitcoin's message start (f9beb4d9). A later "Version B" is supposed to separate the network.
Questions for reviewers:- Does the diff against upstream v32.1 contain only the expected chain-specific changes (chainparams, PoW, address and SegWit handling, fees)?
- Can anyone reproduce the binaries from tag v32.1.0 and confirm the checksums?
- Can anyone confirm the signing-key fingerprint through an independent channel?
- Are there consensus or security concerns, especially given the 51% attack on AU in 2018 and the shared message start with Bitcoin?
Technical issues are best raised directly on GitHub. Otherwise I'm happy to pass questions on to the developers.
Disclosure: I know the developers and am in contact with them, and I hold some AU myself. I'm not a programmer, so I can't vouch for the code. That's exactly why I'm asking here. No price talk, just a technical sanity check.