Svim
  • Unlock RWA Potentials
    • Introduction to Svim Finance
      • Mission statement
      • Our team
      • Key glossary
      • FAQ
    • Market Overview
      • Problem for Web2 asset owners
      • Problem for Web3 investors
      • Our solution
      • Market size
  • Getting Started
    • Svim business model
      • Yield generating assets
      • Yield seeking capital
      • Phased approach
      • Risk management
    • Protocol participants
      • Owners
      • Administrator or Managers
      • Borrowers
      • Investors
      • Strategic partners
      • Service providers
      • Regulators
      • Community
    • Asset onboarding
    • Investor onboarding
    • Liquidity pool features
      • Pool creation
      • Pool parameters
      • Liquidity providing
      • Payment
      • Default & collection
      • Collateral liquidation
    • Points Program
    • Tokenomics
      • Our token
      • Utilities
      • Allocation
      • Staking
  • Technical Documents
    • Protocol Architecture
    • Asset Onboarding
    • Security
    • Smart Contract
  • Legal
    • Risk warning
    • Markets not served
    • Terms of service
    • Privacy policy
    • Email consent policy
  • Frequently Asked Questions
    • Stay connected
Powered by GitBook
On this page
  • Support Chains and Assets
  • Contract Address
  1. Technical Documents

Smart Contract

PreviousSecurityNextRisk warning

Last updated 7 months ago

Support Chains and Assets

Our platform currently supports USDC on multiple blockchain networks, specifically Ethereum and Arbitrum, with plans to expand to more chains in the future. Each supported chain will have its own designated USDC contract address, ensuring seamless integration and compatibility with the native assets of each network.

Chain
USDC

Ethereum

Arbitrum

Contract Address

Functionality
Ethereum
Aribtrum

Access Control

Create Loan

0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48
0xaf88d065e77c8cC2239327C5EDb3A432268e5831
0x21d63c1c802b22d2d632bca96bf27e4cd3712d77
0x919d795cc58526d790e2df5cee5e0a0602722e95
0xcce3a9d318d30631a99a3ae54fae73fb204779ff
0xd3fe16a05de254a5b212f9761c0103ddb1d09a42