@eco-incorp/sauce 0.99.6 → 0.99.7

package/{sdk/src/skills → skills/sauce-protocols/references}/balancer-v2.md

@@ -1,10 +1,12 @@
 # Balancer V2
 
+> **In a Sauce program**, swap through the Sauce Router wherever it services the pool, with a price limit, a minimum output and the unspent input returned (`sauce-swaps`; several pools under one limit, `sauce-distributed-swap`). The templates below call the protocol's own contracts.
+
 Generalized AMM with weighted pools, single Vault architecture, and flash loans. Supports custom pool types (weighted, stable, linear, composable stable) and multi-token pools with up to 8 tokens per pool.
 
 ## Category
 
-dex | Chains: Ethereum, Polygon, Arbitrum, Optimism, Gnosis, Avalanche, Base, BSC
+dex | Chains and addresses: [registry/balancer-v2.md](registry/balancer-v2.md)
 
 ## Key Operations
 
@@ -12,13 +14,12 @@ dex | Chains: Ethereum, Polygon, Arbitrum, Optimism, Gnosis, Avalanche, Base, BS
 - **addLiquidity**: Join a pool by depositing tokens via the Vault
 - **removeLiquidity**: Exit a pool by withdrawing tokens via the Vault
 
-## SDK Usage
-
-```typescript
-import { protocolInfo, deployments, sauceFunctions } from "@eco-incorp/sauce/protocols/balancer-v2";
-```
+## Typed templates for the raw compiler (not for `sauce compile`)
 
-## SauceScript Examples
+These import the protocol's ABI from `./abis`, the way the registry compiles them with the raw
+compiler; `sauce compile` has no such module. In a program for a chain, name the contract by its
+namespace, or import its ABI from `./protocols/<slug>/<Export>.json` as the registry file at the
+top of this document shows, and write SauceScript's values (`~0n`, not `type(uint256).max`).
 
 ### swap
 
@@ -115,29 +116,11 @@ function main(
 - `userData`: ABI-encoded exit type and amounts. Exit types: EXACT_BPT_IN_FOR_ONE_TOKEN_OUT, EXACT_BPT_IN_FOR_TOKENS_OUT, BPT_IN_FOR_EXACT_TOKENS_OUT
 - `minAmountsOut`: Minimum amounts to receive per token (slippage protection)
 
-## Key Addresses
-
-| Chain     | Contract | Address                                      |
-| --------- | -------- | -------------------------------------------- |
-| Ethereum  | Vault    | `0xBA12222222228d8Ba445958a75a0704d566BF2C8` |
-| Polygon   | Vault    | `0xBA12222222228d8Ba445958a75a0704d566BF2C8` |
-| Arbitrum  | Vault    | `0xBA12222222228d8Ba445958a75a0704d566BF2C8` |
-| Optimism  | Vault    | `0xBA12222222228d8Ba445958a75a0704d566BF2C8` |
-| Gnosis    | Vault    | `0xBA12222222228d8Ba445958a75a0704d566BF2C8` |
-| Avalanche | Vault    | `0xBA12222222228d8Ba445958a75a0704d566BF2C8` |
-| Base      | Vault    | `0xBA12222222228d8Ba445958a75a0704d566BF2C8` |
-| BSC       | Vault    | `0xBA12222222228d8Ba445958a75a0704d566BF2C8` |
-
-## ABI Methods
-
-### BalancerV2VaultABI
+## Deployments and ABI
 
-- `swap(tuple(bytes32 poolId, uint8 kind, address assetIn, address assetOut, uint256 amount, bytes userData), tuple(address sender, bool fromInternalBalance, address recipient, bool toInternalBalance), uint256 limit, uint256 deadline) -> uint256 amountCalculated` - Execute a single swap. `kind`: 0=GIVEN_IN, 1=GIVEN_OUT
-- `batchSwap(uint8 kind, tuple[](bytes32 poolId, uint256 assetInIndex, uint256 assetOutIndex, uint256 amount, bytes userData), address[] assets, tuple(address sender, bool fromInternalBalance, address recipient, bool toInternalBalance), int256[] limits, uint256 deadline) -> int256[] assetDeltas` - Execute multi-hop swap through multiple pools in one transaction
-- `joinPool(bytes32 poolId, address sender, address recipient, tuple(address[] assets, uint256[] maxAmountsIn, bytes userData, bool fromInternalBalance))` - Deposit tokens into a pool
-- `exitPool(bytes32 poolId, address sender, address recipient, tuple(address[] assets, uint256[] minAmountsOut, bytes userData, bool toInternalBalance))` - Withdraw tokens from a pool
-- `flashLoan(address recipient, address[] tokens, uint256[] amounts, bytes userData)` - Flash loan from the Vault (zero fee for Balancer pools)
-- `getPoolTokens(bytes32 poolId) -> (address[] tokens, uint256[] balances, uint256 lastChangeBlock)` - Query pool token composition and balances (view)
+The registry's addresses per chain, how a program names each contract there (a namespace, or
+an ABI import bound to the address), and the ABI functions are generated in
+[registry/balancer-v2.md](registry/balancer-v2.md).
 
 ## Notes
 
