How Does Everclear Work?

Bridge|Risk C|5 mechanisms|4 interactions

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 on its own netting chain. The design drastically reduces bridge volume when solvers are healthy. TVL is a flow metric reflecting unsettled solver balances (~$693 at time of scan), not locked deposits — Everclear has processed billions in cumulative intent volume. Novel architecture means novel failure modes: solver market thinness, netting engine correctness, Hyperlane messaging dependencies, and inherited Connext contract complexity are all first-order risks.

TVL

$693

Sector

Bridge

Risk Grade

C

Value Grade

D

Core Mechanisms

8.1.2 Liquidity pool bridges

Novel

Intent-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

Novel

Solver 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

Novel

Netting engine on Everclear chain for solver rebalancing

Everclear runs its own chain where solver positions are netted. This netting chain is a new trust assumption — its security model matters for correctness.

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.

How the Pieces Interact

Solver-based intent fillsSolver capital availabilityHigh

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.

Netting on Everclear chainSolver rebalancing settlementHigh

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.

Hyperlane cross-chain messagingIntent finalityMedium

Intent status updates cross chains via Hyperlane. A Hyperlane security event (validator compromise, bug) affects Everclear correctness.

Connext Amarok inherited contract stackPost-rebrand code complexityMedium

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

  1. Everclear (formerly Connext) rebranded and pivoted to intent-based 'clearing layer' — pivot history means the current product is relatively new and less battle-tested than the TVL might suggest
  2. Intent/solver architecture assumes competing solvers will always find optimal fills; under stress or solver collusion, users can receive worse-than-expected execution
  3. Connext Amarok contracts had a governance/upgrade vulnerability disclosed in 2023; Everclear's contract stack carries inherited complexity

Solver Market Collapse Under Stress

Moderate

Trigger: Market stress (e.g., correlated liquidations, bridge exploit elsewhere) drives solvers to withdraw capital, leaving intent fills unfillable

  1. 1.Market stress event causes solvers to de-risk Active solver capital drops sharply
  2. 2.User intents struggle to find fills; fill prices widen or timeouts occur Users either overpay or get stuck mid-cross-chain
  3. 3.Failed-intent refund process stresses Everclear accounting Operational burden; potentially bad UX at scale

Risk Profile at a Glance

Mechanism Novelty12/15
Interaction Severity10/20
Oracle Surface5/10
Documentation Gaps6/10
Track Record7/15
Scale Exposure0/10
Regulatory Risk4/10
Vitality Risk5/10
C

Overall: C (49/100)

Lower score = safer

More on Everclear

Related Bridge Explainers