feat: add dc-devnet-1 with 200 supernodes and 300 home nodes

[barnabasbusa]

Add dc-devnet-1 for the 500-node decoupled-consensus run: terraform and ansible inventory copied from devnet-0, scaled to 501 DigitalOcean droplets (1 bootnode, 200 prysm-geth supernodes with 200 validators each over 0–40000, and 300 prysm-geth home nodes with 1 validator each over 40000–40300). Genesis matches the agreed spec (ATTESTATION_SUBNET_COUNT=2, AGGREGATE_DUE_BPS_GLOAS=7500, TARGET_AGGREGATORS_PER_COMMITTEE=128), every prysm beacon node runs --goldfish-vote-ledger, and --gossipsub-trace is limited to prysm-geth-1–3 and 201–203 to keep disk usage down. Images are pinned to the sukunrt commits: prysm and the validator to sukunrt-decoupled-casper-6c026c4, ethereum-genesis-generator to sukunrt-decoupled-consensus-9903c93 and dora to sukunrt-decoupled-consensus-08f114e. The genesis seed, terraform state key and ingress usernames are set to dc-devnet-1, ansible.cfg and scripts/run.zsh point at devnet-1, and sops is bumped to 3.13.3 to match the other devnet repos.

[redpandabot]

This PR adds terraform and ansible config for dc-devnet-1 as a copy of devnet-0, scaled to 501 DigitalOcean droplets (1 bootnode, 200 prysm-geth supernodes with 50 validators over 0–10000, 300 home nodes with 2 validators over 10000–10600), with the network seed/state key/ingress usernames, ansible.cfg, and run.zsh updated to devnet-1, plus a sops bump to 3.13.3. I verified the scaling produces 501 unique hostnames with contiguous, non-overlapping validator ranges, and the sops bump has no known advisories; I found no correctness problems in the diff.

---

_{Reviewed 44 changed file(s) @ a486ebe6 — no blocking issues found.
"A child is a deadline with a face."}

[redpandabot]

Summary

dc-devnet-1 is a scaled copy of devnet-0: 501 DigitalOcean droplets (1 bootnode, 200 prysm-geth supernodes at 200 validators each over 0–40000, 300 home nodes at 1 validator each over 40000–40300), retargeted seed/state-key/scripts, sukunrt image pins, commented-out FFG prysm flags, and a new Cloudflare R2 playbook for genesis-config fan-out. The validator arithmetic, host/group naming, image tags (the new 6c026c4 pin does contain --gossipsub-trace, resolving the previous finding) and R2 path-style s3cmd usage all check out. One config inconsistency remains: the genesis delay differs by controller OS.

Issues

• 🟡 ansible/inventories/devnet-1/group_vars/all/all.yaml:54 — genesis delay is 45 minutes on Linux but 60 on Darwin — The commit is described as setting a 60-minute genesis delay, but only the Darwin branch changed (15M→60M); the Linux branch still produces +45 minutes. ethereum_genesis_timestamp is generated from whichever controller OS runs the genesis play, so the resulting MIN_GENESIS_TIME differs by platform, and a Linux-generated genesis launches 15 minutes earlier than the stated spec (two operators on different platforms would even generate different genesis timestamps). Make both branches 60 minutes.

---

_{Reviewed @ 6319eec6
"A child is a deadline with a face."}