Node Operations 1 - Rapid Execution Nodes
How to Create an ERC-20 Token with Custom Features Using Rapid Deployer
Rapid Execution Nodes are the high-performance engines of the network, designed to handle high-frequency computational loads while ensuring data isolation. Unlike standard settlement nodes, these units prioritize throughput and sophisticated smart contract logic to facilitate rapid market interactions.
12.1. Execution Logic and State Management
Rapid Execution Nodes treat transactions as complex financial intents rather than simple value transfers. This approach allows for sophisticated pre-settlement logic to be processed efficiently before committing to the system of record.
Netting and Matching Engine: These nodes perform real-time multilateral netting, reducing the number of final instructions sent to the settlement layer by over 90%.
Dual VM Support: Nodes concurrently run a high-performance EVM for standard dApp logic and the RAda VM for safety-critical, formally verified institutional operations.
Local Data Isolation: To ensure institutional confidentiality, full execution details—such as intermediate state changes and netting logic—are maintained locally within the execution node and are not broadcast to the entire network.
Intent-to-Instruction Pipeline: The node translates complex bilateral agreements and margin logic into clean, minimal settlement instructions compatible with the Canton Network.
12.2. Technical Deployment Specifications
To maintain the required latency and throughput for institutional DeFi and repo markets, operators must deploy nodes on hardware optimized for high-frequency state updates.
Component
Minimum Specification
Recommended (Institutional)
CPU
8 Cores (High clock speed)
16+ Cores (Gold/Platinum Tier)
RAM
32 GB ECC
64 GB+ ECC
Storage
1 TB NVMe SSD
2 TB+ NVMe (RAID 1 Optimized)
Network
1 Gbps Symmetric
10 Gbps Low-latency / Dedicated
Execution Engine
Rapid Geth-Native (Beta)
Rapid High-Assurance Stack
12.3. Operational Parameters and Finality
The Execution Node operates under a deterministic trust model, ensuring that once a state change is netted, it is prepared for immediate atomic synchronization.
BFT Sync Mode: Uses a Byzantine Fault Tolerant consensus to achieve sub-second execution finality within the vetted validator set.
State Pruning: Automatic state pruning is enabled by default to ensure the database remains lean, focusing on the latest "financial intent" snapshots rather than an exhaustive monolithic history.
RPC Gateway: Standard JSON-RPC 8545 is available for EVM interactions, while a dedicated FIX-compatible gateway is provided for institutional API access.
12.4. Deployment Command Line (Beta)
Operators can initialize their execution environment using the following command structure to link directly with the Canton integration adapters.
Last updated