Roadmap Update - 10/21

Roadmap Update 10/21

One thing you may notice regarding the below updated roadmap is that it is a bit shorter than the previous –– this is to be expected. Rather than having a longer to-do list as the project matures, there is a shorter and more intensive list of initiatives.

The prior roadmap was developed by YAM contributors approximately one week after launch, and the Yam protocol was still in many ways the same minimally viable experiment it set out to be in version 1. Yam is not a protocol that has been developed for months by a team of devs and analysts, released into the world in an optimized state; it’s rough around the edges with an open future.

Over the past 1 month since launching V3, we’ve laid effective groundwork for how Yam will operate in the future from both a technical and organizational perspective. As a result, the contributors and community can focus their efforts on high impact initiatives, rather than spreading resources across a large number of issues.

Progress Made Since Last Roadmap:

You can view the previous roadmap here:
https://forum.yam.finance/t/yam-roadmap-from-yam-s-contributors/545

Protocol
LP Governance - Snapshot Passed, In Audit
Treasury Purchase Asset Update - Snapshot Passed, In Audit
Liquidity Incentives - Currently Paused, further analysis coming soon
RageQuit - Snapshot Passed, needs additional concepting

Treasury
Diversification - DPI Purchase Snapshot passed, balanced portfolio in concepting
Bug/Hack Protection Protocol - Further development ongoing

Ecosystem and Community
Governance UI - Completed
Documentation - Completed
Mission, Vision, Values - Draft completed, branding work continuing
Weekly Gov/Dev Calls - Completed, ongoing

Organization
Compensate Contributors - Snapshot Passed
Onboard Full-time Contributors - Further development needed

Updated Roadmap:

Protocol

  • Liquidity Incentives
    • Status: Analysis underway
    • Priority: High
    • Summary: The main purpose of liquidity incentives for the Yam protocol is to ensure deep liquidity for the treasury to utilize on a positive rebase, though we also want to ensure exit and entry liquidity for community members. Due to the absence of positive rebases, we have currently paused incentives while developing a new incentive plan.
    • Next Steps:
      • Share analysis of liquidity incentive plan
      • Create a Snapshot proposal to determine incentives for ETH/YAM Pool
  • YAM RageQuit + Lending
    • Status: Concepting
    • Priority: Medium
    • Summary: Rather than simply developing a RageQuit functionality, it’s been proposed to create a RageQuit + Lending functionality that would also allow YAM holders to borrow their RageQuit value. In order to support both functionalities, the protocol will need to designate a portion of its treasury as eligible for RageQuit, while more active management strategies and operational budget are not affected. This could be modified in the future, but is an important first step.
    • Next Steps:
      • Build out project roadmap and scope
      • Assemble and support team of builders for the project
      • Begin releasing information to public
      • Audit upon smart contract completion
      • Testnet
      • Mainnet

Product

  • Bug/Hack Protection Protocol
    • Status: In Early Code Development
    • Priority: High
    • Summary: The bug/hack protection protocol will be Yam’s first product offering and fill an important niche in the DeFi ecosystem. It will allow underwriters to receive cashflows from coverage buyers’ premiums, while offering coverage buyer’s upside in the event of a bug or hack. Yam will benefit via fees and ownership over the protocol.
    • Next Steps:
      • Build out project roadmap and scope, including builder budget
      • Assemble and support team of builders for the project
      • Begin releasing information to public
      • Audit upon smart contract completion
      • Testnet
      • Mainnet

Treasury

  • Implement portfolio allocation
    • Status: Fine tuning
    • Priority: High
    • Summary: Significant work has been done to create a potential treasury allocation to a more active yield seeking and diversified strategy including yield farming, investments, and hedging. This greatly derisks the treasury and increases its potential upside.
    • Next Steps:
      • Reach consensus regarding allocation levels
      • Develop smart contracts to enact allocations

Governance

  • Multigovernor architecture
    • Status: Concepting
    • Priority: Varied
    • Summary: Because the YAM DAO has a wide range of actions and decisions to make on-chain, it makes sense to have a range of Governor contracts catered to various types of decisions. This could include a Governor with a lower quorum requirement but a longer time delay in execution, or a higher quorum requirement but shorter time delay. This will allow for increased efficiency in governance without sacrificing decentralization.
    • Next Steps:
      • Build out new Governor contracts on an as needed basis for specific functionality

Ecosystem

  • Continue branding efforts
    • Status: In Development
    • Priority: Medium
    • Summary: There has been significant work done in the last few weeks to identify some key narratives in the history of Yam and craft these into a more comprehensive brand narrative. These efforts will serve to guide Yam’s messaging and positioning to the broader DeFi ecosystem, as well as help guide the products and services the community creates.
    • Next Steps:
      • Update Yamifesto
      • Create more detailed Yam Handbook, explaining our approach in depth

Organization

  • Contributor Compensation Frameworks
    • Status: Concepting
    • Priority: Medium
    • Summary: In order to attract talent, Yam needs a comprehensive framework for how it plans to incentivize ongoing work on the protocol and its products. This framework will include governance architecture, contributor vesting, on-going contributor payments, and project based payments.
    • Next Steps:
      • Develop framework
      • Post to forum
      • Snapshot off-chain vote for ratification
1 Like

我们该把投票治理时间优化了!这样的治理根本不适合数字货币市场!

普通话:

对于我对Google翻译的使用和翻译质量不佳,提前致歉。

我认为这将在社区以及当前的贡献者和核心团体中获得支持。作为一个社区,我们只需要共同努力以找出适当和最有效的参数,以免受到不良行为者的滥用。

English:

I apologize in advance for my use of Google Translate and the poor translation quality.

I think this will gain support in the community and current contributors and core groups. As a community, we just need to work together to find the appropriate and most effective parameters to avoid abuse by bad actors.

1 Like

we were wasted much time for vote