SYRUPUSDC: who controls it?

The control finding

Maple undercollateralised credit, wrapped. Yield is compensation for borrower default risk; Maple lenders took ~80% losses in the 2022 Orthogonal default. Rejected including via this wrapper.

Holder’s position

A syrupUSDC holder holds a wrapped share of a Maple private-credit lending pool funded in USDC, collateralized under Maple's own custody and margining process. The yield compensates for borrower default risk, not for a segregated cash claim; Maple lenders took roughly 80% losses in the 2022 Orthogonal default.

Redemption or exit

Redemption runs through Maple's pool withdrawal mechanics, subject to pool liquidity and lockup terms. USDC redemption itself still depends on Circle eligibility or secondary-market exit.

Dependencies an advisor should record

• Circle's freeze and administrator power over underlying USDC
• Maple Finance and pool delegate lending decisions
• Borrower credit and default risk
• Pool withdrawal liquidity and lockup terms
• Wrapper contract mechanics
• Chain-specific deployment

Why this distinction matters

Ketju rejects Maple credit exposure, including through this wrapper. Wrapping the pool share as syrupUSDC changes how the risk is packaged, not the underlying credit risk itself.

A named organization or administrator controls issuance, transfers, reserves, redemption, or address restrictions. That finding can coexist with a sound reserve, useful product, or appropriate client role. The grade prevents the on-chain wrapper from being mistaken for the absence of an administrator.

Questions before use

1. Does the exact contract and chain match the instrument reviewed here?
2. Which party can mint, burn, pause, upgrade, block, or redeem?
3. Does the client have direct redemption access or only secondary liquidity?
4. What protocol, bridge, wallet, and custodian dependencies are added?
5. Which event would force review or exit?