Smart Contract Integrations

Integrate syrupUSDC & syrupUSDT via smart contracts. Lenders (your smart contracts) must deposit through SyrupRouter with authorization handled by PoolPermissionManager.

Step-by-step

Deposit:

1. Determine lender authorization (onchain via PoolPermissionManager)

2. Retrieve authorization signature (from Maple)

3. Execute the deposit (authorize-and-deposit or deposit)

Withdraw:

1. Retrieve lender balance (shares)

2. Calculate shares to redeem (full balance or convertToExitShares for partial)

3. Execute the withdrawal (requestRedeem)

Overview

1. Syrup Protocol Overview

Smart contracts integrating with syrupUSDC & syrupUSDT act as lenders and must interact via SyrupRouter. Authorization is enforced by PoolPermissionManager. First-time deposits require an authorization signature; subsequent deposits can call deposit directly once authorized.

2. SyrupRouter Interface

Below are the primary functions exposed by SyrupRouter for integrators. These mirror the onchain interface and are stable entry points for deposits:

// Events
event DepositData(address indexed owner, uint256 amount, bytes32 depositData);

// Views
function asset() external view returns (address);
function pool() external view returns (address);
function poolManager() external view returns (address);
function poolPermissionManager() external view returns (address);
function nonces(address owner) external view returns (uint256);

// First-time (with authorization signature)
function authorizeAndDeposit(
    uint256 bitmap,
    uint256 deadline,
    uint8   v,
    bytes32 r,
    bytes32 s,
    uint256 amount,
    bytes32 depositData
) external returns (uint256 shares);

// First-time with ERC-2612 token permit
function authorizeAndDepositWithPermit(
    uint256 bitmap,
    uint256 authDeadline,
    uint8   authV,
    bytes32 authR,
    bytes32 authS,
    uint256 amount,
    bytes32 depositData,
    uint256 permitDeadline,
    uint8   permitV,
    bytes32 permitR,
    bytes32 permitS
) external returns (uint256 shares);

// Subsequent deposits (already authorized)
function deposit(uint256 amount, bytes32 depositData) external returns (uint256 shares);
function depositWithPermit(
    uint256 amount,
    uint256 deadline,
    uint8   v,
    bytes32 r,
    bytes32 s,
    bytes32 depositData
) external returns (uint256 shares);

Notes for implementers:

• Authorization signature: For first-time deposits, Maple (a permission admin) provides an ECDSA signature authorizing the lender’s bitmap permissions. The signature digest includes chainId, the SyrupRouter address, the owner (msg.sender), a nonce, the bitmap, and deadline. Your smart contract should pass this signature through to authorizeAndDeposit/authorizeAndDepositWithPermit.

• Permissions: The router enforces PoolPermissionManager.hasPermission(poolManager, owner, "P:deposit"). Your address must be permissioned (via allowlist or bitmaps) before deposits succeed.

• Deposit metadata: depositData is a bytes32 field emitted via DepositData for off-chain correlation (e.g., internal IDs). Use a pre-hashed value if longer than 32 bytes.

• Gas optimization: Prefer depositWithPermit where the asset supports EIP‑2612 to avoid a separate approval step.

3. Syrup Addresses

All ABIs are available on GitHub: Maple JS (ABIs)

Mainnet

syrupUSDC

Contract	Address
PoolV2	0x80ac24aA929eaF5013f6436cdA2a7ba190f5Cc0b
SyrupRouter	0x134cCaaA4F1e4552eC8aEcb9E4A2360dDcF8df76
WithdrawalManagerQueue	0x1bc47a0Dd0FdaB96E9eF982fdf1F34DC6207cfE3
USDC	0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48

syrupUSDT

Contract	Address
PoolV2	0x356B8d89c1e1239Cbbb9dE4815c39A1474d5BA7D
SyrupRouter	0xF007476Bb27430795138C511F18F821e8D1e5Ee2
WithdrawalManagerQueue	0x86eBDf902d800F2a82038290B6DBb2A5eE29eB8C
USDT	0xdAC17F958D2ee523a2206206994597C13D831ec7

Shared (Global)

Contract	Address
PoolPermissionManager	0xBe10aDcE8B6E3E02Db384E7FaDA5395DD113D8b3

Sepolia

3. Testing on Sepolia

Contact [email protected] for test USDC/USDT and access. See the Sepolia tab above for addresses.

---

Deposit

