Skip to content

Latest commit

 

History

History
117 lines (94 loc) · 9.77 KB

MRC00.md

File metadata and controls

117 lines (94 loc) · 9.77 KB
Raw

MRC 00: Morpheus Request for Comment (MRC)

Introduction

Status: Implemented

Summary

MRC, meaning Morpheus Request for Comments, is integral in suggesting and executing changes within the Morpheus ecosystem.
This document is designed to make the submission process more transparent, fair, and efficient. The MRC process generally follows the monthly timing of the weight snapshot Smart Contract updates. So that weights included in MRCs advanced to the "In Progress" stage can be included in the next Smart Contract update which takes place around the 8th of each month.

Purpose and Scope

This guide is crafted for contributors and users within the MOR ecosystem, facilitating structured proposals for standards and material changes to one of the ten Morpheus Reference Implementations (MRIs).

There is an active forum on Discord for all MRCs currently under discussion.

MRIslist

Important

  1. If your contributions is a small incremental improvement to an existing Code base, just Contribute the code, no MRC required.
  2. If you are seeking to build a Smart Agent and deploy it on Morpheus, no MRC is required, just register it on MOR.Software and follow the guidance.
  3. If you have a general proposal for a Morpheus feature its best to discuss it on Discord first. The MRC process is for technical proposals regarding HOW to implement improvements to Morpheus rather than general discussion of ideas.

Submission Timeline and Platforms

Proposals are welcome on GitHub during the Fair Launch phase, eventually moving to MOR.Software for broader community interaction.

Life Cycle of an MRC

1. Pull Request Creates MRC: The author creates a pull request with the details of their new MRC.

2. Merged into "Discussion": The MRC is merged into Discussion by a Maintainer, this indicates the repo maintainer believes the MRC is at least worth discussion and has basic merit to their Reference Implementation.

3. Review: Maintainers should seek to review and provide feedback to MRC authors once a week. So authors can get a sense of the next steps/current state of their MRC.

4. "Pending": Much of the feedback to MRC authors is often about understanding dependencies and what technical hurtles exist for the MRC to be implemented. If a maintainer identifies a technical dependency they can move the MRC into "Pending" status. This indicates they accept the MRC in principle but there is a blocker that needs to be resolved first. The author can then wait on that dependcy and re-open their MRC once it is resolved or help work on resolving the dependency.

5. "In Progress": Once all technical dependencies have been addressed and weights agreed, only then can an MRC be accepted into the "In Progress" stage.

6. "Implemented": For the MRC to be considered "Implemented" the code proposed must be contributed and merged by the maintainer into the correct MRI repository.

Writing a Well-Formed MRC

  • To draft a compelling MRC, study existing examples to grasp the expected format and substance.
  • Use the provided template for standards and changes to Morpheus structure your proposal.
  • Keep the scope of your proposal as narrow as possible. The broader the proposal, the more technical dependencies and complexity will block its path forward.

MRC Request Template

  • Title: MRC#### - [Title of the Proposal]]
  • Author(s): [Author Name (can be anon) and Discord Handle(s)]
  • Category: [refer to Morpheus Reference Implementations (MRIs) list below]
  • Summary: Concise summary of the proposal.
  • Rationale: Importance of the project and why it merits acceptance, including a simple solution description, delivery strategy, and technology stack.
  • Value Proposition: How will the proposal tangibly increase Morpheus's value to Contributors or Users?
  • Dependencies: Other MRCs or tasks needing completion beforehand.
  • New Weights Requested: Number of weights. See guide here.
  • Existing Weights: Current weights of features or code your proposal will enhance.
  • Deliverables: Detailed account of what the proposal once implementated will deliver.
  • Background / Experience of Author / Implementer: Your or your team's credentials for executing the proposal.
  • Status: Current state of the proposal (Discussion, In Progress, Implemented).

Merged or Closed:

  • First, it's important understand that MRCs are a competitive process.
    Someone who proposes better implementation/lower weights/shorter timelines can be chosen (understand that submitting an MRC does not equal that MRC being accepted).
  • Second, if the maintainers' feedback wasn't addressed by an author for two weeks, the MRC is considered closed and can't be re-submitted for one month.
  • Third, a maintainer may close a MRC pull request if there is a technical hurtle that can't be currently addressed in the near term to implement the MRC, or not enough weights being available from that maintainer to accept the MRC, or the maintainer judges the MRC proposal too expensive vs the value of the change / improvement proposed.

Submission Guidelines

Properly document your MRC in the repository and list it in the README for community review. Fork the relevant template and select the most pertinent category.

Meta MRCs about MRCs

  • For most MRCs in general this MRC00 is the first Meta MRC about how to submit an MRC.
  • For MRCs about adding new assets, yield sources, chains, see this MRC guide.

Select the Affected Morpheus Reference Implementation

Choose the matching MRI that your MRC impacts. Reach out to the repo Maintainer you think the MRC is most related to if you are uncertain. List below.

Morpheus Reference Implementation (MRI) List


Smart Contracts: Changes to Morpheus smart contracts.

Smart Agent Tools & Examples: Development and deployment aids for smart agents.

Morpheus Local Desktop/Mobile: Desktop and mobile application proposals.

TCM / MOR20 (Token and Financial Models): TCM/MOR20 standard-related proposals.

Protection Fund: Enhancements to protection funds and security.

Capital Proofs Extending: Capital proofs improvements.

Compute Proofs MOR/Lumerin: Computational proofs improvements.

Code Proofs and Examples

Frontend Proofs & Examples: Frontend resource, proofs, and functionality enhancements.

Interoperability: Proposals for improving ecosystem interoperability.

Competition Among MRI Repo Maintainers To Increase Decentralization

The Morpheus Atomic Governance system aims to be a free marketplace even for the Morpheus Reference Implementations themselves and thus the repo maintainers are not static but compete and are dynamic.

What this will look like in practice is:

  • Anyone can start a fork of an existing Morpheus Reference Implementation.
  • They can set their own weights for how they choose to reward those contributing to their version of the repository.
  • Their code / version of the MRI is a MRC21 Non Fungible Agent with a reward address.
  • The protocol MOR emissions gauge an on chain metric to understand usage of that fork vs all other options.
  • MOR rewards are sent accordingly (as part of the 24% Coding bucket).
  • This on chain mechanism could leverage a lot of the MOR Staking on chain signaling already being developed.
  • If MOR token holding does end up being the mechanism for Signaling then a free market will develop for MRIs.
  • This structure leaves the MRI system open for new forks, new contributors, and free competition over time.
  • Instead of ending up with 1 version the Morpheus network will have multiple competing versions.