Node Types

Plasma supports multiple node types based on architecture roles and operational goals.

​

Node Types

​

Non-Validator Nodes

Non-validator nodes are read-only participants that follow the blockchain without participating in consensus decisions. They provide a lightweight way to access blockchain data without the overhead of consensus participation.

For a more in-depth explanation of our design decisions, please refer to the Overview page.

Key Capabilities

• Block reception: Receive and process blocks from the network
• Chain synchronization: Maintain an up-to-date copy of the blockchain
• Catchup mechanism: Automatically detect and recover missing blocks
• API access: Provide the same API endpoints as validators for querying blockchain state

Technical Characteristics

• Simplified configuration with node ID (string identifier)
• Read-only access to validator public keys
• Connect through bootstrap nodes
• Cannot propose blocks, vote, or trigger view changes

Setup: Follow the Non-Validator Node Setup guide.

​

RPC Providers

Hosted RPC infrastructure with production-grade availability and support.

Current Providers

• QuickNode: High-performance global infrastructure with monitoring and alerting.

Benefits

• Immediate production-ready access
• SLAs and support included
• Scales with application demand

Use Cases

• Production applications requiring high availability
• Teams prioritizing development over infrastructure
• Projects needing enterprise support and guarantees

List of Providers: Follow the RPC Providers page.

​

Consensus Nodes

Consensus nodes are the core participants in the Plasma consensus layer, implementing the Fast-Hotstuff Byzantine Fault Tolerant (BFT) protocol. The network can tolerate up to f faulty nodes in a system of 3f+1 total validators.

Key Responsibilities

• Block production: Validators take turns proposing blocks using round-robin selection based on the current view
• Voting: Validate incoming blocks and cast votes that are aggregated into Quorum Certificates (QCs)
• Consensus participation: Actively participate in view changes, timeouts, and the 2-chain finalization rule
• State management: Maintain full consensus state including vote aggregation, view tracking, and block finalization

Technical Requirements

• BLS keypair for cryptographic operations and vote aggregation
• Full node configuration with validator ID (numeric identifier)
• Access to execution layer (reth) for block production
• P2P networking capabilities for unicast and broadcast messaging

Preparation: Follow the Consensus Node Preparation page.

​

Getting Started

​

For Non-Validator Nodes

Contact required: All node operators must submit a form to our team before deploying nodes.

1. Submit contact form: Reach out here.
2. Review requirements: Check hardware requirements and ensure you meet specifications.
3. Set up infrastructure: Follow our non-validator node setup guide for detailed instructions.
4. Configure monitoring: Implement monitoring using our monitoring guide.
5. Join community: Connect with other operators in our Discord.
6. Stay updated: Monitor announcements for consensus participation timeline.

​

For Application Developers

1. Choose provider: Select between non-validator nodes or professional RPC providers.
2. Configure network: Add Plasma testnet to your development environment.
3. Test integration: Deploy and test your applications on testnet.
4. Monitor performance: Track RPC performance and adjust as needed.
5. Plan production: Prepare for mainnet launch and scaling requirements.

​

For Future Consensus Operators

1. Request access: Start by reaching out to our team here for non-validator nodes.
2. Start with non-validator nodes: Gain operational experience with non-validator nodes.
3. Build infrastructure: Design and test your consensus-ready infrastructure.
4. Engage community: Participate in governance discussions and provide feedback.
5. Prepare economics: Understand staking requirements and reward structures.
6. Monitor timeline: Stay informed about consensus participation opening.