Skip to main content
Two registries. CANONICAL_CHAINS holds every chain a program can name, EVM chains and Solana, and is read by requireChain, resolveChain and the slug, id and alias lookups. The chains record, read by getChain, holds native-currency and explorer metadata for most EVM chains. The same exports come from the root and from @eco-incorp/sauce/chains.
Generated from the type declarations of @eco-incorp/sauce.

NativeErc20

Interface · @eco-incorp/sauce/chains, @eco-incorp/sauce A native coin that is ALSO an ERC-20: one balance, read two ways. eth_getBalance, msg.value and gas use the native scale; balanceOf and transfer at address use decimals. Sending native value and calling transfer move the same money. Nothing needs wrapping, so such a chain has no canonical wrapped native, and a WETH9-style call has no canonical target there.

ChainDeployment

Interface · @eco-incorp/sauce Chain ID to deployment addresses mapping

ProtocolInfo

Interface · @eco-incorp/sauce Protocol metadata

ProtocolCategory

Type · @eco-incorp/sauce

ContractABI

Interface · @eco-incorp/sauce ABI entry for a protocol contract

SauceFunction

Interface · @eco-incorp/sauce A Sauce function that interacts with a protocol

SauceParam

Interface · @eco-incorp/sauce

Chain

Interface · @eco-incorp/sauce EVM chain definition. Carries no RPC endpoint: the SDK ships none. Whatever reads a chain takes its URL, or a client, from the caller.