Files

DanS 46693a355a docs: rebrand documentation, packaging, and helper scripts to DragonX

The docs/packaging were largely un-rebranded Hush3 content, with several
docs stating facts that are wrong for DragonX. This rewrites them against
the verified DragonX source state.

Corrections (not just branding):
- PoW: RandomX (CPU), not Equihash/ASIC — README, overview.md, randomx.md
- Privacy: private from genesis (ac_private=1, Sapling@height1), not "as of
  block 340000" — overview.md, payment-api.md
- Removed the false "coinbase must be shielded" consensus claim
  (shield-coinbase.md, payment-api.md); coinbase is directly spendable
- Fixed default fee 0.0001 (was 0.0010000, 10x); stratum port 22769 (was 19031)
- datadir ~/.hush/DRAGONX, DRAGONX.conf, dragonxd/dragonx-cli/dragonx-tx,
  git.dragonx.is throughout; branch model dev->dragonx
- Softened the inherited dPoW reorg claim (no live DragonX notary infra)

Packaging: fix build-debian-package.sh + gen-manpages.sh to use the dragonx
binaries/manpages; rename bash-completions to dragonx*; drop hush-arrakis-chain
from the package. Keep /usr/share/hush (hardcoded in the binary for params).

Also: README links/logo, ObsidianDragon + SilentDragonXAndroid wallets,
networking/init/dev-process/contrib/util rebrand, and leftover helper scripts.
Delete legacy duplicates (hushd.* init/service, HUSH3.conf examples,
OLD_WALLETS.md, hsc.md) and rename hush-uri.bat -> dragonx-uri.bat.

Out of scope (noted, not changed): historical changelog/copyright, the Hush
mainnet airdrop snapshot, seed data files, depends/ source mirrors, and the
in-code strCurrencyUnits="HUSH".

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-21 13:59:06 -05:00

895 B

Raw Blame History

Compiling/running automated tests

Automated tests will be automatically compiled if dependencies were met in configure and tests weren't explicitly disabled.

There are two scripts for running tests:

qa/hush/full_test_suite.py, to run the main test suite
qa/pull-tester/rpc-tests.sh, to run the RPC tests.

The main test suite uses two different testing frameworks. Tests using the Boost framework are under src/test/; tests using the Google Test/Google Mock framework are under src/gtest/ and src/wallet/gtest/. The latter framework is preferred for new DragonX unit tests.

RPC tests are implemented in Python under the qa/rpc-tests/ directory.

Example

To run a single RPC test, pass its name to the runner. For example, the inherited dpowconfs test (a regtest-only test carried over from the upstream codebase):

./qa/pull-tester/rpc-tests.sh dpowconfs

895 B Raw Blame History

Compiling/running automated tests

Example

895 B

Raw Blame History