Skip to content

c2pool v0.2.12.5

Choose a tag to compare

View all tags
@github-actions github-actions released this 13 Nov 23:59
· 20 commits to master since this release
v0.2.12.5
This tag was signed with the committer’s verified signature.
frstrtr frstrtr
SSH Key Fingerprint: jWjVUY1hYTHj+YZY/r3m5Wm28fL9e6jS4nCXQYSRo2s
Verified
Learn about vigilant mode.
f04f753
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

c2pool v0.2.12.5

DASH fix on top of v0.2.12.4. Every c2pool-dash node should upgrade before superblock 2,575,480 (around November 20; superblock voting opens at block 2,573,818, around November 17). LTC, BTC, DGB, BCH and BIP-110 nodes are unchanged from v0.2.12.4.

DASH: superblock trigger votes re-synced right before the superblock

Dash Core 24.0.1 changes when masternodes vote against superblock triggers. A masternode now waits until a trigger for its own candidate exists, and casts its NO-FUNDING votes on other triggers as late as three blocks before the superblock. Earlier versions voted at once.

c2pool re-synced trigger votes only at fixed points well before the superblock. Late NO votes could therefore be missed, and the node could build the superblock from a stale tally. That gives the wrong payees and a block the network rejects.

The node now re-syncs trigger votes again two blocks before the superblock, so the late votes are counted.

Also: --dash-v24-activation-height now rejects values that cannot be a v24 activation height.

Dash Core 24.0.1

v24 still activates from the chain. Its EHF signal, signed by an LLMQ_400_85 quorum, has not been mined on mainnet yet, so activation comes later than the earliest date given for Dash Core 24.0.0. c2pool follows the chain; nothing needs configuring.

Everything else

Everything in v0.2.12.4 applies, including the LTC restart fix and universal macOS packages. See the v0.2.12.4 notes.

Known issue

  • --solo and --custodial remain disabled.

  • Linux: run the node with the package's lib/ folder. The Linux binaries load libraries shipped in the package's lib/ folder (libsecp256k1, and for DASH also libgmp and libdash_scriptcheck). start.sh sets this up. If you start the binary directly, from your own script or a systemd unit, it can stop at once with error while loading shared libraries: libsecp256k1.so.6: cannot open shared object file. Which libsecp256k1 version a package needs can change between releases: the LTC, BCH and BIP-110 packages of this release need libsecp256k1.so.6, which most systems do not have. The DASH package always needs lib/. To fix it, unpack the whole package and run the node through start.sh, or point the loader at lib/:

    cd c2pool-<coin>-<version>-linux-x86_64
LD_LIBRARY_PATH="$PWD/lib" ./c2pool-<coin> <your options>

    For a systemd unit, add Environment=LD_LIBRARY_PATH=/path/to/c2pool-<coin>-<version>-linux-x86_64/lib. If you upgrade by copying only the binary, copy lib/ too. A later release finds lib/ without this step.

Verify the download

SHA256SUMS is signed with key 99556F8DE6AD66057A1A10EC50AB1379285EFE76:

gpg --verify SHA256SUMS.asc SHA256SUMS
sha256sum -c --ignore-missing SHA256SUMS
Assets 34
Loading