You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BUG A (Linux, all 5 coins): every v0.2.3 Linux tarball was dead-on-arrival.
The Linux packaging step hardcoded libsecp256k1.so.2, but the runners
libsecp256k1-dev provides .so.1, so the find matched nothing and the binary
only dynamic non-glibc dependency (libsecp256k1.so.1) was never bundled;
lib/ carried only the statically-redundant leveldb/snappy. Replace the
hardcoded SONAME list with an ldd-resolved copy of the real runtime closure
(SONAME-agnostic). macOS/Windows already bundle secp256k1 correctly.
BUG B (all 15 packages): every coin tarball shipped the Litecoin config
(LTC header, ports 9326/9327, LTC/DOGE checkpoints, embedded_ltc), so a
DASH pool logged LTC and bound LTC ports. Add per-coin config/<coin>/
mainnet+testnet files with coin-correct headers and authoritative sharechain
ports (btc 9333, ltc 9326/9327, dgb 5024/5025, dash 8999/7903, bch 9349);
release.yml selects config/${COIN}/ on all three platforms. DASH config
documents the external dashd-RPC fallback (embedded SPV unwired per #738).
Guards: release.yml packaging asserts each Linux package bundles
libsecp256k1 and its config header names the coin (fail-fast tripwires);
start.sh/start.bat refuse to launch a binary against a mismatched-coin
config.
Co-authored-by: frstrtr <frstrtr@users.noreply.github.com>
0 commit comments