1. Determine Lender Authorization (onchain)

Use PoolPermissionManager to verify lender authorization for a specific pool. You can derive the manager onchain from the Pool.

interface IPool { function manager() external view returns (address); }

interface IPoolManager { function poolPermissionManager() external view returns (address); }

interface IPoolPermissionManager {
    function hasPermission(address poolManager, address lender, bytes32 functionId) external view returns (bool);

    // Optional introspection helpers
    function lenderBitmaps(address lender) external view returns (uint256);
    function poolBitmaps(address poolManager, bytes32 functionId) external view returns (uint256);
}

function getPoolPermissionManager(address pool) internal view returns (address) {
    address manager = IPool(pool).manager();
    return IPoolManager(manager).poolPermissionManager();
}

function isAuthorizedToDeposit(address pool, address lender) internal view returns (bool) {
    address manager = IPool(pool).manager();
    address ppm     = IPoolManager(manager).poolPermissionManager();
    return IPoolPermissionManager(ppm).hasPermission(manager, lender, "P:deposit");
}

Onchain permission checks are equivalent to a bitmap AND comparison. A lender is authorized for a function if all required bits in the pool’s bitmap are present in the lender’s bitmap:

• Condition: (poolBitmap & lenderBitmap) == poolBitmap

Example (optional introspection, prefer hasPermission in production):

function isAuthorizedBitmaps(address pool, address lender) internal view returns (bool) {
    address manager = IPool(pool).manager();
    address ppm     = IPoolManager(manager).poolPermissionManager();
    // Per-function pool bitmap for deposits
    uint256 poolBitmap   = IPoolPermissionManager(ppm).poolBitmaps(manager, "P:deposit");
    uint256 lenderBitmap = IPoolPermissionManager(ppm).lenderBitmaps(lender);
    return (poolBitmap & lenderBitmap) == poolBitmap;
}

Mainnet PoolPermissionManager (for reference): 0xBe10aDcE8B6E3E02Db384E7FaDA5395DD113D8b3

2. Retrieve Authorization Signature

If not authorized, contact [email protected] to obtain:

• bitmap, deadline, v, r, s

• depositData - conventionally "0:<integrator-name>", encoded as bytes32. Keep within 32 bytes when hex-encoded.

3. Execute the Deposit

Minimal SC calls (lender must hold sufficient USDC/USDT):

interface IERC20 { function approve(address spender, uint256 amount) external returns (bool); }
interface ISyrupRouter {
    function deposit(uint256 amount, bytes32 depositData) external returns (uint256 shares);
    function authorizeAndDeposit(
        uint256 bitmap,
        uint256 deadline,
        uint8   v,
        bytes32 r,
        bytes32 s,
        uint256 amount,
        bytes32 depositData
    ) external returns (uint256 shares);
}

function depositAuthorized(
    address asset,
    address router,
    uint256 amount,
    bytes32 depositData
) external {
    IERC20(asset).approve(router, amount);
    ISyrupRouter(router).deposit(amount, depositData);
}

function authorizeAndDeposit(
    address asset,
    address router,
    uint256 amount,
    bytes32 depositData,
    uint256 bitmap,
    uint256 deadline,
    uint8   v,
    bytes32 r,
    bytes32 s
) external {
    IERC20(asset).approve(router, amount);
    ISyrupRouter(router).authorizeAndDeposit(bitmap, deadline, v, r, s, amount, depositData);
}

Deposit data

• Replace 0:<integrator-name> with your integrator identifier (e.g. 0:acme-protocol).

• Maple will provide the final depositData for production.

• Must be passed as bytes32 (32-byte hex).

---

Withdraw

1. Retrieve Lender’s Balance

interface IPool {
    function balanceOf(address account) external view returns (uint256);
    function convertToExitAssets(uint256 shares) external view returns (uint256);
}

function getLenderPosition(address pool, address lender) external view returns (uint256 shares, uint256 exitAssets) {
    shares     = IPool(pool).balanceOf(lender);
    exitAssets = IPool(pool).convertToExitAssets(shares);
}

2. Calculate Shares to Redeem

Use full balance for full redemption, or compute shares for a specific asset amount.

interface IPool { function convertToExitShares(uint256 assets) external view returns (uint256); }

function sharesForAssets(address pool, uint256 assetAmount) external view returns (uint256) {
    return IPool(pool).convertToExitShares(assetAmount);
}

