How Does Everclear Work?
Everclear is the rebrand + pivot of Connext into a 'clearing layer' for intent-based bridges. Instead of locking-and-minting or pooling liquidity per route, Everclear lets solvers front user capital and then periodically nets solver positions across chains. TVL is a flow metric reflecting unsettled solver balances (~$0 at time of scan), not locked deposits. The Everclear Hub L3 (their dedicated netting chain) was silently shut down in May 2026 with no public announcement; the team states the clearing layer continues on supported L2s. Novel architecture means novel failure modes: solver market thinness, netting engine correctness, Hyperlane messaging dependencies, and inherited Connext contract complexity are first-order risks. The CLEAR token is at all-time lows with sub-$400K market cap.
TVL
$0
Sector
Bridge
Risk Grade
C-
Value Grade
D
Core Mechanisms
8.1.2 Liquidity pool bridges
NovelIntent-based clearing layer — solvers settle, netting occurs later
Users submit 'intents' (what they want, not how to get it). Solvers compete to fill intents using their own capital. The Everclear clearing layer periodically nets solver positions across chains, drastically reducing bridge volume. Novel settlement architecture.
8.4.1 Relayer fee models
NovelSolver fee competition
Solvers bid for intent fills. Users benefit from competitive pricing when solver market is liquid; suffer when it's thin.
2.3.3 Algorithmic treasury
NovelNetting engine on Everclear chain for solver rebalancing
Everclear ran its own L3 chain where solver positions were netted. The L3 hub was silently halted in May 2026; netting now occurs on supported L2s. This shift removes the dedicated netting chain trust assumption but reduces architectural clarity.
8.1.3 Message-passing bridges
Hyperlane + other messaging integrations
Cross-chain state is communicated via Hyperlane and other messaging bridges. Inherits their security.
5.4.1 Multisig override
Team multisig + governance for contract upgrades
Core contract upgrades controlled by multi-signature wallet with governance overlay. Upgrade rights were transferred from Gelato Multisig to a new Safe contract in May 2026 concurrent with L3 hub shutdown.
How the Pieces Interact
If solver capital is thin on a specific route, users face worse pricing or failed fills. Under market stress (when users need cross-chain most), solver market may freeze.
Solvers rely on Everclear's netting to be correct and timely to recover capital. A netting engine bug, halt, or manipulation could strand solver capital and cascade into solver insolvency. The May 2026 L3 halt demonstrated that infrastructure changes can occur without notice.
Intent status updates cross chains via Hyperlane. A Hyperlane security event (validator compromise, bug) affects Everclear correctness.
Everclear's codebase evolved from Connext NXTP -> Amarok -> current clearing layer. Accumulated complexity with a relatively lean team increases the probability of undiscovered bugs.
What Could Go Wrong
- Everclear Hub L3 (their own netting chain) silently halted on May 1, 2026 with no public announcement; team reports clearing layer continues on supported L2s, but hub shutdown removes the primary netting architecture and raises transparency concerns
- Intent/solver architecture assumes competing solvers will always find optimal fills; under stress or solver collusion, users can receive worse-than-expected execution
- CLEAR token has declined 99.5% from ATH to ~$353K market cap; near-zero on-chain revenue ($148/30d) and 4+ months without blog updates signal protocol viability concerns
Solver Market Collapse Under Stress
ModerateTrigger: Market stress (e.g., correlated liquidations, bridge exploit elsewhere) drives solvers to withdraw capital, leaving intent fills unfillable
- 1.Market stress event causes solvers to de-risk — Active solver capital drops sharply
- 2.User intents struggle to find fills; fill prices widen or timeouts occur — Users either overpay or get stuck mid-cross-chain
- 3.Failed-intent refund process stresses Everclear accounting — Operational burden; potentially bad UX at scale
Risk Profile at a Glance
Overall: C- (53/100)
Lower score = safer