Files
DanS c05134e77e Compliant rebrand: legal compliance, code audit, and documentation (Phases 0-3)
Phase 0 - Legal Compliance:
- COPYING: Add DragonX copyright, preserve all upstream attributions
- AUTHORS: Add DragonX developers section
- LICENSE: Restore standard FSF GPLv3 text (fix GNU→GENERAL error)
- Add DragonX copyright headers to all 21 modified source files
- contrib/debian/copyright: Add DragonX attribution
- README.md: Add GPLv3 Section 5(a) attribution section

Phase 1 - init.cpp Cleanup:
- PID file: hushd.pid → dragonxd.pid
- Shutdown thread: hush-shutoff → dragonx-shutoff
- Debug message: stopping HUSH → stopping DragonX

Phase 2 - HUSH3/ishush3 Code Audit:
- Rename ishush3 → isdragonx across ~15 source files
- Update "HUSH3" chain-identity checks to "DRAGONX" in consensus,
  difficulty, notarization, devtax, and RPC code
- Intentionally preserve cross-chain "HUSH3" refs (gateway, notary dest)
- Build verified: all three binaries compile cleanly

Phase 3 - Documentation:
- README.md: Full rewrite with DragonX chain params, build instructions
- Man pages: Create dragonxd.1, dragonx-cli.1, dragonx-tx.1 (v1.0.0)
- Doc files: Add beefy-DRAGONX.conf, dragonxd-systemd.md, dragonxd.service
- Init scripts: Create dragonxd.{conf,init,openrc,openrcconf,service}
- Debian packaging: Update control, changelog, install, manpages, examples
- Update doc/init.md and contrib/init/README.md
2026-03-03 19:01:24 -06:00
..
2024-02-27 23:59:59 +01:00
2024-02-27 23:59:59 +01:00
2024-02-27 23:59:59 +01:00
2026-02-28 12:12:45 -05:00
2024-02-27 23:59:59 +01:00
2022-09-18 14:50:57 -04:00
2024-02-27 23:59:59 +01:00
2026-03-02 11:51:48 -05:00
2024-03-31 23:17:16 +02:00
2024-02-27 23:59:59 +01:00
2024-02-27 23:59:59 +01:00
2024-02-27 23:59:59 +01:00
2024-03-31 23:17:16 +02:00
2024-02-27 23:59:59 +01:00
2024-02-27 23:59:59 +01:00

Hush utilities

Scripts in this directory are used by Hush developers in the process of development or in releasing a new version of Hush.

Utilities in this directory:

build.sh

Compile Hush full node code.

build-arm.sh

Compile Hush full node code for ARM architecture. has not worked for some time

build-arm-xcompile.sh

Cross-Compile Hush full node code for ARM architecture on an x86 build server.

build-debian-package.sh

Builds an x86 Debain package for Hush.

build-debian-package-ARM.sh

Builds an ARM Debain package for Hush.

build-mac.sh

Compile Hush full node code for mac. NOTE: This is likely broken.

build-win.sh

Compile Hush full node code for windows

checkpoints.pl

Generate checkpoint data for chainparams.cpp . This automates the creation of block heights and block hashes by asking hushd for the data and then generating the C++ code needed to embed them in the Hush source code.

docker-entrypoint.sh

Script to use Hush with Docker.

docker-hush-cli.sh

Convenience script to run hush-cli in a running Docker container.

replace.pl

Replace a string in a set of files by another string. Very useful for updating a variable name or value across many files, or updating copyrights.

security-check.py

Perform basic ELF security checks on a series of executables.

symbol-check.py

A script to check that the (Linux) executables produced by gitian only contain allowed gcc, glibc and libstdc++ version symbols. This makes sure they are still compatible with the minimum supported Linux distribution versions.

Example usage after a gitian build:

find ../gitian-builder/build -type f -executable | xargs python util/symbol-check.py 

If only supported symbols are used the return value will be 0 and the output will be empty.

If there are 'unsupported' symbols, the return value will be 1 a list like this will be printed:

.../64/test_bitcoin: symbol memcpy from unsupported version GLIBC_2.14
.../64/test_bitcoin: symbol __fdelt_chk from unsupported version GLIBC_2.15
.../64/test_bitcoin: symbol std::out_of_range::~out_of_range() from unsupported version GLIBCXX_3.4.15
.../64/test_bitcoin: symbol _ZNSt8__detail15_List_nod from unsupported version GLIBCXX_3.4.15

gen-manpages.sh

A small script to automatically create manpages in ../../doc/man by running the release binaries with the -help option. This requires help2man which can be found at: https://www.gnu.org/software/help2man/

When you type "make manpages" it runs this script.

gen-linux-binary-release.sh

Generate linux release binary.