18 August 2026
Replymessage unavailable
Built us a custom block explorer that mimics Etherscan. I always liked their UI/UX.
Replymessage unavailable
I think this incredibly good that we can read this data within the CG infrastructure
Replymessage unavailable
That new version of 21 Wild is going to be the first game to hit the new chain
Adam "WILL NOT DM FIRST" BarlamThat new version of 21 Wild is going to be the first game to hit the new chain
We should start playing by next week right?
Replymessage unavailable
Yeah goal is to get the new chain on prod this week, and start integration of legacy games next week
Replymessage unavailable
you guys will be able to unstake and migrate to the new chain, and setup new validator nodes. I need to get a dockerized version script ready too so that setup is a snap.
Replymessage unavailable
The plan is you can compile from src if you're a nerd and want to, or just run the dockerized version from a script (easiest).
id 6631803124text not yet in the index
A 4 vCPU / 8 GB RAM / 200 GB NVMe box comfortably runs one full validator. NVMe is very important. With a 3s block time and lots of random reads/writes you need very fast storage with high IOPs. HDD and even non-NVME SSDs may cause issues and lag.
Replymessage unavailable
If you want to be future proof, you could get a 8 vCPU / 16 GB / 500 GB NVMe box.
Adam "WILL NOT DM FIRST" BarlamВидео
Looks really beautiful, relaxing and fun! One thing tho, is it me or did the older one seem “faster”?
Adam "WILL NOT DM FIRST" BarlamBuilt us a custom block explorer that mimics Etherscan. I always liked their UI/UX.
The most familiar interface is the better way to go
Adam "WILL NOT DM FIRST" BarlamIf you want to be future proof, you could get a 8 vCPU / 16 GB / 500 GB NVMe box.
Thanks Adam! Stoked to get a node set up.. few more bits of info that would be helpful are:
Internet bandwidth requirement,
Expected monthly data transfer,
Whether validator CPU must be dedicated,
Supported CPU architecture (x86-64 vs ARM),
Supported Linux distribution/version,
Required network ports,
Whether a static public IP is required,
Expected database growth rate,
Recommended SSD endurance,
Backup requirements,
Validator key-storage procedure,
Minimum uptime,
Whether downtime or double-signing can lead to slashing.
id 6631803124Thanks Adam! Stoked to get a node set up.. few more bits of info that would be helpful are:
Internet bandwidth requirement,
Expected monthly data transfer,
Whether validator CPU must be dedicated,
Supported CPU architecture (x86-64 vs ARM),
Supported Linux distribution/version,
Required network
🖥 Chain Games Supernet — Validator Node Requirements
Hardware
• Recommended: 4 cores / 8–16 GB RAM / 250 GB NVMe SSD
• Future Proof: 8 cores / 16–32 GB RAM / 500 GB+ NVMe
⚠️ NVMe SSD is not negotiable. The database is random-I/O heavy and writes every block. SATA SSD is borderline; a spinning disk or a low-IOPS network volume will not keep up with the 3-second block time.
CPU
• Architecture: x86-64 (tested/supported). ARM64 is unverified — should build, but nothing tests it. Use x86-64.
• Validators need dedicated vCPU — no oversubscription/shared “burstable” instances. Fast single-thread speed matters more than core count. A non-validating full node can run on shared CPU.
Operating System
• Ubuntu LTS (22.04 / 24.04) is the tested distro. Any modern Linux should work, or use the container image. Not for Windows/macOS in production.
Storage details
• Growth: ~3.3 GB/month on an idle chain (measured floor). Real growth depends on transaction volume and can be 10–100× that. State only grows — it’s never pruned.
• SSD endurance: use enterprise (0.3–1 DWPD) or high-TBW NVMe. Avoid cheap DRAM-less QLC drives — they throttle and wear out under constant writes.
Networking
• Bandwidth: ~1–5 Mbps sustained symmetric (estimate). Public RPC adds more.
• Monthly transfer: roughly 0.5–2 TB/month for a validator.
• Ports:
– 9000/tcp — P2P (must be reachable from outside)
– 8545/tcp — JSON-RPC (keep on localhost or behind an authenticated proxy — never open it publicly)
– Metrics/ops HTTP (private network only)
• Static public IP:
required for validators. Peers connect to you by IP, so you need a stable reachable address. NAT/dynamic IP is only OK for a non-validating node.
• Keep latency to other validators low — the 3s block includes a full voting round-trip.
Uptime
• The network tolerates up to ⌊(N−1)/3⌋ validators offline at once without stopping.
• No enforced minimum, but target 99%+ — downtime = missed blocks and missed rewards.
🔐 Slashing — read this
bluewhiteorangeLooks really beautiful, relaxing and fun! One thing tho, is it me or did the older one seem “faster”?
I always found desktop was slower than mobile
19 August 2026
Adam "WILL NOT DM FIRST" Barlam🖥 Chain Games Supernet — Validator Node Requirements
Hardware
• Recommended: 4 cores / 8–16 GB RAM / 250 GB NVMe SSD
• Future Proof: 8 cores / 16–32 GB RAM / 500 GB+ NVMe
⚠️ NVMe SSD is not negotiable. The database is random-I/O heavy and writes every block. SATA SSD is borderline; a spinning di
Thanks Adam! This will be a fun learning experience.. Let the (Chain) Games begin! 👽
Replymessage unavailable
I actually run NVMe RAID 0 for any high performance blockchain nodes.
Data redundancy doesn't matter since you can always sync from a node online.
So you want the fastest disk possible.