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
  • Context
  • Objectives
  • Workflow
  • Resources
  1. Resources
  2. Governance
  3. Index Improvement Proposals (IIP) Overview

IIP Step-by-Step

This document outlines the end to end process for IIP contributors.

Context

The IIP process is not just about fulfilling Index Coop’s functional duties. A streamlined and accessible IIP process can help cultivate a community which values open collaboration and ensure contributions are recognized and given a clear path to success.

Objectives

  • Make the path for community contribution simple, accessible, and achievable

  • Set clear guidelines for “next steps” at each stage of proposal process

Workflow

1. Discord & Forum

This is the initial fielding research + discussion on Discord, governance forum, Twitter or any other venue. This is an informal process to gauge community interest in a potential Index Coop improvement.

Here are some questions a proposer might want to answer:

  • Am I able to informally get any traction for this proposal in the Discord?

  • Has this proposal been tried before?

  • How does this proposal get the community closer to achieving its stated goals?

  • What trade-offs are implicit in this improvement's adoption?

2. Create an IIP Proposal

3. Editor Review & IIP Number Assignment

Once an IIP Editor has reviewed the proposal for basic adherence to IIP guidelines, the Editor will create a corresponding entry in the Index Coop GitBook, assign the IIP a number, and create a corresponding discord channel for discussion.

4. Discussion and Minimum Waiting Period

The forum is the formal area to debate the merits of each IIP. While the IIP is on the forum in 'Draft' state, the IIP author is free to make changes to the proposal. Once the IIP author is satisfied with the proposal, they should change the proposal status from 'Draft' to 'Proposed', and contact an IIP editor to schedule a snapshot vote.

5. Calling a Vote

  • The snapshot voting period may not begin until at least 48 hours after the IIP has been proposed.

  • The IIP has a voting period of 3 days where token holders may vote FOR or AGAINST.

  • For standard IIP and meta-governance votes to pass

    • 5% of circulating INDEX tokens must participate

    • 50% or more must vote FOR.

  • For a Product Addition IIP to pass

    • 10% of circulating INDEX tokens must participate

    • 60% or more must vote FOR.

6. Post Voting Process

After the snapshot voting period has concluded an IIP Editor will tally votes and update the GitBook IIP record with the related voting data. If a proposal has passed, the IIP is moved from proposed to approved. If a proposal is rejected the IIP may be moved to rejected or back to WIP to be revised for future consideration.

8. Implementation

In the early stages of Index Coop, approved IIPs will be executed via multisig where necessary. Otherwise, implementation of the IIP will vary on a case-by-case basis.

Resources

PreviousIndex Improvement Proposals (IIP) OverviewNextGovernance Representatives

Last updated 3 years ago

Once a contributor feels they have a rough consensus that their IIP is valuable, original, and achievable, they should submit an on the according

They should also tag an to review the IIP and get an IIP number assigned.

Per , the waiting period before a vote can be called is 48 hours.

All IIPs are confirmed or rejected by the Index Coop via The IIP author is responsible for deciding a snapshot vote date with the following criteria in mind:

Index Improvement Proposal
Index Coop governance forum
to the IIP-0 guidelines.
IIP editor
IIP-26
Snapshot Vote.
IIP-0 Guidelines
Example IIP