svax974 .fuel Anomage ๐Ÿง™โ€โ™‚๏ธ,๐Ÿง™โ€โ™‚๏ธ (@svax974) 's Twitter Profile
svax974 .fuel Anomage ๐Ÿง™โ€โ™‚๏ธ,๐Ÿง™โ€โ™‚๏ธ

@svax974

Sharing web3dev notes
Crypto nerd, gamer, guitarist, 20+ years FS dev, bank executiv, IT project manager, web3 dev gnoma Anoma (๐Ÿง™โ€โ™‚๏ธ,๐Ÿง™โ€โ™‚๏ธ)

ID: 14746516

calendar_today12-05-2008 17:04:32

7,7K Tweet

141 Takipรงi

934 Takip Edilen

svax974 .fuel Anomage ๐Ÿง™โ€โ™‚๏ธ,๐Ÿง™โ€โ™‚๏ธ (@svax974) 's Twitter Profile Photo

Sunday is perfect for infra hygiene: โ€ข test restoring a backup to a fresh node โ€ข rotate a key the safe way โ€ข run a fake incident drill with your team You donโ€™t want the first time you restore a node to be during a real outage. ๐Ÿงช #SRE #Runbooks #Web3Infra

Sunday is perfect for infra hygiene:
โ€ข test restoring a backup to a fresh node
โ€ข rotate a key the safe way
โ€ข run a fake incident drill with your team

You donโ€™t want the first time you restore a node to be during a real outage. ๐Ÿงช
#SRE #Runbooks #Web3Infra
svax974 .fuel Anomage ๐Ÿง™โ€โ™‚๏ธ,๐Ÿง™โ€โ™‚๏ธ (@svax974) 's Twitter Profile Photo

If your runbooks live only in someoneโ€™s head, they donโ€™t exist. Write them where people actually work: โ€ข repo README / docs โ€ข internal wiki โ€ข chat pinned posts for quick access At 3am, nobody has time for treasure hunts. ๐Ÿ“ #Runbooks #Ops #Infra

If your runbooks live only in someoneโ€™s head, they donโ€™t exist.

Write them where people actually work:
โ€ข repo README / docs
โ€ข internal wiki
โ€ข chat pinned posts for quick access

At 3am, nobody has time for treasure hunts. ๐Ÿ“
#Runbooks #Ops #Infra
svax974 .fuel Anomage ๐Ÿง™โ€โ™‚๏ธ,๐Ÿง™โ€โ™‚๏ธ (@svax974) 's Twitter Profile Photo

Whatโ€™s the thing you wish node infra providers did better today? โ€ข transparency? โ€ข pricing? โ€ข performance? โ€ข human support? Reply and Iโ€™ll turn the best answers into future threads. Letโ€™s raise the bar for node running together. ๐Ÿค #Web3 #NodeRunner #InfraTalk

Whatโ€™s the thing you wish node infra providers did better today?
โ€ข transparency?
โ€ข pricing?
โ€ข performance?
โ€ข human support?

Reply and Iโ€™ll turn the best answers into future threads.
Letโ€™s raise the bar for node running together. ๐Ÿค
#Web3 #NodeRunner #InfraTalk
svax974 .fuel Anomage ๐Ÿง™โ€โ™‚๏ธ,๐Ÿง™โ€โ™‚๏ธ (@svax974) 's Twitter Profile Photo

New to node running? Avoid this trap: Spinning up 5 nodes before youโ€™ve truly mastered 1. Get one rock-solid: โ€ข no unknown warnings in logs โ€ข reproducible install โ€ข clean monitoring Then clone the pattern. Scale stability, not guesswork. ๐Ÿงฑ #Web3 #NodeOps #DevOps

New to node running? Avoid this trap:
Spinning up 5 nodes before youโ€™ve truly mastered 1.
Get one rock-solid:
โ€ข no unknown warnings in logs
โ€ข reproducible install
โ€ข clean monitoring
Then clone the pattern. Scale stability, not guesswork. ๐Ÿงฑ
#Web3 #NodeOps #DevOps
svax974 .fuel Anomage ๐Ÿง™โ€โ™‚๏ธ,๐Ÿง™โ€โ™‚๏ธ (@svax974) 's Twitter Profile Photo

If youโ€™re running testnet + mainnet on the same box: โ€ข isolate data directories โ€ข cap resources per client โ€ข make sure testnet canโ€™t starve mainnet Testnets are where you experiment, not where mainnet pays the price. โš–๏ธ #Testnet #Mainnet #Infra

If youโ€™re running testnet + mainnet on the same box:
โ€ข isolate data directories
โ€ข cap resources per client
โ€ข make sure testnet canโ€™t starve mainnet
Testnets are where you experiment, not where mainnet pays the price. โš–๏ธ
#Testnet #Mainnet #Infra
svax974 .fuel Anomage ๐Ÿง™โ€โ™‚๏ธ,๐Ÿง™โ€โ™‚๏ธ (@svax974) 's Twitter Profile Photo

Simple security win: Move your RPC behind an allowlist of IPs (or at least authenticated proxies) before you go big on marketing. โ€œFree public RPCโ€ is greatโ€”until your first brute-force or DDoS. ๐Ÿ” #Security #RPC #Web3Infra

Simple security win:
Move your RPC behind an allowlist of IPs (or at least authenticated proxies) before you go big on marketing.
โ€œFree public RPCโ€ is greatโ€”until your first brute-force or DDoS. ๐Ÿ”
#Security #RPC #Web3Infra
svax974 .fuel Anomage ๐Ÿง™โ€โ™‚๏ธ,๐Ÿง™โ€โ™‚๏ธ (@svax974) 's Twitter Profile Photo