@@ -150,3 +133,4 @@ function main(
 - Internal balances: users can keep tokens in the Vault to save gas on repeated trades
 - `userData` encoding varies by pool type - check Balancer docs for the specific pool's join/exit types
 - Use Balancer for multi-token pools (3+ tokens), weighted index exposure, or flash loans
+- From a Pot program, `@sauce/router` swaps through the Vault directly: `balancerV2(vault, tokenIn, tokenOut, amountIn, poolId, minOut, recipient)` approves the Vault for exactly `amountIn` and calls `swap` (GIVEN_IN, internal balances off) with `minOut` as its limit, returning the amount out; the allowance ends at zero. `tryBalancerV2` catches a failed swap, resets the approval and returns `0n`. The `balancerV2Swap` action is the same call

package/{sdk/src/skills → skills/sauce-protocols/references}/base-bridge.md

@@ -4,9 +4,14 @@ Official Base L1StandardBridge for depositing ETH and ERC-20 tokens from Ethereu
 
 ## Category
 
-native L2 bridge | Direction: L1 to L2 (Ethereum to Base) | Chains: Ethereum (1), Base (8453)
+native L2 bridge | Direction: L1 to L2 (Ethereum to Base) | Chains and addresses: [registry/base-bridge.md](registry/base-bridge.md)
 
-## SauceScript Functions
+## Typed templates for the raw compiler (not for `sauce compile`)
+
+These import the protocol's ABI from `./abis`, the way the registry compiles them with the raw
+compiler; `sauce compile` has no such module. In a program for a chain, name the contract by its
+namespace, or import its ABI from `./protocols/<slug>/<Export>.json` as the registry file at the
+top of this document shows, and write SauceScript's values (`~0n`, not `type(uint256).max`).
 
 ### depositETH
 
@@ -52,21 +57,11 @@ function main(
 - `_extraData`: Optional extra data (typically `0x00`)
 - Requires ERC-20 approval to the L1StandardBridge
 
-## Deployed Addresses
-
-| Chain    | Contract         | Address                                      |
-| -------- | ---------------- | -------------------------------------------- |
-| Ethereum | l1StandardBridge | `0x3154Cf16ccdb4C6d922629664174b904d80F2C35` |
-| Base     | l2StandardBridge | `0x4200000000000000000000000000000000000010` |
-
-## ABI Reference
-
-### BaseL1StandardBridgeABI
+## Deployments and ABI
 
-- `depositETH(uint32 _minGasLimit, bytes _extraData)` [payable] - Deposit ETH to your own address on Base. Amount = msg.value
-- `depositERC20(address _l1Token, address _l2Token, uint256 _amount, uint32 _minGasLimit, bytes _extraData)` - Deposit ERC-20 tokens to your own address on Base
-- `depositETHTo(address _to, uint32 _minGasLimit, bytes _extraData)` [payable] - Deposit ETH to a specific recipient on Base
-- `depositERC20To(address _l1Token, address _l2Token, address _to, uint256 _amount, uint32 _minGasLimit, bytes _extraData)` - Deposit ERC-20 tokens to a specific recipient on Base
+The registry's addresses per chain, how a program names each contract there (a namespace, or
+an ABI import bound to the address), and the ABI functions are generated in
+[registry/base-bridge.md](registry/base-bridge.md).
 
 ## Notes
 

package/{sdk/src/skills → skills/sauce-protocols/references}/baseswap.md

@@ -1,10 +1,12 @@
 # BaseSwap
 
+> **In a Sauce program**, swap through the Sauce Router wherever it services the pool, with a price limit, a minimum output and the unspent input returned (`sauce-swaps`; several pools under one limit, `sauce-distributed-swap`). The templates below call the protocol's own contracts.
+
 Base-native DEX with UniV2-style constant product pools (x*y=k). Features yield farming, launchpad, and NFT marketplace. A simple and straightforward fork of Uniswap V2 on Base.
 
 ## Category
 
-dex | Chains: Base
+dex | Chains and addresses: [registry/baseswap.md](registry/baseswap.md)
 
 ## Key Operations
 
@@ -12,13 +14,12 @@ dex | Chains: Base
 - **addLiquidity**: Deposit two tokens to mint LP tokens
 - **removeLiquidity**: Burn LP tokens to withdraw underlying tokens
 
-## SDK Usage
-
-```typescript
-import { protocolInfo, deployments, sauceFunctions } from "@eco-incorp/sauce/protocols/baseswap";
-```
+## Typed templates for the raw compiler (not for `sauce compile`)
 
-## SauceScript Examples
+These import the protocol's ABI from `./abis`, the way the registry compiles them with the raw
+compiler; `sauce compile` has no such module. In a program for a chain, name the contract by its
+namespace, or import its ABI from `./protocols/<slug>/<Export>.json` as the registry file at the
+top of this document shows, and write SauceScript's values (`~0n`, not `type(uint256).max`).
 
 ### swap
 
@@ -103,19 +104,11 @@ function main(
 
 - LP token must be approved to the router
 
-## Key Addresses
-
-| Chain | Contract  | Address                                      |
-| ----- | --------- | -------------------------------------------- |
-| Base  | V2 Router | `0x327Df1E6de05895d2ab08513aaDD9313Fe505d86` |
-
-## ABI Methods
-
-### BaseSwapRouterABI
+## Deployments and ABI
 
-- `swapExactTokensForTokens(uint256 amountIn, uint256 amountOutMin, address[] path, address to, uint256 deadline) -> uint256[] amounts` - Swap exact input along path
-- `addLiquidity(address tokenA, address tokenB, uint256 amountADesired, uint256 amountBDesired, uint256 amountAMin, uint256 amountBMin, address to, uint256 deadline) -> (uint256 amountA, uint256 amountB, uint256 liquidity)` - Add liquidity and mint LP tokens
-- `removeLiquidity(address tokenA, address tokenB, uint256 liquidity, uint256 amountAMin, uint256 amountBMin, address to, uint256 deadline) -> (uint256 amountA, uint256 amountB)` - Burn LP tokens for underlying
+The registry's addresses per chain, how a program names each contract there (a namespace, or
+an ABI import bound to the address), and the ABI functions are generated in
+[registry/baseswap.md](registry/baseswap.md).
 
 ## Notes
 

package/{sdk/src/skills → skills/sauce-protocols/references}/beefy.md

@@ -4,7 +4,7 @@ Multi-chain yield optimizer. Auto-compounds rewards from LP tokens and other yie
 
 ## Category
 
-yield | Chains: Ethereum, BSC, Polygon, Arbitrum, Optimism, Base, Avalanche
+yield | Chains and addresses: [registry/beefy.md](registry/beefy.md)
 
 ## Key Operations
 
@@ -13,13 +13,12 @@ yield | Chains: Ethereum, BSC, Polygon, Arbitrum, Optimism, Base, Avalanche
 - **withdraw**: Withdraw by specifying share amount
 - **withdrawAll**: Withdraw entire position
 
-## SDK Usage
+## Typed templates for the raw compiler (not for `sauce compile`)
 
-```typescript
-import { protocolInfo, deployments, sauceFunctions } from "@eco-incorp/sauce/protocols/beefy";
-```
-
-## SauceScript Examples
+These import the protocol's ABI from `./abis`, the way the registry compiles them with the raw
+compiler; `sauce compile` has no such module. In a program for a chain, name the contract by its
+namespace, or import its ABI from `./protocols/<slug>/<Export>.json` as the registry file at the
+top of this document shows, and write SauceScript's values (`~0n`, not `type(uint256).max`).
 
 ```typescript
 // Deposit into Beefy vault
@@ -55,30 +54,11 @@ function main(vaultAddress: Address): Uint256 {
 }
 ```
 
-## Key Addresses
-
-| Chain     | Contract | Address                                      |
-| --------- | -------- | -------------------------------------------- |
-| Ethereum  | BIFI     | `0xB1F1ee126e9c96231Cc3d3fAD7C08b4cf873b1f1` |
-| BSC       | BIFI     | `0xCa3F508B8e4Dd382eE878A314789373D80A5190A` |
-| Polygon   | BIFI     | `0xFbdd194376de19a88F4A68671C339563c427310d` |
-| Arbitrum  | BIFI     | `0x99C409E5f62E4bd2AC142f17caFb6810B8F0BAAE` |
-| Optimism  | BIFI     | `0x4E720DD3Ac5CFe1e1fbDE4935f386Bb1C66F4642` |
-| Base      | BIFI     | `0xc55E93C62874D8100dBd2DfE307EDc1036ad5434` |
-| Avalanche | BIFI     | `0xd6070ae98b8069de6B494332d1A1a81B6179D960` |
-
-## ABI Methods
-
-### BeefyVaultABI
+## Deployments and ABI
 
-- `deposit(uint256)` - Deposit want tokens, receive mooTokens (vault shares)
-- `depositAll()` - Deposit entire want token balance
-- `withdraw(uint256)` - Withdraw by burning shares
-- `withdrawAll()` - Withdraw entire position
-- `getPricePerFullShare()` - Current share price (18 decimals)
-- `balance()` - Total want tokens in vault
-- `balanceOf(address)` - Query mooToken (share) balance
-- `want()` - Address of the underlying want token
+The registry's addresses per chain, how a program names each contract there (a namespace, or
+an ABI import bound to the address), and the ABI functions are generated in
+[registry/beefy.md](registry/beefy.md).
 
 ## Notes
 