3. Execute the Withdrawal

Submit a withdrawal request to the pool.

interface IPool { function requestRedeem(uint256 shares, address receiver) external returns (uint256); }

function requestWithdrawal(address pool, uint256 shares, address receiver) external {
    IPool(pool).requestRedeem(shares, receiver);
}

Withdrawals are processed automatically by Maple. If there is sufficient liquidity in the pool, the withdrawal will be processed within a few minutes. Expected processing time is typically less than 2 days, but it can take up to 30 days depending on available liquidity.

---

Edge Cases

• Not authorized → use authorizeAndDeposit with signature

• Insufficient allowance → call approve(router, amount) before depositing

---

FAQ

Why must deposits go through SyrupRouter?

Authorization and routing are enforced via `SyrupRouter` and `PoolPermissionManager`. This ensures only authorized lenders can deposit.

What is depositData and who provides it?

`depositData` is provided by Maple. It typically follows `0:` and your company name. It must be provided as a `bytes32` value (32-byte hex).

How do I verify lender authorization onchain?

Read lenderBitmaps(lender) and poolBitmaps(pool) in PoolPermissionManager and check (lenderBitmap ^ poolBitmap) == poolBitmap.

Do I need authorization for smart contract integration?

Yes, authorization is required for all Syrup deposits. Syrup protocol is built by Maple, which uses a permissioning system for institutional-grade security.

Authorization Process

1. Contact us at [email protected] for eligibility verification

2. Receive authorization signature parameters

3. Use authorizeAndDeposit or authorizeAndDepositWithPermit for first deposit

4. Subsequent deposits only need deposit or depositWithPermit

Once authorized, the permission persists across all Syrup pools and future deposits.

How do withdrawals work?

Withdrawals follow a queue-based system:

1. Request: Call requestRedeem() to enter the withdrawal queue

2. Queue Position: Withdrawals are processed first-in, first-out (FIFO)

3. Processing: When pool liquidity is available, withdrawals are automatically processed

4. Completion: Assets are sent directly to the wallet (no additional transaction required)

Timeline

• Expected processing time is typically less than 2 days

• During low liquidity periods, it may take up to 30 days

• No penalties for withdrawing, but yield stops accumulating once withdrawal is requested

How long do withdrawals take?

syrupUSDC & syrupUSDT normally have instant liquidity, but in rare cases withdrawals can take around 24h with the maximum possible time being 30 days. You can see the available funds to withdraw in the Liquidity section of the Details page.

How can I get the APY data for syrupUSDC or syrupUSDT?

Querying the GraphQL API is the simplest way to get APY data for syrupUSDC or syrupUSDT into your app.

Example request

{
  poolV2(id: "0x80ac24aa929eaf5013f6436cda2a7ba190f5cc0b") {
    name
    weeklyApy
    monthlyApy
  }
  syrupGlobals {
    dripsYieldBoost
  }
}

This returns

{
  "data": {
    "poolV2": {
      "name": "Syrup USDC",
      "weeklyApy": "69937809610000000000000000000",
      "monthlyApy": "67212806350000000000000000000"
    },
    "syrupGlobals": {
      "apy": "69731920498003078965054825961",
      "dripsYieldBoost": "22000"
    }
  }
}

In the example above, the monthly base APY is 6.72% with the Drips rewards adding an extra 2.2% on top.

How can I get the price received on redemption for syrupUSDC or syrupUSDT?

syrupUSDC and syrupUSDT are redeemed at the smart contract exchange rate at the point of processing the withdrawal, incurring no slippage.

You can get the spot exchange rate for syrupUSDC to USDC or syrupUSDT to USDT by querying the GraphQL API.

Example request

{
  account(id: "0xyourwallet") {
    poolV2Positions {
      pool {
        asset {
          symbol
          decimals
        }
        id
        name
      }
      lendingBalance
      totalShares
    }
  }
}

This returns

{
  "data": {
    "account": {
      "poolV2Positions": [
        {
          "pool": {
            "asset": {
              "symbol": "USDC",
              "decimals": 6
            },
            "id": "0x80ac24aa929eaf5013f6436cda2a7ba190f5cc0b",
            "name": "Syrup USDC"
          },
          "lendingBalance": "3102053352414",
          "totalShares": "2742550894631"
        }
      ]
    }
  }
}

The ratio of lendingBalance / totalShares is the spot exchange rate.