Matmo
  • Ⓜ️Matmo
  • πŸš€Mainnet
  • πŸͺ™Token
  • πŸ›‘οΈAudit
  • 🎁Presale
    • πŸ’°Wallet and Buy
    • πŸ“ˆToken price
    • πŸ’ΈBonuses and Discounts
    • πŸ‘«Referral program
    • πŸ€VCS & Angel Investors
  • 🎦Marketing
  • πŸ”’Economics
  • πŸ“»RoadMap
  • πŸ“šDOCS
    • πŸ•ΈοΈWeb3
    • πŸ“’Concepts
    • ↗️Account
    • βš’οΈBlocks
    • πŸ”€Transactions
    • ♨️Gas and Transaction Fees
    • βš–οΈStaking
    • πŸ‘ΊNFT
    • 🏦Swap
    • πŸ•Governance
    • πŸŒ‰Bridging assets
    • πŸ•ŽRun a Validator
      • πŸ“³Run a Fullnode
    • ⛓️API
    • πŸ“€SDK
    • πŸ‘ΎValidator
  • πŸ«‚Team
  • πŸ‘«Community
    • Twitter
    • Telegram Channel
    • Telegram group I
    • Telegram group II
    • Telegram group III
    • Medium
Powered by GitBook
On this page
  • Introduce
  • Default bridges
  1. DOCS

Bridging assets

PreviousGovernanceNextRun a Validator

Last updated 10 months ago

Introduce

Matmo's bridge is an important part of cross-chain in the ecology. It is a bridge linking other chains, supporting cross-chain transfer of and assets, and bridging contracts. This makes matmo different from all main chains. Matmo is the representative of the next-generation chain .

Developers are free to build their own #bridges for any token. However, we provide default bridges (one for ETH and one for BSC).

Default bridges

You can get default bridges' addresses using the matmo_getBridgeContracts endpoint or getDefaultBridgeAddresses method of Provider in our (similar methods are available in the other SDKs).

Matmo provides and methods to undertake resources (including NFT SDK), and the content can be viewed in the corresponding documents.

πŸ“š
πŸŒ‰
applications
API
SDK
Javascript SDK