package/{sdk/src/skills → skills/sauce-protocols/references}/benqi.md

@@ -4,9 +4,14 @@ Leading lending and borrowing protocol on Avalanche. Compound V2 fork with addit
 
 ## Category
 
-lending | Chains: Avalanche (43114)
+lending | Chains and addresses: [registry/benqi.md](registry/benqi.md)
 
-## SauceScript Functions
+## Typed templates for the raw compiler (not for `sauce compile`)
+
+These import the protocol's ABI from `./abis`, the way the registry compiles them with the raw
+compiler; `sauce compile` has no such module. In a program for a chain, name the contract by its
+namespace, or import its ABI from `./protocols/<slug>/<Export>.json` as the registry file at the
+top of this document shows, and write SauceScript's values (`~0n`, not `type(uint256).max`).
 
 ### supply
 
@@ -68,26 +73,11 @@ function main(qiTokenAddress: Address, amount: Uint256): Uint256 {
 
 - Requires ERC-20 approval of underlying to the qiToken
 
-## Deployed Addresses
-
-| Chain     | Contract    | Address                                      |
-| --------- | ----------- | -------------------------------------------- |
-| Avalanche | comptroller | `0x486Af39519B4Dc9a7fCcd318217352830E8AD9b4` |
-
-## ABI Reference
-
-### QiTokenABI
-
-- `mint(uint256 mintAmount) returns (uint256)` - Supply underlying, receive qiTokens
-- `redeem(uint256 redeemTokens) returns (uint256)` - Redeem qiTokens for underlying
-- `redeemUnderlying(uint256 redeemAmount) returns (uint256)` - Redeem exact underlying amount
-- `borrow(uint256 borrowAmount) returns (uint256)` - Borrow underlying
-- `repayBorrow(uint256 repayAmount) returns (uint256)` - Repay borrow debt
-
-### BenqiComptrollerABI
+## Deployments and ABI
 
-- `enterMarkets(address[] qiTokens) returns (uint256[])` - Enable qiTokens as collateral
-- `exitMarket(address qiToken) returns (uint256)` - Remove qiToken from collateral
+The registry's addresses per chain, how a program names each contract there (a namespace, or
+an ABI import bound to the address), and the ABI functions are generated in
+[registry/benqi.md](registry/benqi.md).
 
 ## Notes
 

