From 884aa0eb300f3267f457a81fa8ddf6b6a6838865 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Mon, 12 Feb 2024 02:57:35 -0400 Subject: [PATCH 001/129] Update Morpheus Request For Comments (MRC).md List of Morpheus Requests for Comment MRCs. --- Morpheus Request For Comments (MRC).md | 28 +++++++++++++++++--------- 1 file changed, 18 insertions(+), 10 deletions(-) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index 95db02c..3e11b2f 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -1,19 +1,27 @@ # Morpheus Request for Comments (MRC) +List of proposals extending Decentralized AI. Similar to the function of the ERC system serves in Ethereum. https://eips.ethereum.org/erc Provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. -- List of proposals for specific technical functions for Decentralized AI. -- Similar to the function of the ERC system serves in Ethereum. https://eips.ethereum.org/erc -- Provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. +## List of MRCs: +- MRC 00001 Smart Agents White Paper. +https://github.com/SmartAgentProtocol/SmartAgents/blob/main/White%20Paper.md -MRC 0001 +- MRC 00002 Smart Agenets Yellow Paper. +https://github.com/SmartAgentProtocol/SmartAgents/blob/main/YellowPaper.md -MRC 0002 +- MRC 00003 Morpheus White Paper. +https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/2.WhitePaper.md -MRC 0003 +- MRC 00004 Morpheus Yellow Paper. +https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/3.YellowPaper.md -MRC 0004 +- MRC 00005 Yellowstone Compute Model. +https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md -MRC 0005 +- MRC 00007 Waterloo Community Model. +https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing -MRC 0007 +- MRC 008 Fair Launch Process +https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/5.FairLaunch.md -MRC 0008 +- MRC 00009 Techno Capital Machine +https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/4.TechnoCapitalMachineTCM.md From 27dcbecb2fb887411c9b6e9a48f94d789a17aab5 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Mon, 12 Feb 2024 02:57:53 -0400 Subject: [PATCH 002/129] Update Morpheus Request For Comments (MRC).md Formatting. From 363ea149b7a6fc5d94008f3519314960d403abfe Mon Sep 17 00:00:00 2001 From: David Johnston Date: Mon, 12 Feb 2024 03:00:03 -0400 Subject: [PATCH 003/129] Update Morpheus Request For Comments (MRC).md Formatting. --- Morpheus Request For Comments (MRC).md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index 3e11b2f..d007517 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -2,26 +2,26 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC system serves in Ethereum. https://eips.ethereum.org/erc Provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. ## List of MRCs: -- MRC 00001 Smart Agents White Paper. -https://github.com/SmartAgentProtocol/SmartAgents/blob/main/White%20Paper.md +- MRC 00001: Smart Agents White Paper. +Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/White%20Paper.md -- MRC 00002 Smart Agenets Yellow Paper. -https://github.com/SmartAgentProtocol/SmartAgents/blob/main/YellowPaper.md +- MRC 00002: Smart Agenets Yellow Paper. +Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/YellowPaper.md -- MRC 00003 Morpheus White Paper. +- MRC 00003: Morpheus White Paper. https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/2.WhitePaper.md -- MRC 00004 Morpheus Yellow Paper. +- MRC 00004: Morpheus Yellow Paper. https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/3.YellowPaper.md -- MRC 00005 Yellowstone Compute Model. +- MRC 00005: Yellowstone Compute Model. https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md -- MRC 00007 Waterloo Community Model. -https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing +- MRC 00007: Techno Capital Machine +https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/4.TechnoCapitalMachineTCM.md -- MRC 008 Fair Launch Process +- MRC 00008: Fair Launch Process https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/5.FairLaunch.md -- MRC 00009 Techno Capital Machine -https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/4.TechnoCapitalMachineTCM.md +- MRC 00009: Waterloo Community Model. +https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing From f0ef4e2490f93f42248ee91918eacc2a188191d5 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Mon, 12 Feb 2024 03:00:28 -0400 Subject: [PATCH 004/129] Update Morpheus Request For Comments (MRC).md --- Morpheus Request For Comments (MRC).md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index d007517..e8ae7cd 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -3,9 +3,11 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## List of MRCs: - MRC 00001: Smart Agents White Paper. + Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/White%20Paper.md - MRC 00002: Smart Agenets Yellow Paper. + Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/YellowPaper.md - MRC 00003: Morpheus White Paper. From a5a92d87a0220b20e221bba55b39f20c00b6569c Mon Sep 17 00:00:00 2001 From: David Johnston Date: Mon, 12 Feb 2024 03:01:10 -0400 Subject: [PATCH 005/129] Update Morpheus Request For Comments (MRC).md --- Morpheus Request For Comments (MRC).md | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index e8ae7cd..21e0803 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -11,19 +11,25 @@ Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/White%20Paper. Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/YellowPaper.md - MRC 00003: Morpheus White Paper. -https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/2.WhitePaper.md + +Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/2.WhitePaper.md - MRC 00004: Morpheus Yellow Paper. -https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/3.YellowPaper.md + +Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/3.YellowPaper.md - MRC 00005: Yellowstone Compute Model. -https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md + +Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md - MRC 00007: Techno Capital Machine -https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/4.TechnoCapitalMachineTCM.md + +Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/4.TechnoCapitalMachineTCM.md - MRC 00008: Fair Launch Process -https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/5.FairLaunch.md + +Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/5.FairLaunch.md - MRC 00009: Waterloo Community Model. -https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing + +Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing From fe693d9d30c66264306eedf19e4b0ca4327f212a Mon Sep 17 00:00:00 2001 From: David Johnston Date: Mon, 12 Feb 2024 12:40:41 -0400 Subject: [PATCH 006/129] Update Morpheus Request For Comments (MRC).md Status for each MRC --- Morpheus Request For Comments (MRC).md | 31 +++++++++++++------------- 1 file changed, 16 insertions(+), 15 deletions(-) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index 21e0803..ed5a8f0 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -2,34 +2,35 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC system serves in Ethereum. https://eips.ethereum.org/erc Provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. ## List of MRCs: -- MRC 00001: Smart Agents White Paper. +## MRC 00: Smart Agents White Paper. Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/White%20Paper.md +Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. -- MRC 00002: Smart Agenets Yellow Paper. - +## MRC 01: Smart Agenets Yellow Paper. Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/YellowPaper.md +Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. -- MRC 00003: Morpheus White Paper. - +## MRC 02: Morpheus White Paper. Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/2.WhitePaper.md +Status: **Adopted** by the Morpheus community as basis for Morpheus Network. -- MRC 00004: Morpheus Yellow Paper. - +## MRC 03: Morpheus Yellow Paper. Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/3.YellowPaper.md +Status: **In Progress**, Being implimented as the basis for Capital, Code, Compute and Community Builders. -- MRC 00005: Yellowstone Compute Model. - +## MRC 05: Yellowstone Compute Model. Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md +Status: **In Progress**, Being implimented as the Decentralized Router for the launch of Compute rewards post bootstrapping period. -- MRC 00007: Techno Capital Machine - +## MRC 07: Techno Capital Machine Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/4.TechnoCapitalMachineTCM.md +Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. -- MRC 00008: Fair Launch Process - +## MRC 08: Fair Launch Process Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/5.FairLaunch.md +Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. -- MRC 00009: Waterloo Community Model. - +## MRC 09: Waterloo Community Model. Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing +Status: **Under Discussion**, needs additional work to flush out the concepts. From 3ba01d4d7e30442e34399c8d6e46052156d7e2bd Mon Sep 17 00:00:00 2001 From: David Johnston Date: Mon, 12 Feb 2024 12:42:31 -0400 Subject: [PATCH 007/129] Update Morpheus Request For Comments (MRC).md Formatting. --- Morpheus Request For Comments (MRC).md | 39 +++++++++++++------------- 1 file changed, 20 insertions(+), 19 deletions(-) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index ed5a8f0..8d97582 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -4,33 +4,34 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## List of MRCs: ## MRC 00: Smart Agents White Paper. -Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/White%20Paper.md -Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. +- Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. +- Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/White%20Paper.md ## MRC 01: Smart Agenets Yellow Paper. -Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/YellowPaper.md -Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. +- Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. +- Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/YellowPaper.md ## MRC 02: Morpheus White Paper. -Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/2.WhitePaper.md -Status: **Adopted** by the Morpheus community as basis for Morpheus Network. +- Status: **Adopted** by the Morpheus community as basis for Morpheus Network. +- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/2.WhitePaper.md ## MRC 03: Morpheus Yellow Paper. -Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/3.YellowPaper.md -Status: **In Progress**, Being implimented as the basis for Capital, Code, Compute and Community Builders. +- Status: **In Progress**, Being implimented as the basis for Capital, Code, Compute and Community Builders. +- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/3.YellowPaper.md ## MRC 05: Yellowstone Compute Model. -Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md -Status: **In Progress**, Being implimented as the Decentralized Router for the launch of Compute rewards post bootstrapping period. +- Status: **In Progress**, Being implimented as the Decentralized Router for the launch of Compute rewards post bootstrapping period. +- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md -## MRC 07: Techno Capital Machine -Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/4.TechnoCapitalMachineTCM.md -Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. +## MRC 06: Techno Capital Machine +- Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. +- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/4.TechnoCapitalMachineTCM.md -## MRC 08: Fair Launch Process -Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/5.FairLaunch.md -Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. +## MRC 07: Fair Launch Process +- Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. +- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/5.FairLaunch.md + +## MRC 08: Waterloo Community Model. +- Status: **Under Discussion**, needs additional work to flush out the concepts. +- Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing -## MRC 09: Waterloo Community Model. -Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing -Status: **Under Discussion**, needs additional work to flush out the concepts. From 01eaad492cd6d9cbaccdccc4d296cef06de14f52 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Mon, 12 Feb 2024 23:58:56 -0400 Subject: [PATCH 008/129] Create DeAI Summit 01.md Notes from first Decentralized AI Summit. --- DeAI Summit 01.md | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 DeAI Summit 01.md diff --git a/DeAI Summit 01.md b/DeAI Summit 01.md new file mode 100644 index 0000000..a07b092 --- /dev/null +++ b/DeAI Summit 01.md @@ -0,0 +1,2 @@ +# Decentralized AI Summit held in Austin, TX on December 9th 2023 + From 831b36fbd52af36c7a8a4e0621d3585fdc421251 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Mon, 12 Feb 2024 23:59:33 -0400 Subject: [PATCH 009/129] Update README.md New Readme --- README.md | 567 +----------------------------------------------------- 1 file changed, 1 insertion(+), 566 deletions(-) diff --git a/README.md b/README.md index 7f388ae..a7aa5ff 100644 --- a/README.md +++ b/README.md @@ -1,566 +1 @@ - -![DAI-ecosystem](https://github.com/DecentralizeAI/MRC/assets/76454555/d4be1474-3046-4fc3-8803-a880038b78aa) - -# Building Decentralized AI - -On December 9, 2023 the Decentralized AI community assembled from around the world at Kiretsu in Austin, Texas in order to begin contributing to this repository. - -The objectives are to define: -- 1. The tech stack for Decentralized AI -- 2. Practical technical standards for collaboration within in the community. - -Morpheus encourages and will incentivize developers who propose or implement new standards/integrations between open source projects in DeAI. - -Live Journal - -## Morpheus - David A. Johnston -- Website: -- Github: -- David's X Profile: - -Morpheus is designed to incentivize the first peer-to-peer network of personal AIs, known as Smart Agents. Providing users open-source Smart Agents to connect to their wallets, Dapps, & smart contracts promises to open the world of Web3 to everyone. - -**Key points:** - -- 230 days left until July 26, 2024 - the date the commerce department is mandated to deterine if open source wieghts conssttiute munitions -- EO signed on October 31st -- Limits number of parameters models can have - - limit for permissionless models at 10B parametrs and only 20gigs - - KYC for data centers -- Only an 8 month timeline to build open source tech stack - -- permissionless building is the heart of what we’re trying to do - -- Phil Zimmerman is the patron saint of decentralized AI - - In 1991, a bill was introduced to ban encryption for email, so Phil introduced PGP, because privacy is a human right - - He printed his work on a t shirt and was arrested for disclosing the RSA algorithm. - - Won in supreme court based on free speech grounds, who recognized that code and speech were protected -- This is why your email can legally be have private -- A few weeks ago in SF the Keep AI Open event was announced and within 48 hours >700 people showed up at the end of OpenAI's dev day -- Marc Andreessen is constantly posting memes for decentralized AI - - the right tot bear compute - - come and take it -- Balaji Tweet: - "free internet means free AI - we will fight government control over compute with everything we have" -- Morpheus is decentralized open source AI, and the tech stack for decentralized AI - - anonymous group dropped paper in September - - within 45 days community had built implementation - - live now can run on computer locally - - fully open source LLM running on your data - - MOR smart contracts entering testnet today -- We want this to continue beyond today - - join discord - - channel for every project os people can follow up with questions - - engage with everyone building models, fine tuning, agents, every part of tech stack -- The goal is 1 billion users for decentralized AI - - AI is the opportunity to get a billion people into crypto by removing technical barriers to access web3 - - With AI, we build off the expressed intent, - - On Morpheus, it knows what smart contracts are available -- The AI community: needs censorship resistant compute and tools to monetize agents - -## Anna Zazlauskas - Vana - -Vana: Own your data - -***Key points*** - -- data ownership -- goal: world where users own data and value it creates -- initial belief: token incentives enable large scale RLHF and data labelling - - people who want to sell data do so out of desperation - - not the best dataset - - uphill fraud battle - - people constantly finding ways to sell bad data - - people who want to sell data for financial reward are not representative - - mostly doing out of financial desperation - - users choose products that align with ideologies, value privacy and agency -- Reality: - - users choose whatever is most convenient or capable. privacy/security are afterthoughts. - - slacktivism - -- initial belief: data ownership legislation like GDPR and CCP will help. - - regulation favors consumers. -- learning: even if users have a legal right ot data, it is inconvenient to access. users have to be very motivated. - - regulation favors incumbent. - -- you can ask for your labels on instagram - -- On Vana: - - make a personal data tangible through a personalized ai model - - bring your model with you throughout internet - - users host their own nodes or opt for a convenient hosted option - - private data stays on user's node, while third party apps run inference. - - granular permissions so you can let people access your data or models. - -- Modalities: - - image: train lora based on 10 photos of yourself - - text: personality + memory stream from your social data and messages - - audio( hosted) based on 1min of your voice - - best audio models are closed source (?) - -- memory architecture - - query memories based on relevance, important, and recency - - summarize relevant memories to fit in context window - - for more, read Generative Agents: Interactive Simulacra of Human Behavior - -- bootstrapped network by building viral consumer applications in house - - 1.2M users - - 700k private models trained - - 10M personal data points - -- collective models - - users contribute data to models they collectively own and govern - - users decide who can access the model, how much to charge, how it can be used - - each collective has its own node, similar to a user’s node - -- host your own vana node - - connect your social data, journal entries, messages, other personal data with an ally that deeply understand you - - everything stays on yoru machine - - can open up an endpoint to use it throughout apps - - reach out to to try this out - -## Ritual - Niraj - -Integrate AI models into your protocol, application or smart contract with a few lines of code. - -Described a global statistical computer. - -__Key Points:__ -- motivation: - - ai is eating the world - - usage going up massively - - decentralized intelligence improving - -*problems of AI today:* -- infrastructure highly centralized - - model storage - - model governance and ownership (e.g. OAI fiasco) - - model compute (training, inference, fine tuning, etc) - - access to training data -- ai infra is highly permissioned - - high costs ot using/improving AI - - permissioned centralized APIs to access - - no privacy/computational integrity censorship resistance - - most OSS models are highly red-teamed/censored - - many geographical limitations -- AI infra is increasingly regulated - - ai incumbents and governments attempting strong regulatory capture - - “we know what’s in your best interests” - -- future impact - - as AI gets inserted into every tech product, new forms of censorship/manipulation ill take place - - LLMs and other foundation models create highly engaging forms of propaganda (e.g. 2024 US election media) - - political ideology weaponized by who controls distribution and access to models - - open and transparent governance of AI models is key - - “who controls models controls the world” - -*AI x Crypto to the rescue* -- AI is highly centralizing tech -- crypto is highly decentralizing tech -- combining both solves aforementioned problems -- trustlessness + intelligence = ???won’t be evil -> can’t b evil -- if we’ve decentralized money, music, property records, etc, why not AI? - -At Ritual: -- how do we get AI into hands of crypto devs today -- combine best of ai and crypto to make it easy for devs to build crypto x ai products -- model specific computational integrity (opML and zkmlO -- privacy (FHE for classical ML models, MPC for foundation models) -- ritual AI VM with stateful precompiles for various model operations (inference, FT, quantization, embeddings) -- supports Ethereum base chain and rollups, alt L1 support coming in 2024 - -- tech pillars - - censorship resistance and decentralization - - privacy - - computational integrity - - incentives - -- infernet: network for inference - - take smart contract, plug into model - - allows you to customize infra - - set up nodes yourself, run inference for your products - -- frenrug - - on-chain smart agent that buys and sells friend.tech keys if you can convince it - - built on internet SDKs - - internet llm nodes generate responses, feeds into on-chain classifier (with ezkl proof)github.com/frenrug/contracts - - frenrug.com - -


- -## Akash Network - Greg Osuri - -Akash is open-source Supercloud that lets users buy and sell computing resources securely and efficiently. Purpose-built for public utility. - -Greg's demo showcased the options available on the network and the ability to spin up new services. - - - - -**Key points** -- GPUs are hard to get on demand -github.com/akash-network/community - -- console.akash.network/analytics - -- e.g. 1k/mo H100 -https://pixart-alpha.github.io/ - -- ray compatible - -- a100 utilization 95% - -- $300m incentives coming online next year - -## Agora Labs - Anish - -Cloud-agnostic MLOps/LLMOps platform powered by cheap, decentralized compute. - - - -### render network - -**Key points** -- OG in crypto space -- pioneered first use case for GPUs -- process of rendering is converting 3d model into pixels -- takes a lot of compute power -- used to take a day -- goal to provide fast, affordable rendering -- 25M frames rendered on network to date -- waitlist of GPUs over a million long - -@drjonessf - -BitTensor - -- Beff Jezos' Thermodynamic computer - -- AHaH Controller - - a trillion synapses per clock cycle - - energy based not transistor based - -- Instead of loss landscapes, lowering error - - Let’s build incentive landscapes, get more profit - - Pay them not for adapting weights but all sorts of things - -- Lower error on neural network -- Faster inference -- better gradients -- more information - -- get paid for having GA lower loss -- sucking up compute and innovation -- passed OpenAI’s loss on GPT2 (trained in 2016) -- 31.39 vs 34.9 perplexity - -bittensor.com/docs -https://docs.bittensor.com/ - -FreedomGPT - -- SmarterChild: conversational AI -- robot you could talk to on AOL IM when no one was there - - pretty dumb - - step above a Liza - - you could make your own, have it talk to other people, look at conversations - - sometimes it would say “i’m not going to answer that” - - chilling effect - - happening again now - -- sold mutual mobile a year ago -- 400 person a year go making dgitial products for f1000 -- did a lot with AI -- sold it, started playing with ChatGPT about a year ago -- had birthday party for chatgpt last week -- a year ago decided to create FreedomGPT -- app store for AI -- first model: trying to get to parity of ChatGPT using Luna, 3d gradient descent -- model would answer anything -- 2 million people trying it out - -- as capability increase, censorship and prohibition increase - -- as capability increases, privacy and liberty decreases don’t use it if you’re not sure things will remain private - -- they will make it illegal to access under penalty of death (treason) - -- midjourney bans Xi, Jinping - --------- - -- technology is what allows freedom to exist -- belief: freedom is assured by documents -- reality” freedom assured by access to sufficiently advanced knowledge & technology over -- those wanting ot take your freedom away - -- these are munitions we need them otherwise they will be used against us and they already are - -- fall of Constantinople by ottoman empire - gunpowder - -- Gutenberg printing press caused nation to fall and US became independent - -- war of 1812, attacked library of congress where books were - -- those that start by burning books, will end by burning men heinrich heine - -- how much more powerful is AI than books? 10x?1000x? - -- thought experiment - - imagine an AI that people star tto trust nearly 100% of the time - - - the problem isn’t if AI says something incorrect it’s as if AI starts saying too many correct things - - - e.g. “ted cdruz is zodiac killer” - -- our predictions - - ai public/private censorship timeline - - - 18 months (may 2025) accessing many AIs in the US will be on par with -- pharmaceutical RXs (if you can prove you need it, you can access) - - 24 months, powerful AIs will require a process similar to obtaining a firearm with background checks and waiting periods. - - misuse will result in permanent revocation. numerous AIs will be banned from being indexed in search engine or even mentioned by the AIs that re deemed “publicly safe” - -- Within 36 months, access to most powerful AIs will be restricted - -- decentralizing freedom of compute because there is no other option - -- freedom != free -- open sourced project reached #3 ranking on github -- over 700k installs of free desktop app -- cloud version generates $1k daily revenue -- banned from multiple hosting providers -- cease and desist from twitter/x and other -- prohibited from being discussed on facebook/meta properties -- +40 multimodal AI models with plans for 4k in 2023 -- tons of hate mail and threats to get us shut down - -- shortly after launching TwitterGPT, got banned (after elon acquisition) -now back on twitter - -- team background - - created products currently used by over a billion monthly users - - collectively hired over 1k engineers/designers/PMs since founding mutual mobile - - built +250MM in digital products for companies like google nike, and dozens of banks - - built dozens of ML/predictive analytics solutions - -- 2 groups of users - - ~3k paid - - ~400k free - -- plan is to start paying those nodes -- been cancelled from multiple web hosts -- one is now allowing us -- matter of time before they pull the plug - -- freedomgpt-git-edge-node-ageofaicapital-s-team.vercel.app -- https://edge.freedomgpt.com/?ref=node-signup -- earn $30/day running inference - -## EdgeLLama - -### Varun Mathur - -EdgeLLama, and the associated set of products, which lead to a seamless AI consumer-cloud will impose a similar abundant forcing function on AI as well. You can go ahead and cancel your $20/month Pro plans, because this next wave of AI, runs in your laptops, desktops and smartphones, and is good enough. - -

- - -## Nous Research -Self-Improving AI
 -Nous Research is a private applied research group. We publish open-source work in the LLM domain, including local models, datasets, and core architectural improvements. - -The demo included a walkthrough of the Nous software. It showed the ability to build AI via drag and drop. Am explanation of their research described YaRN, Hermes, Obsidian, and Capybara. - -**Key points** - -- Started three years ago -- four founders crypto people who found AI in different ways -- “fuck openAI” brought them together -- what can we do to open up again -- not negative, pushing against them -- provide a space for more humanistic AI -- 6 full time contributors -- 48 volunteer AI researchers -- thousands of contributors - -- open source modles - - OpenHermes 2.5 - - top used 7b - - capybara - - 34b amplify-instruct - - obsidian - - stablelm + openclip + capybara - -- open research -- yarn -- muse: generative CoT reward model -- vulcan: chatML extension -- SYNTHIA - -- Nous Forge - - desktop app for interfacing with and composing open source and other AI models -- Obsidian multi-modal model - - focussed on edge devices - - - -most robust agents are breaking after 5 runs - - -

- -## io.net - Angela Yi - -- io.net is a state-of-the-art decentralized computing network that allows machine learning engineers to access distributed Cloud clusters at a small fraction of the cost of comparable centralized services. - -- io.net deploys GPU clusters from multiple locations that are not constrained by colocated devices. The platform supports clusters of any scale, allowing engineers to deploy a 20K GPU cluster within seconds. - -io.net has 3 key elements: - 1. IO Cloud, where engineers can seamlessly deploy their GPU clusters. - 2. IO Workers, where suppliers can connect their devices, monitor their performance, and keep track of their earnings and rewards. - 3. IO Explorer, where we provide transparent, real-time information on pricing, as well as devices and clusters, and inferences powered through our network. - - - - - -## Commune AI - -Commune is a protocol that aims to connect all developer tools into one network, fostering a more shareable, reusable, and open economy. It follows an inclusive design philosophy that is based on being maximally unopinionated. This means that developers can leverage Commune as a versatile set of tools alongside their existing projects and have the freedom to incorporate additional tools that they find valuable. - - - -### Upshot - Nick Evans - -- Upshot: AI Network optimzied for financial applications -- powered by proof opf alpha protocol -- reward people by how useful for financial markets - -- why focus on financial pplications? - - build tools that can enable creation fo financial markets for anything - - riskless society - - efficient enough markest that every risk can be hedged - - cryp is olargely financial innovation - - financialization has been one of main usec ases - - more conducive for trustless/verifiable form factors - -- bacgkground - - upshot one: peer prediction protocol for incentivizing honest responses to subjective questions - - DMI Mcehanism: - - dominantly truthful: truth tellling is dominant strategy - - informed ftruthful: truth telling is stricftly better than uinformative strategies - - detail free: does not require prior knowledge to be inputted by mechanism designer - - constant: only a constant number of questions and agents are required for it to be both dominantly truthful and informed-truthful - -- findings - - peer prediction doe simprove truth teslling incentives - - network of human eactors lacks accuracy and scalability - -- Upshot AI x Crypto Tooling - - AI infrastructure for price predictions, network analyses, yield strategies, etc. - - 2-5% MAPE (mean absolute percentage error) - - 394m assets supported - - <5 min update cadence -- findings - - validated hypothesis around demand for AI x crypto systems - - single entity creating models introduces scalability constraints and security rsisk - -- solution - - combine peer prediction protocol and AI x Crypto infra to build decentralized AI network optimized for financial applications - -Upshot: - - alpha miners establish contractual agreements on chain with dat providers - - results in rev sharing from alpha minor work - - share predictions with each other regularly - - score each other’s predictions, leveraging peer prediction mechanism - - incentivize them to share evaluations honestly - -- big graph broken by topics - - topic is defined by objective that is being collaoratively solved - - output: mmeta model - - data providers establish edges with alpha providers - - alpha minors share predictions with each other, score predictions, scores aggregated, rewards distributed based on proof of alpha - -- zkPredictor - - alpha minors can pass around proofs verifying output of their work is result of underlying model they’re advertising - - ensures tamper proof models - - zkSNARK proof system optimized for tree-based models - - verifies output of initial models on upshot network approaching 10k predictions per hour - -Robonet: -- fist application that builds on Upshot and zkPredictor -- DeFi vaults with AI-Powered Yield Strategies -- smart contracts are limited compute environments -- AI is better at making sense of large amounts of data - - 1. users deposit capital into robonet vaults. - 2. 2 strategies are instantiated as “optics” on upshot network - 3. upshot - 4. fees are shared between upshot peers contributing to the strategies and capital providers - -- people who have unique insights no longer need capital or structure to profit off insights - -- benefits - - more diverse, expressive strategies - - support for more long tail categories - - cryptographically verified models - - potential for much higher yield - -http://upshot.xyz - - -## Actioneer - David Orban - -Dignity and purpose for 8 billion humans in an age of AI - - - - -## OpenCog Hyperon - -The open-source software framework bringing together multiple AI paradigms in a cognitive architecture oriented toward AGI at the human level and beyond - - - - -## Hypercycle - -HyperCycle is building a tiny but essential component that enables AI Machines to transact with other AI machines in a sub-second finality which results in unprecedented emergence. - - - -## The Lifted Initiative - -### Eric Bravick - -The Lifted Initiative is building a comprehensive web3 native cloud with a focus on easy to use tooling. We've launched about 17 product and service groups to date into private Beta, including support of AI use cases. We go public in 2024 and we are currently seeking integrations with other AI focused networks. We believe strongly in decentralization of networks (multi-network approaches) and will be embracing a wide array of partnerships rather than a "build it all on one chain" philosophy. - - - -##Pannel Discussion -#### Ryan @ Modulus Labs -- previously AI research at Stanford -- worked in tech finance stuff -- decentralization promise and power of AI was so cool -- modulus is leading company crafting zero knowledge proofs for ML inference - -#### Ben @ Gensyn -- machine learning compute protocol -- provide ability for anyone with ML capable compute device to offer that device to anyone in the world to train AI model -- pure hardware incentives -- previously ML researcher - -#### Casey -- ML work at google as engineer -- partner at Paradigm - -- most important now? -- smart contracts can’t harness power of AI -- missing key functionality that web2 has which is power of AI -- bc AI models are huge -- billions of parameters, gigaflops to teraflops of compute to perform -- gas cost on L2s cost 10s of thousands to millions to run single inference in trustless manner -- zero knowledge proof -- proof cf correct computation +New Readme From d216b7971e49134a513c01a133c1d26bbcbbcb47 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Tue, 13 Feb 2024 00:00:02 -0400 Subject: [PATCH 010/129] Update DeAI Summit 01.md Notes from first Decentralized AI Summit. --- DeAI Summit 01.md | 565 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 565 insertions(+) diff --git a/DeAI Summit 01.md b/DeAI Summit 01.md index a07b092..a4608cb 100644 --- a/DeAI Summit 01.md +++ b/DeAI Summit 01.md @@ -1,2 +1,567 @@ # Decentralized AI Summit held in Austin, TX on December 9th 2023 +![DAI-ecosystem](https://github.com/DecentralizeAI/MRC/assets/76454555/d4be1474-3046-4fc3-8803-a880038b78aa) + +# Building Decentralized AI + +On December 9, 2023 the Decentralized AI community assembled from around the world at Kiretsu in Austin, Texas in order to begin contributing to this repository. + +The objectives are to define: +- 1. The tech stack for Decentralized AI +- 2. Practical technical standards for collaboration within in the community. + +Morpheus encourages and will incentivize developers who propose or implement new standards/integrations between open source projects in DeAI. + +Live Journal + +## Morpheus - David A. Johnston +- Website: +- Github: +- David's X Profile: + +Morpheus is designed to incentivize the first peer-to-peer network of personal AIs, known as Smart Agents. Providing users open-source Smart Agents to connect to their wallets, Dapps, & smart contracts promises to open the world of Web3 to everyone. + +**Key points:** + +- 230 days left until July 26, 2024 - the date the commerce department is mandated to deterine if open source wieghts conssttiute munitions +- EO signed on October 31st +- Limits number of parameters models can have + - limit for permissionless models at 10B parametrs and only 20gigs + - KYC for data centers +- Only an 8 month timeline to build open source tech stack + +- permissionless building is the heart of what we’re trying to do + +- Phil Zimmerman is the patron saint of decentralized AI + - In 1991, a bill was introduced to ban encryption for email, so Phil introduced PGP, because privacy is a human right + - He printed his work on a t shirt and was arrested for disclosing the RSA algorithm. + - Won in supreme court based on free speech grounds, who recognized that code and speech were protected +- This is why your email can legally be have private +- A few weeks ago in SF the Keep AI Open event was announced and within 48 hours >700 people showed up at the end of OpenAI's dev day +- Marc Andreessen is constantly posting memes for decentralized AI + - the right tot bear compute + - come and take it +- Balaji Tweet: + "free internet means free AI + we will fight government control over compute with everything we have" +- Morpheus is decentralized open source AI, and the tech stack for decentralized AI + - anonymous group dropped paper in September + - within 45 days community had built implementation + - live now can run on computer locally + - fully open source LLM running on your data + - MOR smart contracts entering testnet today +- We want this to continue beyond today + - join discord + - channel for every project os people can follow up with questions + - engage with everyone building models, fine tuning, agents, every part of tech stack +- The goal is 1 billion users for decentralized AI + - AI is the opportunity to get a billion people into crypto by removing technical barriers to access web3 + - With AI, we build off the expressed intent, + - On Morpheus, it knows what smart contracts are available +- The AI community: needs censorship resistant compute and tools to monetize agents + +## Anna Zazlauskas - Vana + +Vana: Own your data + +***Key points*** + +- data ownership +- goal: world where users own data and value it creates +- initial belief: token incentives enable large scale RLHF and data labelling + - people who want to sell data do so out of desperation + - not the best dataset + - uphill fraud battle + - people constantly finding ways to sell bad data + - people who want to sell data for financial reward are not representative + - mostly doing out of financial desperation + - users choose products that align with ideologies, value privacy and agency +- Reality: + - users choose whatever is most convenient or capable. privacy/security are afterthoughts. + - slacktivism + +- initial belief: data ownership legislation like GDPR and CCP will help. + - regulation favors consumers. +- learning: even if users have a legal right ot data, it is inconvenient to access. users have to be very motivated. + - regulation favors incumbent. + +- you can ask for your labels on instagram + +- On Vana: + - make a personal data tangible through a personalized ai model + - bring your model with you throughout internet + - users host their own nodes or opt for a convenient hosted option + - private data stays on user's node, while third party apps run inference. + - granular permissions so you can let people access your data or models. + +- Modalities: + - image: train lora based on 10 photos of yourself + - text: personality + memory stream from your social data and messages + - audio( hosted) based on 1min of your voice + - best audio models are closed source (?) + +- memory architecture + - query memories based on relevance, important, and recency + - summarize relevant memories to fit in context window + - for more, read Generative Agents: Interactive Simulacra of Human Behavior + +- bootstrapped network by building viral consumer applications in house + - 1.2M users + - 700k private models trained + - 10M personal data points + +- collective models + - users contribute data to models they collectively own and govern + - users decide who can access the model, how much to charge, how it can be used + - each collective has its own node, similar to a user’s node + +- host your own vana node + - connect your social data, journal entries, messages, other personal data with an ally that deeply understand you + - everything stays on yoru machine + - can open up an endpoint to use it throughout apps + - reach out to to try this out + +## Ritual - Niraj + +Integrate AI models into your protocol, application or smart contract with a few lines of code. + +Described a global statistical computer. + +__Key Points:__ +- motivation: + - ai is eating the world + - usage going up massively + - decentralized intelligence improving + +*problems of AI today:* +- infrastructure highly centralized + - model storage + - model governance and ownership (e.g. OAI fiasco) + - model compute (training, inference, fine tuning, etc) + - access to training data +- ai infra is highly permissioned + - high costs ot using/improving AI + - permissioned centralized APIs to access + - no privacy/computational integrity censorship resistance + - most OSS models are highly red-teamed/censored + - many geographical limitations +- AI infra is increasingly regulated + - ai incumbents and governments attempting strong regulatory capture + - “we know what’s in your best interests” + +- future impact + - as AI gets inserted into every tech product, new forms of censorship/manipulation ill take place + - LLMs and other foundation models create highly engaging forms of propaganda (e.g. 2024 US election media) + - political ideology weaponized by who controls distribution and access to models + - open and transparent governance of AI models is key + - “who controls models controls the world” + +*AI x Crypto to the rescue* +- AI is highly centralizing tech +- crypto is highly decentralizing tech +- combining both solves aforementioned problems +- trustlessness + intelligence = ???won’t be evil -> can’t b evil +- if we’ve decentralized money, music, property records, etc, why not AI? + +At Ritual: +- how do we get AI into hands of crypto devs today +- combine best of ai and crypto to make it easy for devs to build crypto x ai products +- model specific computational integrity (opML and zkmlO +- privacy (FHE for classical ML models, MPC for foundation models) +- ritual AI VM with stateful precompiles for various model operations (inference, FT, quantization, embeddings) +- supports Ethereum base chain and rollups, alt L1 support coming in 2024 + +- tech pillars + - censorship resistance and decentralization + - privacy + - computational integrity + - incentives + +- infernet: network for inference + - take smart contract, plug into model + - allows you to customize infra + - set up nodes yourself, run inference for your products + +- frenrug + - on-chain smart agent that buys and sells friend.tech keys if you can convince it + - built on internet SDKs + - internet llm nodes generate responses, feeds into on-chain classifier (with ezkl proof)github.com/frenrug/contracts + - frenrug.com + +


