# MRC 20: Automated Recurring Revenue / Rewards = ARR via the MOR20 Token Standard ## Status: In Progress - Being coded as of April 2024 => Implemented ## Summary: This is a simplified MRC to introduce the term "ARR" for Automated Recurring Revenue or Rewards.\ This MRC is already described in the Techno Capital Machine paper and implemented in the MOR20 Smart Contracts. * Link: ## Description: Automated Recurring Revenue / Rewards (ARR) Generalizing the TCM Model - MOR20 Token Standard * Any project inside or even outside the context of Web3 & AI, can use Morpheus to bootstrap their project with the push of a button. * The use the MOR20 Smart Contracts to collect stETH in order to provide Automated Recurring Revenue (ARR) to the project is a compelling new framework. * Easily create a fair launch for projects, fair price discovery mechanism and access the large network effect of the Morpheus community. * This model can be extended to many software as a service projects as a means of building recurring revenue / payments from users via yield. * The Morpheus platform charges only 0.35% (35 basis points) of the stETH yield collected by projects using the MOR20 Smart Contracts / Dashboards. * This yield collected is added to the Morpheus Protocol Liquidity and provides on going support for further Dashboards, Smart Contract development and audits. * This adds to the Network Effect of Morpheus when it comes to bootstraping new projects, growing liquidity for all MOR20 Smart Contract users. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://gitbook.mor.org/mrc/closed/mrc20.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.