Index Coop Resource Center
  • Welcome to The Index Coop.
  • Products
    • Trade
      • Index Coop Leverage Suite
      • Leverage Token Parameters
      • Leverage Token Keepers
      • Trading Interface Guide
      • Ripcord Guide
    • Earn
      • High Yield ETH Index (hyETH)
      • Interest Compounding ETH Index (icETH)
    • Asset Management
      • Product Development Process
      • Product Revenue Tokens (PRTs)
    • Legacy Products
      • How to Redeem Legacy Products
      • DeFi Pulse Index (DPI)
      • Bankless BED Index (BED)
      • Metaverse Index (MVI)
      • Diversified Staked ETH Index (dsETH)
      • Index Coop CoinDesk ETH Trend Index (cdETI)
      • Index Coop Large Cap Index (ic21)
      • ETH 2x Flexible Leverage Index (ETH2x-FLI)
      • BTC 2x Flexible Leverage Index (BTC2x-FLI)
      • Flexible Leverage Index- Polygon (FLI-Ps)
        • ETH 2x Flexible Leverage Index (ETH2x-FLI-P)
        • Inverse ETH Flexible Leverage Index (iETH-FLI-P)
        • BTC 2x Flexible Leverage Index (BTC2x-FLI-P)
        • Inverse BTC Flexible Leverage Index (iBTC-FLI-P)
        • MATIC 2x Flexible Leverage Index (MATIC2x-FLI-P)
        • Inverse MATIC Flexible Leverage Index (iMATIC-FLI-P)
      • Market Neutral Yield ETH (MNYe)
      • Bankless DeFi Innovation Index (GMI)
      • Data Economy Index (DATA)
      • Legacy Contract Addresses
      • Gitcoin Staked ETH Index (gtcETH)
  • Protocol
    • Index Protocol
      • Core Contracts
        • Set Token
        • Set Token Creator
        • Controller
        • Integration Registry
        • Price Oracle
        • Set Valuer
      • Modules
        • Basic Issuance Module
        • Debt Issuance Module v2
        • NAV Issuance Module
        • Trade Module
        • Streaming Fee Module
        • Wrap Module
        • Airdrop Module
        • Claim Module
        • Governance Module
        • Compound Leverage Module
        • Aave v2 Leverage Module
        • Aave v3 Leverage Module
        • Auction Rebalance Module
    • Set Protocol v2
    • Security and Audits
    • Contract Verification
    • Programmatic Redemptions
  • Resources
    • Governance
      • $INDEX - Governance Token
      • Index Improvement Proposals (IIP) Overview
        • IIP Step-by-Step
        • Governance Representatives
        • IIP Template
        • Product (DG) Template
      • Meta-Governance
      • Delegation
    • Data & Analytics
    • Multisigs
    • Press Kit
Powered by GitBook
On this page
  • Overview
  • Product Development Timeline
  • Rationale
  1. Products
  2. Asset Management

Product Development Process

PreviousAsset ManagementNextProduct Revenue Tokens (PRTs)

Last updated 1 year ago

Overview

Most new products under consideration will follow the redefined proposed in the forum. The goal of this proposal was to revamp the Index Coop’s product development process by introducing a pre-sale process for new product proposals. This pre-sale process will accomplish four things:

  1. Surface a direct demand signal (or lack thereof) for potential products

  2. Ensure DAO resources are allocated to products with clear demand

  3. Bootstrap TVL and liquidity for new products before launch

  4. Incentivize early adopters to support and grow new products over time

The pre-sale process enables customers and early adopters to demonstrate tangible demand for a proposed product by depositing funds into the token before launch. Each pre-sale will have a pre-defined deposit threshold (ex. $3m) that must be met within a specified amount of time (ex. 30 days) to determine whether or not the product is formally launched. If a pre-sale meets or exceeds this threshold in the allotted time, the product will be launched by the Index Coop. If the pre-sale does not meet the agreed-upon threshold, the product will not be launched and depositors can withdraw their funds. Pre-sale supporters may also be incentivized with $INDEX, future product revenue, or other rewards.

Product Development Timeline

  1. Publish to the forum for comment period

  2. Conduct INDEX vote to advance (or not advance) the product to a pre-sale

  3. If the INDEX vote passes, the pre-sale period will begin on the pre-sale start date. It will last for a period as defined in the proposal, and it must meet the defined deposit threshold at the end of pre-sale period.

  4. If the pre-sale is successful, the product will be developed and marketing materials will be created during the pre-launch period. During this time, the product will be rebalanced into it's initial composition using deposits from the pre-sale.

  5. At the end of pre-launch period, the formal launch will take place. The formal launch allows regular users to begin issuing and/or buying the new product.

  6. After the formal launch, the post-launch period will begin. When distributing incentives to pre-sale depositors, the end of the post-launch period can signify when the incentive recipients will be able to claim their rewards. This is useful as non-binding mechanism to force pre-sale depositors to hold their positions until a sufficient amount of time has passed.

Rationale

In addition to signaling direct demand for potential products, the pre-sale process also ensures that DAO resources are allocated more efficiently. Under the current product development process, a significant amount of resources must be invested to bring a product to market. Almost every contributor is involved at some stage, translating to direct costs and opportunity costs. It’s not until after these investments are made and the product is formally launched that it is apparent if there is a demand for a product.

Under the pre-sale process, the majority of these go-to-market activities do not need to be completed until after the deposit threshold is met and there is a clear indication of customer demand. Therefore, this pre-sale approach minimizes the upfront investment that has been prohibitive in the past and clarifies the case for eventual resource allocation.

Product Development Process
Pre-sale Product Proposal