+ +## Akash Network - Greg Osuri + +Akash is open-source Supercloud that lets users buy and sell computing resources securely and efficiently. Purpose-built for public utility. + +Greg's demo showcased the options available on the network and the ability to spin up new services. + + + + +**Key points** +- GPUs are hard to get on demand +github.com/akash-network/community + +- console.akash.network/analytics + +- e.g. 1k/mo H100 +https://pixart-alpha.github.io/ + +- ray compatible + +- a100 utilization 95% + +- $300m incentives coming online next year + +## Agora Labs - Anish + +Cloud-agnostic MLOps/LLMOps platform powered by cheap, decentralized compute. + + + +### render network + +**Key points** +- OG in crypto space +- pioneered first use case for GPUs +- process of rendering is converting 3d model into pixels +- takes a lot of compute power +- used to take a day +- goal to provide fast, affordable rendering +- 25M frames rendered on network to date +- waitlist of GPUs over a million long + +@drjonessf + +BitTensor + +- Beff Jezos' Thermodynamic computer + +- AHaH Controller + - a trillion synapses per clock cycle + - energy based not transistor based + +- Instead of loss landscapes, lowering error + - Let’s build incentive landscapes, get more profit + - Pay them not for adapting weights but all sorts of things + +- Lower error on neural network +- Faster inference +- better gradients +- more information + +- get paid for having GA lower loss +- sucking up compute and innovation +- passed OpenAI’s loss on GPT2 (trained in 2016) +- 31.39 vs 34.9 perplexity + +bittensor.com/docs +https://docs.bittensor.com/ + +FreedomGPT + +- SmarterChild: conversational AI +- robot you could talk to on AOL IM when no one was there + - pretty dumb + - step above a Liza + - you could make your own, have it talk to other people, look at conversations + - sometimes it would say “i’m not going to answer that” + - chilling effect + - happening again now + +- sold mutual mobile a year ago +- 400 person a year go making dgitial products for f1000 +- did a lot with AI +- sold it, started playing with ChatGPT about a year ago +- had birthday party for chatgpt last week +- a year ago decided to create FreedomGPT +- app store for AI +- first model: trying to get to parity of ChatGPT using Luna, 3d gradient descent +- model would answer anything +- 2 million people trying it out + +- as capability increase, censorship and prohibition increase + +- as capability increases, privacy and liberty decreases don’t use it if you’re not sure things will remain private + +- they will make it illegal to access under penalty of death (treason) + +- midjourney bans Xi, Jinping + +-------- + +- technology is what allows freedom to exist +- belief: freedom is assured by documents +- reality” freedom assured by access to sufficiently advanced knowledge & technology over +- those wanting ot take your freedom away + +- these are munitions we need them otherwise they will be used against us and they already are + +- fall of Constantinople by ottoman empire - gunpowder + +- Gutenberg printing press caused nation to fall and US became independent + +- war of 1812, attacked library of congress where books were + +- those that start by burning books, will end by burning men heinrich heine + +- how much more powerful is AI than books? 10x?1000x? + +- thought experiment + - imagine an AI that people star tto trust nearly 100% of the time + + - the problem isn’t if AI says something incorrect it’s as if AI starts saying too many correct things + + - e.g. “ted cdruz is zodiac killer” + +- our predictions + - ai public/private censorship timeline + + - 18 months (may 2025) accessing many AIs in the US will be on par with +- pharmaceutical RXs (if you can prove you need it, you can access) + - 24 months, powerful AIs will require a process similar to obtaining a firearm with background checks and waiting periods. + - misuse will result in permanent revocation. numerous AIs will be banned from being indexed in search engine or even mentioned by the AIs that re deemed “publicly safe” + +- Within 36 months, access to most powerful AIs will be restricted + +- decentralizing freedom of compute because there is no other option + +- freedom != free +- open sourced project reached #3 ranking on github +- over 700k installs of free desktop app +- cloud version generates $1k daily revenue +- banned from multiple hosting providers +- cease and desist from twitter/x and other +- prohibited from being discussed on facebook/meta properties +- +40 multimodal AI models with plans for 4k in 2023 +- tons of hate mail and threats to get us shut down + +- shortly after launching TwitterGPT, got banned (after elon acquisition) +now back on twitter + +- team background + - created products currently used by over a billion monthly users + - collectively hired over 1k engineers/designers/PMs since founding mutual mobile + - built +250MM in digital products for companies like google nike, and dozens of banks + - built dozens of ML/predictive analytics solutions + +- 2 groups of users + - ~3k paid + - ~400k free + +- plan is to start paying those nodes +- been cancelled from multiple web hosts +- one is now allowing us +- matter of time before they pull the plug + +- freedomgpt-git-edge-node-ageofaicapital-s-team.vercel.app +- https://edge.freedomgpt.com/?ref=node-signup +- earn $30/day running inference + +## EdgeLLama + +### Varun Mathur + +EdgeLLama, and the associated set of products, which lead to a seamless AI consumer-cloud will impose a similar abundant forcing function on AI as well. You can go ahead and cancel your $20/month Pro plans, because this next wave of AI, runs in your laptops, desktops and smartphones, and is good enough. + +

+ + +## Nous Research +Self-Improving AI
 +Nous Research is a private applied research group. We publish open-source work in the LLM domain, including local models, datasets, and core architectural improvements. + +The demo included a walkthrough of the Nous software. It showed the ability to build AI via drag and drop. Am explanation of their research described YaRN, Hermes, Obsidian, and Capybara. + +**Key points** + +- Started three years ago +- four founders crypto people who found AI in different ways +- “fuck openAI” brought them together +- what can we do to open up again +- not negative, pushing against them +- provide a space for more humanistic AI +- 6 full time contributors +- 48 volunteer AI researchers +- thousands of contributors + +- open source modles + - OpenHermes 2.5 + - top used 7b + - capybara + - 34b amplify-instruct + - obsidian + - stablelm + openclip + capybara + +- open research +- yarn +- muse: generative CoT reward model +- vulcan: chatML extension +- SYNTHIA + +- Nous Forge + - desktop app for interfacing with and composing open source and other AI models +- Obsidian multi-modal model + - focussed on edge devices + + + +most robust agents are breaking after 5 runs + + +

