Notes
- Socket is a bridge aggregator — routes through underlying bridges (Across, Stargate, Hop, cBridge, Connext, etc.)
- Two-step process: (1) call Socket API to get a route + encoded
bridgeData, (2) execute on-chain viaexecuteRoute() - There is no separate
bridge()entry point:executeRoute()handles bridge, swap, and combined routes - Same Gateway address (
0x3a23F9...) deployed across all supported chains routeIdidentifies the specific bridge integration (each bridge has its own route handler contract)- The
bridgeDatais opaque — generated by the Socket API based on token, amount, source/destination chains - Requires ERC-20 approval to the Socket Gateway address
- Finality depends on the underlying bridge selected
Its names in a program
On Ethereum,Socket is a namespace: its contracts need no import.
Deployments
ABI
SocketGatewayABI
import SocketGatewayABI from "./protocols/socket/SocketGatewayABI.json"; Speaks for: socketGateway.
executeRoute(uint32 routeId, bytes routeData) payable returns (bytes result)
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.
