DanS
46693a355a
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>
53 lines
2.2 KiB
Markdown
53 lines
2.2 KiB
Markdown
# How To Fix Various Problems
|
|
|
|
This document will document how to recover and fix various issues that users may run into.
|
|
|
|
## Database corruption
|
|
|
|
The problem: You see an error like
|
|
|
|
```
|
|
EXCEPTION: 15dbwrapper_error
|
|
Database corrupted
|
|
```
|
|
|
|
This means your blockchain data on disk is corrupted. This is not the same as wallet corruption.
|
|
The fix to this is to do a fresh sync using the same wallet.dat file. You need to find
|
|
where this data lives on your computer and then move some files around, then restart the wallet.
|
|
|
|
### On Linux
|
|
|
|
If you are on Linux, your wallet lives at `~/.hush/DRAGONX/wallet.dat`.
|
|
|
|
What we will do is backup your entire `DRAGONX` directory, including the blockchain data and wallet,
|
|
then copy the wallet from there into a new directory. This is a non-destructive process that creates
|
|
a new backup of your wallet.
|
|
|
|
```
|
|
# Make sure your node is not running before doing any of this!
|
|
# Doing this while your node is running could corrupt your wallet.dat
|
|
cd ~/.hush
|
|
mv DRAGONX DRAGONX-backup # backup all data
|
|
mkdir DRAGONX # make a new dir
|
|
cp DRAGONX-backup/wallet.dat DRAGONX/wallet.dat # copy old wallet to new dir
|
|
```
|
|
|
|
At this point restart your node (`dragonxd`) and it will perform a fresh sync using your
|
|
wallet. This will likely take at least a few hours or much longer depending on your
|
|
internet connection.
|
|
|
|
### On Windows
|
|
|
|
Basically you want to find where your DragonX wallet is, move the directory that contains
|
|
that wallet.dat file to a new name, then create that same directory and then copy wallet.dat into it.
|
|
Different versions of Windows store things in different locations. Note the app-data folder is
|
|
named `Hush` (inherited) with a `DRAGONX` subdirectory.
|
|
|
|
For example your wallet might be in `C:\Users\Admin\AppData\Roaming\Hush\DRAGONX\wallet.dat` .
|
|
That means you need to
|
|
|
|
* Rename the directory `C:\Users\Admin\AppData\Roaming\Hush\DRAGONX` to something like `C:\Users\Admin\AppData\Roaming\Hush\DRAGONX-backup`
|
|
* Create a new directory called `C:\Users\Admin\AppData\Roaming\Hush\DRAGONX`
|
|
* Copy the file `C:\Users\Admin\AppData\Roaming\Hush\DRAGONX-backup\wallet.dat` to `C:\Users\Admin\AppData\Roaming\Hush\DRAGONX`
|
|
* Now start your DragonX node again
|