dragonx

DragonX/dragonx

Fork 0

Author	SHA1	Message	Date
DanS	4cb5a86056	Rebrand hush3 to DragonX: binaries, defaults, and build system - Rename binaries: hushd/hush-cli/hush-tx → dragonxd/dragonx-cli/dragonx-tx - Default to DRAGONX chain params without -ac_* flags (randomx, blocktime=36, private=1) - Update configure.ac: AC_INIT([DragonX],[1.0.0]) - Update client version string and user-agent to /DragonX:1.0.0/ - Add chainparams.cpp with DRAGONX network parameters - Update build.sh, miner.cpp, pow.cpp for DragonX - Add bootstrap-dragonx.sh utility script - Update .gitignore for release directory	2026-03-03 17:29:06 -06:00
DanS	d6ba1aed4e	Fix RandomX validation exploit: verify nSolution contains valid RandomX hash - Add CheckRandomXSolution() to validate RandomX PoW in nSolution field - Add ASSETCHAINS_RANDOMX_VALIDATION activation height per chain (DRAGONX: 2838976, TUMIN: 1200, others: height 1) - Add CRandomXInput serializer for deterministic RandomX hash input - Fix CheckProofOfWork() to properly reject invalid PoW (was missing SMART_CHAIN_SYMBOL check, allowing bypass) - Call CheckRandomXSolution() in hush_checkPOW and CheckBlockHeader Without this fix, attackers could submit blocks with invalid RandomX hashes that passed validation, as CheckProofOfWork returned early during block loading and the nSolution field was never verified.	2026-03-03 17:28:49 -06:00

Author

SHA1

Message

Date

DanS

4cb5a86056

Rebrand hush3 to DragonX: binaries, defaults, and build system

- Rename binaries: hushd/hush-cli/hush-tx → dragonxd/dragonx-cli/dragonx-tx
- Default to DRAGONX chain params without -ac_* flags (randomx, blocktime=36, private=1)
- Update configure.ac: AC_INIT([DragonX],[1.0.0])
- Update client version string and user-agent to /DragonX:1.0.0/
- Add chainparams.cpp with DRAGONX network parameters
- Update build.sh, miner.cpp, pow.cpp for DragonX
- Add bootstrap-dragonx.sh utility script
- Update .gitignore for release directory

2026-03-03 17:29:06 -06:00

DanS

d6ba1aed4e

Fix RandomX validation exploit: verify nSolution contains valid RandomX hash

- Add CheckRandomXSolution() to validate RandomX PoW in nSolution field
- Add ASSETCHAINS_RANDOMX_VALIDATION activation height per chain
  (DRAGONX: 2838976, TUMIN: 1200, others: height 1)
- Add CRandomXInput serializer for deterministic RandomX hash input
- Fix CheckProofOfWork() to properly reject invalid PoW (was missing
  SMART_CHAIN_SYMBOL check, allowing bypass)
- Call CheckRandomXSolution() in hush_checkPOW and CheckBlockHeader

Without this fix, attackers could submit blocks with invalid RandomX
hashes that passed validation, as CheckProofOfWork returned early
during block loading and the nSolution field was never verified.

2026-03-03 17:28:49 -06:00

Compare commits

2 Commits

93851606d3 ... 4cb5a86056

Diff Content Not Available

Compare commits

2 Commits 93851606d3 ... 4cb5a86056

Diff Content Not Available

2 Commits

93851606d3 ... 4cb5a86056