package/{sdk/src/skills → skills/sauce-protocols/references}/camelot.md

@@ -1,10 +1,12 @@
 # Camelot
 
+> **In a Sauce program**, swap through the Sauce Router wherever it services the pool, with a price limit, a minimum output and the unspent input returned (`sauce-swaps`; several pools under one limit, `sauce-distributed-swap`). The templates below call the protocol's own contracts.
+
 Native Arbitrum DEX with dual AMM: V2 constant product pools (with native fee-on-transfer token support) and V3 concentrated liquidity pools (Algebra-based with dynamic fees, no fixed fee tiers).
 
 ## Category
 
-dex | Chains: Arbitrum
+dex | Chains and addresses: [registry/camelot.md](registry/camelot.md)
 
 ## Key Operations
 
@@ -13,13 +15,12 @@ dex | Chains: Arbitrum
 - **addLiquidity**: Add liquidity to V2 pools
 - **removeLiquidity**: Remove liquidity from V2 pools
 
-## SDK Usage
+## Typed templates for the raw compiler (not for `sauce compile`)
 
-```typescript
-import { protocolInfo, deployments, sauceFunctions } from "@eco-incorp/sauce/protocols/camelot";
-```
-
-## SauceScript Examples
+These import the protocol's ABI from `./abis`, the way the registry compiles them with the raw
+compiler; `sauce compile` has no such module. In a program for a chain, name the contract by its
+namespace, or import its ABI from `./protocols/<slug>/<Export>.json` as the registry file at the
+top of this document shows, and write SauceScript's values (`~0n`, not `type(uint256).max`).
 
 ### swapV2
 