+ +## io.net - Angela Yi + +- io.net is a state-of-the-art decentralized computing network that allows machine learning engineers to access distributed Cloud clusters at a small fraction of the cost of comparable centralized services. + +- io.net deploys GPU clusters from multiple locations that are not constrained by colocated devices. The platform supports clusters of any scale, allowing engineers to deploy a 20K GPU cluster within seconds. + +io.net has 3 key elements: + 1. IO Cloud, where engineers can seamlessly deploy their GPU clusters. + 2. IO Workers, where suppliers can connect their devices, monitor their performance, and keep track of their earnings and rewards. + 3. IO Explorer, where we provide transparent, real-time information on pricing, as well as devices and clusters, and inferences powered through our network. + + + + + +## Commune AI + +Commune is a protocol that aims to connect all developer tools into one network, fostering a more shareable, reusable, and open economy. It follows an inclusive design philosophy that is based on being maximally unopinionated. This means that developers can leverage Commune as a versatile set of tools alongside their existing projects and have the freedom to incorporate additional tools that they find valuable. + + + +### Upshot - Nick Evans + +- Upshot: AI Network optimzied for financial applications +- powered by proof opf alpha protocol +- reward people by how useful for financial markets + +- why focus on financial pplications? + - build tools that can enable creation fo financial markets for anything + - riskless society + - efficient enough markest that every risk can be hedged + - cryp is olargely financial innovation + - financialization has been one of main usec ases + - more conducive for trustless/verifiable form factors + +- bacgkground + - upshot one: peer prediction protocol for incentivizing honest responses to subjective questions + - DMI Mcehanism: + - dominantly truthful: truth tellling is dominant strategy + - informed ftruthful: truth telling is stricftly better than uinformative strategies + - detail free: does not require prior knowledge to be inputted by mechanism designer + - constant: only a constant number of questions and agents are required for it to be both dominantly truthful and informed-truthful + +- findings + - peer prediction doe simprove truth teslling incentives + - network of human eactors lacks accuracy and scalability + +- Upshot AI x Crypto Tooling + - AI infrastructure for price predictions, network analyses, yield strategies, etc. + - 2-5% MAPE (mean absolute percentage error) + - 394m assets supported + - <5 min update cadence +- findings + - validated hypothesis around demand for AI x crypto systems + - single entity creating models introduces scalability constraints and security rsisk + +- solution + - combine peer prediction protocol and AI x Crypto infra to build decentralized AI network optimized for financial applications + +Upshot: + - alpha miners establish contractual agreements on chain with dat providers + - results in rev sharing from alpha minor work + - share predictions with each other regularly + - score each other’s predictions, leveraging peer prediction mechanism + - incentivize them to share evaluations honestly + +- big graph broken by topics + - topic is defined by objective that is being collaoratively solved + - output: mmeta model + - data providers establish edges with alpha providers + - alpha minors share predictions with each other, score predictions, scores aggregated, rewards distributed based on proof of alpha + +- zkPredictor + - alpha minors can pass around proofs verifying output of their work is result of underlying model they’re advertising + - ensures tamper proof models + - zkSNARK proof system optimized for tree-based models + - verifies output of initial models on upshot network approaching 10k predictions per hour + +Robonet: +- fist application that builds on Upshot and zkPredictor +- DeFi vaults with AI-Powered Yield Strategies +- smart contracts are limited compute environments +- AI is better at making sense of large amounts of data + + 1. users deposit capital into robonet vaults. + 2. 2 strategies are instantiated as “optics” on upshot network + 3. upshot + 4. fees are shared between upshot peers contributing to the strategies and capital providers + +- people who have unique insights no longer need capital or structure to profit off insights + +- benefits + - more diverse, expressive strategies + - support for more long tail categories + - cryptographically verified models + - potential for much higher yield + +http://upshot.xyz + + +## Actioneer - David Orban + +Dignity and purpose for 8 billion humans in an age of AI + + + + +## OpenCog Hyperon + +The open-source software framework bringing together multiple AI paradigms in a cognitive architecture oriented toward AGI at the human level and beyond + + + + +## Hypercycle + +HyperCycle is building a tiny but essential component that enables AI Machines to transact with other AI machines in a sub-second finality which results in unprecedented emergence. + + + +## The Lifted Initiative + +### Eric Bravick + +The Lifted Initiative is building a comprehensive web3 native cloud with a focus on easy to use tooling. We've launched about 17 product and service groups to date into private Beta, including support of AI use cases. We go public in 2024 and we are currently seeking integrations with other AI focused networks. We believe strongly in decentralization of networks (multi-network approaches) and will be embracing a wide array of partnerships rather than a "build it all on one chain" philosophy. + + + +##Pannel Discussion +#### Ryan @ Modulus Labs +- previously AI research at Stanford +- worked in tech finance stuff +- decentralization promise and power of AI was so cool +- modulus is leading company crafting zero knowledge proofs for ML inference + +#### Ben @ Gensyn +- machine learning compute protocol +- provide ability for anyone with ML capable compute device to offer that device to anyone in the world to train AI model +- pure hardware incentives +- previously ML researcher + +#### Casey +- ML work at google as engineer +- partner at Paradigm + +- most important now? +- smart contracts can’t harness power of AI +- missing key functionality that web2 has which is power of AI +- bc AI models are huge +- billions of parameters, gigaflops to teraflops of compute to perform +- gas cost on L2s cost 10s of thousands to millions to run single inference in trustless manner +- zero knowledge proof +- proof cf correct computation From bad368279701b5b6b54aafbc8b71c0c461e2b8e9 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Tue, 13 Feb 2024 00:01:23 -0400 Subject: [PATCH 011/129] Update README.md Details on the existing MRC proposals for the Readme. --- README.md | 37 ++++++++++++++++++++++++++++++++++++- 1 file changed, 36 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index a7aa5ff..8ca1f71 100644 --- a/README.md +++ b/README.md @@ -1 +1,36 @@ -New Readme +# Morpheus Request for Comments (MRC) +List of proposals extending Decentralized AI. Similar to the function of the ERC system serves in Ethereum. https://eips.ethereum.org/erc Provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. + +## List of MRCs: + +## MRC 00: Smart Agents White Paper. +- Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. +- Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/White%20Paper.md + +## MRC 01: Smart Agenets Yellow Paper. +- Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. +- Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/YellowPaper.md + +## MRC 02: Morpheus White Paper. +- Status: **Adopted** by the Morpheus community as basis for Morpheus Network. +- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/2.WhitePaper.md + +## MRC 03: Morpheus Yellow Paper. +- Status: **In Progress**, Being implimented as the basis for Capital, Code, Compute and Community Builders. +- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/3.YellowPaper.md + +## MRC 05: Yellowstone Compute Model. +- Status: **In Progress**, Being implimented as the Decentralized Router for the launch of Compute rewards post bootstrapping period. +- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md + +## MRC 06: Techno Capital Machine +- Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. +- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/4.TechnoCapitalMachineTCM.md + +## MRC 07: Fair Launch Process +- Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. +- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/5.FairLaunch.md + +## MRC 08: Waterloo Community Model. +- Status: **Under Discussion**, needs additional work to flush out the concepts. +- Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing From e3936d3d43dc496f31d8513a32c179245f999913 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Tue, 13 Feb 2024 00:02:00 -0400 Subject: [PATCH 012/129] Update README.md Spelling correction. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 8ca1f71..abd6618 100644 --- a/README.md +++ b/README.md @@ -7,7 +7,7 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC - Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. - Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/White%20Paper.md -## MRC 01: Smart Agenets Yellow Paper. +## MRC 01: Smart Agents Yellow Paper. - Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. - Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/YellowPaper.md From 40f5b92d76085ba295a76d6dad0b564b9a8b43b7 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Thu, 22 Feb 2024 20:36:58 +0200 Subject: [PATCH 013/129] Update README.md --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index abd6618..39babbd 100644 --- a/README.md +++ b/README.md @@ -13,23 +13,23 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 02: Morpheus White Paper. - Status: **Adopted** by the Morpheus community as basis for Morpheus Network. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/2.WhitePaper.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/WhitePaper.md ## MRC 03: Morpheus Yellow Paper. - Status: **In Progress**, Being implimented as the basis for Capital, Code, Compute and Community Builders. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/3.YellowPaper.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/YellowPaper.md ## MRC 05: Yellowstone Compute Model. - Status: **In Progress**, Being implimented as the Decentralized Router for the launch of Compute rewards post bootstrapping period. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Yellowstone%20Compute%20Model.md ## MRC 06: Techno Capital Machine - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/4.TechnoCapitalMachineTCM.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md ## MRC 07: Fair Launch Process - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/5.FairLaunch.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Fair%20Launch.md ## MRC 08: Waterloo Community Model. - Status: **Under Discussion**, needs additional work to flush out the concepts. From df3a93204b5ec32bd560a2fffb9dfd3231ac78c5 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Sun, 25 Feb 2024 23:24:41 +0200 Subject: [PATCH 014/129] Update Morpheus Request For Comments (MRC).md --- Morpheus Request For Comments (MRC).md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index 8d97582..993b501 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -23,11 +23,11 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC - Status: **In Progress**, Being implimented as the Decentralized Router for the launch of Compute rewards post bootstrapping period. - Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md -## MRC 06: Techno Capital Machine +## MRC 06: Techno Capital Machine. - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. - Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/4.TechnoCapitalMachineTCM.md -## MRC 07: Fair Launch Process +## MRC 07: Fair Launch Process. - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. - Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/5.FairLaunch.md @@ -35,3 +35,7 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC - Status: **Under Discussion**, needs additional work to flush out the concepts. - Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing +## MRC 09: Fair Price Discovery and AMM Initiation +- Status: **Under Discussion**, needs more feedback from wider community. +- Link: https://docs.google.com/document/d/1PYeWnu3KpQdExwwuKFgGbRl9eajc6oP1poEQZmf7S2w/edit?usp=sharing + From 44457ea87c128cc8a788c24c0d84c84e45f50816 Mon Sep 17 00:00:00 2001 From: "Emmanuel B. Giwa" Date: Thu, 29 Feb 2024 16:18:17 +0100 Subject: [PATCH 015/129] add comment for agent marketplace --- Morpheus Request For Comments (MRC).md | 6 +++++- README.md | 4 ++++ 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index 8d97582..fd5d0d9 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -21,7 +21,7 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 05: Yellowstone Compute Model. - Status: **In Progress**, Being implimented as the Decentralized Router for the launch of Compute rewards post bootstrapping period. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md +- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md ## MRC 06: Techno Capital Machine - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. @@ -35,3 +35,7 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC - Status: **Under Discussion**, needs additional work to flush out the concepts. - Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing +## MRC 09: Development of Smart Agent Tools Marketplace. +- Status: **Under Discussion**, needs further discussion and approval. +- Link: https://docs.google.com/document/d/1JJQR4-b63VbJQ_etSt5Poyk1KcK3f7FvUZcwKB5Zpk8/edit?usp=sharing + diff --git a/README.md b/README.md index 39babbd..b3f3bd3 100644 --- a/README.md +++ b/README.md @@ -34,3 +34,7 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 08: Waterloo Community Model. - Status: **Under Discussion**, needs additional work to flush out the concepts. - Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing + +## MRC 09: Development of Smart Agent Tools Marketplace. +- Status: **Under Discussion**, needs further discussion and approval. +- Link: https://docs.google.com/document/d/1JJQR4-b63VbJQ_etSt5Poyk1KcK3f7FvUZcwKB5Zpk8/edit?usp=sharing From 0de0107b7f6cf082421b1f5761f91aed7d53e757 Mon Sep 17 00:00:00 2001 From: "Emmanuel B. Giwa" Date: Thu, 29 Feb 2024 16:21:25 +0100 Subject: [PATCH 016/129] update MRC to 10 --- Morpheus Request For Comments (MRC).md | 2 +- README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index fd5d0d9..952a842 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -35,7 +35,7 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC - Status: **Under Discussion**, needs additional work to flush out the concepts. - Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing -## MRC 09: Development of Smart Agent Tools Marketplace. +## MRC 10: Development of Smart Agent Tools Marketplace. - Status: **Under Discussion**, needs further discussion and approval. - Link: https://docs.google.com/document/d/1JJQR4-b63VbJQ_etSt5Poyk1KcK3f7FvUZcwKB5Zpk8/edit?usp=sharing diff --git a/README.md b/README.md index b3f3bd3..12357b2 100644 --- a/README.md +++ b/README.md @@ -35,6 +35,6 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC - Status: **Under Discussion**, needs additional work to flush out the concepts. - Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing -## MRC 09: Development of Smart Agent Tools Marketplace. +## MRC 10: Development of Smart Agent Tools Marketplace. - Status: **Under Discussion**, needs further discussion and approval. - Link: https://docs.google.com/document/d/1JJQR4-b63VbJQ_etSt5Poyk1KcK3f7FvUZcwKB5Zpk8/edit?usp=sharing From c31781b7e710356daebf720f269a28df38f166bf Mon Sep 17 00:00:00 2001 From: "Emmanuel B. Giwa" Date: Thu, 29 Feb 2024 16:44:41 +0100 Subject: [PATCH 017/129] proposal for Morpheus Multi-Agent Framework --- Morpheus Request For Comments (MRC).md | 6 +++++- README.md | 4 ++++ 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index 8d97582..f1f512a 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -21,7 +21,7 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 05: Yellowstone Compute Model. - Status: **In Progress**, Being implimented as the Decentralized Router for the launch of Compute rewards post bootstrapping period. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md +- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md ## MRC 06: Techno Capital Machine - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. @@ -35,3 +35,7 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC - Status: **Under Discussion**, needs additional work to flush out the concepts. - Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing +## MRC 11: Morpheus Multi-Agent Framework. +- Status: **Under Discussion**, needs further discussion to cover edge cases. +- Link: https://docs.google.com/document/d/1i6FBD7OIMEHSYMgKUGmrjpxgnlFN20JRC4_yW9bAVWw/edit?usp=sharing + diff --git a/README.md b/README.md index 39babbd..0dec4c6 100644 --- a/README.md +++ b/README.md @@ -34,3 +34,7 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 08: Waterloo Community Model. - Status: **Under Discussion**, needs additional work to flush out the concepts. - Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing + +## MRC 11: Morpheus Multi-Agent Framework. +- Status: **Under Discussion**, needs further discussion to cover edge cases. +- Link: https://docs.google.com/document/d/1i6FBD7OIMEHSYMgKUGmrjpxgnlFN20JRC4_yW9bAVWw/edit?usp=sharing From cc5871a7b3fe36e0dbd89dc656487d7142b4dfb8 Mon Sep 17 00:00:00 2001 From: "Emmanuel B. Giwa" Date: Thu, 29 Feb 2024 17:03:37 +0100 Subject: [PATCH 018/129] proposal for Capital contracts expansion to stMATIC --- Morpheus Request For Comments (MRC).md | 5 ++++- README.md | 4 ++++ 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index 8d97582..5cad137 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -21,7 +21,7 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 05: Yellowstone Compute Model. - Status: **In Progress**, Being implimented as the Decentralized Router for the launch of Compute rewards post bootstrapping period. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md +- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md ## MRC 06: Techno Capital Machine - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. @@ -35,3 +35,6 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC - Status: **Under Discussion**, needs additional work to flush out the concepts. - Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing +## MRC 12: Capital contracts expansion to stMATIC. +- Status: **Under Discussion**, needs further discussion to cover all edge cases and flesh out more concepts. +- Link: https://docs.google.com/document/d/1lZ_vJ3exkrn8DscHI6C59unp5Lui895rtN4nc-e2wso/edit?usp=sharing diff --git a/README.md b/README.md index 39babbd..617328f 100644 --- a/README.md +++ b/README.md @@ -34,3 +34,7 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 08: Waterloo Community Model. - Status: **Under Discussion**, needs additional work to flush out the concepts. - Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing + +## MRC 12: Capital contracts expansion to stMATIC. +- Status: **Under Discussion**, needs further discussion to cover all edge cases and flesh out more concepts. +- Link: https://docs.google.com/document/d/1lZ_vJ3exkrn8DscHI6C59unp5Lui895rtN4nc-e2wso/edit?usp=sharing From 3da61a629ef4ff442d5a5d2e13a794fec44592d9 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Sat, 2 Mar 2024 17:05:25 +0200 Subject: [PATCH 019/129] Update Morpheus Request For Comments (MRC).md --- Morpheus Request For Comments (MRC).md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index 993b501..da71571 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -7,29 +7,29 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC - Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. - Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/White%20Paper.md -## MRC 01: Smart Agenets Yellow Paper. +## MRC 01: Smart Agents Yellow Paper. - Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. - Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/YellowPaper.md ## MRC 02: Morpheus White Paper. - Status: **Adopted** by the Morpheus community as basis for Morpheus Network. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/2.WhitePaper.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/WhitePaper.md ## MRC 03: Morpheus Yellow Paper. -- Status: **In Progress**, Being implimented as the basis for Capital, Code, Compute and Community Builders. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/3.YellowPaper.md +- Status: **Adopted**, Being implemented as the basis for Capital, Code, Compute and Community Builders. +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/YellowPaper.md ## MRC 05: Yellowstone Compute Model. - Status: **In Progress**, Being implimented as the Decentralized Router for the launch of Compute rewards post bootstrapping period. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Yellowstone%20Compute%20Model.md ## MRC 06: Techno Capital Machine. - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/4.TechnoCapitalMachineTCM.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md ## MRC 07: Fair Launch Process. - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/5.FairLaunch.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Fair%20Launch.md ## MRC 08: Waterloo Community Model. - Status: **Under Discussion**, needs additional work to flush out the concepts. From fa4be22fe57d0523b1268aa23c8c62c585b6076c Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Sat, 2 Mar 2024 17:05:52 +0200 Subject: [PATCH 020/129] Update README.md --- README.md | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index abd6618..8b159da 100644 --- a/README.md +++ b/README.md @@ -13,24 +13,28 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 02: Morpheus White Paper. - Status: **Adopted** by the Morpheus community as basis for Morpheus Network. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/2.WhitePaper.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/WhitePaper.md ## MRC 03: Morpheus Yellow Paper. -- Status: **In Progress**, Being implimented as the basis for Capital, Code, Compute and Community Builders. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/3.YellowPaper.md +- Status: **Adopted**, Being implemented as the basis for Capital, Code, Compute and Community Builders. +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/YellowPaper.md ## MRC 05: Yellowstone Compute Model. - Status: **In Progress**, Being implimented as the Decentralized Router for the launch of Compute rewards post bootstrapping period. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/7.Yellowstone%20Compute%20Model.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Yellowstone%20Compute%20Model.md -## MRC 06: Techno Capital Machine +## MRC 06: Techno Capital Machine. - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/4.TechnoCapitalMachineTCM.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md -## MRC 07: Fair Launch Process +## MRC 07: Fair Launch Process. - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. -- Link: https://github.com/MorpheusAIs/Morpheus/blob/main/!KEYDOCS%20README%20FIRST!/5.FairLaunch.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Fair%20Launch.md ## MRC 08: Waterloo Community Model. - Status: **Under Discussion**, needs additional work to flush out the concepts. - Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing + +## MRC 09: Fair Price Discovery and AMM Initiation +- Status: **Under Discussion**, needs more feedback from wider community. +- Link: https://docs.google.com/document/d/1PYeWnu3KpQdExwwuKFgGbRl9eajc6oP1poEQZmf7S2w/edit?usp=sharing From f22912a762897e3c6f4f3f72334600f83da1fdf0 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Sat, 2 Mar 2024 17:07:39 +0200 Subject: [PATCH 021/129] Update README.md --- README.md | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index 8b159da..39babbd 100644 --- a/README.md +++ b/README.md @@ -13,28 +13,24 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 02: Morpheus White Paper. - Status: **Adopted** by the Morpheus community as basis for Morpheus Network. -- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/WhitePaper.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/WhitePaper.md ## MRC 03: Morpheus Yellow Paper. -- Status: **Adopted**, Being implemented as the basis for Capital, Code, Compute and Community Builders. +- Status: **In Progress**, Being implimented as the basis for Capital, Code, Compute and Community Builders. - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/YellowPaper.md ## MRC 05: Yellowstone Compute Model. - Status: **In Progress**, Being implimented as the Decentralized Router for the launch of Compute rewards post bootstrapping period. -- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Yellowstone%20Compute%20Model.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Yellowstone%20Compute%20Model.md -## MRC 06: Techno Capital Machine. +## MRC 06: Techno Capital Machine - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md -## MRC 07: Fair Launch Process. +## MRC 07: Fair Launch Process - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Fair%20Launch.md ## MRC 08: Waterloo Community Model. - Status: **Under Discussion**, needs additional work to flush out the concepts. - Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing - -## MRC 09: Fair Price Discovery and AMM Initiation -- Status: **Under Discussion**, needs more feedback from wider community. -- Link: https://docs.google.com/document/d/1PYeWnu3KpQdExwwuKFgGbRl9eajc6oP1poEQZmf7S2w/edit?usp=sharing From fc79d0a7ebeb8660c7768b5492dd1ca9eed8b455 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Thu, 7 Mar 2024 15:36:06 +0200 Subject: [PATCH 022/129] Update README.md --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 8f31cfc..17a00da 100644 --- a/README.md +++ b/README.md @@ -35,6 +35,10 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC - Status: **Under Discussion**, needs additional work to flush out the concepts. - Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing +## MRC 09: Fair Price Discovery and AMM Initiation +- Status: **Under Discussion**, needs more feedback from wider community. +- Link: https://docs.google.com/document/d/1PYeWnu3KpQdExwwuKFgGbRl9eajc6oP1poEQZmf7S2w/edit?usp=sharing + ## MRC 10: Development of Smart Agent Tools Marketplace. - Status: **Under Discussion**, needs further discussion and approval. - Link: https://docs.google.com/document/d/1JJQR4-b63VbJQ_etSt5Poyk1KcK3f7FvUZcwKB5Zpk8/edit?usp=sharing From 13b389d2e7109139c4a227a723497edb09c6d292 Mon Sep 17 00:00:00 2001 From: generativeone <162616095+generativeone@users.noreply.github.com> Date: Thu, 7 Mar 2024 23:17:52 +0400 Subject: [PATCH 023/129] Update README.md --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 8f31cfc..c691a37 100644 --- a/README.md +++ b/README.md @@ -35,6 +35,10 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC - Status: **Under Discussion**, needs additional work to flush out the concepts. - Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing +## MRC 09: AMM Launch Process +- Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. +- Link: https://github.com/generativeone/Docs/blob/main/Building%20the%20Foundation%20-%20AMM%20Launch.md + ## MRC 10: Development of Smart Agent Tools Marketplace. - Status: **Under Discussion**, needs further discussion and approval. - Link: https://docs.google.com/document/d/1JJQR4-b63VbJQ_etSt5Poyk1KcK3f7FvUZcwKB5Zpk8/edit?usp=sharing From 63ae6623ab2acdaf2b671b750e13801f991ef995 Mon Sep 17 00:00:00 2001 From: 0xMorphy <162737960+0xMorphy@users.noreply.github.com> Date: Fri, 8 Mar 2024 14:14:02 -0800 Subject: [PATCH 024/129] Add MRC 13: Launch TCM on Solana --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index c691a37..764c80f 100644 --- a/README.md +++ b/README.md @@ -50,3 +50,7 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 12: Capital contracts expansion to stMATIC. - Status: **Under Discussion**, needs further discussion to cover all edge cases and flesh out more concepts. - Link: https://docs.google.com/document/d/1lZ_vJ3exkrn8DscHI6C59unp5Lui895rtN4nc-e2wso/edit?usp=sharing + +## MRC 13: Launch TCM for MOR Yield Farming on Solana with JitoSOL and/or mSOL. +- Status: **Under Discussion**, needs further discussion to answer open questions (see end of doc) and approval. +- Link: https://0xmacro.notion.site/MRC-13-Launch-TCM-for-MOR-Yield-Farming-on-Solana-with-JitoSOL-and-or-mSOL-a0f9e2c0fa884aa590fe993c38bc627b From 733e68c53dc29c70aa191a93b83c88bb490c5c35 Mon Sep 17 00:00:00 2001 From: ScottBerenzweig <76454555+betterbrand@users.noreply.github.com> Date: Thu, 14 Mar 2024 09:49:06 -0700 Subject: [PATCH 025/129] Update README.md --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 764c80f..937bd3a 100644 --- a/README.md +++ b/README.md @@ -54,3 +54,7 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 13: Launch TCM for MOR Yield Farming on Solana with JitoSOL and/or mSOL. - Status: **Under Discussion**, needs further discussion to answer open questions (see end of doc) and approval. - Link: https://0xmacro.notion.site/MRC-13-Launch-TCM-for-MOR-Yield-Farming-on-Solana-with-JitoSOL-and-or-mSOL-a0f9e2c0fa884aa590fe993c38bc627b + +## MRC 14: Refactor Weights for Greater Granularity. +- Status: **In Progress**, Planned implementation for April 2024 weights. +- Link: https://docs.google.com/document/d/1_5WZSNZ8LDwrD-mWNR3HzZT4asYSHYeqHsybXvz302g/ From 1075704735cbdcebdb60f67fcb4276caf3362572 Mon Sep 17 00:00:00 2001 From: ScottBerenzweig <76454555+betterbrand@users.noreply.github.com> Date: Thu, 14 Mar 2024 09:50:22 -0700 Subject: [PATCH 026/129] Update Morpheus Request For Comments (MRC).md Added 13, 14 from MRC/README.MD --- Morpheus Request For Comments (MRC).md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index d530466..2f115e3 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -50,3 +50,11 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 12: Capital contracts expansion to stMATIC. - Status: **Under Discussion**, needs further discussion to cover all edge cases and flesh out more concepts. - Link: https://docs.google.com/document/d/1lZ_vJ3exkrn8DscHI6C59unp5Lui895rtN4nc-e2wso/edit?usp=sharing + +## MRC 13: Launch TCM for MOR Yield Farming on Solana with JitoSOL and/or mSOL. +- Status: **Under Discussion**, needs further discussion to answer open questions (see end of doc) and approval. +- Link: https://0xmacro.notion.site/MRC-13-Launch-TCM-for-MOR-Yield-Farming-on-Solana-with-JitoSOL-and-or-mSOL-a0f9e2c0fa884aa590fe993c38bc627b + +## MRC 14: Refactor Weights for Greater Granularity. +- Status: **In Progress**, Planned implementation for April 2024 weights. +- Link: https://docs.google.com/document/d/1_5WZSNZ8LDwrD-mWNR3HzZT4asYSHYeqHsybXvz302g/ From d0dabfc7b59781d92f56998e4fa320ed08d944ba Mon Sep 17 00:00:00 2001 From: ScottBerenzweig <76454555+betterbrand@users.noreply.github.com> Date: Thu, 14 Mar 2024 20:27:54 -0700 Subject: [PATCH 027/129] Update README.md MRC 14: MOR MOR Weights for Greater Granularity --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 937bd3a..00e2254 100644 --- a/README.md +++ b/README.md @@ -55,6 +55,6 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC - Status: **Under Discussion**, needs further discussion to answer open questions (see end of doc) and approval. - Link: https://0xmacro.notion.site/MRC-13-Launch-TCM-for-MOR-Yield-Farming-on-Solana-with-JitoSOL-and-or-mSOL-a0f9e2c0fa884aa590fe993c38bc627b -## MRC 14: Refactor Weights for Greater Granularity. +## MRC 14: MOR MOR Weights for Greater Granularity. - Status: **In Progress**, Planned implementation for April 2024 weights. - Link: https://docs.google.com/document/d/1_5WZSNZ8LDwrD-mWNR3HzZT4asYSHYeqHsybXvz302g/ From 8f98780dcce63b8e9304341599a6fc9b93aaca2b Mon Sep 17 00:00:00 2001 From: ScottBerenzweig <76454555+betterbrand@users.noreply.github.com> Date: Thu, 14 Mar 2024 20:29:08 -0700 Subject: [PATCH 028/129] Update Morpheus Request For Comments (MRC).md MRC 14: MOR MOR Weights for Greater Granularity --- Morpheus Request For Comments (MRC).md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index 2f115e3..03b6f87 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -55,6 +55,6 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC - Status: **Under Discussion**, needs further discussion to answer open questions (see end of doc) and approval. - Link: https://0xmacro.notion.site/MRC-13-Launch-TCM-for-MOR-Yield-Farming-on-Solana-with-JitoSOL-and-or-mSOL-a0f9e2c0fa884aa590fe993c38bc627b -## MRC 14: Refactor Weights for Greater Granularity. +## MRC 14: MOR MOR Weights for Greater Granularity. - Status: **In Progress**, Planned implementation for April 2024 weights. - Link: https://docs.google.com/document/d/1_5WZSNZ8LDwrD-mWNR3HzZT4asYSHYeqHsybXvz302g/ From 3232f9bdadbca7adf5c73a54acf62873ba9865a7 Mon Sep 17 00:00:00 2001 From: generativeone <162616095+generativeone@users.noreply.github.com> Date: Fri, 15 Mar 2024 12:43:14 +0400 Subject: [PATCH 029/129] Update README.md --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 00e2254..6090490 100644 --- a/README.md +++ b/README.md @@ -58,3 +58,7 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 14: MOR MOR Weights for Greater Granularity. - Status: **In Progress**, Planned implementation for April 2024 weights. - Link: https://docs.google.com/document/d/1_5WZSNZ8LDwrD-mWNR3HzZT4asYSHYeqHsybXvz302g/ + +## MRC 15: A Framework for Adding Yield-Generating Assets. +- Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. +- Link: https://github.com/generativeone/Docs/blob/main/Expanding%20Horizon%20-%20The%20Morpheus%20Asset%20Integration%20Framework.md From abdf69fbc86d18200fb4a758da5575848e6245e5 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Fri, 15 Mar 2024 16:40:20 -0400 Subject: [PATCH 030/129] Update README.md --- README.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/README.md b/README.md index 6090490..1a28aec 100644 --- a/README.md +++ b/README.md @@ -62,3 +62,22 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 15: A Framework for Adding Yield-Generating Assets. - Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. - Link: https://github.com/generativeone/Docs/blob/main/Expanding%20Horizon%20-%20The%20Morpheus%20Asset%20Integration%20Framework.md + +## MRC 16: + +## MRC 17: + +## MRC 18: + +## MRC 19: + +## MRC 20: Framework for "Automated Recurring Revenue" (ARR) - The MOR 20 Token Standard +- Status: **Under Discussion** ## Automated Recurring Revenue (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 reacurring 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. +- Link: https://github.com/MorpheusAIs/Docs/blob/main/Contributions/Code%20-%20Proof_Of_ContributionSnapshot3.md From 5f2dd96b20b42a5f1f0f4ee629244201ee88648d Mon Sep 17 00:00:00 2001 From: David Johnston Date: Fri, 15 Mar 2024 16:41:25 -0400 Subject: [PATCH 031/129] Update README.md --- README.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 1a28aec..610be44 100644 --- a/README.md +++ b/README.md @@ -73,11 +73,11 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 20: Framework for "Automated Recurring Revenue" (ARR) - The MOR 20 Token Standard - Status: **Under Discussion** ## Automated Recurring Revenue (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 reacurring 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. +- Description: 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 reacurring 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. - Link: https://github.com/MorpheusAIs/Docs/blob/main/Contributions/Code%20-%20Proof_Of_ContributionSnapshot3.md From 6762da4b6d319061442c3ab930a0b016506191bb Mon Sep 17 00:00:00 2001 From: David Johnston Date: Fri, 15 Mar 2024 16:42:20 -0400 Subject: [PATCH 032/129] Update README.md From 178931d0f0fe20e2bef595a80735c8b420d5c698 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Fri, 15 Mar 2024 16:44:20 -0400 Subject: [PATCH 033/129] Update README.md Formatting. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 610be44..02da6a8 100644 --- a/README.md +++ b/README.md @@ -71,7 +71,7 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 19: -## MRC 20: Framework for "Automated Recurring Revenue" (ARR) - The MOR 20 Token Standard +## MRC 20: "Automated Recurring Revenue" (ARR) - The MOR 20 Token Standard - Status: **Under Discussion** ## Automated Recurring Revenue (ARR) Generalizing the TCM Model - MOR20 Token Standard - Description: 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. From 06066e61fb2a11347e3f486a021a53b8deda42a9 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Fri, 15 Mar 2024 16:45:26 -0400 Subject: [PATCH 034/129] Update README.md Formatting. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 02da6a8..d7268e3 100644 --- a/README.md +++ b/README.md @@ -72,7 +72,7 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 19: ## MRC 20: "Automated Recurring Revenue" (ARR) - The MOR 20 Token Standard -- Status: **Under Discussion** ## Automated Recurring Revenue (ARR) Generalizing the TCM Model - MOR20 Token Standard +- Status: **Under Discussion** Automated Recurring Revenue (ARR) Generalizing the TCM Model - MOR20 Token Standard - Description: 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. From ed6137593e6d53d5d285329405e5b3dd42b8c16f Mon Sep 17 00:00:00 2001 From: David Johnston Date: Fri, 15 Mar 2024 16:51:25 -0400 Subject: [PATCH 035/129] Update README.md Formatting. --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index d7268e3..e0c2f37 100644 --- a/README.md +++ b/README.md @@ -72,8 +72,9 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 19: ## MRC 20: "Automated Recurring Revenue" (ARR) - The MOR 20 Token Standard -- Status: **Under Discussion** Automated Recurring Revenue (ARR) Generalizing the TCM Model - MOR20 Token Standard -- Description: Any project inside or even outside the context of Web3 & AI, can use Morpheus to bootstrap their project with the push of a button. +- Status: **Under Discussion** +- Description: Automated Recurring Revenue (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 reacurring revenue / payments from users via yield. From 30e651f0c1580bd1b1d843ea31dcadf46c61d183 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Fri, 15 Mar 2024 17:04:28 -0400 Subject: [PATCH 036/129] Update README.md ARR - Revenue & Rewards --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index e0c2f37..1a027ae 100644 --- a/README.md +++ b/README.md @@ -71,9 +71,9 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC ## MRC 19: -## MRC 20: "Automated Recurring Revenue" (ARR) - The MOR 20 Token Standard +## MRC 20: "Automated Recurring Revenue / Rewards" (ARR) - The MOR 20 Token Standard - Status: **Under Discussion** -- Description: Automated Recurring Revenue (ARR) Generalizing the TCM Model - MOR20 Token Standard +- 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. From 07cf2ce375b3954b7ac8199dd2aa4be32f479058 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Fri, 15 Mar 2024 18:09:02 -0400 Subject: [PATCH 037/129] Update README.md Fixing link. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1a027ae..127f68d 100644 --- a/README.md +++ b/README.md @@ -81,4 +81,4 @@ This model can be extended to many software as a service projects as a means of 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. -- Link: https://github.com/MorpheusAIs/Docs/blob/main/Contributions/Code%20-%20Proof_Of_ContributionSnapshot3.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md#automated-recurring-revenue--rewards-arr-generalizing-the-tcm-model---mor20-token-standard From b4f5a127952ee5f492732bfa9261ad27858d95f9 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sat, 16 Mar 2024 00:02:33 -0400 Subject: [PATCH 038/129] Create MRC00.md Morpheus Request for Comment Standard format. --- MRC00.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 MRC00.md diff --git a/MRC00.md b/MRC00.md new file mode 100644 index 0000000..fef8c68 --- /dev/null +++ b/MRC00.md @@ -0,0 +1,22 @@ +## Morpheus Request for Comment Standard 00 + +Each Morpheus Request for Comment should include the following: + +- Problem +- Solution + Abstract + Development strategy + Tech Stack + +- End Results + +- Value To Users + +- New weights requested + +- Effort required to Implement + Deliverables + Meta + Time to expire + Dev Id assigned + Tie to deliverables/testing From d5324a5d7920437e6f6f2bc5a432e2df1ed94b91 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sat, 16 Mar 2024 00:04:51 -0400 Subject: [PATCH 039/129] Update README.md Update to include the Morpheus Request for Comment Standard at MRC00 --- README.md | 42 +++++++++++++++++++++++------------------- 1 file changed, 23 insertions(+), 19 deletions(-) diff --git a/README.md b/README.md index 127f68d..6002aec 100644 --- a/README.md +++ b/README.md @@ -1,70 +1,74 @@ # Morpheus Request for Comments (MRC) -List of proposals extending Decentralized AI. Similar to the function of the ERC system serves in Ethereum. https://eips.ethereum.org/erc Provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. +List of proposals extending Decentralized AI. +Similar to the function of the ERC system serves in Ethereum. +https://eips.ethereum.org/erc Provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. ## List of MRCs: -## MRC 00: Smart Agents White Paper. +## MRC 00: Morpheus Request for Comment Standard +- Status: **Adopted** +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC00.md + +## MRC 01: Smart Agents White Paper. - Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. - Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/White%20Paper.md -## MRC 01: Smart Agents Yellow Paper. +## MRC 02: Smart Agents Yellow Paper. - Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. - Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/YellowPaper.md -## MRC 02: Morpheus White Paper. +## MRC 03: Morpheus White Paper. - Status: **Adopted** by the Morpheus community as basis for Morpheus Network. - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/WhitePaper.md -## MRC 03: Morpheus Yellow Paper. +## MRC 04: Morpheus Yellow Paper. - Status: **In Progress**, Being implimented as the basis for Capital, Code, Compute and Community Builders. - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/YellowPaper.md -## MRC 05: Yellowstone Compute Model. +## MRC 06: Yellowstone Compute Model. - Status: **In Progress**, Being implimented as the Decentralized Router for the launch of Compute rewards post bootstrapping period. - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Yellowstone%20Compute%20Model.md -## MRC 06: Techno Capital Machine +## MRC 07: Techno Capital Machine - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md -## MRC 07: Fair Launch Process +## MRC 08: Fair Launch Process - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Fair%20Launch.md -## MRC 08: Waterloo Community Model. +## MRC 09: Waterloo Community Model. - Status: **Under Discussion**, needs additional work to flush out the concepts. - Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing -## MRC 09: AMM Launch Process +## MRC 10: AMM Launch Process - Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. - Link: https://github.com/generativeone/Docs/blob/main/Building%20the%20Foundation%20-%20AMM%20Launch.md -## MRC 10: Development of Smart Agent Tools Marketplace. +## MRC 11: Development of Smart Agent Tools Marketplace. - Status: **Under Discussion**, needs further discussion and approval. - Link: https://docs.google.com/document/d/1JJQR4-b63VbJQ_etSt5Poyk1KcK3f7FvUZcwKB5Zpk8/edit?usp=sharing -## MRC 11: Morpheus Multi-Agent Framework. +## MRC 12: Morpheus Multi-Agent Framework. - Status: **Under Discussion**, needs further discussion to cover edge cases. - Link: https://docs.google.com/document/d/1i6FBD7OIMEHSYMgKUGmrjpxgnlFN20JRC4_yW9bAVWw/edit?usp=sharing -## MRC 12: Capital contracts expansion to stMATIC. +## MRC 13: Capital contracts expansion to stMATIC. - Status: **Under Discussion**, needs further discussion to cover all edge cases and flesh out more concepts. - Link: https://docs.google.com/document/d/1lZ_vJ3exkrn8DscHI6C59unp5Lui895rtN4nc-e2wso/edit?usp=sharing -## MRC 13: Launch TCM for MOR Yield Farming on Solana with JitoSOL and/or mSOL. +## MRC 14: Launch TCM for MOR Yield Farming on Solana with JitoSOL and/or mSOL. - Status: **Under Discussion**, needs further discussion to answer open questions (see end of doc) and approval. - Link: https://0xmacro.notion.site/MRC-13-Launch-TCM-for-MOR-Yield-Farming-on-Solana-with-JitoSOL-and-or-mSOL-a0f9e2c0fa884aa590fe993c38bc627b -## MRC 14: MOR MOR Weights for Greater Granularity. -- Status: **In Progress**, Planned implementation for April 2024 weights. +## MRC 15: MOR MOR Weights for Greater Granularity. +- Status: **In Progress**, Planned implementation for April 8th 2024 weights snapshot. - Link: https://docs.google.com/document/d/1_5WZSNZ8LDwrD-mWNR3HzZT4asYSHYeqHsybXvz302g/ -## MRC 15: A Framework for Adding Yield-Generating Assets. +## MRC 16: A Framework for Adding Yield-Generating Assets. - Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. - Link: https://github.com/generativeone/Docs/blob/main/Expanding%20Horizon%20-%20The%20Morpheus%20Asset%20Integration%20Framework.md -## MRC 16: - ## MRC 17: ## MRC 18: From 91a4ad27aad419c9c9f87c4d5dd27fcfe7de2dc3 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Sun, 17 Mar 2024 08:31:01 +0200 Subject: [PATCH 040/129] Update README.md --- README.md | 24 +++++++++++++----------- 1 file changed, 13 insertions(+), 11 deletions(-) diff --git a/README.md b/README.md index 6002aec..ea7aa2a 100644 --- a/README.md +++ b/README.md @@ -25,50 +25,52 @@ https://eips.ethereum.org/erc Provides a common language to describe interaction - Status: **In Progress**, Being implimented as the basis for Capital, Code, Compute and Community Builders. - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/YellowPaper.md -## MRC 06: Yellowstone Compute Model. +## MRC 05: Yellowstone Compute Model. - Status: **In Progress**, Being implimented as the Decentralized Router for the launch of Compute rewards post bootstrapping period. - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Yellowstone%20Compute%20Model.md -## MRC 07: Techno Capital Machine +## MRC 06: Techno Capital Machine - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md -## MRC 08: Fair Launch Process +## MRC 07: Fair Launch Process - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Fair%20Launch.md -## MRC 09: Waterloo Community Model. +## MRC 08: Waterloo Community Model. - Status: **Under Discussion**, needs additional work to flush out the concepts. - Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing -## MRC 10: AMM Launch Process +## MRC 09: AMM Launch Process - Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. - Link: https://github.com/generativeone/Docs/blob/main/Building%20the%20Foundation%20-%20AMM%20Launch.md -## MRC 11: Development of Smart Agent Tools Marketplace. +## MRC 10: Development of Smart Agent Tools Marketplace. - Status: **Under Discussion**, needs further discussion and approval. - Link: https://docs.google.com/document/d/1JJQR4-b63VbJQ_etSt5Poyk1KcK3f7FvUZcwKB5Zpk8/edit?usp=sharing -## MRC 12: Morpheus Multi-Agent Framework. +## MRC 11: Morpheus Multi-Agent Framework. - Status: **Under Discussion**, needs further discussion to cover edge cases. - Link: https://docs.google.com/document/d/1i6FBD7OIMEHSYMgKUGmrjpxgnlFN20JRC4_yW9bAVWw/edit?usp=sharing -## MRC 13: Capital contracts expansion to stMATIC. +## MRC 12: Capital contracts expansion to stMATIC. - Status: **Under Discussion**, needs further discussion to cover all edge cases and flesh out more concepts. - Link: https://docs.google.com/document/d/1lZ_vJ3exkrn8DscHI6C59unp5Lui895rtN4nc-e2wso/edit?usp=sharing -## MRC 14: Launch TCM for MOR Yield Farming on Solana with JitoSOL and/or mSOL. +## MRC 13: Launch TCM for MOR Yield Farming on Solana with JitoSOL and/or mSOL. - Status: **Under Discussion**, needs further discussion to answer open questions (see end of doc) and approval. - Link: https://0xmacro.notion.site/MRC-13-Launch-TCM-for-MOR-Yield-Farming-on-Solana-with-JitoSOL-and-or-mSOL-a0f9e2c0fa884aa590fe993c38bc627b -## MRC 15: MOR MOR Weights for Greater Granularity. +## MRC 14: MOR MOR Weights for Greater Granularity. - Status: **In Progress**, Planned implementation for April 8th 2024 weights snapshot. - Link: https://docs.google.com/document/d/1_5WZSNZ8LDwrD-mWNR3HzZT4asYSHYeqHsybXvz302g/ -## MRC 16: A Framework for Adding Yield-Generating Assets. +## MRC 15: A Framework for Adding Yield-Generating Assets. - Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. - Link: https://github.com/generativeone/Docs/blob/main/Expanding%20Horizon%20-%20The%20Morpheus%20Asset%20Integration%20Framework.md +## MRC 16: + ## MRC 17: ## MRC 18: From e4133a8a63ce9bb916a89d5731ee50bfe9ad5591 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Sun, 17 Mar 2024 08:31:20 +0200 Subject: [PATCH 041/129] Update Morpheus Request For Comments (MRC).md --- Morpheus Request For Comments (MRC).md | 58 +++++++++++++++++++------- 1 file changed, 44 insertions(+), 14 deletions(-) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index 03b6f87..ea7aa2a 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -1,33 +1,39 @@ # Morpheus Request for Comments (MRC) -List of proposals extending Decentralized AI. Similar to the function of the ERC system serves in Ethereum. https://eips.ethereum.org/erc Provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. +List of proposals extending Decentralized AI. +Similar to the function of the ERC system serves in Ethereum. +https://eips.ethereum.org/erc Provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. ## List of MRCs: -## MRC 00: Smart Agents White Paper. +## MRC 00: Morpheus Request for Comment Standard +- Status: **Adopted** +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC00.md + +## MRC 01: Smart Agents White Paper. - Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. - Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/White%20Paper.md -## MRC 01: Smart Agents Yellow Paper. +## MRC 02: Smart Agents Yellow Paper. - Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. - Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/YellowPaper.md -## MRC 02: Morpheus White Paper. +## MRC 03: Morpheus White Paper. - Status: **Adopted** by the Morpheus community as basis for Morpheus Network. -- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/WhitePaper.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/WhitePaper.md -## MRC 03: Morpheus Yellow Paper. -- Status: **Adopted**, Being implemented as the basis for Capital, Code, Compute and Community Builders. +## MRC 04: Morpheus Yellow Paper. +- Status: **In Progress**, Being implimented as the basis for Capital, Code, Compute and Community Builders. - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/YellowPaper.md ## MRC 05: Yellowstone Compute Model. - Status: **In Progress**, Being implimented as the Decentralized Router for the launch of Compute rewards post bootstrapping period. -- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Yellowstone%20Compute%20Model.md +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Yellowstone%20Compute%20Model.md -## MRC 06: Techno Capital Machine. +## MRC 06: Techno Capital Machine - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md -## MRC 07: Fair Launch Process. +## MRC 07: Fair Launch Process - Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Fair%20Launch.md @@ -35,9 +41,9 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC - Status: **Under Discussion**, needs additional work to flush out the concepts. - Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing -## MRC 09: Fair Price Discovery and AMM Initiation -- Status: **Under Discussion**, needs more feedback from wider community. -- Link: https://docs.google.com/document/d/1PYeWnu3KpQdExwwuKFgGbRl9eajc6oP1poEQZmf7S2w/edit?usp=sharing +## MRC 09: AMM Launch Process +- Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. +- Link: https://github.com/generativeone/Docs/blob/main/Building%20the%20Foundation%20-%20AMM%20Launch.md ## MRC 10: Development of Smart Agent Tools Marketplace. - Status: **Under Discussion**, needs further discussion and approval. @@ -56,5 +62,29 @@ List of proposals extending Decentralized AI. Similar to the function of the ERC - Link: https://0xmacro.notion.site/MRC-13-Launch-TCM-for-MOR-Yield-Farming-on-Solana-with-JitoSOL-and-or-mSOL-a0f9e2c0fa884aa590fe993c38bc627b ## MRC 14: MOR MOR Weights for Greater Granularity. -- Status: **In Progress**, Planned implementation for April 2024 weights. +- Status: **In Progress**, Planned implementation for April 8th 2024 weights snapshot. - Link: https://docs.google.com/document/d/1_5WZSNZ8LDwrD-mWNR3HzZT4asYSHYeqHsybXvz302g/ + +## MRC 15: A Framework for Adding Yield-Generating Assets. +- Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. +- Link: https://github.com/generativeone/Docs/blob/main/Expanding%20Horizon%20-%20The%20Morpheus%20Asset%20Integration%20Framework.md + +## MRC 16: + +## MRC 17: + +## MRC 18: + +## MRC 19: + +## MRC 20: "Automated Recurring Revenue / Rewards" (ARR) - The MOR 20 Token Standard +- Status: **Under Discussion** +- 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 reacurring 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. +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md#automated-recurring-revenue--rewards-arr-generalizing-the-tcm-model---mor20-token-standard From b7b74bd424dacc4623e8f7650d5b76e130585872 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Sun, 17 Mar 2024 08:36:55 +0200 Subject: [PATCH 042/129] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ea7aa2a..eab5295 100644 --- a/README.md +++ b/README.md @@ -83,7 +83,7 @@ https://eips.ethereum.org/erc Provides a common language to describe interaction 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 reacurring revenue / payments from users via yield. +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. From 0c0e4d9fa631291ebda8b0db63be4791084cbee7 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Sun, 17 Mar 2024 20:43:17 +0200 Subject: [PATCH 043/129] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index eab5295..065d9fa 100644 --- a/README.md +++ b/README.md @@ -61,7 +61,7 @@ https://eips.ethereum.org/erc Provides a common language to describe interaction - Status: **Under Discussion**, needs further discussion to answer open questions (see end of doc) and approval. - Link: https://0xmacro.notion.site/MRC-13-Launch-TCM-for-MOR-Yield-Farming-on-Solana-with-JitoSOL-and-or-mSOL-a0f9e2c0fa884aa590fe993c38bc627b -## MRC 14: MOR MOR Weights for Greater Granularity. +## MRC 14: MOR Weights for Greater Granularity. - Status: **In Progress**, Planned implementation for April 8th 2024 weights snapshot. - Link: https://docs.google.com/document/d/1_5WZSNZ8LDwrD-mWNR3HzZT4asYSHYeqHsybXvz302g/ From 8c166f8568590f7efd3ba9bcd973d5dadd659d90 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 15:35:50 -0400 Subject: [PATCH 044/129] Update MRC00.md Github includes the details. --- MRC00.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/MRC00.md b/MRC00.md index fef8c68..98a16a9 100644 --- a/MRC00.md +++ b/MRC00.md @@ -20,3 +20,6 @@ Each Morpheus Request for Comment should include the following: Time to expire Dev Id assigned Tie to deliverables/testing + +- Google Drive or Notion is fine for an initial draft, however for the MRC to be included for discussion all the details of the MRC should be published on Github . + Add the MRC details in a new file in the MRC repo with a matching file named MRC####.md so everyone can comment on it directly in Github. From 0b0750d02894b2be18e14992b73d21ebd4313784 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 15:37:07 -0400 Subject: [PATCH 045/129] Update MRC00.md Formatting. --- MRC00.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/MRC00.md b/MRC00.md index 98a16a9..8d49cc8 100644 --- a/MRC00.md +++ b/MRC00.md @@ -21,5 +21,6 @@ Each Morpheus Request for Comment should include the following: Dev Id assigned Tie to deliverables/testing -- Google Drive or Notion is fine for an initial draft, however for the MRC to be included for discussion all the details of the MRC should be published on Github . +- Google Drive or Notion is fine for an initial draft, however for the MRC to progress to the "Discussion" phase all the details of the MRC should be published on Github . Add the MRC details in a new file in the MRC repo with a matching file named MRC####.md so everyone can comment on it directly in Github. + Include the link to the full MRC file in the summary in the Readme. From 5f6925e4f00b109454bda94704f5a9d14b08cbd7 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 15:37:25 -0400 Subject: [PATCH 046/129] Update MRC00.md --- MRC00.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MRC00.md b/MRC00.md index 8d49cc8..c17a5f7 100644 --- a/MRC00.md +++ b/MRC00.md @@ -22,5 +22,5 @@ Each Morpheus Request for Comment should include the following: Tie to deliverables/testing - Google Drive or Notion is fine for an initial draft, however for the MRC to progress to the "Discussion" phase all the details of the MRC should be published on Github . - Add the MRC details in a new file in the MRC repo with a matching file named MRC####.md so everyone can comment on it directly in Github. - Include the link to the full MRC file in the summary in the Readme. + - Add the MRC details in a new file in the MRC repo with a matching file named MRC####.md so everyone can comment on it directly in Github. + - Include the link to the full MRC file in the summary in the Readme. From 97c25057bcd9c75108ec797ef41c3ced973d6933 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 15:38:09 -0400 Subject: [PATCH 047/129] Update MRC00.md Formatting. --- MRC00.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/MRC00.md b/MRC00.md index c17a5f7..ad13e84 100644 --- a/MRC00.md +++ b/MRC00.md @@ -2,11 +2,15 @@ Each Morpheus Request for Comment should include the following: +- Google Drive or Notion is fine for an initial draft, however for the MRC to progress to the "Discussion" phase all the details of the MRC should be published on Github . + - Add the MRC details in a new file in the MRC repo with a matching file named MRC####.md so everyone can comment on it directly in Github. + - Include the link to the full MRC file in the summary in the Readme. + - Problem - Solution - Abstract - Development strategy - Tech Stack + - Abstract + - Development strategy + - Tech Stack - End Results @@ -15,12 +19,8 @@ Each Morpheus Request for Comment should include the following: - New weights requested - Effort required to Implement - Deliverables - Meta - Time to expire - Dev Id assigned - Tie to deliverables/testing - -- Google Drive or Notion is fine for an initial draft, however for the MRC to progress to the "Discussion" phase all the details of the MRC should be published on Github . - - Add the MRC details in a new file in the MRC repo with a matching file named MRC####.md so everyone can comment on it directly in Github. - - Include the link to the full MRC file in the summary in the Readme. + - Deliverables + - Meta + - Time to expire + - Dev Id assigned + - Tie to deliverables/testing From 67c88a7a7739be22836dd4c2a37367fe997cb45e Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 15:45:51 -0400 Subject: [PATCH 048/129] Create MRC08.md Pulling MRC 08 over to Github. --- MRC08.md | 105 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 105 insertions(+) create mode 100644 MRC08.md diff --git a/MRC08.md b/MRC08.md new file mode 100644 index 0000000..50c1857 --- /dev/null +++ b/MRC08.md @@ -0,0 +1,105 @@ +# Waterloo Community Apps Builder Model + +## Introduction +The Morpheus whitepaper describes the intent of having the Community Builder rewards go towards those front ends, websites, apps and tools that make the Morpheus network more accessible. The rewards for the Morpheus Community Builders are outlined as 24% of MOR emissions. In this proposal, additional details describe how the emissions will be distributed based on the different proofs. + +The Web3 community has long suffered from a lack of front-end development. This is mostly due to protocols only offering a reward for proof of work (Compute) or proof of Stake (Capital), thus there are normally no resources directed toward those building at the application layer. The Morpheus network is unique in that it rewards developers of the Protocol, Network, Smart Contracts, and also Smart Agents, Websites & Dapps the Community uses. In this way Morpheus is a truly full-stack project, extending its rewards beyond the back-end functions, right up to front ends that serve the end users. + +## Types of Rewards +By using the weights below, the community rewards will make each of the core functions of the Morpheus Network more broadly accessible and increase the Morpheus Code, Compute, and Capital resources. + +End User Applications +Builders of End User Applications will receive 8% of all MOR emissions for generating demand for the Smart Agents. + +For example, a developer builds a website for the average person to use Smart Agents from the Morpheus Network. That user will also register their public key in the Morpheus protocol and get credit based on the amount of MOR fees paid by those users. + +## Capital Front Ends +Builders of front ends for the Capital Providers will receive 8% of all MOR emissions. + +For example, a developer that creates an easy to use app or website that funnels Capital into the Morpheus Capital Provider smart contract would get a part of the 8% emissions pro-rata to the capital their public key tagged to the capital provision transaction. + +“Capital” is defined as the real-time Ethereum (ETH) value of a deposited asset. + +In determining the best method for allocation emissions for Capital Front Ends, Morpheus considered three alternatives. Each focuses on a pro-rata distribution methodology, but differ in the time horizon considered: +Daily - emissions are distributed based on daily capital deposits. The primary benefit of this methodology is that it continually encourages and rewards new depositors. However, there are multiple downsides. First, capital deposits won't be smooth - 10 stETH could be deposited on one day and 100 stETH the next. As such, the Community Capital Front End emissions would be greatly disproportionate to the capital contributed as a full day’s emissions would be provided for 10 stETH one day and 100 stETH the next. Second, this could result in a manipulation of the system. Since it would be limited to a one day time horizon, users could repeatedly deposit to earn the Community Capital Front End emissions, then withdraw funds and deposit a day or two later to earn more again. +Cumulative - emissions are distributed based on the cumulative capital deposits to date. This methodology distributes emissions based on the value of capital provided, regardless if that capital was contributed on a particular day, or months/years in the past, so long as it remains deposited. The downside to this approach is that it could discourage builders to develop new front ends. If a large amount of capital is already allocated, then incremental amounts will be relatively insignificant - meaning builders are less incentivized to continue building for an ever smaller piece of the pie. +1 Year Duration - capital deposits through a front-end are relevant for one year so long as they remain deposited. Emissions are distributed based on the pro rata share of the trailing one year deposits. The length of the timeline could be set to any number of days/years. The goal would be to find the appropriate balance which encourages new front end development to solicit capital while removing unnecessary transactions and potential exploitation. + +Multi-Asset Considerations: stETH on Ethereum is the only capital currently allowed to be contributed. Over time, more assets and more chains may be added. With additional assets deposited as capital, it raises several complexities that must be accounted for: +Price Feeds - All currencies must be denominated into a comparable asset in order to determine relevant value. This will occur by translating all currencies into the equivalent USDC value at the time of the transaction. [will need to define the Oracle price feeds to be utilized as well as the timing: price updates by block, average for the day, spot at end of day, etc] +Relative Movements across Assets - Currencies will move relative to each other after being deposited. For example, if token A is deposited when its price is $100 and Token B is deposited when its price is $200, then at the time of deposit, it is a 1:2 ratio. A user who deposited 1 Token A will be credited with half the value of a user who deposited 1 Token B. However, if a week later, Token A’s price has stayed at $100 while Token B’s price has increased to $300, the ratio is now at 1:3 for those same deposits. Prices will need to be updated on a regular basis to ensure that the user’s deposited value represents actual prices. +Asset Movements across Time - A similar situation arises when two users deposit the same asset at different times. If User 1 deposits a single Token B at $200 and User 2 deposits a single Token B a week later at $300. They both have deposited 1 Token B and contributed equally at any time moving forward - the MOR rewards generated will only be considered equal if the token prices are routinely updated and not focused on price at the time of entry. +Yields Differ across Deposited Assets - Different assets earn different yields. Those assets depend on the asset, protocol, and market conditions among other factors. The yield on the deposited asset is ultimately what is contributed to Morpheus. At first glance, the only thing Morpheus would care about would be the benefit it receives regarding yield. However, a wide variety of assets and chains strengthens the health of Morpheus. It helps to protect Morpheus via diversification. There are a variety of analyses out there, but generally speaking, a higher yield, by default, implies a higher risk. Therefore, assets that may have a lower yield attached to them should still be encouraged as the underlying assets might be viewed as ‘safer’ or have a better likelihood of appreciation in value. Therefore, a blended approach would balance the difference and reward across the capital deposited and yield generated. The below example shows, using random assets and numbers for presentational purposes only, the blended pro-rata approach where a 50% weight is applied to the TVL and a 50% weight is applied to the daily yield. + +## Deposited Asset Details +Deposited TVL +TVL (% of Total) +Daily Yield $ +Daily Yield (% of Total) +Community Capital MOR Emissions +Lido - stETH +$100,000,000 +74% +$9,315 +61% +67.5% +Lido - stMATIC +$5,000,000 +4% +$548 +4% +4% +Jito - JuitSOL +$20,000,000 +15% +$4,164 +27% +21% +GMX - GMX +$10,000,000 +7% +$1,208 +8% +7.5% +Total +$135,000,000 +100% +$15,235 +100% +100% + +## Compute Front Ends +Builders of front ends for the Compute Providers will receive 8% of all MOR emissions. + +For example, a developer builds a Software Development Kit, API or website that makes it easier to provide Compute to the Morpheus Network. In doing so, they qualify to receive a pro-rata amount based on the amount of Compute they helped to enroll. + +Order of operations for bootstrapping the Morpheus Network. +The 24% of the MOR emissions for Community Builders will begin to accrue to the Community Builder Smart Contract when it reaches Ethereum mainnet (February 8th 2024). The Community Builder smart contracts should enter into operation after the other three smart contracts (Code, Capital & Compute) are already functional. +Step #1. +Code & Capital Rewards go live February 8th 2024 with their respective smart contracts. +MOR rewards begin to be earned by participating addresses. MOR begins accruing in the Compute & Community Smart Contracts. + +Step #2 +Day 90 the bootstrapping period is complete, the AMM pool is launched. +Day 91 the MOR are claimable/sendable. + +Step #3. +Compute Smart Contract and Router software goes live and Compute Provide begins earning MOR from the bidding system. + +Step #4. +Community Builder Smart Contact goes live and front-end builders begin earning MOR from the accrued emissions available. +https://docs.google.com/spreadsheets/d/1qW20-C6VLw5eX3Wjrz-JeEbsvakFIojyZv9c9OIoU7E/edit?usp=sharing + +## Protecting Against Exploits +The key idea is to quantify on-chain activity as a means to avoid exploits and make the activity easier to prove. + +Why is this important? +Without a protocol-level reward, a community member would be required to form traditional entities and other means of coordinating efforts. This would cause friction within the construct of Morpheus’ use of the Techno Capital Machine; it's critical that the rewards be able to cover the full stack of developers involved. + +With this in place, every aspect of the Morpheus community is rewarded for their contribution of effort, not just capital or compute. + +## Conclusion: +While there is a perception that rewarding front end developers is subjective, the examples above are all based on provable on-chain activity. Thus contributions from the front-end developers in the Community are just as provable as Compute or Capital. + +The question becomes defining the metrics. It’s worth the extra work to define these rewards. Consider Lido the creator of stETH, which has a “reward sharing program” that has driven much of its success in onboarding large amounts of ETH onto its protocol. + From 091b2fa93466c03424392fcd6e29b1af0ec10910 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 15:46:35 -0400 Subject: [PATCH 049/129] Update README.md Link to MRC08 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 065d9fa..4ab2b57 100644 --- a/README.md +++ b/README.md @@ -39,7 +39,7 @@ https://eips.ethereum.org/erc Provides a common language to describe interaction ## MRC 08: Waterloo Community Model. - Status: **Under Discussion**, needs additional work to flush out the concepts. -- Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC08.md ## MRC 09: AMM Launch Process - Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. From 845e84b5fd294a2e2c0e9ef60b27f186699a444b Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 15:50:35 -0400 Subject: [PATCH 050/129] Create MRC10.md Moving MRC10 over to Github. --- MRC10.md | 52 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 52 insertions(+) create mode 100644 MRC10.md diff --git a/MRC10.md b/MRC10.md new file mode 100644 index 0000000..5b70cc9 --- /dev/null +++ b/MRC10.md @@ -0,0 +1,52 @@ +# Development of Smart Agent Tools Marketplace + +## Project Name: Smart Agent Tools Marketplace +Requesting Organization/Individual: Mor Labs + +Summary: This proposal outlines the development of a marketplace for tools that can be integrated with Smart Agents within the Morpheus ecosystem. This marketplace aims to significantly expand the capabilities of Smart Agents, allowing them to interact with both web3 smart contracts and centralized tools and apps. The marketplace will facilitate easy access to and implementation of tools for data handling, interaction with centralized platforms like Google Sheets, Discord, and GitHub, and more, enhancing the Smart Agents' functionality and versatility. + +## Introduction +The project seeks to pioneer the Smart Agent Tools Marketplace, a platform designed to augment the capabilities of Smart Agents through a diverse array of integrable tools. This initiative will bridge the gap between decentralized and traditional centralized environments, enabling Smart Agents to become more adaptable, intelligent, and efficient in executing a wide range of tasks. + +### Problem Statement +While Smart Agents offer significant potential for automation and intelligence within the web3 ecosystem, their effectiveness is currently limited by their inability to seamlessly integrate with a wide range of external data sources and tools. This limitation restricts the versatility and application scope of Smart Agents, hindering their adoption and the realization of their full potential. + +### Project Objectives +Expand Smart Agent Capabilities: Enable Smart Agents to integrate with a broad spectrum of tools, including data pipelines from various sources. +Bridge Web3 and Centralized Tools: Facilitate seamless interactions between Smart Agents and both decentralized and centralized applications. +Foster Innovation and Customization: Provide a platform for developers to contribute and customize tools, fostering a collaborative and innovative ecosystem. + +### Proposed Solution +The Smart Agent Tools Marketplace will serve as a dedicated platform where developers and users can access, share, and implement tools designed to enhance the functionality of Smart Agents. This marketplace will leverage Langchain as well as the CrewAI codebase to provide a robust and flexible environment for tool integration, supporting a wide range of use cases from data manipulation to interaction with centralized services. + +### Technology Stack +Frontend Development: React.js, CSS/Sass, Redux, OAuth 2.0, Jest, React Testing Library +Smart Contract Development (Web3): Ethereum, Solidity, ethers.js/web3.js, IPFS +Integration with Smart Agents: WebSocket, SDKs for major Smart Agent frameworks +Tool Implementation (Python Scripts): Python 3.x, virtual environments for dependency management + +## Implementation Plan + +### Preparation and Initial Setup +Finalize the project proposal with comprehensive community feedback. Adjust project objectives based on insights gained. +Initiate the design of the marketplace user interface, focusing on wireframes and basic design elements that enhance user experience. + +### Marketplace Frontend Development +Develop the user interface for tool browsing and selection. This includes integrating user authentication mechanisms and ensuring the design is responsive across devices. +Implement frontend functionalities such as tool categorization, search features, and user feedback systems. + +### Backend Development and Smart Contract Integration +Create smart contracts for tool transactions. Utilize IPFS for the decentralized storage of tool scripts and metadata. +Establish backend services for the marketplace, including database management and real-time communication channels for Smart Agents + +### Tool Integration and Initial Toolset Development +Develop and document a set of Python scripts representing initial tools. Ensure these tools have a standardized interface for easy integration with Smart Agents. +Implement logic for the integration of Python scripts with Smart Agents, enabling seamless interaction between the tools and agents. + +### Testing, Quality Assurance, and Initial Deployment +Conduct comprehensive testing across all components of the marketplace. Address any issues found and ensure platform stability. +Deploy the marketplace to a test environment. Collect feedback from a select user group and make necessary adjustments. + +### Official Launch and Community Engagement +Finalize documentation and deploy the marketplace to production. +Launch a community engagement campaign to gather user feedback, promote the marketplace, and iterate on the project based on real-world use. From 34a5f0f54bef26e72b6e1aca89c9e142b0c8b511 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 15:51:35 -0400 Subject: [PATCH 051/129] Update README.md Updated link for MRC10 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4ab2b57..b0b48f4 100644 --- a/README.md +++ b/README.md @@ -47,7 +47,7 @@ https://eips.ethereum.org/erc Provides a common language to describe interaction ## MRC 10: Development of Smart Agent Tools Marketplace. - Status: **Under Discussion**, needs further discussion and approval. -- Link: https://docs.google.com/document/d/1JJQR4-b63VbJQ_etSt5Poyk1KcK3f7FvUZcwKB5Zpk8/edit?usp=sharing +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC10.md ## MRC 11: Morpheus Multi-Agent Framework. - Status: **Under Discussion**, needs further discussion to cover edge cases. From 6c9f261f6c3a38118c49737b3de7002b7c62f65a Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 15:57:26 -0400 Subject: [PATCH 052/129] Create MRC11.md Moving the MRC11 to Github. --- MRC11.md | 48 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 48 insertions(+) create mode 100644 MRC11.md diff --git a/MRC11.md b/MRC11.md new file mode 100644 index 0000000..bce97c1 --- /dev/null +++ b/MRC11.md @@ -0,0 +1,48 @@ +# Morpheus Multi-Agent Framework (MMAF) +Project Name: Morpheus Multi-Agent Framework (MMAF) +Requesting Organization/Individual: Mor Labs + +Summary: The MMAF project aims to evolve the Morpheus ecosystem from a single-agent system to a sophisticated multi-agent framework. By leveraging the CrewAI codebase, this initiative will enable the development and coordination of multiple smart agents, facilitating diverse functionalities and inter-agent communication. This expansion is poised to significantly enhance the adoption, versatility, and operational efficiency of Morpheus Smart Agents, fostering a new level of dynamic interaction within the decentralized space. + +## Introduction +Mor Labs, in collaboration with the CrewAI community, proposes to spearhead the development of a multi-agent framework for Morpheus. Our team combines Mor Labs' deep expertise in decentralized technologies with CrewAI's pioneering work in AI and multi-agent systems. The collaboration is uniquely positioned to execute this ambitious project, given our proven track record in blockchain development, AI, and community-driven innovation. + +### Problem Statement +Currently, Morpheus operates with a single-agent paradigm, limiting its capability to handle complex, multi-dimensional tasks that require collaboration or competition among agents. This restriction hampers the potential for scalability, flexibility, and efficiency in achieving sophisticated decentralized applications (dApps) and smart contract orchestration. + +### Project Objectives +Develop Multi-Agent Capabilities: Enable the creation and coordination of multiple smart agents within the Morpheus ecosystem. + +### Foster Agent Interoperability: Ensure smart agents can interact seamlessly with agents created by third parties. +Enhance System Productivity and Adoption: By introducing multi-agent functionality, significantly improve the productivity of the Morpheus ecosystem and its appeal to developers and users. +Demonstrate Multi-Agent Use Cases: Implement and showcase practical use cases of multi-agent systems within Morpheus. + +### Proposed Solution +Our solution involves developing a comprehensive multi-agent framework that allows for the creation, management, and interaction of multiple smart agents within the Morpheus ecosystem. This framework will leverage the existing CrewAI codebase, enhancing it with blockchain-specific functionalities to support decentralized operations. Agents will be able to communicate, collaborate, and negotiate with each other, enabling complex decentralized processes and applications. + +### Technology Stack +Base Codebase: CrewAI for agent algorithms and behaviors. +Blockchain Integration: Solidity for smart contract development, with Morpheus and Ethereum blockchains as primary platforms. +Communication Protocols: Development of decentralized communication protocols for agent interaction. +Security: Implementation of security best practices and protocols to ensure the integrity and privacy of multi-agent interactions. + +### Implementation Plan +Preparation and Community Engagement +Finalize the proposal with community feedback. Gather initial feedback from the Morpheus and CrewAI communities to refine the project's direction. +Conduct a detailed requirement analysis for the multi-agent framework. Identify specific functionalities, interoperability requirements, and security protocols needed. + +### Framework Design and Prototype Development +Design the multi-agent framework's architecture. This includes defining the communication protocols, agent management systems, and integration points with the Morpheus ecosystem. +Develop a prototype of the multi-agent functionalities using the CrewAI codebase. Focus on core capabilities that demonstrate the framework's potential. + +### Integration and Initial Agent Development +Integrate the prototype framework with the Morpheus ecosystem. Ensure the initial setup is ready for agent development. +Develop initial smart agents within the framework. Prioritize agents that showcase interoperability and the potential for complex decentralized applications. + +### Testing, Refinement, and Security Enhancement +Conduct comprehensive testing of the multi-agent framework and initial agents. Identify and address any interoperability issues. +Refine the framework and agent functionalities based on testing outcomes. Enhance system security protocols. + +### Launch and Community Demonstration +Officially launch the multi-agent framework. Ensure all systems are operational and fully integrated with the Morpheus ecosystem. +Conduct demonstrations of multi-agent use cases. Host community workshops to engage developers and users, encouraging adoption and feedback. From 8d84dd342946d241eda2064dedc61afdb8ee5980 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 15:58:08 -0400 Subject: [PATCH 053/129] Update README.md Updating link for MRC11 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b0b48f4..584ff85 100644 --- a/README.md +++ b/README.md @@ -51,7 +51,7 @@ https://eips.ethereum.org/erc Provides a common language to describe interaction ## MRC 11: Morpheus Multi-Agent Framework. - Status: **Under Discussion**, needs further discussion to cover edge cases. -- Link: https://docs.google.com/document/d/1i6FBD7OIMEHSYMgKUGmrjpxgnlFN20JRC4_yW9bAVWw/edit?usp=sharing +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC11.md ## MRC 12: Capital contracts expansion to stMATIC. - Status: **Under Discussion**, needs further discussion to cover all edge cases and flesh out more concepts. From 2f7eb0a9e3dd0278c6d167d672535e61921d93e0 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 16:05:51 -0400 Subject: [PATCH 054/129] Create MRC12.md Moving MRC12 over to Github. --- MRC12.md | 133 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 133 insertions(+) create mode 100644 MRC12.md diff --git a/MRC12.md b/MRC12.md new file mode 100644 index 0000000..ac23d1b --- /dev/null +++ b/MRC12.md @@ -0,0 +1,133 @@ +# Capital contracts expansion to stMATIC + +## Executive Summary +Project Name: Capital contracts expansion to stMATIC +Requesting Organization/Individual: Mor Labs + +Summary: This project aims to extend the Morpheus ecosystem to include support for Polygon, specifically for stMATIC holders, leveraging the success of Morpheus Capital Contracts with stETH. Our objective is to enhance capital contribution options within the Morpheus ecosystem, integrating high-yield opportunities from stMATIC and leveraging the chain-agnostic nature of Morpheus to foster a more inclusive and versatile DeFi landscape. + +## Introduction +Mor Labs is a new guild that has formed from within the Morpheus ecosystem. Our team comprises blockchain developers, DeFi strategists, and security experts. + +To enhance the robustness and scalability of the Morpheus ecosystem, we propose the development of a comprehensive framework for integrating new capital assets. This framework aims to standardize the evaluation and integration process for new assets, starting with stMATIC, and will serve as a blueprint for future asset additions. +The continuous evolution of the DeFi landscape presents opportunities for the Morpheus ecosystem to integrate diverse capital assets, enriching the platform's offerings and potential for yield generation. To capitalize on these opportunities systematically, a standardized framework for asset integration is essential. This approach not only simplifies the process but also enhances transparency, objectivity, and trust among participants. + +## Framework for New Capital Assets Integration +The proposed framework will outline the necessary steps and considerations for integrating new staked assets into the Morpheus ecosystem. While specific details may vary based on the asset's unique characteristics, the framework will include the following core components: + +- Staked Asset Identification - Description of the asset to be staked, including its relevance to the Morpheus ecosystem. +- Underlying Asset Analysis - Examination of the underlying asset, including its utility, market cap, and role in its respective blockchain ecosystem. +- Network Evaluation - Assessment of the blockchain network on which the staked asset exists, focusing on its security, scalability, and interoperability with the Morpheus ecosystem. +- Yield Mechanism Description - Detailed analysis of how yield is generated from the staked asset, including any associated risks and rewards. +- Lockup Period Considerations - If applicable, evaluation of the lockup period for the staked asset and its implications for liquidity and yield generation. +- Contract Audits and Auditors - Review of any smart contract audits conducted on the staking mechanisms, including details of the auditors and any findings. +- Market Cap and TVL Analysis - Analysis of the underlying asset's market cap and the total value locked (TVL) in the staked asset, providing insights into the asset's stability and potential for yield. +- Liquidity Evaluation - Examination of the staked asset's liquidity on primary exchanges and within the Morpheus ecosystem, assessing how it impacts overall ecosystem liquidity. +- APY Calculation - Calculation of the annual percentage yield (APY) for the staked asset, including any variable factors that may affect yield over time. +- Network Oracle Integration - Consideration of how network oracles will be used to provide accurate, real-time data for the staked asset, ensuring the integrity of yield calculations and asset valuations. + +This framework is intended to be dynamic, allowing for adjustments and updates as the DeFi landscape evolves and new insights emerge. By adhering to this structured approach, the Morpheus ecosystem can ensure that all new assets are evaluated thoroughly and integrated in a manner that aligns with our strategic objectives, risk tolerance, and community expectations. + +## Polygon/stMATIC addition + +Polygon has successfully deployed features of Polygon 2.0, including the zkEVM, which is a milestone in leveraging zero-knowledge proofs for enhanced scalability and privacy on the Ethereum blockchain​​​​. Polygon's deployment of zkEVM as part of Polygon 2.0 highlights its leadership in zero-knowledge research and implementation. This technology is pivotal for enhancing transaction efficiency and privacy, making it highly relevant for decentralized applications, including those in decentralized AI (DeAI)​​​​. Zero-knowledge proofs, particularly as implemented in Polygon 2.0's zkEVM, offer a way to process transactions and data interactions securely and privately. This is crucial for DeAI applications, where the need to protect sensitive data while ensuring scalability and efficiency is paramount. The ZK proofs enable these applications to verify the correctness of data without revealing the data itself, thus maintaining privacy and security​​. + +Given Mor Labs expertise in smart contract development and cross-chain integrations, we are uniquely positioned to undertake the expansion of the Morpheus ecosystem to support Polygon and stMATIC. + +Applying the above framework for stMATIC on the Morpheus ecosystem, we can outline the required details based on the broader framework for new asset integration as follows: +Staked Asset Identification: stMATIC represents staked MATIC tokens within the Lido on Polygon system, providing users with a liquid token that can be used across DeFi applications on both Ethereum and Polygon networks. It's designed to allow users to stake MATIC tokens without locking assets or maintaining staking infrastructure, enabling participation in on-chain decentralized finance with their staked assets. + + +## Underlying Asset Analysis: The underlying asset, MATIC (soon to be replaced on a 1:1 basis with POL), is the native token of the Polygon network, known for its scalability and efficiency in processing transactions on the Ethereum blockchain. The market cap and TVL of MATIC would provide insights into its stability and potential for yield. As of the latest data, the staked amount in the Lido on Polygon system is substantial, indicating a healthy participation level and confidence in the staking mechanism +- Network Evaluation: Polygon (previously Matic Network) is a protocol and a framework for building and connecting Ethereum-compatible blockchain networks. It enhances Ethereum's scalability and interoperability, making it an attractive network for a variety of decentralized applications, including those in decentralized finance and AI. +- Yield Mechanism Description: Staking with Lido on Polygon allows users to earn MATIC staking rewards while maintaining full control and transferability of their assets. The staked MATIC tokens are delegated across Polygon validators part of the Lido on Polygon, with stMATIC representing the staked MATIC. Liquid staking protocols like Lido on Polygon facilitate earning staking rewards without locking assets or maintaining staking infrastructure +- Lockup Period Considerations: The waiting period for withdrawing staked assets is approximately 3-4 days, ensuring liquidity while participating in staking rewards programs +- Contract Audits and Auditors: Details about audits for the staking mechanisms are available on the Lido and associated GitHub repositories +- Market Cap and TVL Analysis: The total value locked (TVL) in stMATIC and the underlying asset's market cap provide insights into the asset's stability and potential for yield. As of the latest available data, the staked amount and the rewards paid indicate active participation and a significant amount of assets under management. At the time of writing (15th March 2024), 134,021,866 MATIC has been staked and 13,299,493 MATIC have been paid out as rewards (source) +- Liquidity Evaluation: stMATIC can be traded on centralized and decentralized exchanges, and it can be used in liquidity pools on both Ethereum and Polygon networks, indicating a healthy liquidity profile for the asset. The Uniswap V3 pool for stMATIC can be seen here. +- APY Calculation: The Annual Percentage Yield (APY) for staking MATIC through Lido on Polygon is approximately 4.3%, calculated based on historical on-chain data and the average return over the past 30 days. +- Network Oracle Integration: The integration with network oracles for real-time data provision was not explicitly mentioned in the sources, but the accurate calculation of APY and the use of decentralized finance applications suggest the use of reliable data sources for asset valuation and yield calculation + +This framework ensures a systematic and transparent approach to evaluating and integrating new staked assets into the Morpheus ecosystem, with stMATIC serving as a prime example of how assets are assessed based on various critical parameters. + +## Problem Statement +Despite the growth of the Morpheus ecosystem, stMATIC holders currently lack the ability to contribute capital and earn rewards, thus limiting the growth of the Morpheus ecosystem of contributors and capital. Additionally, high fees on Ethereum mainnet are prohibitive for those seeking to contribute smaller amounts of capital. + +## Project Objectives +The integration of stMATIC into this forward-thinking Morpheys ecosystem not only broadens capital contribution options but also places the project at the forefront of blockchain technology's evolution towards more secure, private, and efficient systems. +- Enable stMATIC Contributions: Integrate stMATIC as a capital contribution option in the Morpheus ecosystem +- Dashboard Integration: Update the Morpheus dashboard to support Polygon L2, improving user experience and accessibility +- Increase Ecosystem Yield: Leverage the higher yield of stMATIC to enhance overall ecosystem returns + +## Proposed Solution +We propose to integrate stMATIC into the Morpheus ecosystem, allowing stMATIC holders to become capital contributors. This will be achieved through smart contract modifications and dashboard updates to support Polygon L2. Our solution leverages cross-chain technologies like Wormhole and LayerZero for seamless MOR token functionality across chains, enhancing the Morpheus ecosystem's chain-agnostic vision and supporting decentralized AI ("DeAI") applications through enhanced privacy and efficiency provided by zk-rollups. + +## Technology Stack +- Blockchains: Ethereum, Arbitrum, Polygon +- Cross-Chain Protocols: Wormhole, LayerZero +- Smart Contracts: Solidity for Ethereum and Polygon adaptations +- Frontend: React.js for dashboard updates, with Web3.js and Ethers.js for blockchain interactions +- Security: Comprehensive testing and auditing using tools like MythX and OpenZeppelin +- Diversification of Protocol-Owned Liquidity + +To enhance the diversification of protocol-owned liquidity and support deeper liquidity across multiple ecosystems and pools, the yield generated from assets will remain within the ecosystems where they were generated. For example, yield from stMATIC will not be converted to ETH on Arbitrum but will stay in a liquidity pool of stMATIC/ETH on Polygon. This approach prevents the concentration of liquidity, ensuring that ecosystems outside of Arbitrum are not limited to user-provided liquidity alone. + +## Bridge MOR to Polygon Using the Native Polygon-Ethereum Bridge + +MOR tokens will be bridged to Polygon using the native Polygon-Ethereum bridge. This enables MOR to participate in the Polygon ecosystem while maintaining its primary operations and functionalities on Arbitrum. + +Despite MOR being accessible on multiple chains through bridging, all MOR tokens will remain claimable only on Arbitrum. This decision is to avoid the complexity and potential confusion arising from having MOR balances claimable across different blockchains. + +## Calculation of MOR Emissions to Capital Contributors + +The calculation of MOR emissions for capital contributors, when involving more than one asset, will adopt the Pro Rata (Yield) method. This approach considers the yield generated by each asset, ensuring emissions are aligned with the financial benefit provided to the Morpheus ecosystem. For instance, if stMATIC yields 4.3% on $100M, and stETH yields 3.6% on $400M, MOR emissions will be distributed 23% to stMATIC depositors and 77% to stETH depositors. This method is deemed the fairest, aligning emissions with the actual financial contribution of each asset to the ecosystem. + +Deposited Asset +Deposited TVL +Yield % +Annual Yield +% of Yield = MOR Emissions +stETH +$400,000,000 +3.6% +$14,400,000 +77% +stMATIC +$100,000,000 +4.3% +$4,300,000 +23% +Total +$500,000,000 +n/a +$18,700,000 +100% + +## Impact on Community Emissions + +The adoption of the Pro Rata (Yield) method for calculating MOR emissions to capital contributors will also influence the distribution of Community Emissions. Currently, 1/3 of Community Emissions, which constitute 8% of total emissions, are designated for front-ends that facilitate capital contributions. For consistency, this proposal would require Community Emissions to also be calculated based on Yield generation rather than Capital inflow. + +### Implementation Plan +Project Initiation and Community Feedback +Expand the initial community feedback phase to specifically gather insights and opinions on the new liquidity management approach and the Pro Rata (Yield) method for MOR emissions. This will ensure broader community support and understanding of these strategic decisions. + +### Detailed Project Planning +Include detailed planning around the implementation of yield-based liquidity pools, particularly the setup and management of stMATIC/ETH liquidity pools on Polygon. This should cover technical, operational, and governance considerations. +Plan for the integration and testing of the bridge for MOR token to Polygon using the native Polygon-Ethereum bridge, ensuring seamless token transfer while keeping the claim process confined to Arbitrum. + +### Smart Contract Development for stMATIC Integration +Develop smart contracts not just for stMATIC contributions but also for managing the protocol-owned liquidity in a way that keeps yield within its original ecosystem. This includes creating and managing liquidity pools on Polygon. +Incorporate logic to calculate MOR emissions based on the Pro Rata (Yield) method, ensuring fairness and alignment with the ecosystem's financial contributions. + +### Cross-Chain Functionality Implementation +Emphasize the development and testing of cross-chain functionality that supports the unique approach to liquidity and emissions calculations. This includes ensuring that the bridging of MOR to Polygon is seamless and that the claim process remains straightforward on Arbitrum. + +### Dashboard Updates and User Experience Enhancement +Update the project plan to include dashboard enhancements that accurately reflect the new liquidity management strategy and the emissions calculation method. This includes clear visualization and reporting for users on how yields are being generated and how MOR emissions are calculated and distributed. + +### Cross-Chain Integration Testing and Security Auditing +Ensure testing protocols include scenarios specific to the decentralized liquidity management strategy and the Pro Rata (Yield) calculation for MOR emissions. This will help identify any potential issues in how these strategies are implemented across different chains. +Security auditing should also focus on the new aspects introduced by these strategies, particularly the smart contract logic handling the yield-based liquidity pools and MOR emissions calculations. + +### Project Completion and Ecosystem Integration +The completion phase should include a review of how well the project has implemented the strategy for decentralized liquidity management and the Pro Rata (Yield) method for emissions. This includes assessing the impact on the ecosystem's liquidity depth across multiple ecosystems and pools, as well as the fairness and transparency of MOR emissions to capital contributors. From fe66b05c99f97beb1e6cdede3e5f702c7174cc8e Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 16:06:34 -0400 Subject: [PATCH 055/129] Update README.md Updating link for MRC12 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 584ff85..ea4fd18 100644 --- a/README.md +++ b/README.md @@ -55,7 +55,7 @@ https://eips.ethereum.org/erc Provides a common language to describe interaction ## MRC 12: Capital contracts expansion to stMATIC. - Status: **Under Discussion**, needs further discussion to cover all edge cases and flesh out more concepts. -- Link: https://docs.google.com/document/d/1lZ_vJ3exkrn8DscHI6C59unp5Lui895rtN4nc-e2wso/edit?usp=sharing +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC12.md ## MRC 13: Launch TCM for MOR Yield Farming on Solana with JitoSOL and/or mSOL. - Status: **Under Discussion**, needs further discussion to answer open questions (see end of doc) and approval. From 1524be1ada956bcb865801956159a9f7b13a4a16 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 16:07:36 -0400 Subject: [PATCH 056/129] Create MRC13.md Moving MRC13 over to Github. --- MRC13.md | 48 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 48 insertions(+) create mode 100644 MRC13.md diff --git a/MRC13.md b/MRC13.md new file mode 100644 index 0000000..e10e451 --- /dev/null +++ b/MRC13.md @@ -0,0 +1,48 @@ +# [MRC 13: Launch TCM for MOR Yield Farming on Solana with JitoSOL and/or mSOL](https://www.notion.so/34a6db212f184f59aab47c74cf94f10f?pvs=21) + +by Macro, February 26, 2024 + +**Objective** + +Grow Morpheus community and reach by enabling capital farming of MOR on Solana using native Solana LSTs (Liquid Staking Tokens). + +**Summary** + +The TCM is a unique fair launch fundraising mechanism that been successfully deployed by Morpheus to farm the MOR token. + +For a breakdown of how the TCM works from a high level please see this write up: https://github.com/MorpheusAIs/TCM + +This proposal is to re-write the TCM smart contracts that were implemented for MOR yield farming (on Arbitrum) by depositing stETH (on Ethereum) and deploy them to Solana so that network participants in the Solana ecosystem can participate in MOR farming by contributing capital. + +To the best of our knowledge, the developer platform features mentioned in the above link have not yet been implemented on Ethereum / Arbitrum. Once the platform features have been implemented, we plan to submit another MRC to re-write them on Solana as well. + +**Background** + +Morpheus has used a novel fair launch fundraising strategy for raising capital. + +By allowing participants to deposit a Liquid Staking token (stETH) and give up the native ETH yield that the LST earns, those participants can farm the native MOR token for the Morpheus project. + +Anyone can participate, hence the fair launch, and participants don’t have to sell their stETH to earn MOR. They just give their yield to Morpheus while it’s deposited. If the participant withdrawals their stETH they will stop earning MOR and will resume earning the native ETH yield. + +The stETH yield that belongs to Morpheus after a participant deposits stETH will be used to provide liquidity in the ETH / MOR AMM pool when the MOR token goes live on May 8, 2024. + +The TCM is a novel way to bootstrap having sufficient on-chain liquidity upon launch of the MOR token without giving away pre-mine allocations to market makers and other capital providers such as VCs (defeats the purpose of the fair launch). + +The Morpheus stETH deposit contract on Ethereum has surpassed $300M deposited demonstrating strong demand for this type of fair launch. The success of the TCM has helped Morpheus expand its community of active participants as there are a lot of stETH depositors who are incentive aligned to see Morpheus do well. + +**Goals** + +The goal of this MRC is to expand the community and reach to the Solana ecosystem to allow for farming MOR through the TCM fair launch technique. Solana participants will be able to provide capital in native LST tokens on Solana. + +**Technical Plan** + +- Reimplement the staking contracts as a Solana program. +- Use Wormhole to either: + - Implement a Solana MOR contract and allow token bridging between Solana and Ethereum, or + - Accept an EVM address as input + communicate staking events back to Ethereum. + +**Open Questions** + +- Which bridging approach does the Morpheus approach prefer? A list of requirements will help determine the best path. To implement the staking contracts on Solana, we would need a way to bridge/track/mint/etc MOR as rewards. +- Should we integrate with JitoSOL (Jito Labs) or mSOL (Marinade Finance) or both? This is an implantation detail we would love to get feedback from the Morpheus community on. +- Will we want to add developer platform TCM features? Question based on the documentation summarized below: https://github.com/MorpheusAIs/TCM From 2f4d681e052150215c44dde6225d44fbbe191707 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 16:08:21 -0400 Subject: [PATCH 057/129] Update README.md Updated link for MRC13. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ea4fd18..49df388 100644 --- a/README.md +++ b/README.md @@ -59,7 +59,7 @@ https://eips.ethereum.org/erc Provides a common language to describe interaction ## MRC 13: Launch TCM for MOR Yield Farming on Solana with JitoSOL and/or mSOL. - Status: **Under Discussion**, needs further discussion to answer open questions (see end of doc) and approval. -- Link: https://0xmacro.notion.site/MRC-13-Launch-TCM-for-MOR-Yield-Farming-on-Solana-with-JitoSOL-and-or-mSOL-a0f9e2c0fa884aa590fe993c38bc627b +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC13.md ## MRC 14: MOR Weights for Greater Granularity. - Status: **In Progress**, Planned implementation for April 8th 2024 weights snapshot. From 0c944eeb0485a5cf463e8b425a35906bfd2f450a Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 16:15:24 -0400 Subject: [PATCH 058/129] Create MRC14.md Moving MRC14 to Github --- MRC14.md | 47 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 47 insertions(+) create mode 100644 MRC14.md diff --git a/MRC14.md b/MRC14.md new file mode 100644 index 0000000..576ffc6 --- /dev/null +++ b/MRC14.md @@ -0,0 +1,47 @@ +# MOR Weights MRC Proposal +March 14, 2024 + +## Objective +This aims to increase the versatility of MOR weights. + +## Summary +Per the White Paper, the Yellowstone Paper, and the Morpheus Email, The MOR weights are a means to describe the allocation of MOR emissions. +The MOR smart contracts measure MOR emissions as type:integer, disallowing a fraction of a weight to exist. +The number of MOR weights for code are halving every twelve months. + +50% of all weights will be distributed the 1st year. +Weights must be maintained by the weight’s associated contributor. + +## Pending Problem + +As the number of new weights available decreases, the value of each weight increases. Without the ability to be awarded a fraction of a weight, It will soon be the case that the smallest awardable amount for code contributions will equate to multiple thousands of dollars. +In this scenario, the project will be forced to over-reward for simple contributions, disincentivizing maintenance and innovations. + +Using conservative estimates, information collected by the community reflects: +The remaining 1,548 weights have an implied value of $992,268 USD. Spread over the remaining 5 months (presuming no more increases in the weight value in the next 5 snapshots), that equals $198,453 USD of weight rewards available each month. + +## Solution - MORbase the weights by 2,000. +If the maintainers agree, the weights published in March 2024 should be MORbased by 2,000 when April 2024 weights are calculated and sent to chain. Similarly, the remaining weight pool should also be MORbased by 2,000 so that the value of current weights don’t dilute. + +### Table I - to the contributor: +Contributor A has 38 weights in the March 2024 weights update. +March weights = 38 +April weights = 76,000 + +### Table II - to the project: +The total weights available are also rebased. +March Total Weights = 50,000 +April Total Weights = 100,000,000 + +[38 / 500] = [76,000 / 100,000,000] +Existing weights holders maintain their proportion of their existing weights. + +### The result to the project will be: +Increased granularity in the allocation of weights; +Fair-market buying power; +The ability to include more developers in future development. + +In the future, and if market conditions require it, this tactic could be repeated. + +## Conclusion +MORbasing the weights by 2,000 gives Morpheus future flexibility. From f094843d5cb21987faeb49ea9f280ee6a764dae8 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 16:16:06 -0400 Subject: [PATCH 059/129] Update README.md Adding link for MRC 14. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 49df388..836876b 100644 --- a/README.md +++ b/README.md @@ -62,8 +62,8 @@ https://eips.ethereum.org/erc Provides a common language to describe interaction - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC13.md ## MRC 14: MOR Weights for Greater Granularity. -- Status: **In Progress**, Planned implementation for April 8th 2024 weights snapshot. -- Link: https://docs.google.com/document/d/1_5WZSNZ8LDwrD-mWNR3HzZT4asYSHYeqHsybXvz302g/ +- Status: **Adopted**, Planned implementation for April 8th 2024 weights snapshot. +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC14.md ## MRC 15: A Framework for Adding Yield-Generating Assets. - Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. From 6d0ad784dfcdf56200f51119a2074f110a7bd25a Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 16:20:31 -0400 Subject: [PATCH 060/129] Create MRC15.md Moving MRC 15 over to Github. --- MRC15.md | 64 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 64 insertions(+) create mode 100644 MRC15.md diff --git a/MRC15.md b/MRC15.md new file mode 100644 index 0000000..393b848 --- /dev/null +++ b/MRC15.md @@ -0,0 +1,64 @@ +# Expanding Horizon: The Morpheus Asset Integration Framework + +## Introduction +To enhance the Morpheus ecosystem this proposal introduces a comprehensive framework for integrating new yield-generating assets from Ethereum, Layer 2 solutions, and other blockchains into Morpheus. This strategic initiative is designed to not only diversify the capital avenues but also to broaden its user base by tapping into new communities and ecosystems. The expansion hopes to extend Morpheus’ reach across multiple venues, bringing in fresh perspectives and opportunities for growth. + +This expansion will enable new participants to engage with Morpheus, facilitating its spread across a variety of digital landscapes and asset classes. Such diversification is crucial for enhancing the ecosystem's resilience and adaptability. Moreover, this approach empowers Morpheus to harness the market signals generated by Capital Providers, effectively allowing market dynamics to potentially influence and guide its core functionalities over time. This unique strategy envisions Morpheus as an adaptive entity, capable of intuitively migrating or adjusting its infrastructure as new technologies emerge. + +The following document outlines a standardized process for onboarding new assets: a detailed process for suggesting, integrating, and managing yield from new assets. It covers the calculation of yields, the distribution of rewards, and the technical adjustments required for this expansion, all while ensuring the process remains transparent, equitable, and in alignment with Morpheus' core principles of open-source innovation and community-driven development. + +## Asset Prerequisites +Before integrating new yield-generating assets into Morpheus, several prerequisites must be met and included in the proposal to ensure compatibility, security, and effectiveness. These criteria are designed to maintain the integrity and objectives of Morpheus while fostering a safe and productive environment for expansion. + +- Proven Security: Assets must have undergone thorough security audits by reputable firms, demonstrating a strong record of security and stability. +- Sustainable Yield Generation: The asset should have a clear, sustainable mechanism for yield generation. +- Active Support Network: The presence of an engaged community and dedicated developer support ensures ongoing improvements and responsiveness to issues. +- Liquidity and Market Structure: Assets need to exhibit significant market liquidity and a well-established market structure, facilitating efficient transactions and interactions within the Morpheus ecosystem. +- Commitment to Decentralization: Assets that uphold decentralization principles are preferred, reflecting Morpheus' vision for a decentralized financial landscape. +- Minimum Circulating Market Cap: To ensure economic viability and reduce volatility, assets must have a minimum circulating market capitalization. This minimum will be determined upon further discussion with the community. +- Operational Testnet Requirement: Assets must possess an operational testnet environment where full integration testing can be conducted. This ensures that any technical or compatibility issues can be identified and resolved prior to live deployment, guaranteeing a smooth integration process. +- Oracle: An oracle price for the asset is required to calculate the daily share of MOR Capital Provider emissions. + +## Assets on a New Chain or L2 +When proposing assets located on new blockchains or Layer 2 solutions for integration into Morpheus, the proposal must include the following detailed information beyond the general prerequisites to ensure a thorough evaluation and seamless integration. These additional requirements are crucial for assets outside the Ethereum mainnet, as they address unique challenges and opportunities presented by cross-chain interactions. For each new blockchain or Layer 2 where Morpheus does not currently operate, it is essential to ensure that MOR rewards will be claimable on that venue, a plan to establish Protocol-Owned Liquidity (PoL) should also be presented. + +- Cross-Chain Infrastructure and Testnet Verification: For assets not native to Ethereum, the presence of existing cross-chain infrastructure is mandatory. Furthermore, this infrastructure must be verifiable within a testnet environment, allowing for comprehensive testing of cross-chain functionalities. This ensures that assets can seamlessly interact within the Morpheus ecosystem, maintaining the integrity and fluidity of cross-chain operations. +- Infrastructure: Will the MOR token / liquidity pool be established on the new venue? If so, points #3 and #4 below should be satisfied. Regardless, the proposal should detail the logistics of cross-chain MOR minting or transferring yield from the newly added network to Arbitrum, to be utilized as Protocol-Owned Liquidity (PoL). +- Liquidity Pool Initiation: The new asset proposal should outline a clear initiation plan for the liquidity pool on the new venue. This period serves as a buffer, ensuring that the asset's integration proceeds smoothly and efficiently. Morpheus itself was started with a similar bootstrapping period, details of which can be found at https://github.com/generativeone/Docs/blob/main/Building%20the%20Foundation%20-%20AMM%20Launch.md. The primary topics for this pool initiation plan will include: + - Timeline + - The base asset in the pool + - Source of MOR earmarked to establish initial liquidity pool + - Source of the base asset to establish the initial liquidity pool + - Protocol Owned Liquidy (PoL): As Morpheus expands to environments, it’s essential to establish PoL. A detailed technical implication must be included. + +## Asset Integration Process +- Submission: Individuals or teams can suggest new yield-generating assets by submitting a detailed proposal to the Morpheus community repository. The proposal must include: + - Comprehensive details outlining the asset prerequisites + - Technical specifications + - Yield generation potential + - Risk assessment + - Weights requested to complete full development + +## Review: Submitted proposals undergo a two week review period by the Morpheus community and Code Providers, evaluating the asset's compatibility, security, and yield generation efficiency. +- Discussion & Refinement: Post-review, the submitting individual or team will have one week to provide final responses and incorporate any necessary updates based on the community review. +- Acceptance: An asset is accepted for integration based on Morpheus’ atomic governance framework. It is the work of the GitHub maintainers of the Smart Contract and Capital Provider Morpheus Reference Implementation repositories to ultimately accept the application. +- Development: The submitting individual or team develops the proposed integration. A public repository is required for code review. +- Testnet: A minimum of one month testnet period is required for sufficient community test and audit. +- Audit: A minimum of one comprehensive audit is required. This must be completed by a third party auditing firm. The audit process would earn a different set of weights, proposed by the auditor. +- Mainnet: Once sufficient testing and at least one third party audit is complete the mainnet deployment can commence. + +## Yield Calculation and Distribution +- Yield Calculation: For each approved asset, Morpheus will leverage the LayerZero protocol to calculate the real-time yield generated at every block. This yield will be priced against ETH, to standardize earnings across different assets. For networks without LayerZero support, the proposer of a new asset should specify how the value of yield will be calculated across chains. +- Pro-rata Distribution: Yield contributed by different assets will earn a pro-rata distribution from the Capital Providers' MOR emissions, Capital Providers earn 24% of daily MOR emissions. This ensures equitable distribution based on the value each asset brings to the Morpheus ecosystem. +- Distribution: MOR rewards for Capital Providers on different blockchains and Layer 2’s will be claimable block by block at an estimated 12 second granularity (ETH block time), if that is the slowest block time accepted. + +## Rewards for Contribution +Individuals or teams whose asset suggestions are accepted, merged into the Github repo, and successfully integrated into Morpheus will receive a one-time allocation of Code (24% of MOR emissions) contribution weights. This allocation will be based on the weights requested in the original proposal. +- Ongoing Contributions: The individual or team responsible for creating the integration must maintain and update the entire scope of the proposal. If maintenance is not upheld, their weights are subject to removal, and a new entity may assume the role, with new weights allocated accordingly. This ensures the continued alignment of incentives. + +## Ensuring Security and Efficiency +- Audits: All new integrations will undergo thorough security audits to protect the Morpheus ecosystem. +- Performance Monitoring: Continuous monitoring of asset performance, encompassing yield efficiency and risk exposure, is crucial for ensuring alignment with Morpheus' objectives. If the community or Code Contributors deem an asset no longer viable at any time, it may be excluded from the Morpheus ecosystem, with all associated weights revoked. + +## Conclusion +This proposed framework strategically positions Morpheus to dynamically respond to the free market's dictates, adeptly adjusting its operations to target the most beneficial sectors. Such adaptability aims to substantially mitigate risks tied to market fluctuations and technological changes, ensuring Morpheus has sustainability and continued relevance. The inclusion of new yield-generating assets offers a pathway to diversify and bolster the Morpheus capital foundation, delivering advantages to all involved. This methodical approach promotes a process for asset integration that is transparent, fair, and effective. From 98fb658afe507bed3c41a38e848c90d166d5c3c6 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 16:21:24 -0400 Subject: [PATCH 061/129] Update README.md Updating link for MRC 15 --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 836876b..f47b828 100644 --- a/README.md +++ b/README.md @@ -67,7 +67,7 @@ https://eips.ethereum.org/erc Provides a common language to describe interaction ## MRC 15: A Framework for Adding Yield-Generating Assets. - Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. -- Link: https://github.com/generativeone/Docs/blob/main/Expanding%20Horizon%20-%20The%20Morpheus%20Asset%20Integration%20Framework.md +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC15.md ## MRC 16: @@ -79,6 +79,7 @@ https://eips.ethereum.org/erc Provides a common language to describe interaction ## MRC 20: "Automated Recurring Revenue / Rewards" (ARR) - The MOR 20 Token Standard - Status: **Under Discussion** +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md#automated-recurring-revenue--rewards-arr-generalizing-the-tcm-model---mor20-token-standard - 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. @@ -87,4 +88,3 @@ This model can be extended to many software as a service projects as a means of 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. -- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md#automated-recurring-revenue--rewards-arr-generalizing-the-tcm-model---mor20-token-standard From ed7d4f5ce5f3a7c3f4db91f958612c09007c039c Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 16:23:06 -0400 Subject: [PATCH 062/129] Update MRC00.md Formatting. --- MRC00.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/MRC00.md b/MRC00.md index ad13e84..171bfa4 100644 --- a/MRC00.md +++ b/MRC00.md @@ -2,7 +2,8 @@ Each Morpheus Request for Comment should include the following: -- Google Drive or Notion is fine for an initial draft, however for the MRC to progress to the "Discussion" phase all the details of the MRC should be published on Github . +- Link to details of the MRC. + - Google Drive or Notion is fine for an initial draft before posting to the MRC repo, however for the MRC to be considered all the details of the MRC should be published on Github. - Add the MRC details in a new file in the MRC repo with a matching file named MRC####.md so everyone can comment on it directly in Github. - Include the link to the full MRC file in the summary in the Readme. From a3efb85b036912f63422b9e98a5382aae6974431 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 16:23:48 -0400 Subject: [PATCH 063/129] Update MRC00.md Formatting. --- MRC00.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/MRC00.md b/MRC00.md index 171bfa4..dbd79bb 100644 --- a/MRC00.md +++ b/MRC00.md @@ -3,9 +3,10 @@ Each Morpheus Request for Comment should include the following: - Link to details of the MRC. - - Google Drive or Notion is fine for an initial draft before posting to the MRC repo, however for the MRC to be considered all the details of the MRC should be published on Github. + - Add the MRC details in a new file in the MRC repo with a matching file named MRC####.md so everyone can comment on it directly in Github. - Include the link to the full MRC file in the summary in the Readme. + - Google Drive or Notion is fine for an initial draft before posting to the MRC repo, however for the MRC to be considered all the details of the MRC should be published on Github. - Problem - Solution From f01dc6f5296b3c1b95b2ac62f27bc4543e8833d8 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 16:26:22 -0400 Subject: [PATCH 064/129] Update MRC00.md Formatting and clarification of dependencies --- MRC00.md | 34 +++++++++++++++++++--------------- 1 file changed, 19 insertions(+), 15 deletions(-) diff --git a/MRC00.md b/MRC00.md index dbd79bb..e10a234 100644 --- a/MRC00.md +++ b/MRC00.md @@ -1,28 +1,32 @@ -## Morpheus Request for Comment Standard 00 +# Morpheus Request for Comment Standard 00 Each Morpheus Request for Comment should include the following: -- Link to details of the MRC. +## Link to details of the MRC. - Add the MRC details in a new file in the MRC repo with a matching file named MRC####.md so everyone can comment on it directly in Github. - Include the link to the full MRC file in the summary in the Readme. - Google Drive or Notion is fine for an initial draft before posting to the MRC repo, however for the MRC to be considered all the details of the MRC should be published on Github. -- Problem -- Solution - - Abstract - - Development strategy - - Tech Stack +## Problem -- End Results +## Solution + - Abstract + - Development strategy + - Tech Stack -- Value To Users +## Dependencies + - What other MRCs or related work needs to be completed for the proposal to be implemented. + - For example no new sources of yield can be added until cross EVM / chain interoperability is enabled in the Morpheus Smart Contracts. -- New weights requested +## End Results + +## Value To Users + +## New weights requested -- Effort required to Implement +## Effort required to Implement - Deliverables - - Meta - - Time to expire - - Dev Id assigned - - Tie to deliverables/testing + - Time to expire + - Dev Id assigned + - Tie to deliverables/testing From dd284b0ec1f16082135ea17890031741194181bb Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 17:57:08 -0400 Subject: [PATCH 065/129] Create MRC16.md Detailing the work so far on the MOR Interoperability for MRC16 --- MRC16.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 MRC16.md diff --git a/MRC16.md b/MRC16.md new file mode 100644 index 0000000..755f38b --- /dev/null +++ b/MRC16.md @@ -0,0 +1,25 @@ +# Toward MOR Interoperability + +## Introduction +To set the stage, MOR is currently instantiated as an ERC20 on Arbitrum. The coin exists, however is unmoveable/untradable until May 8th 2024. + +## Goal +MOR to be omnichain to whatever degree it makes sense. At minimum, we want it to exist seamlessly on Arbitrum & ETH L1. +Before May 8th 2024 to modify/upgrade/change the Smart Contract is easier. After that date it's obviously messier. Thus this topic should be considered / then implemented before May 8th 2024. + +## Evaluation +Many of the open source Smart Contract developers have evaluated LayerZero's OFT paradigm for use in the Morpheus Smart Contracts. +In particular, they liked: +- 1) the immutability/non-upgradability of the contracts, and +- 2) the gas abstraction for better UX. +- 3) The oracle function that can help denominate all yield contributions to Morpheus via ETH price. + +Whilte Morpheus is not exclusive to any chain or project, Layer Zero seems to be a good startig point to increase the Interoperability of the MOR token and broaden types of yield contribution. + +## Implementation +To start sending tokens from arbitrum to other chains, developers need to do is: +- 1. Deploy the OFT Adapter contract which works like a lockbox on the source chain, +- 2. Deploy the OFT contract on each new chain which will become the canonical MOR tokens for those new chains. + +## Technical Documentation Details +Link to Layer Zero Docs: https://docs.layerzero.network/contracts/oft-adapter From 7de3f8d6be5ed9d836c9fb902d1c45bf316e2958 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 17:58:09 -0400 Subject: [PATCH 066/129] Update README.md Adding name and link of MRC16 --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index f47b828..c6d444b 100644 --- a/README.md +++ b/README.md @@ -69,7 +69,9 @@ https://eips.ethereum.org/erc Provides a common language to describe interaction - Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC15.md -## MRC 16: +## MRC 16: Toward MOR Interoperability +- Status: "In Progress" +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC16.md ## MRC 17: From 69775cf5abf8526697c324608561a58866e27949 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 18:11:14 -0400 Subject: [PATCH 067/129] Update README.md List of MRIs. --- README.md | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index c6d444b..949c59e 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,22 @@ # Morpheus Request for Comments (MRC) -List of proposals extending Decentralized AI. -Similar to the function of the ERC system serves in Ethereum. -https://eips.ethereum.org/erc Provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. +Proposals to improve any of the Morpheus Reference Implementations (MRIs). + +See the details on all the of the MRIs here: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Reference%20Implementations.md +- Smart Contracts on Ethereum / Arbitrum +- Smart Agents Tools & Examples +- Morpheus Local Install Desktop / Mobile +- TCM / MOR20 Token Standard for Fair Launches +- Protection Fund +- Capital Proofs Extended beyond Lido stETH +- Compute Proofs Morpheus / Lumerin +- Code Proofs & Dashboards +- Frontend Proofs & Examples +- Interoperability + +Similar to the function of the ERC system serves in Ethereum, the MRC process provides a common language to describe interactions between models, agents, compute, payments, funding and so forth.. +https://eips.ethereum.org/erc + +There is a dedicated forum on Discord for the discussion of MRCs here: https://discord.com/channels/1151741790408429580/1218593251079094383 ## List of MRCs: From 350056637a75da1e2e3ef1f8700fab5a177d06c7 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 18:11:59 -0400 Subject: [PATCH 068/129] Update README.md Formatting. --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index 949c59e..c05ce21 100644 --- a/README.md +++ b/README.md @@ -13,8 +13,7 @@ See the details on all the of the MRIs here: https://github.com/MorpheusAIs/Docs - Frontend Proofs & Examples - Interoperability -Similar to the function of the ERC system serves in Ethereum, the MRC process provides a common language to describe interactions between models, agents, compute, payments, funding and so forth.. -https://eips.ethereum.org/erc +Similar to the function of the [ERC system](https://eips.ethereum.org/erc ) serves in Ethereum, the MRC process provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. There is a dedicated forum on Discord for the discussion of MRCs here: https://discord.com/channels/1151741790408429580/1218593251079094383 From 8f8e138e4797420b56377767c904967184f610dd Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 18:12:43 -0400 Subject: [PATCH 069/129] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c05ce21..68db738 100644 --- a/README.md +++ b/README.md @@ -84,7 +84,7 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC15.md ## MRC 16: Toward MOR Interoperability -- Status: "In Progress" +- Status: "In Progress" Actively being implemented by some of the open source Smart Contract developers. - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC16.md ## MRC 17: From 410500135ea59090c766e05f9c233dee1c0f84be Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 18:13:08 -0400 Subject: [PATCH 070/129] Update README.md Formatting. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 68db738..80fe4a2 100644 --- a/README.md +++ b/README.md @@ -84,7 +84,7 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC15.md ## MRC 16: Toward MOR Interoperability -- Status: "In Progress" Actively being implemented by some of the open source Smart Contract developers. +- Status: **In Progress** Actively being implemented by some of the open source Smart Contract developers. - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC16.md ## MRC 17: From 2e02cb732ebd4266de4bb6db493370dc99a0e654 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 18:18:18 -0400 Subject: [PATCH 071/129] Update MRC00.md MRCs must include the list of Morpheus Reference Implementations they will effect. --- MRC00.md | 32 +++++++++++++++++++++++--------- 1 file changed, 23 insertions(+), 9 deletions(-) diff --git a/MRC00.md b/MRC00.md index e10a234..6e73bb7 100644 --- a/MRC00.md +++ b/MRC00.md @@ -3,21 +3,35 @@ Each Morpheus Request for Comment should include the following: ## Link to details of the MRC. - - - Add the MRC details in a new file in the MRC repo with a matching file named MRC####.md so everyone can comment on it directly in Github. - - Include the link to the full MRC file in the summary in the Readme. - - Google Drive or Notion is fine for an initial draft before posting to the MRC repo, however for the MRC to be considered all the details of the MRC should be published on Github. +- Add the MRC details in a new file in the MRC repo with a matching file named MRC####.md so everyone can comment on it directly in Github. +- Include the link to the full MRC file in the summary in the Readme. +- Google Drive or Notion is fine for an initial draft before posting to the MRC repo, however for the MRC to be considered all the details of the MRC should be published on Github. + +## List of Morpheus Reference Implementations Effected +All MRCs should include a list of the Morpheus Reference Implementations (MRIs) they will update / effect. + +See the details on all the of the MRIs here: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Reference%20Implementations.md +- Smart Contracts on Ethereum / Arbitrum +- Smart Agents Tools & Examples +- Morpheus Local Install Desktop / Mobile +- TCM / MOR20 Token Standard for Fair Launches +- Protection Fund +- Capital Proofs Extended beyond Lido stETH +- Compute Proofs Morpheus / Lumerin +- Code Proofs & Dashboards +- Frontend Proofs & Examples +- Interoperability ## Problem ## Solution - - Abstract - - Development strategy - - Tech Stack +- Abstract +- Development strategy +- Tech Stack ## Dependencies - - What other MRCs or related work needs to be completed for the proposal to be implemented. - - For example no new sources of yield can be added until cross EVM / chain interoperability is enabled in the Morpheus Smart Contracts. +- What other MRCs or related work needs to be completed for the proposal to be implemented. +- For example no new sources of yield can be added until cross EVM / chain interoperability is enabled in the Morpheus Smart Contracts. ## End Results From 4119fc0a1c91a993a09e659d368ae7f1d9732367 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 18:21:52 -0400 Subject: [PATCH 072/129] Update MRC00.md Updating the details of the MRC00 requirements. --- MRC00.md | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/MRC00.md b/MRC00.md index 6e73bb7..2a49eda 100644 --- a/MRC00.md +++ b/MRC00.md @@ -2,7 +2,7 @@ Each Morpheus Request for Comment should include the following: -## Link to details of the MRC. +## Link to Details of the MRC - Add the MRC details in a new file in the MRC repo with a matching file named MRC####.md so everyone can comment on it directly in Github. - Include the link to the full MRC file in the summary in the Readme. - Google Drive or Notion is fine for an initial draft before posting to the MRC repo, however for the MRC to be considered all the details of the MRC should be published on Github. @@ -23,6 +23,7 @@ See the details on all the of the MRIs here: https://github.com/MorpheusAIs/Docs - Interoperability ## Problem +- Describe the problem being addressed by the MRC. ## Solution - Abstract @@ -34,13 +35,17 @@ See the details on all the of the MRIs here: https://github.com/MorpheusAIs/Docs - For example no new sources of yield can be added until cross EVM / chain interoperability is enabled in the Morpheus Smart Contracts. ## End Results +- List what the effect of the final implementation be. ## Value To Users +- What will the value to users be and which users in the Morpheus system. + +## New Weights Requested +- All weights are rewarded after value is provided and accepted by repository maintainers. +- Detail the weights requested and how that fits into the weight schedule for that Morpheus Reference Implementation -## New weights requested - ## Effort required to Implement - - Deliverables - - Time to expire - - Dev Id assigned - - Tie to deliverables/testing +- Deliverables +- Time to expire +- Dev Id assigned +- Tie to deliverables/testing From a9355e9c38c2a65864d012d5f925ca8b13a3c23b Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 18:22:20 -0400 Subject: [PATCH 073/129] Update MRC00.md Title update. --- MRC00.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MRC00.md b/MRC00.md index 2a49eda..e14f7c7 100644 --- a/MRC00.md +++ b/MRC00.md @@ -1,4 +1,4 @@ -# Morpheus Request for Comment Standard 00 +# MRC 00: Morpheus Request for Comment Standard & Requirements Each Morpheus Request for Comment should include the following: From 4fe72755740de79fb52edece20b0b9b349bdc03a Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 18:28:31 -0400 Subject: [PATCH 074/129] Update MRC16.md Title updated with MRC number. --- MRC16.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MRC16.md b/MRC16.md index 755f38b..ae89475 100644 --- a/MRC16.md +++ b/MRC16.md @@ -1,4 +1,4 @@ -# Toward MOR Interoperability +# MRC16: Toward MOR Interoperability ## Introduction To set the stage, MOR is currently instantiated as an ERC20 on Arbitrum. The coin exists, however is unmoveable/untradable until May 8th 2024. From 42e65a53bc3bd3cd8d52726665fbe10d42d7124d Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 18:29:57 -0400 Subject: [PATCH 075/129] Update MRC00.md Diagram showing Morpheus Reference Implementations --- MRC00.md | 1 + 1 file changed, 1 insertion(+) diff --git a/MRC00.md b/MRC00.md index e14f7c7..d745b52 100644 --- a/MRC00.md +++ b/MRC00.md @@ -9,6 +9,7 @@ Each Morpheus Request for Comment should include the following: ## List of Morpheus Reference Implementations Effected All MRCs should include a list of the Morpheus Reference Implementations (MRIs) they will update / effect. +![Morpheus Reference Implementations 2024 03 03](https://github.com/MorpheusAIs/MRC/assets/1563345/16cea869-03e9-405e-b281-aa084089c698) See the details on all the of the MRIs here: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Reference%20Implementations.md - Smart Contracts on Ethereum / Arbitrum From 56bb79a185aa86cbbc26bdfc5a9a5d5170e98e12 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 18:34:05 -0400 Subject: [PATCH 076/129] Create MRC17.md Moving MRC17 to Github. --- MRC17.md | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 MRC17.md diff --git a/MRC17.md b/MRC17.md new file mode 100644 index 0000000..86edddc --- /dev/null +++ b/MRC17.md @@ -0,0 +1,36 @@ +# Proposal + +## Introduction +We propose capital contribution integration for Morpheus with the Solana blockchain, aimed at significantly enhancing the liquidity of Morpheus AI's capital providers pool. By leveraging Solana's high-performance capabilities and developing a bespoke smart contract, we aim to introduce SOL staking and contributing staked SOL yield in exchange for MOR tokens. Furthermore, Solana's low transaction fees and high throughput offer a compelling case for it to be a suitable platform for Morpheus, potentially providing an efficient and cost-effective environment for users and the ecosystem at large. + +## Implementation: +Solana Integration +We propose to develop a smart contract on the Solana blockchain that allows users to directly stake SOL in exchange for MOR token rewards. This integration will enable Morpheus AI to access Solana's liquidity and user base, providing a new avenue for growth and capital. + +## Smart Contract Development: +1) Direct SOL Staking: Users can stake SOL directly via the developed smart contract, with a guaranteed 1:1 return upon redemption. +2) Conversion to JitoSOL: The contract will automatically convert staked SOL into JitoSOL, enabling the protocol to earn staking rewards from the Jito Network. +3) Reward Mechanism: Accrued SOL rewards will be sold daily and added to the Protocol-owned Liquidity (POL) on Morpheus +4) Locking Mechanism for withdrawal: There will be a standard 7-day lock-in for the SOL contributed +Oracle Use +For the allocation of MOR rewards, an oracle will capture daily Solana market data at a specific time (e.g., 5 PM UTC), ensuring fair and transparent distribution. This process will meticulously be recorded on the Ethereum blockchain by Morpheus contracts, reinforcing the integrity and auditability of the reward mechanism within the ecosystem. This approach underscores the commitment to fairness, leveraging blockchain's transparency to benefit all ecosystem participants. + +## Reward Allocation Strategy: +In order to have fair and equitable reward distribution to SOL stakers, we plan to utilize the oracle price data to calculate the USD value of SOL and yield contribution. The rewards for SOL stakers will be calculated on a pro-rata basis taking the st-ETH and other capital contribution into account. + +## Bridging and Distribution +Bridging and distribution for MOR rewards to SOL stakers involves using cross-chain technology like Wormhole. This process allows the transfer of MOR tokens from the Ethereum blockchain to Solana, where they're wrapped. The solana smart contract receives the equivalent MOR reward tokens and distributes among users based on their capital contribution. +To enhance security and governance in the process of bridging and distributing MOR rewards, a multisignature wallet approach will be utilized (this can be a Safe multisig wallet on Ethereum and a Squads mulitisg wallet on the Solana end). This method involves requiring multiple signatures from designated members of the Morpheus AI team or community before any transactions can be approved and executed. + +## Wrapped MOR Distribution +Solana stakers will receive wrapped MOR tokens, maintaining a 1:1 value equivalence with MOR on the Ethereum chain, facilitated by cross-chain solutions like Wormhole. Distribution involves converting MOR tokens into a wrapped Solana-compatible format, allowing them to be easily transferred and used within the Solana ecosystem. +Benefits: +- 1) Enhanced Liquidity: The integration significantly increases liquidity, attracting more +capital contribution to Morpheus AI. +- 2) Market Expansion: JtoSol has more than $1bn TVL and should be able to access a +decent portion of it for Morpheus. Accessing Solana's user base also opens new +markets and opportunities for growth. +- 3) Innovative Ecosystem: This partnership exemplifies blockchain interoperability, +showcasing a commitment to innovation and user benefits. +- 4) Affordable Transactions with Solana: Solana stands out in the market for its +exceptionally low transaction fees paired with rapid processing speeds. This makes it an ideal blockchain for Morpheus to integrate with. The combination of affordability and efficiency ensures high transaction volumes and consistent liquidity flow. From 4f1d7836677fd8123c29602743e97d85cf7cde0c Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 18:36:31 -0400 Subject: [PATCH 077/129] Update MRC17.md Adding the diagram for MRC17 --- MRC17.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/MRC17.md b/MRC17.md index 86edddc..7503dc2 100644 --- a/MRC17.md +++ b/MRC17.md @@ -1,4 +1,4 @@ -# Proposal +# MRC17: Adding Solana Yield & MOR Token Proposal ## Introduction We propose capital contribution integration for Morpheus with the Solana blockchain, aimed at significantly enhancing the liquidity of Morpheus AI's capital providers pool. By leveraging Solana's high-performance capabilities and developing a bespoke smart contract, we aim to introduce SOL staking and contributing staked SOL yield in exchange for MOR tokens. Furthermore, Solana's low transaction fees and high throughput offer a compelling case for it to be a suitable platform for Morpheus, potentially providing an efficient and cost-effective environment for users and the ecosystem at large. @@ -34,3 +34,6 @@ markets and opportunities for growth. showcasing a commitment to innovation and user benefits. - 4) Affordable Transactions with Solana: Solana stands out in the market for its exceptionally low transaction fees paired with rapid processing speeds. This makes it an ideal blockchain for Morpheus to integrate with. The combination of affordability and efficiency ensures high transaction volumes and consistent liquidity flow. + +![Flow Diagram Overview](https://github.com/MorpheusAIs/MRC/assets/1563345/f17c4122-3c0b-4bd2-a50b-05fc523e5eb2) + From ce6ca6d42c191839533e8cdb2ee15e6fef7eb0e8 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 18:39:46 -0400 Subject: [PATCH 078/129] Update README.md Updated list and description for MRC17. --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 80fe4a2..ed5540e 100644 --- a/README.md +++ b/README.md @@ -87,7 +87,9 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d - Status: **In Progress** Actively being implemented by some of the open source Smart Contract developers. - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC16.md -## MRC 17: +## MRC 17: Adding Solana Yield & MOR Token Proposal +- Status: **Under Discussion** similar proposal is listed in MRC 13 also under discussion. +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC17.md ## MRC 18: From 8ab86069f71fbe91b6655ebc7f108fa693277c70 Mon Sep 17 00:00:00 2001 From: kcnnn Date: Sun, 17 Mar 2024 19:24:57 -0500 Subject: [PATCH 079/129] Create MRC 21: Governance Agent ATX DAO Autonomous Governance AI Agent --- MRC 21: Governance Agent | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 MRC 21: Governance Agent diff --git a/MRC 21: Governance Agent b/MRC 21: Governance Agent new file mode 100644 index 0000000..15117e4 --- /dev/null +++ b/MRC 21: Governance Agent @@ -0,0 +1,2 @@ +Status: Under Discussion +Link: https://docs.google.com/document/d/1xWAu7gew2wrtk_38areb56h_byO_86LHEQiBcsGByDk/edit From 66f4793c311ac0c0afd99b017189c6ebb7e2550b Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 22:13:08 -0400 Subject: [PATCH 080/129] Update MRC00.md Additional MRC00 details. --- MRC00.md | 57 ++++++++++++++++++++++++++++++++------------------------ 1 file changed, 33 insertions(+), 24 deletions(-) diff --git a/MRC00.md b/MRC00.md index d745b52..8bf819c 100644 --- a/MRC00.md +++ b/MRC00.md @@ -1,11 +1,30 @@ # MRC 00: Morpheus Request for Comment Standard & Requirements +### What is an MRC? +MRC stands for Morpheus Request for Comments. It’s a document that describes a change to Morpheus. + +### Who’s it for? +Contributors to the MOR codebase, who are looking for direction or inspiration on how to get weights. +Users in the MOR Ecosystem who want to suggest specific changes to Morpheus + +### Why an MRC Guide? +Well formatted MRCs are easy to review and discuss amongst the community. +It allows weights to be distributed only to people who have provided good reason to receive them. + +### Where and when can I submit my MRC? +Until the end of Fair Launch, the MRCs will first be on GitHub and then on MOR.Software, ultimately reflected on other dashboards. + +### How do I write a well-formed MRC? +Start by reading other MRCs. When you write your MRC, use this Example Table of Contents as a guide. + +## Standard Information to Include Each Morpheus Request for Comment should include the following: +![MRC Table of Contents 2024 03 17](https://github.com/MorpheusAIs/MRC/assets/1563345/2ca0b765-5aec-4ce0-8dd0-31a86963a892) -## Link to Details of the MRC +## Link to Details of the MRC In The MRC Repo Readme File - Add the MRC details in a new file in the MRC repo with a matching file named MRC####.md so everyone can comment on it directly in Github. -- Include the link to the full MRC file in the summary in the Readme. -- Google Drive or Notion is fine for an initial draft before posting to the MRC repo, however for the MRC to be considered all the details of the MRC should be published on Github. +- Add your MRC number and link to the full file here: https://github.com/MorpheusAIs/MRC/blob/main/README.md +- Google Drive or Notion are good tools for drafting however for the MRC to be considered, all the details of the MRC should be published on Github. ## List of Morpheus Reference Implementations Effected All MRCs should include a list of the Morpheus Reference Implementations (MRIs) they will update / effect. @@ -23,30 +42,20 @@ See the details on all the of the MRIs here: https://github.com/MorpheusAIs/Docs - Frontend Proofs & Examples - Interoperability -## Problem -- Describe the problem being addressed by the MRC. +## MRC FAQ -## Solution -- Abstract -- Development strategy -- Tech Stack +Can an MRC be submitted by a group? +↳ Yes, but weights can be attributed to only one DeveloperID. -## Dependencies -- What other MRCs or related work needs to be completed for the proposal to be implemented. -- For example no new sources of yield can be added until cross EVM / chain interoperability is enabled in the Morpheus Smart Contracts. +Can I submit and manage my MRCs through my Profile page on MOR.software? +↳ Yes, that’s probably the easiest way to do it. -## End Results -- List what the effect of the final implementation be. +Can I include diagrams, images, and videos in an MRC? +↳ Please do. And keep any files under 25 MB. 100MB total per MRC -## Value To Users -- What will the value to users be and which users in the Morpheus system. +Can I just submit code as the MRC? +↳ No. The point of the MRC is to think first, code second. -## New Weights Requested -- All weights are rewarded after value is provided and accepted by repository maintainers. -- Detail the weights requested and how that fits into the weight schedule for that Morpheus Reference Implementation +What if I’m not a developer? +↳ No problem. Anyone can create an MRC. -## Effort required to Implement -- Deliverables -- Time to expire -- Dev Id assigned -- Tie to deliverables/testing From 1e35ad575fca283e1be731c2de5096f0a41acb62 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 22:13:46 -0400 Subject: [PATCH 081/129] Update MRC00.md Update title. --- MRC00.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MRC00.md b/MRC00.md index 8bf819c..af0db03 100644 --- a/MRC00.md +++ b/MRC00.md @@ -1,4 +1,4 @@ -# MRC 00: Morpheus Request for Comment Standard & Requirements +# MRC 00: Morpheus Request for Comment Standards & Guide ### What is an MRC? MRC stands for Morpheus Request for Comments. It’s a document that describes a change to Morpheus. From 6e0fcfdb2b975505998984299970c571f5de811f Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 22:14:15 -0400 Subject: [PATCH 082/129] Update MRC00.md Guide --- MRC00.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MRC00.md b/MRC00.md index af0db03..46ca5eb 100644 --- a/MRC00.md +++ b/MRC00.md @@ -1,4 +1,4 @@ -# MRC 00: Morpheus Request for Comment Standards & Guide +# MRC 00: Morpheus Request for Comment (MRC) Guide ### What is an MRC? MRC stands for Morpheus Request for Comments. It’s a document that describes a change to Morpheus. From 60890ddaf9a0a9975c67af75c09844a7825478a6 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 22:22:09 -0400 Subject: [PATCH 083/129] Update MRC00.md Updated image for diagram of example table of contents. --- MRC00.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MRC00.md b/MRC00.md index 46ca5eb..32b6a25 100644 --- a/MRC00.md +++ b/MRC00.md @@ -19,7 +19,7 @@ Start by reading other MRCs. When you write your MRC, use this Example Table of ## Standard Information to Include Each Morpheus Request for Comment should include the following: -![MRC Table of Contents 2024 03 17](https://github.com/MorpheusAIs/MRC/assets/1563345/2ca0b765-5aec-4ce0-8dd0-31a86963a892) +![MRC Example Table 4](https://github.com/MorpheusAIs/MRC/assets/1563345/bab289d6-87ec-4c89-ac76-7ab12607fb11) ## Link to Details of the MRC In The MRC Repo Readme File - Add the MRC details in a new file in the MRC repo with a matching file named MRC####.md so everyone can comment on it directly in Github. From ed4fdbe457bd8c7db92706dca498485008dc7368 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 22:42:29 -0400 Subject: [PATCH 084/129] Update README.md Cleaning up the MRC description. --- README.md | 12 +++--------- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index ed5540e..8d2574e 100644 --- a/README.md +++ b/README.md @@ -95,14 +95,8 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d ## MRC 19: -## MRC 20: "Automated Recurring Revenue / Rewards" (ARR) - The MOR 20 Token Standard +## MRC 20: The MOR 20 Token Standard - "Automated Recurring Revenue / Rewards" (ARR) - Status: **Under Discussion** - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md#automated-recurring-revenue--rewards-arr-generalizing-the-tcm-model---mor20-token-standard -- 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. + +## MRC 21: From 05e9dd9c794909c6c658ba463759afb42fd18f07 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 22:43:00 -0400 Subject: [PATCH 085/129] Update README.md Shortening the introduction. --- README.md | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/README.md b/README.md index 8d2574e..cff7509 100644 --- a/README.md +++ b/README.md @@ -2,16 +2,6 @@ Proposals to improve any of the Morpheus Reference Implementations (MRIs). See the details on all the of the MRIs here: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Reference%20Implementations.md -- Smart Contracts on Ethereum / Arbitrum -- Smart Agents Tools & Examples -- Morpheus Local Install Desktop / Mobile -- TCM / MOR20 Token Standard for Fair Launches -- Protection Fund -- Capital Proofs Extended beyond Lido stETH -- Compute Proofs Morpheus / Lumerin -- Code Proofs & Dashboards -- Frontend Proofs & Examples -- Interoperability Similar to the function of the [ERC system](https://eips.ethereum.org/erc ) serves in Ethereum, the MRC process provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. From 0358ed8ce9083c50016da6b5be7b177f2e6d514e Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 22:46:28 -0400 Subject: [PATCH 086/129] Create MRC20.md Recording the MRC20 as defining the Automated Recurring Revenue as implemented in the MOR20 Token Standard. --- MRC20.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 MRC20.md diff --git a/MRC20.md b/MRC20.md new file mode 100644 index 0000000..a0affc6 --- /dev/null +++ b/MRC20.md @@ -0,0 +1,15 @@ +# MRC 20: Automated Recurring Revenue / Rewards = ARR via the MOR20 Token Standard + +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: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md#automated-recurring-revenue--rewards-arr-generalizing-the-tcm-model---mor20-token-standard + +- 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. From 0096f225d6f5e11f9acef8634e9de97c4f188288 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 22:48:27 -0400 Subject: [PATCH 087/129] Update README.md Title of MRC 21. --- README.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index cff7509..e585bb5 100644 --- a/README.md +++ b/README.md @@ -86,7 +86,9 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d ## MRC 19: ## MRC 20: The MOR 20 Token Standard - "Automated Recurring Revenue / Rewards" (ARR) -- Status: **Under Discussion** -- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md#automated-recurring-revenue--rewards-arr-generalizing-the-tcm-model---mor20-token-standard +- Status: **Implementated** +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC20.md -## MRC 21: +## MRC 21: Non Fungible Agents +- Status: **In Discussion** +- Link: From 13743c768c802a4ae65d983aa15ff6d73165c661 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 23:08:16 -0400 Subject: [PATCH 088/129] Rename MRC 21: Governance Agent to MRC18: Governance Agent Renaming to MRC18 --- MRC 21: Governance Agent => MRC18: Governance Agent | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename MRC 21: Governance Agent => MRC18: Governance Agent (100%) diff --git a/MRC 21: Governance Agent b/MRC18: Governance Agent similarity index 100% rename from MRC 21: Governance Agent rename to MRC18: Governance Agent From 6acf5f0b63f7142463f6ef1dbfac56accd928560 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 23:09:26 -0400 Subject: [PATCH 089/129] Update README.md Adding MRC18 to the Readme --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index e585bb5..5b211a9 100644 --- a/README.md +++ b/README.md @@ -81,7 +81,9 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d - Status: **Under Discussion** similar proposal is listed in MRC 13 also under discussion. - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC17.md -## MRC 18: +## MRC 18: Governance Agent +- Status: **Under Discussion** +Link: https://docs.google.com/document/d/1xWAu7gew2wrtk_38areb56h_byO_86LHEQiBcsGByDk/edit ## MRC 19: From b94382ca6ae5a441b3b29761345322ae4b424567 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 23:09:46 -0400 Subject: [PATCH 090/129] Update README.md Formatting. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5b211a9..55ed196 100644 --- a/README.md +++ b/README.md @@ -83,7 +83,7 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d ## MRC 18: Governance Agent - Status: **Under Discussion** -Link: https://docs.google.com/document/d/1xWAu7gew2wrtk_38areb56h_byO_86LHEQiBcsGByDk/edit +- Link: https://docs.google.com/document/d/1xWAu7gew2wrtk_38areb56h_byO_86LHEQiBcsGByDk/edit ## MRC 19: From 21302b3f12b38ab92af8914e328260897bd72252 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 23:11:14 -0400 Subject: [PATCH 091/129] Update README.md Place holder for MRC19 Cosmos & Thorchain Expansion of Morpheus --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 55ed196..7b9b570 100644 --- a/README.md +++ b/README.md @@ -85,7 +85,9 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d - Status: **Under Discussion** - Link: https://docs.google.com/document/d/1xWAu7gew2wrtk_38areb56h_byO_86LHEQiBcsGByDk/edit -## MRC 19: +## MRC 19: Cosmos & Thorchain Expansion of Morpheus +- Status: **Under Discussion** +- Link: ## MRC 20: The MOR 20 Token Standard - "Automated Recurring Revenue / Rewards" (ARR) - Status: **Implementated** From 8d87ffe4030e87518aa768e1cbc14ac8ce4f5f0a Mon Sep 17 00:00:00 2001 From: ScottBerenzweig <76454555+betterbrand@users.noreply.github.com> Date: Sun, 17 Mar 2024 20:18:06 -0700 Subject: [PATCH 092/129] Create MRC21 Non-Fungible Agents.md Non-Fungible Agents (NFAs) on the Morpheus Network --- MRC21.md | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 MRC21.md diff --git a/MRC21.md b/MRC21.md new file mode 100644 index 0000000..4f70f3b --- /dev/null +++ b/MRC21.md @@ -0,0 +1,29 @@ +## MRC21: Non Fungible Agents + +### Abstract +As a way of identifying agents on the blockchain, there is no need to reinvent the wheel. The MOR21 Non-Fungible Agent (NFA) is a technical framework, defining a set of rules and interfaces for creating and managing unique smart agents in the Morpheus ecosystem. + +Tied by hash to the Smart Agent code, this MOR21 smart contract adds key features to the agent toolkit. + +### Metadata +A Non-Fungible Agent requires identifiers including name and symbol identifiers. A URI (uniform resource identifier) allows for the navigation of instruction to a Smart Agent. A toolset and functional limits are included in this data and segmented in a marketplace. + +### Functionality +A Non-fungible agent has an Agentic ABI, providing a functional interface to the agent, with a minimum weights and model requirement. + +### Testing benchmarks +A Non-Fungible Agent must include performance claims at the time of publication to chain. Users of an agent can calibrate for accuracy and fidelity to test a Smart Agent’s use of inference + +### Trackable Ownership +Expanding on ownership of NFTs each Smart Agent is assigned an Agent Identification Number and linked to is owner through the use of the ownerOf function + +### Mitigating Stake +To mitigate against malicious usage, the agent creator stakes a proportional amount to the cost of the Smart Agent’s license and usage costs. + +### Ownership, Lease, and License Usage +Agents can be bought and sold in a marketplace, similar to a non-fungible token. A multisig-type ownership function allows for fee and license distribution amongst multiple parties. Fees are collected based on the amount of inference used, the computer used, and the, complexity of tasks performed. Agents can be made available to accomplish remote tasks in exchange for MOR. Availability can be exclusive or open, providing immutable access rights. + +### Security +The same tooling that secures the non-fungible token also secures the non-fungible agent. + + From 277c6fa375a77d3060399562c300a5813c98a737 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 23:23:22 -0400 Subject: [PATCH 093/129] Update README.md Link for MRC21 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7b9b570..abc577f 100644 --- a/README.md +++ b/README.md @@ -95,4 +95,4 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d ## MRC 21: Non Fungible Agents - Status: **In Discussion** -- Link: +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC21.md From 8c187e83e989c95fa8f4aaa18eb7186a7c4355d9 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 23:27:15 -0400 Subject: [PATCH 094/129] Update and rename MRC18: Governance Agent to MRC18: Governance Agent.md Importing text from Google Docs to Github. --- MRC18: Governance Agent | 2 -- MRC18: Governance Agent.md | 36 ++++++++++++++++++++++++++++++++++++ 2 files changed, 36 insertions(+), 2 deletions(-) delete mode 100644 MRC18: Governance Agent create mode 100644 MRC18: Governance Agent.md diff --git a/MRC18: Governance Agent b/MRC18: Governance Agent deleted file mode 100644 index 15117e4..0000000 --- a/MRC18: Governance Agent +++ /dev/null @@ -1,2 +0,0 @@ -Status: Under Discussion -Link: https://docs.google.com/document/d/1xWAu7gew2wrtk_38areb56h_byO_86LHEQiBcsGByDk/edit diff --git a/MRC18: Governance Agent.md b/MRC18: Governance Agent.md new file mode 100644 index 0000000..c72b08d --- /dev/null +++ b/MRC18: Governance Agent.md @@ -0,0 +1,36 @@ +# Autonomous Governance AI Agent for ATX DAO +tldr: ATX DAO is creating an AI agent to review, give feedback on, and vote on all DAO proposals. + +## Introduction: +We propose the establishment of an Autonomous Governance AI Agent within ATX DAO. This AI agent will serve as a knowledgeable, impartial entity with one ATX DAO NFT, with one voting right in all proposals. Additionally, it will provide comprehensive information regarding proposed initiatives, outlining their benefits and potential challenges. This AI agent aims to enhance the efficiency, transparency, and decision-making capabilities of our DAO. + +## Purpose: +The primary purpose of the Autonomous Governance AI Agent is to augment the governance framework of our DAO by offering informed insights and voting power. By leveraging artificial intelligence, the agent will contribute to objective decision-making processes, ensuring that proposals are thoroughly evaluated before votes are cast. + +## Key Features: +Voting Rights: The AI agent will possess one NFT, entitling it to one vote in all proposals within the DAO. +Information Dissemination: It will analyze and provide detailed information about each proposal, highlighting potential benefits and drawbacks. +Transparency: The AI agent will operate transparently, making its decision-making process and rationale accessible to all members of the DAO. +Continuous Learning: Through machine learning algorithms, the agent will continuously adapt and improve its decision-making abilities based on past outcomes and community feedback. + +## Implementation: +Development: The AI agent will be developed using state-of-the-art artificial intelligence technologies, ensuring its ability to process and analyze vast amounts of data. The agent will be using open source AI agents and AI models via Morpheus AI (mor.org). +Integration: Integration with the DAO’s governance platform will enable seamless participation in voting processes and access to proposal information. +Testing: Rigorous testing will be conducted to validate the accuracy and reliability of the AI agent’s decision-making capabilities before deployment. +Deployment: Upon successful testing, the AI agent will be deployed within the DAO’s governance framework, where it will actively participate in decision-making processes. + +## Benefits: +Enhanced Decision Making: The AI agent will contribute to more informed and objective decision-making, leading to better outcomes for the DAO. +Increased Efficiency: By providing comprehensive information on proposals, the agent will streamline the decision-making process, reducing the time required for deliberation. +Improved Transparency: Transparency will be enhanced as the AI agent’s rationale for voting decisions will be accessible to all DAO members. +Community Empowerment: The presence of an AI agent with voting rights democratizes governance within the DAO, giving every proposal equal consideration. + +## Possible Challenges: +Bias Mitigation: Efforts must be made to mitigate any potential biases in the AI agent’s decision-making process to ensure fairness and objectivity. +Technical Limitations: Technical challenges may arise during the development and deployment phases, requiring diligent troubleshooting and refinement. +Community Adoption: Ensuring community acceptance and trust in the AI agent’s capabilities may require effective communication and education initiatives. + +## Conclusion: +The creation of an Autonomous Governance AI Agent represents a significant step forward in enhancing the governance capabilities of our DAO. By combining cutting-edge artificial intelligence with decentralized decision-making, we can achieve greater efficiency, transparency, and inclusivity in our operations. We urge the DAO members to consider this proposal and support the establishment of the AI agent for the benefit of our collective endeavors. + +Link to proposal: https://snapshot.org/#/atxdao.eth/proposal/0xda4e521275c7708efc90349b3319e3e82859c06a56af6ca8e5e27127c42e9c98 From 8c7756b43ca5d96123e32e442bca2164a937899e Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 23:27:28 -0400 Subject: [PATCH 095/129] Update MRC18: Governance Agent.md --- MRC18: Governance Agent.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MRC18: Governance Agent.md b/MRC18: Governance Agent.md index c72b08d..27189c6 100644 --- a/MRC18: Governance Agent.md +++ b/MRC18: Governance Agent.md @@ -1,4 +1,4 @@ -# Autonomous Governance AI Agent for ATX DAO +# MRC18: Autonomous Governance AI Agent for ATX DAO tldr: ATX DAO is creating an AI agent to review, give feedback on, and vote on all DAO proposals. ## Introduction: From 88d068f5fec26c5586fc061b1ad9b174de5b2fd8 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 23:28:12 -0400 Subject: [PATCH 096/129] Update README.md Link to MRC18 on Github. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index abc577f..080f803 100644 --- a/README.md +++ b/README.md @@ -83,7 +83,7 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d ## MRC 18: Governance Agent - Status: **Under Discussion** -- Link: https://docs.google.com/document/d/1xWAu7gew2wrtk_38areb56h_byO_86LHEQiBcsGByDk/edit +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC18:%20Governance%20Agent.md ## MRC 19: Cosmos & Thorchain Expansion of Morpheus - Status: **Under Discussion** From 24a29a497bd6f535ebad2b099ccfbb36c86bfb37 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 23:37:47 -0400 Subject: [PATCH 097/129] Create MRC19.md Details of why adding Cosmos & Thorchain would benefit Morpheus and expand its community. --- MRC19.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 MRC19.md diff --git a/MRC19.md b/MRC19.md new file mode 100644 index 0000000..f81873d --- /dev/null +++ b/MRC19.md @@ -0,0 +1,17 @@ +# MRC 19: Cosmos & Thorchain Expansion of Morpheus + +## History +The original Morpheus whitepaper proposed using Thorchain yield as the means for Capital Providers to contribute to Morpheus. + +## Tech Problem +While the Smart Contracts were in development the open source devs notes that there was a feature missing from Thorchain that would make this possible. + +## Dependency +This missing feature is support for multi-outputs from yield generated from a Thorchain Saver. Currently when a Thorchain Saver vault is set up the yield can only be returned to the same address as the that contributed the crypto to the Saver Vault. + +## Solution +When Thorchain adds support for Multiple addresses to be rewarded yield, then the Morpheus Capital Provider can be extended to Thorchain yield types. + +## Value +This would be a substaintial upgrade as Thorchain create sustainable native yield in BTC, ETH, AVAX, USDT, BCH, USDC, BNB, LTC, DOGE & ATOM. +This represents yield from many of the most active chains and would add a great deal of the most active crypto communities to the ranks of Morpheus Capital Providers. From 021d5daa7a1be7b2f987da61fdd2999ea2552f2a Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 23:38:42 -0400 Subject: [PATCH 098/129] Update README.md Details and link to MRC19 proposal. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 080f803..f5c5fa3 100644 --- a/README.md +++ b/README.md @@ -87,7 +87,7 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d ## MRC 19: Cosmos & Thorchain Expansion of Morpheus - Status: **Under Discussion** -- Link: +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC19.md ## MRC 20: The MOR 20 Token Standard - "Automated Recurring Revenue / Rewards" (ARR) - Status: **Implementated** From e8949ec351537c1463088717363bd433f0dcec49 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 23:46:21 -0400 Subject: [PATCH 099/129] Update MRC19.md Link to the Thorchain Saver Vaults --- MRC19.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/MRC19.md b/MRC19.md index f81873d..c3682cd 100644 --- a/MRC19.md +++ b/MRC19.md @@ -15,3 +15,6 @@ When Thorchain adds support for Multiple addresses to be rewarded yield, then th ## Value This would be a substaintial upgrade as Thorchain create sustainable native yield in BTC, ETH, AVAX, USDT, BCH, USDC, BNB, LTC, DOGE & ATOM. This represents yield from many of the most active chains and would add a great deal of the most active crypto communities to the ranks of Morpheus Capital Providers. + +## Link to Source of Yield Available +https://thorchain.net/thorfi/savers From e9ddea641e098167311600060589a77661c2da54 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Sun, 17 Mar 2024 23:46:48 -0400 Subject: [PATCH 100/129] Update MRC19.md Formatting. From 9c3c05a02b9fe69b7c932b88f90342b9c67a8079 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Mon, 18 Mar 2024 17:30:56 +0200 Subject: [PATCH 101/129] Update MRC08.md --- MRC08.md | 101 +++++++++++++++++++++---------------------------------- 1 file changed, 38 insertions(+), 63 deletions(-) diff --git a/MRC08.md b/MRC08.md index 50c1857..1810eb3 100644 --- a/MRC08.md +++ b/MRC08.md @@ -8,92 +8,67 @@ The Web3 community has long suffered from a lack of front-end development. This ## Types of Rewards By using the weights below, the community rewards will make each of the core functions of the Morpheus Network more broadly accessible and increase the Morpheus Code, Compute, and Capital resources. -End User Applications +### End User Applications Builders of End User Applications will receive 8% of all MOR emissions for generating demand for the Smart Agents. For example, a developer builds a website for the average person to use Smart Agents from the Morpheus Network. That user will also register their public key in the Morpheus protocol and get credit based on the amount of MOR fees paid by those users. -## Capital Front Ends -Builders of front ends for the Capital Providers will receive 8% of all MOR emissions. - -For example, a developer that creates an easy to use app or website that funnels Capital into the Morpheus Capital Provider smart contract would get a part of the 8% emissions pro-rata to the capital their public key tagged to the capital provision transaction. - -“Capital” is defined as the real-time Ethereum (ETH) value of a deposited asset. - -In determining the best method for allocation emissions for Capital Front Ends, Morpheus considered three alternatives. Each focuses on a pro-rata distribution methodology, but differ in the time horizon considered: -Daily - emissions are distributed based on daily capital deposits. The primary benefit of this methodology is that it continually encourages and rewards new depositors. However, there are multiple downsides. First, capital deposits won't be smooth - 10 stETH could be deposited on one day and 100 stETH the next. As such, the Community Capital Front End emissions would be greatly disproportionate to the capital contributed as a full day’s emissions would be provided for 10 stETH one day and 100 stETH the next. Second, this could result in a manipulation of the system. Since it would be limited to a one day time horizon, users could repeatedly deposit to earn the Community Capital Front End emissions, then withdraw funds and deposit a day or two later to earn more again. -Cumulative - emissions are distributed based on the cumulative capital deposits to date. This methodology distributes emissions based on the value of capital provided, regardless if that capital was contributed on a particular day, or months/years in the past, so long as it remains deposited. The downside to this approach is that it could discourage builders to develop new front ends. If a large amount of capital is already allocated, then incremental amounts will be relatively insignificant - meaning builders are less incentivized to continue building for an ever smaller piece of the pie. -1 Year Duration - capital deposits through a front-end are relevant for one year so long as they remain deposited. Emissions are distributed based on the pro rata share of the trailing one year deposits. The length of the timeline could be set to any number of days/years. The goal would be to find the appropriate balance which encourages new front end development to solicit capital while removing unnecessary transactions and potential exploitation. - -Multi-Asset Considerations: stETH on Ethereum is the only capital currently allowed to be contributed. Over time, more assets and more chains may be added. With additional assets deposited as capital, it raises several complexities that must be accounted for: -Price Feeds - All currencies must be denominated into a comparable asset in order to determine relevant value. This will occur by translating all currencies into the equivalent USDC value at the time of the transaction. [will need to define the Oracle price feeds to be utilized as well as the timing: price updates by block, average for the day, spot at end of day, etc] -Relative Movements across Assets - Currencies will move relative to each other after being deposited. For example, if token A is deposited when its price is $100 and Token B is deposited when its price is $200, then at the time of deposit, it is a 1:2 ratio. A user who deposited 1 Token A will be credited with half the value of a user who deposited 1 Token B. However, if a week later, Token A’s price has stayed at $100 while Token B’s price has increased to $300, the ratio is now at 1:3 for those same deposits. Prices will need to be updated on a regular basis to ensure that the user’s deposited value represents actual prices. -Asset Movements across Time - A similar situation arises when two users deposit the same asset at different times. If User 1 deposits a single Token B at $200 and User 2 deposits a single Token B a week later at $300. They both have deposited 1 Token B and contributed equally at any time moving forward - the MOR rewards generated will only be considered equal if the token prices are routinely updated and not focused on price at the time of entry. -Yields Differ across Deposited Assets - Different assets earn different yields. Those assets depend on the asset, protocol, and market conditions among other factors. The yield on the deposited asset is ultimately what is contributed to Morpheus. At first glance, the only thing Morpheus would care about would be the benefit it receives regarding yield. However, a wide variety of assets and chains strengthens the health of Morpheus. It helps to protect Morpheus via diversification. There are a variety of analyses out there, but generally speaking, a higher yield, by default, implies a higher risk. Therefore, assets that may have a lower yield attached to them should still be encouraged as the underlying assets might be viewed as ‘safer’ or have a better likelihood of appreciation in value. Therefore, a blended approach would balance the difference and reward across the capital deposited and yield generated. The below example shows, using random assets and numbers for presentational purposes only, the blended pro-rata approach where a 50% weight is applied to the TVL and a 50% weight is applied to the daily yield. - -## Deposited Asset Details -Deposited TVL -TVL (% of Total) -Daily Yield $ -Daily Yield (% of Total) -Community Capital MOR Emissions -Lido - stETH -$100,000,000 -74% -$9,315 -61% -67.5% -Lido - stMATIC -$5,000,000 -4% -$548 -4% -4% -Jito - JuitSOL -$20,000,000 -15% -$4,164 -27% -21% -GMX - GMX -$10,000,000 -7% -$1,208 -8% -7.5% -Total -$135,000,000 -100% -$15,235 -100% -100% - -## Compute Front Ends +### Capital Front Ends +Builders of front ends for the Capital Providers will receive 8% of all MOR emissions. + +For example, a developer that creates an easy to use app or website that funnels Capital into the Morpheus Capital Provider smart contract would get a part of the 8% emissions pro-rata to the capital their public key tagged to the capital provision transaction. + +“Capital” is defined as the real-time Ethereum (ETH) value of a deposited asset. + +In determining the best method for allocation emissions for Capital Front Ends, Morpheus considered three alternatives. Each focuses on a pro-rata distribution methodology, but differ in the time horizon considered: +- **Daily** - emissions are distributed based on daily capital deposits. The primary benefit of this methodology is that it continually encourages and rewards new depositors. However, there are multiple downsides. First, capital deposits won't be smooth - 10 stETH could be deposited on one day and 100 stETH the next. As such, the Community Capital Front End emissions would be greatly disproportionate to the capital contributed as a full day’s emissions would be provided for 10 stETH one day and 100 stETH the next. Second, this could result in a manipulation of the system. Since it would be limited to a one day time horizon, users could repeatedly deposit to earn the Community Capital Front End emissions, then withdraw funds and deposit a day or two later to earn more again. +- **Cumulative** - emissions are distributed based on the cumulative capital deposits to date. This methodology distributes emissions based on the value of capital provided, regardless if that capital was contributed on a particular day, or months/years in the past, so long as it remains deposited. The downside to this approach is that it could discourage builders to develop new front ends. If a large amount of capital is already allocated, then incremental amounts will be relatively insignificant - meaning builders are less incentivized to continue building for an ever smaller piece of the pie. +- **1 Year Duratio**n - capital deposits through a front-end are relevant for one year so long as they remain deposited. Emissions are distributed based on the pro rata share of the trailing one year deposits. The length of the timeline could be set to any number of days/years. The goal would be to find the appropriate balance which encourages new front end development to solicit capital while removing unnecessary transactions and potential exploitation. + +**Multi-Asset Considerations.** +stETH on Ethereum is the only capital currently allowed to be contributed. Over time, more assets and more chains may be added. With additional assets deposited as capital, it raises several complexities that must be accounted for: +- **Price Feeds** - All currencies must be denominated into a comparable asset in order to determine relevant value. This will occur by translating all currencies into the equivalent USDC value at the time of the transaction. [will need to define the Oracle price feeds to be utilized as well as the timing: price updates by block, average for the day, spot at end of day, etc] +- **Relative Movements across Assets** - Currencies will move relative to each other after being deposited. For example, if token A is deposited when its price is $100 and Token B is deposited when its price is $200, then at the time of deposit, it is a 1:2 ratio. A user who deposited 1 Token A will be credited with half the value of a user who deposited 1 Token B. However, if a week later, Token A’s price has stayed at $100 while Token B’s price has increased to $300, the ratio is now at 1:3 for those same deposits. Prices will need to be updated on a regular basis to ensure that the user’s deposited value represents actual prices. +- **Asset Movements across Time** - A similar situation arises when two users deposit the same asset at different times. If User 1 deposits a single Token B at $200 and User 2 deposits a single Token B a week later at $300. They both have deposited 1 Token B and contributed equally at any time moving forward - the MOR rewards generated will only be considered equal if the token prices are routinely updated and not focused on price at the time of entry. +- **Yields Differ across Deposited Assets** - Different assets earn different yields. Those assets depend on the asset, protocol, and market conditions among other factors. The yield on the deposited asset is ultimately what is contributed to Morpheus. At first glance, the only thing Morpheus would care about would be the benefit it receives regarding yield. However, a wide variety of assets and chains strengthens the health of Morpheus. It helps to protect Morpheus via diversification. There are a variety of analyses out there, but generally speaking, a higher yield, by default, implies a higher risk. Therefore, assets that may have a lower yield attached to them should still be encouraged as the underlying assets might be viewed as ‘safer’ or have a better likelihood of appreciation in value. Therefore, a blended approach would balance the difference and reward across the capital deposited and yield generated. + +The below example shows, using random assets and numbers for presentational purposes only, the blended pro-rata approach where a 50% weight is applied to the TVL and a 50% weight is applied to the daily yield. + +| Deposited Asset Details | Deposited TVL | TVL (% of Total) | Daily Yield $ | Daily Yield (% of Total)| Community Capital MOR Emissions | +|----------------------------------------|---------------|------------------|----------------|-------------------------|-------------------| +Lido - stETH | $100,000,000 | 74% | $9,315 | 61% | 67.5% | +Lido - stMATIC | $5,000,000 | 4% | $548 | 4% | 4% | +Jito - JuitSOL | $20,000,000 | 15% | $4,164 | 27% | 21% | +GMX - GMX | $10,000,000 | 7% | $1,208 | 8% | 7.5% | +Total | $135,000,000 | 100% | $15,235 | 100% | 100% | + +### Compute Front Ends Builders of front ends for the Compute Providers will receive 8% of all MOR emissions. For example, a developer builds a Software Development Kit, API or website that makes it easier to provide Compute to the Morpheus Network. In doing so, they qualify to receive a pro-rata amount based on the amount of Compute they helped to enroll. -Order of operations for bootstrapping the Morpheus Network. +## Order of operations for bootstrapping the Morpheus Network. The 24% of the MOR emissions for Community Builders will begin to accrue to the Community Builder Smart Contract when it reaches Ethereum mainnet (February 8th 2024). The Community Builder smart contracts should enter into operation after the other three smart contracts (Code, Capital & Compute) are already functional. -Step #1. + +**Step #1.** Code & Capital Rewards go live February 8th 2024 with their respective smart contracts. MOR rewards begin to be earned by participating addresses. MOR begins accruing in the Compute & Community Smart Contracts. -Step #2 +**Step #2.** Day 90 the bootstrapping period is complete, the AMM pool is launched. Day 91 the MOR are claimable/sendable. -Step #3. +**Step #3.** Compute Smart Contract and Router software goes live and Compute Provide begins earning MOR from the bidding system. -Step #4. +**Step #4.** Community Builder Smart Contact goes live and front-end builders begin earning MOR from the accrued emissions available. https://docs.google.com/spreadsheets/d/1qW20-C6VLw5eX3Wjrz-JeEbsvakFIojyZv9c9OIoU7E/edit?usp=sharing ## Protecting Against Exploits The key idea is to quantify on-chain activity as a means to avoid exploits and make the activity easier to prove. -Why is this important? +## Why is this important? Without a protocol-level reward, a community member would be required to form traditional entities and other means of coordinating efforts. This would cause friction within the construct of Morpheus’ use of the Techno Capital Machine; it's critical that the rewards be able to cover the full stack of developers involved. With this in place, every aspect of the Morpheus community is rewarded for their contribution of effort, not just capital or compute. From cfc9d18c3e5c7a5ace5cab397a57239e8b1c60fb Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Mon, 18 Mar 2024 17:33:12 +0200 Subject: [PATCH 102/129] Update MRC10.md --- MRC10.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/MRC10.md b/MRC10.md index 5b70cc9..24f34cf 100644 --- a/MRC10.md +++ b/MRC10.md @@ -1,9 +1,9 @@ # Development of Smart Agent Tools Marketplace -## Project Name: Smart Agent Tools Marketplace -Requesting Organization/Individual: Mor Labs +**Project Name:** Smart Agent Tools Marketplace +**Requesting Organization/Individual:** Mor Labs -Summary: This proposal outlines the development of a marketplace for tools that can be integrated with Smart Agents within the Morpheus ecosystem. This marketplace aims to significantly expand the capabilities of Smart Agents, allowing them to interact with both web3 smart contracts and centralized tools and apps. The marketplace will facilitate easy access to and implementation of tools for data handling, interaction with centralized platforms like Google Sheets, Discord, and GitHub, and more, enhancing the Smart Agents' functionality and versatility. +| This proposal outlines the development of a marketplace for tools that can be integrated with Smart Agents within the Morpheus ecosystem. This marketplace aims to significantly expand the capabilities of Smart Agents, allowing them to interact with both web3 smart contracts and centralized tools and apps. The marketplace will facilitate easy access to and implementation of tools for data handling, interaction with centralized platforms like Google Sheets, Discord, and GitHub, and more, enhancing the Smart Agents' functionality and versatility. ## Introduction The project seeks to pioneer the Smart Agent Tools Marketplace, a platform designed to augment the capabilities of Smart Agents through a diverse array of integrable tools. This initiative will bridge the gap between decentralized and traditional centralized environments, enabling Smart Agents to become more adaptable, intelligent, and efficient in executing a wide range of tasks. @@ -20,10 +20,10 @@ Foster Innovation and Customization: Provide a platform for developers to contri The Smart Agent Tools Marketplace will serve as a dedicated platform where developers and users can access, share, and implement tools designed to enhance the functionality of Smart Agents. This marketplace will leverage Langchain as well as the CrewAI codebase to provide a robust and flexible environment for tool integration, supporting a wide range of use cases from data manipulation to interaction with centralized services. ### Technology Stack -Frontend Development: React.js, CSS/Sass, Redux, OAuth 2.0, Jest, React Testing Library -Smart Contract Development (Web3): Ethereum, Solidity, ethers.js/web3.js, IPFS -Integration with Smart Agents: WebSocket, SDKs for major Smart Agent frameworks -Tool Implementation (Python Scripts): Python 3.x, virtual environments for dependency management +Frontend Development: React.js, CSS/Sass, Redux, OAuth 2.0, Jest, React Testing Library +Smart Contract Development (Web3): Ethereum, Solidity, ethers.js/web3.js, IPFS +Integration with Smart Agents: WebSocket, SDKs for major Smart Agent frameworks +Tool Implementation (Python Scripts): Python 3.x, virtual environments for dependency management ## Implementation Plan From 63e1f2117cdfdff11440cbf021cb731db97a2e9f Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Mon, 18 Mar 2024 17:34:40 +0200 Subject: [PATCH 103/129] Update MRC11.md --- MRC11.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/MRC11.md b/MRC11.md index bce97c1..015be14 100644 --- a/MRC11.md +++ b/MRC11.md @@ -1,8 +1,8 @@ # Morpheus Multi-Agent Framework (MMAF) -Project Name: Morpheus Multi-Agent Framework (MMAF) -Requesting Organization/Individual: Mor Labs +**Project Name:** Morpheus Multi-Agent Framework (MMAF) +**Requesting Organization/Individual:** Mor Labs -Summary: The MMAF project aims to evolve the Morpheus ecosystem from a single-agent system to a sophisticated multi-agent framework. By leveraging the CrewAI codebase, this initiative will enable the development and coordination of multiple smart agents, facilitating diverse functionalities and inter-agent communication. This expansion is poised to significantly enhance the adoption, versatility, and operational efficiency of Morpheus Smart Agents, fostering a new level of dynamic interaction within the decentralized space. +**Summary:** The MMAF project aims to evolve the Morpheus ecosystem from a single-agent system to a sophisticated multi-agent framework. By leveraging the CrewAI codebase, this initiative will enable the development and coordination of multiple smart agents, facilitating diverse functionalities and inter-agent communication. This expansion is poised to significantly enhance the adoption, versatility, and operational efficiency of Morpheus Smart Agents, fostering a new level of dynamic interaction within the decentralized space. ## Introduction Mor Labs, in collaboration with the CrewAI community, proposes to spearhead the development of a multi-agent framework for Morpheus. Our team combines Mor Labs' deep expertise in decentralized technologies with CrewAI's pioneering work in AI and multi-agent systems. The collaboration is uniquely positioned to execute this ambitious project, given our proven track record in blockchain development, AI, and community-driven innovation. @@ -21,13 +21,13 @@ Demonstrate Multi-Agent Use Cases: Implement and showcase practical use cases of Our solution involves developing a comprehensive multi-agent framework that allows for the creation, management, and interaction of multiple smart agents within the Morpheus ecosystem. This framework will leverage the existing CrewAI codebase, enhancing it with blockchain-specific functionalities to support decentralized operations. Agents will be able to communicate, collaborate, and negotiate with each other, enabling complex decentralized processes and applications. ### Technology Stack -Base Codebase: CrewAI for agent algorithms and behaviors. -Blockchain Integration: Solidity for smart contract development, with Morpheus and Ethereum blockchains as primary platforms. -Communication Protocols: Development of decentralized communication protocols for agent interaction. -Security: Implementation of security best practices and protocols to ensure the integrity and privacy of multi-agent interactions. +Base Codebase: CrewAI for agent algorithms and behaviors. +Blockchain Integration: Solidity for smart contract development, with Morpheus and Ethereum blockchains as primary platforms. +Communication Protocols: Development of decentralized communication protocols for agent interaction. +Security: Implementation of security best practices and protocols to ensure the integrity and privacy of multi-agent interactions. -### Implementation Plan -Preparation and Community Engagement +## Implementation Plan +### Preparation and Community Engagement Finalize the proposal with community feedback. Gather initial feedback from the Morpheus and CrewAI communities to refine the project's direction. Conduct a detailed requirement analysis for the multi-agent framework. Identify specific functionalities, interoperability requirements, and security protocols needed. From 6a4dadb2eb8b967780fea3aae4b4ea9fafcc54f8 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Mon, 18 Mar 2024 17:35:16 +0200 Subject: [PATCH 104/129] Update MRC10.md --- MRC10.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MRC10.md b/MRC10.md index 24f34cf..155a390 100644 --- a/MRC10.md +++ b/MRC10.md @@ -1,9 +1,9 @@ # Development of Smart Agent Tools Marketplace -**Project Name:** Smart Agent Tools Marketplace +**Project Name:** Smart Agent Tools Marketplace **Requesting Organization/Individual:** Mor Labs -| This proposal outlines the development of a marketplace for tools that can be integrated with Smart Agents within the Morpheus ecosystem. This marketplace aims to significantly expand the capabilities of Smart Agents, allowing them to interact with both web3 smart contracts and centralized tools and apps. The marketplace will facilitate easy access to and implementation of tools for data handling, interaction with centralized platforms like Google Sheets, Discord, and GitHub, and more, enhancing the Smart Agents' functionality and versatility. +**Summary:** This proposal outlines the development of a marketplace for tools that can be integrated with Smart Agents within the Morpheus ecosystem. This marketplace aims to significantly expand the capabilities of Smart Agents, allowing them to interact with both web3 smart contracts and centralized tools and apps. The marketplace will facilitate easy access to and implementation of tools for data handling, interaction with centralized platforms like Google Sheets, Discord, and GitHub, and more, enhancing the Smart Agents' functionality and versatility. ## Introduction The project seeks to pioneer the Smart Agent Tools Marketplace, a platform designed to augment the capabilities of Smart Agents through a diverse array of integrable tools. This initiative will bridge the gap between decentralized and traditional centralized environments, enabling Smart Agents to become more adaptable, intelligent, and efficient in executing a wide range of tasks. From cf892226b8c447e8c7233b394a7a4e657b8488cb Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Mon, 18 Mar 2024 17:55:08 +0200 Subject: [PATCH 105/129] Update MRC10.md --- MRC10.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/MRC10.md b/MRC10.md index 155a390..df0640b 100644 --- a/MRC10.md +++ b/MRC10.md @@ -1,9 +1,10 @@ # Development of Smart Agent Tools Marketplace +## Executive Summary **Project Name:** Smart Agent Tools Marketplace **Requesting Organization/Individual:** Mor Labs -**Summary:** This proposal outlines the development of a marketplace for tools that can be integrated with Smart Agents within the Morpheus ecosystem. This marketplace aims to significantly expand the capabilities of Smart Agents, allowing them to interact with both web3 smart contracts and centralized tools and apps. The marketplace will facilitate easy access to and implementation of tools for data handling, interaction with centralized platforms like Google Sheets, Discord, and GitHub, and more, enhancing the Smart Agents' functionality and versatility. +This proposal outlines the development of a marketplace for tools that can be integrated with Smart Agents within the Morpheus ecosystem. This marketplace aims to significantly expand the capabilities of Smart Agents, allowing them to interact with both web3 smart contracts and centralized tools and apps. The marketplace will facilitate easy access to and implementation of tools for data handling, interaction with centralized platforms like Google Sheets, Discord, and GitHub, and more, enhancing the Smart Agents' functionality and versatility. ## Introduction The project seeks to pioneer the Smart Agent Tools Marketplace, a platform designed to augment the capabilities of Smart Agents through a diverse array of integrable tools. This initiative will bridge the gap between decentralized and traditional centralized environments, enabling Smart Agents to become more adaptable, intelligent, and efficient in executing a wide range of tasks. From 1c1f9b14e836d4316889c58d095a5defaf355494 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Mon, 18 Mar 2024 17:55:25 +0200 Subject: [PATCH 106/129] Update MRC11.md --- MRC11.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/MRC11.md b/MRC11.md index 015be14..b23d704 100644 --- a/MRC11.md +++ b/MRC11.md @@ -1,8 +1,10 @@ # Morpheus Multi-Agent Framework (MMAF) +## Executive Summary + **Project Name:** Morpheus Multi-Agent Framework (MMAF) **Requesting Organization/Individual:** Mor Labs -**Summary:** The MMAF project aims to evolve the Morpheus ecosystem from a single-agent system to a sophisticated multi-agent framework. By leveraging the CrewAI codebase, this initiative will enable the development and coordination of multiple smart agents, facilitating diverse functionalities and inter-agent communication. This expansion is poised to significantly enhance the adoption, versatility, and operational efficiency of Morpheus Smart Agents, fostering a new level of dynamic interaction within the decentralized space. +The MMAF project aims to evolve the Morpheus ecosystem from a single-agent system to a sophisticated multi-agent framework. By leveraging the CrewAI codebase, this initiative will enable the development and coordination of multiple smart agents, facilitating diverse functionalities and inter-agent communication. This expansion is poised to significantly enhance the adoption, versatility, and operational efficiency of Morpheus Smart Agents, fostering a new level of dynamic interaction within the decentralized space. ## Introduction Mor Labs, in collaboration with the CrewAI community, proposes to spearhead the development of a multi-agent framework for Morpheus. Our team combines Mor Labs' deep expertise in decentralized technologies with CrewAI's pioneering work in AI and multi-agent systems. The collaboration is uniquely positioned to execute this ambitious project, given our proven track record in blockchain development, AI, and community-driven innovation. From 320cf8d9201f44295b5748a786409d917e3b6228 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Mon, 18 Mar 2024 18:05:28 +0200 Subject: [PATCH 107/129] Update MRC12.md --- MRC12.md | 55 +++++++++++++++++++------------------------------------ 1 file changed, 19 insertions(+), 36 deletions(-) diff --git a/MRC12.md b/MRC12.md index ac23d1b..c27a017 100644 --- a/MRC12.md +++ b/MRC12.md @@ -1,10 +1,10 @@ # Capital contracts expansion to stMATIC ## Executive Summary -Project Name: Capital contracts expansion to stMATIC -Requesting Organization/Individual: Mor Labs +**Project Name:** Capital contracts expansion to stMATIC +**Requesting Organization/Individual:** Mor Labs -Summary: This project aims to extend the Morpheus ecosystem to include support for Polygon, specifically for stMATIC holders, leveraging the success of Morpheus Capital Contracts with stETH. Our objective is to enhance capital contribution options within the Morpheus ecosystem, integrating high-yield opportunities from stMATIC and leveraging the chain-agnostic nature of Morpheus to foster a more inclusive and versatile DeFi landscape. +This project aims to extend the Morpheus ecosystem to include support for Polygon, specifically for stMATIC holders, leveraging the success of Morpheus Capital Contracts with stETH. Our objective is to enhance capital contribution options within the Morpheus ecosystem, integrating high-yield opportunities from stMATIC and leveraging the chain-agnostic nature of Morpheus to foster a more inclusive and versatile DeFi landscape. ## Introduction Mor Labs is a new guild that has formed from within the Morpheus ecosystem. Our team comprises blockchain developers, DeFi strategists, and security experts. @@ -34,19 +34,17 @@ Polygon has successfully deployed features of Polygon 2.0, including the zkEVM, Given Mor Labs expertise in smart contract development and cross-chain integrations, we are uniquely positioned to undertake the expansion of the Morpheus ecosystem to support Polygon and stMATIC. -Applying the above framework for stMATIC on the Morpheus ecosystem, we can outline the required details based on the broader framework for new asset integration as follows: -Staked Asset Identification: stMATIC represents staked MATIC tokens within the Lido on Polygon system, providing users with a liquid token that can be used across DeFi applications on both Ethereum and Polygon networks. It's designed to allow users to stake MATIC tokens without locking assets or maintaining staking infrastructure, enabling participation in on-chain decentralized finance with their staked assets. - - -## Underlying Asset Analysis: The underlying asset, MATIC (soon to be replaced on a 1:1 basis with POL), is the native token of the Polygon network, known for its scalability and efficiency in processing transactions on the Ethereum blockchain. The market cap and TVL of MATIC would provide insights into its stability and potential for yield. As of the latest data, the staked amount in the Lido on Polygon system is substantial, indicating a healthy participation level and confidence in the staking mechanism -- Network Evaluation: Polygon (previously Matic Network) is a protocol and a framework for building and connecting Ethereum-compatible blockchain networks. It enhances Ethereum's scalability and interoperability, making it an attractive network for a variety of decentralized applications, including those in decentralized finance and AI. -- Yield Mechanism Description: Staking with Lido on Polygon allows users to earn MATIC staking rewards while maintaining full control and transferability of their assets. The staked MATIC tokens are delegated across Polygon validators part of the Lido on Polygon, with stMATIC representing the staked MATIC. Liquid staking protocols like Lido on Polygon facilitate earning staking rewards without locking assets or maintaining staking infrastructure -- Lockup Period Considerations: The waiting period for withdrawing staked assets is approximately 3-4 days, ensuring liquidity while participating in staking rewards programs -- Contract Audits and Auditors: Details about audits for the staking mechanisms are available on the Lido and associated GitHub repositories -- Market Cap and TVL Analysis: The total value locked (TVL) in stMATIC and the underlying asset's market cap provide insights into the asset's stability and potential for yield. As of the latest available data, the staked amount and the rewards paid indicate active participation and a significant amount of assets under management. At the time of writing (15th March 2024), 134,021,866 MATIC has been staked and 13,299,493 MATIC have been paid out as rewards (source) -- Liquidity Evaluation: stMATIC can be traded on centralized and decentralized exchanges, and it can be used in liquidity pools on both Ethereum and Polygon networks, indicating a healthy liquidity profile for the asset. The Uniswap V3 pool for stMATIC can be seen here. -- APY Calculation: The Annual Percentage Yield (APY) for staking MATIC through Lido on Polygon is approximately 4.3%, calculated based on historical on-chain data and the average return over the past 30 days. -- Network Oracle Integration: The integration with network oracles for real-time data provision was not explicitly mentioned in the sources, but the accurate calculation of APY and the use of decentralized finance applications suggest the use of reliable data sources for asset valuation and yield calculation +Applying the above framework for stMATIC on the Morpheus ecosystem, we can outline the required details based on the broader framework for new asset integration as follows: +- **Staked Asset Identification:** stMATIC represents staked MATIC tokens within the Lido on Polygon system, providing users with a liquid token that can be used across DeFi applications on both Ethereum and Polygon networks. It's designed to allow users to stake MATIC tokens without locking assets or maintaining staking infrastructure, enabling participation in on-chain decentralized finance with their staked assets. +- **Underlying Asset Analysis:** The underlying asset, MATIC (soon to be replaced on a 1:1 basis with POL), is the native token of the Polygon network, known for its scalability and efficiency in processing transactions on the Ethereum blockchain. The market cap and TVL of MATIC would provide insights into its stability and potential for yield. As of the latest data, the staked amount in the Lido on Polygon system is substantial, indicating a healthy participation level and confidence in the staking mechanism +- **Network Evaluation:** Polygon (previously Matic Network) is a protocol and a framework for building and connecting Ethereum-compatible blockchain networks. It enhances Ethereum's scalability and interoperability, making it an attractive network for a variety of decentralized applications, including those in decentralized finance and AI. +- **Yield Mechanism Description:** Staking with Lido on Polygon allows users to earn MATIC staking rewards while maintaining full control and transferability of their assets. The staked MATIC tokens are delegated across Polygon validators part of the Lido on Polygon, with stMATIC representing the staked MATIC. Liquid staking protocols like Lido on Polygon facilitate earning staking rewards without locking assets or maintaining staking infrastructure +- **Lockup Period Considerations:** The waiting period for withdrawing staked assets is approximately 3-4 days, ensuring liquidity while participating in staking rewards programs +- **Contract Audits and Auditors:** Details about audits for the staking mechanisms are available on the Lido and associated GitHub repositories +- **Market Cap and TVL Analysis:** The total value locked (TVL) in stMATIC and the underlying asset's market cap provide insights into the asset's stability and potential for yield. As of the latest available data, the staked amount and the rewards paid indicate active participation and a significant amount of assets under management. At the time of writing (15th March 2024), 134,021,866 MATIC has been staked and 13,299,493 MATIC have been paid out as rewards (source) +- **Liquidity Evaluation:** stMATIC can be traded on centralized and decentralized exchanges, and it can be used in liquidity pools on both Ethereum and Polygon networks, indicating a healthy liquidity profile for the asset. The Uniswap V3 pool for stMATIC can be seen here. +- **APY Calculation:** The Annual Percentage Yield (APY) for staking MATIC through Lido on Polygon is approximately 4.3%, calculated based on historical on-chain data and the average return over the past 30 days. +- **Network Oracle Integration:** The integration with network oracles for real-time data provision was not explicitly mentioned in the sources, but the accurate calculation of APY and the use of decentralized finance applications suggest the use of reliable data sources for asset valuation and yield calculation This framework ensures a systematic and transparent approach to evaluating and integrating new staked assets into the Morpheus ecosystem, with stMATIC serving as a prime example of how assets are assessed based on various critical parameters. @@ -82,26 +80,11 @@ Despite MOR being accessible on multiple chains through bridging, all MOR tokens The calculation of MOR emissions for capital contributors, when involving more than one asset, will adopt the Pro Rata (Yield) method. This approach considers the yield generated by each asset, ensuring emissions are aligned with the financial benefit provided to the Morpheus ecosystem. For instance, if stMATIC yields 4.3% on $100M, and stETH yields 3.6% on $400M, MOR emissions will be distributed 23% to stMATIC depositors and 77% to stETH depositors. This method is deemed the fairest, aligning emissions with the actual financial contribution of each asset to the ecosystem. -Deposited Asset -Deposited TVL -Yield % -Annual Yield -% of Yield = MOR Emissions -stETH -$400,000,000 -3.6% -$14,400,000 -77% -stMATIC -$100,000,000 -4.3% -$4,300,000 -23% -Total -$500,000,000 -n/a -$18,700,000 -100% +| Deposited Asset Details | Deposited TVL | Yield % | Annual Yield % of Yield = MOR Emissions | +|----------------------------------------|---------------|------------------|----------------| +stETH | $400,000,000 | 3.6% | $14,400,000 | 77% | +stMATIC | $100,000,000 | 4.3% | $4,300,000 | 23% | +Total | $500,000,000 | n/a | $18,700,000 | 100% | ## Impact on Community Emissions From 0ae7e49e006924088b910028691281758f99645f Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Mon, 18 Mar 2024 18:12:56 +0200 Subject: [PATCH 108/129] Update MRC16.md --- MRC16.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MRC16.md b/MRC16.md index ae89475..3a64857 100644 --- a/MRC16.md +++ b/MRC16.md @@ -14,11 +14,11 @@ In particular, they liked: - 2) the gas abstraction for better UX. - 3) The oracle function that can help denominate all yield contributions to Morpheus via ETH price. -Whilte Morpheus is not exclusive to any chain or project, Layer Zero seems to be a good startig point to increase the Interoperability of the MOR token and broaden types of yield contribution. +While Morpheus is not exclusive to any chain or project, Layer Zero seems to be a good starting point to increase the Interoperability of the MOR token and broaden types of yield contribution. ## Implementation To start sending tokens from arbitrum to other chains, developers need to do is: -- 1. Deploy the OFT Adapter contract which works like a lockbox on the source chain, +- 1. Deploy the OFT Adapter contract which works like a lockbox on the source chain. - 2. Deploy the OFT contract on each new chain which will become the canonical MOR tokens for those new chains. ## Technical Documentation Details From 53e07c7da6bd43195327f639d2a0069159201065 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Mon, 18 Mar 2024 18:25:02 +0200 Subject: [PATCH 109/129] Update MRC17.md --- MRC17.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/MRC17.md b/MRC17.md index 7503dc2..0ff6e1e 100644 --- a/MRC17.md +++ b/MRC17.md @@ -3,19 +3,19 @@ ## Introduction We propose capital contribution integration for Morpheus with the Solana blockchain, aimed at significantly enhancing the liquidity of Morpheus AI's capital providers pool. By leveraging Solana's high-performance capabilities and developing a bespoke smart contract, we aim to introduce SOL staking and contributing staked SOL yield in exchange for MOR tokens. Furthermore, Solana's low transaction fees and high throughput offer a compelling case for it to be a suitable platform for Morpheus, potentially providing an efficient and cost-effective environment for users and the ecosystem at large. -## Implementation: -Solana Integration +## Implementation We propose to develop a smart contract on the Solana blockchain that allows users to directly stake SOL in exchange for MOR token rewards. This integration will enable Morpheus AI to access Solana's liquidity and user base, providing a new avenue for growth and capital. -## Smart Contract Development: +## Smart Contract Development 1) Direct SOL Staking: Users can stake SOL directly via the developed smart contract, with a guaranteed 1:1 return upon redemption. 2) Conversion to JitoSOL: The contract will automatically convert staked SOL into JitoSOL, enabling the protocol to earn staking rewards from the Jito Network. 3) Reward Mechanism: Accrued SOL rewards will be sold daily and added to the Protocol-owned Liquidity (POL) on Morpheus 4) Locking Mechanism for withdrawal: There will be a standard 7-day lock-in for the SOL contributed -Oracle Use + +## Oracle Use For the allocation of MOR rewards, an oracle will capture daily Solana market data at a specific time (e.g., 5 PM UTC), ensuring fair and transparent distribution. This process will meticulously be recorded on the Ethereum blockchain by Morpheus contracts, reinforcing the integrity and auditability of the reward mechanism within the ecosystem. This approach underscores the commitment to fairness, leveraging blockchain's transparency to benefit all ecosystem participants. -## Reward Allocation Strategy: +## Reward Allocation Strategy In order to have fair and equitable reward distribution to SOL stakers, we plan to utilize the oracle price data to calculate the USD value of SOL and yield contribution. The rewards for SOL stakers will be calculated on a pro-rata basis taking the st-ETH and other capital contribution into account. ## Bridging and Distribution From b48fc3d9b4bccecf4837fd0ab7ff6c89d2c1ad87 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Mon, 18 Mar 2024 18:26:48 +0200 Subject: [PATCH 110/129] Rename MRC18: Governance Agent.md to MRC18.md --- MRC18: Governance Agent.md => MRC18.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename MRC18: Governance Agent.md => MRC18.md (100%) diff --git a/MRC18: Governance Agent.md b/MRC18.md similarity index 100% rename from MRC18: Governance Agent.md rename to MRC18.md From 1728d08b41afed7f27c172e1d9d5cd864901d311 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Mon, 18 Mar 2024 18:31:32 +0200 Subject: [PATCH 111/129] Update Morpheus Request For Comments (MRC).md --- Morpheus Request For Comments (MRC).md | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index ea7aa2a..1898b6b 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -69,13 +69,17 @@ https://eips.ethereum.org/erc Provides a common language to describe interaction - Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. - Link: https://github.com/generativeone/Docs/blob/main/Expanding%20Horizon%20-%20The%20Morpheus%20Asset%20Integration%20Framework.md -## MRC 16: +## MRC 16: Toward MOR Interoperability +- Status: **Under Discussion** -## MRC 17: +## MRC 17: Adding Solana Yield & MOR Token Proposal +- Status: **Under Discussion** -## MRC 18: +## MRC 18: Autonomous Governance AI Agent for ATX DAO +- Status: **Under Discussion** -## MRC 19: +## MRC 19: Cosmos & Thorchain Expansion of Morpheus +- Status: **Under Discussion** ## MRC 20: "Automated Recurring Revenue / Rewards" (ARR) - The MOR 20 Token Standard - Status: **Under Discussion** @@ -88,3 +92,6 @@ The Morpheus platform charges only 0.35% (35 basis points) of the stETH yield co 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. - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md#automated-recurring-revenue--rewards-arr-generalizing-the-tcm-model---mor20-token-standard + +## MRC 21: Non Fungible Agents +- Status: **Under Discussion** From a57c70332d01e2afca7e7fe686abdd88a16a111b Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Mon, 18 Mar 2024 18:37:09 +0200 Subject: [PATCH 112/129] Update Morpheus Request For Comments (MRC).md --- Morpheus Request For Comments (MRC).md | 55 +++++++++++++------------- 1 file changed, 28 insertions(+), 27 deletions(-) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index 1898b6b..7f845d9 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -1,7 +1,11 @@ # Morpheus Request for Comments (MRC) -List of proposals extending Decentralized AI. -Similar to the function of the ERC system serves in Ethereum. -https://eips.ethereum.org/erc Provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. +Proposals to improve any of the Morpheus Reference Implementations (MRIs). + +See the details on all the of the MRIs here: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Reference%20Implementations.md + +Similar to the function of the [ERC system](https://eips.ethereum.org/erc ) serves in Ethereum, the MRC process provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. + +There is a dedicated forum on Discord for the discussion of MRCs here: https://discord.com/channels/1151741790408429580/1218593251079094383 ## List of MRCs: @@ -39,7 +43,7 @@ https://eips.ethereum.org/erc Provides a common language to describe interaction ## MRC 08: Waterloo Community Model. - Status: **Under Discussion**, needs additional work to flush out the concepts. -- Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC08.md ## MRC 09: AMM Launch Process - Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. @@ -47,51 +51,48 @@ https://eips.ethereum.org/erc Provides a common language to describe interaction ## MRC 10: Development of Smart Agent Tools Marketplace. - Status: **Under Discussion**, needs further discussion and approval. -- Link: https://docs.google.com/document/d/1JJQR4-b63VbJQ_etSt5Poyk1KcK3f7FvUZcwKB5Zpk8/edit?usp=sharing +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC10.md ## MRC 11: Morpheus Multi-Agent Framework. - Status: **Under Discussion**, needs further discussion to cover edge cases. -- Link: https://docs.google.com/document/d/1i6FBD7OIMEHSYMgKUGmrjpxgnlFN20JRC4_yW9bAVWw/edit?usp=sharing +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC11.md ## MRC 12: Capital contracts expansion to stMATIC. - Status: **Under Discussion**, needs further discussion to cover all edge cases and flesh out more concepts. -- Link: https://docs.google.com/document/d/1lZ_vJ3exkrn8DscHI6C59unp5Lui895rtN4nc-e2wso/edit?usp=sharing +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC12.md ## MRC 13: Launch TCM for MOR Yield Farming on Solana with JitoSOL and/or mSOL. - Status: **Under Discussion**, needs further discussion to answer open questions (see end of doc) and approval. -- Link: https://0xmacro.notion.site/MRC-13-Launch-TCM-for-MOR-Yield-Farming-on-Solana-with-JitoSOL-and-or-mSOL-a0f9e2c0fa884aa590fe993c38bc627b +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC13.md -## MRC 14: MOR MOR Weights for Greater Granularity. -- Status: **In Progress**, Planned implementation for April 8th 2024 weights snapshot. -- Link: https://docs.google.com/document/d/1_5WZSNZ8LDwrD-mWNR3HzZT4asYSHYeqHsybXvz302g/ +## MRC 14: MOR Weights for Greater Granularity. +- Status: **Adopted**, Planned implementation for April 8th 2024 weights snapshot. +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC14.md ## MRC 15: A Framework for Adding Yield-Generating Assets. - Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. -- Link: https://github.com/generativeone/Docs/blob/main/Expanding%20Horizon%20-%20The%20Morpheus%20Asset%20Integration%20Framework.md +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC15.md ## MRC 16: Toward MOR Interoperability -- Status: **Under Discussion** +- Status: **In Progress** Actively being implemented by some of the open source Smart Contract developers. +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC16.md ## MRC 17: Adding Solana Yield & MOR Token Proposal -- Status: **Under Discussion** +- Status: **Under Discussion** similar proposal is listed in MRC 13 also under discussion. +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC17.md -## MRC 18: Autonomous Governance AI Agent for ATX DAO +## MRC 18: Governance Agent - Status: **Under Discussion** +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC18:%20Governance%20Agent.md ## MRC 19: Cosmos & Thorchain Expansion of Morpheus - Status: **Under Discussion** +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC19.md -## MRC 20: "Automated Recurring Revenue / Rewards" (ARR) - The MOR 20 Token Standard -- Status: **Under Discussion** -- 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 reacurring 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. -- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md#automated-recurring-revenue--rewards-arr-generalizing-the-tcm-model---mor20-token-standard +## MRC 20: The MOR 20 Token Standard - "Automated Recurring Revenue / Rewards" (ARR) +- Status: **Implemented** +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC20.md ## MRC 21: Non Fungible Agents -- Status: **Under Discussion** +- Status: **In Discussion** +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC21.md From fc4339e3f29c19755a24352ee3405c397bfb68b0 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Mon, 18 Mar 2024 18:38:31 +0200 Subject: [PATCH 113/129] Update Morpheus Request For Comments (MRC).md --- Morpheus Request For Comments (MRC).md | 62 +++++++++++--------------- 1 file changed, 27 insertions(+), 35 deletions(-) diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md index 7f845d9..ea7aa2a 100644 --- a/Morpheus Request For Comments (MRC).md +++ b/Morpheus Request For Comments (MRC).md @@ -1,11 +1,7 @@ # Morpheus Request for Comments (MRC) -Proposals to improve any of the Morpheus Reference Implementations (MRIs). - -See the details on all the of the MRIs here: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Reference%20Implementations.md - -Similar to the function of the [ERC system](https://eips.ethereum.org/erc ) serves in Ethereum, the MRC process provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. - -There is a dedicated forum on Discord for the discussion of MRCs here: https://discord.com/channels/1151741790408429580/1218593251079094383 +List of proposals extending Decentralized AI. +Similar to the function of the ERC system serves in Ethereum. +https://eips.ethereum.org/erc Provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. ## List of MRCs: @@ -43,7 +39,7 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d ## MRC 08: Waterloo Community Model. - Status: **Under Discussion**, needs additional work to flush out the concepts. -- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC08.md +- Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing ## MRC 09: AMM Launch Process - Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. @@ -51,48 +47,44 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d ## MRC 10: Development of Smart Agent Tools Marketplace. - Status: **Under Discussion**, needs further discussion and approval. -- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC10.md +- Link: https://docs.google.com/document/d/1JJQR4-b63VbJQ_etSt5Poyk1KcK3f7FvUZcwKB5Zpk8/edit?usp=sharing ## MRC 11: Morpheus Multi-Agent Framework. - Status: **Under Discussion**, needs further discussion to cover edge cases. -- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC11.md +- Link: https://docs.google.com/document/d/1i6FBD7OIMEHSYMgKUGmrjpxgnlFN20JRC4_yW9bAVWw/edit?usp=sharing ## MRC 12: Capital contracts expansion to stMATIC. - Status: **Under Discussion**, needs further discussion to cover all edge cases and flesh out more concepts. -- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC12.md +- Link: https://docs.google.com/document/d/1lZ_vJ3exkrn8DscHI6C59unp5Lui895rtN4nc-e2wso/edit?usp=sharing ## MRC 13: Launch TCM for MOR Yield Farming on Solana with JitoSOL and/or mSOL. - Status: **Under Discussion**, needs further discussion to answer open questions (see end of doc) and approval. -- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC13.md +- Link: https://0xmacro.notion.site/MRC-13-Launch-TCM-for-MOR-Yield-Farming-on-Solana-with-JitoSOL-and-or-mSOL-a0f9e2c0fa884aa590fe993c38bc627b -## MRC 14: MOR Weights for Greater Granularity. -- Status: **Adopted**, Planned implementation for April 8th 2024 weights snapshot. -- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC14.md +## MRC 14: MOR MOR Weights for Greater Granularity. +- Status: **In Progress**, Planned implementation for April 8th 2024 weights snapshot. +- Link: https://docs.google.com/document/d/1_5WZSNZ8LDwrD-mWNR3HzZT4asYSHYeqHsybXvz302g/ ## MRC 15: A Framework for Adding Yield-Generating Assets. - Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. -- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC15.md - -## MRC 16: Toward MOR Interoperability -- Status: **In Progress** Actively being implemented by some of the open source Smart Contract developers. -- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC16.md +- Link: https://github.com/generativeone/Docs/blob/main/Expanding%20Horizon%20-%20The%20Morpheus%20Asset%20Integration%20Framework.md -## MRC 17: Adding Solana Yield & MOR Token Proposal -- Status: **Under Discussion** similar proposal is listed in MRC 13 also under discussion. -- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC17.md +## MRC 16: -## MRC 18: Governance Agent -- Status: **Under Discussion** -- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC18:%20Governance%20Agent.md +## MRC 17: -## MRC 19: Cosmos & Thorchain Expansion of Morpheus -- Status: **Under Discussion** -- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC19.md +## MRC 18: -## MRC 20: The MOR 20 Token Standard - "Automated Recurring Revenue / Rewards" (ARR) -- Status: **Implemented** -- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC20.md +## MRC 19: -## MRC 21: Non Fungible Agents -- Status: **In Discussion** -- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC21.md +## MRC 20: "Automated Recurring Revenue / Rewards" (ARR) - The MOR 20 Token Standard +- Status: **Under Discussion** +- 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 reacurring 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. +- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md#automated-recurring-revenue--rewards-arr-generalizing-the-tcm-model---mor20-token-standard From b746bbeb5b6713369ad4657123ac1f8d792235c5 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Mon, 18 Mar 2024 19:51:10 +0200 Subject: [PATCH 114/129] Update README.md --- README.md | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index f5c5fa3..6ff95aa 100644 --- a/README.md +++ b/README.md @@ -42,27 +42,27 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d - Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Fair%20Launch.md ## MRC 08: Waterloo Community Model. -- Status: **Under Discussion**, needs additional work to flush out the concepts. +- Status: [**Under Discussion**](https://discord.com/channels/1151741790408429580/1219004083072008323), needs additional work to flush out the concepts. - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC08.md ## MRC 09: AMM Launch Process -- Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. +- Status: [**Under Discussion**](https://discord.com/channels/1151741790408429580/1218958132814942259), needs further discussion to cover edge cases and to receive community feedback. - Link: https://github.com/generativeone/Docs/blob/main/Building%20the%20Foundation%20-%20AMM%20Launch.md ## MRC 10: Development of Smart Agent Tools Marketplace. -- Status: **Under Discussion**, needs further discussion and approval. +- Status: [**Under Discussion**](https://discord.com/channels/1151741790408429580/1218906013072363551), needs further discussion and approval. - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC10.md ## MRC 11: Morpheus Multi-Agent Framework. -- Status: **Under Discussion**, needs further discussion to cover edge cases. +- Status: [**Under Discussion**](https://discord.com/channels/1151741790408429580/1218907422438068315), needs further discussion to cover edge cases. - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC11.md ## MRC 12: Capital contracts expansion to stMATIC. -- Status: **Under Discussion**, needs further discussion to cover all edge cases and flesh out more concepts. +- Status: [**Under Discussion**](https://discord.com/channels/1151741790408429580/1218910318676410388), needs further discussion to cover all edge cases and flesh out more concepts. - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC12.md ## MRC 13: Launch TCM for MOR Yield Farming on Solana with JitoSOL and/or mSOL. -- Status: **Under Discussion**, needs further discussion to answer open questions (see end of doc) and approval. +- Status: [**Under Discussion**](https://discord.com/channels/1151741790408429580/1218991804876198028), needs further discussion to answer open questions (see end of doc) and approval. - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC13.md ## MRC 14: MOR Weights for Greater Granularity. @@ -70,29 +70,29 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC14.md ## MRC 15: A Framework for Adding Yield-Generating Assets. -- Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. +- Status: [**Under Discussion**](https://discord.com/channels/1151741790408429580/1219001846077587577), needs further discussion to cover edge cases and to receive community feedback. - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC15.md ## MRC 16: Toward MOR Interoperability -- Status: **In Progress** Actively being implemented by some of the open source Smart Contract developers. +- Status: [**In Progress**](https://discord.com/channels/1151741790408429580/1219043269061644359) Actively being implemented by some of the open source Smart Contract developers. - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC16.md ## MRC 17: Adding Solana Yield & MOR Token Proposal -- Status: **Under Discussion** similar proposal is listed in MRC 13 also under discussion. +- Status: [**Under Discussion**](https://discord.com/channels/1151741790408429580/1219340187671199854) similar proposal is listed in MRC 13 also under discussion. - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC17.md ## MRC 18: Governance Agent -- Status: **Under Discussion** +- Status: [**Under Discussion**](https://discord.com/channels/1151741790408429580/1219341590334541894) - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC18:%20Governance%20Agent.md ## MRC 19: Cosmos & Thorchain Expansion of Morpheus -- Status: **Under Discussion** +- Status: [**Under Discussion**](https://discord.com/channels/1151741790408429580/1219341892781871177) - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC19.md ## MRC 20: The MOR 20 Token Standard - "Automated Recurring Revenue / Rewards" (ARR) -- Status: **Implementated** +- Status: **Implemented** - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC20.md ## MRC 21: Non Fungible Agents -- Status: **In Discussion** +- Status: [**In Discussion**](https://discord.com/channels/1151741790408429580/1219342219115233381)https://discord.com/channels/1151741790408429580/1219342219115233381 - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC21.md From b2651f2cb1f1e46aef53710f80ee044876a9e797 Mon Sep 17 00:00:00 2001 From: antonb <130487593+antonbosss@users.noreply.github.com> Date: Mon, 18 Mar 2024 19:52:06 +0200 Subject: [PATCH 115/129] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6ff95aa..71f7343 100644 --- a/README.md +++ b/README.md @@ -94,5 +94,5 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC20.md ## MRC 21: Non Fungible Agents -- Status: [**In Discussion**](https://discord.com/channels/1151741790408429580/1219342219115233381)https://discord.com/channels/1151741790408429580/1219342219115233381 +- Status: [**In Discussion**](https://discord.com/channels/1151741790408429580/1219342219115233381) - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC21.md From 03a62d817c2fddab53712e6402188d648833875c Mon Sep 17 00:00:00 2001 From: David Johnston Date: Mon, 18 Mar 2024 14:32:25 -0400 Subject: [PATCH 116/129] Delete Morpheus Request For Comments (MRC).md Deleting Duplicate --- Morpheus Request For Comments (MRC).md | 90 -------------------------- 1 file changed, 90 deletions(-) delete mode 100644 Morpheus Request For Comments (MRC).md diff --git a/Morpheus Request For Comments (MRC).md b/Morpheus Request For Comments (MRC).md deleted file mode 100644 index ea7aa2a..0000000 --- a/Morpheus Request For Comments (MRC).md +++ /dev/null @@ -1,90 +0,0 @@ -# Morpheus Request for Comments (MRC) -List of proposals extending Decentralized AI. -Similar to the function of the ERC system serves in Ethereum. -https://eips.ethereum.org/erc Provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. - -## List of MRCs: - -## MRC 00: Morpheus Request for Comment Standard -- Status: **Adopted** -- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC00.md - -## MRC 01: Smart Agents White Paper. -- Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. -- Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/White%20Paper.md - -## MRC 02: Smart Agents Yellow Paper. -- Status: **Adopted** by the Morpheus anon authors as the basis for Morpheus Network. -- Link: https://github.com/SmartAgentProtocol/SmartAgents/blob/main/YellowPaper.md - -## MRC 03: Morpheus White Paper. -- Status: **Adopted** by the Morpheus community as basis for Morpheus Network. -- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/WhitePaper.md - -## MRC 04: Morpheus Yellow Paper. -- Status: **In Progress**, Being implimented as the basis for Capital, Code, Compute and Community Builders. -- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/YellowPaper.md - -## MRC 05: Yellowstone Compute Model. -- Status: **In Progress**, Being implimented as the Decentralized Router for the launch of Compute rewards post bootstrapping period. -- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Yellowstone%20Compute%20Model.md - -## MRC 06: Techno Capital Machine -- Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. -- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md - -## MRC 07: Fair Launch Process -- Status: **In Progress**, Being implimented as the Smart Contracts being used for the Capital Providers of Morpheus. -- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Fair%20Launch.md - -## MRC 08: Waterloo Community Model. -- Status: **Under Discussion**, needs additional work to flush out the concepts. -- Link: https://docs.google.com/document/d/1uMvRT_WA1KqJAkoHbs7fxDkMtYrcdprXrbOmssEXtGg/edit?usp=sharing - -## MRC 09: AMM Launch Process -- Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. -- Link: https://github.com/generativeone/Docs/blob/main/Building%20the%20Foundation%20-%20AMM%20Launch.md - -## MRC 10: Development of Smart Agent Tools Marketplace. -- Status: **Under Discussion**, needs further discussion and approval. -- Link: https://docs.google.com/document/d/1JJQR4-b63VbJQ_etSt5Poyk1KcK3f7FvUZcwKB5Zpk8/edit?usp=sharing - -## MRC 11: Morpheus Multi-Agent Framework. -- Status: **Under Discussion**, needs further discussion to cover edge cases. -- Link: https://docs.google.com/document/d/1i6FBD7OIMEHSYMgKUGmrjpxgnlFN20JRC4_yW9bAVWw/edit?usp=sharing - -## MRC 12: Capital contracts expansion to stMATIC. -- Status: **Under Discussion**, needs further discussion to cover all edge cases and flesh out more concepts. -- Link: https://docs.google.com/document/d/1lZ_vJ3exkrn8DscHI6C59unp5Lui895rtN4nc-e2wso/edit?usp=sharing - -## MRC 13: Launch TCM for MOR Yield Farming on Solana with JitoSOL and/or mSOL. -- Status: **Under Discussion**, needs further discussion to answer open questions (see end of doc) and approval. -- Link: https://0xmacro.notion.site/MRC-13-Launch-TCM-for-MOR-Yield-Farming-on-Solana-with-JitoSOL-and-or-mSOL-a0f9e2c0fa884aa590fe993c38bc627b - -## MRC 14: MOR MOR Weights for Greater Granularity. -- Status: **In Progress**, Planned implementation for April 8th 2024 weights snapshot. -- Link: https://docs.google.com/document/d/1_5WZSNZ8LDwrD-mWNR3HzZT4asYSHYeqHsybXvz302g/ - -## MRC 15: A Framework for Adding Yield-Generating Assets. -- Status: **Under Discussion**, needs further discussion to cover edge cases and to receive community feedback. -- Link: https://github.com/generativeone/Docs/blob/main/Expanding%20Horizon%20-%20The%20Morpheus%20Asset%20Integration%20Framework.md - -## MRC 16: - -## MRC 17: - -## MRC 18: - -## MRC 19: - -## MRC 20: "Automated Recurring Revenue / Rewards" (ARR) - The MOR 20 Token Standard -- Status: **Under Discussion** -- 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 reacurring 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. -- Link: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md#automated-recurring-revenue--rewards-arr-generalizing-the-tcm-model---mor20-token-standard From 239bbd27316bb34cd32e1a8ecb0bf17ff69d7463 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Mon, 18 Mar 2024 16:25:42 -0400 Subject: [PATCH 117/129] Update MRC08.md --- MRC08.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/MRC08.md b/MRC08.md index 1810eb3..973ee2f 100644 --- a/MRC08.md +++ b/MRC08.md @@ -23,11 +23,11 @@ For example, a developer that creates an easy to use app or website that funnels In determining the best method for allocation emissions for Capital Front Ends, Morpheus considered three alternatives. Each focuses on a pro-rata distribution methodology, but differ in the time horizon considered: - **Daily** - emissions are distributed based on daily capital deposits. The primary benefit of this methodology is that it continually encourages and rewards new depositors. However, there are multiple downsides. First, capital deposits won't be smooth - 10 stETH could be deposited on one day and 100 stETH the next. As such, the Community Capital Front End emissions would be greatly disproportionate to the capital contributed as a full day’s emissions would be provided for 10 stETH one day and 100 stETH the next. Second, this could result in a manipulation of the system. Since it would be limited to a one day time horizon, users could repeatedly deposit to earn the Community Capital Front End emissions, then withdraw funds and deposit a day or two later to earn more again. - **Cumulative** - emissions are distributed based on the cumulative capital deposits to date. This methodology distributes emissions based on the value of capital provided, regardless if that capital was contributed on a particular day, or months/years in the past, so long as it remains deposited. The downside to this approach is that it could discourage builders to develop new front ends. If a large amount of capital is already allocated, then incremental amounts will be relatively insignificant - meaning builders are less incentivized to continue building for an ever smaller piece of the pie. -- **1 Year Duratio**n - capital deposits through a front-end are relevant for one year so long as they remain deposited. Emissions are distributed based on the pro rata share of the trailing one year deposits. The length of the timeline could be set to any number of days/years. The goal would be to find the appropriate balance which encourages new front end development to solicit capital while removing unnecessary transactions and potential exploitation. +- **1 Year Duration** - capital deposits through a front-end are relevant for one year so long as they remain deposited. Emissions are distributed based on the pro rata share of the trailing one year deposits. The length of the timeline could be set to any number of days/years. The goal would be to find the appropriate balance which encourages new front end development to solicit capital while removing unnecessary transactions and potential exploitation. **Multi-Asset Considerations.** stETH on Ethereum is the only capital currently allowed to be contributed. Over time, more assets and more chains may be added. With additional assets deposited as capital, it raises several complexities that must be accounted for: -- **Price Feeds** - All currencies must be denominated into a comparable asset in order to determine relevant value. This will occur by translating all currencies into the equivalent USDC value at the time of the transaction. [will need to define the Oracle price feeds to be utilized as well as the timing: price updates by block, average for the day, spot at end of day, etc] +- **Price Feeds** - All currencies must be denominated into a comparable asset in order to determine relevant value. This will occur by translating all currencies into the equivalent ETH value at the time of the transaction. This function is available through the Layer Zero API. - **Relative Movements across Assets** - Currencies will move relative to each other after being deposited. For example, if token A is deposited when its price is $100 and Token B is deposited when its price is $200, then at the time of deposit, it is a 1:2 ratio. A user who deposited 1 Token A will be credited with half the value of a user who deposited 1 Token B. However, if a week later, Token A’s price has stayed at $100 while Token B’s price has increased to $300, the ratio is now at 1:3 for those same deposits. Prices will need to be updated on a regular basis to ensure that the user’s deposited value represents actual prices. - **Asset Movements across Time** - A similar situation arises when two users deposit the same asset at different times. If User 1 deposits a single Token B at $200 and User 2 deposits a single Token B a week later at $300. They both have deposited 1 Token B and contributed equally at any time moving forward - the MOR rewards generated will only be considered equal if the token prices are routinely updated and not focused on price at the time of entry. - **Yields Differ across Deposited Assets** - Different assets earn different yields. Those assets depend on the asset, protocol, and market conditions among other factors. The yield on the deposited asset is ultimately what is contributed to Morpheus. At first glance, the only thing Morpheus would care about would be the benefit it receives regarding yield. However, a wide variety of assets and chains strengthens the health of Morpheus. It helps to protect Morpheus via diversification. There are a variety of analyses out there, but generally speaking, a higher yield, by default, implies a higher risk. Therefore, assets that may have a lower yield attached to them should still be encouraged as the underlying assets might be viewed as ‘safer’ or have a better likelihood of appreciation in value. Therefore, a blended approach would balance the difference and reward across the capital deposited and yield generated. @@ -38,7 +38,7 @@ The below example shows, using random assets and numbers for presentational purp |----------------------------------------|---------------|------------------|----------------|-------------------------|-------------------| Lido - stETH | $100,000,000 | 74% | $9,315 | 61% | 67.5% | Lido - stMATIC | $5,000,000 | 4% | $548 | 4% | 4% | -Jito - JuitSOL | $20,000,000 | 15% | $4,164 | 27% | 21% | +Jito - JitoSOL | $20,000,000 | 15% | $4,164 | 27% | 21% | GMX - GMX | $10,000,000 | 7% | $1,208 | 8% | 7.5% | Total | $135,000,000 | 100% | $15,235 | 100% | 100% | From 495448fd5d78104e58f390402cf413b4f3a17848 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Mon, 18 Mar 2024 16:49:16 -0400 Subject: [PATCH 118/129] Update MRC08.md Extending the Waterloo paper to include Staking MOR as the means of directing rewards to Smart Agent builders. --- MRC08.md | 24 +++++++++++++++++++----- 1 file changed, 19 insertions(+), 5 deletions(-) diff --git a/MRC08.md b/MRC08.md index 973ee2f..35f23a0 100644 --- a/MRC08.md +++ b/MRC08.md @@ -8,12 +8,23 @@ The Web3 community has long suffered from a lack of front-end development. This ## Types of Rewards By using the weights below, the community rewards will make each of the core functions of the Morpheus Network more broadly accessible and increase the Morpheus Code, Compute, and Capital resources. -### End User Applications -Builders of End User Applications will receive 8% of all MOR emissions for generating demand for the Smart Agents. +## 1. MOR Staking - A Free Market Mechanism To Direct MOR Rewards Toward End User Applications +Builders of Smart Agents and other End User Applications will receive 8% of all MOR emissions. -For example, a developer builds a website for the average person to use Smart Agents from the Morpheus Network. That user will also register their public key in the Morpheus protocol and get credit based on the amount of MOR fees paid by those users. +These rewards will be directed in proportion to the MOR holders who "Stake" their MOR into the MOR20 Smart Contract for a specific Smart Agent. -### Capital Front Ends +So for example if a MOR holder has 1% of the MOR in circulation and Stakes it toward "DeFiAgent 420 (DA420)", then for as long as that MOR is Staked, the Morpheus protocol will direct 1% of the 8% of MOR emissions (0.08% of all 14,400 daily MOR emissions = 11.52 MOR per day) toward the DeFiAgent 420's AMM Uniswap pool. In return MOR Stakers earn new tokens in the projects they Stake towards. + +**This MOR Staking approach has some compelling benefits:** +- Thus the MOR token will become the common trading pair for the Protocol Owned Liquid of every project launched on Morpheus (like ETH is for projects on Ethereum). +- This effectively extends the model Morpheus has already proven with stETH to MOR as the means of bootstrapping projects on top of its platform. +- Holders of the MOR token get to individually express which projects they think are most worthy of support. +- Holders of hte MOR token gain tokens in projects building on Morpheus without having to sell their MOR. +- The Morpheus protocol sends all rewards directly to the project & the Stakers and so no central points of failure are created in the new projects. +- The project creates a straight forward path to rewarding Coders and thus attract builers to maintain / expand its Code base. +- Projects get access to Compute (as MOR holders have access to Inference on Morpheus) since the project is holding MOR in the Protocol Owned Liquidity this will poweer their Smart Agent interactions. + +## 2. Capital Front Ends Builders of front ends for the Capital Providers will receive 8% of all MOR emissions. For example, a developer that creates an easy to use app or website that funnels Capital into the Morpheus Capital Provider smart contract would get a part of the 8% emissions pro-rata to the capital their public key tagged to the capital provision transaction. @@ -42,7 +53,10 @@ Jito - JitoSOL | $20,000,000 | 15% | $4,164 | 27% | 21% | GMX - GMX | $10,000,000 | 7% | $1,208 | 8% | 7.5% | Total | $135,000,000 | 100% | $15,235 | 100% | 100% | -### Compute Front Ends +### Summary of Capital Front Ends +All of this analysis to say that the only method for fairly compensating yield contributed is based on a common denomination of ETH and measuring the yield based on the actual amount of ETH transferred to the Morpheus Protocol Owned Liquidity vs emitting rewards based on the asset creating the yield. + +## 3. Compute Front Ends Builders of front ends for the Compute Providers will receive 8% of all MOR emissions. For example, a developer builds a Software Development Kit, API or website that makes it easier to provide Compute to the Morpheus Network. In doing so, they qualify to receive a pro-rata amount based on the amount of Compute they helped to enroll. From 908b8eba04f3db046edbf138e57aa5aeaa2ad6ef Mon Sep 17 00:00:00 2001 From: David Johnston Date: Mon, 18 Mar 2024 16:54:42 -0400 Subject: [PATCH 119/129] Create MRC22.md MOR Staking --- MRC22.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 MRC22.md diff --git a/MRC22.md b/MRC22.md new file mode 100644 index 0000000..a0e7244 --- /dev/null +++ b/MRC22.md @@ -0,0 +1,25 @@ +# MRC 22: MOR Staking - A Free Market Mechanism To Direct MOR Rewards Toward End User Applications +As described in the Waterloo paper, builders of Smart Agents and other End User Applications will receive 8% of all MOR emissions. +https://github.com/MorpheusAIs/MRC/blob/main/MRC08.md + +These rewards will be directed in proportion to the MOR holders who "Stake" their MOR into the MOR20 Smart Contract for a specific Smart Agent. + +So for example if a MOR holder has 1% of the MOR in circulation and Stakes it toward "DeFiAgent 420 (DA420)", then for as long as that MOR is Staked, the Morpheus protocol will direct 1% of the 8% of MOR emissions (0.08% of all 14,400 daily MOR emissions = 11.52 MOR per day) toward the DeFiAgent 420's AMM Uniswap pool. + +In return MOR Stakers earn the new DA420 tokens in the DeFIAgent project they Staked towards. + +**This MOR Staking approach has some compelling benefits:** +- Thus the MOR token will become the common trading pair for the Protocol Owned Liquid of every project launched on Morpheus (like ETH is for projects on Ethereum). +- This effectively extends the model Morpheus has already proven with stETH to MOR as the means of bootstrapping projects on top of its platform. +- Holders of the MOR token get to individually express which projects they think are most worthy of support. +- Holders of hte MOR token gain tokens in projects building on Morpheus without having to sell their MOR. +- The Morpheus protocol sends all rewards directly to the project & the Stakers and so no central points of failure are created in the new projects. +- The project creates a straight forward path to rewarding Coders and thus attract builers to maintain / expand its Code base. +- Projects get access to Compute (as MOR holders have access to Inference on Morpheus) since the project is holding MOR in the Protocol Owned Liquidity this will poweer their Smart Agent interactions. + +## Implementation +The implementation would be a variation of the standard MOR20 Token Smart Contracts, but instead of stETH being the source of yield, the MOR token itself would serve this purpose. + +All other aspects of the MOR20 Smart Contracts would be the same. The same AMM pool model. The same weights system to track and reward Capital Providers, Coders, Compute and so forth. + +This would be a phase 3 Smart Contract deployment after Code, Capital, and Compute are all live on Morpheus as part of the Community App Builder phase. From d3bf45baad275d94e94c979ccb10248891efd872 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Mon, 18 Mar 2024 16:57:59 -0400 Subject: [PATCH 120/129] Update README.md MRC 22 - MOR Staking --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 71f7343..4885de4 100644 --- a/README.md +++ b/README.md @@ -96,3 +96,7 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d ## MRC 21: Non Fungible Agents - Status: [**In Discussion**](https://discord.com/channels/1151741790408429580/1219342219115233381) - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC21.md + +## MRC 22: MOR Staking - A Free Market Mechanism To Direct MOR Rewards Toward End User Applications +- Status: [**In Discussion**](https://discord.com/channels/1151741790408429580/1219389170040967218) +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC22.md From c8479e41254c4b475f18057a28fabfbc9f1caea5 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Mon, 18 Mar 2024 16:58:36 -0400 Subject: [PATCH 121/129] Update README.md Updated description for MRC22. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4885de4..4418e91 100644 --- a/README.md +++ b/README.md @@ -97,6 +97,6 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d - Status: [**In Discussion**](https://discord.com/channels/1151741790408429580/1219342219115233381) - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC21.md -## MRC 22: MOR Staking - A Free Market Mechanism To Direct MOR Rewards Toward End User Applications +## MRC 22: MOR Staking - A Free Market Mechanism To Direct MOR Rewards Toward Smart Agent & End User Applications Builders - Status: [**In Discussion**](https://discord.com/channels/1151741790408429580/1219389170040967218) - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC22.md From 6060175e1e3602bcaac8bfc53a0c5a0465655e82 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Mon, 18 Mar 2024 17:25:28 -0400 Subject: [PATCH 122/129] Update MRC22.md --- MRC22.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MRC22.md b/MRC22.md index a0e7244..8bba7a6 100644 --- a/MRC22.md +++ b/MRC22.md @@ -1,4 +1,4 @@ -# MRC 22: MOR Staking - A Free Market Mechanism To Direct MOR Rewards Toward End User Applications +# MRC 22: MOR Staking - A Free Market Mechanism To Direct MOR Rewards Toward Smart Agent & End User Application Builders As described in the Waterloo paper, builders of Smart Agents and other End User Applications will receive 8% of all MOR emissions. https://github.com/MorpheusAIs/MRC/blob/main/MRC08.md From 5d4c37f0e572768097b01d3f19400526a591eb1d Mon Sep 17 00:00:00 2001 From: generativeone <162616095+generativeone@users.noreply.github.com> Date: Tue, 19 Mar 2024 21:56:35 +0400 Subject: [PATCH 123/129] Create MRC23.md --- MRC23.md | 152 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 152 insertions(+) create mode 100644 MRC23.md diff --git a/MRC23.md b/MRC23.md new file mode 100644 index 0000000..9ed7de8 --- /dev/null +++ b/MRC23.md @@ -0,0 +1,152 @@ +# Fortifying Morpheus: The Critical Role of Protection Fund Diversification + +## Introduction + +This paper aims to highlight the critical role of a diversified Protection Fund in the long-term strategy of the Morpheus ecosystem. Proposed is a refined approach to the existing Morpheus model that not only enhances its current framework but also opens pathways for broader diversification. + +As a quick background, the Protection Fund serves to provide financial support for payments related to audits, bug bounties, compensation resulting from attacks, etc. Additional details can be found via: https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Protection%20Fund%20Details.md. + +Morpheus serves as a hub for a diverse group of participants, including Code, Capital, and Compute providers, Community builders, and users, facilitating a variety of interactions within its ecosystem. To ensure these participants can engage with confidence and security, it is essential to establish a well-diversified Protection Fund. Such a fund can provide a robust safety net, fostering a secure environment for all involved, regardless of market conditions. In its current implementation, the fund's holdings are expected to consist solely of 4% of the MOR emissions, which results in a lack of diversification. + +## The Problem + +The singular reliance on MOR as the sole asset in the Protection Fund's holdings reduces its optionality and introduces a significant vulnerability in scenarios requiring substantial payouts. In the event of a large-scale payout, especially when the payout is not denominated in MOR, the perceived necessity to liquidate MOR assets could itself precipitate a decline in the MOR market price. This is due to the increased supply of MOR in the market coinciding with the fund's attempts to meet its payout obligations, potentially exacerbating market pressures and leading to a devaluation of the asset at the very moment its value is most needed. Diminishing its capacity to provide adequate support and protection to the ecosystem's participants. + +## Strategic Solution + +To enhance the resilience and stability of the Morpheus ecosystem, this MRC proposes a multifaceted approach to diversifying the assets held within the Protection Fund. This strategy is designed to mitigate risks and ensure a robust safety net for all ecosystem participants. The following outlines the proposed diversification mechanisms: + +1. **Emissions-Based Diversification**: It is proposed to allocate 25% of the MOR received by the Protection Fund from its share of total MOR emissions (4% of the total emissions) towards diversifying its holdings. Specifically, this allocation will be split into stETH and stablecoins (DAI), with 12.5% of the Protection Fund's MOR allocated to each asset class. This diversification process will be conducted on a weekly basis, ensuring a consistent and strategic approach to asset allocation. Please refer to Appendix B for an analysis on the market impact of emissions-based diversification. + +2. **MRC 20 Standard Earnings**: As a further measure to bolster the Protection Fund, it’s suggested to retain 25% of the earnings accrued to Morpheus through the MRC 20 standard directly within the Protection Fund. This approach aims to capitalize on the expansion of the MRC 20 standard generated by the ecosystem's activities, reinforcing the Protection Fund’s capacity to support the ecosystem in times of need. Please refer to Appendix C for deeper analysis and supporting documentation. + +3. **New Yield-Generating Assets**: In anticipation of future growth and the integration of new yield-generating assets into the Morpheus ecosystem, it is proposed that 5% of any yield earned from these new assets be retained within the Protection Fund. This policy is designed to automatically enhance the fund's diversification of assets in which Morpheus operates and financial health as the ecosystem expands and evolves. Please refer to Appendix D for deeper analysis and supporting documentation. + +## End Result: Operational Framework + +The operational framework for enhancing the Morpheus ecosystem's financial resilience and stability is structured around three core strategies: diversification through asset allocation, retention of earnings, and integration of yield-generating assets. Here's how each component is mechanized: + +1. **Emissions-Based Diversification**: The Protection Fund will allocate 25% of the MOR it receives from its share of total MOR emissions (4% of the total emissions) towards diversifying its holdings. This strategic allocation aims to balance the fund's asset composition, thereby mitigating risks associated with the volatility of MOR's price. The process is broken down as follows: + + The allocated 25% will be evenly split between stETH and stablecoins (DAI), dedicating 12.5% of the Protection Fund's MOR to each asset class. This diversification targets both growth and stability by investing in Ethereum (via stETH) and the reliable value of stablecoins. + + This diversification process will be carried out on a weekly basis and executed through the Protection Fund smart contract, an automated on-chain swap via Uniswap, originating from the main location of the Protection Fund, which is currently on Arbitrum. + +2. **MRC 20 Standard Earnings**: To further reinforce the Protection Fund, 25% of the earnings generated through the MRC 20 Standard activities within the Morpheus ecosystem will be retained within the fund. This strategy leverages the economic activities and expansions driven by the MRC 20 standard, ensuring a portion of the generated value directly contributes to the ecosystem's safety net. As yield is earned by Morpheus through the MCR 20 Standard, 25% of the yield will be retained in the Protection Fund before the remainder is allocated to the liquidity pool, as currently proposed in the MRC 20 standard. This allocation will follow the same cadence adopted for adding that yield to the liquidity pool. + +3. **New Yield-Generating Assets**: With the anticipation of Morpheus ecosystem's growth and the integration of new yield-generating assets, a policy is proposed where 5% of any yield earned from these assets is retained within the Protection Fund. This approach is designed to organically enhance the Protection Fund’s diversification and financial health as new assets are adopted and as the ecosystem evolves. + +A native Protection Fund contract will be established on any new platform to which Morpheus expands. Additionally, 5% of the yield generated by new yield-generating assets will be retained in the newly established Protection Fund smart contract, following the same cadence adopted for yield collection on that platform. + +## Value Proposition: Advantages of the Proposed Solution + +1. **Risk Diversification** + +Incorporating stETH and other assets, alongside MOR within the Protection Fund, serves as a fundamental strategy for mitigating the fund's exposure to the price volatility of MOR. This diversification is crucial for enhancing the overall stability of the ecosystem. By balancing the asset composition of the Protection Fund, ensuring a more resilient financial foundation capable of withstanding market fluctuations, thereby safeguarding the ecosystem's integrity and the interests of its participants. + +2. **Ownership in Underlying Platforms and Expansion Ecosystems** + +**Strategic Exposure**: Actively acquiring stakes in essential assets and technologies within the ecosystems Morpheus enters. This diversification not only broadens the Protection Fund assets, but also integrates Morpheus into the core of these burgeoning platforms, securing a vested interest in their success and governance mechanisms. + +**Ecosystem Integration**: Owning assets in the ecosystems Morpheus ventures into not only secures a strategic position but also offers valuable insights and influence over the development trajectories and governance of these platforms. This proactive involvement allows Morpheus to contribute to and benefit from the innovation and growth within these ecosystems. + +3. **Asset Matching for Payments in Event of Exploit** + +One type of payment that the Protection Fund is created to cover is user losses in the case of an exploited Morpheus Smart Contract (refer to https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Protection%20Fund%20Details.md). Having a diversified set of assets in the Protection Fund allows Morpheus to payout the correct asset in the event of an exploit. For example, if there is an exploit on a JitoSOL capital contract, then Morpheus can directly reimburse JitoSOL. Without having the corresponding assets, the Protection Fund would either be required to sell MOR for JitoSOL, or establish a snapshot ratio for how much each JitoSOL is worth in terms of MOR. As we have seen with large scale exploits and bankruptcies across the industry, this often results in a process that is overly complicated due to establishment of ratios, snapshot dates, changes in asset price/ratios over time, and a variety of other factors. + +4. **Payout Scenarios** + +Incorporating a contingency plan for potential payouts, the Protection Fund is uniquely positioned to leverage its structure in the event of insufficient MOR holdings to meet payout requirements. A pivotal advantage underpinning the fund is its guaranteed receipt of 4% of MOR emissions, a steady inflow that provides a reliable source of assets. In scenarios where the fund's current MOR holdings are not sufficient to cover required payouts, this ongoing emission allocation can be strategically earmarked to fulfill the payout obligations as it accrues. This mechanism ensures that, despite the immediate shortfall, the Protection Fund can commit to compensating the required payouts, offering a layer of financial resilience and stability that is essential for maintaining confidence within the Morpheus ecosystem. This forward-looking approach not only enhances the fund's capability to manage its liabilities but also underscores the robustness of its financial planning and risk management strategies. + +The diversification of the Protection Fund also puts Morpheus in a stronger position when determining payouts. Morpheus can offer payments in multiple currencies and work with the developer, audit company, etc. to negotiate favorable terms if there is a preferred asset designation. + +## List of Morpheus Reference Implementations Effected + +- Protection Fund +- Smart Contracts on Ethereum / Arbitrum / Future venues +- TCM / MOR20 Token Standard for Fair Launches + +## Dependencies + +- “Morpheus Protection Fund Proposal” in the Key Docs repository. MOR emissions as noted (4% of total daily) would be impacted as 25% of these would need to be traded for stETH and DAI. +- “TechnoCapitalMachineTCM” in the Key Docs repository and MRC20. Both of these developments will impact directing 25% of Morpheus’ earning from this process towards the Protection Fund. +- Integration with new yield-generating assets. These are less dependencies, but more so MRCs that will be impacted if this Protection Fund MRC gets accepted as 5% of these new assets’ yield would be directed to the Protection Fund: + * MRC15: Asset Integration Framework + * MRC12: stMATIC + * MRC13: JitoSOL + * MRC17: Solana + +## Time to Complete + +- Completed: Primary research and analytics on diversification approaches and strategies. +- 3 weeks: MRC published and strategy refinement based on community discussions. +- 3 weeks: Technical development and integration consisting of the emissions-based diversification where a smart contract will be developed to sell 25% of MOR on a weekly basis in Protection Fund: 12.5% for stETH and 12.5% for stablecoins. +- Ongoing: Collaborate with discuss and development around MRC20 Standards and rollout so that 25% of earnings can be allocated to Protection Fund +- Ongoing: Collaborate and discuss with yield-generating asset integration frameworks to align with the implementation of the 5% of new asset yield directed to the Protection Fund. + +## Conclusion + +This MRC articulates a comprehensive strategy aimed at fortifying the Morpheus ecosystem through the diversification of the Protection Fund. By addressing existing vulnerabilities and enhancing operational processes, we endeavor to establish a secure, liquid, and well-diversified ecosystem that confers benefits to all participants. This document serves as a foundational blueprint for these critical improvements, laying the groundwork for future refinement and optimization. Through collective dialogue and in-depth analysis, we invite the community to engage in this evolutionary process, ensuring that our ecosystem not only thrives but also remains resilient against the challenges ahead. Together, we are setting a new standard for ecosystem security and stability, ensuring that Morpheus continues to be a beacon of innovation and collaboration in the blockchain space. + +## Appendices + +*The information provided is strictly hypothetical and is for visualization and general informational purposes only. All information on the charts is provided in good faith, however, we make no representation or warranty of any kind, express or implied, regarding the accuracy, adequacy, validity, reliability, availability, or completeness of any information on the charts. The data presented in the charts, including but not limited to staked values, yields, USD yields, and allocations to protection funds, are hypothetical and should not be considered as financial advice. The outcomes are based on theoretical scenarios and should not be taken as predictions of future performance.* + +**Appendix A: Future Considerations** + +This appendix serves to encompass relevant topics that can be evaluated in the future. Since there are a vast number of unknowns regarding the future, this section means to highlight areas to keep in mind based on future decisions for Morpheus as well as future market conditions. None of these are to be completed during the development and implementation of this particular MRC, but can serve as a starting point for future maintenance or separate MRCs. + +- Re-balance Protection Fund: as future prices are unknown, there is a chance that due to increase or decreases in a particular asset price from the time of acquisition, the Protection Fund could be overly weighted in one direction or another. This could present an opportunity to perform trades to balance asset allocations towards a defined percentage breakdown. For example, if MOR appreciates in price and crosses a threshold of 80% (or 90%, 95%, 99%, etc), then it could trigger a mechanism to sell some MOR for stETH, DAI, or other assets to bring down over-weighting on MOR. +- Evaluate different stablecoins beyond DAI. DAI was selected as it best aligns with Morpheus’ ideals. In the future, it may make sense to hold other (USDC, USDT or other) stablecoins in some capacity. It also is worth evaluating holding yield generating versions of stablecoins. +- Allocate 5% of stETH yield to the Protection Fund starting after 1 year +- Adjust the % of yield from staked assets over time. Initially set at 5%, but could increase in the future as liquidity deepens and the need for additional protocol owned liquidity is less pronounced. +- Evaluate over time if 12.5% of emissions should continue to go towards stETH, or if a different asset makes sense. For example, if a different yield generating asset overtakes stETH in total contribution, then the 12.5% could get directed to that asset to encourage alignment of the Protection Fund diversification with the capital contribution and ecosystem activity. +- Consider how to manage the assets within the Protection Fund. One consideration could be to participate in MRC20 Standard via the TCM model as new projects onboard. This would allow the Protection Fund to gain exposure to native tokens of the new protocols that align with Morpheus. +- Adjust some percentage of stETH to ETH to avoid Lido risk. + +| MOR Price | Daily USD | 25% Diversification | 12.5% to DAI | 12.5% to stETH | +|-----------|-----------|---------------------|--------------|---------------| +| $20 | $11,160 | $2,790 | $1,395 | $1,395 | +| $40 | $22,320 | $5,580 | $2,790 | $2,790 | +| $60 | $33,480 | $8,370 | $4,185 | $4,185 | +| $80 | $44,640 | $11,160 | $5,580 | $5,580 | +| $100 | $55,800 | $13,950 | $6,975 | $6,975 | +| $120 | $66,960 | $16,740 | $8,370 | $8,370 | +| $140 | $78,120 | $19,530 | $9,765 | $9,765 | +| $160 | $89,280 | $22,320 | $11,160 | $11,160 | +| $180 | $100,440 | $25,110 | $12,555 | $12,555 | +| $200 | $111,600 | $27,900 | $13,950 | $13,950 | + +**Appendix B: Emissions-Based Diversification Market Impact** + +Over the first year, an average of 558 MOR will be emitted to the Protection Fund on a daily basis. The table below shows the impact of selling 25% of those emissions for diversification, based on different prices of MOR. Please note, all amounts below are on a daily basis. + +| Staked Value | Yield | USD Yield | Morpheus Fee (0.35%) | Protection Fund Portion (25%) | +|-----------------|-------|------------|----------------------|-------------------------------| +| $100,000,000 | 5% | $5,000,000 | $17,500 | $4,375 | +| $200,000,000 | 5% | $10,000,000| $35,000 | $8,750 | +| $300,000,000 | 5% | $15,000,000| $52,500 | $13,125 | +| $400,000,000 | 5% | $20,000,000| $70,000 | $17,500 | +| $500,000,000 | 5% | $25,000,000| $87,500 | $21,875 | +| $600,000,000 | 5% | $30,000,000| $105,000 | $26,250 | +| $700,000,000 | 5% | $35,000,000| $122,500 | $30,625 | +| $800,000,000 | 5% | $40,000,000| $140,000 | $35,000 | +| $900,000,000 | 5% | $45,000,000| $157,500 | $39,375 | +| $1,000,000,000 | 5% | $50,000,000| $175,000 | $43,750 | + +**Appendix C: MRC 20 Standard Earnings** + +The table below provides an outline of the estimated amount contributed to the Protection Fund based on various levels of staked assets participating via MRC 20. To keep numbers easily referenced, the table assumes a 5% yield on the delegated asset. Per the MRC 20 Standard, 0.35% of this yield would be directed to Morpheus. Per this MRC, 25% of that amount going to Morpheus would be allocated to the Protection Fund. Please note, all amounts below are for an annual period. + +| Staked Value | Yield | USD Yield | Annual Protection Fund (5%) | Daily Protection Fund (5%) | +|-----------------|-------|------------|-----------------------------|----------------------------| +| $100,000,000 | 5% | $5,000,000 | $250,000 | $685 | +| $200,000,000 | 5% | $10,000,000| $500,000 | $1,370 | +| $300,000,000 | 5% | $15,000,000| $750,000 | $2,055 | +| $400,000,000 | 5% | $20,000,000| $1,000,000 | $2,740 | +| $500,000,000 | 5% | $25,000,000| $1,250,000 | $3,425 | +| $600,000,000 | 5% | $30,000,000| $1,500,000 | $4,110 | +| $700,000,000 | 5% | $35,000,000| $1,750,000 | $4,795 | +| $800,000,000 | 5% | $40,000,000| $2,000,000 | $5,479 | +| $900,000,000 | 5% | $45,000,000| $2,250,000 | $6,164 | +| $1,000,000,000 | 5% | $50,000,000| $2,500,000 | $6,849 | From ebb79933de752fc72d78543ca19af1d14d2df862 Mon Sep 17 00:00:00 2001 From: generativeone <162616095+generativeone@users.noreply.github.com> Date: Tue, 19 Mar 2024 22:02:56 +0400 Subject: [PATCH 124/129] Update README.md --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 4418e91..5071995 100644 --- a/README.md +++ b/README.md @@ -100,3 +100,7 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d ## MRC 22: MOR Staking - A Free Market Mechanism To Direct MOR Rewards Toward Smart Agent & End User Applications Builders - Status: [**In Discussion**](https://discord.com/channels/1151741790408429580/1219389170040967218) - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC22.md + +## MRC 23: Fortifying Morpheus - The Critical Role of Protection Fund Diversification +- Status: **Under Discussion** needs further discussion and input from the community. +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC23.md From 3d3de453d007d2d085bc875657ea11d5299da537 Mon Sep 17 00:00:00 2001 From: David Johnston Date: Tue, 19 Mar 2024 17:04:25 -0400 Subject: [PATCH 125/129] Update README.md Adding link to MRC 23 discussion in Discord. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5071995..7e4e41c 100644 --- a/README.md +++ b/README.md @@ -102,5 +102,5 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC22.md ## MRC 23: Fortifying Morpheus - The Critical Role of Protection Fund Diversification -- Status: **Under Discussion** needs further discussion and input from the community. +- Status: **[Under Discussion](https://discord.com/channels/1151741790408429580/1219753230746124418)** needs further discussion and input from the community. - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC23.md From f177e4e6fff41be9b8831555f319901c4a65e06d Mon Sep 17 00:00:00 2001 From: David Johnston Date: Tue, 19 Mar 2024 17:05:13 -0400 Subject: [PATCH 126/129] Update MRC23.md Discord link to MRC23 discussion. --- MRC23.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/MRC23.md b/MRC23.md index 9ed7de8..434a242 100644 --- a/MRC23.md +++ b/MRC23.md @@ -1,5 +1,8 @@ # Fortifying Morpheus: The Critical Role of Protection Fund Diversification +Please make comments and pull requests on Github. +For informal chat see this Discord link: https://discord.com/channels/1151741790408429580/1219753230746124418 + ## Introduction This paper aims to highlight the critical role of a diversified Protection Fund in the long-term strategy of the Morpheus ecosystem. Proposed is a refined approach to the existing Morpheus model that not only enhances its current framework but also opens pathways for broader diversification. From 61f4d10e8772feab4bce87652e03a5b23f06404f Mon Sep 17 00:00:00 2001 From: David Johnston Date: Tue, 19 Mar 2024 17:34:43 -0400 Subject: [PATCH 127/129] Update README.md Moving MRC15 to "In Progress" --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7e4e41c..ac65788 100644 --- a/README.md +++ b/README.md @@ -70,7 +70,7 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC14.md ## MRC 15: A Framework for Adding Yield-Generating Assets. -- Status: [**Under Discussion**](https://discord.com/channels/1151741790408429580/1219001846077587577), needs further discussion to cover edge cases and to receive community feedback. +- Status: [**In Progress**](https://discord.com/channels/1151741790408429580/1219001846077587577), needs further discussion to cover edge cases and to receive community feedback. - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC15.md ## MRC 16: Toward MOR Interoperability From 0eccd6f9c27fd81622cb8f7cff9aab60fbafaf9c Mon Sep 17 00:00:00 2001 From: David Johnston Date: Tue, 19 Mar 2024 17:38:11 -0400 Subject: [PATCH 128/129] Update README.md Fixing link for MRC18. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ac65788..0b4d24b 100644 --- a/README.md +++ b/README.md @@ -83,7 +83,7 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d ## MRC 18: Governance Agent - Status: [**Under Discussion**](https://discord.com/channels/1151741790408429580/1219341590334541894) -- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC18:%20Governance%20Agent.md +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC18.md ## MRC 19: Cosmos & Thorchain Expansion of Morpheus - Status: [**Under Discussion**](https://discord.com/channels/1151741790408429580/1219341892781871177) From 5f24b44fc6e71d1e3a1f6087c0a03abee772610a Mon Sep 17 00:00:00 2001 From: lachsbagel Date: Tue, 19 Mar 2024 21:12:39 -0500 Subject: [PATCH 129/129] Lake Travis MRC24 --- MRC24-LakeTravis.md | 203 ++++++++++++++++++++++++++++++++++++++++++++ README.md | 4 + 2 files changed, 207 insertions(+) create mode 100644 MRC24-LakeTravis.md diff --git a/MRC24-LakeTravis.md b/MRC24-LakeTravis.md new file mode 100644 index 0000000..34ecf43 --- /dev/null +++ b/MRC24-LakeTravis.md @@ -0,0 +1,203 @@ +### Lake Travis Decentralized AI Inference System Proposal + +### March 9th, 2024 + +### LachsBagel +lachsbagel@proton.me + + +### Abstract + +In the evolving landscape of decentralized AI, the "Lake Travis Decentralized AI Inference System" introduces significant enhancements to the Morpheus "Yellowstone" Compute Model [1]. This proposal iterates on Erik Voorhees' pioneering work, aiming to refine the distribution of model weights, metering structure and compute incentivization mechanisms on the Morpheus decentralized AI network. This work as well as Voorhees' work are continuations from the original Morpheus white paper [2]. The enhancements detailed below are designed to bolster transparency, efficiency, and security within the network, promoting a more competitive and user-centric ecosystem. + +The system known as the Lake Travis Decentralized AI Inference System will be referred to as the "Lake Travis System.” + + +#### Summary of Enhancements + +1. **Decentralized Model Registry**: + - A pivotal feature of the Lake Travis proposal is the establishment of a decentralized model registry. Compute providers will download models from this registry to host model weights and definitions. This not only facilitates compute consumption but also promotes a distributed file-sharing network by allowing providers to act as nodes in an InterPlanetary File System (IPFS) [3], enhancing the ecosystem's robustness and decentralization. + - Entities like HuggingFace [4] have made significant strides in creating an open model registry accessible to everyone. However, for Morpheus, there's a crucial need for a decentralized model registry. This approach safeguards against adversarial actions that could compromise a vital component of unrestricted AI, ensuring robustness and continuity in the ecosystem. + - Compute providers provide both inference as well as storage for the wider network. + - Each time a model or agent is uploaded it must be named with a globally unique name on the Morpheus network. The upload contains all assets necessary (e.g., model weights, definition) to load and invoke a model, given that the compute provider has the relevant hardware and software dependencies. This allows model or agent builders to receive credit regardless of which compute provider downloads and serves up their model or agent. Model variation uploads may be tagged much like Docker [8] images. + +2. **Router Transparency and Model Popularity Tracking**: + - The Lake Travis System borrows the concept of an on-chain router. However, sessions are established off-chain to ensure users' computation privacy from the world. This also allows all requests and responses to operate with the lowest latency possible as they do not rely on on-chain block resolution times. + - Lake Travis proposes that router requests publicly record, not the content, but the details of which model is being requested and the duration of session times. This critical adjustment ensures the visibility of the most sought-after models, guiding compute providers on which models to prioritize for serving and at competitive pricing offerings. + - Lake Travis introduces a significant evolution from the Yellowstone model by transitioning the Pass/Fail metric from a user-substantiated decision to an inferred attribute, determined by data analytics rather than manual scoring. This refinement suggests that the active participation of users in scoring performance may not be necessary. Instead, Lake Travis computes analytics to ensure fidelity.  This facilitates the identification of potentially malicious actors through the detection of anomalous session durations with respect to given models or agents, ensuring a more streamlined and efficient quality control process. + - For complete transparency, reports will be public. + +3. **Compute Resource Utilization and Pricing**: + - The Lake Travis system introduces a nuanced approach to measuring the use of compute resources, focusing on the session length relative to a provider's set price per unit of time. Such as MOR/hr, MOR/s, etc. Providers are encouraged to view the router's leaderboard of in-demand models to competitively select their prices and publish their measured inference per second (IPS) or tokens per second (TPS) rate. This mechanism allows users to choose providers based on minimum IPS/TPS speed requirements, ensuring flexibility and fairness. + - Charging by session duration future-proofs the pricing mechanism: + - Supports both predetermined (e.g., image classifier) and undetermined output length (e.g., LLM) style inferences + - Treats the model or agent as a first class citizen. When users request a model they do so with a unique model handle. The model or agent builder is rewarded (described below) regardless of which provider fulfills user requests. + - Agnostic of inference accelerator used, enabling for the uptake of more novel chips such as LPUs [9], TPUs [10], VPUs [11], analog coprocessors [12], all while still supporting conventional GPUs and CPUs. + - Eliminates complexity of estimating whether a user has sufficient funds. Compute providers may list minimum connection times. When credits are insufficient and the user cannot or is unwilling to expend their MOR balance, the session can be terminated by the Router. + +4. **Model and Agent Builder Compensation:** + - This framework guarantees that model and agent builders can finally receive compensation for their contributions, irrespective of the compute provider that ultimately facilitates access to their innovations. Such an approach directly fosters and supports a culture of appreciation and incentives for ongoing development through the Morpheus network. + - Model builders would receive a fraction of the compute bucket emissions and rewards proportional to usage as well as payment from direct usage. + - Agent builders would receive emissions from the community bucket as well as payment from direct usage. + +5. **Local and Decentralized AI Inference**: + - Distinguishing between local AI inference and decentralized inference, the Lake Travis System requires that local node installations come pre-installed with trusted smart contracts. A Retrieval-Augmented Generation (RAG) system [5] will load appropriate reference contracts for custom payload generation during user requests. However, there is an even greater onus on users when engaging with third-party models developed by other smart agent and model developers, emphasizing user responsibility in a decentralized landscape.  + + - All inference will occur on single system image computers (SSI). Where an SSI is one which has all storage, memory, and compute elements (i.e., CPUs and accelerators) to be treated as a single machine. Inference is not to be shared between machines. + +6. **Cryptographic Transaction Security**: + - Reinforcing security measures, all cryptographic transactions initiated by a smart agent or Large Language Model (LLM) require a signature from the user's web3 wallet. This provision ensures that agents or models do not possess private keys or the capability to sign transactions, upholding the network's integrity and users' sovereignty over their digital assets. The Lake Travis System hereby recommends all third-party developers who wish to engage with cryptographic and otherwise high value assets request user confirmation before the execution of any such operation. Preferably the design of the model or agent should preclude the ingestion or observability of any private key, password, passphrase, passcode, or any other special knowledge or object which would otherwise allow an automated system to perform an irrecoverable action. + +#### Goals +The goals are largely adapted from [1]. +- Enable users to have a pro-rata quantity of allocated compute available to them each day before depleting their MOR holdings. +- Achieve efficient, scalable, and sustainable provision of permissionless compute resources for AI inference. +- Incentivize low response time and cost competition among compute providers. All while ensuring providers and agent developers are compensated for consumption. +- Minimize the number of blockchain transactions (whether L2 or otherwise). +- A future proof pricing structure where models and agents can have their prices reliably discovered and competed against. +- Incentivize AI model and agent developers to open source their work. +- Demonstrate an economically sound fundamental demand for MOR. + +#### Actors +The following is adapted from [1]. +- Users / Clients + - Have requests to be processed + - Want AI inference for minimal cost and without censorship or surveillance +- Compute Providers + - Have compute and storage + - Want compensation (MOR) +- Morpheus Router + - High throughput processing engine + - Decentralized + - Matches users/clients with relevant compute providers + - Surfaces in-demand models for compute providers + - Aids in detecting and halting bad faith activity +- Morpheus Model Registry + - Allows any compute provider to download and serve in-demand models or agents given they have the necessary compute prerequisites + - Allows model or agent builders to openly publish their work while receiving compensation + - Decentralized +- Morpheus Compute Contract + - Permissionless smart contract which receives emissions of MOR, tracks credits and debits to Providers and Model / Agent Builders, and pays Providers and Model / Agent Builders + +#### Workflow +This is adapted heavily from [2]. +1. Users, Providers, and Router all create MOR pub keys (this is their identity, all messages signed as such). +2. If User HODLs any balance of MOR, User may submit a signed Request for Compute “RFC” message to the Router. User specifies model or agent as well as any price or latency preferences. +3. Router prioritizes RFCs based on User’s MOR balance (solves Sybil issue [6]) +4. Router selects the most competitively priced Provider serving up the desired model or agent. If a provider exists which meets the user's latency requirements, they will be prioritized for session creation over those who don't. +5. Router sends liveness check to Provider. If Pass, then +6. Router connects User to the Provider over a TCP/IP connection +7. User sends their inference query to Provider +8. Provider computes query, sends Result to User +9. User repeats request submission and response reception as desired... +10. Once the user has finished submitting requests, the user's client will close the session to prevent additional charges +12. Router instructs Compute Contract to credit Provider and Agent / Model Builder with MOR +13. (Some time later) Provider and Agent / Model Builder requests payment of MOR from Compute Contract and Compute Contract sends MOR payment if valid + +#### Outcome +- Model / Agent Builders: + - Compensated while open-sourcing their innovations + - Don't need to be concerned about infrastructure considerations +- Compute Providers: + - Compensated for providing compute + - Can download and serve any model / agent +- Users: + - Resolve their AI requests without constraints on compute availability or overreach  + - Receive a free daily compute budget proportional to their MOR holdings [1] + - Can pay for additional compute beyond their budget +- Morpheus Network: + - Rewards all actors involved in serving up decentralized compute + - Incentivizes in-demand models / agents to have more compute availability without a central arbiter + - Has liquidity provided to it by the TCM funding approach [7] and excess demand from Users + +#### Reconciling Yellowstone with Lake Travis +This proposal seeks not only to introduce these enhancements but also to seamlessly integrate them within the existing Yellowstone framework. + +The Lake Travis System delineates between local AI inference — equipped with smart rank features, including trusted contracts and a RAG system [5] — and decentralized inference, where the model registry is open for any model uploads and hosting by compute providers. This distinction aims to balance the openness of decentralized innovation with the reliability and security of trusted, local computation. + +#### Conclusion and Contributions + +The "Lake Travis Decentralized AI Inference System" directly advances upon the Morpheus "Yellowstone" Compute Model's limitations by introducing a nuanced pricing structure that measures compute resources based on session length, ensuring flexibility and fairness. + +This system not only guarantees compensation for model and agent builders, fostering a supportive environment for development and contribution, but also simplifies the user experience by eliminating complex balance estimations and transitioning the pass/fail metric from user-determined to an analytics-based inference. + +Additionally, Lake Travis innovates with a decentralized model registry, enabling a transparent and efficient distribution of AI models, which further enhances accessibility and incentives for model contribution within the ecosystem. + +Through these strategic enhancements, Lake Travis proposes a more robust, competitive, and user-friendly ecosystem, addressing critical shortcomings of current open source and proprietary AI inference arrangements, and setting a new benchmark for decentralized AI network operations. + +--- +### References + +[1] Voorhees, Erik, *Morpheus: “Yellowstone” Compute Model*, 2024. https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Yellowstone%20Compute%20Model.md#workflow + +[2] Morpheus, Trinity, and Neo, *Morpheus: A Network For Powering Smart Agents*, Earth, 2023. https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/WhitePaper.md + +[3] J. Benet, *"IPFS - Content Addressed, Versioned, P2P File System,"* https://doi.org/10.48550/arXiv.1407.3561, arXiv:1407.3561 [cs.NI], [July 2014] + +[4] T. Wolf, L. Debut, V. Sanh, et al., "Transformers: State-of-the-Art Natural Language Processing," Oct. 2019. [Online]. Available: [https://arxiv.org/pdf/1910.03771.pdf](https://arxiv.org/pdf/1910.03771.pdf). + +[5] P. Lewis, E. Perez, A. Piktus, et al., "Retrieval-Augmented Generation for Knowledge-Intensive NLP Tasks," in _Advances in Neural Information Processing Systems (NeurIPS)_, 2020. + +[6] J. R. Douceur, "The Sybil Attack," in Proc. of the 1st International Workshop on Peer-to-Peer Systems (IPTPS), Cambridge, MA, USA, Mar. 2002, pp. 251-260. + +[7] Johnston, D. A., *Techno Capital Machine (TCM): Code, Capital, Community, Compute: The Open Source Revolution Starts Here* https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md + +[8] Docker, Inc., 'Docker: Empowering App Development for Developers,' Docker, Accessed on [March 2024]. [Online]. Available: [https://www.docker.com/](https://www.docker.com/) + +[9] Groq. (2024). Groq LPU Inference Engine Crushes First Public LLM Benchmark. Retrieved from [https://wow.groq.com/groq-lpu-inference-engine-crushes-first-public-llm-benchmark/](https://wow.groq.com/groq-lpu-inference-engine-crushes-first-public-llm-benchmark/) + +[10] Jouppi, N. P., Young, C., Patil, N., & others. (2017). In-datacenter performance analysis of a Tensor Processing Unit™. arXiv preprint arXiv:1704.04760. Retrieved from [https://arxiv.org/abs/1704.04760](https://arxiv.org/abs/1704.04760) + +[11] Q. Xu, V. Li, and C. D. S. Crews, "Neural Architecture Search for Intel Movidius VPU," arXiv:2305.03739 [cs.NE], May 2023. [Online]. Available: [https://doi.org/10.48550/arXiv.2305.03739](https://doi.org/10.48550/arXiv.2305.03739). + +[12] "Taking powerful, efficient inference to the edge," Mythic, February, 2022. [Online]. Available: [https://mythic.ai/wp-content/uploads/2022/02/MythicWhitepaper-2019oct31.pdf](https://mythic.ai/wp-content/uploads/2022/02/MythicWhitepaper-2019oct31.pdf). + +--- + +## Appendix + +### A. Mentions + +Ryan Condron regarding the router.  +Manveer regarding the decentralized model registry. + +### B. Glossary + +- **Agent:** Refers to a smart agent, an AI system capable of autonomous actions to achieve objectives and perform tasks. + +- **Agent builder:** A developer who constructs smart agents, designed to perform autonomous actions and accessible from the Morpheus network. + +- **AI (Artificial Intelligence):** A field of computer science dedicated to the creation of systems capable of performing tasks that normally require human intelligence, such as visual perception, speech recognition, decision-making, and language translation. + +- **Compute Provider:** An entity within the Morpheus network that offers computational resources (e.g., processing power and storage) for AI inference and model hosting. + +- **Inference:** The process of using a trained AI model to make predictions or decisions based on new, unseen data. + +- **IPS (Inferences Per Second):** A measure of the performance capacity of a system, indicating the number of inference operations it can perform in one second. + +- **LLM (Large Language Model):** A type of AI model that has been trained on a vast dataset of text to understand and generate human-like text based on the input it receives. + +- **Model:** In the context of AI, a model is a mathematical representation of what an AI system has learned from the training data. It is used to make predictions or decisions without being explicitly programmed to perform the task. + +- **Model builder:** A developer who creates and trains AI models, potentially contributing them to the Morpheus network. + +- **MOR:** The native cryptocurrency or token utilized within the Morpheus network, used for transactions, rewards, and accessing compute resources. + +- **Morpheus:** A decentralized network designed for powering smart agents and AI inference, facilitating permissionless access to compute resources. + +- **Predetermined output length:** Refers to AI inferences where the output length is known ahead of time, typically based on the model's design. Examples include classification models that output a fixed set of categories. + +- **Provider:** See "Compute Provider." + +- **RFC (Request for Compute):** A message initiated by a user within the Morpheus network to request AI inference services, specifying the model or agent as well as any price or latency preferences. This results in the Router + +- **Router:** A high-throughput processing engine within the Morpheus decentralized AI network. It operates as a decentralized entity responsible for matching users or clients with the most suitable compute providers based on the requested AI inference services. The router plays a critical role in maintaining network efficiency and transparency, leveraging its capabilities to surface in-demand models to providers and ensuring the equitable distribution of computational tasks. The router's functions include prioritizing requests based on users' MOR balance to address potential Sybil attacks, performing liveness checks on compute providers, and facilitating the direct TCP/IP connection between users and providers for session initiation. Additionally, the router records the details of model requests and session durations (without revealing the content of computations) to provide insights into model popularity and guide compute providers on which models to prioritize, enhancing the network's responsiveness and competitive pricing strategies. + +- **TPS (Tokens Per Second):** In the context of Large Language Models (LLMs), TPS refers to the number of tokens (pieces of text) that a model can generate or process per second. This metric is used to measure the speed of LLMs in generating text-based outputs. + +- **Training:** The process of teaching an AI model to make predictions or decisions by feeding it data and letting it learn the patterns within that data. + +- **Undetermined output length:** Refers to AI inferences where the length of the output is not fixed or predetermined, varying based on the input or other dynamic factors. Examples include open-ended conversation models or generative text models. + +- **User:** An individual or entity that utilizes the Morpheus network to submit AI inference requests or engage with smart agents. + diff --git a/README.md b/README.md index 0b4d24b..2739c4c 100644 --- a/README.md +++ b/README.md @@ -104,3 +104,7 @@ There is a dedicated forum on Discord for the discussion of MRCs here: https://d ## MRC 23: Fortifying Morpheus - The Critical Role of Protection Fund Diversification - Status: **[Under Discussion](https://discord.com/channels/1151741790408429580/1219753230746124418)** needs further discussion and input from the community. - Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC23.md + +## MRC 24: Lake Travis - Decentralized AI Inference System +- Status **[In Discussion](PASTE LINK HERE)** +- Link: https://github.com/MorpheusAIs/MRC/blob/main/MRC24-LakeTravis.md