The protocol’s integrity reduces to three defense layers. Subnet economic security, relay challenge economics, and adapter contract correctness. An attacker must defeat all three to produce a bad verdict that gets paid.Documentation Index
Fetch the complete documentation index at: https://docs.pelion.dev/llms.txt
Use this file to discover all available pages before exploring further.
Single-subnet attack cost
The first defense is the cost of corrupting subnet-level consensus. To move a single subnet’s weighted verdict, an attacker must acquire enough alpha-weighted validator influence to override honest validators. The approximate cost formula.Multi-subnet defense
For higher-stakes questions, Pelion’s adapter supports routing the same question to multiple subnets. The verdicts must agree (or meet a quorum rule) before finalization. An attacker must now corrupt a quorum of subnets simultaneously. The cost of this scales close to multiplicatively across subnets because the attacks are largely independent. Acquiring alpha in SN6 does not give any advantage when attacking SN28. There is some sub-linearity from shared attack infrastructure (bot nets, coordination) but the dominant term is independent per-subnet cost. Routing policy. Low-stakes questions default to a single subnet to keep cost down. High-stakes questions fan out to multiple subnets. The threshold is configurable and is expected to move with observed attack attempts.Relay challenge economics
Even with corrupted subnet consensus, the relay challenge layer provides an orthogonal defense. Here’s how. The relayer that posts a verdict to Base bonds USDC. The verdict it posts carries validator signatures claiming to represent subnet consensus at a specific block height. A challenger running a 24/7 verification client can (a) watchVerdictSubmitted events on Base, (b) independently fetch the actual subnet consensus at the cited block height, (c) compare, and (d) submit a counter-verdict with their own bond if the two don’t match.
The economics make honest challenging rational. Challenger bonds are sized so that successful challenges earn the challenger a portion of the losing relayer’s bond. Unsuccessful challenges (challenger’s verdict doesn’t match actual consensus either) forfeit the challenger’s bond.
For this defense to be effective, at least one honest challenger must be watching. With public subnet consensus data and a published challenger client, this is a low bar. A single aligned validator operator or a protocol-adjacent watchdog is enough. The attack requires compromising not just the subnet but also every honest observer watching the relay.
Quantitative comparison to UMA
| Property | UMA | Pelion |
|---|---|---|
| Economic security anchor | UMA token market cap (~$95M) | Alpha market caps across routed subnets, scaled by quorum |
| Attack vector | Acquire or coordinate UMA | Acquire or coordinate alpha across multiple subnets, plus defeat bonded relay challenge |
| Security scaling | Linear with voting-token market cap | Roughly multiplicative across routed subnets, plus relay layer |
| Attacker cost for single subnet (SN6 today) | N/A | Several million USD, plus operational overhead |
| Attacker cost for multi-subnet route (2 subnets) | N/A | Multiplies, roughly square of single-subnet cost |
| Breakeven against $100M market | Requires UMA market cap ≥ $100M, which it isn’t | Covered by single-subnet routing at SN6 alpha levels |