Contracts
All relevant contracts for the SherpoEarn yield vault — Expand contract title for more info
Sherpa Deployments
SherpaVault / Staked Sherpa USD
shUSD
A multi-chain yield vault that issues interest-bearing ERC20 share tokens (shUSD) representing pro-rata ownership of the underlying USDC asset pool. The contract manages round-based deposit/withdrawal cycles with synchronized pricing across all chains, maintaining a critical accountingSupply variable that tracks logical share ownership per chain (immune to CCIP bridge fluctuations) to ensure accurate global shUSD price calculations. Primary chain deployments calculate global prices by aggregating state from all chains, while secondary chains apply the propagated price during their cycle rolls.
SherpaUSD / USDC Wrapper
sherpaUSD
A 1:1 USDC wrapper token that implements epoch-based withdrawal mechanics, providing immediate liquidity for deposits while enforcing a one-epoch delay for withdrawals to ensure the vault has adequate liquidity for operations. The wrapper serves as the intermediary between user USDC deposits and the SherpaVault contract, enabling permissioned minting/burning operations for yield distribution adjustments and cross-chain liquidity rebalancing through operator-controlled ownerMint()and ownerBurn() functions.
CCIP Pools
Chainlink's burn-and-mint token pool contract that enables cross-chain transfers of shUSD by burning tokens on the source chain and minting equivalent amounts on the destination chain, while enforcing rate limits and validating against the Risk Management Network (RMN). Each pool is configured with remote chain mappings via applyChainUpdates() and must be registered in the TokenAdminRegistry and authorized in the vault's ccipPools mapping to execute mint/burn operations. The pool interacts with the CCIP Router's OnRamp and OffRamp contracts to coordinate token transfers as part of cross-chain messages.
Third Party Deployments
CCIP Router
Chainlink's universal entry point contract for cross-chain messaging that users call via ccipSend() to initiate token transfers or arbitrary message passing between supported chains. The Router directs outbound messages to chain-specific OnRamp contracts (which handle token pool interactions and emit events for the DON) and receives inbound messages from OffRamp contracts (which validate and deliver messages from the DON). While not deployed by Sherpa, the Router is a critical dependency that coordinates the entire CCIP message lifecycle, enabling the vault's burn-and-mint bridging architecture.
Last updated