[Asset Technical Assessment] syrupUSDC on Aave V3 Monad
Author: Aave Labs
Date: 2026-06-30
Summary
Technical assessment of syrupUSDC (Syrup USDC) for onboarding to Aave V3 Monad, following the Technical Asset Listing Framework.
Overall result: 
MEDIUM
syrupUSDC on Monad is a correctly wired Chainlink burn-and-mint representation of the Ethereum Maple vault token, and the bridge plumbing itself is sound (canonical pools, mirrored rate limits, and a fully collateralised Ethereum lockbox). syrupUSDC can be priced on Monad through a Correlated-Asset Price Oracle (CAPO) composition: the syrupUSDC/USDC exchange-rate feed combined with the Chainlink USDC/USD feed, the same design used to price the canonical token on Ethereum. Mint is uncapped at the token level but bounded in practice by the single bridge’s mirrored rate limits and governed by a Safe multisig with a visible security configuration, without an on-chain timelock. The conditions that hold this at Medium are the multisig-without-timelock control of mint and bridge configuration, the CAPO composition’s reliance on off-Monad vault value, and short bridge admin delays.
Listing Recommendation
From a technical standpoint, syrupUSDC on Aave V3 Monad is eligible for listing, with conditions to surface. Pricing uses a Correlated-Asset Price Oracle (CAPO) composition of the syrupUSDC/USDC exchange-rate feed and the Chainlink USDC/USD feed. The mint and bridge authorities are governed by a Safe multisig with a visible security configuration but without an on-chain timelock; migrating these behind a timelock is a recommended hardening to revisit as exposure grows, not a blocker. The absence of a local liquidation path is not treated as a blocker here, but should be documented and resolved as the market develops.
Asset under review
| Field | Value |
|---|---|
| Asset | Syrup USDC (syrupUSDC) |
| Target chain | Monad (chain ID 143) |
| Target market | Aave V3 Monad |
| Token contract | 0xaB6e5a0C3799d020c790D34F7B2C02639e238AF7 |
| Native to target chain? | No. The Monad token is a bridged representation minted by a Chainlink burn-and-mint token pool, with the canonical token locked in a lockbox on Ethereum. |
| AAcA classification | Yield-bearing (Group 3) on the home chain; a non-yield-bearing wrapped representation on Monad |
syrupUSDC is Maple Finance’s permissionless yield-bearing dollar: depositing USDC into the Maple vault on Ethereum mints syrupUSDC, an ERC-4626 share whose USDC value rises as the vault earns lending yield. The token proposed for Monad is not that vault, but a separate Chainlink representation minted on Monad when canonical syrupUSDC is locked on Ethereum and burned when it is released. The Monad token carries the same dollar claim but exposes none of the vault’s yield machinery locally.
0. Pre-screening
syrupUSDC is deployed and verified on Monad at 0xaB6e5a0C…38AF7, created roughly five weeks before review, and its runtime bytecode is the canonical Chainlink burn-and-mint token implementation. It is an established asset that is not in any non-approved or sanctioned category, and the canonical token is already used as Aave collateral on Ethereum, where it is priced as USDC/USD times the vault exchange rate wrapped in a CAPO adapter. No Monad listing exists yet.
Rating: 
GOOD
1. ERC20 Compliance
The Monad token is the canonical Chainlink burn-and-mint ERC20 with 6 decimals: transfer() and transferFrom() return a boolean, with no fee on transfer, no rebasing, no ERC777 or ERC1363 hooks, and no flash mint. Smart contracts can hold and transfer it without restriction, as the only allowlist sits on the bridge pool and is disabled, not on the token.
Rating: GOOD
2. Oracle
syrupUSDC can be priced on Monad through a Correlated-Asset Price Oracle (CAPO) composition: a syrupUSDC/USDC exchange-rate feed combined with the Chainlink USDC/USD feed published on Monad, the same design used to price the canonical token on Ethereum (USDC/USD times the vault rate wrapped in a CAPO adapter). This composition does not depend on the bridged token exposing its own exchange rate (see Section 4), since the rate is supplied by the feed rather than read from the token. The residual considerations are that the composition depends on a chain of feeds, including the off-Monad vault value, and that syrupUSDC currently has negligible on-chain liquidity on Monad.
Rating: MEDIUM → syrupUSDC is priceable through a CAPO composition (the syrupUSDC/USDC exchange rate plus USDC/USD) and the off-Monad vault value.
3. Access Control
The token uses standard OpenZeppelin AccessControl: the bridge pool holds the mint and burn roles, and the default admin role can grant those roles. Privileged control is held by a single Gnosis Safe (a 4-of-8 multisig) with a visible security configuration, without an on-chain timelock delaying privileged changes. The token carries no supply cap (maxSupply() returns 0, which in this implementation means no token-level ceiling), so the effective bound on minting is the single bridge’s mirrored rate limits rather than a token cap. The token is non-upgradeable and immutable, with all EIP-1967 proxy slots reading zero, has no pause or blacklist function, and the deployer externally owned account (EOA) renounced its admin after deployment.
Rating: MEDIUM → mint is uncapped at the token level but bounded by the single bridge’s mirrored rate limits, and privileged control sits with a Safe multisig with a visible security configuration but no on-chain timelock.
4. Exchange Rate and Yield
The Monad token is not an ERC-4626 vault and exposes no exchange rate: asset(), convertToAssets(), and totalAssets() all revert, so the vault rate (the ratio of vault assets to shares, which on the home chain rises with yield) is not readable from the bridged token itself. The token does not rebase and does not appreciate visibly, so its valuation on Monad is supplied by the external CAPO composition described in Section 2 (the syrupUSDC/USDC exchange-rate feed combined with USDC/USD) rather than read from the token. There is no local redemption path: the token has no redeem or withdraw function, and the only exit is to bridge back to Ethereum, an asynchronous and bridge-dependent route. The absence of a local liquidation path is documented as a known issue rather than a blocker.
Rating: MEDIUM → the bridged token exposes no exchange rate of its own, so valuation relies on the external CAPO composition (Section 2), and there is no local redemption path or observable Monad DEX liquidity.
5. Token Architecture
syrupUSDC on Monad is a single immutable deployment with no duplicate or legacy entry point to the same supply, and supply moves only through the bridge pool’s mint and burn on verified messages, with standard Transfer events emitted. The implementation contains no tx.origin authorization and no delegatecall, and all privileged functions (mint, burn, role changes) are access-controlled. The architecture is clean; supply carries no token-level cap and is bounded by the bridge rate limits, and the deployment is effectively unused at about 193.9 tokens at this early stage.
Rating: MEDIUM → architecturally clean and immutable, with no token-level supply cap (bounded by the bridge rate limits).
6. Bridge and Cross-Chain Risk
The bridge uses Chainlink’s Cross-Chain Interoperability Protocol (CCIP): the Ethereum side locks the canonical token in a lockbox and the Monad side mints and burns a representation, with both routes wired reciprocally, rate limits enabled and mirrored on both ends, and the Ethereum lockbox holding canonical syrupUSDC many times over the Monad claim, so backing holds. The bridge admin roles (pool owner, router owner, and the Ethereum lockbox owner) are Chainlink-operated timelocks with no EOA in the control chain, but the bridge admin delay is 3 hours currently, which is less than the 24-hour bar.
Rating: MEDIUM → the bridge admin delay is 3 hours, and the design uses a single bridge provider.
7. Audit and Security History
The deployed Monad token is the canonical Chainlink burn-and-mint implementation, with runtime bytecode byte-identical to the audited Chainlink Cross-Chain Token, and it is immutable, so no implementation rotation is possible. The CCIP token pools, verifier, and router are canonical Chainlink contracts, with the token pool layer covered by the Cyfrin CodeHawks CCIP competitive audit and the wider stack under Chainlink’s continuous audits. The home-chain Maple vault and its cross-chain receiver carry an extensive audit history (Trail of Bits, Spearbit, Three Sigma, 0xMacro, Sherlock, Dedaub, and Sigma Prime), and the Maple Governor timelock that holds the token admin was audited by Sherlock and 0xMacro. Maple runs a public bug bounty program, and the only residual is that the Monad deployment of the Maple timelock is not source-verified on-chain, tracked as an issuer item.
Rating: GOOD
8. Dependencies
The asset depends on the Ethereum Maple vault (the source of all value and yield), Chainlink CCIP (the only bridge path), the Ethereum lockbox (collateral backing), the Maple timelock with its controlling Safe (token mint governance), and the Chainlink timelocks (bridge governance). These dependencies are reputable, audited, and governed on-chain, with no EOA admin on any critical dependency, and token-admin and bridge-config changes both route through on-chain visible timelocks. The defining limitation is that the value-setting dependency, the vault and its rate, lives entirely off Monad; the CAPO composition surfaces the vault rate through the syrupUSDC/USDC feed, but the underlying vault performance itself is not observable on Monad.
Rating: MEDIUM → dependencies are reputable and audited, but the value-defining vault and its performance live entirely off Monad, with valuation dependent on the off-chain vault rate surfaced through the syrupUSDC/USDC feed.
9. Summary
Findings table
| Area | Key finding | Rating |
|---|---|---|
| 0. Pre-screening | Canonical Chainlink burn-and-mint token at 0xaB6e5a0C…38AF7, immutable, byte-identical to the audited implementation; freshly seeded deployment at about 193.9 tokens. |
Good |
| 1. ERC20 | Canonical Chainlink burn-and-mint ERC20, 6 decimals; returns bool, no fee on transfer, no rebase, no hooks, no flash mint, no transfer restriction on the token. | Good |
| 2. Oracle | Priceable via a CAPO composition (syrupUSDC/USDC exchange-rate feed plus Chainlink USDC/USD), the same design as on Ethereum; residual reliance on a chain of feeds including off-Monad vault value and negligible on-chain syrupUSDC liquidity. | Medium |
| 3. Access control | No token-level supply cap (maxSupply() = 0); mint bounded by the single bridge’s mirrored rate limits; privileged control with a 4-of-8 Safe multisig with a visible security configuration, no on-chain timelock; immutable, no pause or blacklist. |
Medium |
| 4. Exchange rate / yield | Bridged token exposes no exchange rate (asset(), convertToAssets(), totalAssets() revert); valuation supplied by the external CAPO composition (Section 2); no local redemption and no observable Monad DEX liquidity (documented, not a blocker). |
Medium |
| 5. Token architecture | Single immutable deployment; no tx.origin, no delegatecall, no duplicate supply path; uncapped supply and an effectively empty deployment. |
Medium |
| 6. Bridge and cross-chain | Burn-and-mint over CCIP; lockbox fully collateralised, routes reciprocal, rate limits mirrored; 3-hour admin delay, single bridge provider. | Medium |
| 7. Audit and security | Token and pools are the audited canonical Chainlink stack with bytecode identity confirmed; immutable; Maple vault and Governor timelock independently audited. | Good |
| 8. Dependencies | Depends on the Ethereum vault, CCIP, the lockbox, and the Maple and Chainlink governance; reputable and audited, but the value-defining vault and its performance live off Monad, surfaced through the syrupUSDC/USDC feed. | Medium |
Disclaimer
Aave Labs has no formal or informal affiliation with Maple Finance or the syrupUSDC issuer beyond this technical assessment. Aave Labs has not been compensated by Maple Finance or any related party in connection with this work.
Copyright
Copyright and related rights waived via CC0.