Swap and supply as an actions document

​

Prerequisites

​

Document

{
  "version": 1,
  "actions": [
    { "type": "argument", "name": "wethIn" },
    {
      "type": "uniswapV3Swap",
      "tokenIn": "WETH",
      "tokenOut": "USDC",
      "factory": "UniswapV3.Factory",
      "fee": 500,
      "amountOutMin": "2000000000",
      "recipient": "pot",
      "saveOutputAs": "usdc"
    },
    { "type": "approve", "token": "USDC", "spender": "AaveV3.Pool", "amountRef": "usdc" },
    {
      "type": "aaveV3Supply",
      "pool": "AaveV3.Pool",
      "token": "USDC",
      "onBehalfOf": "pot",
      "amountRef": "usdc"
    }
  ]
}

// actions-swap-supply.json, lowered for base (chain 8453)
import { uniswapV3 } from "@sauce/router";

function main(a_wethIn: Uint256): void {
  let t_out0 = a_wethIn;
  const pool0 = UniswapV3.Factory.getPool(WETH, USDC, 500);
  require(pool0 != 0, "actions[1]: no pool under that key");
  const amt1 = uniswapV3(pool0, WETH, USDC, t_out0, 0, 2000000000, pot);
  let v_usdc = amt1;
...
  IAaveV3Pool.at(AaveV3.Pool).supply(USDC, v_usdc, pot, 0);
}

​

How it works

• The argument action becomes main’s parameter a_wethIn, so one compiled document takes any amount through --args. amountOutMin cannot be an argument: it is a string fixed in the document, so 2,000 USDC is the minimum for every wethIn. Set it again from a quote when you change the amount.
• The pool is given by key (factory + fee). The program reads it from UniswapV3.Factory.getPool while it runs and reverts with actions[1]: no pool under that key if there is none. The swap is a call to @sauce/router’s uniswapV3, the same function a SauceScript program imports.
• saveOutputAs: "usdc" names the swap’s output, and both the approval and the supply spend exactly that amount through amountRef. The approval is lowered to an inline checked approve that resets a non-zero allowance first.
• The document cannot do what the SauceScript version does: quote two pools and choose one at run time. The actions format has no quote, comparison or condition action; each swap names its pool when the document is written.

​

Run the example

sauce actions actions-swap-supply.json --chain base

sauce compile actions-swap-supply.json --chain base

sauce simulate actions-swap-supply.json --chain base --owner <your-address> \
  --assume-balance WETH:1 --args 1000000000000000000

sauce run actions-swap-supply.json --chain base --wallet <name> \
  --fund WETH:1 --args 1000000000000000000

sauce tx actions-swap-supply.json --chain base --owner <your-address> \
  --fund WETH:1 --args 1000000000000000000

​

Simulation result

The cook succeeds from 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266: gas used 367218 for the cook, after the Pot's deploy (1. below), returns 0x
Left in the Pot, not in the owner's wallet:
  2316.836894 aBasUSDC
...
What moved, in order:
...
  [3] 0xd0b5…F224        -> Pot                   2316.836895 USDC
  [4] Pot                -> 0xd0b5…F224           1 WETH
  [5] Pot                -> aBasUSDC 0x4e65…c0AB  2316.836895 USDC
  [6] mint               -> Pot                   2316.836894 aBasUSDC

​

Next steps

• Quote two pools, swap on the better one, supply to Aave: the same flow in SauceScript, choosing the pool at run time.
• Low-level calls: raw calldata and a program’s own ABI, for what neither the actions format nor the registry covers.
• sauce actions, sauce simulate, Protocols reference.