Node Roles Overview

Explore the different roles your nodes can take on. Each role plays a crucial part in defining how nodes interact with networks.

Add New Role Configure Roles Refresh Roles
Name Description Color Active Nodes Actions
Eavesdropper-v2 Passive node that listens to all traffic and logs sensitive activity. 8 View
Replay-node Resends old transactions to test replay attack resistance. 10 View
Sybil-agent Part of a Sybil attack network — used to flood with fake identities. 6 View
Interceptor Modifies or delays block propagation to analyze propagation attacks. 9 View
Rogue-validator Validator that proposes invalid blocks or double signs. 8 View
Front-runner Simulates MEV-style attacks by observing mempool and jumping transactions. 6 View
Chain-reorganizer Tries to force forks or deep reorgs for double-spending. 10 View
Fake-oracle Injects incorrect external data into smart contracts. 8 View
M-light-node Requests data inconsistently to test full nodes. 5 View
Entrypoint First node in network for new peers (can be flooded). 7 View
Exit-node Final relay node for broadcasting to outside networks. 10 View
Bridge-node Connects two different chains or subnets (vulnerable to bridge attacks). 11 View
Archive-node Stores full chain history — resource intensive and target for data attacks. 3 View
Indexer Indexes data for APIs — prone to overload or DOS attacks. 11 View
Load-balancer Distributes traffic — can be used to simulate bottlenecks. 6 View
Fuzzer Injects malformed or random inputs to detect crashes or unexpected behavior. 8 View
Dust-attacker Sends small-value transactions to trace wallet activity. 4 View
Spam-relay Floods mempool with spam transactions to simulate congestion. 8 View
Slowloris-node Keeps connections open indefinitely to exhaust peer slots. 6 View
Fork-trigger Intentionally mines conflicting blocks to simulate fork scenarios. 6 View
Consensus-splitter Creates conflicting messages to desync consensus. 6 View
Fake-time-server Messes with timestamp info to test clock drift and sync issues. 15 View
Deep-inspector Runs packet-level inspection on all P2P traffic. 6 View
Zombie-node Dormant or hijacked node reactivated for attacks. 6 View
Ghost-relay Invisible relay that hides metadata and origin. 1 View
Toxic-mirror Reflects invalid data or requests to crash other nodes. 6 View
Backdoor-node Intentionally vulnerable node for exploit testing. 6 View
Cloaked-agent Masks its traffic and identity like a normal node. 9 View
Payload-dropper Drops custom payloads into peers to exploit parsing. 8 View
Rate-limiter Throttles traffic to simulate network strain or slow peers. 9 View
Blackhole-node Receives but never forwards or responds — simulates packet loss. 7 View
Header-forger Sends blocks with crafted or forged headers. 5 View
State-corruptor Alters local state to simulate DB inconsistencies or rollback attacks. 6 View
Tx-modifier Alters transactions mid-flight to test signature checks and verification. 8 View
Log-stripper Removes logging or emits misleading logs. 10 View
Oracle-desyncer Introduces desync between multiple oracle feeds. 8 View
Fake-bootstrapper Fakes bootstrap data to seed new nodes with invalid state. 8 View
Checksum-attacker Sends corrupted packets with correct checksum to test validation layers. 7 View
Dns-poisoner Manipulates DNS responses to reroute traffic. 9 View
Sidecar-injector Injects sidecar code or plugins into target peers. 9 View
Connection-jammer Rapidly opens and closes sockets to exhaust file descriptors. 4 View