@@ -83,7 +84,7 @@ function main(
 
 - `routerAddress`: Camelot V3 SwapRouter on Arbitrum
 - No `fee` parameter needed: Camelot V3 uses dynamic fees (Algebra-based), not fixed fee tiers
-- `limitSqrtPrice`: Set to `0` for no price limit
+- `limitSqrtPrice`: `0` in this template, no price limit, so `amountOutMin` is the only bound. Camelot V3 is an Algebra pool, which the Sauce Router's `swapV3` drives with a real limit (`sauce-swaps`)
 
 ### addLiquidity
 
@@ -145,26 +146,11 @@ function main(
 
 - LP token must be approved to the V2 router
 
-## Key Addresses
-
-| Chain    | Contract      | Address                                      |
-| -------- | ------------- | -------------------------------------------- |
-| Arbitrum | V2 Factory    | `0x6EcCab422D763aC031210895C81787E87B43A652` |
-| Arbitrum | V2 Router     | `0xc873fEcbd354f5A56E00E710B90EF4201db2448d` |
-| Arbitrum | V3 Factory    | `0x1a3c9B1d2F0529D97f2afC5136Cc23e58f1FD35B` |
-| Arbitrum | V3 SwapRouter | `0x1F721E2E82F6676FCE4eA07A5958cF098D339e18` |
-
-## ABI Methods
-
-### CamelotV2RouterABI
-
-- `swapExactTokensForTokensSupportingFeeOnTransferTokens(uint256 amountIn, uint256 amountOutMin, address[] path, address to, address referrer, uint256 deadline)` - V2 swap with fee-on-transfer token support and referral. Note: no return value
-- `addLiquidity(address tokenA, address tokenB, uint256 amountADesired, uint256 amountBDesired, uint256 amountAMin, uint256 amountBMin, address to, uint256 deadline) -> (uint256 amountA, uint256 amountB, uint256 liquidity)` - Add V2 LP
-- `removeLiquidity(address tokenA, address tokenB, uint256 liquidity, uint256 amountAMin, uint256 amountBMin, address to, uint256 deadline) -> (uint256 amountA, uint256 amountB)` - Remove V2 LP
-
-### CamelotV3SwapRouterABI
+## Deployments and ABI
 
-- `exactInputSingle(tuple(address tokenIn, address tokenOut, address recipient, uint256 deadline, uint256 amountIn, uint256 amountOutMinimum, uint160 limitSqrtPrice)) -> uint256 amountOut` - V3 concentrated liquidity swap with dynamic fees
+The registry's addresses per chain, how a program names each contract there (a namespace, or
+an ABI import bound to the address), and the ABI functions are generated in
+[registry/camelot.md](registry/camelot.md).
 
 ## Notes
 

package/{sdk/src/skills → skills/sauce-protocols/references}/cbeth.md

@@ -4,20 +4,19 @@ Coinbase's liquid staking token for Ethereum. cbETH represents staked ETH plus a
 
 ## Category
 
-liquid-staking | Chains: Ethereum, Base
+liquid-staking | Chains and addresses: [registry/cbeth.md](registry/cbeth.md)
 
 ## Key Operations
 
 - **transfer**: Transfer cbETH tokens
 - **approve**: Approve spender for cbETH
 
-## SDK Usage
+## Typed templates for the raw compiler (not for `sauce compile`)
 
-```typescript
-import { protocolInfo, deployments, sauceFunctions } from "@eco-incorp/sauce/protocols/cbeth";
-```
-
-## SauceScript Examples
+These import the protocol's ABI from `./abis`, the way the registry compiles them with the raw
+compiler; `sauce compile` has no such module. In a program for a chain, name the contract by its
+namespace, or import its ABI from `./protocols/<slug>/<Export>.json` as the registry file at the
+top of this document shows, and write SauceScript's values (`~0n`, not `type(uint256).max`).
 
 ```typescript
 // Transfer cbETH
@@ -35,22 +34,11 @@ function main(cbethAddress: Address, spender: Address, amount: Uint256): Uint256
 }
 ```
 
-## Key Addresses
-
-| Chain    | Contract | Address                                      |
-| -------- | -------- | -------------------------------------------- |
-| Ethereum | cbETH    | `0xBe9895146f7AF43049ca1c1AE358B0541Ea49704` |
-| Base     | cbETH    | `0x2Ae3F1Ec7F1F5012CFEab0185bfc7aa3cf0DEc22` |
-
-## ABI Methods
-
-### CbETHABI
+## Deployments and ABI
 
-- `mint(address to, uint256 amount) returns (bool)` - Mint cbETH (restricted to Coinbase's minters)
-- `exchangeRate()` - Current cbETH/ETH exchange rate (Ethereum only; Base cbETH is a bridged token without it)
-- `balanceOf(address)` - Query cbETH balance
-- `approve(address,uint256)` - Approve spender
-- `transfer(address,uint256)` - Transfer cbETH
+The registry's addresses per chain, how a program names each contract there (a namespace, or
+an ABI import bound to the address), and the ABI functions are generated in
+[registry/cbeth.md](registry/cbeth.md).
 
 ## Notes
 

package/skills/sauce-protocols/references/cctp.md

@@ -0,0 +1,47 @@
+# CCTP
+
+Circle's Cross-Chain Transfer Protocol moves native USDC between chains: `depositForBurn` burns it
+on this chain, Circle attests the burn, and a `receiveMessage` on the destination mints it there.
+
+## When to use it
+
+- Move USDC to another chain as native USDC, with Circle's attestation as the only trust.
+- Only the burn happens in the program's transaction. The mint is a separate transaction on the
+  destination, sent by anyone with the attestation; to run code there too, open a Sauce intent
+  (`sauce-intents`).
+
+## Pitfalls for a program
+
+- Approve the TokenMessenger for the amount first.
+- `destinationDomain` is Circle's domain id, not the chain id: each chain's file in `sauce-chains`
+  gives its CCTP domain.
+- `mintRecipient` and `destinationCaller` are 32-byte words: an EVM address fits as is, and a
+  `destinationCaller` of `0n` lets anyone complete the mint.
+- `minFinalityThreshold` 2000 waits for standard finality; 1000 asks for a fast transfer, for which
+  `maxFee` (in USDC units, taken on the destination) must cover Circle's fee.
+
+## In a Sauce program
+
+Burn the Pot's USDC on Base for `recipient` on Arbitrum:
+
+```sauce chain=base
+function main(amount: Uint256, recipient: Address, maxFee: Uint256) {
+  // Arbitrum is CCTP domain 3; 2000 is standard finality (1000 asks for a fast transfer).
+  USDC.approve(Cctp.TokenMessenger, amount);
+  Cctp.TokenMessenger.depositForBurn(amount, 3n, recipient, USDC, 0n, maxFee, 2000n);
+}
+```
+
+## Category
+
+bridge | Chains and addresses: [registry/cctp.md](registry/cctp.md)
+
+## Deployments and ABI
+
+The registry's addresses per chain, how a program names each contract there (a namespace, or
+an ABI import bound to the address), and the ABI functions are generated in
+[registry/cctp.md](registry/cctp.md).
+
+## Notes
+
+- Domains are Circle's numbering; the registry records them per chain.

