Join as a Validator
This guide is for operators joining mainnet after genesis: you sync a full node, obtain your Verifiable Presentation
(VP), and promote the node with a create-validator transaction. (The gentx process described in the
networks repository applied only to genesis validators.)
Prerequisites
-
Onboarding & Verifiable Presentation — dchain validators must complete KYB onboarding with Gayadeed on behalf of D-Foundation, after which a VP bound to your validator consensus address (
dchainvalcons1...) is issued. The flow is the same one used on previous testnets — see the historical Theodoric-2 onboarding guide for reference.Without the VP your validator cannot propose or vote on blocks and will be jailed.
Note: D-Foundation is not onboarding new validators at the moment. You can register your interest at info@dfoundation.io and we will reach out when the validator set opens up.
-
DT funds — an operator account funded with DT for self-delegation and transaction fees. Note the active set is capped at 30 validators: once full, joining requires more voting power than the lowest-ranked active validator.
-
A server meeting the hardware requirements, with port
26656reachable at a stable public address.
1. Install the binary
Mainnet runs protocol v1.0.0-rc.4. Pre-built static linux binaries (amd64/arm64) are published on the
D-Foundation GitLab. Downloading requires a GitLab credential: a personal access token (read_api scope) or the deploy
token shared with validators. Pick the file matching your architecture (uname -m):
# 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.4/dchain-v1.0.0-rc.4-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.4/dchain-v1.0.0-rc.4-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, then install:
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.4/checksums-v1.0.0-rc.4.txt"
grep "$(sha256sum dchain | cut -d' ' -f1)" checksums-v1.0.0-rc.4.txt
# the grep must print a matching line — do not proceed otherwise
chmod +x dchain
sudo mv dchain /usr/local/bin
A multi-arch Docker image is available as an alternative:
docker pull repos.gayadeed.it:5006/d-foundation/protocol:v1.0.0-rc.4 (after docker login repos.gayadeed.it:5006 with
a read_registry-scope token). You can also build from source: clone the
protocol repository at tag v1.0.0-rc.4 and run make build.
Verify the version:
dchain version --long
# version: v1.0.0-rc.4
# cosmos_sdk_version: v0.54.3-dchain-v1.0
2. Initialize the node
dchain init <your-moniker> --chain-id dchain-1
dchain config set client chain-id dchain-1
This creates the node home (default ~/.dchain, referred to as DCHAIN_HOME below) including the consensus key
priv_validator_key.json. Back this key up — it is your validator identity.
3. Required node configuration
dchain init writes defaults that are wrong for this network — every validator must change all three settings below
before starting the node.
1. DCHAIN_HOME/config/app.toml — set the EVM chain ID to 433 (the default is 262144):
[evm]
# EVMChainID is the EIP-155 compatible replay protection chain ID. This is separate from the Cosmos chain ID.
evm-chain-id = 433 # Differs from testnet (430)
2. DCHAIN_HOME/config/config.toml — use the app-side mempool, required for EVM tx handling (the default is
"flood"):
[mempool]
type = "app"
3. DCHAIN_HOME/config/app.toml — node-local CheckTx floor; align it with the network's feemarket min_gas_price:
minimum-gas-prices = "12500000000000adt"
4. Get the genesis file
Replace the default genesis written by dchain init with the mainnet genesis:
curl -o $DCHAIN_HOME/config/genesis.json \
https://raw.githubusercontent.com/d-foundation/networks/main/mainnet/genesis.json
5. Configure peers and seeds
Current seed and persistent-peer addresses are maintained in the
networks repository under mainnet/seeds/ and mainnet/peers/ — check
there for the up-to-date list. Set them in DCHAIN_HOME/config/config.toml as comma-separated <node-id>@<host>:<port>
entries:
[p2p]
seeds = "babc3f3f7804933265ec9c40ad94f4da8e9e0017@seed.rhinostake.com:30956,bec5774d784778524b29f704367fdad409bc2685@seed.solva.solutions:26009"
persistent_peers = "18b8b79e8a5f4e270ac13f99724aae1a539b3783@89.168.107.120:26656,9d4684e3c3e5fd67b2de73ea8f8d729971576426@92.5.147.21:26656"
6. Add your Verifiable Presentation
If you do not have the VP, you will not be able to propose / vote on blocks and will be jailed.
The VP must be issued for your consensus address (dchain cometbft show-address). Add it before promoting the node to a
validator, either as a file in the node home at DCHAIN_HOME/config/validator_vp, or via:
dchain vp add <verifiable-presentation>
You can inspect the contents of the presentation by pasting it into the Paradym Debug tool.
7. Start the node and sync
Run the node with Cosmovisor under systemd so future coordinated upgrades are applied automatically — see the Run a Node guide for the Cosmovisor and systemd setup (identical for mainnet). Then wait until the node is fully synced:
dchain status | jq .sync_info.catching_up
# must be false before continuing
8. Create the validator
Create (or recover) an operator key and fund it with DT for self-delegation and fees:
dchain keys add <key-name> # or: dchain keys add <key-name> --recover
Write a validator.json describing your validator. The pubkey is your consensus public key from
dchain cometbft show-validator. The network enforces a minimum commission rate of 0.05. Amounts are in adt (the
example self-delegates 10,000 DT with a minimum self-delegation of 1 DT):
{
"pubkey": { "@type": "/cosmos.crypto.ed25519.PubKey", "key": "<key from dchain cometbft show-validator>" },
"amount": "10000000000000000000000adt",
"moniker": "<your validator name>",
"identity": "<keybase identity, used for logo>",
"website": "<optional website>",
"security": "<optional security contact email>",
"details": "<optional details>",
"commission-rate": "0.05",
"commission-max-rate": "0.1",
"commission-max-change-rate": "0.01",
"min-self-delegation": "1000000000000000000"
}
Submit the transaction. A fee meeting the feemarket minimum gas price is required — pass --gas-prices so it is
computed from the gas limit:
dchain tx staking create-validator validator.json \
--from <key-name> \
--chain-id dchain-1 \
--gas auto --gas-adjustment 1.5 \
--gas-prices 12500000000000adt
9. Verify
# your validator should appear (bonded once you have enough stake for the active set)
dchain query staking validators --node <your-node-rpc>
# check signing status / jailing for your consensus address
dchain query slashing signing-info $(dchain cometbft show-validator)
# follow the logs
journalctl -u dchain -f
If your validator is bonded but immediately jailed, verify the VP is installed (step 6) and issued for the correct consensus address.