Upgrade Details
Overview
This upgrade to version v1.0.0-rc.3 removes the x/group module. Group policy accounts have no private key, so state
that depended on them is moved to plain accounts:
-
Group store: the
groupstore is deleted. -
Policy balances: the full balance of each group policy is sent to its replacement account:
Policy From To oversight-committee dchain1afk9zr2hn2jsac63h4hm60vl9z3e5u69gndzf7c99cqge3vzwjzsm8h65cdchain1uf9hqy5vqpwaywe4sudkns3h7w9vnryaexfq3mdf-treasury dchain1dlszg2sst9r69my4f84l3mj66zxcf3umcgujys30t84srg95dgvsf6sqvfdchain1drcphm0yljqxa7hhuxa85d6yl43kgvmx7e8aweecosystem-fee dchain1c799jddmlz7segvg6jrw6w2k6svwafganjdznard3tc74n7td7rqlu29z6dchain1zf2653q7jryx2cymk50xsp8vvkmfpmfaqr7tx2 -
Fee grants: every fee allowance granted by one of these policies is revoked.
-
Oversight Committee: the dgov Oversight Committee address is set to
dchain1uf9hqy5vqpwaywe4sudkns3h7w9vnryaexfq3m. Its decision process (multisig, etc.) is off-chain.
The upgrade will be at testnet Block TBD (Expected around - TBD UTC).
Upgrade Methods
You can upgrade using one of two methods:
- Cosmovisor (recommended): Automated upgrade handling
- Manual Upgrade: Manual binary replacement
Preparation
Pre-built dchain v1.0.0-rc.3 binaries are published on the D-Foundation GitLab — no source checkout or build is
required. Static linux binaries are available for amd64 (x86_64) and arm64 (aarch64); check your server architecture
with uname -m if unsure.
Download the Binary
Downloading requires a GitLab credential: your personal access token (read_api scope) or the deploy token shared with
validators. Pick the file matching your architecture:
# amd64 (uname -m: x86_64)
curl --fail --header "PRIVATE-TOKEN: <your-token>" -o dchain \
"https://repos.gayadeed.it/api/v4/projects/d-foundation%2Fprotocol/packages/generic/dchain/v1.0.0-rc.3/dchain-v1.0.0-rc.3-linux-amd64"
# arm64 (uname -m: aarch64)
curl --fail --header "PRIVATE-TOKEN: <your-token>" -o dchain \
"https://repos.gayadeed.it/api/v4/projects/d-foundation%2Fprotocol/packages/generic/dchain/v1.0.0-rc.3/dchain-v1.0.0-rc.3-linux-arm64"
If you use a deploy token, replace the header with --header "DEPLOY-TOKEN: <token>". The files are also available from
the release page and the
package registry in the browser.
Verify the Checksum
curl --fail --header "PRIVATE-TOKEN: <your-token>" -O \
"https://repos.gayadeed.it/api/v4/projects/d-foundation%2Fprotocol/packages/generic/dchain/v1.0.0-rc.3/checksums-v1.0.0-rc.3.txt"
grep "$(sha256sum dchain | cut -d' ' -f1)" checksums-v1.0.0-rc.3.txt
The grep must print a matching line (the published filename differs from your local dchain name, so a plain
sha256sum -c will not match). Do not proceed with a binary whose checksum does not appear in the file.
Make the binary executable:
chmod +x dchain
Docker Image
If you run your node in Docker, a multi-arch image (amd64/arm64) is available instead of the raw binary:
docker login repos.gayadeed.it:5006 # GitLab username + token (read_registry scope)
docker pull repos.gayadeed.it:5006/d-foundation/protocol:v1.0.0-rc.3
The binaries and the image are built from the same source and flags (static, ledger-enabled).
Option A: Cosmovisor Upgrade (Recommended)
Create Upgrade Directory
Create the directory structure for the upgrade. The directory name must match the plan name v1.0.0-rc.3:
mkdir -p <path-to-dchain-home>/cosmovisor/upgrades/v1.0.0-rc.3/bin
Replace <path-to-dchain-home> with your cosmovisor data directory path.
Copy Binary
Copy the provided binary to the upgrade directory:
cp dchain <path-to-dchain-home>/cosmovisor/upgrades/v1.0.0-rc.3/bin/
What Happens During Upgrade
When the network halts with CONSENSUS FAILURE!!! for the upgrade:
- Cosmovisor detects the upgrade height
- Automatically replaces the binary symlink
- Restarts
dchainwith the new binary
Option B: Manual Upgrade
If not using cosmovisor, follow these steps when the network halts:
- Stop the running
dchainprocess - Replace the old binary with the new
v1.0.0-rc.3binary - Restart
dchain
Note: You must monitor for the CONSENSUS FAILURE!!! message and perform these steps promptly to avoid prolonged
downtime.