├── !KEYDOCS README FIRST! ├── Capital Providers, MOR20, TCM │ ├── MOR20 A Standard for Recurring Protocol Payments and Payouts in Web3.pdf │ ├── MOR20 Token Launch Guide, Lessons and Tips.md │ ├── MOR20 Value Proposition.md │ ├── Phased AMM Deployment and Fair Price Discovery.md │ ├── Protocol Owned Liquidity Generation Events (POLG).md │ ├── Techno Capital Machine (TCM).md │ └── The Morpheus Asset Integration Framework.md ├── Code Providers │ ├── Weight Allocation by MRI.md │ ├── Weight Maintenance Guide.md │ ├── Code Contributor Best Practices.md │ ├── Code Contributor Weights Guide.md │ ├── Coder Guide.md │ ├── Morpheus Builders Guide.md │ └── Morpheus Reference Implementations (MRI).md ├── Compute Providers │ ├── Compute Node │ │ ├── Compute Node FAQ.md │ │ ├── Intro to Morpheus Compute Node.md │ │ ├── Model_ID Registry.md │ │ ├── Sample Basic Compute Provider Build.md │ │ └── Subnets.md │ ├── Lake Travis Decentralized AI Inference System.md │ ├── Morpheus Lumerin Model Lightpaper.md │ ├── Morpheus Lumerin Model.md │ └── Yellowstone Compute Model.md ├── FAQs & Guides │ ├── Application Builders FAQ.md │ ├── Capital Providers FAQ.md │ ├── Code Providers FAQ.md │ ├── Compute Providers FAQ.md │ ├── General FAQ.md │ ├── Guides │ │ ├── MOR │ │ │ ├── Mainnet │ │ │ │ ├── Capital Rewards Staking Contract Guide.md │ │ │ │ ├── Code Rewards Staking Contract Guide.md │ │ │ │ ├── MOR OFT Bridge Guide.md │ │ │ │ ├── MOR Rewards Dashboard Claim Guide.md │ │ │ │ ├── MOR Rewards Smart Contract Claim Guide.md │ │ │ │ ├── MOR Token Uniswap Swap Guide.md │ │ │ │ └── Morpheus Capital Providers Contract Guide.md │ │ │ └── Testnet │ │ │ │ ├── Builders Contract Testnet Guide.md │ │ │ │ ├── Capital Rewards Staking Testnet Guide.md │ │ │ │ ├── Code Rewards Staking Testnet Guide.md │ │ │ │ ├── Referral Contract Testnet Guide.md │ │ │ │ ├── Rewards Claim Testnet Guide.md │ │ │ │ └── Uniswap Swap Testnet Guide.md │ │ ├── MOR20 Launch Testnet Guide.md │ │ ├── Morpheus Meetup Guide.md │ │ ├── Morstats Info Capital Providers Guide.md │ │ ├── README_MACOS_DEV_BUILD.md │ │ ├── README_WINDOWS_DEV_BUILD.md │ │ └── Techno Capital Machine Capital Providers Dune Dashboard Guide.md │ ├── MOR Rewards Staking FAQ.md │ └── MOR Token and Liquidity FAQ.md ├── MOR - Network For Powering Smart Agents.pdf ├── Morpheus Fundamentals │ ├── MOR Burn Function.md │ ├── MOREconomics.md │ ├── Mastery of Tokenomics.md │ ├── Morpheus Freedoms.md │ └── Top 10 Reasons People Get Excited About Morpheus.md ├── Morpheus Launch Phases.md ├── Morpheus Multisignature Account.md ├── Morpheus Smart Agent Router.md ├── Protection Fund Details.md ├── StagesofDevelopment.md ├── Token Emission Schedule.md ├── WhitePaper.md └── YellowPaper.md ├── Archive ├── Development.md ├── GoerliTestnetSmartContracts.md ├── GoerliTestnetSmartContractsRU.md ├── Installing Morpheus on WSL.md ├── Integrations.md ├── Morpheus Testing Plan.md ├── README 0.0.5.md ├── README 0.0.6.md ├── README 0.0.8.md ├── Sepolia Capital Provision Guides │ ├── Testnet Guide EN.md │ ├── Testnet Guide ES.md │ ├── Testnet Guide PL.md │ ├── Testnet Guide PT.md │ ├── Testnet Guide RU.md │ ├── Testnet Guide UA.md │ └── Testnet Guide ZH.md ├── Steps of Phased AMM Deployment.md ├── Subscription Discount Rate.md ├── Translations │ ├── Arabic │ │ ├── Protection Fund Details Arabic.md │ │ └── Whitepaper Arabic.md │ ├── Bengali │ │ ├── Whitepaper Bengali.md │ │ └── Yellowpaper Bengali.md │ ├── Bulgarian │ │ ├── Protection Fund Details Bulgarian.md │ │ ├── Whitepaper Bulgarian.md │ │ └── Yellowpaper Bulgarian.md │ ├── Chinese │ │ ├── FAQs Chinese.md │ │ ├── Mastery of Tokenomics Chinese.md │ │ ├── Morpheus Meetup Guide Chinese.md │ │ ├── Morpheus Windows Install Guide Chinese.md │ │ ├── Phased AMM Deployment and Fair Price Discovery Chinese.md │ │ ├── Protection Fund Details Chinese.md │ │ ├── Techno Capital Machine TCM Chinese.md │ │ ├── Whitepaper Chinese.md │ │ ├── Whitepaper Traditional Chinese.md │ │ ├── Yellowpaper Chinese.md │ │ └── Yellowstone Compute Model Chinese.md │ ├── Dutch │ │ ├── Whitepaper Dutch.md │ │ └── Yellowpaper Dutch.md │ ├── Estonian │ │ └── Estonian Whitepaper.md │ ├── Finnish │ │ ├── Protection Fund Details Finnish.md │ │ └── Whitepaper Finnish.md │ ├── French │ │ ├── Morpheus Windows Install Guide French.md │ │ ├── Protection Fund Details French.md │ │ ├── Whitepaper French.md │ │ ├── Yellowpaper French.md │ │ └── Yellowstone Compute Model French.md │ ├── German │ │ ├── Morpheus Windows Install Guide German.md │ │ ├── Protection Fund Details German.md │ │ ├── Techno Capital Machine TCM German.md │ │ ├── Whitepaper German.md │ │ ├── Yellowpaper German.md │ │ └── Yellowstone Compute Model German.md │ ├── Greek │ │ ├── Protection Fund Details Greek.md │ │ ├── Whitepaper Greek.md │ │ └── Yellowpaper Greek.md │ ├── Hindi │ │ ├── Protection Fund Details Hindi.md │ │ ├── Whitepaper Hindi.md │ │ ├── Yellowpaper Hindi.md │ │ └── Yellowstone Compute Model Hindi.md │ ├── Hungarian │ │ ├── Protection Fund Details Hungarian.md │ │ ├── Whitepaper Hungarian.md │ │ ├── Yellowpaper Hungarian.md │ │ └── Yellowstone Compute Model Hungarian.md │ ├── Indonesian │ │ ├── Protection Fund Details Indonesian.md │ │ ├── Whitepaper Indonesian.md │ │ └── Yellowpaper Indonesian.md │ ├── Italian │ │ ├── Whitepaper Italian.md │ │ ├── Yellowpaper Italian.md │ │ └── Yellowstone Compute Model Italian.md │ ├── Japanese │ │ ├── Mastery of Tokenomics Japanese.md │ │ ├── Morpheus Meetup Guide japanese.md │ │ ├── Morpheus Windows Install Guide japanese.md │ │ ├── Phased AMM Deployment and Fair Price Discovery Japanese.md │ │ ├── Protection Fund Details Japanese.md │ │ ├── Techno Capital Machine TCM Japanese.md │ │ ├── Whitepaper Japanese.md │ │ ├── Yellowpaper Japanese.md │ │ ├── Yellowstone Compute Model Japanese.md │ │ └── faq japanese.md │ ├── Korean │ │ ├── MOREconomics Korean.md │ │ ├── Morpheus Freedoms Korean.md │ │ ├── Protection Fund Details Korean.md │ │ ├── Techno Capital Machine TCM Korean.md │ │ ├── Token Emission Schedule Korean.md │ │ ├── Top 10 Reasons to be Excited About Morpheus Korean.md │ │ ├── Whitepaper Korean.md │ │ ├── Yellowpaper Korean.md │ │ └── Yellowstone Compute Model Korean.md │ ├── Malay │ │ ├── Morpheus Windows Install Guide Malay.md │ │ ├── Whitepaper Malay.md │ │ └── Yellowpaper Malay.md │ ├── Malayalam │ │ ├── Whitepaper Malayalam.md │ │ ├── Yellowpaper Malayalam.md │ │ └── Yellowstone Compute Model Malayalam.md │ ├── Norwegian │ │ └── Whitepaper Norwegian.md │ ├── Polish │ │ ├── Protection Fund Details Polish.md │ │ ├── Techno Capital Machine TCM Polish.md │ │ ├── Whitepaper Polish.md │ │ └── Yellowpaper Polish.md │ ├── Portuguese │ │ ├── Protection Fund Details Portuguese.md │ │ ├── Whitepaper Portuguese.md │ │ └── Yellowpaper Portuguese.md │ ├── Romanian │ │ ├── Protection Fund Details Romanian.md │ │ └── Whitepaper Romanian.md │ ├── Russian │ │ ├── Protection Fund Details Russian.md │ │ ├── Techno Capital Machine TCM Russian.md │ │ ├── Whitepaper Russian.md │ │ ├── Yellowpaper Russian.md │ │ └── Yellowstone Compute Model Russian.md │ ├── Slovenian │ │ └── Whitepaper Slovenian.md │ ├── Spanish │ │ ├── Whitepaper Spanish.md │ │ ├── Yellowpaper Spanish.md │ │ └── Yellowstone Compute Model Spanish.md │ ├── Swedish │ │ ├── Protection Fund Details Swedish.md │ │ └── Whitepaper Swedish.md │ ├── Turkish │ │ ├── Whitepaper Turkish.md │ │ └── Yellowpaper Turkish.md │ ├── Ukrainian │ │ ├── Protection Fund Details Ukrainian.md │ │ ├── Techno Capital Machine TCM Ukrainian.md │ │ ├── Whitepaper Ukrainian.md │ │ ├── Yellowpaper Ukrainian.md │ │ └── Yellowstone Compute Model Ukrainian.md │ ├── Urdu │ │ ├── Code Contributor Best PracticesCode Contributor Best Practices Urdu.md │ │ ├── Coder Guide Urdu.md │ │ ├── FAQs Urdu.md │ │ ├── Mastery of Tokenomics Urdu.md │ │ ├── Protection Fund Details Urdu.md │ │ ├── Techno Capital Machine TCM Urdu.md │ │ ├── Whitepaper Urdu.md │ │ ├── Yellowpaper Urdu.md │ │ └── Yellowstone Compute Model Urdu.md │ ├── Uzbek │ │ ├── Whitepaper Uzbek.md │ │ └── Yellowpaper Uzbek.md │ └── Vietnamese │ │ └── Whitepaper Vietnamese.md └── ollama_instructions_in_pictures.md ├── Contributions ├── Code - Proof_Of_Contribution.md ├── Code - Proof_Of_ContributionSnapshot1.md ├── Code - Proof_Of_ContributionSnapshot2.md ├── Code - Proof_Of_ContributionSnapshot3.md ├── Code - Proof_Of_ContributionSnapshot4.md ├── Code - Proof_Of_ContributionSnapshot5.md ├── Code - Proof_Of_ContributionSnapshot6.md ├── Code - Proof_Of_ContributionSnapshot7.md ├── Code - Proof_Of_ContributionSnapshot8.md ├── Community - Proof of Contribution.md ├── Compute - Proof of Contribution.md └── PULL_REQUEST_TEMPLATE.md ├── Graphics ├── Design Library.md ├── Docs Graphics │ ├── Chinese │ │ └── Meme for TCM.jpg │ ├── English │ │ ├── MOR Bridge Guide │ │ │ ├── arb-base-fee.png │ │ │ ├── arb-base-send.png │ │ │ ├── arb-eth-fee.png │ │ │ ├── arb-eth-send.png │ │ │ ├── base-eth-fee.png │ │ │ ├── eth-arb-fee.png │ │ │ ├── eth-arb-transact.png │ │ │ ├── eth-base-fee.png │ │ │ ├── eth-base-transact.png │ │ │ ├── mor-value.png │ │ │ ├── remix-base-arb-transact.png │ │ │ ├── remix-base-ataddress.png │ │ │ ├── remix-base-eth-transact.png │ │ │ ├── remix-clone.png │ │ │ ├── remix-compile.png │ │ │ ├── remix-connect.png │ │ │ ├── remix-ethereum-ataddress.png │ │ │ ├── remix-link.png │ │ │ └── remix-moroft.png │ │ ├── MOR Claim Test Guide │ │ │ ├── approve.png │ │ │ ├── approvemainnet.png │ │ │ ├── claim.png │ │ │ ├── deposited.png │ │ │ ├── import MOR.png │ │ │ ├── mint mock steth.png │ │ │ ├── mor balance.png │ │ │ ├── rewards.png │ │ │ └── stake.png │ │ ├── MOR Rewards Dashboard Claim Guide │ │ │ ├── addmor.png │ │ │ ├── addtoken.png │ │ │ ├── chainlist.png │ │ │ ├── claim.png │ │ │ ├── confirm.png │ │ │ ├── connect.png │ │ │ └── connect1.png │ │ ├── MOR Rewards Staking Guides │ │ │ ├── Mainnet │ │ │ │ ├── code user multiplier.png │ │ │ │ ├── codelockend.png │ │ │ │ └── сode lockclaim.png │ │ │ └── Testnet │ │ │ │ ├── add sepolia.png │ │ │ │ ├── approve.png │ │ │ │ ├── approvemainnet.png │ │ │ │ ├── capital lockclaim.png │ │ │ │ ├── claimlockend.png │ │ │ │ ├── convert multiplier.png │ │ │ │ ├── date to timestamp.png │ │ │ │ ├── mint mock steth.png │ │ │ │ ├── stake.png │ │ │ │ ├── timestamp to date(new).png │ │ │ │ ├── timestamp to date.png │ │ │ │ ├── user multiplier.png │ │ │ │ ├── wei convert.png │ │ │ │ └── weights lockclaim.png │ │ ├── Morpheus Capital Providers Contract Guide │ │ │ ├── approval.png │ │ │ ├── deposit.png │ │ │ ├── deposited.png │ │ │ ├── rewards.png │ │ │ └── withdraw.png │ │ ├── Morpheus Lumerin Model │ │ │ ├── figure1.png │ │ │ ├── figure2.png │ │ │ └── figure3.png │ │ ├── Morpheus Node │ │ │ ├── Architecture.png │ │ │ ├── Session Flow.png │ │ │ └── Smart Contracts Structure.png │ │ ├── Phased AMM Deployment │ │ │ ├── 1.png │ │ │ ├── 2-.png │ │ │ ├── 3.png │ │ │ ├── 4.png │ │ │ ├── range1-.png │ │ │ └── range2.png │ │ ├── README │ │ │ ├── Data agent.png │ │ │ ├── agent_clarify3.png │ │ │ ├── successful_swap2.png │ │ │ └── wallet_integration1.png │ │ └── Uniswap Guide │ │ │ ├── add increase.png │ │ │ ├── add token.png │ │ │ ├── approve increase.png │ │ │ ├── approve weth.png │ │ │ ├── approve1.png │ │ │ ├── approve2.png │ │ │ ├── approve3.png │ │ │ ├── arb.png │ │ │ ├── change chain.png │ │ │ ├── chose token.png │ │ │ ├── confirm increase.png │ │ │ ├── connect1.png │ │ │ ├── connect2.png │ │ │ ├── deposit amounts.png │ │ │ ├── fee tier.png │ │ │ ├── import morr.png │ │ │ ├── increase liquidity.png │ │ │ ├── mint.png │ │ │ ├── new position.png │ │ │ ├── percentage.png │ │ │ ├── positions.png │ │ │ ├── price range.png │ │ │ ├── remove liquidity.png │ │ │ ├── select mor.png │ │ │ ├── select tokens.png │ │ │ ├── select weth.png │ │ │ ├── success increase.png │ │ │ ├── swap success.png │ │ │ ├── swap successs.png │ │ │ ├── swap weth mor.png │ │ │ ├── swap.png │ │ │ └── warning.png │ ├── French │ │ └── Installation Guide.jpeg │ ├── German │ │ ├── Meme for TCM German.jpeg │ │ └── Whitepaper │ │ │ ├── 1 for German WP.png │ │ │ ├── 2 for German WP.png │ │ │ ├── 3 for German WP.png │ │ │ ├── 4 for German WP.png │ │ │ ├── 5 for German WP.png │ │ │ ├── 6 for German WP.png │ │ │ ├── 7 for German WP.png │ │ │ ├── 8 for German WP.png │ │ │ └── 9 for German WP.png │ ├── Indonesian │ │ └── Whitepaper │ │ │ ├── Circulation.png │ │ │ ├── Diagram_Pengguna.png │ │ │ ├── Distribute.png │ │ │ ├── Emission.png │ │ │ ├── Emitted.png │ │ │ ├── MorpheusNetwork.png │ │ │ ├── Supply_curve.png │ │ │ └── Year.png │ ├── Polish │ │ └── Whitepaper │ │ │ ├── 001 Morpheus Logo.png │ │ │ ├── 01 Morpheus Whitepaper Polish.png │ │ │ ├── 02 Morpheus Whitepaper Polish.png │ │ │ ├── 03 Morpheus Whitepaper Polish.png │ │ │ ├── 04 Morpheus Whitepaper Polish.png │ │ │ ├── 05 Morpheus Whitepaper Polish.png │ │ │ ├── 06 Morpheus Whitepaper Polish.png │ │ │ ├── 07 Morpheus Whitepaper Polish.png │ │ │ └── 08 Morpheus Whitepaper Polish.png │ ├── Russian │ │ └── Meme for TCM RU.jpg │ ├── Ukrainian │ │ └── Meme for TCM UA.jpg │ └── Urdu │ │ ├── Whitepaper │ │ ├── 5050version3.jpg │ │ ├── ComputeContractImage2.png │ │ ├── MOR25ScenarioV9.jpg │ │ ├── MOREmissionSchedule.jpg │ │ ├── MOREmissionsCurve2.jpg │ │ ├── MORSupplyCurve20231019.jpg │ │ ├── MaxMORScenario25.jpg │ │ ├── MorpheusNetworkDiagram.jpg │ │ └── UpdatedDiagram2UserFlow.jpg │ │ └── Yellowpaper │ │ ├── 2023-10-15_13-28-08_page-0001.jpg │ │ ├── Diagram1ofETHDontator_page-0001.jpg │ │ ├── Diagram3ForETHGiven_page-0001.jpg │ │ ├── Diagram_page-0001.jpg │ │ ├── ETHGivenDiagram2_page-0001.jpg │ │ ├── MORForCompute2_page-0001.jpg │ │ ├── MORForCompute_page-0001.jpg │ │ ├── MorpheusDecentralized_page-0001.jpg │ │ ├── MorpheusLocalDiagram_page-0001.jpg │ │ ├── MorpheusP2PDiagram_page-0001.jpg │ │ ├── User_Contributor_Diagram_page-0001.jpg │ │ ├── mordist_page-0001.jpg │ │ ├── new-buckets_page-0001.jpg │ │ └── ticketing_page-0001.jpg ├── MOR network diagram.png └── logos │ ├── Logo Files.md │ ├── MOR gradient logo.png │ ├── Morpheus Brand Kit | Graphics Guide.md │ ├── Morpheus Ecosystem Logo.md │ ├── Morpheus Logo - White.svg │ └── Video logos.md ├── LICENSE ├── README.md ├── Security Audit Reports ├── Bug Bounty Program.md ├── Builders │ └── Morpheus BuildersV2 Audit Report | Trust Security.pdf ├── Compute │ ├── Morpheus Lumerin Audit Report 1 | Renascence.pdf │ ├── Morpheus Lumerin Audit Report 2 | Renascence.pdf │ └── Morpheus Lumerin Audit Report 3 | Renascence.pdf ├── Distribution Contract │ ├── Distribution V1 Audit | Community.md │ ├── Distribution V1 Public Bug Bounty | Code Hawks.md │ ├── Distribution V2 Audit | Renascence.pdf │ ├── Distribution V3 (Capital Staking) Audit | Renascence.pdf │ ├── Distribution V3 (Code Staking) Audit | Renascence.pdf │ ├── Distribution V4 (Claim Lock) Audit | Renascence.pdf │ └── Distribution V5 (Referral Program) Audit | Renascence.pdf ├── L2 Token Receiver V2 │ ├── L2TokenReceiverV2 Audit (Final) | Renascence.pdf │ └── L2TokenReceiverV2 Audit (Initial) | Renascence.pdf ├── MOR OFT Token │ ├── MOR Dynamic Minter Security Audit (Wormhole) | Renascence.pdf │ └── MOR Token Contract | OpenZepellin.pdf └── MOR20 Contracts | Renascence.pdf └── Smart Contracts ├── Distribution.md ├── L1Sender.md ├── L2MessageReceiver.md ├── L2TokenReceiverV2.md ├── LinearDistributionIntervalDecrease.md ├── MOROFT.md └── readme.md /!KEYDOCS README FIRST!/Capital Providers, MOR20, TCM/MOR20 A Standard for Recurring Protocol Payments and Payouts in Web3.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/!KEYDOCS README FIRST!/Capital Providers, MOR20, TCM/MOR20 A Standard for Recurring Protocol Payments and Payouts in Web3.pdf -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/Code Providers/Coder Guide.md: -------------------------------------------------------------------------------- 1 | # Coder Guide: 2 | A lot of developers are joining the Morpheus community. Welcome to you all! 3 | You are a key part of the Morpheus community and there are lots of rewards to be earned for your hard work. 4 | In Morpheus 24% of all MOR emissions go to Coders and will for the next 16 years as part of all the 42 Million MOR emitted. 5 | 6 | ## Guide: 7 | To get started here is a short list of resources and some of the best ways to get involved and add code to improve Morpheus. 8 | 9 | ## TL;DR 10 | - Review Morpheus Request for Comment (MRC) list for high level understanding. 11 | - Review list of GitHub Issues for specifics. 12 | - Review Best Practices for tips on how to get your code added. 13 | - Review Code Contributor Guide to Earning Weights & Their Implied Value. 14 | - Review Reference Implementations List. 15 | - Submit a Pull Request that adds value to Morpheus. 16 | 17 | ## Morpheus Request For Comments: 18 | Includes a list of all the papers / proposals related to improving, implementing Morpheus, Smart Agents, Tokenomics, & the Techno Capital Machine. 19 | 20 | https://github.com/MorpheusAIs/MRC/blob/main/README.md 21 | 22 | ## Check the list of Issue On GitHub For Details Of Ongoing Work 23 | Includes a list of active issues reported on the Morpheus GitHub. 24 | 25 | https://github.com/MorpheusAIs 26 | 27 | ## Best Practices for Contributing Code 28 | The step by step details of how to Contribute Code, increase those odds of having your Pull Request merged. 29 | 30 | https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Code%20Providers/Code%20Contributor%20Best%20Practices.md 31 | 32 | ## Code Contributor Guide to Earning Weights & Their Implied Value 33 | The detailed description of the implied value per weight which is updated each month. 34 | 35 | https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Code%20Providers/Code%20Contributor%20Weights%20Guide.md 36 | 37 | ## Reference Implementations List 38 | Existing and new Morpheus implementations 39 | 40 | https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Code%20Providers/Morpheus%20Reference%20Implementations%20(MRC).md 41 | 42 | ## Code Contributor Table To Include In Pull Requests 43 | Include an update to the Code Contributor table on GitHub with your Code Contributions with your weights request. 44 | 45 | https://github.com/MorpheusAIs/Docs/tree/main/Contributions 46 | 47 | If a developer is looking for committees, and RFPs they are looking at the wrong project. The nature of Morpheus is [Atomic Governance](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Capital%20Providers%2C%20MOR20%2C%20TCM/Techno%20Capital%20Machine%20(TCM).md#atomic-governance). That means experts build what they want and GitHub maintainers act as judges to merge if its in the platform or users decide to use the Smart Agent in an open marketplace. Coders here compete. No guarantees anyone will use the Code until its released. 48 | -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/Code Providers/Morpheus Reference Implementations (MRI).md: -------------------------------------------------------------------------------- 1 | # Morpheus Reference Implementations (MRIs) 2 | 3 | ![Morpheus Reference Implementations 2024 03 03](https://github.com/MorpheusAIs/Docs/assets/1563345/197ca0eb-d523-409c-a53c-cc844457c56a) 4 | 5 | ## List of Existing Morpheus Reference Implementations 6 | - **MRI Number 1:** [Smart Contracts on Ethereum / Arbitrum](https://github.com/MorpheusAIs/SmartContracts) 7 | - **Maintainer's Discord Handle:** smartagents 8 | - **Maintainer's GitHub Handle:** [DavidAJohnston](https://github.com/DavidAJohnston) 9 | 10 | - **MRI Number 2:** [Smart Agents Tools & Examples](https://github.com/MorpheusAIs/moragents) 11 | - **Maintainer's Discord Handle:** lachsbagel 12 | - **Maintainer's GitHub Handle:** [LachsBagel](https://github.com/LachsBagel) 13 | 14 | - **MRI Number 3:** [Morpheus Local Install Desktop / Mobile](https://github.com/MorpheusAIs/Morpheus) 15 | - **Maintainer's Discord Handle:** scott_b_ 16 | - **Maintainer's GitHub Handle:** [betterbrand](https://github.com/betterbrand) 17 | 18 | - **MRI Number 4**: [TCM / MOR20 Token Standard for Fair Launches](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md) 19 | - **Maintainer's Discord Handle:** storm.father 20 | - **Maintainer's GitHub Handle:** [EnergyHound](https://github.com/EnergyHound) 21 | 22 | - **MRI Number 5**: [Protection Fund](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Protection%20Fund%20Details.md) 23 | - **Maintainer's Discord Handle:** storm.father 24 | - **Maintainer's GitHub Handle:** [EnergyHound](https://github.com/EnergyHound) 25 | 26 | - **MRI Number 6:** [Capital Proofs Extended beyond Lido stETH](https://github.com/MorpheusAIs/MRC/blob/main/IMPLEMENTED/MRC15.md) 27 | - **Maintainer's Discord Handle:** smartagents 28 | - **Maintainer's GitHub Handle:** [DavidAJohnston](https://github.com/DavidAJohnston) 29 | 30 | - **MRI Number 7:** [Compute Proofs Morpheus / Lumerin](https://github.com/MorpheusAIs/Morpheus-Lumerin-Node) 31 | - **Maintainer's Discord Handle:** rcondron 32 | - **Maintainer's GitHub Handle:** [rcondron](https://github.com/rcondron) 33 | 34 | - **MRI Number 8:** [Code Proofs & Dashboards](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Coder%20Guide.md) 35 | - **Maintainer's Discord Handle:** scott_b_ 36 | - **Maintainer's GitHub Handle:** [betterbrand](https://github.com/betterbrand) 37 | 38 | - **MRI Number 9:** [Frontend Proofs & Examples](https://github.com/MorpheusAIs/MRC/blob/main/IN%20PROGRESS/MRC08.md) 39 | - **Maintainer's Discord Handle:** erikvoorhees 40 | - **Maintainer's GitHub Handle:** [ErikVoorhees](https://github.com/ErikVoorhees) 41 | 42 | - **MRI Number 10:** [Interoperability](https://github.com/MorpheusAIs/MRC/blob/main/IMPLEMENTED/MRC16.md) 43 | - **Maintainer's Discord Handle:** urklan / smartagents 44 | - **Maintainer's GitHub Handle:** [RuslanProgrammer](https://github.com/RuslanProgrammer) / [DavidAJohnston](https://github.com/DavidAJohnston) 45 | -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/Compute Providers/Compute Node/Compute Node FAQ.md: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/Compute Providers/Compute Node/Model_ID Registry.md: -------------------------------------------------------------------------------- 1 | # Model ID Registry 2 | 3 | ## Introduction 4 | Within the Mopheus Compute Node, users can add new models to the marketplace. For the simplicity of consumers, some model_IDs have been pre-seeded into the marketplace. Consumers have the option of initiating sessions with providers by: 5 | - `Bid_ID` (meaning a specific provider/model pair), or by 6 | - `Model_ID` (all providers hosting a specific model). 7 | 8 | Ideally, all providers hosting the same model utilize the same model_ID for that model, allowing users to match with the best provider for their session. 9 | 10 | When opening sessions by Model_ID (expected common path, see basic instructions [here](/!KEYDOCS%20README%20FIRST!/Compute%20Providers/Compute%20Node/Intro%20to%20Morpheus%20Compute%20Node.md#provider-setup)), the value of the system increases exponentially when providers use standard Model_IDs 11 | #### Value to users: 12 | User matches with the best provider, utilizing ranking of a larger subset of providers. 13 | #### Value to providers: 14 | Provider has higher liklihood to match with a consumer, entering a larger pool of demand. 15 | 16 | > [!NOTE] 17 | > If you are a provider and using one of the below models, **DO NOT** create a new model within the proxy router. Use the Model_ID below for your models-config.json file 18 | > 19 | > If you are a provider and using a model that is not on the list below, edit this file and submit a pull request to faciliate larger scale use 20 | 21 | ## Standard Marketplace Models 22 | 23 | ### Meta Llama Models 24 | | Model Name| Filename | URL | Model ID | 25 | | :---------------- | :----------: | :----------: | :----: | 26 | | Llama-3.1-405B | Meta-Llama-3.1-405B-Instruct-Q4_K_M | [https://huggingface.co/ThomasBaruzier/Meta-Llama-3.1-405B-Instruct-GGUF/tree/main/Meta-Llama-3.1-405B-Instruct-Q4_K_M] | 0x01a95edd655e15a0043b2a2329258e165660794f98f63c2b03842c0a98f6d74c | 27 | | Llama-3.1-70B | Meta-Llama-3.1-70B-Instuct.Q5_K_M.gguf | [https://huggingface.co/MaziyarPanahi/Meta-Llama-3.1-70B-Instruct-GGUF/resolve/main/Meta-Llama-3.1-70B-Instruct.Q5_K_M.gguf] | 0xcb6bd9a66175ab6d1a96c6acf33ac70e8666e6dcd71dd7be6903f3c1ab80fd7d | 28 | | Llama-3.1-8B | Meta-Llama-3.1-8B-Instruct-Q8_0.gguf | [https://huggingface.co/bartowski/Meta-Llama-3.1-8B-Instruct-GGUF/resolve/main/Meta-Llama-3.1-8B-Instruct-Q8_0.gguf] | 0x85686c6f53cc5d0b01820bd802832633d89f35cbcee3f8e1b82df2f27d982ef8 | 29 | 30 | ### NousReseach Models 31 | | Model Name| Filename | URL | Model ID | 32 | | :---------------- | :----------: | :----------: | :----: | 33 | | Hermes-3-Llama-3.1-70B | Hermes-3-Llama-3.1-70B.Q5_K_M.gguf | [https://huggingface.co/NousResearch/Hermes-3-Llama-3.1-70B-GGUF/resolve/main/Hermes-3-Llama-3.1-70B.Q5_K_M.gguf] | 0xc823a1b04ea113fffa28b3663f12976fda0285e2a3df90303a3bd7488e7fdeed | 34 | | Hermes-3-Llama-3.1-8B | Hermes-3-Llama-3.1-8B.Q8_0.gguf | [https://huggingface.co/NousResearch/Hermes-3-Llama-3.1-8B-GGUF/resolve/main/Hermes-3-Llama-3.1-8B.Q8_0.gguf] | 0x790d53e2386b9c6a8a20d133f20e0e9f30c3bbcd58443866adbdde242bdb1b8c | 35 | | Hermes-2-Pro-Llama-3-8B | Hermes-2-Pro-Llama-3-Instruct-Merged-DPO-Q8_0.gguf | [https://huggingface.co/NousResearch/Hermes-2-Theta-Llama-3-8B-GGUF/resolve/main/Hermes-2-Pro-Llama-3-Instruct-Merged-DPO-Q8_0.gguf] | 0xfc91411c689d11319171c2e29f9d8533cd87348b6c5d15016c230df266af3d0a | 36 | 37 | ### Qwen Models 38 | | Model Name| Filename | URL | Model ID | 39 | | :---------------- | :----------: | :----------: | :----: | 40 | | Qwen2.5-Coder-32B | qwen2.5-coder-32b-instruct-q8_0.gguf | [https://huggingface.co/Qwen/Qwen2.5-Coder-32B-Instruct-GGUF/resolve/main/qwen2.5-coder-32b-instruct-q8_0.gguf] | 0xb5edae401693f2aaa83908ef9d65d4b89d889eb0bace51a5ee3d1f92bc56408f | 41 | | Qwen2.5-14B-Instruct | qwen2.5-14b-instruct-q8_0 | [https://huggingface.co/Qwen/Qwen2.5-14B-Instruct-GGUF/tree/main] | 0x1a2b8bf57423a72a9aff8fb4adebaf17b8ef2c1370be20e22f82bf24fa8175bb | 42 | | Qwen2.5-72B | qwen2.5-72b-instruct-q8_0 | [https://huggingface.co/Qwen/Qwen2.5-72B-Instruct-GGUF/tree/main] | 0x1a2b8bf57423a72a9aff8fb4adebaf17b8ef2c1370be20e22f82bf24fa8175bb | 43 | 44 | ### CognitiveComputations Models 45 | 46 | | Model Name| Filename | URL | Model ID | 47 | | :---------------- | :----------: | :----------: | :----: | 48 | | Dolphin-2.94-Llama3.1-8B | dolphin-2.9.4-llama3.1-8b-Q8_0.gguf | [https://huggingface.co/cognitivecomputations/dolphin-2.9.4-llama3.1-8b-gguf/resolve/main/dolphin-2.9.4-llama3.1-8b-Q8_0.gguf] | 0xdfa6c1a4e4d3c56fb985de46debd9d4b6fb8e624dd770f0fc1e3feb2b7a26d5b | 49 | 50 | -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/Compute Providers/Compute Node/Subnets.md: -------------------------------------------------------------------------------- 1 | # Defining a Morpheus Compute "Subnet" 2 | - A Morpheus Compute Subnet is a specific Compute Provider who is offering "Inference" (LLM & Diffusion Models) to users of Morpheus. 3 | - A Subnet runs a Node on the network and utilizes the Morpheus / Lumerin Router to match with users requesting Inference. 4 | - MOR is required to Stake towards each Subnets for them to increase their "rank" with the Router and odds of getting matched to a user. 5 | - MOR is rewarded to Subnets based on the "sessions" they do with users, the longer the sessions remain open the better their "reputation". 6 | - Subnets may open the ability for MOR holders to Stake toward their Subnets and share the rewards (still under development). 7 | - Morpheus is agnostic to where Subnets serve the Inference from, so users of Akash and other GPU networks are welcome to become providers. 8 | 9 | ## Technical Documentation on Ranking 10 | https://docs.google.com/document/d/1jQPcGcjpO-vu9PTiMKyEqXOwRyuE_gzmQq56irXd3Zc/edit?usp=sharing 11 | 12 | ## MOR Staking Requirement For Subnets To Earn MOR Emissions From The Protocol 13 | - A certain level of minimum Staking of MOR will prevent bad actors from hurting the Morpheus Inference users with bad sessions & other attacks. 14 | - This brings up the question of "how much economic alignment with Morpheus" is required to block most bad actors. 15 | - An alaysis of existing ETH Staking requirements of 32 ETH per validator would suggest around 6,400 MOR presuming 0.005 ETH per MOR. 16 | - Though the risks around an ETH validator today are perhaps less than that of an earlier stage project such as Morpheus. 17 | - With this in mind 10,000 MOR seems like an appropriate level to require. 18 | - With over 1,000,000 MOR claimed and "in circulation" that enables over 100+ potential Subnets. 19 | 20 | **Clarifying Notes** 21 | - This requirement should only apply to earning new MOR emissions from the protocol. 22 | - Anyone is free to set a direct session with a Compute Provider and pay MOR directly. 23 | - Also each Subnet operator will not be required to directly own 10,000 MOR, they can instead borrow it from users via Delegration. 24 | - Subnets can Stake additional MOR beyond the minimum in order to increase their ranking in the Morpheus Router. 25 | 26 | ## There Will Also Be Builder Subnets (Under Development) 27 | -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/FAQs & Guides/Application Builders FAQ.md: -------------------------------------------------------------------------------- 1 | # Frequently Asked Questions about Application Builders 2 | 3 | ### Who are Morpheus application builders? 4 | They are developers or teams behind end-user applications (smart agents, dashboards, frontends, tools, etc.) at various stages of development, which are integrated with Morpheus and serve the community's needs. 5 | 6 | ### What is the purpose of rewards for builders? 7 | The rewards for builders are designed to incentivize developers of applications by allowing users to stake their MOR tokens in favor of specific projects. 8 | 9 | ### What is the difference between coder rewards and builder rewards? 10 | Any contribution to the Morpheus codebase is related to coder rewards, while third-party apps are eligible for builder rewards. 11 | 12 | ### Who is eligible for builder rewards? 13 | Any individual or project can apply for builder rewards. It's an open market, and users are incentivized to stake MOR towards projects that bring the most value. 14 | 15 | ### Are there any requirements for projects? 16 | There are no requirements. 17 | 18 | ### How to get builder rewards? 19 | Builders will need to register their addresses in the decentralized registry along with the desired stake duration. After that, users can stake MOR to this address and direct MOR emissions toward builders. 20 | 21 | ### How is the amount of rewards for builders determined? 22 | Builders share daily MOR emissions proportionally to the amount of MOR staked for them and the Power Factor multiplier they receive from staking. 23 | 24 | ### What happens to the MOR accumulated as builder rewards? 25 | To be determined. Proposals that this should go towards builders generating Morpheus protocol fees. 26 | 27 | ### If a builder stakes their MOR rewards, will they be eligible for the daily Morpheus compute share? 28 | No. The MOR token has to be used for one specific function at a time. 29 | 30 | ### Are users' tokens locked when they stake them towards a project? 31 | No, users can withdraw their tokens at any time. 32 | 33 | ### If a user stakes their MOR towards a builder, will they be eligible for the daily Morpheus compute share? 34 | No, users can only choose one option for staking their MOR tokens. 35 | 36 | ### What are the benefits for users who stake? 37 | It’s up to the builders to decide how to incentivize their users to stake MOR. 38 | 39 | ### Does the project have access to the MOR staked by users? 40 | No, staked MOR will be stored in Morpheus' audited contract. 41 | 42 | ### How will users learn about the projects? 43 | The idea is to have third-party dashboards where builders can list their applications. There will also be a discussion channel in Discord. There are also community websites such as www.mor.builders which display some of the community projects. 44 | 45 | ### When are the builder rewards expected to launch? 46 | Q3 2024 47 | 48 | ### I would like more detailed information about the rewards. 49 | Please refer to [MRC 41](https://github.com/MorpheusAIs/MRC/blob/main/PENDING/MRC41.md). 50 | 51 | ### I didn't find an answer to my question. 52 | Please seek community help in the Discord [#app-builders](https://discord.com/channels/1151741790408429580/1167520940297551913) channel. 53 | -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/FAQs & Guides/Code Providers FAQ.md: -------------------------------------------------------------------------------- 1 | # Frequently Asked Questions about Code Providers 2 | 3 | ### What do code providers do? 4 | Code providers contribute to Morpheus code base for ongoing development, upgrades and improvements. 5 | 6 | ### How can I get involved with Morpheus as a code provider? 7 | An onboarding process is described in the [Coder Guide](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Code%20Providers/Coder%20Guide.md) 8 | 9 | ### What are the requirements to code contributors? 10 | There are [Code Contributor Best Practices](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Code%20Providers/Code%20Contributor%20Best%20Practices.md) on GitHub. 11 | 12 | ### How do code providers get rewarded? 13 | They get MOR emissions depending on their contributed weights vs the total amount of weights contributed. 14 | 15 | ### What are the weights? 16 | Weight is the unit that represents contribution value. Weights concept explained [here.](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Code%20Providers/Code%20Contributor%20Weights%20Guide.md) 17 | 18 | ### Can I be paid in USD or stablecoins? 19 | No, code providers are rewarded only in MOR. 20 | 21 | ### How do I get in touch with other builders for collaborations? 22 | Discord server Accelerator Corner is your go to ⁠=> https://discord.gg/morpheusai 23 | 24 | ### Where can I see a task list? 25 | There is no task list available. Developers build what they want based on their experience and belief in its value for Morpheus. GitHub maintainers act as judges to merge contributors' work. Coders here compete, but there are no guarantees that anyone will use the code until it's released. 26 | 27 | ### Are there other ways to get involved? 28 | You can contribute by submitting a proposal as Morpheus Request for Comments (MRC). Explore the guidance [here](https://github.com/MorpheusAIs/MRC/blob/main/MRC00.md) 29 | 30 | ### Where can I get support and ask questions? 31 | Community members would love to assist you in [**#code-provider**](https://discord.com/channels/1151741790408429580/1167520984849469530) discord channel. 32 | 33 | ### If you did not find the answer to your question, you can add it through this [form.](https://forms.gle/6yt5ps3kAfUfkF4N8) 34 | 35 | > [!WARNING] 36 | > Beware of scams, anyone who message you with proposal to help is likely scammer. 37 | -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/FAQs & Guides/Guides/README_MACOS_DEV_BUILD.md: -------------------------------------------------------------------------------- 1 | ## For Developers 2 | 3 | This README will guide you on building a Docker container for agent execution as well as a desktop UI app. 4 | You may instead simply download the [pre-built app](README.md) 5 | 6 | #### macOS 7 | 1. Ensure you have Python, Pip, [Docker Desktop](https://www.docker.com/products/docker-desktop/), and Git installed. Note: please install python version 3.10.0+, older versions will produce outdated versions of tkinter when running the requirements install. 8 | 9 | 10 | 2. Clone Repo 11 | ```shell 12 | $ git clone https://github.com/LachsBagel/moragents.git 13 | $ cd moragents 14 | ``` 15 | 16 | 3. Build Docker Image for Local Agent Execution 17 | 18 | ```shell 19 | For ARM (M1, M2, M3) 20 | $ docker build -t morpheus/price_fetcher_agent -f agents/morpheus_price_agent/agent/Dockerfile-apple agents/morpheus_price_agent/agent 21 | 22 | For Intel (x86_64) 23 | $ docker build -t morpheus/price_fetcher_agent -f agents/morpheus_price_agent/agent/Dockerfile agents/morpheus_price_agent/agent 24 | ``` 25 | 26 | 27 | 4. Install Deps for UI, Recommended to use virtualenv 28 | ```shell 29 | $ python3 -m venv .venv 30 | $ . .venv/bin/activate 31 | $ pip install -r requirements.txt 32 | ``` 33 | 34 | 5. Build App for Local Installation 35 | ```shell 36 | $ pyinstaller --windowed --runtime-hook runtime_hook.py --name="MORagents" --icon="moragents.icns" main.py 37 | ``` 38 | # If you have issues, try 39 | python -m PyInstaller --windowed --runtime-hook runtime_hook.py --name="MORagents" --icon="moragents.icns" main.py 40 | 41 | 6. Install Application 42 | ```shell 43 | $ cp dist/MORagents.app /Applications 44 | ``` 45 | 46 | 7. Open the ```MORagents``` app on your Mac, Docker needs to be running before opening MORagents 47 | 48 | -- 49 | ### Signing, Notarization, and Stapling for Distribution 50 | Instructions are [here](Packaging_Instructions_macOS.md). 51 | 52 | -- 53 | 54 | 55 | Windows build instructions can be found [here](README_WINDOWS_DEV_BUILD.md) 56 | -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/FAQs & Guides/Guides/README_WINDOWS_DEV_BUILD.md: -------------------------------------------------------------------------------- 1 | ## For Developers 2 | 3 | This README will guide you on building a Docker container for agent execution as well as a desktop UI app. 4 | You may instead simply download the [pre-built app](README.md) 5 | 6 | #### Windows 7 | 1. Ensure you have Python, Pip, [Docker Desktop](https://www.docker.com/products/docker-desktop/), and Git installed on your Windows machine. Note: please install python version 3.10.0+, older versions will produce outdated versions of tkinter when running the requirements install. 8 | 9 | 2. Clone the repository using Command Prompt or PowerShell: 10 | ```shell 11 | > git clone https://github.com/LachsBagel/moragents.git 12 | > cd moragents 13 | ``` 14 | 15 | 3. Build the Docker Image for Local Agent Execution: 16 | ```shell 17 | > docker build -t morpheus/price_fetcher_agent -f agents/morpheus_price_agent/agent/Dockerfile agents/morpheus_price_agent/agent 18 | ``` 19 | 20 | If we have run this command before, run this to clear the old docker image. 21 | ```shell 22 | docker rmi morpheus/price_fetcher_agent 23 | ``` 24 | 25 | 4. Install Deps for UI, Recommended to use virtualenv 26 | ```shell 27 | > python -m venv .venv 28 | > Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass 29 | > .\.venv\Scripts\Activate.ps1 30 | > pip install -r requirements.txt 31 | ``` 32 | 33 | 6. Build App for Local Installation 34 | ```shell 35 | pyinstaller --runtime-hook runtime_hook_windows.py --name="MORagentsWindows" --icon="moragents.ico" main.py 36 | ``` 37 | There is a known and common issue where pyinstaller will trigger Windows Defender (see [here](https://stackoverflow.com/questions/54733909/windows-defender-alert-users-from-my-pyinstaller-exe) for more details). If there is a security warning, perform the following: 38 | 39 | - Open Windows Security: Go to Start > Settings > Update & Security > Windows Security > Virus & threat protection. 40 | - Manage Settings: Under Virus & threat protection settings, select "Manage settings." 41 | - Add or remove exclusions: Scroll down to "Exclusions" and select "Add or remove exclusions." 42 | - Add an exclusion: Select "Add an exclusion" and choose the folder where your project is located. 43 | 44 | More details located [here](https://support.microsoft.com/en-us/windows/add-an-exclusion-to-windows-security-811816c0-4dfd-af4a-47e4-c301afe13b26) 45 | 46 | 7. The compiled executable will be located in the dist folder. You can create a shortcut to the MORagents.exe file for easy access. 47 | 8. Double-click the MORagents.exe file to open the MORagents app on your Windows machine. Make sure Docker is running before opening MORagents. 48 | 49 | --- 50 | 51 | MacOS build instructions can be found [here](README_MACOS_DEV_BUILD.md) 52 | -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/FAQs & Guides/MOR Rewards Staking FAQ.md: -------------------------------------------------------------------------------- 1 | # MOR Rewards Staking (MRS) FAQ 2 | 3 | ### Why does Morpheus need rewards staking? 4 | The MRS has been introduced as a community initiative to close the negative feedback loop at the capital providers bucket and separate the real contributors from short-term opportunists. 5 | 6 | ### How does MOR Rewards Staking (MRS) work? 7 | In simple terms, Morpheus contributors can stake MOR reward claims for a future date. In exchange, contributors get a "Power Factor" or just "Power" that amplifies their MOR rewards. 8 | 9 | ### How is the Power Factor determined? 10 | The Power Factor mirrors the dilution rate due to daily emissions contributors experience while staking the MOR rewards. The equation can be found in the [MRC42](https://github.com/antonbosss/MRC/blob/main/IN%20PROGRESS/MRC42.md#the-time-power-factor-shortened-power). 11 | 12 | ### What is the maximum Power Factor multiplier? 13 | The maximum Power Factor multiplier is 10.7x if staked for 6 years. 14 | 15 | ### For how long can I stake my rewards? 16 | There are no limits, but Power factor starts to grow from 1x after six months of staking and reach its maximum of 10.7x if rewards are staked for six years. 17 | While there are no limits, the reasonable range is from six months to six years. 18 | 19 | ### Can I stake MOR that I already have in my wallet? 20 | No, only future MOR reward claims can participate in this staking. 21 | 22 | ### Who is eligible for rewards staking? 23 | All four types of Morpheus contributions (Code, Capital, Compute, or Builders) can participate in MRS. Capital and Code will go live first, with Compute and Builder rewards staking following afterward. 24 | 25 | ### I'm a contributor, do I have to stake my rewards? 26 | Staking rewards is not mandatory, but without it, you will not gain Power Factor. 27 | 28 | ### Can I decrease or increase the staking period? 29 | No, the MOR staking period can only be increased. 30 | 31 | ### Can I withdraw rewards earlier? 32 | The user is not able to withdraw their MOR rewards until the end of the MRS period. 33 | 34 | ### MRC states that every transaction will recalculate Power. I’d like to know more. 35 | Not every transaction will trigger recalculation, but only transactions with the Distribution contract, due to the technical specifics of the contract. 36 | For example, depositing or withdrawing stETH for capital providers, or increasing or decreasing weights for code contributors. 37 | 38 | ### If I want to buy or sell MOR from the wallet where rewards are staked, will this trigger recalculation? 39 | No, because these transactions do not call functions of the Distribution contract. 40 | 41 | ### Do staking rewards affect MOR emissions? 42 | No, MRS has no impact on daily MOR emissions, but due to staking, fewer MOR tokens will flow into circulation. 43 | 44 | ### What should I do to stake my reward? 45 | You will be able to do that via the dashboard or directly through the smart contract. If you are a code provider, you can also submit the staking time with your contribution submission. 46 | 47 | ### I'm a capital contributor. If I stake my reward, will I be able to withdraw stETH? 48 | Nothing changes the ability of capital contributors to withdraw their stETH (beyond the normal 7 days), only the claiming of MOR rewards is delayed. However, when you withdraw stETH, you will no longer get rewards. 49 | 50 | ### I'd like to have more information about MRS. 51 | You are welcome to read the full version of the proposal [MRC42](https://github.com/MorpheusAIs/MRC/blob/main/IN%20PROGRESS/MRC42.md). 52 | 53 | ### I have a question I didn’t find the answer to. 54 | Please ask it in the Discord in the [#capital-providers](https://discord.com/channels/1151741790408429580/1167520881908666569) or [#code-providers](https://discord.com/channels/1151741790408429580/1167520984849469530) channel. 55 | 56 | -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/MOR - Network For Powering Smart Agents.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/!KEYDOCS README FIRST!/MOR - Network For Powering Smart Agents.pdf -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/Morpheus Fundamentals/MOR Burn Function.md: -------------------------------------------------------------------------------- 1 | # MOR Burn Function 2 | The Morpheus White paper proposed a burning function for MOR in order to increase scarcity. 3 | Though the details of how the burning function were left for future implementation. 4 | 5 | ## Now in MRC 43 the Burn Address has been added to play a part in the function of the Protocol Owned Liquidity. 6 | See link for details: https://github.com/MorpheusAIs/MRC/blob/main/IN%20PROGRESS/MRC43.md 7 | 8 | ## Burning & Tail Emissions Section from MRC 43 9 | - This approach will be the basis for implementing the Burn Function described in the white paper. 10 | - The 50% of the MOR left after Protocol owned Liquidity Generation Event in the Multisignature account will be locked for 16 years. In order to function as the basis for [the #2 epochs Tail Emissions](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/WhitePaper.md#tail-emissions-of-mor). 11 | - The other 50% of the MOR left after Protocol owned Liquidity Generation Event will be sent to a permanent burn address and destroyed forever. 12 | 13 | ## Burn and Epoch 2 Lock Addresses 14 | - **Burn address:** [0x000000000000000000000000000000000000dead](https://arbiscan.io/token/0x092baadb7def4c3981454dd9c0a0d7ff07bcfc86?a=0x000000000000000000000000000000000000dead) 15 | This is an address commonly used by Ethereum projects for the purpose of burning tokens. 16 | 17 | - **Epoch 2 tail emissions lock address:** [0xb1972e86b3380fd69dcb395f98d39fbf1a5f305a](https://arbiscan.io/token/0x092baadb7def4c3981454dd9c0a0d7ff07bcfc86?a=0xb1972e86b3380fd69dcb395f98d39fbf1a5f305a) 18 | The address manages by multisignature account, but will be replaced by lock smart contract in the near future. 19 | 20 | ## History 21 | The first MOR purchased for the purpose of Burning were those bought on June 24th 2024 and second set of purchases begun on July 1st 2024. 22 | The Burn address is expected to be used for the first time on July 9th 2024. 23 | 24 | You can track the Protocol Owned Liquidity action on https://morlord.com/ or directly with blockchain explorer https://arbiscan.io/address/0x151c2b49CdEC10B150B2763dF3d1C00D70C90956 25 | -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/Morpheus Fundamentals/MOREconomics.md: -------------------------------------------------------------------------------- 1 | # MOR Economics 2 | ## All Networks Live or Die Based On Their Economic Principles & Values 3 | 4 | Morpheus is one of the first networks since Bitcoin to take a purely free market approach to every single one of its functions. Its economic theory rests on the foundations of individual sovereignty, voluntary markets, & anarcho-capitalism. 5 | 6 | This belief in free markets to self organize has been proven out as Morpheus went from a white paper proposed by anonymous authors in September of 2023, to the first open source Morpheus install in October of 2023, to Smart Contracts for a Fair Launch in February of 2024, to the MOR token going live in May of 2024. 7 | 8 | In the span of just 9 months with no Company, no Team, no Pre-mine, no CEO, and no Foundation, Morpheus created a powerful platform for generative AI applications. Morpheus did this as 100% open source Smart Contracts & Peer to Peer software, built in public & available to all. 9 | 10 | The economic philosophy of Morpheus & the value of a truly Personal AI attracted hundreds of independent coders from around the world to contribute open source software, and thousands of capital providers to contribute yield from their staked Ethereum. In the first 30 days, 100,000 stETH, worth more than $300 million USD, was staked by the community. As the Capital Provider MOR emissions continue for 16 years, this attracts ever more talent & capital as if into a gravity well that becomes stronger as its network effects compound. 11 | 12 | ## Every aspect of the project operates as a competitive free market. 13 | 1. Capital Providers compete to provide Liquidity. 14 | 2. Compute Providers compete to provide Inference. 15 | 3. Coders compete to provide the open source Software. 16 | 4. Builders compete to provide valuable Smart Agents to Users. 17 | 5. Reference implementation maintainers compete for Usage. 18 | 19 | ## Add In Sound Economic Principles of Scarcity & Predictability of Supply 20 | - The competition for a limited supply of 42,000,000 MOR tokens. 21 | - It’s a fair & long term competition, as the MOR are emitted over ~16 years. 22 | - A burning function to make MOR even more scarce. 23 | - A tail emission that goes 256 years, keeping the competition going for centuries. 24 | 25 | ## Add In Technical Utility, Capital & Governance Use Cases 26 | - MOR holders have access to a pro-rata amount of the daily Compute budget. 27 | - MOR holders will Stake their MOR yield toward Builders & earn additional tokens. 28 | - MOR holders will Stake their MOR to direct Coding rewards to improve Morpheus. 29 | 30 | ## Add In The Techno Capital Machine 31 | The liquidity engine of yield provided every day from staked Ethereum isn’t centrally managed by votes or a committee, but rather added directly into Protocol Owned Liquidity. Specifically, 50% of the ETH yield is used to buy MOR from the Uniswap pool. Then, both the purchased MOR & remaining ETH are paired and added to a full-range liquidity position owned by Morpheus, known as the Protocol Owned Liquidity. This design provides a consistent demand for MOR while also deepening liquidity, making it easier for all users to buy or sell MOR tokens at scale. 32 | 33 | ## Unstoppable Progress & Massive Scale 34 | Combined these elements have incentivized a global community of builders to collaborate together at a massive scale that is only accelerating. As Smart Agents serving our individual personal AIs, become the vast majority of economic activity in the coming years, Morpheus will be there serving as the beating heart of Free AI. 35 | -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/Morpheus Fundamentals/Morpheus Freedoms.md: -------------------------------------------------------------------------------- 1 | # Morpheus Is Freedom & Liberty For All 2 | 3 | Thanks to all those in the Morpheus community Staking, Computing, Building & Coding for Freedom. 4 | 5 | ## The following 10 values embody the type of communities, projects & freedom tech Morpheus is built to protect. 6 | 7 | ## Open Source: 8 | The software code underpinning the Morpheus must be freely reviewable, editable & copyable by all. 9 | ## Peer to Peer: 10 | A system which allows for direct connection by all and is free of centralized intermediaries in all their functions. 11 | ## Public Blockchain: 12 | A distributed public immutable ledger / system of record for interactions of the Morpheus members. This can be used as proof that a Morpheus is following its own rules and offers a high level of transparency in the system. 13 | ## Tokenized Ownership: 14 | Setting forth the means of rewarding participants & stake holders in the Morpheus. 15 | ## Permissionless: 16 | No one should be required to ask an authority to use the public features of the Morpheus. 17 | ## Freedom of Access: 18 | No one should have their use of the application blocked or otherwise censored when using a Morpheus. 19 | ## Privacy Preserving: 20 | No one should have to expose their private information to use a Morpheus. 21 | ## Freedom of Choice / Exit: 22 | No one should be forced to continue running software or otherwise participate in a Morpheus if they choose to leave or join another Morpheus. 23 | ## Self Sovereign Identity: 24 | All users have the power to generate their own identities and their consent is required to use those credentials. 25 | ## Freedom of Association: 26 | Members of a Morpheus must be free to practice free association between themselves. 27 | -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/Morpheus Launch Phases.md: -------------------------------------------------------------------------------- 1 | # The 5 phases of Morpheus launch match those of Ethereum - Genesis, Frontier, Homestead, Metropolis & Serenity 2 | 3 | ![image](https://github.com/user-attachments/assets/77feb435-0f0f-43b3-ba3d-a63f0324a339) 4 | 5 | 6 | ## Genesis 7 | **September 2nd 2023 to February 8th 2024** 8 | Morheus whitepaper released, first local install in October 2023. Following successful audits and testnet deployments, smart contracts for the Morpheus (MOR) token and its fair launch were deployed to Ethereum and Arbitrum mainnet on February 7th 2024. 9 | 10 | ## Frontier 11 | The fair launch commenced on February 8th 2024 kicking off the 90 day bootstrapping period. 12 | The Smart Contracts began allocating MOR token emissions for Code, Capital, Compute, and Community from day 1. Tokens become claimable and transferrable on day 91 of the bootstrapping period which is May 8th. 13 | 14 | ## Homestead 15 | Rewards for Compute via Morpheus / Lumerin node go live. 16 | While rewards for Compute contributors began accruing on day 1, they will not be distributed until the Compute Router and other details are developed by the community. 17 | 18 | ## Metropolis 19 | Launch of Smart Agents / End User Applications rewards via MOR staking. 20 | Similarly, rewards for Community (frontend) contributors began accruing on day 1, but will not be distributed until distribution details are developed by the community. 21 | 22 | ## Serenity 23 | Morpheus spreads across many chains & yield types. 24 | As Morpheus is intended to be chain-agnostic, it is worth considering proposals to deploy the MOR token on other chains and provision yield (with eligibility for Capital rewards) from other sources. 25 | 26 | - Examples of cross-chain deployments could entail using Wormhole or LayerZero to move MOR tokens between ETH, ARB, POLY, Solana, and the Cosmos chains. 27 | - Examples of alternative yield sources could include BTC yield from Thorchain or mSOL from Solana. 28 | 29 | These are significant and interrelated projects as adding yield sources necessitates adding the MOR token to other chains in a way where cross-chain messaging is possible. 30 | 31 | --- 32 | 33 | ### History 34 | February 8th 2024 is the 28th Anniversary of "A Declaration of the Independence of Cyberspace" (February 8th 1996). 35 | Seems like a good day to release Decentralized AI into the world. 36 | https://www.eff.org/cyberspace-independence 37 | -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/Morpheus Smart Agent Router.md: -------------------------------------------------------------------------------- 1 | # Morpheus Smart Agent Router 2 | 3 | The Morpheus corrdinator agent is designed to tap other agents on an as needed basis to complete tasks. 4 | 5 | Leveraging the ranking of Smart Agents according to their economic alignment with Moprhues as described in MRC41. 6 | 7 | https://github.com/MorpheusAIs/MRC/blob/main/PENDING/MRC41.md 8 | 9 | ## The MSAR is being developed as part of the MOR Agents repo. 10 | https://github.com/MorpheusAIs/moragents 11 | 12 | Morpheus Reference Implemenation #2 for Smart Agents. 13 | -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/Protection Fund Details.md: -------------------------------------------------------------------------------- 1 | # Morpheus Protection Fund Proposal 2 | 3 | ## Introduction 4 | The Morpheus white paper sets aside 4% of all MOR emissions for the purpose of a “Protection Fund” and delegates to the Code Providers to act as oracles in the case of its resources being needed. 5 | Type of actions: 6 | - Payment of bug bounty to avoid attacks. 7 | - Payment of audits before new Smart Contracts are deployed. 8 | - Halting the Smart Contracts in case of an on going attack. 9 | - Signaling and Mechansim for payout after an attack. 10 | - Plan In Case of Significant Loss Event (Hard Fork Scenario) 11 | 12 | ## Pre-Defined Cases Triggering Minor Payouts 13 | Before the Smart Contracts go live on the Ethereum network here defined are the conditions under which the Protection Fund will pay out MOR or stETH. 14 | 15 | ## Types of Payments: 16 | 1. Bugs discovered and responsibly disclosed to the developers of a Morpheus Capital, Code, Compute, Community or Protection Fund Smart Contract. 17 | 2. Payment of audits before new Smart Contracts are deployed on the Morpheus network. 18 | 3. User losses of MOR or stETH in the case of an exploited Morpheus Smart Contract. 19 | 4. Making whole providers who didn’t receive MOR emissions in the case of a failure of the Morpheus Smart Contract. 20 | 21 | Amounts of payments from the protection fund should be in proportion to the bug, loss or emission error. 22 | 23 | ## Halting Conditions For Smart Contracts 24 | Before payments for damages can be figured out, there should be conditions that trigger a halt of the Smart Contracts in the case of an on going attack. 25 | 26 | ## Signaling & Mechanism For Payout 27 | Code Providers will participate in signaling when a payment should be triggered. First an incident will be detailed and posted on the GitHub repository of the affected Smart Contract. Including a list of affected addresses and amounts of MOR and / or stETH. 28 | 29 | If a majority of Code Providers (as measured by the weight of their MOR tokens held) which participate in the Signaling period (no longer than 7 days) validate the report as TRUE, then a payment will be triggered. 30 | 31 | Once a payment is triggered the software will message the developers to authorize a payment to the affected addresses in the amounts specified. 32 | 33 | ## Plan In Case of a Significant Loss Event 34 | A Significant Loss Event is defined as an event in which the MOR losses exceed the total resources of the Protection Fund. In this case, rather than make a payout of MOR the Code Providers should deploy new Smart Contracts and correct the MOR balances effected manually. This would effectively cause a hard fork in the code / MOR balances and all Providers, token hodlers and other infrastructure providers would have to update their code to the new Smart Contracts. 35 | 36 | In the case of stETH lost in a Significant Loss Event, the Protection Fund shall pay out to the maximum extent possible on a pro rata basis to the amount of each person’s losses. 37 | 38 | ## Conclusion 39 | Bugs and errors in software are a reality and mark the history from the two unintentional hard forks of Bitcoin to The DAO during the early days of Ethereum. 40 | 41 | So planning ahead for different scenarios and cases and how to handle them is a wise approach for protecting against and otherwise mitigating risks. Fortunately, having set aside resources in advance with the Protection Fund, and also part of the protection fund earning LP rewards in the AMM the resources dedicated to protection of users ought to grow larger over time. 42 | -------------------------------------------------------------------------------- /!KEYDOCS README FIRST!/StagesofDevelopment.md: -------------------------------------------------------------------------------- 1 | # Defining the six "Stages" of new Code: 2 | ## Design, Development, Testnet, Audit, Deployment & Checks. 3 | 4 | ## Morpheus Open Source Development Best Practices 5 | 6 | ### Stage 1. Planning / Design: 7 | Description and spec for what is to be developed. :Backend 8 | 9 | ### Stage 2A. Begin Coding: 10 | Once that backend work is complete then we need to deploy the Code to Testnet. :Backend 11 | ### Stage 2B. Begin Dashboard Development: 12 | Once backend coding is complete (runs in parrell to Testnet and auditing :Frontend 13 | 14 | ### Stage 3. Testnet for Code: 15 | Once testnet testers verify backend is functioning as expected ship to auditor. :Backend 16 | 17 | ### Stage 4A. Audit for Code: 18 | The auditor completes their work and remediations are completed. :Backend 19 | ### Stage 4B. Dashboard Testing: 20 | Deploy Dashboard for Testing before Code goes to mainnet :Frontend 21 | 22 | ### Stage 5A. Mainnet Deployment of Code: 23 | Either code is directly deployed on Mainnet by devs or preparation of a Deployment Guide. :Backend 24 | ### Stage 5B. Mainnet Deployment of Dashboard: 25 | Either Dashboard is directly deployed on Mainnet by devs to main branch or preparation of a Deployment Guide. :Frontend 26 | 27 | ### Stage 6A. Final Checks of Code: 28 | Post mainnet deployment, confirmation of correct deployment & expected function. :Backend 29 | ### Stage 6B. Final Checks of Dashboard: 30 | Testing and deployment of Dashboard to add Frontend UI to the new Smart Contract functions. :Frontend 31 | 32 | -------------------------------------------------------------------------------- /Archive/Development.md: -------------------------------------------------------------------------------- 1 | ## Development 2 | 3 | Run the following commands in the root directory. 4 | 5 | ```bash 6 | npm install 7 | npm run start 8 | ``` 9 | 10 | ## Packaging and Distribution 11 | 12 | ### MacOS 13 | 14 | 1. Download the latest Ollama release for MacOS from [here](https://github.com/jmorganca/ollama/releases). 15 | 2. Unzip the downloaded file. 16 | 3. Copy the `ollama` executable to `chatd/src/service/ollama/runners/ollama-darwin`. 17 | 4. The Electron app should be signed to be able to run on MacOS, so you need a developer certificate. To sign the app, set the following environment variables: 18 | 19 | ```bash 20 | APPLE_ID=your_apple_id@example.com 21 | APPLE_IDENTITY="Developer ID Application: Your Name (ABCDEF1234)" 22 | APPLE_ID_PASSWORD=your_apple_id_app_specific_password 23 | APPLE_TEAM_ID=ABCDEF1234 24 | ``` 25 | 26 | You can find your Apple ID, Apple Team ID, and Apple ID Application in your Apple Developer account. You can create an app-specific password [here](https://appleid.apple.com/account/manage). 27 | 28 | 5. Run `npm run package` to package the app. 29 | 30 | ### Windows 31 | 32 | 1. Build Ollama from source for Windows, this will support CPU only. See [here](https://github.com/jmorganca/ollama). 33 | 2. Copy the `ollama.exe` executable to `chatd/src/service/ollama/runners/ollama.exe`. 34 | 3. Run `npm run package` to package the app. 35 | 36 | Note: The Windows app is not signed, so you will get a warning when you run it. 37 | 38 | ### Linux 39 | 40 | 1. Build Ollama from source for Linux x64 to support CPU only, this allows for a smaller executable package. See [here](https://github.com/jmorganca/ollama). 41 | 2. Copy the `ollama` executable to `chatd/src/service/ollama/runners/ollama-linux`. 42 | 3. Run `npm run package` to package the app. 43 | -------------------------------------------------------------------------------- /Archive/Installing Morpheus on WSL.md: -------------------------------------------------------------------------------- 1 | ## Installing Morpheus on Windows 2 | 3 | - First, install WSL2, you can do that by running `wsl --install` on an admin command prompt. Then open WSL2 with `wsl` and follow the setup process. 4 | 5 | - Then run `curl https://ollama.ai/install.sh | sh` to install ollama. 6 | 7 | - Then install python by doing `sudo apt-get update` and `sudo apt-get install python3`. 8 | 9 | - Then run `pip3 install gdown`. 10 | 11 | - Now download the morpheus dpkg by running `gdown https://drive.google.com/uc?id=1PQ3n7LXeJHe_jmkYLDUQ9fWjZQTWbHCB`. 12 | 13 | - Verify the integrity of the Morpheus download by `sha1sum morpheus_0.0.5_amd64.deb`. make sure it matches the hash `b227e7bcb21ec9e8e2b4bf9510a2e1f224953fe5`, otherwise abort the installation process. 14 | 15 | - Then run `sudo dpkg -i morpheus_0.0.5_amd64.deb`, if the installation fails at first, install the dependencies, and try again. 16 | 17 | - Now once you have morpheus installed without any dependency errors, open 2 WSL2 windows by opening 2 commandline windows and typing wsl on both of them, then on one of them run `ollama serve` and on the other run `morpheus`. 18 | 19 | -------------------------------------------------------------------------------- /Archive/Integrations.md: -------------------------------------------------------------------------------- 1 | # Documentation Related To Projects Integrating With Morpheus 2 | 3 | Starting point Decentralize AI Summit repository including the Morpheus Request For Comment (MRC) is here. 4 | https://github.com/MorpheusAIs/MRC 5 | 6 | ## Morpheus Decentralized AI Ecosystem 7 | - Website: https://www.decentralizeai.org, Mor.org 8 | - X Profile: https://twitter.com/MorpheusAIs 9 | 10 | - Event 01 in Austin December 9th 2023: 11 | 12 | https://lu.ma/dofjyni8 13 | 14 | - Event 02 in Denver February 28th-29th 2024: 15 | 16 | Summary of the Decentralized AI Day at ETH Denver hosted by the Morpheus Community last week. Amazing talks by the top builders in the DeAI space. 17 | 18 | - 1. David Johnston - Talk about Morpheus 19 | https://www.youtube.com/watch?v=unbC-Md6q7g 20 | 21 | - 2. Greg from Akash - Talk about Akash Decentralized Compute Market Place 22 | https://streameth.org/watch?event=decentralize_ai_day__eth_denver_2024&session=65df6577bf97e02da98d286e 23 | 24 | - 3. Illia from NEAR - Talk about AI Agents & Web3 25 | https://streameth.org/watch?event=decentralize_ai_day__eth_denver_2024&session=65df6579bf97e02da98d2873 26 | 27 | - 4. Emozilla talk from NOUS Research - Talk about Fine Tuning Models 28 | https://streameth.org/watch?event=decentralize_ai_day__eth_denver_2024&session=65df657abf97e02da98d2878 29 | 30 | - 5. Casey and Anna - Talk about Vana the Personalized AI 31 | https://streameth.org/watch?event=decentralize_ai_day__eth_denver_2024&session=65df657bbf97e02da98d287d 32 | 33 | - 6. Scott from Stability AI - Talk about Stable Diffusion 34 | https://streameth.org/watch?event=decentralize_ai_day__eth_denver_2024&session=65df657cbf97e02da98d2882 35 | 36 | - 7. Trevor from Sapien.io -Talk about Decentralizing Data Labeling 37 | https://streameth.org/watch?event=decentralize_ai_day__eth_denver_2024&session=65df657ebf97e02da98d2887 38 | 39 | - 8. Ryan from Titan / Lumerin - Decentralized Router Yellowstone Implementation Talk 40 | https://streameth.org/watch?event=decentralize_ai_day__eth_denver_2024&session=65df6584bf97e02da98d28a5 41 | 42 | - 9. ORA - Talk on Optimistic Machine Learning 43 | https://streameth.org/watch?event=decentralize_ai_day__eth_denver_2024&session=65df6583bf97e02da98d28a0 44 | 45 | - 10. David Johnston - Talk about the Morpheus Marketplace For Code 46 | https://streameth.org/watch?event=decentralize_ai_day__eth_denver_2024&session=65df6585bf97e02da98d28aa 47 | 48 | - 11. Closing Fireside Chat with David Johnston & Erik Voorhees 49 | https://streameth.org/watch?event=decentralize_ai_day__eth_denver_2024&session=65df6586bf97e02da98d28af 50 | 51 | -Event 03 in Austin March 11th: 52 | 53 | https://lu.ma/UnrestrictedIntelligence 54 | 55 | ## List of Resources for Building Decentralized AI 56 | 57 | **Incentives, Payments, Funding** 58 | Morpheus: https://mor.org/ 59 | 60 | **Models** 61 | Bittensor API Docs https://docs.bittensor.com/python-api/html/index.html 62 | HyperSpaceAI 63 | 64 | **Fine Tuning / Training** 65 | NOUS Research 66 | 67 | **Tools** 68 | Ora(Previously HyperOracle) 69 | Lumerin 70 | OKX wallet 71 | 72 | **Compute** 73 | Akash 74 | Phala 75 | 76 | **Forges / Agent Builders** 77 | Langchain / Langsmith 78 | Polywrap 79 | Tensorplex 80 | Hive network 81 | Shinkai 82 | Assisterr 83 | Vold 84 | 85 | **Data** 86 | Syntropy 87 | Jackal Protocol 88 | Bagel 89 | HyperSpaceAI 90 | Lighthouse 91 | Inferix 92 | Rivalz 93 | 94 | **Smart Contracts** 95 | Syntropy 96 | Arbitrum 97 | Monad 98 | Sei 99 | Polygon 100 | BSC 101 | Rango 102 | Kintsu 103 | 104 | **Inference** 105 | Livepeer 106 | HyperSpaceAI 107 | 6079 108 | 109 | ## Morpheus Request for Comments (MRC) 110 | List of proposals for specific technical functions and integrations for Decentralized AI. 111 | Similar to the function of the ERC system serves in Ethereum. https://eips.ethereum.org/erc 112 | 113 | Provides a common language to describe interactions between models, agents, compute, payments, funding and so forth. 114 | Current MRCs: https://github.com/MorpheusAIs/MRC 115 | -------------------------------------------------------------------------------- /Archive/Morpheus Testing Plan.md: -------------------------------------------------------------------------------- 1 | # Testing Plan For Morpheus Smart Contracts 2 | 3 | ## Complete 4 | - **Stage 0:** Development version of Smart Contracts Deployed on Testnet. 5 | - **Stage 1:** Open source developers publish the source code. 6 | - **Stage 2:** Colleagues of original devs test the Smart Contracts. 7 | - **Stage 3:** Community members test for vulnerabilities. 8 | - **Stage 4:** Dedicated testing firm reviews the Smart Contracts on testnet. [Link](https://github.com/MorpheusAIs/Docs/blob/main/Security%20Audit%20Reports/Distribution%20Contract/Renascence%20Morpheus%20Audit%20v2.pdf) to Audit report. 9 | - **Stage 5:** Public Audit and bug bounty. 10 | The competition was held through https://www.codehawks.com/. 11 | Link to [Audit Competition](https://www.codehawks.com/contests/clrzgrole0007xtsq0gfdw8if). 12 | Link to [Report](https://www.codehawks.com/report/clrzgrole0007xtsq0gfdw8if). 13 | - **Stage 6:** Smart Contracts deployed on Ethereum / Arbitrum mainnet - **12 p.m. UTC February 8th 2024**. 14 | - **Stage 7:** Audit of the [MOR OFT](https://github.com/MorpheusAIs/Docs/tree/main/Security%20Audit%20Reports/MOR%20OFT%20Token%20Contract) and [L2TokenRecieverV2](https://github.com/MorpheusAIs/Docs/tree/main/Security%20Audit%20Reports/L2%20Token%20Receiver%20V2) Smart Contracts. 15 | - **Stage 8:** Day 90 of the bootstrapping period the AMM liquidity is deployed based on the [guidance.](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Capital%20Providers%2C%20MOR20%2C%20TCM/Phased%20AMM%20Deployment%20and%20Fair%20Price%20Discovery.md) 16 | - **Stage 9:** MOR20 Standard Smart Contracts [audit](https://github.com/MorpheusAIs/Docs/blob/main/Security%20Audit%20Reports/MOR20%20Contracts%20Audit.pdf). 17 | - **Stage 10:** MOR Rewards Staking contract [audit](/Security%20Audit%20Reports/Distribution%20Contract/Distribution%20V2%20%2B%20Staking%20Audit%20%7C%20Renascence.pdf) 18 | 19 | ## In Progress 20 | - **Stage 11**: Testnet for the [Compute Smart Contract and Router](https://github.com/Lumerin-protocol/Morpheus-Lumerin-Node/releases). 21 | - **Stage 12**: Audit of the Compute Smart Contract and Router code. 22 | 23 | ## Pending 24 | - **Stage 13**: Compute Smart Contract and Proxy Router launch on mainnet. 25 | - **Stage 14**: Testnet for the Community Frontend Builders Smart Contract. 26 | - **Stage 15**: Audit of the Community Frontend Builders Smart Contract. 27 | 28 | ## 2024-2025 29 | - **Stage 16**: Remove admin function from Smart Contracts. 30 | - **Stage 17:** Additional upgrades to Smart Contracts will require effectively everyone to update the software. 31 | -------------------------------------------------------------------------------- /Archive/Steps of Phased AMM Deployment.md: -------------------------------------------------------------------------------- 1 | # Deployment of the Liquidity Pool 2 | 3 | Below is a quick outline of the steps to be taken in the coming days as Morpheus heads into the Token launch. 4 | 5 | The first phase will be the conversion of stETH (Mainnet) to wETH (on Arbitrum) 6 | The second phase will be the creation of the pool on May 8 and the liquidity range. 7 | 8 | 9 | ## Phase 1: Conversion of stETH (on Ethereum Mainnet) to wETH (on Arbitrum) 10 | When: Will be completed prior to May 6th by the multi-sig 11 | 12 | ### Step 1: The multi-sig will convert stETH to wETH using Option A 13 | 14 | - Option A: Use Dex Aggregatior [Cow Swap](https://swap.cow.fi/#/1/swap/WETH) 15 | - This results in slippage of approximately .5 eth 16 | - The net negative impact to Mor Price at the creation of the pool will be $.01 lower due to the slippage 17 | 18 | - Option B: Unstake with Lido 19 | - Slippage: None 20 | - Time to Receive Fund: Up to 5 Days, Dependent on validator queue. ([Source](https://stake.lido.fi/wrap)) 21 | - Impact to MOR price when the pool is established is $.01 higher due to less slippage 22 | - Note: This option declined to avoid any risk of delay in receiving funds. 23 | 24 | ### Step 2: Bridge wETH from Eth Mainnet to Arbitrum using the main bridge 25 | 26 | ([Link](https://bridge.arbitrum.io)) 27 | 28 | 29 | ## Phase 2: Creation of the Liquidity Pool on May 8th. 12:00PM UTC 30 | 31 | - Step 1: Create the MOR/wETH Pool. 32 | - 52% of the wETH (converted from the stETH accumulated during the bootstrapping phase via Phase 1 process above) will be paired with 50,309 MOR tokens on Uniswap 33 | - The pool fee will be set to 0.3% 34 | - Position will be created adopting a 'full range' liquidity position 35 | - This will naturally create the initiation ratio, aka launch price 36 | - Step 2: Create second liquidity position in MOR/wETH Pool 37 | - Single-sided concentrated liquidity position comprised of the remaining 48% wETH (converted from the stETH accumulated during the bootstrapping phase via Phase 1 process above) 38 | - As detailed in MRC09, concentrated position is strategically set from 0 to the initiation ratio 39 | 40 | Note: The Morpheus multi-sig will establish the main pool on Arbitrum. All liquidity from capital providers will be concentrated there. Presumably, other market participants will create additional liquidity pools elsewhere. 41 | 42 | Beware of pools with low liquidity which may result in significant slippage. 43 | 44 | BEWARE of Fake Token Pools and SCAMS. The pool address will be posted on all Morpheus channels once it has been established. 45 | 46 | **Resources:** 47 | 48 | [Phased AMM Deployment | Fair Price Discorvery Proposal](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Phased%20AMM%20Deployment%20and%20Fair%20Price%20Discovery.md) 49 | 50 | [UniswapV3: How to Add Liquidity](https://support.uniswap.org/hc/en-us/articles/7423194619661-How-to-add-liquidity-to-Uniswap-v3) 51 | 52 | [Lido Staking and Redemption Process](https://stake.lido.fi/wrap) 53 | 54 | [Lido Validator Queue](https://www.validatorqueue.com/ ) 55 | -------------------------------------------------------------------------------- /Archive/Subscription Discount Rate.md: -------------------------------------------------------------------------------- 1 | # What is the "RSD" Metric? = "Recurring Subscription Discount" % 2 | 3 | ## Description: 4 | This number represents the discount rate of providing stETH to Morpheus in order to earn 1 MOR, as compared to buying MOR on Uniswap. 5 | 6 | This is an important metric because the network effect desired is those that want to earn MOR and use it for its utility. So by providing stETH one can think of this as "subscribing" to the Morpheus protocol or platform in order to access Compute / AI Inference. 7 | 8 | At the moment this document is written, there is a significant discount to providing stETH vs buying MOR from Uniswap. This calculation is shown on Morlord as currently $14.55 USD worth of ETH yield earning 1 MOR. And the current Uniswap price is: $78.21 USD worth of ETH. So the current RSD rate is 81.73% 9 | 10 | As the amount of stETH has increased so has the effective price to earn 1 MOR. Also with the daily decay rate of MOR emitted the competition to earn MOR increases between those providing stETH. 11 | https://morlord.com/ 12 | 13 | ![PriceperMOR](https://github.com/MorpheusAIs/Docs/assets/1563345/4ee35840-632f-4fc7-8d8f-641f816cbcc8) 14 | 15 | ![CurrentRSDrate](https://github.com/MorpheusAIs/Docs/assets/1563345/974c2dfe-09d3-4087-88d4-151798e65647) 16 | 17 | ## Context: 18 | The purpose of the Morpheus is to build a community of contributors. 19 | Best to attract people interesting in the real utility who want to acquire MOR at the best price compared to those seeking ETH on ETH returns (who are only sellers). 20 | 21 | Its like BTC mining. It attracts people competing to earn BTC at the best price (or MOR in this case), which due to the decay rate and increasing competition tends to rise over time. 22 | 23 | Keep in mind Morpheus is a LONG term project. Builders, users, Contributors are what create long term value. 24 | 25 | One used to be able to earn more for a few dollars, then it was $5, then $10 worth of yield, now its $14.55. 26 | -------------------------------------------------------------------------------- /Archive/Translations/Arabic/Protection Fund Details Arabic.md: -------------------------------------------------------------------------------- 1 | # مقترح صندوق الحماية لمورفيوس 2 | 3 | ## مقدمة 4 | 5 | يخصص الورقة البيضاء لمورفيوس 4٪ من جميع انبعاثات مور لغرض "صندوق الحماية" ويفوض مزودي الرموز بالعمل كأوراكل في حالة حاجة موارده. 6 | 7 | أنواع الإجراءات: 8 | 9 | - دفع مكافأة الثغرات لتجنب الهجمات. 10 | - دفع التدقيقات قبل نشر عقود ذكية جديدة. 11 | - توقف عقود ذكية في حالة هجوم جارٍ. 12 | - الإشارة والآلية للدفع بعد الهجوم. 13 | - خطة في حالة حدوث حدث خسارة كبير (سيناريو الشوكة الصعبة) 14 | 15 | ## الحالات المحددة مسبقًا التي تشغل دفعات صغيرة 16 | 17 | قبل أن تذهب العقود الذكية مباشرة على شبكة Ethereum تم تحديد الشروط الذي تحتها سيدفع صندوق الحماية MOR أو stETH. 18 | 19 | ## أنواع المدفوعات: 20 | 21 | 1. الثغرات التي تم اكتشافها والتي تم الإبلاغ عنها بشكل مسؤول لمطوري Morpheus Capital، Code، Compute، Community أو صندوق الحماية الذكية. 22 | 2. دفع التدقيقات قبل نشر عقود ذكية جديدة على شبكة Morpheus. 23 | 3. خسائر المستخدمين من MOR أو stETH في حالة استغلال عقد ذكي Morpheus. 24 | 4. جعل مزودي الخدمة الذين لم يتلقوا انبعاثات MOR في حالة فشل عقد ذكي Morpheus بالكامل. 25 | 26 | يجب أن تكون مبالغ المدفوعات من الصندوق الوقائي متناسبة مع الثغرة أو الخسارة أو خطأ الانبعاث. 27 | 28 | ## شروط التوقف للعقود الذكية 29 | 30 | قبل أن يتمكنوا من معرفة مدى الأضرار، يجب أن تكون هناك شروط تؤدي إلى توقف العقود الذكية في حالة هجوم جارٍ. 31 | 32 | ## الإشارة والآلية للدفع 33 | 34 | سيشارك مزودو الرموز في الإشارة عندما يجب تشغيل دفعة. أولاً، سيتم تفصيل الحادث ونشره في مستودع GitHub للعقد الذكي المتضرر. بما في ذلك قائمة العناوين المتضررة ومبالغ MOR و / أو stETH. 35 | 36 | إذا قامت غالبية مزودي الرموز (كما يقاس بوزن رموز MOR التي يمتلكونها) الذين شاركوا في فترة الإشارة (لا تزيد عن 7 أيام) بالتحقق من تقرير الصحة كصحيح، فسيتم تشغيل دفعة. 37 | 38 | بمجرد تشغيل الدفعة، سيقوم البرنامج بإرسال رسالة إلى المطورين للمصادقة على دفعة إلى العناوين المتضررة بالمبالغ المحددة. 39 | 40 | ## خطة في حالة حدوث حدث خسارة كبير 41 | 42 | يتم تعريف حدث الخسارة الكبيرة على أنه حدث يتجاوز فيه خسائر MOR الموارد الإجمالية لصندوق الحماية. في هذه الحالة، بدلاً من إجراء دفعة من MOR، يجب على مزودي الرموز نشر عقود ذكية جديدة وتصحيح أرصدة MOR المتأثرة يدويًا. سيؤدي هذا بشكل فعال إلى تسبب الشوكة الصعبة في الرموز / أرصدة MOR وسيتعين على جميع مزودي الخدمات وحاملي الرموز ومزودي البنية التحتية الأخرى تحديث كودهم إلى العقود الذكية الجديدة. 43 | 44 | في حالة فقدان stETH في حدث خسارة كبير، يجب على صندوق الحماية دفع بأقصى قدر ممكن بنسبة مئوية لمبلغ خسائر كل شخص. 45 | 46 | ## الختام 47 | 48 | الثغرات والأخطاء في البرمجيات هي واقع وتميز التاريخ من انقسامات الشوكة الصعبة غير المقصودة ل 49 | -------------------------------------------------------------------------------- /Archive/Translations/Bulgarian/Protection Fund Details Bulgarian.md: -------------------------------------------------------------------------------- 1 | # Предложение за Фонд за Защита на Морфеус 2 | 3 | ## Въведение 4 | 5 | Бялата книга на Морфеус отделя 4% от всички емисии на MOR за целта на "Фонд за Защита" и делегира на Доставчиците на Код да действат като оракули в случай на необходимост от ресурси. 6 | 7 | Видове действия: 8 | 9 | - Плащане на награди за откриване на грешки, за да се предотвратят атаки. 10 | - Плащане на проверки, преди да бъдат разгърнати нови умни договори. 11 | - Спиране на умните договори в случай на текуща атака. 12 | - Сигнализиране и механизъм за плащане след атака. 13 | - План в случай на събитие със значителна загуба (Сценарий за Твърдо Разклонение) 14 | 15 | ## Предварително Дефинирани Случаи, Извикващи Малки Плащания 16 | 17 | Преди да умните договори бъдат пуснати на мрежата на Ethereum, тук са дефинирани условията, при които Фондът за Защита ще плаща MOR или stETH. 18 | 19 | ## Видове Плащания: 20 | 21 | 1. Открити грешки и отговорно разкрити на разработчиците на Морфеус Капитал, Код, Пресмятане, Общност или Умни Договори за Защита. 22 | 2. Плащане на проверки, преди да бъдат разгърнати нови умни договори в мрежата на Морфеус. 23 | 3. Загуби на потребители от MOR или stETH в случай на експлоатиран умен договор на Морфеус. 24 | 4. Възстановяване на доставчици, които не получиха емисии на MOR в случай на неуспех на умния договор на Морфеус. 25 | 26 | Сумите на плащанията от фонда за защита трябва да бъдат пропорционални на грешката, загубата или грешката при емисията. 27 | 28 | ## Условия за Спиране на Умни Договори 29 | 30 | Преди да бъдат определени плащания за вреди, трябва да има условия, които да предизвикат спиране на умните договори в случай на текуща атака. 31 | 32 | ## Сигнализиране и Механизъм за Плащане 33 | 34 | Доставчиците на Код ще участват в сигнализирането, когато трябва да се задейства плащане. Първо ще бъде подробно описан инцидентът и публикуван в GitHub хранилището на засегнатия умен договор. Включително списък на засегнатите адреси и суми на MOR и / или stETH. 35 | 36 | Ако повечето Доставчици на Код (колкото се измерва по теглото на техните MOR токени) участват в периода на сигнализация (не повече от 7 дни), потвърждавайки доклада като ИСТИНСК, тогава ще се задейства плащане. 37 | 38 | След като плащането е задействано, софтуерът ще уведоми разработчиците да упълномощат плащане на засегнатите адреси в посочените суми. 39 | 40 | ## План в Случай на Събитие със Значителна Загуба 41 | 42 | Събитие със Значителна Загуба се дефинира като събитие, при което загубите от MOR надхвърлят общите ресурси на Фонда за Защита. В този случай, вместо да се извърши плащане на MOR, Доставчиците на Код трябва да разгърнат нови умни договори и да коригират емисиите на MOR ръчно. Това би предизвикало ефективно твърдо разклонение в кода / емисиите на MOR и всички доставчици, токени холдъри и други инфраструктурни доставчици би трябвало да актуализират своя код до новите умни договори. 43 | 44 | В случай на загуба на stETH в събитие със Значителна Загуба, Фондът за Защита ще извърши плащане до максималния възможен обем на пропорционална основа спрямо загубите на всеки човек. 45 | 46 | ## Заключение 47 | 48 | Грешките и грешките в софтуера са реалност и отбелязват историята от двата непреднамер 49 | -------------------------------------------------------------------------------- /Archive/Translations/Chinese/Mastery of Tokenomics Chinese.md: -------------------------------------------------------------------------------- 1 | # 深入探讨 Morpheus 代币经济学 2 | ## 简介： 3 | 代币经济学是 Web3 项目的支柱，塑造了它们的动态和优势。通过 Bitcoin 开始的代币经济学演进之旅揭示了它的关键作用。 4 | 随时间推移的代币经济学模型： 5 | - **比特币时代：** 比特币引入了去中心化货币，通过有限的供应和工作证明强调了稀缺性和价值。 6 | - **以太坊和智能合约：** 以太坊扩展了代币经济学，通过智能合约实现了可编程资产，引领了代币化趋势。 7 | - **DeFi 和治理代币：** DeFi 中的治理代币展示了代币如何赋予用户协议决策权的能力。 8 | - **NFTs：** NFT 的兴起展示了代币在金融应用之外的多功能性。 9 | - **RWA（真实世界资产）：** 部分或完全依赖于真实世界资产的代币经济学变体。 10 | 11 | ## 问题在哪里？ 12 | 当探讨受到有缺陷的模型影响的挑战时，有效的代币经济学的重要性变得显而易见，这影响了用户参与度、项目商业模式和长期可持续性。 13 | 吸引和保留用户成为一个挑战，因为糟糕的代币经济学会阻碍用户的积极参与，未能提供明确的好处或激励，缺乏实用性或有形价值会降低项目的吸引力。这也导致了不合理高昂的营销成本。 14 | 代币经济学缺陷可能导致经济失调，导致价值分配不公，并影响生态系统的整体健康。在这种情况下，商业模式停止运作，危及项目的可持续性，从而导致无休止的转型或破产。 15 | 16 | ## 是否有出路？ 17 | Morpheus 通过一套全面的解决方案来解决这些挑战，将各种组件相互交织，有效利用 MOR 代币，从而创造出内部和外部需求。 18 | Morpheus 代币经济学融合了所有模型的元素： 19 | 1. 受比特币启发，它将发行上限设定为 42,000,000，并从每天发放 14,400 MOR 开始，然后每天减少 2.468994701 MOR，直到奖励在第 5,833 天（约 16 年后）达到 0。这个时间表与项目的增长保持一致，防止了供应过剩。 20 | 2. 受以太坊启发，通过智能合约确保透明度和严格遵守设定条件。 21 | 3. 借鉴 DeFi，代币经济学允许将 MOR 代币用作投资工具，为项目开发的贡献提供奖励。 22 | 4. 借鉴 NFT 和 RWAs，使 MOR 持有者每日领取一部分网络计算能力，并与其他玩家类别进行各种操作（包括奖励）。 23 | 24 | ![meme](https://github.com/antonbosss/fantastic-bassoon/blob/main/tokenomics-doc/meme-tokenomics1.jpg) 25 | 26 | ## Techno Capital Machine 代币经济学引擎 27 | Morpheus 引入了一种新颖的代币分配机制，称为 Techno Capital Machine（TCM）。它在公平分配代币的同时积累价值，用于提供协议拥有的流动性（POL）。 28 | 29 | 以下是 TCM 机制的概述： 30 | 1. 资本提供者存入 stETH（Lido 抵押的以太坊），产生收益，并按比例以本机代币 MOR 获得奖励。 31 | 2. Morpheus 合约使用收益的 50% 从 AMM 购买 MOR 代币，并将其余 50% 用于提供流动性。 32 | 3. MOR 持有者可以访问 Morpheus 的实用功能。 33 | 34 | **与其他引导和代币发行模型相比，TCM 模型具有许多优势：** 35 | - 用户不直接提供资本/本金，而是提供收益。 36 | - 没有永久损失的风险。 37 | - 收益为本机代币持续创造需求。 38 | - 协议拥有的流动性随时间增长。 39 | - 该模型公平、链不可知且可扩展。 40 | 41 | ![TCM](https://github.com/antonbosss/fantastic-bassoon/blob/main/tokenomics-doc/TCM-tokenomics.jpg) 42 | 43 | ## 生态系统参与者的激励 44 | Morpheus 中有四类生态系统参与者，每类参与者分配 24% 的 MOR 发行量： 45 | - 资本提供者。 46 | - 计算提供者。 47 | - 代码提供者。 48 | - 社区建设者。 49 | 50 | **资本提供者** 参与 Techno Capital Machine，提供产生收益的资本，推动 MOR 的协议拥有流动性。 51 | 52 | **代码提供者** 参与 Morpheus 代码的演进和智能代理的创建。贡献后，代码提供者请求“权重”——确定 MOR 发行量如何在此类参与者之间分配的任意工作单位。 53 | 54 | **计算提供者** 生产网络的主要资源——计算。 55 | 56 | **社区提供者/建设者** 主要通过创建前端来推动 Morpheus 的采用。 57 | 58 | ![tknmcs](https://github.com/antonbosss/fantastic-bassoon/blob/main/tokenomics-doc/tkenmcs.png) 59 | 60 | ## 特别元素 61 | 由于首先采用了代币实用性方法，持有后即可使用，相当大比例的代币将停留在没有动静的钱包中，并随着新用户的涌入而增值。这反过来又导致网络效应的增长。 62 | 63 | 通过公平启动，避免了风险投资者、私人投资者或通过私人分配或预挖矿获得代币的人所带来的卖压，进一步确保了代币经济学的长期可持续性。 64 | 65 | MOR 销毁机制与以太坊的销毁功能类似，可确保随着时间的推移，MOR 的稀缺性。 66 | 67 | 除此之外，还有一个锦上添花的保护基金，它收到所有发行量的 4%，旨在作为代币经济学在意外事件发生时的稳定器。 68 | 69 | ## 结论 70 | Morpheus 的代币经济学提出了一个全面的框架，避免了陷阱，并考虑到了实用性。通过激励主要贡献者、促进其互动并维持公平的市场动态，它确立了 Morpheus 作为去中心化领域中的可持续创新者。开放性、清晰性和公平性是自然吸引越来越多新用户的因素。 71 | 72 | ## 阅读： 73 | 1. [白皮书](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/WhitePaper.md) 74 | 2. [Techno Capital Machine 论文](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md) 75 | 3. [保护计划详情](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Protection%20Fund%20Details.md) 76 | -------------------------------------------------------------------------------- /Archive/Translations/Chinese/Morpheus Meetup Guide Chinese.md: -------------------------------------------------------------------------------- 1 | # Morpheus Meetup Guide 2 | 3 | ## Abstract: 4 | 组织加密货币聚会是一个令人兴奋的机会，可以与志同道合的人联系，分享知识和见解，交流想法并促进社区参与。无论您是经验丰富的组织者还是新手活动策划者，本指南都将为您提供最佳实践，确保您的 Morpheus 聚会取得成功。 5 | 6 | ## 聚会形式： 7 | ### 在酒吧或咖啡馆举办的休闲聚会： 8 | 在当地酒吧、咖啡馆或餐厅举行的非正式聚会，与会者可以在轻松的氛围中交流、建立网络并讨论与加密货币相关的话题。典型持续时间为 2-3 小时，允许与会者自由进出。开放式讨论、闪电演讲或非正式演示。考虑加入网络活动以促进人际关系。 9 | ### 在共享办公空间举办的交互式研讨会： 10 | 在共享办公空间或社区中心举办的动手研讨会，侧重于与 Morpheus 相关的特定主题或技能培训练习（例如如何运行和使用 Morpheus 节点）。典型持续时间为 2-4 小时，提供充分的互动时间和小组活动。您还可以准备教程，并组织迷你黑客马拉松，与会者可以学习新概念、合作项目，并获得实践经验。 11 | ### 面板讨论和社交活动： 12 | 一个由行业（DeAI / AI / Web3）专家主持的专题讨论会，随后是与与会者和热心爱好者交流的机会。典型持续时间为 2-3 小时，既分配了时间进行专题讨论，也有时间进行社交活动。重要的是要涵盖热门话题或相关叙述，随后进行问答环节，并在茶歇期间进行非正式社交活动。 13 | ### 社区圆桌会议和知识交流： 14 | 一个协作论坛，社区成员齐聚一堂，分享见解，讨论挑战，并就 DeAI / AI / Morpheus 相关主题、法规或行业趋势进行头脑风暴。典型持续时间为 2-3 小时，结合了结构化讨论和开放式交流。您可以为深入讨论的细分领域组建小组，并组织促进知识共享的会议。 15 | ### 项目展示和演示日（在 Morpheus 开发的后期阶段）： 16 | 一个展示活动，重点介绍 Morpheus 生态系统中的创新解决方案、项目、工具、智能代理或倡议。与会者有机会展示他们的项目，并从社区中获得反馈。典型持续时间为 3-4 小时，每位演讲者有足够的时间展示他们的工作并与观众互动。考虑加入投票机制或观众选择奖项，以表彰突出的项目。 17 | 18 | **注意：** 不论选择哪种格式，强调聚会旨在成为一次包容和互动的聚会，而不是正式的半日会议。鼓励与会者积极参与并为社区驱动的氛围做出贡献。 19 | 20 | # 准备工作： 21 | 1) **确定形式。** 确定最适合您观众的形式。是一个教育性的、以建立网络为重点的聚会，还是两者兼而有之？ 22 | 2) **选择场地。** 选择一个能容纳您预期人数并提供座位、AV 设备和互联网接入等必要设施的场地。重要提示：考虑到可及性和靠近公共交通的因素。 23 | 3) **确定日期和时间。** 提前安排聚会，并考虑关键演讲者的可用性、节假日和其他竞争性事件。 24 | 4) **推广。** 创建引人入胜的活动描述和视觉材料（您可以寻求 Morpheus 社区的帮助），并利用各种渠道推广您的聚会，包括社交媒体（包括 Morpheus 的社交媒体）、社区论坛、合作伙伴和本地媒体。鼓励与会者 RSVP 以评估兴趣并做出相应计划。 25 | 5) **实现计划。** 提前考虑所有细节，例如位置标识、潜在与会者的问题、足够的茶点以及制定预算。 26 | 27 | **提示：** 28 | - 一个好的解决方案可能是将聚会作为更大型的活动或会议的一部分； 29 | - 与经验丰富的组织者或社区成员合作，以获得策划和执行聚会的见解和支持； 30 | - 如果聚会持续 3-4 小时，安排休息时间是很重要的； 31 | - 无论形式如何，在活动开始前为注册预留足够的时间，之后为社交活动留出时间； 32 | - 在 RSVP 上使用多个平台或您所在地区常用的平台； 33 | - 您可以成为演讲者，或邀请来自开源贡献者的人，例如 Discord 中的 David Johnston（智能代理）。 34 | 35 | # 在聚会期间： 36 | 1) **欢迎和介绍。** 以热烈的欢迎开始您的聚会，并简要介绍议程。为一个包容和互动的活动定下基调。 37 | 2) **与与会者互动。** 通过问答环节、社交活动和小组讨论鼓励积极参与。创造机会让与会者分享他们的经验和见解。 38 | 3) **内容传递。** 如果有演讲者或演示，请确保他们提供与聚会主题相符的有价值内容。保持演示简洁有趣，以保持与会者的兴趣。 39 | 4) **促进社交活动。** 为与会者安排时间进行社交活动和交换想法。考虑使用破冰活动或小组练习来促进参与者之间的联系。 40 | 41 | **提示：** 42 | - 单独的演示时间不应超过 15-20 分钟，因为参与者在此时间之后往往会失去注意力； 43 | - 重要的是要混合和交替不同的活动形式，以保持聚会的动态； 44 | - 担任聚会的主持人，并添加您的评论以保持谈话引人入胜； 45 | - 有效管理时间；与演讲者商定一个信号，指示他们的发言时间即将结束； 46 | - 为额外激励参与者分配一小笔奖金基金是个好主意； 47 | - 如果可能的话，拍摄大量照片，考虑邀请专业摄影师； 48 | - 最好在聚会结束后提供茶点，以保持观众的参与直到活动结束；茶点应在聚会开始前供应水。 49 | 50 | # 聚会后： 51 | 1) **收集反馈。** 从与会者那里收集反馈，评估您的聚会的成功程度，并确定需要改进的方面。使用调查或非正式讨论征求意见。 52 | 2) **后续跟进。** 通过分享资源、演示材料、演示录音或即将到来的机会与与会者保持沟通。感谢他们的参与并鼓励持续参与。 53 | 3) **反思和迭代。** 反思您的聚会经验，并为未来的活动确定教训。根据反馈和不断变化的社区需求持续迭代和完善您的方法。 54 | 55 | # 新手组织者的提示： 56 | 1) **从小开始。** 如果您是新手组织者，可以考虑从规模较小、更亲密的聚会开始，然后逐步扩大规模。 57 | 2) **利用资源。** 利用在线资源、模板和可用于活动策划、推广和后勤管理的工具。 58 | 3) **保持灵活。** 优雅地适应意外挑战或情况变化。在整个过程中与与会 59 | 60 | # 聚会及奖励证明要求： 61 | 62 | 1) 聚会只能在附件（最后一页）指定的城市举办，每月不超过一次。 63 | 2) 所有费用由组织者承担，可以按每小时 50 美元的全职当量率进行报销。所有费用必须有文件记录并得到确认。 64 | 3) 聚会报告必须与其有用性的证据一起发布在 GitHub 上，这些证据可能包括： 65 | a) 照片和视频文档； 66 | b) 讨论笔记； 67 | c) 演讲者反馈表； 68 | d) 网络跟踪器； 69 | e) 项目演示和反馈； 70 | f) 社交媒体提及和参与度； 71 | g) 出席和参与度指标； 72 | h) 推荐和引用。 73 | 4) 工作小时数并不像工作所产生的价值那样重要。如果没有创造价值，则不计算小时数。 74 | 5) 在组织聚会之前，请熟悉代码贡献者最佳实践，并在“问题”部分发布有关您城市需要 Morpheus 聚会的帖子。 75 | 6) 预期奖励小时数为 2 到 6 小时。每小时聚会及其结果报告、数据、笔记、分析和智能代理开发的启动等项，奖励 2 小时。 76 | 7) 这是每个城市的一次性奖励。聚会应在第一次聚会后由社区主导，因为这为他们带来价值。希望第一次会议能引起当地代码贡献者、计算提供者、资本提供者和前端构建者的兴趣，使他们定期聚会。 77 | 78 | **明确的是，任何人都可以举办 Morpheus 聚会。无需获得许可。没有团队。社区以无需许可的方式推动该项目。** 79 | 80 | **注意：** 本指南旨在促进成功的 Morpheus 聚会并鼓励社区参与，同时遵循指定的准则和最佳实践。 81 | 82 | # 附件 83 | ## 亚洲 + 大洋洲 (28) 84 | 东京，日本 85 | 北京，中国 86 | 孟买，印度 87 | 德里，印度 88 | 钦奈，印度 89 | 艾哈迈达巴德，印度 90 | 班加罗尔，印度 91 | 海得拉巴，印度 92 | 上海，中国 93 | 悉尼，澳大利亚 94 | 首尔，韩国 95 | 雅加达，印度尼西亚 96 | 德里，印度 97 | 马尼拉，菲律宾 98 | 香港 99 | 新加坡 100 | 吉隆坡，马来西亚 101 | 曼谷，泰国 102 | 奥克兰，新西兰 103 | 台北，台湾 104 | 墨尔本，澳大利亚 105 | 迪拜，阿拉伯联合酋长国 106 | 大阪，日本 107 | 墨尔本，澳大利亚 108 | 布里斯班，澳大利亚 109 | 釜山，韩国 110 | 珀斯，澳大利亚 111 | 伊斯坦布尔，土耳其 112 | 113 | ## 欧洲 (24) 114 | 基辅，乌克兰 115 | 伦敦，英国 116 | 巴黎，法国 117 | 柏林，德国 118 | 罗马，意大利 119 | 马德里，西班牙 120 | 阿姆斯特丹，荷兰 121 | 斯德哥尔摩，瑞典 122 | 维也纳，奥地利 123 | 都柏林，爱尔兰 124 | 布鲁塞尔，比利时 125 | 慕尼黑，德国 126 | 巴塞罗那，西班牙 127 | 哥本哈根，丹麦 128 | 雅典，希腊 129 | 华沙，波兰 130 | 布达佩斯，匈牙利 131 | 里斯本，葡萄牙 132 | 苏黎世，瑞士 133 | 日内瓦，瑞士 134 | 赫尔辛基，芬兰 135 | 布拉格，捷克共和国 136 | 爱丁堡，苏格兰 137 | 米兰，意大利 138 | 139 | ## 非洲 + 中东 (9) 140 | 开罗，埃及 141 | 拉各斯，尼日利亚 142 | 约翰内斯堡，南非 143 | 内罗毕，肯尼亚 144 | 开普敦，南非 145 | 亚的斯亚贝巴，埃塞俄比亚 146 | 突尼斯，突尼斯 147 | 特拉维夫，以色列 148 | 迪拜，阿联酋 149 | 150 | ## 北美 + 南美 (24) 151 | 纽约市，美国 152 | 奥斯汀，美国 153 | 洛杉矶，美国 154 | 芝加哥，美国 155 | 多伦多，加拿大 156 | 墨西哥城，墨西哥 157 | 圣保罗，巴西 158 | 布宜诺斯艾利斯，阿根廷 159 | 里约热内卢，巴西 160 | 波哥大，哥伦比亚 161 | 圣地亚哥，智利 162 | 蒙特利尔，加拿大 163 | 达拉斯，美国 164 | 休斯顿，美国 165 | 迈阿密，美国 166 | 旧金山，美国 167 | 西雅图，美国 168 | 亚特兰大，美国 169 | 波士顿，美国 170 | 温哥华，加拿大 171 | 魁北克城，加拿大 172 | 巴拿马城，巴拿马 173 | 圣胡安，波多黎各 174 | 罗利，美国 175 | -------------------------------------------------------------------------------- /Archive/Translations/Chinese/Morpheus Windows Install Guide Chinese.md: -------------------------------------------------------------------------------- 1 | ## 在Windows上安装Morpheus 2 | 3 | - 首先，必须先安装 WSL2，你可以通过在管理员命令提示符下运行 `wsl --install` 来做到这一点。然后打开 WSL2，输入 `wsl` 并跟随设置过程。 4 | 5 | - 然后运行 `curl https://ollama.ai/install.sh | sh` 来安装ollama。 6 | 7 | - 接着通过运行 `sudo apt-get update` 和 `sudo apt-get install python3` 来安装 python。 8 | 9 | - 然后运行 `pip3 install gdown`。 10 | 11 | - 现在你可以下载 morpheus dpkg。 请运行 `gdown https://drive.google.com/uc?id=1PQ3n7LXeJHe_jmkYLDUQ9fWjZQTWbHCB`。 12 | 13 | - 通过使用 `sha1sum morpheus_0.0.5_amd64.deb` 验证 Morpheus 下载文件的完整性。确保它与哈希值 `b227e7bcb21ec9e8e2b4bf9510a2e1f224953fe5` 匹配，否则中止安装过程。 14 | 15 | - 接下来，运行 `sudo dpkg -i morpheus_0.0.5_amd64.deb`，如果安装初次失败，安装依赖项然后再试一次。 16 | 17 | - 现在一旦你安装了 morpheus 而没有任何依赖错误，通过打开2个命令行窗口并在两者中输入 wsl 来打开2个 WSL2 窗口，然后在其中一个上运行 `ollama serve`，在另一个上运行 `morpheus`。 18 | -------------------------------------------------------------------------------- /Archive/Translations/Chinese/Protection Fund Details Chinese.md: -------------------------------------------------------------------------------- 1 | # Morpheus 保护基金提案 2 | 3 | ## 简介 4 | 5 | Morpheus 白皮书规定将所有 MOR 发行的 4% 保留为 "保护基金"，并在需要时委托代码提供者为资源提供支持。 6 | 操作类型： 7 | 8 | - 支付漏洞赏金以避免攻击。 9 | - 在部署新智能合约之前支付审计费用。 10 | - 在攻击持续时暂停智能合约。 11 | - 攻击后的信号和支付机制。 12 | - 严重损失事件（硬分叉场景）的计划。 13 | 14 | ## 触发预定义小额支付的案例 15 | 16 | 在智能合约在以太坊网络上转为实时之前，这里定义了保护基金支付 MOR 或 stETH 的条件。 17 | 18 | ## 支付类型： 19 | 20 | 1. 向 Morpheus 资本、代码、计算、社区或保护基金智能合约的开发者负责地报告发现的漏洞。 21 | 2. 在 Morpheus 网络部署新智能合约之前支付审计费用。 22 | 3. 当 Morpheus 智能合约被滥用时，用户失去 MOR 或 stETH。 23 | 4. 在 Morpheus 智能合约失败的情况下，完全补偿未收到 MOR 发行的提供者。 24 | 25 | 在保护基金中支付的金额应与漏洞、损失或发行错误成比例。 26 | 27 | ## 暂停智能合约的条件 28 | 29 | 在确认损失支付之前，应该有条件来暂停智能合约，如果攻击持续发生。 30 | 31 | ## 信号和支付机制 32 | 33 | 代码提供者参与信号触发时的支付。首先，事件将被详细说明并发布到受影响的智能合约的 GitHub 存储库中。包括受影响地址和 MOR 和/或 stETH 的金额列表。 34 | 35 | 如果大多数代码提供者（以 MOR 令牌持有量衡量）在信号周期（最长 7 天）内参与，则报告将确认为 TRUE 并触发支付。 36 | 37 | 支付触发后，软件会向开发者发送消息，以批准向受影响地址支付指定金额。 38 | 39 | ## 严重损失事件场景的计划 40 | 41 | 严重损失事件定义为 MOR 损失超过保护基金总资源的事件。在这种情况下，代码提供者应部署新智能合约并手动调整 MOR 余额，而不是支付 MOR。这实际上会导致代码/MOR 余额产生硬分叉，并且所有提供者、令牌持有者和其他基础设施提供者都必须将代码更新到新的智能合约。 42 | 43 | 在严重损失事件中，如果 stETH 出现损失，保护基金应该按比例支付每个人的损失金额。 44 | 45 | ## 结论 46 | 47 | 软件中的漏洞和错误展示了历史上比特币两次意外的硬分叉以及以太坊早期的 DAO。因此，对各种情况和案例做好准备并提前规划如何处理它们是一种明智的风险管理和缓解风险的方法。幸运的是，提前预留资源到保护基金，并且为 LP 奖励在 AMM 中获得一些保护基金，并且为用户的保护提供资源应随着时间的推移而增长。# Morpheus 保护基金提案 48 | 49 | ## 简介 50 | 51 | Morpheus 白皮书规定将所有 MOR 发行的 4% 保留为 "保护基金"，并在需要时委托代码提供者为资源提供支持。 52 | 操作类型： 53 | 54 | - 支付漏洞赏金以避免攻击。 55 | - 在部署新智能合约之前支付审计费用。 56 | - 在攻击持续时暂停智能合约。 57 | - 攻击后的信号和支付机制。 58 | - 严重损失事件（硬分叉场景）的计划。 59 | 60 | ## 触发预定义小额支付的案例 61 | 62 | 在智能合约在以太坊网络上转为实时之前，这里定义了保护基金支付 MOR 或 stETH 的条件。 63 | 64 | ## 支付类型： 65 | 66 | 1. 向 Morpheus 资本、代码、计算、社区或保护基金智能合约的开发者负责地报告发现的漏洞。 67 | 2. 在 Morpheus 网络部署新智能合约之前支付审计费用。 68 | 3. 当 Morpheus 智能合约被滥用时，用户失去 MOR 或 stETH。 69 | 4. 在 Morpheus 智能合约失败的情况下，完全补偿未收到 MOR 发行的提供者。 70 | 71 | 在保护基金中支付的金额应与漏洞、损失或发行错误成比例。 72 | 73 | ## 暂停智能合约的条件 74 | 75 | 在确认损失支付之前，应该有条件来暂停智能合约，如果攻击持续发生。 76 | 77 | ## 信号和支付机制 78 | 79 | 代码提供者参与信号触发时的支付。首先，事件将被详细说明并发布到受影响的智能合约的 GitHub 存储库中。包括受影响地址和 MOR 和/或 stETH 的金额列表。 80 | 81 | 如果大多数代码提供者（以 MOR 令牌持有量衡量）在信号周期（最长 7 天）内参与，则报告将确认为 TRUE 并触发支付。 82 | 83 | 支付触发后，软件会向开发者发送消息，以批准向受影响地址支付指定金额。 84 | 85 | ## 严重损失事件场景的计划 86 | 87 | 严重损失事件定义为 MOR 损失超过保护基金总资源的事件。在这种情况下，代码提供者应部署新智能合约并手动调整 MOR 余额，而不是支付 MOR。这实际上会导致代码/MOR 余额产生硬分叉，并且所有提供者、令牌持有者和其他基础设施提供者都必须将代码更新到新的智能合约。 88 | 89 | 在严重损失事件中，如果 stETH 出现损失，保护基金应该按比例支付每个人的损失金额。 90 | 91 | ## 结论 92 | 93 | 软件中的漏洞和错误展示了历史上比特币两次意外的硬分叉以及以太坊早期的 DAO。因此，对各种情况和案例做好准备并提前规划如何处理它们是一种明智的风险管理和缓解风险的方法。幸运的是，提前预留资源到保护基金，并且为 LP 奖励在 AMM 中获得一些保护基金，并且为用户的保护提供资源应随着时间的推移而增长。 94 | -------------------------------------------------------------------------------- /Archive/Translations/Finnish/Protection Fund Details Finnish.md: -------------------------------------------------------------------------------- 1 | # Morpheus Suojarahaston Ehdotus 2 | 3 | ## Johdanto 4 | 5 | Morpheusin valkoinen kirja varaa 4 % kaikista MOR-päästöistä "Suojarahaston" tarkoitukseen ja valtuuttaa Koodin Tarjoajat toimimaan oraakkeleina, jos sen resursseja tarvitaan. 6 | Toimintatyypit: 7 | 8 | - Palkkioiden maksaminen haavoittuvuuksien estämiseksi. 9 | - Tarkastusten maksaminen ennen uusien Älykkäiden Sopimusten käyttöönottoa. 10 | - Älykkäiden Sopimusten keskeyttäminen jatkuvan hyökkäyksen tapauksessa. 11 | - Merkkien ja mekanismin allekirjoittaminen maksun jälkeen hyökkäyksen jälkeen. 12 | - Suunnitelma Merkittävän Tappion Tapahtumassa (Hard Fork -skenaario) 13 | 14 | ## Ennalta määritellyt tapaukset, jotka laukaisevat vähäiset maksut 15 | 16 | Ennen kuin Älykkäät Sopimukset menevät live-tilaan Ethereum-verkossa, tässä määritellään ehdot, joiden mukaisesti Suojarahasto maksaa MOR:ia tai stETH:ia. 17 | 18 | ## Maksujen Tyypit: 19 | 20 | 1. Bugit, jotka on löydetty ja vastuullisesti ilmoitettu Morpheus-pääoman, koodin, laskennan, yhteisön tai Suojarahaston Älykkäiden Sopimusten kehittäjille. 21 | 2. Tarkastusten maksaminen ennen uusien Älykkäiden Sopimusten käyttöönottoa Morpheus-verkossa. 22 | 3. Käyttäjien menetykset MOR:issa tai stETH:issa tapauksessa, jossa Morpheus-Älykäs Sopimus on hyödynnetty. 23 | 4. Korvaaminen tarjoajille, jotka eivät saaneet MOR-päästöjä Morpheus-Älykkään Sopimuksen epäonnistuessa. 24 | 25 | Suojarahastosta maksettavien summien tulee olla suhteessa bugeihin, menetyksiin tai päästövirheisiin. 26 | 27 | ## Keskeytysolosuhteet Älykkäille Sopimuksille 28 | 29 | Ennen vahinkojen maksamista on oltava ehdot, jotka laukaisevat Älykkäiden Sopimusten keskeytyksen jatkuvan hyökkäyksen tapauksessa. 30 | 31 | ## Merkintä & Mekanismi Maksun Suorittamiseksi 32 | 33 | Koodin Tarjoajat osallistuvat merkintään, kun maksu tulisi laukaista. Ensin tapaus yksityiskohtaisesti ja julkaistaan GitHub-varastossa vaikuttavan Älykkään Sopimuksen. Sisältää luettelon vaikutetuista osoitteista ja MOR: n ja / tai stETH: n määristä. 34 | 35 | Jos enemmistö Koodin Tarjoajista (mitattuna heidän MOR-tokensa painolla) osallistuu Merkintäjaksoon (ei kauemmin kuin 7 päivää), vahvistavatko raportin TODELLISEKSI, niin maksu laukaistaan. 36 | 37 | Kun maksu on laukaistu, ohjelmisto lähettää kehittäjille viestin, jotta maksu voidaan hyväksyä vaikutetuille osoitteille määritetyissä määrissä. 38 | 39 | ## Suunnitelma Merkittävän Tappion Tapahtumassa 40 | 41 | Merkittävä Tappiotapahtuma määritellään tapahtumaksi, jossa MOR-menetykset ylittävät Suojarahaston kokonaisresurssit. Tässä tapauksessa sen sijaan, että maksettaisiin MOR:ia, Koodin Tarjoajien tulisi ottaa käyttöön uudet Älykkäät Sopimukset ja korjata MOR-saldot manuaalisesti. Tämä aiheuttaisi käytännössä kovan haaran koodissa / MOR-saldoissa, ja kaikkien Tarjoajien, tokenien haltijoiden ja muiden infrastruktuuritarjoajien olisi päivitettävä koodinsa uusiin Älykkäisiin Sopimuksiin. 42 | 43 | stETH: n menetyksen tapauksessa Merkkirahasto maksaa mahdollisimman suuren osan pro rata -perusteella kunkin henkilön menetyksistä. 44 | 45 | ## Johtopäätös 46 | 47 | Bugeja ja virheitä ohjelmistossa esiintyy todellisuudessa ja merkitsevät historiaa kahdesta tahattomasta Bitcoinin kovasta haaraantumisesta The DAO: han Ethereumin varhaisina päivinä. 48 | 49 | Joten erilaisten skenaarioiden ja tapausten suunnittelu ja niiden käsittelytapa on viisas lähestymistapa riskien suojaamiseksi ja muuten lieventämiseksi. Onneksi varojen varaaminen etukäteen Suojarahastoon ja myös osan suojarahaston ansaitsemisesta LP-palkkioissa AMM:ssä resurssit, jotka on omistettu käyttäjien suojaamiselle, tulisi kasvaa ajan myötä. 50 | -------------------------------------------------------------------------------- /Archive/Translations/French/Morpheus Windows Install Guide French.md: -------------------------------------------------------------------------------- 1 | ## Guide d'installation de Morpheus sur Windows 2 | 3 | 4 | 5 | > [!NOTE] 6 | > Ce guide détaillé vous accompagne pas à pas dans l'installation de Morpheus. 7 | 8 | ### Étape 1 : Installation de WSL2 9 | Ouvrez une invite de commandes en mode administrateur. \ 10 | Exécutez la commande suivante : `wsl --install` \ 11 | Une fois l'installation terminée, lancez WSL2 en tapant `wsl` dans l'invite de commandes, puis suivez les étapes de configuration indiquées. 12 | 13 | ### Étape 2 : Installation d'Ollama 14 | Dans l'interface de WSL2, exécutez la commande suivante pour installer Ollama : `curl https://ollama.ai/install.sh | sh` 15 | 16 | ### Étape 3 : Installation de Python 17 | 18 | Mettez à jour la liste des paquets avec la commande : `sudo apt-get update` \ 19 | Installez Python en exécutant : `sudo apt-get install python3` 20 | 21 | ### Étape 4 : Installation de gdown 22 | Installez gdown à l'aide de pip3 : `pip3 install gdown`. 23 | 24 | ### Étape 5 : Téléchargement de Morpheus 25 | Téléchargez le paquet Morpheus en exécutant : `gdown https://drive.google.com/uc?id=1PQ3n7LXeJHe_jmkYLDUQ9fWjZQTWbHCB` 26 | 27 | ### Étape 6 : Vérification de l'intégrité de Morpheus 28 | Vérifiez l'intégrité du téléchargement avec la commande : `sha1sum morpheus_0.0.5_amd64.deb` \ 29 | Assurez-vous que le hachage correspond à `b227e7bcb21ec9e8e2b4bf9510a2e1f224953fe5` \ 30 | Si le hachage ne correspond pas, interrompez le processus d'installation. 31 | 32 | ### Étape 7 : Installation de Morpheus 33 | Installez Morpheus avec la commande : `sudo dpkg -i morpheus_0.0.5_amd64.deb` \ 34 | Si l'installation échoue initialement en raison de dépendances manquantes, installez les dépendances nécessaires et réessayez. 35 | 36 | ### Étape 8 : Lancement de Morpheus et Ollama 37 | Ouvrez deux fenêtres WSL2 en tapant `wsl` dans deux fenêtres d'invite de commandes différentes. \ 38 | Dans l'une d'elles, lancez Ollama avec la commande : `ollama serve` \ 39 | Dans l'autre, exécutez Morpheus avec la commande : `morpheus` une fois que le processus `ollama serve` est actif. 40 | -------------------------------------------------------------------------------- /Archive/Translations/French/Protection Fund Details French.md: -------------------------------------------------------------------------------- 1 | # Proposition du Fonds de Protection Morpheus 2 | 3 | ## Introduction 4 | Dans le livre blanc de Morpheus, 4 % de l'émission totale de MOR sont alloués à la création d'un "Fonds de Protection" et sont délégués aux fournisseurs de code qui agissent comme des oracles lorsque leurs ressources sont nécessaires. 5 | 6 | #### Les types d'actions incluent : 7 | - Récompenser la découverte de bugs ou de vulnérabilités pour prévenir les attaques. 8 | - Payer pour des audits avant de déployer de nouveaux contrats intelligents. 9 | - Arrêter les contrats intelligents en cas d'attaque. 10 | - Évaluer les dommages et mettre en place un mécanisme de compensation après une attaque. 11 | - Planifier pour des pertes significatives (scénario de hard fork). 12 | 13 | ## Cas Prédéfinis pour des Paiements Mineurs 14 | Avant que les contrats intelligents soient lancés sur le réseau Ethereum, les conditions sous lesquelles le Fonds de Protection effectuera des paiements en MOR ou stETH sont définies. 15 | 16 | ## Types de Paiements : 17 | 1. Bugs découverts et divulgués de manière responsable aux développeurs de contrats intelligents de Capital, Calcul, Code, Communauté et du Fonds de Protection. 18 | 2. Paiement pour des audits avant de déployer de nouveaux contrats intelligents sur le réseau Morpheus. 19 | 3. Pertes des utilisateurs de MOR ou sETH dues à des bugs dans les contrats intelligents de Morpheus. 20 | 4. Paiements dans les cas où les participants n'ont pas reçu l'émission de MOR en raison de défaillances des contrats intelligents de Morpheus. 21 | 22 | Les paiements du fonds de protection devraient être proportionnels à l'erreur, à la perte ou à l'erreur d'émission. 23 | 24 | ## Conditions pour Arrêter les Contrats Intelligents 25 | Avant de déterminer les paiements pour la compensation des dommages, les conditions qui déclenchent l'arrêt des contrats intelligents en cas d'attaque en cours doivent être établies. 26 | 27 | ## Évaluation des Dommages et Mécanisme de Paiement 28 | Les fournisseurs de code participeront à l'évaluation des dommages nécessaire pour la compensation. D'abord, l'incident sera détaillé et publié dans le dépôt GitHub du contrat intelligent affecté, incluant une liste des adresses affectées et les montants de MOR et/ou stETH. 29 | 30 | Si la majorité des fournisseurs de code (mesurée par le poids de leurs tokens MOR détenus), participant à l'évaluation des dommages (pas plus de 7 jours), confirme le rapport comme VRAI, un paiement sera initié. 31 | 32 | Une fois le paiement initié, le logiciel enverra un message aux développeurs demandant l'autorisation du paiement aux adresses affectées dans les montants spécifiés. 33 | 34 | ## Plan en Cas de Dommages Substantiels 35 | Une perte substantielle est définie comme un événement où les pertes de MOR dépassent les ressources totales du Fonds de Protection. Dans ce cas, au lieu de paiements en MOR, les fournisseurs de code doivent déployer de nouveaux contrats intelligents et ajuster manuellement les soldes de MOR affectés. Cela déclenchera effectivement un hard fork du code/solde de MOR, et tous les fournisseurs, détenteurs de tokens et autres fournisseurs d'infrastructure devront mettre à jour leur code vers les nouveaux contrats intelligents. 36 | 37 | En cas de perte de stETH due à des dommages significatifs, le Fonds de Protection paiera le montant maximal possible sur une base proportionnelle en tenant compte des dommages de chaque personne. 38 | 39 | ## Conclusion 40 | Les bugs et les erreurs dans les logiciels sont une réalité, marquée dans l'histoire depuis les deux hard forks involontaires dans Bitcoin jusqu'à The DAO dans les premiers jours d'Ethereum. 41 | 42 | Ainsi, planifier pour divers scénarios et cas et comment y faire face à l'avance est une approche judicieuse pour la protection et l'atténuation des risques. Heureusement, grâce aux ressources pré-allouées dans le Fonds de Protection, ainsi qu'à une partie du fonds qui génère des revenus à travers des récompenses de commission pour la fourniture de liquidité dans AMM, les ressources allouées pour la protection des utilisateurs augmenteront au fil du temps. 43 | -------------------------------------------------------------------------------- /Archive/Translations/German/Morpheus Windows Install Guide German.md: -------------------------------------------------------------------------------- 1 | ## Installieren von Morpheus unter Windows 2 | 3 | - Installieren Sie zunächst WSL2, indem Sie `wsl --install` in einer Admin-Eingabeaufforderung. Öffnen Sie dann WSL2 mit `wsl` und folgen Sie dem Setup-Prozess. 4 | 5 | - Dann laufen `curl https://ollama.ai/install.sh | sh` um ollama zu installieren. 6 | 7 | - Dann installieren Sie Python, indem Sie `sudo apt-get update` und `sudo apt-get install python3`. 8 | 9 | - Dann laufen `pip3 install gdown`. 10 | 11 | - Laden Sie nun das Morpheus dpkg herunter, indem Sie `gdown https://drive.google.com/uc?id=1PQ3n7LXeJHe_jmkYLDUQ9fWjZQTWbHCB`. 12 | 13 | - Überprüfen Sie die Integrität des Herunterladens von Morpheus durch `sha1sum morpheus_0.0.5_amd64.deb`. sicherstellen, dass sie mit dem Hash übereinstimmt `b227e7bcb21ec9e8e2b4bf9510a2e1f224953fe5`, sonst brechen Sie den Installationsvorgang ab. 14 | 15 | - Dann laufen `sudo dpkg -i morpheus_0.0.5_amd64.deb`, Wenn die Installation zunächst fehlschlägt, installieren Sie die Abhängigkeiten, und versuchen Sie es erneut. 16 | 17 | - Sobald Morpheus ohne Abhängigkeitsfehler installiert ist, öffnen Sie 2 WSL2-Fenster, indem Sie 2 Kommandozeilenfenster öffnen und in beiden wsl eingeben, dann führen Sie in einem davon `ollama serve` und im anderen `morpheus` aus. 18 | 19 | -------------------------------------------------------------------------------- /Archive/Translations/German/Protection Fund Details German.md: -------------------------------------------------------------------------------- 1 | # Vorschlag für einen Morpheus-Schutzfonds 2 | 3 | ## Einführung 4 | Das Morpheus-Weißbuch sieht 4 % aller MOR-Emissionen für einen "Schutzfonds" vor und überträgt den Anbietern von Kodizes die Aufgabe, als Orakel zu fungieren, falls die Mittel benötigt werden. 5 | Art der Maßnahmen: 6 | - Zahlung von Bug Bounty zur Vermeidung von Angriffen. 7 | - Zahlung von Audits, bevor neue Smart Contracts eingesetzt werden. 8 | - Anhalten der Smart Contracts im Falle eines laufenden Angriffs. 9 | - Signalisierung und Mechansim für die Auszahlung nach einem Angriff. 10 | - Plan im Falle eines signifikanten Verlustes (Hard Fork Szenario) 11 | 12 | ## Vordefinierte Fälle, die geringfügige Auszahlungen auslösen 13 | Bevor die Smart Contracts im Ethereum-Netzwerk live gehen, werden hier die Bedingungen definiert, unter denen der Schutzfonds MOR oder stETH auszahlt. 14 | 15 | ## Arten von Zahlungen: 16 | 1. Fehler, die entdeckt und den Entwicklern eines Morpheus Capital-, Code-, Berechnungs-, Gemeinschafts- oder Schutzfonds-Smart Contracts verantwortungsvoll mitgeteilt werden. 17 | 2. Zahlung von Audits, bevor neue Smart Contracts im Morpheus-Netzwerk eingesetzt werden. 18 | 3. Nutzerverluste von MOR oder stETH im Falle eines ausgenutzten Morpheus Smart Contracts. 19 | 4. Entschädigung von Anbietern, die keine MOR-Emissionen erhalten haben, im Falle eines Ausfalls des Morpheus-Smart-Contracts. 20 | 21 | Die Höhe der Zahlungen aus dem Schutzfonds sollte im Verhältnis zu dem Fehler, dem Verlust oder der Emission stehen. 22 | 23 | ## Haltebedingungen für Smart Contracts 24 | Bevor Zahlungen für Schäden in Betracht gezogen werden können, sollten Bedingungen festgelegt werden, die im Falle eines laufenden Angriffs einen Stopp der Smart Contracts auslösen. 25 | 26 | ## Signalisierung und Mechanismus der Auszahlung 27 | Code-Anbieter werden sich an der Signalisierung beteiligen, wenn eine Zahlung ausgelöst werden soll. Zunächst wird ein Vorfall detailliert beschrieben und auf dem GitHub-Repository des betroffenen Smart Contracts veröffentlicht. Dazu gehört eine Liste der betroffenen Adressen und Beträge von MOR und/oder stETH. 28 | 29 | Wenn eine Mehrheit der Anbieter von Codes (gemessen am Gewicht der von ihnen gehaltenen MOR-Tokens), die an der Signalisierungsperiode (nicht länger als 7 Tage) teilnehmen, den Bericht als WAHR bestätigt, wird eine Zahlung ausgelöst. 30 | 31 | Sobald eine Zahlung ausgelöst wird, benachrichtigt das Programm die Entwickler, um eine Zahlung an die betroffenen Adressen in der angegebenen Höhe zu genehmigen. 32 | 33 | ## Plan für den Fall eines bedeutenden Schadensereignisses 34 | Ein signifikantes Verlustereignis ist definiert als ein Ereignis, bei dem die MOR-Verluste die Gesamtressourcen des Schutzfonds übersteigen. In diesem Fall sollten die Anbieter von Code statt einer Auszahlung von MOR neue Smart Contracts einführen und die betroffenen MOR-Salden manuell korrigieren. Dies würde zu einem Hard Fork der Code-/MOR-Salden führen und alle Anbieter, Token-Hodler und andere Infrastrukturanbieter müssten ihren Code auf die neuen Smart Contracts aktualisieren. 35 | 36 | Im Falle von StETH, das bei einem bedeutenden Schadensereignis verloren geht, zahlt der Schutzfonds so weit wie möglich anteilig zur Höhe der Verluste jeder Person aus. 37 | 38 | ## Schlussfolgerung 39 | Bugs und Fehler in Programmen sind eine Realität und kennzeichnen die Geschichte von den beiden unbeabsichtigten Hard Forks von Bitcoin bis hin zu The DAO in den frühen Tagen von Ethereum. 40 | 41 | Daher ist es klug, verschiedene Szenarien und Fälle vorauszuplanen und zu wissen, wie damit umzugehen ist, um sich vor Risiken zu schützen und diese zu mindern. Glücklicherweise dürften die für den Schutz der Nutzer bereitgestellten Mittel mit der Zeit größer werden, da mit dem Schutzfonds im Voraus Mittel zurückgelegt wurden und ein Teil des Schutzfonds auch LP-Belohnungen in der AMM einbringt. 42 | -------------------------------------------------------------------------------- /Archive/Translations/Greek/Protection Fund Details Greek.md: -------------------------------------------------------------------------------- 1 | # Πρόταση Ταμείου Προστασίας Morpheus 2 | 3 | ## Εισαγωγή 4 | 5 | Το λευκό βιβλίο του Morpheus δεσμεύει το 4% όλων των εκπομπών MOR για τον σκοπό ενός "Ταμείου Προστασίας" και αναθέτει στους Παρόχους Κώδικα να ενεργήσουν ως οράματα στην περίπτωση που οι πόροι του χρειάζονται. 6 | Τύποι ενεργειών: 7 | 8 | - Πληρωμή ανταμοιβής για εύρεση ελαττωμάτων για την αποφυγή επιθέσεων. 9 | - Πληρωμή ελέγχων πριν από την αναπτυξη νέων Έξυπνων Συμβολαίων. 10 | - Διακοπή των Έξυπνων Συμβολαίων σε περίπτωση επίθεσης που εξελίσσεται. 11 | - Σήμανση και μηχανισμός αποζημίωσης μετά από μια επίθεση. 12 | - Σχέδιο σε περίπτωση σημαντικού γεγονότος απώλειας (Σενάριο Σκληρής Διακοπής Αλυσίδας) 13 | 14 | ## Προκαθορισμένες Περιπτώσεις που Ενεργοποιούν Μικρές Αποζημιώσεις 15 | 16 | Πριν τα Έξυπνα Συμβόλαια γίνουν ζωντανά στο δίκτυο Ethereum, καθορίζονται εδώ οι συνθήκες υπό τις οποίες το Ταμείο Προστασίας θα πληρώσει MOR ή stETH. 17 | 18 | ## Τύποι Πληρωμών: 19 | 20 | 1. Ευρεση ελαττωμάτων και ευθύνη δημοσιοποίησης στους προγραμματιστές ενός Έξυπνου Συμβολαίου Morpheus Capital, Code, Compute, Community ή Protection Fund. 21 | 2. Πληρωμή ελέγχων πριν από την αναπτυξη νέων Έξυπνων Συμβολαίων στο δίκτυο Morpheus. 22 | 3. Απώλειες χρηστών MOR ή stETH σε περίπτωση εκμετάλλευσης Έξυπνου Συμβολαίου Morpheus. 23 | 4. Αποκατάσταση παρόχων που δεν έλαβαν εκπομπές MOR σε περίπτωση αποτυχίας του Έξυπνου Συμβολαίου Morpheus. 24 | 25 | Οι ποσότητες των πληρωμών από το ταμείο προστασίας πρέπει να είναι ανάλογες με το σφάλμα, την απώλεια ή το σφάλμα εκπομπής. 26 | 27 | ## Συνθήκες Διακοπής για Έξυπνα Συμβόλαια 28 | 29 | Πριν τα πληρωμής για ζημίες μπορέσουν να διευθετηθούν, πρέπει να υπάρχουν συνθήκες που ενεργοποιούν μια διακοπή των Έξυπνων Συμβολαίων σε περίπτωση επίθεσης που εξελίσσεται. 30 | 31 | ## Σήμανση & Μηχανισμός Πληρωμής 32 | 33 | Οι Παρόχοι Κώδικα θα συμμετέχουν στη σήμανση όταν πρέπει να ενεργοποιηθεί μια πληρωμή. Αρχικά, 34 | -------------------------------------------------------------------------------- /Archive/Translations/Hindi/Protection Fund Details Hindi.md: -------------------------------------------------------------------------------- 1 | # Morpheus संरक्षण कोष प्रस्ताव 2 | 3 | ## परिचय 4 | 5 | मॉर्फियस सफेद पेपर के अनुसार, सभी एमओआर इमिशन्स का 4% एक "संरक्षण कोष" के लिए निर्धारित किया गया है और उसके संसाधकों को उसके संसाधनों की आवश्यकता के मामले में ऑरेकल के रूप में कार्रवाई करने के लिए सौंपा गया है। 6 | क्रिया के प्रकार: 7 | 8 | - हमलों से बचने के लिए बग बाउंटी का भुगतान। 9 | - नए स्मार्ट कॉन्ट्रैक्ट को डिप्लॉय करने से पहले ऑडिट का भुगतान। 10 | - एक चल रहे हमले के मामले में स्मार्ट कॉन्ट्रैक्ट को रोकना। 11 | - हमले के बाद पेआउट के लिए संकेतन और तंत्र। 12 | - अहम हानि घटना के मामले में योजना (हार्ड फोर्क स्थिति) 13 | 14 | ## पूर्व-निर्धारित मामले मामलों को छोटे पेआउट को ट्रिगर करने 15 | 16 | एथेरियम नेटवर्क पर स्मार्ट कॉन्ट्रैक्ट्स जीवन जीने से पहले यहां पर परिभाषित हैं शर्तें जिनके तहत संरक्षण कोष MOR या stETH का भुगतान करेगा। 17 | 18 | ## भुगतान के प्रकार: 19 | 20 | 1. बग्स का खोज और उन्हें जिम्मेदारीपूर्वक संबंधित स्मार्ट कॉन्ट्रैक्ट के विकासकों को बताया जाता है। 21 | 2. एमॉर्फियस नेटवर्क पर नए स्मार्ट कॉन्ट्रैक्ट को डिप्लॉय करने से पहले ऑडिट का भुगतान। 22 | 3. एक उत्पीडित मॉर्फियस स्मार्ट कॉन्ट्रैक्ट के मामले में MOR या stETH के उपयोगकर्ता हानियों। 23 | 4. मॉर्फियस स्मार्ट कॉन्ट्रैक्ट की असफलता के मामले में जो प्रदाताओं को MOR इमिशन नहीं मिले, उन्हें पूरा करना। 24 | 25 | संरक्षण कोष से भुगतानों की राशि बग, हानि या इमिशन त्रुटि के अनुपात में होनी चाहिए। 26 | 27 | ## स्मार्ट कॉन्ट्रैक्ट्स के लिए ठहराव शर्तें 28 | 29 | नुकसान के लिए भुगतानों से पहले, एक हमले के मामले में स्मार्ट कॉन्ट्रैक्ट्स को रोकने की शर्तें होनी चाहिए। 30 | 31 | ## संकेतन और पेआउट के लिए तंत्र 32 | 33 | कोड प्रदाताओं को संकेतन में हिस्सा लेना होगा जब एक भुगतान ट्रिगर होना चाहिए। सबसे पहले, घटना को विस्तृत रूप से विवरण और प्रभावित स्मार्ट कॉन्ट्रैक्ट के GitHub भंडार में पोस्ट किया जाएगा। जिसमें प्रभावित 34 | -------------------------------------------------------------------------------- /Archive/Translations/Hungarian/Protection Fund Details Hungarian.md: -------------------------------------------------------------------------------- 1 | # Morpheus Védelmi Alapjavaslat 2 | 3 | ## Bevezetés 4 | 5 | A Morpheus fehér könyv 4%-át minden MOR kibocsátás céljára "Védelmi Alapnak" szánja, és feladata a Kód Szolgáltatóknak, hogy az eszközeik szükség esetén szerepeljenek az oracle-ként. 6 | Cselekvéstípusok: 7 | 8 | - Buggelvédelmi jutalom kifizetése a támadások elkerülése érdekében. 9 | - Auditok kifizetése az új Smart Contracts telepítése előtt. 10 | - A Smart Contracts leállítása, ha folyamatban van egy támadás. 11 | - Jelzés és Kifizetési mechanizmus egy támadás után. 12 | - Terv jelentős veszteség esetén (Hard Fork Szcenárió) 13 | 14 | ## Előre meghatározott esetek, amelyek kisebb kifizetéseket indítanak 15 | 16 | Mielőtt a Smart Contracts élővé válnának az Ethereum hálózaton, itt vannak a Védelmi Alapnak a MOR vagy stETH kifizetéseiről szóló feltételek. 17 | 18 | ## Fizetés típusai: 19 | 20 | 1. Buggok felfedezése és felelős módon történő közzététele a Morpheus Capital, Kód, Számítás, Közösség vagy Védelmi Alap Smart Contract fejlesztői számára. 21 | 2. Auditok kifizetése az új Smart Contracts telepítése előtt a Morpheus hálózaton. 22 | 3. Felhasználói veszteségek MOR vagy stETH esetén egy kihasznált Morpheus Smart Contract esetén. 23 | 4. A szolgáltatók teljes mértékben történő kifizetése, akik nem kaptak MOR kibocsátást a Morpheus Smart Contract meghibásodása esetén. 24 | 25 | A védelmi alapból történő kifizetések összegei arányosak legyenek a hibák, veszteségek vagy kibocsátási hibák mértékével. 26 | 27 | ## Smart Contracts leállítási feltételek 28 | 29 | Mielőtt a kártérítési összegeket megállapítanák, olyan feltételeknek kell lenniük, amelyek leállítják a Smart Contracteket egy folyamatban lévő támadás esetén. 30 | 31 | ## Jelzés és Kifizetési mechanizmus 32 | 33 | A Kód Szolgáltatók részt vesznek a jelzésben, amikor a kifizetésnek jelzettnek kell lennie. Először egy incidensről részletes leírást és posztot tesznek közzé az érintett Smart Contract GitHub tárolójában. Tartalmaz egy érintett címek és MOR és / vagy stETH összegek listáját. 34 | 35 | Ha a Kód Szolgáltatók többsége (a birtokolt MOR tokenek súlya által mérve), akik részt vesznek a Jelző időszakban (legfeljebb 7 napig) megerősítik a jelentést IGAZNAK, akkor a kifizetés megtörténik. 36 | 37 | Amint a kifizetés megtörténik, a szoftver üzenetet küld a fejlesztőknek a megfelelő összegekkel rendelkező érintett címekre történő kifizetéshez. 38 | 39 | ## Terv jelentős veszteség esetén 40 | 41 | Egy Jelentős Veszteség Eseményt úgy határoztak meg, hogy az MOR vesztesége meghaladja a Védelmi Alap összes erőforrását. Ebben az esetben a Kód Szolgáltatóknak nem az MOR kifizetése lesz a cél, hanem új Smart Contractsokat kell telepíteniük és a MOR egyenlegeket kézzel kell helyreállítaniuk. Ez gyakorlatilag egy hard forkot okozna a kódban / MOR egyenlegekben, és az összes Szolgáltató, token tulajdonos és egyéb infrastruktúra szolgáltatóknak frissíteniük kellene a kódjukat az új Smart Contractsokhoz. 42 | 43 | Ha a stETH elveszik egy Jelentős Vesztési Eseményben, akkor a Védelmi Alapnak a lehető legnagyobb mértékben kifizetnie kell pro-rata alapon minden személy veszteségének összegét. 44 | 45 | ## Következtetés 46 | 47 | A szoftverekben található hibák és hibák valóságot képviselnek, és megjelölik a történelmet a Bitcoin két szándéktalan hard forkjától az Ethereum kezdeti napjaiban lévő The DAO-ig. 48 | 49 | Ezért előre tervezni a különböző forgatókönyveket és eseteket, valamint azt, hogyan kell kezelni őket, bölcs megközelítés a védekezés és a kockázatok egyéb csökkentése érdekében. Szerencsére előre elkülönített erőforrások állnak rendelkezésre a Védelmi Alapban, és a védelmi alap egy része LP jutalmakat is kap az AMM-ben, az idő múlásával a felhasználók védelmére szolgáló erőforrásoknak növekednie kellene. 50 | -------------------------------------------------------------------------------- /Archive/Translations/Indonesian/Protection Fund Details Indonesian.md: -------------------------------------------------------------------------------- 1 | # Usulan Dana Proteksi Morpheus 2 | 3 | ## Pendahuluan 4 | 5 | White paper Morpheus menetapkan 4% dari semua emisi MOR untuk tujuan "Dana Proteksi" dan menugaskan kepada Penyedia Kode untuk bertindak sebagai orakel dalam kasus sumber dayanya diperlukan. 6 | Jenis tindakan: 7 | 8 | - Pembayaran hadiah bug untuk menghindari serangan. 9 | - Pembayaran audit sebelum kontrak pintar baru diimplementasikan. 10 | - Menghentikan kontrak pintar dalam kasus serangan yang sedang berlangsung. 11 | - Sinyal dan Mekanisme untuk pembayaran setelah serangan. 12 | - Rencana dalam Kasus Kehilangan Event Penting (Skenario Fork Keras) 13 | 14 | ## Kasus-Kasus Pre-Definisi yang Memicu Pembayaran Kecil 15 | 16 | Sebelum Kontrak Pintar aktif di jaringan Ethereum, di sini ditentukan kondisi di mana Dana Proteksi akan membayar MOR atau stETH. 17 | 18 | ## Jenis Pembayaran: 19 | 20 | 1. Bug yang ditemukan dan secara bertanggung jawab diungkapkan kepada pengembang Kontrak Pintar Morpheus Capital, Kode, Compute, Komunitas atau Dana Proteksi. 21 | 2. Pembayaran audit sebelum kontrak pintar baru diimplementasikan di jaringan Morpheus. 22 | 3. Kerugian pengguna dari MOR atau stETH dalam kasus Kontrak Pintar Morpheus dieksploitasi. 23 | 4. Mengembalikan penyedia yang tidak menerima emisi MOR dalam kasus kegagalan Kontrak Pintar Morpheus. 24 | 25 | Jumlah pembayaran dari dana proteksi harus sebanding dengan bug, kerugian, atau kesalahan emisi. 26 | 27 | ## Kondisi Penghentian untuk Kontrak Pintar 28 | 29 | Sebelum pembayaran kerusakan dapat dihitung, harus ada kondisi yang memicu penghentian Kontrak Pintar dalam kasus serangan yang sedang berlangsung. 30 | 31 | ## Sinyal & Mekanisme untuk Pembayaran 32 | 33 | Penyedia Kode akan berpartisipasi dalam memberi sinyal kapan pembayaran harus dipicu. Pertama, insiden akan dijelaskan dan diposting di repositori GitHub Kontrak Pintar yang terkena dampak. Termasuk daftar alamat yang terkena dampak dan jumlah MOR dan / atau stETH. 34 | 35 | Jika sebagian besar Penyedia Kode (sebagaimana diukur berdasarkan bobot token MOR yang mereka pegang) yang berpartisipasi dalam periode Sinyal (tidak lebih dari 7 hari) memvalidasi laporan sebagai BENAR maka pembayaran akan dipicu. 36 | 37 | Setelah pembayaran dipicu, perangkat lunak akan mengirim pesan kepada pengembang untuk mengotorisasi pembayaran ke alamat yang terkena dampak sesuai dengan jumlah yang ditentukan. 38 | 39 | ## Rencana dalam Kasus Event Kehilangan yang Signifikan 40 | 41 | Event Kehilangan yang Signifikan didefinisikan sebagai event di mana kerugian MOR melebihi total sumber daya Dana Proteksi. Dalam hal ini, daripada melakukan pembayaran MOR, Penyedia Kode harus menerapkan Kontrak Pintar baru dan memperbaiki saldo MOR yang terkena dampak secara manual. Ini efektif akan menyebabkan fork keras dalam kode / saldo MOR dan semua Penyedia, pemegang token, dan penyedia infrastruktur lainnya harus memperbarui kode mereka ke Kontrak Pintar baru. 42 | 43 | Dalam kasus stETH yang hilang dalam Event Kehilangan yang Signifikan, Dana Proteksi harus membayar sebanyak mungkin secara proporsional terhadap jumlah kerugian setiap orang. 44 | 45 | ## Kesimpulan 46 | 47 | Bug dan kesalahan dalam perangkat lunak adalah kenyataan dan menandai sejarah dari dua fork keras tidak disengaja dari Bitcoin hingga The DAO selama masa awal Ethereum. 48 | 49 | Jadi merencanakan ke depan untuk skenario dan kasus yang berbeda dan bagaimana cara mengatasinya adalah pendekatan yang bijaksana untuk melindungi dan mengurangi risiko. Untungnya, dengan menyisihkan sumber daya di muka dengan Dana Proteksi, dan juga bagian dari dana proteksi yang mendapatkan hadiah LP dalam AMM, sumber daya yang ditujukan untuk perlindungan pengguna harus tumbuh lebih besar dari waktu ke waktu. 50 | -------------------------------------------------------------------------------- /Archive/Translations/Japanese/Mastery of Tokenomics Japanese.md: -------------------------------------------------------------------------------- 1 | # Morpheus トークンエコノミクスの深い探求 2 | ## 紹介： 3 | トークンエコノミクスは、Web3プロジェクトの支柱であり、それらのダイナミクスと利点を形作っています。ビットコインを起点としたトークンエコノミクスの進化の旅は、その重要な役割を明らかにしました。 4 | 時を経て進化するトークンエコノミクスモデル： 5 | - **ビットコイン時代:** ビットコインは分散型通貨を導入し、供給の制限と作業証明によって希少性と価値を強調しました。 6 | - **イーサリアムとスマートコントラクト:** イーサリアムはトークンエコノミクスを拡張し、スマートコントラクトによるプログラム可能な資産を実現し、トークン化のトレンドを牽引しました。 7 | - **DeFiとガバナンストークン:** DeFi内のガバナンストークンは、ユーザーにプロトコルの意思決定権を与えるトークンの能力を示しています。 8 | - **NFTs:** NFTの台頭は、トークンが金融応用に限らず多機能性を持つことを示しました。 9 | - **RWA（実世界資産）:** 実世界の資産に部分的または完全に依存するトークンエコノミクスのバリエーションです。 10 | 11 | ## 問題点は何ですか？ 12 | 不完全なモデルに影響を受ける課題を探求する際、効果的なトークンエコノミクスの重要性は明らかになり、ユーザー参加度やプロジェクトのビジネスモデル、長期的な持続可能性に影響を与えます。 13 | ユーザーの獲得と保持は課題となります。悪質なトークンエコノミクスは、積極的な参加を妨げ、明確な利点やインセンティブを提供せず、実用性や具体的な価値の欠如によりプロジェクトの魅力が低下します。これは不合理に高いマーケティングコストにもつながります。 14 | トークンエコノミクスの欠陥は、経済の不均衡を引き起こし、価値分配の不公平をもたらし、エコシステム全体の健全性に影響を与える可能性があります。このような場合、ビジネスモデルは機能停止し、プロジェクトの持続可能性が危機にさらされ、結果として終わりのない転換や破産に至る可能性があります。 15 | 16 | ## 解決策はありますか？ 17 | Morpheusはこれらの課題を解決するために包括的なソリューションを提供し、さまざまな要素を相互に組み合わせ、MORトークンを効果的に活用して内部および外部の需要を創出します。 18 | Morpheusのトークンエコノミクスはすべてのモデルの要素を統合しています： 19 | 1. ビットコインからの影響を受け、発行上限を42,000,000に設定し、毎日14,400 MORから始まり、その後は毎日2.468994701 MORずつ減少し、5,833日目（約16年後）に報酬が0に達するまでです。このスケジュールはプロジェクトの成長と一致しており、供給過剰を防止します。 20 | 2. イーサリアムからの影響を受け、スマートコントラクトを使用して透明性を確保し、設定条件を厳守します。 21 | 3. DeFiから借鉴し、トークンエコノミクスはMORトークンを投資ツールとして使用することを可能にし、プロジェクトへの貢献に対する報酬を提供します。 22 | 4. NFTとRWAから借鉴し、MOR保有者はネットワークの計算能力の一部を毎日受け取り、他のプレイヤーカテゴリとのさまざまな操作（報酬を含む）を行うことができます。 23 | 24 | ![meme](https://github.com/antonbosss/fantastic-bassoon/blob/main/tokenomics-doc/meme-tokenomics1.jpg) 25 | 26 | ## Techno Capital Machineトークンエコノミクスエンジン 27 | MorpheusはTechno Capital Machine（TCM）と呼ばれる革新的なトークン配布メカニズムを導入しています。これは、トークンの公正な配布と同時に、プロトコル所有の流動性（POL）を提供するために価値を蓄積します。 28 | 29 | 以下にTCMメカニズムの概要を示します： 30 | 1. キャピタルプロバイダーはstETH（LidoによってステーキングされたEthereum）を預け入れ、収益を生み出し、利益相当するMORトークンを比例して報酬として受け取ります。 31 | 2. Morpheus契約は収益の50％をAMMからMORトークンを購入し、残りの50％を流動性提供に使用します。 32 | 3. MOR保有者はMorpheusの実用機能にアクセスできます。 33 | 34 | **他のガイドおよびトークン発行モデルと比較して、TCMモデルには多くの利点があります：** 35 | - ユーザーは直接資本/元本を提供せずに収益を提供します。 36 | - 恒久的な損失のリスクはありません。 37 | - 収益はMORトークンの需要を持続的に創出します。 38 | - プロトコル所有の流動性は時間とともに成長します。 39 | - このモデルは公平でチェーンに依存しないスケーラブルです。 40 | 41 | ![TCM](https://github.com/antonbosss/fantastic-bassoon/blob/main/tokenomics-doc/TCM-tokenomics.jpg) 42 | 43 | ## エコシステム参加者のインセンティブ 44 | Morpheusには、4つのエコシステム参加者があります。各参加者はMOR発行量の24％を割り当てられます： 45 | - キャピタルプロバイダー。 46 | - コンピューティングプロバイダー。 47 | - コードプロバイダー。 48 | - コミュニティビルダー。 49 | 50 | **キャピタルプロバイダー** はTechno Capital Machineに参加し、収益を生むための資本を提供し、MORトークンのプロトコル所有流動性を推進します。 51 | 52 | ## 翻译 private_upload\default_user\2024-04-15-15-06-41\Mastery of Tokenomics Chinese.md.part-1.md 53 | 54 | **コードプロバイダー** Morpheusのコードの進化およびインテリジェントエージェントの作成に参加します。コードの提供者は、対象のパートナー間でMORの配布量を決定する任意の作業単位である「ウェイト」を要求します。 55 | 56 | **コンピューティングプロバイダー** ネットワークの主要なリソースである計算を提供します。 57 | 58 | **コミュニティプロバイダー/ビルダー** Morpheusの採用を促進するために、主にフロントエンドの開発に取り組んでいます。 59 | 60 | ![tknmcs](https://github.com/antonbosss/fantastic-bassoon/blob/main/tokenomics-doc/tkenmcs.png) 61 | 62 | ## 特別な要素 63 | まず、ユーティリティトークンのアプローチが採用されているため、トークンを所有するだけで使用できるため、トークンの相当部分は動かないウォレットに留まります。新たなユーザーの増加に伴い、価値が向上することから、ネットワーク効果が増加します。 64 | 65 | 公正な開始により、リスク投資家、プライベート投資家、プライベート配布またはプレマインの取得者による売り圧力を回避し、トークンエコノミクスの長期的な持続可能性をさらに確保します。 66 | 67 | MORの破壊機構は、イーサリアムの破壊機能と似ており、時間の経過とともにMORの希少性を確保します。 68 | 69 | その他にも、トークンエコノミクスにおける安定化装置として、ボーナスファンドがあります。このファンドは、発行量の4%を受け取り、予期しないイベントが発生した際の安定性を目的としています。 70 | 71 | ## 結論 72 | Morpheusのトークンエコノミクスは包括的なフレームワークを提供し、トラップを回避し、ユーティリティを考慮しています。主要な貢献者をインセンティブ付けし、相互作用を促進し、公正な市場のダイナミクスを維持することで、Morpheusを分散型領域の持続可能なイノベーターとして確立しています。オープンで透明で公正な性質は、ますます多くの新しいユーザーを引きつける要因です。 73 | 74 | ## 参考文献： 75 | 1. [ホワイトペーパー](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/WhitePaper.md) 76 | 2. [テクノキャピタルマシン論文](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/TechnoCapitalMachineTCM.md) 77 | 3. [保護プランの詳細](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Protection%20Fund%20Details.md) 78 | 79 | -------------------------------------------------------------------------------- /Archive/Translations/Japanese/Morpheus Windows Install Guide japanese.md: -------------------------------------------------------------------------------- 1 | ## WindowsでMorpheusをインストールする方法 2 | 3 | - 最初に、WSL2をインストールする必要があります。次のコマンドを管理者のコマンドプロンプトで実行することで、WSL2をインストールできます: `wsl --install`。その後、WSL2を開き、`wsl`を入力して設定を行ってください。 4 | 5 | - 次に、`curl https://ollama.ai/install.sh | sh`を実行して、ollamaをインストールします。 6 | 7 | - その後、`sudo apt-get update`と`sudo apt-get install python3`を実行して、Pythonをインストールします。 8 | 9 | - そして、`pip3 install gdown`を実行します。 10 | 11 | - これで、morpheusのdpkgをダウンロードできます。次のコマンドを実行してください: `gdown https://drive.google.com/uc?id=1PQ3n7LXeJHe_jmkYLDUQ9fWjZQTWbHCB`。 12 | 13 | - Morpheusのダウンロードファイルの正当性を確認するために、`sha1sum morpheus_0.0.5_amd64.deb`を使用してください。ハッシュ値`b227e7bcb21ec9e8e2b4bf9510a2e1f224953fe5`と一致することを確認してください。一致しない場合は、インストールプロセスを中止してください。 14 | 15 | - 次に、`sudo dpkg -i morpheus_0.0.5_amd64.deb`を実行してください。インストールが最初に失敗した場合は、依存関係をインストールしてから再試行してください。 16 | 17 | - これで、依存関係エラーがなくmorpheusがインストールされている場合は、2つのコマンドラインウィンドウを開き、両方で`wsl`を入力して、2つのWSL2ウィンドウを開いてください。その後、一つのウィンドウで`ollama serve`を実行し、もう一つのウィンドウで`morpheus`を実行してください。 18 | 19 | -------------------------------------------------------------------------------- /Archive/Translations/Japanese/Protection Fund Details Japanese.md: -------------------------------------------------------------------------------- 1 | # Morpheus 保護基金提案 2 | 3 | ## 簡介 4 | 5 | Morpheus ホワイトペーパーによれば、すべての MOR の発行量の4%を「保護基金」として確保し、必要な場合にはコードプロバイダにリソースサポートを委託します。 6 | 操作タイプ： 7 | 8 | - 攻撃を回避するための脆弱性報奨金の支払い。 9 | - 新しいスマートコントラクトのデプロイ前の監査料の支払い。 10 | - 攻撃が継続している間、スマートコントラクトを一時停止する。 11 | - 攻撃後のシグナルと支払いのメカニズム。 12 | - 重大な損失イベント（ハードフォークのシナリオ）の計画。 13 | 14 | ## ファンドからトリガーされる小額の支払いのケース 15 | 16 | イーサリアムネットワーク上でスマートコントラクトがリアルタイムになる前に、MORまたはstETHの支払い条件が保護基金に定義されています。 17 | 18 | ## 支払いタイプ： 19 | 20 | 1. Morpheus キャピタル、コード、計算、コミュニティ、または保護基金スマートコントラクトの開発者に対して、発見した脆弱性を報告します。 21 | 2. Morpheus ネットワークに新しいスマートコントラクトをデプロイする前に監査料を支払います。 22 | 3. Morpheus スマートコントラクトが不正使用された場合、ユーザーがMORまたはstETHを失います。 23 | 4. Morpheus スマートコントラクトの失敗の場合、発行が受け取られなかったプロバイダーを完全に補償します。 24 | 25 | 保護基金からの支払いは、脆弱性、損失、または発行のエラーに比例する必要があります。 26 | 27 | ## スマートコントラクトの一時停止条件 28 | 29 | 損失の支払いを確認する前に、攻撃が継続している場合にはスマートコントラクトを一時停止する条件が必要です。 30 | 31 | ## シグナルと支払いのメカニズム 32 | 33 | コードプロバイダは、支払いがトリガーされた際にシグナルに参加します。まず、イベントは詳細に説明され、影響を受けるスマートコントラクトのGitHubリポジトリに公開されます。影響を受けるアドレスとMORと/またはstETHの金額のリストが含まれます。 34 | 35 | コードプロバイダの大多数（MORトークンの量で測定）がシグナルサイクル（最長7日間）内に参加した場合、報告はTRUEとして確認され、支払いがトリガーされます。 36 | 37 | 支払いがトリガーされた後、ソフトウェアは開発者にメッセージを送信し、影響を受けるアドレスに指定された金額を支払うことを承認します。 38 | 39 | ## 重大な損失イベントシナリオの計画 40 | 41 | 重大な損失イベントは、保護基金の総リソースを超えるMORの損失が発生した場合に定義されます。この場合、コードプロバイダは新しいスマートコントラクトをデプロイし、MORの残高を手動で調整することにより、MORの支払いではなくMORの供給を行います。これにより、コード/MORの残高がハードフォークによって生じ、すべてのプロバイダ、トークン保有者、およびその他のインフラプロバイダは新しいスマートコントラクトにコードを更新する必要があります。 42 | 43 | 重大な損失イベントの場合、stETHに損失が発生した場合、保護基金は各人の損失金額に比例して支払われるべきです。 44 | 45 | ## 結論 46 | 47 | ソフトウェアの脆弱性とエラーは、ビットコインの二度の意図しないハードフォークとイーサリアムの初期のDAOのような過去の事件を示しています。したがって、さまざまなシナリオやケースに備え、それらを処理する方法を事前に計画することは、賢明なリスク管理とリスク軽減の方法です。幸いにも、保護基金にリソースを事前に確保し、AMMでLP報奨金を受け取るための保護基金の一部を確保し、ユーザーの保護のためにリソースを提供することは、時間とともに成長する必要があります。 48 | 49 | ## 翻译 private_upload\default_user\2024-04-15-16-06-32\Protection Fund Details Chinese.md.part-1.md 50 | 51 | # 損失支払を確定する前に、攻撃が続く場合はスマートコントラクトを一時停止するための条件が必要です。 52 | 53 | ## シグナルと支払メカニズム 54 | 55 | 開発者はシグナルがトリガーされたときに支払いに参加します。最初に、イベントは詳細に説明され、関連するスマートコントラクトのGitHubリポジトリに公開されます。影響を受けるアドレスと、影響を受けるMORおよび/またはstETHの金額リストが含まれます。 56 | 57 | ほとんどのコードプロバイダ（MORトークン量に基づいて）が信号サイクル（最長7日間）内で参加する場合、報告はTRUEと確認され、支払いがトリガーされます。 58 | 59 | 支払いがトリガーされた後、ソフトウェアは開発者に対してメッセージを送信し、指定された金額を影響を受けるアドレスに支払うことを承認します。 60 | 61 | ## 重大な損失イベントシナリオの計画 62 | 63 | 重大な損失イベントは、保護基金の総資源を超えるMORの損失が発生するイベントと定義されます。この場合、コードプロバイダは新しいスマートコントラクトを展開し、MORの支払い代わりにMOR残高を手動で調整する必要があります。これにより、コード/MORの残高は実際にはハードフォークが発生し、すべてのプロバイダ、トークン保有者、および他のインフラプロバイダは新しいスマートコントラクトにコードを更新する必要があります。 64 | 65 | 重大な損失イベントでは、stETHの損失が発生した場合、保護基金は各人の損失金額に比例して支払われるべきです。 66 | 67 | ## 結論 68 | 69 | ソフトウェアのバグやエラーは、ビットコインの2回の予期しないハードフォークとイーサリアムの早期のDAOの歴史を示しています。したがって、さまざまな状況とケースに対して準備をし、それらを処理する方法を事前に計画することは、賢明なリスク管理とリスク軽減策です。幸いなことに、保護基金に予めリソースを確保し、AMMでLP報酬を得るための一部の保護基金を提供し、ユーザーの保護にリソースを提供することは、時間の経過とともに増えるべきです。 70 | 71 | -------------------------------------------------------------------------------- /Archive/Translations/Korean/MOREconomics Korean.md: -------------------------------------------------------------------------------- 1 | # MOR 이코노믹스 2 | ## 모든 네트워크는 경제 원칙과 가치에 따라 존폐가 갈린다 3 | 4 | 모피어스는 비트코인 이후로 모든 기능에 대해 순수 자유 시장 접근 방식을 채택한 최초의 네트워크 중 하나입니다. 그리고 그 경제 원리는 개인 자주권, 자발적 시장, 무정부 자본주의를 기본으로 합니다. 5 | 6 | 자유 시장이 스스로 형성될 것이란 믿음은 2023년 9월 익명의 저자들이 제안한 백서를 시작으로 2023년 10월 유저 컴퓨터에 설치할 수 있는 첫 번째 버전의 오픈 소스 모피어스 애플리케이션, 2024년 2월 페어 론칭(Fair Launch)을 위한 스마트 컨트랙트, 그리고 같은 해 5월 MOR 토큰이 출시되면서 증명되었습니다. 7 | 8 | 이처럼 9개월 동안 모피어스는 회사, 팀, 사전 마이닝, CEO, 재단도 없이 생성형 AI 애플리케이션을 위한 강력한 플랫폼을 만들어 냈습니다. 이는 완전한 오픈 소스 스마트 컨트랙트와 P2P 소프트웨어로서 공개적으로 구축하여 누구나 이용할 수 있도록 하였습니다. 9 | 10 | 모피어스의 경제 철학과 진정한 개인용 AI라는 가치는 수백명의 전세계 각지 독립 코더들의 오픈 소스 소프트웨어에 기여하고, 수천명의 자본 기여자들이 이더리움 스테이킹을 통해 수익을 기여하도록 이끌었습니다. 첫 30일 동안 커뮤니티는 100,000 stETH, 미화 3억 달러 (약 4,083억 원)가 넘는 금액을 스테이킹 하였습니다. 자본 제공자의 MOR 배출은 16년 동안 이어집니다. 이는 중력 함정에 빠진 것 처럼 많은 인재와 자본을 끌어들이고 네트워크 효과가 결합되어 더욱 강력해집니다. 11 | 12 | ## 모든 면에 있어 자유 경쟁 시장과 같이 운영되는 프로젝트 13 | 1. 자본 제공자: 유동성 제공에 대한 경쟁 14 | 2. 연산 제공자: 인터페이스 제공에 대한 경쟁 15 | 3. 코더 (개발자): 오픈 소스 제공에 대한 경쟁 16 | 4. 빌더: 유저에게 유용한 스마트 에이전트 제공에 대한 경쟁 17 | 5. 참고 구현 관리자: 인용에 대한 경쟁 18 | 19 | ## 희소성과 수요 예측 가능성이 있는 건전한 경제 (sound economy) 원칙이 포함 20 | - 한정된 42,000,000 MOR 토큰에 대한 경쟁 21 | - MOR 토큰이 16년 동안 방출됨에 따른 공정하고 장기적인 경쟁 22 | - MOR 토큰을 더욱 희소하게 만드는 소각 기능 23 | - 256년 동안 이루어지는 꼬리 방출로 수 세기에 걸쳐 경쟁이 계속됨 24 | 25 | ## 기술적 유용성, 자본 거버넌스 유즈 케이스 포함 26 | - MOR 토큰 홀더는 일일 연산 예산의 비례하는 금액에 액세스 27 | - MOR 홀더는 MOR 수익을 빌더에게 스테이킹 하여 추가적인 토큰 획득 28 | - MOR 홀더는 MOR 수익을 스테이킹 하여 모피어스 개선을 위한 코딩 보상 획득 29 | 30 | ## 테크노 캐피털 머신 포함 31 | 스테이킹 된 이더리움에서 매일 발생하는 수익의 유동성 엔진은 투표나 위원회와 같이 중앙에서 관리되는 것이 아니라 프로토콜 소유 유동성 (Protocol Owned Liquidity)으로 바로 추가됩니다. 구체적으로, ETH 수익의 50%는 유니스왑 풀에서 MOR을 구매하는 데 사용됩니다. 그런 후, 구매한 MOR과 남아 있는 ETH 모두 페어링 되어 모피어스가 소유한 전체 범위의 유동성 포지션에 추가되는데, 이를 프로토콜 소유 유동성이라고 합니다. 이와 같은 설계는 MOR에 대한 안정적인 수요를 제공하는 동시에 유동성을 증가시켜 모든 유저가 MOR 토큰을 더 쉽게 사고, 팔 수 있도록 합니다. 32 | 33 | ## 막을 수 없는 진행과 거대한 규모 34 | 이 요소들의 결합은 글로벌 빌더 커뮤니티가 거대한 규모로 협력 하는 원동력 역할을 해오고 있으며, 이러한 양상은 오직 가속되기만 합니다. 향후 몇 년 안에 우리 각자를 위한 개인용 AI를 지원하는 스마트 에이전트가 경제 활동 대부분을 담당하게 될 때, 모피어스는 ‘Free AI’의 중추가 될 것입니다. 35 | -------------------------------------------------------------------------------- /Archive/Translations/Korean/Morpheus Freedoms Korean.md: -------------------------------------------------------------------------------- 1 | # 모든 이의 자유를 위한 프로젝트, 모피어스 2 | 3 | 모피어스 커뮤니티 안에서 프리 AI를 위해 스테이킹하고 컴퓨팅을 제공하며, 구축 및 코딩을 하는 모든이에게 감사드립니다. 4 | 5 | ## 다음은 모피어스가 지키고자 하는 커뮤니티, 프로젝트와 프리덤 테크의 유형을 상징하는 10가지 가치입니다. 6 | 7 | ## 오픈 소스: 8 | 모피어스의 기반이 되는 소프트웨어 코드는 누구든 자유로이 살펴보고, 편집하며 복사할 수 있어야 합니다. 9 | ## P2P: 10 | 누구나 직접적인 연결이 가능하고, 모든 기능에 있어 중앙화된 중개자가 없는 시스템입니다. 11 | ## 퍼블릭 블록체인: 12 | 모피어스 구성원들의 상호작용을 위한 분산화된 공개형 불변 원장/기록 시스템입니다. 이는 모피어스가 자체 규칙을 따르고 있으며, 시스템 내에서 고도의 투명성을 제공한다는 증거로 삼을 수 있습니다. 13 | ## 소유권의 토큰화: 14 | 모피어스의 참여자 및 스테이크 홀더에게 보상을 지급하는 방법을 제시합니다. 15 | ## 허가 불필요성: 16 | 누구도 모피어스의 공개 기능을 사용하기 위한 승인을 권한자에게 요청할 필요가 없어야 합니다. 17 | ## 자유로운 액세스: 18 | 누구도 모피어스 사용에 있어 애플리케이션 사용이 차단되거나 검열되어서는 안 됩니다. 19 | ## 프라이버시 보호: 20 | 누구도 모피어스 사용을 위해 개인 정보를 노출할 필요가 없어야 합니다. 21 | ## 선택과 탈퇴의 자유: 22 | 모피어스를 탈퇴하거나 다른 모피어스에 참여하기로 선택한 경우, 그 누구도 소프트웨어를 계속해서 실행해야 하거나 다른 방식으로 모피어스에 참여하도록 강요받아서는 안 됩니다. 23 | ## 자기 주권 신원 (SSI: Self Sovereign Identity): 24 | 모든 유저는 자신의 신원을 생성할 수 있는 권리가 있으며, 크리덴셜(credential) 사용에는 유저의 동의가 필요합니다. 25 | ## 연합/결사(Association)의 자유: 26 | 모피어스 멤버는 서로 자유롭게 연합/결사할 수 있어야 합니다. 27 | -------------------------------------------------------------------------------- /Archive/Translations/Korean/Protection Fund Details Korean.md: -------------------------------------------------------------------------------- 1 | # Morpheus 보호 기금 제안 2 | 3 | ## 소개 4 | 5 | Morpheus 백서는 모든 MOR 발행의 4%를 "보호 기금" 용도로 예약하고 필요 시 자원이 필요할 경우 코드 제공자를 신들로 위임합니다. 6 | 동작 유형: 7 | 8 | - 공격을 피하기 위한 버그 바운티 지급. 9 | - 새로운 스마트 컨트랙트를 배포하기 전에 감사 지불. 10 | - 공격이 계속되는 경우 스마트 컨트랙트 중단. 11 | - 공격 후 신호 및 지불 메커니즘. 12 | - 중대한 손실 사건 (하드 포크 시나리오)의 경우 계획. 13 | 14 | ## 사전 정의된 소액 지급을 트리거하는 사례 15 | 16 | 스마트 컨트랙트가 이더리움 네트워크에 라이브로 전환되기 전에 보호 기금이 MOR 또는 stETH를 지불 할 조건이 여기에 정의됩니다. 17 | 18 | ## 지불 유형: 19 | 20 | 1. Morpheus Capital, Code, Compute, Community 또는 보호 기금 스마트 컨트랙트의 개발자에게 발견된 버그를 책임 있게 알려줌. 21 | 2. Morpheus 네트워크에 새로운 스마트 컨트랙트를 배포하기 전에 감사 지불. 22 | 3. Morpheus 스마트 컨트랙트가 악용 된 경우 사용자가 MOR 또는 stETH를 잃는다. 23 | 4. Morpheus 스마트 컨트랙트의 실패의 경우 MOR 발행을받지 못한 제공자를 완전하게 만듭니다. 24 | 25 | 보호 기금에서의 지급 금액은 버그, 손실 또는 발행 오류에 비례해야합니다. 26 | 27 | ## 스마트 컨트랙트를 중단하는 조건 28 | 29 | 손해에 대한 지불이 파악되기 전에, 공격이 계속되는 경우 스마트 컨트랙트를 중단시키는 조건이 있어야합니다. 30 | 31 | ## 신호 및 지불 메커니즘 32 | 33 | 코드 제공자는 지불이 트리거 될 때 신호에 참여합니다. 먼저 사건이 상세히 설명되고 영향을받는 스마트 컨트랙트의 GitHub 저장소에 게시됩니다. 영향을받는 주소 및 MOR 및 / 또는 stETH의 금액 목록을 포함합니다. 34 | 35 | 코드 제공자의 대다수 (MOR 토큰 보유량으로 측정되는)가 신호 주기 (최대 7 일) 동안 참여하면 보고서를 TRUE로 확인하면 지급이 트리거됩니다. 36 | 37 | 지불이 트리거 된 후 소프트웨어는 개발자에게 영향을받는 주소에 지정된 금액으로 지불을 승인하도록 메시지를 보냅니다. 38 | 39 | ## 중대한 손실 사건 시나리오의 경우 계획 40 | 41 | 중대한 손실 사건은 MOR 손실이 보호 기금의 총 자원을 초과하는 사건으로 정의됩니다. 이 경우, MOR의 지급 대신 코드 제공자는 새로운 스마트 컨트랙트를 배포하고 MOR 잔액을 수동으로 수정해야합니다. 이는 사실상 코드 / MOR 잔액에서 하드 포크를 일으키며 모든 제공자, 토큰 보유자 및 기타 인프라 제공자가 새로운 스마트 컨트랙트로 코드를 업데이트해야합니다. 42 | 43 | 중대한 손실 사건에서 stETH가 손실 된 경우 보호 기금은 각 사람의 손실 금액에 비례하여 최대한 지불해야합니다. 44 | 45 | ## 결론 46 | 47 | 소프트웨어에서 발생하는 버그와 오류는 비트 코인의 두 번의 의도하지 않은 하드 포크에서 시작하여 이더리움 초기의 The DAO에 이르기까지 역사를 표시합니다. 48 | 49 | 따라서 다양한 시나리오와 사례에 대비하고 그것들을 어떻게 처리할 것인지 미리 계획하는 것이 위험에 대비하고 그렇지 않으면 위험을 완화하는 지혜로운 접근 방식입니다. 다행히도, 보호 기금에 리소스를 미리 예약하고, 보호 기금의 일부가 AMM에서 LP 보상을 획득하고, 사용자의 보호를 위한 리소스는 시간이 지남에 따라 커져야합니다. 50 | -------------------------------------------------------------------------------- /Archive/Translations/Korean/Top 10 Reasons to be Excited About Morpheus Korean.md: -------------------------------------------------------------------------------- 1 | # 모피어스가 매력적인 10가지 이유 2 | 3 | #### 제프 맥도널드 4 | 5 | #### 2024년 3월 8일 6 | 7 | >“컴퓨팅은 미래의 화폐, 어쩌면 세상에서 가장 값비싼 재화가 될 것이다.” - 샘 알트만 8 | 9 | ## 소개 10 | 최근 모피어스 행사에 참석하고 커뮤니티의 질문에 답하면서 생각해 본 모피어스가 매력적인 점과 당신에게도 매력적일 수 있는 10가지 이유를 소개합니다. 11 | 12 | ## _개발자인 경우_ 13 | ### 1. AI를 위한 모피어스 앱스토어 14 | 모피어스는 컴퓨팅 제공자와 AI 코드를 위한 마켓플레이스 역할을 합니다. 마켓플레이스는 자유 시장 경쟁과 탈중앙화 원칙에 따라 만들어져 중개자나 중앙 통제 없이 기여자에게 직접 보상됩니다. 자유 시장 접근 방식의 모피어스 앱 스토어 상 최적의 모델과 컴퓨팅 제공자는 가장 많은 소비자를 끌어모을 수 있습니다. 15 | 16 | ### 2. 첫 날부터 빌더에게 지급할 수 있는 충분한 자금 17 | 컴퓨팅 파워나 모델을 제공하는 기여자에게는 출시 즉시 보상이 지급됨에 따라 장기간의 마케팅을 하는 수고스러움이나 유저 확보가 불필요합니다. stETH를 스테이킹하는 사람들이 이미 생태계를 활성해 놓았기 때문입니다. 18 | 19 | ### 3. 생태계처럼 확장되지만 스마트 컨트랙트처럼 작동 20 | 모피어스의 탈중앙 컨트랙트는 최소한의 간접비로 생태계 자금을 효율적으로 관리하고 통제합니다. 처음부터 구축하고 유지보수하는데 있어 L1이나 L2만큼 복잡하지 않아 마켓플레이스 모델의 기하급수적인 확장을 가능하게 합니다. 21 | 22 | 더 자세한 정보: [Morpheus Lumerin Model](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Compute%20Providers/Morpheus%20Lumerin%20Model.md#ecosystem-model), [The Morpheus Asset Integration Framework](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Capital%20Providers%2C%20MOR20%2C%20TCM/The%20Morpheus%20Asset%20Integration%20Framework.md) 23 | 24 | ## _투자자인 경우_ 25 | ### 4. 테크노 캐피털 머신 26 | 테크노 캐피털 머신은 기발한 이름을 넘어 [펀드 레이징의 판도를 바꿀 아이디어](https://github.com/MorpheusAIs/Docs/blob/main/Translations/Korean/Techno%20Capital%20Machine%20TCM%20Korean.md)입니다. 투자자는 이더리움 메인 체인 상의 모피어스 컨트랙트에 ETH를 stETH로 예치하여, 매일 MOR을 획득할 수 있습니다. 여기서 가장 매력적인 점은, “Your keys, your coins”이라는 말 들어보셨을 겁니다. 언제라도 stETH를 인출하고 획득한 MOR을 클레임할 수 있습니다. 현재 LIDO stETH의 1% 이상이 이미 모피어스 컨트랙트에 들어있습니다. 27 | 28 | ### 5. 영원히 성장하는 유동성 29 | 코인의 유동성 공급을 위해 언제든지 자금을 인출할 수 있는 기존의 유동성 공급자와는 달리, 모피어스에서는 [커뮤니티가 스테이킹해 발생된 stETH 수익이 유니스왑의 유동성 풀로 바로 전달](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Capital%20Providers%2C%20MOR20%2C%20TCM/Phased%20AMM%20Deployment%20and%20Fair%20Price%20Discovery.md)되어 매일 증가합니다. 이러한 성장은 고래 투자자들에게 매력적인 지표입니다. 30 | 31 | ### 6. 실사용이 가능한 MOR의 유용성 32 | MOR 홀더는 토큰 소유 비율에 따라 [매일 무료 AI 컴퓨팅에 액세스](https://github.com/MorpheusAIs/Docs/blob/main/Translations/Korean/Yellowstone%20Compute%20Model%20Korean.md)할 수 있습니다. MOR을 소유하면 반복적인 수수료 없이도 네트워크의 컴퓨팅 파워에 직접적으로 액세스할 수 있습니다. 33 | 34 | ### 7. 그리고 MOR을 스테이킹할 수 있다는 점 35 | MOR 홀더는 복잡한 4진법 투표 절차, DAO 또는 정치적으로 동요되는 커뮤니티 펀드를 다룰필요 없이 자신이 지지하는 새로운 프로젝트에 [토큰을 스테이킹](https://github.com/MorpheusAIs/Docs/blob/main/Translations/Korean/Techno%20Capital%20Machine%20TCM%20Korean.md)하고 노력에 대한 보상 수령에 따라 직접적으로 투표합니다. 36 | 37 | ## _사업가인 경우_ 38 | ### 8. 커뮤니티가 만들어가는 보상 39 | 모피어스는 모피어스 도입을 확산하는 사람들에게 인센티브를 제공합니다. [다른 사람이 stETH를 스테이킹하도록 돕는 추천인에게도 보상](https://github.com/MorpheusAIs/MRC/blob/main/IN%20PROGRESS/MRC08.md#2-capital-front-ends)함으로써 커뮤니티 리더쉽을 분권화하고, 기여자 간 글로벌 네트워크를 조성하는 동시에 운영 자금을 확보하는데도 도움이 됩니다. 40 | 41 | ### 9. 현 시대에서 중대하게 요구되는 솔루션과 시장 적합성 42 | 탈중앙 AI는 빅테크에 대한 개인 정보 문제와 불신과 같은 시급한 문제를 해결합니다. 모피어스는 블록체인의 진보를 발판으로 탈중앙 네트워크상 AI를 배포해 중앙화 플랫폼에 대한 무검열과 개인정보 보호를 중심으로한 대안을 제공합니다. 43 | 44 | ### 10. MOR20 표준 45 | 모피어스는 AI 마켓플레이스를 부트스트래핑 하기 위한 자금 조달 매커니즘을 (테크노 캐피털 머신) 포함하는 컨트랙트의 집합입니다. 이 컨트랙트들은 오픈 소스로, 실제 환경에서 실전 테스트를 거쳐 미화 4억 달러 (한화 5천5백억 원 이상)가 넘는 stETH를 확보하였습니다. 또, [MOR20](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Capital%20Providers%2C%20MOR20%2C%20TCM/Techno%20Capital%20Machine%20(TCM).md#automated-recurring-revenue--rewards-arr-generalizing-the-tcm-model---mor20-token-standard) 표준의 일부로 패키징되어, 누구나 이 모델을 통한 프로젝트 자금 조달이 가능하도록 하고 있습니다. 46 | 47 | ------------------- 48 | **Jeff's Contacts** 49 | - Telegram: @jabo38 50 | - Twitter: @thejabo38 51 | -------------------------------------------------------------------------------- /Archive/Translations/Malay/Morpheus Windows Install Guide Malay.md: -------------------------------------------------------------------------------- 1 | ## Memasang Morpheus pada Windows 2 | 3 | - Mula-mula, pasang WSL2, anda boleh melakukannya dengan menjalankan `wsl --install` pada gesaan arahan pentadbir. Kemudian buka WSL2 dengan `wsl` dan ikuti proses persediaan. 4 | 5 | - Kemudian jalankan `curl https://ollama.ai/install.sh | sh` untuk memasang ollama. 6 | 7 | - Kemudian pasang python dengan melakukan `sudo apt-get update` dan `sudo apt-get install python3`. 8 | 9 | - Kemudian jalankan `pip3 install gdown`. 10 | 11 | - Sekarang muat turun morpheus dpkg dengan menjalankan `gdown https://drive.google.com/uc?id=1PQ3n7LXeJHe_jmkYLDUQ9fWjZQTWbHCB`. 12 | 13 | - Sahkan integriti muat turun Morpheus oleh `sha1sum morpheus_0.0.5_amd64.deb`. pastikan ia sepadan dengan cincang `b227e7bcb21ec9e8e2b4bf9510a2e1f224953fe5`, jika tidak, hentikan proses pemasangan. 14 | 15 | - Kemudian jalankan `sudo dpkg -i morpheus_0.0.5_amd64.deb`, jika pemasangan gagal pada mulanya, pasang dependencies dan cuba lagi. 16 | 17 | - Sekarang setelah anda memasang morpheus tanpa sebarang ralat kebergantungan, buka 2 tetingkap WSL2 dengan membuka 2 tetingkap baris perintah dan taip wsl pada kedua-duanya, kemudian pada salah satu daripadanya jalankan `ollama serve` dan pada satu lagi jalankan `morpheus`. 18 | -------------------------------------------------------------------------------- /Archive/Translations/Polish/Protection Fund Details Polish.md: -------------------------------------------------------------------------------- 1 | # Propozycja Funduszu Ochronnego Morpheus 2 | 3 | ## Wstęp 4 | 5 | Biały księga Morpheus przeznacza 4% wszystkich emisji MOR na cele "Funduszu Ochronnego" i powierza Dostawcom Kodu rolę orakul w przypadku potrzeby wykorzystania jego zasobów. 6 | Typy działań: 7 | 8 | - Wypłata nagród za znalezienie błędu w celu uniknięcia ataków. 9 | - Wypłata audytów przed wdrożeniem nowych Smart Contracts. 10 | - Wstrzymanie Smart Contracts w przypadku trwającego ataku. 11 | - Sygnalizacja i mechanizm wypłaty po ataku. 12 | - Plan w przypadku znaczącego zdarzenia stratnego (scenariusz Hard Fork). 13 | 14 | ## Predefiniowane przypadki wywołujące mniejsze wypłaty 15 | 16 | Zanim Smart Contracts zostaną uruchomione w sieci Ethereum, tu zdefiniowane są warunki, w których Fundusz Ochronny wypłaci MOR lub stETH. 17 | 18 | ## Rodzaje płatności: 19 | 20 | 1. Odkryte błędy i odpowiedzialnie ujawnione deweloperom Smart Contractów Morpheus Capital, Code, Compute, Community lub Protection Fund. 21 | 2. Płatność audytów przed wdrożeniem nowych Smart Contracts w sieci Morpheus. 22 | 3. Straty użytkowników MOR lub stETH w przypadku wykorzystania Smart Contractu Morpheus. 23 | 4. Wypłacenie dostawcom, którzy nie otrzymali emisji MOR w przypadku awarii Smart Contractu Morpheus. 24 | 25 | Wysokość płatności z funduszu ochronnego powinna być proporcjonalna do błędu, straty lub błędu emisji. 26 | 27 | ## Warunki wstrzymania Smart Contracts 28 | 29 | Zanim płatności za szkody zostaną ustalone, powinny istnieć warunki, które wywołają wstrzymanie Smart Contracts w przypadku trwającego ataku. 30 | 31 | ## Sygnalizacja i mechanizm wypłaty 32 | 33 | Dostawcy Kodu będą uczestniczyć w sygnalizacji, kiedy należy wywołać płatność. Najpierw zdarzenie zostanie szczegółowo opisane i opublikowane w repozytorium GitHub dotkniętego Smart Contractu. Będzie to zawierać listę dotkniętych adresów i kwot MOR i / lub stETH. 34 | 35 | Jeśli większość Dostawców Kodu (mierzona wagą ich posiadanych tokenów MOR) biorących udział w okresie Sygnalizacji (nie dłużej niż 7 dni) zweryfikuje raport jako PRAWDZIWY, wtedy płatność zostanie wywołana. 36 | 37 | Po wywołaniu płatności oprogramowanie powiadomi deweloperów o konieczności autoryzacji płatności na dotknięte adresy w określonych kwotach. 38 | 39 | ## Plan w przypadku znaczącego zdarzenia stratnego 40 | 41 | Znaczące Zdarzenie Stratne definiuje się jako zdarzenie, w którym straty MOR przekraczają łączne zasoby Funduszu Ochronnego. W takim przypadku, zamiast wypłacić MOR, Dostawcy Kodu powinni wdrożyć nowe Smart Contracts i ręcznie poprawić saldo MOR. Spowoduje to efektywnie hardfork w kodzie / saldach MOR, a wszyscy dostawcy, hodlerzy tokenów i inni dostawcy infrastruktury będą musieli zaktualizować swój kod do nowych Smart Contracts. 42 | 43 | W przypadku stETH utraconego w Znaczącym Zdarzeniu Stratnym, Fundusz Ochronny wypłaci maksymalnie możliwą kwotę na proporcjonalnej zasadzie do kwoty strat każdej osoby. 44 | 45 | ## Podsumowanie 46 | 47 | Błędy i błędy w oprogramowaniu są rzeczywistością i zaznaczają historię od dwóch niezamierzonych hardforków Bitcoin do The DAO w początkach Ethereum. 48 | 49 | Dlatego planowanie różnych scenariuszy i przypadków oraz sposób ich obsługi jest mądrym podejściem do ochrony przed ryzykiem i jego ograniczania. Na szczęście, mając zarezerwowane zasoby z góry w Funduszu Ochronnym, a także część funduszu ochronnego, która generuje nagrody LP w AMM, zasoby przeznaczone na ochronę użytkowników powinny rosnąć z czasem. 50 | -------------------------------------------------------------------------------- /Archive/Translations/Portuguese/Protection Fund Details Portuguese.md: -------------------------------------------------------------------------------- 1 | # Proposta do Fundo de Proteção Morpheus 2 | 3 | ## Introdução 4 | 5 | O white paper do Morpheus reserva 4% de todas as emissões de MOR com o objetivo de um "Fundo de Proteção" e delega aos provedores de código agirem como oráculos no caso de seus recursos serem necessários. 6 | Tipos de ações: 7 | 8 | - Pagamento de recompensa por bugs para evitar ataques. 9 | - Pagamento de auditorias antes da implantação de novos Smart Contracts. 10 | - Interrupção dos Smart Contracts em caso de ataque em andamento. 11 | - Sinalização e mecanismo para pagamento após um ataque. 12 | - Plano em caso de Evento de Perda Significativa (Cenário de Hard Fork) 13 | 14 | ## Casos Predefinidos que Disparam Pagamentos Menores 15 | 16 | Antes dos Smart Contracts irem ao ar na rede Ethereum, aqui estão definidas as condições sob as quais o Fundo de Proteção pagará MOR ou stETH. 17 | 18 | ## Tipos de Pagamentos: 19 | 20 | 1. Bugs descobertos e divulgados de forma responsável aos desenvolvedores de um Contrato de Smart Morpheus Capital, Código, Computação, Comunidade ou Fundo de Proteção. 21 | 2. Pagamento de auditorias antes da implantação de novos Smart Contracts na rede Morpheus. 22 | 3. Perdas de usuários de MOR ou stETH no caso de um Smart Contract Morpheus ser explorado. 23 | 4. Reembolsando fornecedores que não receberam emissões de MOR no caso de falha do Smart Contract Morpheus. 24 | 25 | Os valores dos pagamentos do fundo de proteção devem ser proporcionais ao bug, perda ou erro de emissão. 26 | 27 | ## Condições de Interrupção para Smart Contracts 28 | 29 | Antes que os pagamentos por danos possam ser calculados, deve haver condições que disparem uma interrupção dos Smart Contracts no caso de um ataque em andamento. 30 | 31 | ## Sinalização e Mecanismo para Pagamento 32 | 33 | Os provedores de código participarão da sinalização quando um pagamento deverá ser acionado. Primeiro, um incidente será detalhado e postado no repositório GitHub do Smart Contract afetado. Incluindo uma lista de endereços afetados e quantidades de MOR e / ou stETH. 34 | 35 | Se a maioria dos provedores de código (medidos pelo peso de seus tokens MOR mantidos) que participarem do período de sinalização (não superior a 7 dias) validarem o relatório como VERDADEIRO, então um pagamento será acionado. 36 | 37 | Uma vez que um pagamento seja acionado, o software enviará uma mensagem aos desenvolvedores para autorizar um pagamento aos endereços afetados nas quantidades especificadas. 38 | 39 | ## Plano em Caso de Evento de Perda Significativa 40 | 41 | Um Evento de Perda Significativa é definido como um evento no qual as perdas de MOR excedem os recursos totais do Fundo de Proteção. Nesse caso, em vez de realizar um pagamento de MOR, os provedores de código deverão implantar novos Smart Contracts e corrigir manualmente os saldos de MOR afetados. Isso efetivamente causaria um hard fork no código / saldos de MOR e todos os provedores, detentores de tokens e outros provedores de infraestrutura teriam que atualizar seu código para os novos Smart Contracts. 42 | 43 | No caso de stETH perdido em um Evento de Perda Significativa, o Fundo de Proteção deverá pagar na medida do possível, de forma proporcional ao valor das perdas de cada pessoa. 44 | 45 | ## Conclusão 46 | 47 | Bugs e erros de software são uma realidade e marcam a história desde os dois hard forks não intencionais do Bitcoin até o The DAO durante os primeiros dias do Ethereum. 48 | 49 | Portanto, planejar com antecedência para diferentes cenários e casos e como lidar com eles é uma abordagem sábia para proteger e mitigar riscos. Felizmente, ao reservar recursos com antecedência no Fundo de Proteção e também parte do fundo de proteção ganhando recompensas LP no AMM, os recursos dedicados à proteção dos usuários deveriam crescer ao longo do tempo. 50 | -------------------------------------------------------------------------------- /Archive/Translations/Romanian/Protection Fund Details Romanian.md: -------------------------------------------------------------------------------- 1 | # Propunere Fond de Protecție Morpheus 2 | 3 | ## Introducere 4 | 5 | Documentul alb Morpheus aloca 4% din toate emisiile de MOR în scopul unui "Fond de Protecție" și delegă Furnizorilor de Cod să acționeze ca oracole în cazul în care resursele sale sunt necesare. 6 | Tipuri de acțiuni: 7 | 8 | - Plata recompenselor pentru găsirea de bug-uri pentru a evita atacurile. 9 | - Plata auditurilor înainte ca noi Smart Contracts să fie implementate. 10 | - Suspendarea Smart Contracts în cazul unui atac în desfășurare. 11 | - Semnalizarea și mecanismul de plată după un atac. 12 | - Plan în cazul unui eveniment de pierdere semnificativă (Scenariu de bifurcare dură) 13 | 14 | ## Cazuri Predefinite Care Declanșează Plăți Minore 15 | 16 | Înainte ca Smart Contracts să fie lansate pe rețeaua Ethereum, sunt definite condițiile în care Fondul de Protecție va plăti MOR sau stETH. 17 | 18 | ## Tipuri de Plăți: 19 | 20 | 1. Bug-uri descoperite și divulgate responsabil dezvoltatorilor unui Smart Contract Morpheus Capital, Cod, Compute, Comunitate sau Fond de Protecție. 21 | 2. Plata auditurilor înainte ca noi Smart Contracts să fie implementate pe rețeaua Morpheus. 22 | 3. Pierderi ale utilizatorilor de MOR sau stETH în cazul unui Smart Contract Morpheus exploatat. 23 | 4. Facerea întregilor furnizori care nu au primit emisii MOR în cazul unei defecțiuni a Smart Contractului Morpheus. 24 | 25 | Suma plăților din fondul de protecție ar trebui să fie proporțională cu bug-ul, pierderea sau eroarea de emisie. 26 | 27 | ## Condiții de Suspendare a Smart Contracts 28 | 29 | Înainte ca plățile pentru daune să poată fi stabilite, trebuie să existe condiții care să declanșeze o suspendare a Smart Contracts în cazul unui atac în desfășurare. 30 | 31 | ## Semnalizare și Mecanism pentru Plăți 32 | 33 | Furnizorii de Cod vor participa la semnalizarea când ar trebui să fie declanșată o plată. Mai întâi, un incident va fi detaliat și postat pe depozitul GitHub al Smart Contractului afectat. Incluzând o listă de adrese afectate și sume de MOR și / sau stETH. 34 | 35 | Dacă o majoritate a Furnizorilor de Cod (măsurată în funcție de ponderea token-urilor MOR deținute) care participă la perioada de Semnalizare (nu mai mult de 7 zile) validează raportul ca ADEVĂRAT, atunci o plată va fi declanșată. 36 | 37 | Odată ce o plată este declanșată, software-ul va trimite un mesaj dezvoltatorilor pentru a autoriza o plată către adresele afectate în sumele specificate. 38 | 39 | ## Plan în Cazul unui Eveniment Semnificativ de Pierdere 40 | 41 | Un Eveniment Semnificativ de Pierdere este definit ca un eveniment în care pierderile MOR depășesc resursele totale ale Fondului de Protecție. În acest caz, în loc să facă o plată de MOR, Furnizorii de Cod ar trebui să implementeze noi Smart Contracts și să corecteze manual balanțele MOR afectate. Aceasta ar provoca efectiv o bifurcare dură în cod / balanțele MOR și toți furnizorii, deținătorii de token-uri și alți furnizori de infrastructură ar trebui să-și actualizeze codul la noile Smart Contracts. 42 | 43 | În cazul stETH pierdut într-un Eveniment Semnificativ de Pierdere, Fondul de Protecție va plăti în măsura maximă posibilă în mod proporțional cu suma pierderilor fiecărei persoane. 44 | 45 | ## Concluzie 46 | 47 | Bug-urile și erorile din software sunt o realitate și marchează istoria de la cele două bifurcări accidentale ale Bitcoin la The DAO în primele zile ale Ethereum. 48 | 49 | Așadar, planificarea pentru diferite scenarii și cazuri și modul de gestionare a acestora este o abordare inteligentă pentru protejarea împotriva riscurilor și reducerea acestora. Din fericire, având resurse alocate în avans cu Fondul de Protecție, și, de asemenea, o parte din fondul de protecție câștigând recompense LP în AMM, resursele dedicate protecției utilizatorilor ar trebui să crească în timp. 50 | -------------------------------------------------------------------------------- /Archive/Translations/Russian/Protection Fund Details Russian.md: -------------------------------------------------------------------------------- 1 | # Предложение Фонда защиты Морфеуса 2 | 3 | ## Введение 4 | В Белой Книге Morpheus 4% всей эмиссии MOR выделяется для создания «Фонда защиты» и делегируется поставщикам кода, которые выступают в качестве оракулов в случае необходимости в его ресурсах. 5 | Тип действий: 6 | - Выплата награды за нахождение ошибки или уязвимости во избежание атак. 7 | - Оплата аудитов перед развертыванием новых смарт-контрактов. 8 | - Остановка смарт-контрактов в случае атаки. 9 | - Оценка ущерба и механизм выплаты после атаки. 10 | - План на случай значительных потерь (сценарий хард-форка) 11 | 12 | ## Заранее определенные случаи для небольших выплат 13 | Прежде чем смарт-контракты будут запущены в сети Ethereum, здесь определены условия, при которых Фонд защиты будет выплачивать MOR или stETH. 14 | 15 | ## Виды платежей: 16 | 1. Ошибки, обнаруженные и ответственно раскрытые разработчикам смарт-контрактов Капитала, Вычислений, Кода, Комьюнити и Фонда защиты. 17 | 2. Оплата аудита перед развертыванием новых смарт-контрактов в сети Morpheus. 18 | 3. Потери пользователей MOR или sETH в результате ошибки смарт-контрактов Morpheus. 19 | 4. Выплаты в случае, если участники не получили эмиссии MOR, в случае сбоя смарт-контрактов Morpheus. 20 | 21 | Суммы выплат из фонда защиты должны быть пропорциональны ошибке, потере или ошибке эмиссии. 22 | 23 | ## Условия остановки смарт-контрактов 24 | Прежде чем определить выплаты для компенсации ущерба, должны быть условия, которые вызывают остановку смарт-контрактов в случае текущей атаки. 25 | 26 | ## Оценка ущерба и механизм выплат 27 | Поставщики кода будут участвовать в оценке ущерба в случае необходимости выплаты. Сначала инцидент будет подробно описан и опубликован в репозитории GitHub затронутого смарт-контракта. Включая список затронутых адресов и сумм MOR и/или stETH. 28 | 29 | Если большинство поставщиков кода (измеряемое весом их удерживаемых токенов MOR), участвующих в оценке ущерба (не более 7 дней), подтвердит отчет как ИСТИННЫЙ, то будет инициирована выплата. 30 | 31 | Как только выплата будет инициирована, программное обеспечение отправит разработчикам сообщение с просьбой авторизовать выплату на затронутые адреса в указанных суммах. 32 | 33 | ## План в случае существенного ущерба 34 | Существенная потеря определяется как событие, при котором потери MOR превышают общие ресурсы Фонда Защиты. В этом случае вместо выплаты MOR поставщики кода должны развернуть новые смарт-контракты и вручную скорректировать затронутые балансы MOR. Это фактически вызовет хард-форк кода / балансоа MOR, и все поставщики, держатели токенов и другие поставщики инфраструктуры должны будут обновить свой код до новых смарт-контрактов. 35 | 36 | В случае утери stETH в результате существенной ущерба, Фонд Защиты выплатит максимально возможную сумму на пропорциональной основе с учетом ущерба каждого человека. 37 | 38 | ## Заключение 39 | Баги и ошибки в программном обеспечении - это реальность отмеченная в истории начиная от двух неумышленных хард форков в Bitcoin до The DAO в ранние дни Ethereum. 40 | 41 | Таким образом, заранее планировать различные сценарии и случаи и то, как с ними справляться, - мудрый подход для защиты и смягчения рисков. К счастью, благодаря заранее выделенным ресурсам в Фонде Защиты, а также части фонда защиты, приносящей доход в виде комиссионных наград за предоставление ликвидности в AMM, ресурсы, выделенные на защиту пользователей, будут увеличиваться со временем. 42 | -------------------------------------------------------------------------------- /Archive/Translations/Swedish/Protection Fund Details Swedish.md: -------------------------------------------------------------------------------- 1 | # Propunere Fond de Protecție Morpheus 2 | 3 | ## Introducere 4 | 5 | Documentul alb Morpheus aloca 4% din toate emisiile de MOR în scopul unui "Fond de Protecție" și delegă Furnizorilor de Cod să acționeze ca oracole în cazul în care resursele sale sunt necesare. 6 | Tipuri de acțiuni: 7 | 8 | - Plata recompenselor pentru găsirea de bug-uri pentru a evita atacurile. 9 | - Plata auditurilor înainte ca noi Smart Contracts să fie implementate. 10 | - Suspendarea Smart Contracts în cazul unui atac în desfășurare. 11 | - Semnalizarea și mecanismul de plată după un atac. 12 | - Plan în cazul unui eveniment de pierdere semnificativă (Scenariu de bifurcare dură) 13 | 14 | ## Cazuri Predefinite Care Declanșează Plăți Minore 15 | 16 | Înainte ca Smart Contracts să fie lansate pe rețeaua Ethereum, sunt definite condițiile în care Fondul de Protecție va plăti MOR sau stETH. 17 | 18 | ## Tipuri de Plăți: 19 | 20 | 1. Bug-uri descoperite și divulgate responsabil dezvoltatorilor unui Smart Contract Morpheus Capital, Cod, Compute, Comunitate sau Fond de Protecție. 21 | 2. Plata auditurilor înainte ca noi Smart Contracts să fie implementate pe rețeaua Morpheus. 22 | 3. Pierderi ale utilizatorilor de MOR sau stETH în cazul unui Smart Contract Morpheus exploatat. 23 | 4. Facerea întregilor furnizori care nu au primit emisii MOR în cazul unei defecțiuni a Smart Contractului Morpheus. 24 | 25 | Suma plăților din fondul de protecție ar trebui să fie proporțională cu bug-ul, pierderea sau eroarea de emisie. 26 | 27 | ## Condiții de Suspendare a Smart Contracts 28 | 29 | Înainte ca plățile pentru daune să poată fi stabilite, trebuie să existe condiții care să declanșeze o suspendare a Smart Contracts în cazul unui atac în desfășurare. 30 | 31 | ## Semnalizare și Mecanism pentru Plăți 32 | 33 | Furnizorii de Cod vor participa la semnalizarea când ar trebui să fie declanșată o plată. Mai întâi, un incident va fi detaliat și postat pe depozitul GitHub al Smart Contractului afectat. Incluzând o listă de adrese afectate și sume de MOR și / sau stETH. 34 | 35 | Dacă o majoritate a Furnizorilor de Cod (măsurată în funcție de ponderea token-urilor MOR deținute) care participă la perioada de Semnalizare (nu mai mult de 7 zile) validează raportul ca ADEVĂRAT, atunci o plată va fi declanșată. 36 | 37 | Odată ce o plată este declanșată, software-ul va trimite un mesaj dezvoltatorilor pentru a autoriza o plată către adresele afectate în sumele specificate. 38 | 39 | ## Plan în Cazul unui Eveniment Semnificativ de Pierdere 40 | 41 | Un Eveniment Semnificativ de Pierdere este definit ca un eveniment în care pierderile MOR depășesc resursele totale ale Fondului de Protecție. În acest caz, în loc să facă o plată de MOR, Furnizorii de Cod ar trebui să implementeze noi Smart Contracts și să corecteze manual balanțele MOR afectate. Aceasta ar provoca efectiv o bifurcare dură în cod / balanțele MOR și toți furnizorii, deținătorii de token-uri și alți furnizori de infrastructură ar trebui să-și actualizeze codul la noile Smart Contracts. 42 | 43 | În cazul stETH pierdut într-un Eveniment Semnificativ de Pierdere, Fondul de Protecție va plăti în măsura maximă posibilă în mod proporțional cu suma pierderilor fiecărei persoane. 44 | 45 | ## Concluzie 46 | 47 | Bug-urile și erorile din software sunt o realitate și marchează istoria de la cele două bifurcări accidentale ale Bitcoin la The DAO în primele zile ale Ethereum. 48 | 49 | Așadar, planificarea pentru diferite scenarii și cazuri și modul de gestionare a acestora este o abordare inteligentă pentru protejarea împotriva riscurilor și reducerea acestora. Din fericire, având resurse alocate în avans cu Fondul de Protecție, și, de asemenea, o parte din fondul de protecție câștigând recompense LP în AMM, resursele dedicate protecției utilizatorilor ar trebui să crească în timp. 50 | -------------------------------------------------------------------------------- /Archive/Translations/Ukrainian/Protection Fund Details Ukrainian.md: -------------------------------------------------------------------------------- 1 | # Пропозиція Фонду захисту Морфеуса 2 | 3 | ## Вступ 4 | У Білій Книзі Morpheus 4% всієї емісії MOR виділяється для створення «Фонду захисту» та делегується постачальникам коду, які виступають як оракули у разі потреби в його ресурсах. 5 | Тип дій: 6 | - Виплата нагороди за знаходження помилки або вразливості, щоб уникнути атак. 7 | - Оплата аудитів безпеки перед розгортанням нових смарт-контрактів. 8 | - Зупинка смарт-контрактів у разі атаки. 9 | - Оцінка збитків та механізм виплати після атаки. 10 | - План на випадок значних втрат (сценарій хард-форка) 11 | 12 | ## Заздалегідь визначені випадки для невеликих виплат 13 | Перш ніж смарт-контракти будуть запущені в мережі Ethereum, тут визначено умови, за яких Фонд захисту виплачуватиме MOR або stETH. 14 | 15 | ## Види платежів: 16 | 1. Помилки, виявлені та відповідально розкриті розробникам смарт-контрактів Капіталу, Обчислень, Коду, Ком'юніті та Фонду захисту. 17 | 2. Оплата аудиту перед розгортанням нових смарт-контрактів у мережі Morpheus. 18 | 3. Втрати користувачів MOR або sETH внаслідок помилки смарт-контрактів Morpheus. 19 | 4. Виплати у випадку, якщо учасники не одержали емісії MOR, у разі збою смарт-контрактів Morpheus. 20 | 21 | Суми виплат із фонду захисту повинні бути пропорційні до помилки, втрати або помилки емісії. 22 | 23 | ## Умови зупинки смарт-контрактів 24 | Перш ніж визначити виплати для компенсації збитків, мають бути умови, які спричиняють зупинку смарт-контрактів у разі поточної атаки. 25 | 26 | ## Оцінка збитків та механізм виплат 27 | Постачальники коду братимуть участь у оцінці збитків у разі потреби виплати. Спочатку інцидент буде докладно описаний та опублікований у репозиторії GitHub порушеного смарт-контракту. Включаючи список постраждалих адрес та сум MOR та/або stETH. 28 | 29 | Якщо більшість постачальників коду (вимірювана вагою їх утримуваних токенів MOR), що беруть участь в оцінці збитків (не більше 7 днів), підтвердить звіт як СПРАВЖНИЙ, то буде ініційовано виплату. 30 | 31 | Як тільки виплата буде ініційована, програмне забезпечення надішле розробникам повідомлення з проханням авторизувати виплату постраждалим адресам у зазначених сумах. 32 | 33 | ## План у разі суттєвої шкоди 34 | Істотна втрата визначається як подія, коли втрати MOR перевищують загальні ресурси Фонду Захисту. У цьому випадку замість виплати MOR постачальники коду мають розгорнути нові смарт-контракти та вручну скоригувати порушені баланси MOR. Це фактично викликає хард-форк коду / балансу MOR, і всі постачальники, власники токенів та інші постачальники інфраструктури повинні будуть оновити свій код до нових смарт-контрактів. 35 | 36 | У разі втрати stETH внаслідок суттєвої шкоди, Фонд Захисту виплатить максимально можливу суму на пропорційній основі з урахуванням шкоди кожнії людини. 37 | 38 | ## Висновок 39 | Вразливості та помилки в програмному забезпеченні - це реальність відзначена в історії, починаючи від двох ненавмисних хард форків у Bitcoin до The DAO в ранні дні Ethereum. 40 | 41 | Таким чином, заздалегідь планувати різні сценарії та випадки та те, як з ними справлятися, – мудрий підхід для захисту та пом'якшення ризиків. На щастя, завдяки заздалегідь виділеним ресурсам у Фонді захисту, а також частині фонду захисту, що приносить дохід у вигляді комісійних нагород за надання ліквідності в AMM, ресурси, виділені на захист користувачів, збільшуватимуться з часом. 42 | -------------------------------------------------------------------------------- /Archive/Translations/Urdu/Coder Guide Urdu.md: -------------------------------------------------------------------------------- 1 | # کوڈر گائیڈ: 2 | بہت سے ڈویلپرز مورفیئس کمیونٹی میں شامل ہو رہے ہیں۔ آپ سب کا خیرمقدم ہے! 3 | آپ مورفیئس کمیونٹی کا ایک اہم حصہ ہیں اور آپ کی محنت کے لیے بہت سے انعامات حاصل کیے جا سکتے ہیں۔ 4 | مورفیئس میں تمام MOR اخراجات کا 24٪ کوڈرز کو جاتا ہے اور یہ آئندہ 16 سالوں تک جاری رہے گا جیسا کہ 42 ملین MOR کے تمام اخراجات کا حصہ ہے۔ 5 | 6 | ## گائیڈ: 7 | شروع کرنے کے لیے یہاں کچھ وسائل کی ایک مختصر فہرست اور مورفیئس میں بہتری اور کوڈ شامل کرنے کے بہترین طریقوں کی فہرست دی گئی ہے۔ 8 | 9 | ## ‏ TL;DR 10 | - مورفیئس کمنٹس کے لیے درخواست (MRC) کی فہرست کا جائزہ لیں بلند سطح کی سمجھ بوجھ کے لیے۔ 11 | - خاصیتوں کے لیے GitHub کے مسائل کی فہرست کا جائزہ لیں۔ 12 | - اپنے کوڈ کو شامل کرنے کے طریقوں پر مشوروں کے لیے بہترین عملیات کا جائزہ لیں۔ 13 | - مورفیئس کو قدر میں اضافہ کرنے والا ایک Pull Request جمع کروائیں۔ 14 | 15 | ## مورفیئس کمنٹس کے لیے درخواست: 16 | مورفیئس، سمارٹ ایجنٹس، ٹوکنومکس، اور ٹیکنو کیپیٹل مشین کو بہتر بنانے، نافذ کرنے سے متعلق تمام کاغذات / تجاویز کی فہرست شامل ہے۔ 17 | 18 | ‏ https://github.com/MorpheusAIs/MRC/blob/main/Morpheus%20Request%20For%20Comments%20(MRC).md 19 | 20 | ## جاری کام کی تفصیلات کے لیے GitHub پر مسئلہ کی فہرست چیک کریں 21 | مورفیئس GitHub پر رپورٹ کی گئی فعال مسائل کی فہرست شامل ہے۔ 22 | 23 | ‏ https://github.com/MorpheusAIs/Morpheus/issues 24 | 25 | ## کوڈ شامل کرنے کے لیے بہترین عملیات 26 | کوڈ شامل کرنے کا طریقہ کار، اور آپ کے Pull Request کے شامل ہونے کے امکانات کو بڑھانے کی تفصیلات۔ 27 | 28 | ‏ https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Code%20Contributor%20Best%20Practices.md 29 | 30 | ## ‏ Pull Requests میں شامل کرنے کے لیے کوڈ کنٹریبیوٹر ٹیبل 31 | اپنی کوڈ شراکتوں کے ساتھ GitHub پر کوڈ کنٹریبیوٹر ٹیبل کو اپ ڈیٹ کریں اور اپنی گھنٹہ کی درخواست کے ساتھ شامل کریں۔ 32 | 33 | ‏ https://github.com/MorpheusAIs/Docs/blob/main/Contributions/Code%20-%20Proof_Of_Contribution.md 34 | -------------------------------------------------------------------------------- /Archive/Translations/Urdu/Protection Fund Details Urdu.md: -------------------------------------------------------------------------------- 1 | # مورفیس پروٹیکشن فنڈ کی تجویز 2 | 3 | ## تعارف 4 | مورفیس وائٹ پیپر "پروٹیکشن فنڈ" کے مقصد کے لیے تمام MOR اخراجات کا 4% مختص کرتا ہے اور کوڈ پرووائیڈرز کو اس کے وسائل کی ضرورت ہونے کی صورت میں اوریکلز کے طور پر عمل کرنے کا اختیار دیتا ہے۔ 5 | عمل کی قسمیں: 6 | - حملوں سے بچنے کے لیے بگ باؤنٹی کی ادائیگی۔ 7 | - نئے سمارٹ کانٹریکٹس کو مورفیس نیٹ ورک پر ڈپلائے کرنے سے پہلے آڈٹس کی ادائیگی۔ 8 | - جاری حملے کی صورت میں سمارٹ کانٹریکٹس کو روکنا۔ 9 | - حملے کے بعد ادائیگی کے لیے سگنلنگ اور میکانزم۔ 10 | - اہم نقصان کی واقعہ کی صورت میں منصوبہ (ہارڈ فورک سیناریو) 11 | 12 | ## معمولی ادائیگیوں کے لیے مقرر شدہ حالات کا ٹرگر 13 | سمارٹ کانٹریکٹس ایتھریم نیٹ ورک پر زندہ ہونے سے پہلے یہاں مقرر کردہ حالات ہیں جن کے تحت پروٹیکشن فنڈ MOR یا stETH ادا کرے گا۔ 14 | 15 | ## ادائیگیوں کی قسمیں: 16 | 1. بگز جو دریافت کی گئیں اور مورفیس کیپٹل، کوڈ، کمپیوٹ، کمیونٹی یا پروٹیکشن فنڈ سمارٹ کانٹریکٹ کے ڈویلپرز کو ذمہ دارانہ طور پر ظاہر کی گئیں۔ 17 | 2. نئے سمارٹ کانٹریکٹس کو مورفیس نیٹ ورک پر ڈپلائے کرنے سے پہلے آڈٹس کی ادائیگی۔ 18 | 3. مورفیس سمارٹ کانٹریکٹ کے استحصال کی صورت میں MOR یا stETH کے صارفین کے نقصانات۔ 19 | 4. ان پرووائیڈرز کو مکمل بنانا جنہوں نے مورفیس سمارٹ کانٹریکٹ کی ناکامی کی صورت میں MOR اخراجات وصول نہیں کیے۔ 20 | 21 | پروٹیکشن فنڈ سے ادائیگیوں کی رقمیں بگ، نقصان یا اخراجات کی غلطی کے تناسب میں ہونی چاہیے۔ 22 | 23 | ## سمارٹ کانٹریکٹس کے لیے روکنے کی حالات 24 | نقصانات کی ادائیگیوں کے لیے حالات کا تعین کرنے سے پہلے، جاری حملے کی صورت میں سمارٹ کانٹریکٹس کو روکنے کے لیے حالات کا ٹرگر ہونا چاہیے۔ 25 | 26 | ## ادائیگی کے لیے سگنلنگ اور میکانزم 27 | کوڈ پرووائیڈرز ادائیگی کے ٹرگر ہونے پر سگنلنگ میں حصہ لیں گے۔ پہلے ایک واقعہ کی تفصیل بیان کی جائے گی اور متاثرہ سمارٹ کانٹریکٹ کے GitHub ریپوزٹری پر پوسٹ کی جائے گی۔ اس میں متاثرہ ایڈریسز اور MOR اور / یا stETH کی مقداروں کی ایک فہرست شامل ہوگی۔ 28 | 29 | اگر کوڈ پرووائیڈرز کی اکثریت (ان کے ہولڈ کردہ MOR ٹوکنز کے وزن کے ذریعہ ناپا گیا) جو سگنلنگ کی مدت (زیادہ سے زیادہ 7 دن) میں حصہ لیتے ہیں، رپورٹ کو TRUE کے طور پر تصدیق کرتے ہیں، تو ایک ادائیگی کا ٹرگر ہو جائے گا۔ 30 | 31 | ایک بار جب ادائیگی کا ٹرگر ہو جاتا ہے تو سافٹ ویئر ڈویلپرز کو متاثرہ ایڈریسز کو مخصوص مقداروں میں ادائیگی کی اجازت دینے کے لیے پیغام بھیجے گا۔ 32 | 33 | ## اہم نقصان کی واقعہ کی صورت میں منصوبہ 34 | اہم نقصان کی واقعہ ایسے واقعہ کے طور پر معین کی گئی ہے جس میں MOR کے نقصانات پروٹیکشن فنڈ کے کل وسائل سے تجاوز کر جائیں۔ اس صورت میں، MOR کی ادائیگی کے بجائے کوڈ پرووائیڈرز کو نئے سمارٹ کانٹریکٹس کو ڈپلائے کرنا چاہیے اور دستی طور پر متاثرہ MOR بیلنسز کو درست کرنا چاہیے۔ یہ عملی طور پر کوڈ / MOR بیلنسز میں ایک ہارڈ فورک کا باعث بنے گا اور تمام پرووائیڈرز، ٹوکن ہولڈرز اور دیگر انفراسٹرکچر پرووائیڈرز کو نئے سمارٹ کانٹریکٹس کے لیے اپنے کوڈ کو اپ ڈیٹ کرنا ہوگا۔ 35 | 36 | اہم نقصان کی واقعہ میں stETH کے نقصان کی صورت میں، پروٹیکشن فنڈ ہر ایک کے نقصانات کی مقدار کے تناسب میں زیادہ سے زیادہ حد تک ادائیگی کرے گا۔ 37 | 38 | ## نتیجہ 39 | سافٹ ویئر میں بگز اور غلطیاں ایک حقیقت ہیں اور بٹ کوائن کے دو غیر ارادی ہارڈ فورکس سے لے کر ایتھریم کے ابتدائی دنوں میں ڈاؤ کے تاریخ کو نشان زد کرتی ہیں۔ 40 | 41 | لہذا مختلف منظرناموں اور معاملات کے لیے پہلے سے منصوبہ بندی کرنا اور ان کا انتظام کرنے کا طریقہ ایک دانشمندانہ نقطہ نظر ہے جو خطرات کے خلاف تحفظ فراہم کرتا ہے اور دوسری صورت میں خطرات کو کم کرتا ہے۔ خوش قسمتی سے، پروٹیکشن فنڈ میں پہلے سے وسائل مختص کرنے کے ساتھ، اور پروٹیکشن فنڈ کا حصہ AMM میں LP انعامات حاصل کرنے کے ساتھ، صارفین کے تحفظ کے لیے مختص وسائل کے ساتھ وقت کے ساتھ بڑھنے کی توقع کی جاتی ہے۔ 42 | -------------------------------------------------------------------------------- /Archive/ollama_instructions_in_pictures.md: -------------------------------------------------------------------------------- 1 | ### Ollama Instructions 2 | 3 | 1) Download Ollama from [Ollama AI](https://Ollama.ai) 4 | 5 | 6 | 7 | 2) Double click to unzip 8 | 9 | 10 | 11 | 3) Unzip Ollama.zip 12 | 13 | Screen Shot 2023-10-24 at 2 26 15 PM 14 | 15 | 4) Double-click the Ollama Icon to install. You may see a message reminding you that you downloaded this from the internet. Agree and allow. 16 | 17 | accept 18 | 19 | 20 | 5) When the install is finished, you will see a little llama lounging in the system bar.
21 | ollama 22 | 23 | 7) You're almost done! Now we open the terminal to test the install. When you've opened the terminal app, type 24 | ```Ollama run orca-mini:latest``` 25 | 26 | 8) This will download a small model called Orca-Mini. Later, you can scale up to a lorger model as your computer will allow. We're just using orca-mini to test. 27 | 28 | If you are ever wondering if Ollama is running, open a browser and navigate to https://localhost:11434, and if it's running, you will see a message saying so. 29 | 30 | ![localhost](https://github.com/MorpheusAIs/Morpheus/assets/76454555/1dfcfffe-2365-402a-84de-f0fc17cf3b6c) 31 | 32 | If it's not running, you will see a "Not Found" error. Just open terminal and enter: 33 | ```ollama serve``` 34 | 35 | and refresh https://localhost:11434. 36 | 37 | Now you're ready to install Morpheus! 38 | -------------------------------------------------------------------------------- /Contributions/Community - Proof of Contribution.md: -------------------------------------------------------------------------------- 1 | # Proof of Contribution 2 | 3 | You can register as a contributor here. 4 | 5 | [www.mor.software](https://mor.software) 6 | 7 | -------------------------------------------------------------------------------- /Contributions/Compute - Proof of Contribution.md: -------------------------------------------------------------------------------- 1 | # Compute Contributions 2 | 3 | Compute contributions will be available after the bootstrapping period. The Lumerin model as pioneered by Ryan Condron of Lumerin is being incorporated into Morpheus. More information can be found in the resources below. 4 | 5 | ## Morpheus Lumerin Model Lightpaper 6 | 7 | 

Ryan founded Lumerin as a response to Bitcoin's centralization issue in mining, aiming to create a decentralized hashpower routing system. The architecture of Lumerin, which emphasizes decentralization, transparency, and efficiency, serves as a solid foundation for the Morpheus node. By adopting the principles and design patterns established in Lumerin, Morpheus inherits the benefits of decentralization, such as increased security, reduced risk of manipulation or censorship, and improved scalability.
 8 | https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Morpheus%20Lumerin%20Model%20Lightpaper.md 9 | 10 | 11 | ## Morpheus Lumerin Model

 12 | 13 | The Morpheus Lumerin Model utilizes the Lumerin protocol routing pattern to create a peer-to-peer, decentralized, and anonymous ecosystem for connecting AI users with AI model and agent compute providers. This model seeks to incorporate aspects of the original Morpheus white paper and yellow paper as well as core concepts from the Yellowstone Compute Model and Lake Travis System. 14 | The below proposal explains the key design principles that have been incorporated as well as outline each part of the on-chain ecosystem model, client-side node, and underlying protocol. 15 | 16 | https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Morpheus%20Lumerin%20Model.md

 17 | 18 | 19 | Ryan Condron’s talk outlining the design principles of decentralized compute at Decentralize AI Day is available here. 
 20 | If you’d like to find out more about providing compute join us in discord here - https://discord.com/channels/1151741790408429580/1167520834139738289 21 | -------------------------------------------------------------------------------- /Contributions/PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | ## Description of Change 2 | 3 | 4 | ## Related MRI 5 | Every change must fall under an MRI. See [Reference Implementations](https://github.com/MorpheusAIs/Docs/blob/main/!KEYDOCS%20README%20FIRST!/Reference%20Implementations.md) for more details. 6 | 7 | - [ ] MRI Number 1. Smart Contracts on Ethereum / Arbitrum 8 | - [ ] MRI Number 2. Smart Agents Tools & Examples 9 | - [ ] MRI Number 3. Morpheus Local Install Desktop / Mobile 10 | - [ ] MRI Number 4. TCM / MOR20 Token Standard for Fair Launches 11 | - [ ] MRI Number 5. Protection Fund 12 | - [ ] MRI Number 6. Capital Proofs Extended beyond Lido stETH 13 | - [ ] MRI Number 7. Compute Proofs Morpheus / Lumerin 14 | - [ ] MRI Number 8. Code Proofs & Dashboards 15 | - [ ] MRI Number 9. Frontend Proofs & Examples 16 | - [ ] MRI Number 10. Interoperability 17 | 18 | ## Justification 19 | 20 | 21 | ## Additional Notes 22 | 23 | -------------------------------------------------------------------------------- /Graphics/Design Library.md: -------------------------------------------------------------------------------- 1 | Full Design Library of infogrpahics and colour tiles 2 | 3 | https://drive.google.com/drive/folders/1w3pOJMDIuq-7IDGHHUYQvEnLmWCR6uAX?usp=sharing 4 | -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Chinese/Meme for TCM.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Chinese/Meme for TCM.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/arb-base-fee.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/arb-base-fee.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/arb-base-send.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/arb-base-send.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/arb-eth-fee.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/arb-eth-fee.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/arb-eth-send.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/arb-eth-send.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/base-eth-fee.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/base-eth-fee.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/eth-arb-fee.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/eth-arb-fee.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/eth-arb-transact.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/eth-arb-transact.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/eth-base-fee.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/eth-base-fee.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/eth-base-transact.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/eth-base-transact.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/mor-value.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/mor-value.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/remix-base-arb-transact.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/remix-base-arb-transact.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/remix-base-ataddress.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/remix-base-ataddress.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/remix-base-eth-transact.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/remix-base-eth-transact.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/remix-clone.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/remix-clone.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/remix-compile.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/remix-compile.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/remix-connect.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/remix-connect.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/remix-ethereum-ataddress.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/remix-ethereum-ataddress.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/remix-link.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/remix-link.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Bridge Guide/remix-moroft.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Bridge Guide/remix-moroft.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Claim Test Guide/approve.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Claim Test Guide/approve.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Claim Test Guide/approvemainnet.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Claim Test Guide/approvemainnet.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Claim Test Guide/claim.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Claim Test Guide/claim.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Claim Test Guide/deposited.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Claim Test Guide/deposited.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Claim Test Guide/import MOR.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Claim Test Guide/import MOR.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Claim Test Guide/mint mock steth.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Claim Test Guide/mint mock steth.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Claim Test Guide/mor balance.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Claim Test Guide/mor balance.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Claim Test Guide/rewards.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Claim Test Guide/rewards.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Claim Test Guide/stake.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Claim Test Guide/stake.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Dashboard Claim Guide/addmor.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Dashboard Claim Guide/addmor.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Dashboard Claim Guide/addtoken.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Dashboard Claim Guide/addtoken.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Dashboard Claim Guide/chainlist.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Dashboard Claim Guide/chainlist.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Dashboard Claim Guide/claim.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Dashboard Claim Guide/claim.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Dashboard Claim Guide/confirm.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Dashboard Claim Guide/confirm.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Dashboard Claim Guide/connect.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Dashboard Claim Guide/connect.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Dashboard Claim Guide/connect1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Dashboard Claim Guide/connect1.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Mainnet/code user multiplier.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Mainnet/code user multiplier.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Mainnet/codelockend.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Mainnet/codelockend.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Mainnet/сode lockclaim.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Mainnet/сode lockclaim.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/add sepolia.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/add sepolia.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/approve.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/approve.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/approvemainnet.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/approvemainnet.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/capital lockclaim.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/capital lockclaim.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/claimlockend.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/claimlockend.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/convert multiplier.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/convert multiplier.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/date to timestamp.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/date to timestamp.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/mint mock steth.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/mint mock steth.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/stake.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/stake.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/timestamp to date(new).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/timestamp to date(new).png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/timestamp to date.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/timestamp to date.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/user multiplier.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/user multiplier.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/wei convert.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/wei convert.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/weights lockclaim.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/MOR Rewards Staking Guides/Testnet/weights lockclaim.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Morpheus Capital Providers Contract Guide/approval.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Morpheus Capital Providers Contract Guide/approval.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Morpheus Capital Providers Contract Guide/deposit.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Morpheus Capital Providers Contract Guide/deposit.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Morpheus Capital Providers Contract Guide/deposited.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Morpheus Capital Providers Contract Guide/deposited.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Morpheus Capital Providers Contract Guide/rewards.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Morpheus Capital Providers Contract Guide/rewards.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Morpheus Capital Providers Contract Guide/withdraw.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Morpheus Capital Providers Contract Guide/withdraw.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Morpheus Lumerin Model/figure1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Morpheus Lumerin Model/figure1.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Morpheus Lumerin Model/figure2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Morpheus Lumerin Model/figure2.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Morpheus Lumerin Model/figure3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Morpheus Lumerin Model/figure3.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Morpheus Node/ Architecture.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Morpheus Node/ Architecture.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Morpheus Node/ Session Flow.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Morpheus Node/ Session Flow.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Morpheus Node/ Smart Contracts Structure.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Morpheus Node/ Smart Contracts Structure.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Phased AMM Deployment/1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Phased AMM Deployment/1.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Phased AMM Deployment/2-.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Phased AMM Deployment/2-.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Phased AMM Deployment/3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Phased AMM Deployment/3.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Phased AMM Deployment/4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Phased AMM Deployment/4.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Phased AMM Deployment/range1-.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Phased AMM Deployment/range1-.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Phased AMM Deployment/range2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Phased AMM Deployment/range2.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/README/Data agent.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/README/Data agent.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/README/agent_clarify3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/README/agent_clarify3.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/README/successful_swap2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/README/successful_swap2.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/README/wallet_integration1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/README/wallet_integration1.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/add increase.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/add increase.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/add token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/add token.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/approve increase.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/approve increase.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/approve weth.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/approve weth.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/approve1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/approve1.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/approve2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/approve2.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/approve3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/approve3.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/arb.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/arb.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/change chain.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/change chain.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/chose token.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/chose token.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/confirm increase.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/confirm increase.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/connect1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/connect1.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/connect2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/connect2.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/deposit amounts.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/deposit amounts.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/fee tier.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/fee tier.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/import morr.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/import morr.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/increase liquidity.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/increase liquidity.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/mint.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/mint.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/new position.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/new position.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/percentage.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/percentage.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/positions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/positions.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/price range.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/price range.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/remove liquidity.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/remove liquidity.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/select mor.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/select mor.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/select tokens.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/select tokens.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/select weth.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/select weth.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/success increase.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/success increase.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/swap success.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/swap success.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/swap successs.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/swap successs.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/swap weth mor.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/swap weth mor.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/swap.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/swap.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/English/Uniswap Guide/warning.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/English/Uniswap Guide/warning.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/French/Installation Guide.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/French/Installation Guide.jpeg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/German/Meme for TCM German.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/German/Meme for TCM German.jpeg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/German/Whitepaper/1 for German WP.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/German/Whitepaper/1 for German WP.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/German/Whitepaper/2 for German WP.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/German/Whitepaper/2 for German WP.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/German/Whitepaper/3 for German WP.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/German/Whitepaper/3 for German WP.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/German/Whitepaper/4 for German WP.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/German/Whitepaper/4 for German WP.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/German/Whitepaper/5 for German WP.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/German/Whitepaper/5 for German WP.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/German/Whitepaper/6 for German WP.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/German/Whitepaper/6 for German WP.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/German/Whitepaper/7 for German WP.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/German/Whitepaper/7 for German WP.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/German/Whitepaper/8 for German WP.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/German/Whitepaper/8 for German WP.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/German/Whitepaper/9 for German WP.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/German/Whitepaper/9 for German WP.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Indonesian/Whitepaper/Circulation.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Indonesian/Whitepaper/Circulation.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Indonesian/Whitepaper/Diagram_Pengguna.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Indonesian/Whitepaper/Diagram_Pengguna.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Indonesian/Whitepaper/Distribute.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Indonesian/Whitepaper/Distribute.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Indonesian/Whitepaper/Emission.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Indonesian/Whitepaper/Emission.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Indonesian/Whitepaper/Emitted.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Indonesian/Whitepaper/Emitted.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Indonesian/Whitepaper/MorpheusNetwork.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Indonesian/Whitepaper/MorpheusNetwork.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Indonesian/Whitepaper/Supply_curve.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Indonesian/Whitepaper/Supply_curve.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Indonesian/Whitepaper/Year.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Indonesian/Whitepaper/Year.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Polish/Whitepaper/001 Morpheus Logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Polish/Whitepaper/001 Morpheus Logo.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Polish/Whitepaper/01 Morpheus Whitepaper Polish.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Polish/Whitepaper/01 Morpheus Whitepaper Polish.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Polish/Whitepaper/02 Morpheus Whitepaper Polish.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Polish/Whitepaper/02 Morpheus Whitepaper Polish.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Polish/Whitepaper/03 Morpheus Whitepaper Polish.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Polish/Whitepaper/03 Morpheus Whitepaper Polish.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Polish/Whitepaper/04 Morpheus Whitepaper Polish.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Polish/Whitepaper/04 Morpheus Whitepaper Polish.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Polish/Whitepaper/05 Morpheus Whitepaper Polish.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Polish/Whitepaper/05 Morpheus Whitepaper Polish.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Polish/Whitepaper/06 Morpheus Whitepaper Polish.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Polish/Whitepaper/06 Morpheus Whitepaper Polish.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Polish/Whitepaper/07 Morpheus Whitepaper Polish.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Polish/Whitepaper/07 Morpheus Whitepaper Polish.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Polish/Whitepaper/08 Morpheus Whitepaper Polish.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Polish/Whitepaper/08 Morpheus Whitepaper Polish.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Russian/ Meme for TCM RU.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Russian/ Meme for TCM RU.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Ukrainian/Meme for TCM UA.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Ukrainian/Meme for TCM UA.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Whitepaper/5050version3.jpg: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Whitepaper/ComputeContractImage2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Whitepaper/ComputeContractImage2.png -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Whitepaper/MOR25ScenarioV9.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Whitepaper/MOR25ScenarioV9.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Whitepaper/MOREmissionSchedule.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Whitepaper/MOREmissionSchedule.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Whitepaper/MOREmissionsCurve2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Whitepaper/MOREmissionsCurve2.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Whitepaper/MORSupplyCurve20231019.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Whitepaper/MORSupplyCurve20231019.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Whitepaper/MaxMORScenario25.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Whitepaper/MaxMORScenario25.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Whitepaper/MorpheusNetworkDiagram.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Whitepaper/MorpheusNetworkDiagram.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Whitepaper/UpdatedDiagram2UserFlow.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Whitepaper/UpdatedDiagram2UserFlow.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Yellowpaper/2023-10-15_13-28-08_page-0001.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Yellowpaper/2023-10-15_13-28-08_page-0001.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Yellowpaper/Diagram1ofETHDontator_page-0001.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Yellowpaper/Diagram1ofETHDontator_page-0001.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Yellowpaper/Diagram3ForETHGiven_page-0001.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Yellowpaper/Diagram3ForETHGiven_page-0001.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Yellowpaper/Diagram_page-0001.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Yellowpaper/Diagram_page-0001.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Yellowpaper/ETHGivenDiagram2_page-0001.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Yellowpaper/ETHGivenDiagram2_page-0001.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Yellowpaper/MORForCompute2_page-0001.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Yellowpaper/MORForCompute2_page-0001.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Yellowpaper/MORForCompute_page-0001.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Yellowpaper/MORForCompute_page-0001.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Yellowpaper/MorpheusDecentralized_page-0001.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Yellowpaper/MorpheusDecentralized_page-0001.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Yellowpaper/MorpheusLocalDiagram_page-0001.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Yellowpaper/MorpheusLocalDiagram_page-0001.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Yellowpaper/MorpheusP2PDiagram_page-0001.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Yellowpaper/MorpheusP2PDiagram_page-0001.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Yellowpaper/User_Contributor_Diagram_page-0001.jpg: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Yellowpaper/mordist_page-0001.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Yellowpaper/mordist_page-0001.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Yellowpaper/new-buckets_page-0001.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Yellowpaper/new-buckets_page-0001.jpg -------------------------------------------------------------------------------- /Graphics/Docs Graphics/Urdu/Yellowpaper/ticketing_page-0001.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/Docs Graphics/Urdu/Yellowpaper/ticketing_page-0001.jpg -------------------------------------------------------------------------------- /Graphics/MOR network diagram.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/MOR network diagram.png -------------------------------------------------------------------------------- /Graphics/logos/Logo Files.md: -------------------------------------------------------------------------------- 1 | Logo files for free use by the Morpheus community use. 2 | 3 | **PDF Format:** 4 | [MORPHEUS_vector_v1.pdf](https://github.com/MorpheusAIs/Morpheus/files/13394782/MORPHEUS_vector_v1.pdf) 5 | 6 | **PNG Format:** 7 | ![MORPHEUS_vector_v1-01](https://github.com/MorpheusAIs/Morpheus/assets/1563345/ae08ce1d-e5a8-48ee-b2a7-b8b3dbf36caf) 8 | 9 | **JPEG Format:** 10 | ![MORPHEUS_vector_v1-01](https://github.com/MorpheusAIs/Morpheus/assets/1563345/e925c4ea-60f3-48ea-ac3a-a054084a2e76) 11 | 12 | **SVG Format:** 13 | ![MORPHEUS_vector_v1](https://github.com/MorpheusAIs/Morpheus/assets/1563345/f82a5648-8bd4-4ff3-815b-885cc1c6dc15) 14 | 15 | **White Logo SVG Format:** 16 | ![MORPHEUS_white_vector_v2](https://github.com/MorpheusAIs/Docs/blob/main/Graphics/Morpheus%20Logo%20-%20White.svg) 17 | 18 | -------------------------------------------------------------------------------- /Graphics/logos/MOR gradient logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Graphics/logos/MOR gradient logo.png -------------------------------------------------------------------------------- /Graphics/logos/Morpheus Brand Kit | Graphics Guide.md: -------------------------------------------------------------------------------- 1 | # Morpheus Brand Kit | Graphics Guide 2 | 3 | ## Common Colors Used in Morpheus 4 | 5 | - Mor.org Background: #03170F (Dark Green) 6 | - Buttons/Header: #1EDC8D (Light Green) 7 | - White Logo: #ECEDEC
 (Off-White) 8 | 9 | ### Examples: 10 | 11 | [Mor.org](https://www.mor.org) 12 | 13 | [X Profile](https://twitter.com/MorpheusAIs) 14 | 15 | ### Frequently Used Images: 16 | 17 | [Link to Black Logo on White](https://github.com/MorpheusAIs/Morpheus/assets/1563345/f82a5648-8bd4-4ff3-815b-885cc1c6dc15 ) 18 | 19 | [Link to White Logo with transparent background](https://github.com/MorpheusAIs/Docs/Graphics/logos/Morpheus%20Logo%20-%20White.svg) 20 | 21 | [Other Common Logo Files](https://github.com/MorpheusAIs/Docs/Graphics/logos/LogoFiles.md) 22 | 23 | [Morpheus Ecosystem Badges](https://github.com/MorpheusAIs/Docs/Graphics/logos/MorpheusEcosystemLogo.md) 24 | 25 | [Full Design Library Here](https://github.com/MorpheusAIs/Docs/Graphics/Design%20Library.md) 26 | -------------------------------------------------------------------------------- /Graphics/logos/Morpheus Ecosystem Logo.md: -------------------------------------------------------------------------------- 1 | # Morpheus Ecosystem Logo Badge Zip File 2 | 3 | [Morpheus_Ecosystem_Badge.zip](https://github.com/MorpheusAIs/Docs/files/15082003/Morpheus_Ecosystem_Badge.zip) 4 | 5 | Open source and available to all projects and people who count themselves as part of the Morpheus Ecosystem. 6 | 7 | Zip includes: PNG version, SVG version, white, black and green versions. 8 | -------------------------------------------------------------------------------- /Graphics/logos/Morpheus Logo - White.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 10 | 11 | 12 | 13 | -------------------------------------------------------------------------------- /Graphics/logos/Video logos.md: -------------------------------------------------------------------------------- 1 | https://drive.google.com/drive/folders/11PbKnH9X98JgOA9Pml2zjxf6mFaVws8f?usp=sharing 2 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2025 Morpheus 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /Security Audit Reports/Builders/Morpheus BuildersV2 Audit Report | Trust Security.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Security Audit Reports/Builders/Morpheus BuildersV2 Audit Report | Trust Security.pdf -------------------------------------------------------------------------------- /Security Audit Reports/Compute/Morpheus Lumerin Audit Report 1 | Renascence.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Security Audit Reports/Compute/Morpheus Lumerin Audit Report 1 | Renascence.pdf -------------------------------------------------------------------------------- /Security Audit Reports/Compute/Morpheus Lumerin Audit Report 2 | Renascence.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Security Audit Reports/Compute/Morpheus Lumerin Audit Report 2 | Renascence.pdf -------------------------------------------------------------------------------- /Security Audit Reports/Compute/Morpheus Lumerin Audit Report 3 | Renascence.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Security Audit Reports/Compute/Morpheus Lumerin Audit Report 3 | Renascence.pdf -------------------------------------------------------------------------------- /Security Audit Reports/Distribution Contract/Distribution V2 Audit | Renascence.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Security Audit Reports/Distribution Contract/Distribution V2 Audit | Renascence.pdf -------------------------------------------------------------------------------- /Security Audit Reports/Distribution Contract/Distribution V3 (Capital Staking) Audit | Renascence.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Security Audit Reports/Distribution Contract/Distribution V3 (Capital Staking) Audit | Renascence.pdf -------------------------------------------------------------------------------- /Security Audit Reports/Distribution Contract/Distribution V3 (Code Staking) Audit | Renascence.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Security Audit Reports/Distribution Contract/Distribution V3 (Code Staking) Audit | Renascence.pdf -------------------------------------------------------------------------------- /Security Audit Reports/Distribution Contract/Distribution V4 (Claim Lock) Audit | Renascence.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Security Audit Reports/Distribution Contract/Distribution V4 (Claim Lock) Audit | Renascence.pdf -------------------------------------------------------------------------------- /Security Audit Reports/Distribution Contract/Distribution V5 (Referral Program) Audit | Renascence.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Security Audit Reports/Distribution Contract/Distribution V5 (Referral Program) Audit | Renascence.pdf -------------------------------------------------------------------------------- /Security Audit Reports/L2 Token Receiver V2/L2TokenReceiverV2 Audit (Final) | Renascence.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Security Audit Reports/L2 Token Receiver V2/L2TokenReceiverV2 Audit (Final) | Renascence.pdf -------------------------------------------------------------------------------- /Security Audit Reports/L2 Token Receiver V2/L2TokenReceiverV2 Audit (Initial) | Renascence.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Security Audit Reports/L2 Token Receiver V2/L2TokenReceiverV2 Audit (Initial) | Renascence.pdf -------------------------------------------------------------------------------- /Security Audit Reports/MOR OFT Token/MOR Dynamic Minter Security Audit (Wormhole) | Renascence.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Security Audit Reports/MOR OFT Token/MOR Dynamic Minter Security Audit (Wormhole) | Renascence.pdf -------------------------------------------------------------------------------- /Security Audit Reports/MOR OFT Token/MOR Token Contract | OpenZepellin.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Security Audit Reports/MOR OFT Token/MOR Token Contract | OpenZepellin.pdf -------------------------------------------------------------------------------- /Security Audit Reports/MOR20 Contracts | Renascence.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MorpheusAIs/Docs/2a32885db9ee2c58fd80e16ec17dbf55141bb0c9/Security Audit Reports/MOR20 Contracts | Renascence.pdf -------------------------------------------------------------------------------- /Smart Contracts/LinearDistributionIntervalDecrease.md: -------------------------------------------------------------------------------- 1 | # LinearDistributionIntervalDecrease 2 | 3 | [`LinearDistributionIntervalDecrease.sol`](https://github.com/MorpheusAIs/SmartContracts/blob/main/contracts/libs/LinearDistributionIntervalDecrease.sol) is a custom library used by [`Distribution`](Distribution.md) to calculate MOR token rewards for a specified period. It supports linear distribution schedules with stepped decreases at regular intervals. 4 | 5 | ## Functions 6 | 7 | ### getPeriodReward 8 | 9 | ```solidity 10 | function getPeriodReward( 11 | uint256 initialAmount_, 12 | uint256 decreaseAmount_, 13 | uint128 payoutStart_, 14 | uint128 interval_, 15 | uint128 startTime_, 16 | uint128 endTime_ 17 | ) external pure returns (uint256) 18 | ``` 19 | 20 | Calculates and returns the reward amount for a given period and distribution parameters. The calculation accounts for partial intervals pro rata. 21 | 22 | #### Parameters 23 | 24 | | Name | Type | Description | 25 | |-------------------|---------|----------------------------------------------------------| 26 | | `initialAmount_` | uint256 | The initial reward amount per interval. | 27 | | `decreaseAmount_` | uint256 | The amount by which the reward decreases each interval. | 28 | | `payoutStart_` | uint128 | The timestamp at which the distribution schedule starts. | 29 | | `interval_` | uint128 | The duration of each interval in seconds. | 30 | | `startTime_` | uint128 | The timestamp at which the period starts. | 31 | | `endTime_` | uint128 | The timestamp at which the period ends. | 32 | 33 | #### Return Values 34 | 35 | | Type | Description | 36 | |---------|--------------------------------------| 37 | | uint256 | The reward for the specified period. | -------------------------------------------------------------------------------- /Smart Contracts/MOROFT.md: -------------------------------------------------------------------------------- 1 | # MOROFT 2 | 3 | [`MOROFT.sol`](https://github.com/MorpheusAIs/SmartContracts/blob/main/contracts/MOROFT.sol), the Morpheus token, is a [LayerZero Omnichain Fungible Token](https://docs.layerzero.network/v2/developers/evm/oft/quickstart) (OFT). This allows the token to be transferred across [supported networks](https://docs.layerzero.network/v2/developers/evm/technical-reference/endpoints) such as Ethereum, Arbitrum, BNB Chain, and others without the need for wrapping. 4 | 5 | Tokens can only be minted by the immutable `minter_` – [`L2MessageReceiver`](L2MessageReceiver.md) – when claimed by users. 6 | 7 | ## Functions 8 | 9 | *Standard [ERC20](https://docs.openzeppelin.com/contracts/2.x/api/token/erc20) and [OFT](https://docs.layerzero.network/v2/developers/evm/oft/quickstart) functions are not listed below.* 10 | 11 | ### mint 12 | 13 | ```solidity 14 | function mint( 15 | address _account, 16 | uint256 amount_ 17 | ) external onlyOwner 18 | ``` 19 | 20 | Mints new tokens to the specified account. This function can only be called by the `_minter_` – [`L2MessageReceiver`](L2MessageReceiver.md). 21 | 22 | #### Parameters: 23 | 24 | | Name | Type | Description | 25 | |------------|---------|-----------------------------------------| 26 | | `_account` | address | The account to which tokens are minted. | 27 | | `_amount` | uint256 | The number of tokens to mint. | 28 | 29 | --- 30 | 31 | ### burn 32 | 33 | ```solidity 34 | function burn( 35 | uint256 _amount 36 | ) public override 37 | ``` 38 | 39 | Burns a specified amount of tokens from the caller's account, reducing the total supply. 40 | 41 | #### Parameters: 42 | 43 | | Name | Type | Description | 44 | |-----------|---------|--------------------------------------------------------------------| 45 | | `_amount` | uint256 | The number of tokens to be burned (removed) from the total supply. | 46 | 47 | ### burnFrom 48 | 49 | ```solidity 50 | function burnFrom( 51 | address _account, 52 | uint256 _amount 53 | ) public override 54 | ``` 55 | 56 | Burns a specified amount of tokens from the specified account, reducing the total supply. The caller must have allowance for at least the specified amount of tokens. 57 | 58 | #### Parameters: 59 | 60 | | Name | Type | Description | 61 | |------------|---------|--------------------------------------------------------------------| 62 | | `_account` | uint256 | The account from which to burn tokens. | 63 | | `_amount` | uint256 | The number of tokens to be burned (removed) from the total supply. | 64 | 65 | ### minter 66 | 67 | ```solidity 68 | function minter( 69 | ) public view returns(address) 70 | ``` 71 | 72 | Returns the address of the `minter_`. 73 | 74 | #### Return Values 75 | 76 | | Type | Description | 77 | |---------|-------------------------------| 78 | | address | The address of the `minter_`. | --------------------------------------------------------------------------------