Engineering Constraints Follow Up & Next Steps

[Thomas_Hepner]

Thank you, @dylan - this is an excellent follow-up that addresses many of the concerns I shared on Punia’s original post on Engineering and Product Constraints.

@dylan

Key Results - How You’ll Know if the EWG succeeds

Indices

• Rebalances: Infrastructure to handle 10 rebalances a week safely w/o MEV, slippage issues
• New Products: Preparedness to launch 2 index products a month
• Maintenance: Ability to handle 100 metagovernance transactions a week

Leverage Indices

• Supply Scalability: Infrastructure to scale ETH 2x FLI to 2,000,000 supply (400k today) for 10 products
• Maintenance Scalability: Teams and infrastructure to support 10 products, their parameter updates, notifications, etc.
• New Products: Preparedness to launch and support 10 products

Previously, the EWG set out to reduce technical operations overhead weathered by the Set Team.

The new goal is to scale technical operations of Index Coop products. Scaling these operations will unlock the next stage of growth for the Coop & enable more products to be launched more quickly.

I am percent on-board with this and believe it’s the key to unlocking products from many methodologists that @overanalyser has outlined here.

Please count me in on helping to resolve this problem specifically:

@dylan

Indices

• Rebalances: Infrastructure to handle 10 rebalances a week safely w/o MEV, slippage issues
• New Products: Preparedness to launch 2 index products a month
• Maintenance: Ability to handle 100 metagovernance transactions a week

It is a must-have for @Kiba and I to be able to launch our proposed Data Economy Index (DATA) and I’m willing to pull out all the stops to make this happen.

I will be attending the EWG meeting this Wednesday (6/16) and would be happy to spearhead a Technical Operations Working Group to begin making progress on the required items you have you outlined:

@dylan

In order to scale technical operations we need:

Current Process Documentation

EWG will need help from many more contributors. Contributors need high context on the current technical processes in order to make decisions about how the system can be scaled. So far context has been most commonly shared via detailed forum posts & documentation, but other context sharing strategies like Q&A’s and process walkthroughs have been very effective and will be promoted.

Technical Process Design & Automation

Once enough context has been shared, expert groups can begin establishing processes to efficiently & safely own aspects of technical operations, with the goal of maximizing automation & safety.