package/{sdk/src/skills → skills/sauce-protocols/references}/celer.md

@@ -4,9 +4,14 @@ Multi-chain bridging protocol using SGN (State Guardian Network) for cross-chain
 
 ## Category
 
-bridge | Direction: any-to-any (L1-to-L2, L2-to-L2, L2-to-L1) | Chains: Ethereum (1), Arbitrum (42161), Optimism (10), Polygon (137), BSC (56), Avalanche (43114)
+bridge | Direction: any-to-any (L1-to-L2, L2-to-L2, L2-to-L1) | Chains and addresses: [registry/celer.md](registry/celer.md)
 
-## SauceScript Functions
+## Typed templates for the raw compiler (not for `sauce compile`)
+
+These import the protocol's ABI from `./abis`, the way the registry compiles them with the raw
+compiler; `sauce compile` has no such module. In a program for a chain, name the contract by its
+namespace, or import its ABI from `./protocols/<slug>/<Export>.json` as the registry file at the
+top of this document shows, and write SauceScript's values (`~0n`, not `type(uint256).max`).
 
 ### bridge
 
@@ -36,23 +41,11 @@ function main(
 - `maxSlippage`: Maximum slippage in basis points (e.g. 500 = 5%). Applied during pool-based bridging
 - Requires ERC-20 approval to the Bridge
 
-## Deployed Addresses
-
-| Chain     | Contract | Address                                      |
-| --------- | -------- | -------------------------------------------- |
-| Ethereum  | bridge   | `0x5427FEFA711Eff984124bFBB1AB6fbf5E3DA1820` |
-| Arbitrum  | bridge   | `0x1619DE6B6B20eD217a58d00f37B9d47C7663feca` |
-| Optimism  | bridge   | `0x9D39Fc627A6d9d9F8C831c16995b209548cc3401` |
-| Polygon   | bridge   | `0x88DCDC47D2f83a99CF0000FDF667A468bB958a78` |
-| BSC       | bridge   | `0xdd90E5E87A2081Dcf0391920868eBc2FFB81a1aF` |
-| Avalanche | bridge   | `0xef3c714c9425a8F3697A9C969Dc1af30ba82e5d4` |
-
-## ABI Reference
-
-### CelerBridgeABI
+## Deployments and ABI
 
-- `send(address _receiver, address _token, uint256 _amount, uint64 _dstChainId, uint64 _nonce, uint32 _maxSlippage)` - Send ERC-20 tokens cross-chain via liquidity pool
-- `sendNative(address _receiver, uint256 _amount, uint64 _dstChainId, uint64 _nonce, uint32 _maxSlippage)` [payable] - Send native token (ETH/BNB/etc.) cross-chain
+The registry's addresses per chain, how a program names each contract there (a namespace, or
+an ABI import bound to the address), and the ABI functions are generated in
+[registry/celer.md](registry/celer.md).
 
 ## Notes
 

