dogechain-snapshots

Database:

The current database is for latest dogechain bsc client.

Endpoint

(Very Important) The image is only worked on Dogechain DBSC client V2.

Pruned Ancient Database

Only works on DBSC client V2 after Hawaii Fork.

snapshot file: dbsc.2024-09-12T06_46_20-UTC.snapshot.tar.zst

checksum file: dbsc.2024-09-12T06_46_20-UTC.snapshot.tar.zst.sha256sum

• file size: 53GiB.
• sha256sum: b890cf2faf7e37bf3d5b20b92497addf5e3b722b1a20cc32862bf17cb69c2ece.

archive file directory tree structure:

${DBSC_DataDir}         # this is Dogechain DBSC client V2 data directory (`--datadir` parameter)
└── geth                # new dbsc data directory
    ├── chaindata
    └── triecache

Ancient Database

Only works on DBSC client V2 after Hawaii Fork.

snapshot file: dbsc.2023-11-03T06_25_55-UTC.archive.snapshot.tar.zst

checksum file: dbsc.2023-11-03T06_25_55-UTC.archive.snapshot.tar.zst.sha256sum

• file size: 763GiB.
• sha256sum: 3114e7a1105248c425ed4d2ec9e46ebedd1286ddd67f92c1b118bd5d74ca2d49.

archive file directory tree structure:

${DBSC_DataDir}         # this is Dogechain DBSC client V2 data directory (`--datadir` parameter)
└── geth                # new dbsc data directory
    ├── chaindata
    └── triecache

Dogechain V1 Finally Archive Database

Only works on Dogechain client V1 before Hawaii Fork.

snapshot file: dogechain.2023-11-03T13_06_45-UTC.finally.snapshot.tar.zst

checksum file: dogechain.2023-11-03T13_06_45-UTC.finally.snapshot.tar.zst.sha256sum

• file size: 765G.

• sha256sum: 39ed6675b740eceab6ee4223db939f76dfffe98333b9d49d304a9da3c5301104.

${DataDir}
└── dogechain           # this is Dogechain client data directory (`--data-dir` parameter)
    ├── blockchain
    └── trie

Usage

TIPS: archive file is compressed by zstd and archived by tar, so you need to install zstd and tar first.

Step 1: Preparation

• Make sure your hardware meets the suggested requirement.
• A disk with enough free storage space, at least twice the size of the snapshot.
• Install tmux or another terminal multiplexer, if you want to run a terminal background session instead of processing in the background.

Step 2: Download

• Copy the above snapshot URL.

• Download:

  • wget -O dbsc.snapshot.zst "paste_snapshot_URL_here"

• Download takes more than 1 hours,

  • You can run the following command in the background:

  • nohup wget -O dbsc.snapshot.zst "paste_snapshot_URL_here" &

  • Or you can put it in a tmux background terminal session which can be detached and reattached later.

• Check that its sha256sum is consistent with the official one.

  • sha256sum dbsc.snapshot.zst > dbsc.snapshot.zst.sha256sum

  • It will take minutes to finish checksum calculating.

Step 3: Decompression

• Decompression:

  • zstd -d dbsc.snapshot.zst -c | tar -xvf - -C "paste_your_target_dir_here"

• Decompression takes more than 2 hours,

  • You can run the following command in the background:

  • mkdir -p paste_your_target_dir_here

    nohup bash -c 'zstd -d dbsc.snapshot.zst -c | tar -xvf - -C paste_your_target_dir_here' > dogechain-decompression.log 2>&1 &

  • Or you can put it in a tmux background terminal session which can be detached and reattached later.

Step 1-3 in one line:

• You can combine step 1 to 3 in oneline, but take care of the network interruption, otherwise you have to restart from the very beginning.

• wget "paste_snapshot_URL_here" -O - | zstd -d -c - | tar -xvf - -C "paste_your_target_dir_here"

Step 4: Replacing Data

• First, stop the running dbsc client if you have one by kill {pid}, and make sure the client has shut down.
• Consider backing up the original data: mv ${DBSC_DataDir}/geth/chaindata ${DBSC_DataDir}/geth/chaindata_backup; mv ${DBSC_DataDir}/geth/triecache ${DBSC_DataDir}/geth/triecache_backup.
• Replace the data: mv server/data-seed/geth/chaindata ${DBSC_DataDir}/geth/chaindata; mv server/data-seed/geth/triecache ${DBSC_DataDir}/geth/triecache.
• Start the dbsc client again and check the logs.