Valoper's details:
dvg-hel-01
dvg-hel-01 — independent node operator, private multi-chain farm on own hardware.
- Name: dvg-hel-01.
- Networks / AuM: currently Logos (5 nodes), Cysic verifier, Blockcast; previously Nexus (7 provers). NOT a commercial staking provider: no assets under management, no third-party delegations. Self-funded, run for research and testnet participation.
- Presence: Discord fumo696 (ID 402239749009571852).
- Contact: [email protected]; Discord fumo696.
- Why gno.land: Gno is a deterministic Go VM with on-chain, readable source — contracts you can actually audit. Running a validator is the practical way to learn the stack from the inside.
- Contributions: during setup I found four gaps in VALIDATOR.md and will file them upstream: (a) GNOROOT must be set or gnoland panics before flag parsing, so even --help fails; (b) no prebuilt gnoland/gnokey on the chain/pearl release page — the gno_* assets are the developer tool, so the node must be built from source (Go 1.25.9); (c) log-level is a command flag, not a config.toml field, and defaults to debug, which writes tens of MB per minute during sync; (d) "gnoland secrets get validator_key --data-dir" panics with reflect.Value.Interface on zero Value, while the same command works from the node directory without the flag. Ongoing: keep the node at tip, monitor with Prometheus/Grafana tracking inbound peers separately (behind NAT a node looks healthy while unreachable), and report further issues.
Infra: dedicated server, Helsinki FI, static IPv4, inbound 26656/tcp, 4 vCPU / 8 GB / 100 GB NVMe.
- Operator Address: g1epqf9wqa4uvh5a42pa56vd66hsx933jfygwl8v
- Signing Address: g1ywfh4rut5tpq2stlsyt4mxyk34407mxsjptncv
- Signing PubKey: gpub1pggj7ard9eg82cjtv4u52epjx56nzwgjyg9zpl2zkfzm2p8s9t3apqlfgy36jvvyqyd0ys9uc9fsslyher97puvk92h95y
- Server Type: data-center