package/{sdk/src/skills → skills/sauce-protocols/references}/chainlink-ccip.md

@@ -4,9 +4,14 @@ Cross-Chain Interoperability Protocol by Chainlink. Enterprise-grade cross-chain
 
 ## Category
 
-cross-chain messaging + token transfer | Direction: any-to-any | Chains: Ethereum (1), Arbitrum (42161), Optimism (10), Base (8453), Polygon (137), Arc (5042)
+cross-chain messaging + token transfer | Direction: any-to-any | Chains and addresses: [registry/chainlink-ccip.md](registry/chainlink-ccip.md)
 
-## SauceScript Functions
+## Typed templates for the raw compiler (not for `sauce compile`)
+
+These import the protocol's ABI from `./abis`, the way the registry compiles them with the raw
+compiler; `sauce compile` has no such module. In a program for a chain, name the contract by its
+namespace, or import its ABI from `./protocols/<slug>/<Export>.json` as the registry file at the
+top of this document shows, and write SauceScript's values (`~0n`, not `type(uint256).max`).
 
 ### sendMessage
 
@@ -41,26 +46,11 @@ function main(
 - Requires native token (ETH) as msg.value when `feeToken` is `address(0)`
 - Requires ERC-20 approval to the Router for any tokens in `tokenAmounts`
 
-## Deployed Addresses
-
-| Chain    | Contract | Address                                      |
-| -------- | -------- | -------------------------------------------- |
-| Ethereum | router   | `0x80226fc0Ee2b096224EeAc085Bb9a8cba1146f7D` |
-| Arbitrum | router   | `0x141fa059441E0ca23ce184B6A78bafD2A517DdE8` |
-| Optimism | router   | `0x3206695CaE29952f4b0c22a169725a865bc8Ce0f` |
-| Base     | router   | `0x881e3A65B4d4a04dD529061dd0071cf975F58bCD` |
-| Polygon  | router   | `0x849c5ED5a80F5B408Dd4969b78c2C8fdf0565Bfe` |
-
-## ABI Reference
-
-### CCIPRouterABI
-
-- `ccipSend(uint64 destinationChainSelector, EVM2AnyMessage message) returns (bytes32 messageId)` [payable] - Send cross-chain message and/or tokens. Returns message ID for tracking
-- `getFee(uint64 destinationChainSelector, EVM2AnyMessage message) returns (uint256 fee)` - Estimate fee for a CCIP message before sending (view)
-- `isChainSupported(uint64 chainSelector) returns (bool)` - Check if a destination chain selector is supported (view)
+## Deployments and ABI
 
-EVM2AnyMessage tuple: `(bytes receiver, bytes data, EVMTokenAmount[] tokenAmounts, address feeToken, bytes extraArgs)`
-EVMTokenAmount tuple: `(address token, uint256 amount)`
+The registry's addresses per chain, how a program names each contract there (a namespace, or
+an ABI import bound to the address), and the ABI functions are generated in
+[registry/chainlink-ccip.md](registry/chainlink-ccip.md).
 
 ## Notes
 

