Reveel Protocol v2 Documentation
  • πŸš€Reveel Protocol - Introduction
  • 🏁Getting Started
    • Creating a Revenue Path
    • Adding Revenue Path Tiers
    • Viewing your Revenue Path
    • Withdrawing Funds
    • Revenue Path Dashboard
    • Updating your Revenue Path
    • Selecting a Network
  • βš—οΈProtocol Concepts
    • Tiers
    • Mutable Revenue Paths
    • Path Manager
    • Platform Fee
    • Meta Transactions
  • πŸ§‘β€πŸŒΎSDK
    • Overview
    • 1.0 React Hooks
    • 2.0 Async Javascript
    • 3.0 Data API
  • NFT Marketplace Integrations
    • Lens
    • Zora
    • Foundation
    • OpenSea
    • Manifold
    • Decent
    • Vol FM
  • ♾️Revenue Share Use Cases
    • Recoup Advance
    • Primary vs. Secondary Splits
    • Revenue Milestone
    • Cap Earnings
Powered by GitBook
On this page
  1. Getting Started

Selecting a Network

How to deploy your Revenue Paths to various networks.

PreviousUpdating your Revenue PathNextTiers

Last updated 1 year ago

You may deploy a Revenue Path on the EVM-compatible blockchains below. Additionally, refer to each network tab to see the current supported Tierstokens. For more info on how to set up Tiers, please refer to Adding Revenue Path Tiers.

Contract:

  • Ethereum (ETH)

  • Wrapped Ether (WETH)

  • USD Coin (USDC)

  • DAI (DAI)

Contract:

  • Polygon (MATIC)

  • Wrapped MATIC (WMATIC)

  • Wrapped Ether (WETH)

  • USD Coin (USDC)

Contract:

  • Optimism (OP)

  • Wrapped Ether (WETH)

  • USD Coin (USDC)

Contract:

  • Wrapped Ether (WETH)

  • USD Coin (USDC)

  • DAI (DAI)

To create a Revenue Path in your network of choice, navigate to the Reveel app home page and click the network selector above the "New Revenue Path" button.

Select the network where you'd like your Revenue Path to be created.

Finally, confirm the network switch in your wallet.

That's it! The rest of the process is the same as you would normally follow by Creating a Revenue Path.

Contract:

Ethereum (ETH)

Wrapped Ether (WETH)

USD Coin (USDC)

DAI (DAI)

🏁
0xae4EfaEB758f149f9C780268986537E45Bd57d7C
0xEF44D8e4eAb1ACB4922B983253B5B50386E8668E
0xEF44D8e4eAb1ACB4922B983253B5B50386E8668E
0xEF44D8e4eAb1ACB4922B983253B5B50386E8668E
0x25A7516406FEe7394d40ece9f3EbFaB2a592b4ec