Verifiers

Verifiers secure publisher quality by checking homepage badge ownership against on-chain records. Good verifier performance improves registry trust and can qualify for rewards.

Step 1 — Prepare wallet + stake

Use a dedicated verifier account. Keep enough balance for bonding and tx fees.

# Bond (example amount)
./content-grid-d verifier bond 1000000 \
  --denom ucongrid \
  --from <local-key-name> \
  --chain-id congrid-main-1 \
  --node tcp://127.0.0.1:26657 \
  --gas-prices 0.001ucongrid \
  -y

# Optional unbond later
./content-grid-d verifier unbond 1000000 \
  --denom ucongrid \
  --from <local-key-name> \
  --chain-id congrid-main-1 \
  --node tcp://127.0.0.1:26657 \
  --gas-prices 0.001ucongrid \
  -y

Step 2 — Run verifier daemon

Use offchain/verifierd from this repository for chain-driven assignments. Run it continuously and monitor logs so you can submit checks inside each assignment window.

# Example status checks
./content-grid-d verifier assignments <verifier-address> \
  --node tcp://127.0.0.1:26657 \
  --grpc-addr 127.0.0.1:9090 \
  --grpc-insecure -o json

./content-grid-d query registry publisher --domain <domain> \
  --node tcp://127.0.0.1:26657 \
  --grpc-addr 127.0.0.1:9090 \
  --grpc-insecure -o json

Step 3 — Keep your verifier reliable

• Use stable DNS/network; avoid frequent IP rotations.
• Track failed checks and homepage fetch latency.
• Alert on process exit, RPC disconnect, and backlog growth.
• Keep software updated with protocol changes.