package/skills/sauce-protocols/references/chainlink.md

@@ -0,0 +1,47 @@
+# Chainlink
+
+Industry-standard decentralized oracle network providing price feeds, VRF randomness, automation, and cross-chain interoperability (CCIP).
+
+## Category
+
+oracle | Chains and addresses: [registry/chainlink.md](registry/chainlink.md)
+
+## Key Operations
+
+- **getLatestPrice**: Read latest price from a Chainlink price feed aggregator
+
+## Typed templates for the raw compiler (not for `sauce compile`)
+
+These import the protocol's ABI from `./abis`, the way the registry compiles them with the raw
+compiler; `sauce compile` has no such module. In a program for a chain, name the contract by its
+namespace, or import its ABI from `./protocols/<slug>/<Export>.json` as the registry file at the
+top of this document shows, and write SauceScript's values (`~0n`, not `type(uint256).max`).
+
+```typescript
+// Get latest price from feed
+import { AggregatorV3ABI as IAggregatorV3 } from "./abis";
+function main(feedAddress: Address): {
+  roundId: Uint256;
+  answer: Uint256;
+  startedAt: Uint256;
+  updatedAt: Uint256;
+  answeredInRound: Uint256;
+} {
+  const feed = IAggregatorV3.at(feedAddress);
+  return feed.latestRoundData();
+}
+```
+
+## Deployments and ABI
+
+The registry's addresses per chain, how a program names each contract there (a namespace, or
+an ABI import bound to the address), and the ABI functions are generated in
+[registry/chainlink.md](registry/chainlink.md).
+
+## Notes
+
+- Price feeds return answer in int256 with feed-specific decimals (usually 8 for USD pairs)
+- Always check updatedAt timestamp for staleness - stale prices can cause issues
+- Feed Registry is Ethereum-only; on L2s, use individual feed addresses directly
+- VRF provides verifiable randomness for on-chain applications
+- Common feed addresses vary by chain - check Chainlink docs for specific chain deployments