Blockchain and Web3 workloads concentrate value in RPC, wallet APIs, and frontends. Attacks target public nodes, mint windows, and exchange login paths—edge policy must be explainable.
Typical pressures
- Public JSON-RPC flooded until nodes exhaust bandwidth and connections
- Validator IPs exposed to targeted DDoS
- Exchange and wallet APIs under stuffing and bots
- Mint events combining L7 CC with static asset bandwidth spikes
Typical scenarios
Edge entry for on-chain workloads
Scenario path
Method-level limits
Split reads vs writes; drop bad JSON-RPC.
dApp → gateway → node
Scenario path
Login and withdraw guard
Stuffing and bots; auditable write path.
User → WAF → core
Scenario path
Static + dynamic split
CDN for pages; dedicated CC/queue for mint APIs.
Page CDN → API guard
Node concealment
Validators sit behind the edge
Focus areas
RPC gateway guard
Method-level limits, bad JSON-RPC dropped, node IPs hidden.
Exchange / wallet
TLS termination, bot management, auditable write-path logs.
DDoS scrub
Tbps capacity with L4/L7 alignment in front of node racks.
Mint & campaigns
CDN for static, dedicated rules and queues for mint APIs.
RPC posture
Abnormal JSON-RPC radar
Architecture
RPC & dApp edge path
Anycast → layered JSON-RPC/REST policy → WAF & CC → only clean traffic to nodes or origin clusters.
- 01RPC/API hostnames on global edges
- 02Method and path rate limits; split read calls vs write broadcast
- 03Bot and geo controls on wallet write APIs
- 04Full-path logs with policy IDs