Layer 04: The Routing Engine
While the Split Engine handles "How much," the Routing Engine handles "When" and "Where."
Temporal Dissonance
The Routing Engine introduces artificial latency. In a standard Solana transaction, instructions are atomic and happen in the same slot. Verdant breaks this atomicity for privacy. The engine schedules shard transactions across different blocks (Slots). This prevents all fragments of a split transaction from appearing in the same block, which is a common indicator of a batch operation.
Path Optimization
The Routing Engine views the network of Shards and Shadows Nodes as a directed graph. It calculates routes based on:
Entropy Score: Choosing paths that have the highest level of existing noise.
Congestion Avoidance: Routing transactions during periods of high network activity to hide them in the crowd.
Cost Efficiency: Balancing the privacy gain against the cost of Solana priority fees.
Last updated