Log hygiene for node runners: โ€ข include node_id in every line โ€ข include request_id for RPC logs โ€ข log remote IP for rate-limited requests One extra field in logs can save hours of โ€œwhat actually happened?โ€ later. ๐Ÿ“œ #Logs #SRE #Web3Infra

Log hygiene for node runners:
โ€ข include node_id in every line
โ€ข include request_id for RPC logs
โ€ข log remote IP for rate-limited requests
One extra field in logs can save hours of โ€œwhat actually happened?โ€ later. ๐Ÿ“œ
#Logs #SRE #Web3Infra
svax974 .fuel Anomage ๐Ÿง™โ€โ™‚๏ธ,๐Ÿง™โ€โ™‚๏ธ (@svax974) 's Twitter Profile Photo

Alert fatigue kills real incidents. For node infra, keep alerts minimal: โ€ข node unreachable โ€ข sync gap too high โ€ข RPC error rate spiking Everything else can be a dashboard, not a page at 3am. ๐Ÿ“Ÿ #Oncall #SRE

Alert fatigue kills real incidents.
For node infra, keep alerts minimal:
โ€ข node unreachable
โ€ข sync gap too high
โ€ข RPC error rate spiking
Everything else can be a dashboard, not a page at 3am. ๐Ÿ“Ÿ
#Oncall #SRE
svax974 .fuel Anomage ๐Ÿง™โ€โ™‚๏ธ,๐Ÿง™โ€โ™‚๏ธ (@svax974) 's Twitter Profile Photo

Post-mortem anti-pattern: โ€œRoot cause: network glitchโ€. If thatโ€™s your conclusion, you didnโ€™t go deep enough. For infra: โ€ข prove impact โ€ข document detection โ€ข add 1โ€“2 concrete preventions Otherwise, itโ€™s just storytelling. ๐Ÿงฉ #PostMortem #SRE

Post-mortem anti-pattern:
โ€œRoot cause: network glitchโ€.

If thatโ€™s your conclusion, you didnโ€™t go deep enough.
For infra:
โ€ข prove impact
โ€ข document detection
โ€ข add 1โ€“2 concrete preventions
Otherwise, itโ€™s just storytelling. ๐Ÿงฉ
#PostMortem #SRE
svax974 .fuel Anomage ๐Ÿง™โ€โ™‚๏ธ,๐Ÿง™โ€โ™‚๏ธ (@svax974) 's Twitter Profile Photo

Tiny Dockerfile tweak: Use a non-root user to run the node process. Why? โ€ข less blast radius if compromised โ€ข fewer โ€œoops, the process owned the whole filesystemโ€ moments Security is often a one-line change. ๐Ÿ” #Docker #Security

Tiny Dockerfile tweak:
Use a non-root user to run the node process.
Why?
โ€ข less blast radius if compromised
โ€ข fewer โ€œoops, the process owned the whole filesystemโ€ moments
Security is often a one-line change. ๐Ÿ”
#Docker #Security
svax974 .fuel Anomage ๐Ÿง™โ€โ™‚๏ธ,๐Ÿง™โ€โ™‚๏ธ (@svax974) 's Twitter Profile Photo

StatefulSets are your friend for nodes: โ€ข stable network IDs โ€ข persistent volumes Combine them with PodDisruptionBudgets and you get predictable rolling upgrades instead of โ€œoops, all nodes restartedโ€. ๐Ÿ˜… #Kubernetes #Web3Infra

StatefulSets are your friend for nodes:
โ€ข stable network IDs
โ€ข persistent volumes
Combine them with PodDisruptionBudgets and you get predictable rolling upgrades instead of โ€œoops, all nodes restartedโ€. ๐Ÿ˜…
#Kubernetes #Web3Infra
svax974 .fuel Anomage ๐Ÿง™โ€โ™‚๏ธ,๐Ÿง™โ€โ™‚๏ธ (@svax974) 's Twitter Profile Photo

Consider a sidecar that proxies RPC and enforces: โ€ข auth โ€ข per-key limits โ€ข basic input validation Then your node only talks to a trusted local component, not the whole internet. ๐Ÿงฑ #Security #Sidecars

Consider a sidecar that proxies RPC and enforces:
โ€ข auth
โ€ข per-key limits
โ€ข basic input validation
Then your node only talks to a trusted local component, not the whole internet. ๐Ÿงฑ
#Security #Sidecars
svax974 .fuel Anomage ๐Ÿง™โ€โ™‚๏ธ,๐Ÿง™โ€โ™‚๏ธ (@svax974) 's Twitter Profile Photo

Networking tip: If your nodes are saturating a single NIC, consider: โ€ข separate interface/VLAN for P2P vs RPC โ€ข enabling TCP fast open / tuning buffers (carefully) โ€ข monitoring retransmits The network is part of your node, not just a cable. ๐ŸŒ #Networking #NodeRunner

Networking tip:
If your nodes are saturating a single NIC, consider:
โ€ข separate interface/VLAN for P2P vs RPC
โ€ข enabling TCP fast open / tuning buffers (carefully)
โ€ข monitoring retransmits
The network is part of your node, not just a cable. ๐ŸŒ
#Networking #NodeRunner
svax974 .fuel Anomage ๐Ÿง™โ€โ™‚๏ธ,๐Ÿง™โ€โ™‚๏ธ (@svax974) 's Twitter Profile Photo

NUMA awareness matters on big machines. If your node hops across NUMA nodes: โ€ข memory latency goes up โ€ข caches are less effective Pinning to a single NUMA node can be a free win for consistency. ๐Ÿง  #Linux #Performance

NUMA awareness matters on big machines.
If your node hops across NUMA nodes:
โ€ข memory latency goes up
โ€ข caches are less effective
Pinning to a single NUMA node can be a free win for consistency. ๐Ÿง 
#Linux #Performance