R5 Network
WebsiteR5 LabsGitHub
  • Getting Started
    • Hello & Welcome!
  • About R5
    • Overview
    • R5 Components
    • Consensus Mechanism
    • zkNet (Privacy)
  • R5 Coin
  • R5 Tokenomics
  • Tutorials & Guides
    • Connect & Use R5
      • R5 Desktop Wallet
      • MetaMask
      • Rabby Wallet
      • Coinbase Wallet
    • zkNet Web Wallet
    • R5 Desktop Wallet
      • Interface Overview
      • Send a Transaction
      • Receive a Transaction
      • Backup Your Wallet
      • Retrieve Your Private Key
    • How To: Deploy a Node
    • How To: Mine R5
    • How To: GPU Mine R5
    • How To: Build R5 From Source
    • How To: Connect Local Nodes
  • For Developers
    • R5 SDK
      • R5 Relayer
      • R5 Console
      • JS Console
      • CLI Wallet
      • SCdev
      • SSL Proxy
    • Hardware Requirements
    • R5 Testnet
    • R5 Devnet
    • Local Networks
    • JSON-RPC API
      • admin
      • debug
      • ethash
      • miner
      • net
      • r5 (eth)
      • rpc
      • txpool
      • web3
    • Indexer API
    • zkNet API
    • DeFi Engine SDK
      • Overview
      • Price Fetching
      • Trade Entity
      • Smart Contract Addresses
    • Node Configuration
    • Ethash-R5
    • Smart Contracts
    • Wrapped R5 (Native)
    • Tokens & NFTs
  • Bug Bounty Program
  • Resources
    • Website
    • R5 Labs
    • R5 Labs GitHub
Powered by GitBook
On this page
  • Factory
  • Router
  • Deploying Your Own Router Contract
  1. For Developers
  2. DeFi Engine SDK

Smart Contract Addresses

Factory

Mainnet

0xeC1C8476c7b38014B07ce02C080eF38D2166F141

Router

Mainnet

0x8D36f6Ef098263427e6ce9Db7a6bC518727002b5

Deploying Your Own Router Contract

If you prefer, you can deploy your own router contract and still leverage the R5 DeFi Engine SDK and Factory. To that end, you can use the init_code_hash below:

0x544a6894c2418600f8c457fe5d4135814cf3fa97f6faebe3e5f68ef34f1b02d8
PreviousTrade EntityNextNode Configuration

Last updated 1 day ago