Notes
- Intent-based architecture: users express desired outcome, solvers compete to fill
- Rebranded from Connext to Everclear — same contracts
- Same EverclearSpoke address deployed across all chains
- Uses domain IDs (uint32) for destination chains, NOT EVM chain IDs
- Supports cross-chain swaps (inputAsset != outputAsset)
ttldetermines how long the intent is valid — unfilled intents can be cancelled after expiry- Finality: typically 2-15 minutes depending on solver activity
- Requires ERC-20 approval to the EverclearSpoke
Its names in a program
On Ethereum,Connext is a namespace: its contracts need no import.
Deployments
ABI
EverclearSpokeABI
import EverclearSpokeABI from "./protocols/connext/EverclearSpokeABI.json"; Speaks for: everclearSpoke.
newIntent(uint32[] destinations, address receiver, address inputAsset, address outputAsset, uint256 amount, uint256 amountOutMin, uint48 ttl, bytes data) returns (bytes32 intentId, (bytes32 initiator, bytes32 receiver, bytes32 inputAsset, bytes32 outputAsset, uint32 origin, uint64 nonce, uint48 timestamp, uint48 ttl, uint256 amount, uint256 amountOutMin, uint32[] destinations, bytes data) intent)
Next steps
- Protocols: the other protocols, by what they do.
- Protocols and tokens: calling a contract by its namespace, or through its ABI.
- Glossary: the words these pages use, in plain terms.
