Engineering Q4 ‘21 Recap + Q1 ‘22 Priorities

[edwardk]

Author: @edwardk

For sake of speed I’m sharing this in condensed form. Where available I’ve linked to requirements docs, active tasks, and/or code. An upcoming post will go into my vision for the engineering team more broadly.

If you’re curious about anything listed, I’ll see you in the comments! I also plan to hold an open community call next week to encourage more conversation.

Highlights in Q4 2021

• Launched Liquidity Analyzer (Oct)
  • Added 0x Exchange Data (Nov)
• Launched Coop.tax (Nov)
• Launched ETH2x-FLI-P (Dec)
• Polygon Support on App.indexcoop.com (Dec)
• @blockdev running the Wizardry program
  • Led to recruiting @christn and @FlattestWhite as Solidity Devs and @MAK , @jd899, and @teddy as Web3 / Front-end devs

For a more granular list we have a publicly viewable sprint board on Pivotal Tracker (click “Done” in the side menu) and Wizadry Notion Board (soon to be deprecated).

Planned Initiatives for Q1 2022

Product Launches

• $GMI
  • Token contract
  • Staking contract
  • App updates
• $LDI - Detailed Scope of Work
• MATIC2x-FLI (Polygon)
• iMATIC-FLI (Polygon)
• Product Team’s Roadmap
• Any new products using existing tech (simple indices, FLIs on Polygon or Mainnet) need deploy scripts and web app updates.

Liquidity/Tradeability

• 0x API Exchange Issuance
  • Code is written. Waiting for 0x team to fix a bug in their API, and then code review by Set team
• Leverage Token Exchange Issuance (on Polygon)
  • A more efficient way to mint/redeem FLI tokens
  • Will make it so we don’t have to rely on DEXs for FLI liquidity
  • Maybe: Leverage Token Trading App for FLI products
    • Idea for a dYdX-style trading experience once we have LT Exchange Issuance
• Liquidity Analyzer
  • UniswapV3 Fee Tiers
  • Finish Polygon Support WIP
  • Bug fixes
  • Documentation
  • Maybe: Cross-chain liquidity
• app.indexcoop.com
  • Ground up redesign
  • UI for Buying / Exchange Issuance
  • Event tracking (ex. successful purchase, Wallet errors)

Rebalancing System

• Either follow through on IPRebalanceExtension or potentially upgrade to an auction based system (Set to begin research and design). I’m hoping for the latter.

Intrinsic Productivity (Yield)

• Detailed Scope of Work for $LDI
• Scope of work for $PAY
  • Research Balancer Boosted Pools Integration
• How to handle rebalancing for IP products is still an open question (see “Rebalancing System” above)

Smart Contract Upgrades

• IIP-64: Methodologist Smart Contract Permissioning
  • Deploy and testing in progress
• IIP-72: Redirect revenue for FLI products to Operations account
  • Deploy and testing in progress
• IIP-116: Redirect revenue for DPI, MVI, BED, DATA to Operations account
  • Will follow soon after IIP-72
• IIP-117: Change DATA fee structure to include mint/redeem fees
  • Research task
  • Discuss best option with Set
  • Write deploy scripts
• Support Decentral Games token migration for MVI
• Upgraded Basic Issuance Module that supports being removed/upgraded and safe handling of rebasing tokens
• Maybe: Additional upgrade to Basic Issuance Module to enable mint/redeem fees

Security/Internal operations

• Set up bug bounty
• TBD: Dynamic staking

You can visit the up-to-date sprint board here.

[Thomas_Hepner]

@edwardk This recap and roadmap is unbelievably helpful. Thank you for sharing - this really helps us at Titans of Data develop our strategy and make a product/growth roadmap.

cc: @Kiba

[edwardk]

@LemonadeAlpha

Understand this is not expansive, but was curious if there is any room for things like intrinsic productivity w/in $GMI and for various growth-related engineering work such as bridging our products to rollups and reproducing incentive contracts on EVM-compatible chains.

The short answer is yes! We must continue to invest in our products with marketing and engineering work well beyond their launch if they are to be maximally successful. The marketing part probably doesn’t need any further explanation. I just bought the most expensive hoodie of my life and I can’t wait to become a walking NFT.

A half-baked idea I have is that $GMI and all our other products are Software-as-a-Service (SaaS). Unlike investment products of old, ours are written in code and run on the Ethereum Virtual Machine, interacting with lots of other software in a highly dynamic ecosystem. What we have now is only $GMI v1.0.

How we resolve the tension between upgrading/maintaining existing products and launching new products is something we’ll have to work on with our Product team.

I don’t think we’ve fully thought through how each product we launch can have its own tech roadmap and need ongoing engineering maintenance just to stay viable. Just like every other piece of software you use today.

This is one of the reasons I get worried whenever someone uses # of Products launched as a KPI. I want each of our products to have the proper attention of our amazing marketing and growth machine behind them. And I also want to have the time to allocate more engineering effort when we think a product’s got legs.

Thanks for giving me the chance to get on my soapbox