morpheusais/docs

Technical Documentation

docs's Issues

Translation issue in WhitePaper of Chinese edition

There are some little translation issues in Chinese WhitePaper.

"Community" -> "复杂的"
"Capital" -> "首都"
"stETH" -> "斯蒂斯"
"MOR" -> "公尺"

Withdrawing my deposit

I can’t withdraw my steth back to my wallet. It’s not showing on the platform. 7 days elapsed from the deposit date

Issue of transparency of contributions in past snapshots

Some contributions (quite a lot of weigth points) in the snapshot 1 & 2 table are anonymous or @username only (without a link to commit or PR). Which removes the transparency of the contributions. Also, some links to code contribution are already outdated and don't work (404). Perhaps this can be re-evaluated and updated somehow to improve transparency.

Morpheus Windows, displaying incorrect ETH and WETH balance

Images below:

Morpheus displays a balance of 0.00 ETH and WETH.

Metamask connected through IOS Metamask app.

Missing/broken link for community and compute page

Morpheus project should secure its social handles to prevent bad actors getting them.

Morpheus project should secure its social handles to prevent bad actors getting them.

FAQs.md discord links display Invalid Invite

The How can I contribute? discord links on the Docs / !KEYDOCS README FIRST! / FAQs.md are displaying Invite Invalid.

Affected channel invites:

• 👥 dev-intros
• 👥 designer-intros
• 🎣 skills
• 🤖 smart-agent-dev
• 🦾 rag-dev
• 🎛 llm-fine-tunes
• 🖼 front-end

Discord Documentation:
https://support.discord.com/hc/en-us/articles/360001556852-Invalid-Invite-Links

No way to contact

Hello, I accidentally sent stETH to the multisig on launch and have no way to contact the people on the multisig. the wording in this tweet confused me and assumed that on launch I could send there to stake https://x.com/MorpheusAIs/status/1754949646336553131?s=20
If there is anyway to contact the multisig plz lmk as I would appreciate getting it sent back.
here is the txn https://etherscan.io/tx/0x7bb90aa13d5189467880a280b8806bcd54879e891f8e1060d024b76f7a88dda7
Sorry to raise as an issue on github, but dont know where else to find a contact for people on the multisig.

Coder Guide > Morphues Request for Comments link results in `404 Not Found`

The link under the heading Morphues Request for Comments in Docs / !KEYDOCS README FIRST! / Coder Guide.md results in a 404 Not Found

Example:

morpheus windows stuck initializing

stuck initializing

Make FAQs.md questions linkable for communications in discord & other social

It would be super convenient for discord moderators and even responding to comments on social, if the FAQs questions were markdown headers. Markdown headers are linkable, so we can deep link to the specific question a user is asking rather than sending them to the top of the FAQ.

Currently:

The questions are currently using **bold** markdown

Suggested:

Change the questions markdown to us ### Question?

Example:

questions-are-not-linkable.mov

Strategic Advantages of Launching the Morpheus Token on Flare Networks

In this whitepaper, we delve into the strategic advantages of launching the Morpheus token (MOR) on Flare Networks, as opposed to alternatives like Arbitrum. Our recommendation is deeply rooted in the unique technological advancements offered by Flare, specifically its Time Series Oracle (FTSO) and State Connector. These technologies together create a secure, decentralized framework for data procurement, which is crucial for the autonomous functionality of Morpheus's intelligent agents. By highlighting the need for real-time, reliable data, we position Flare Networks as not just an option but a strategic asset for Morpheus.

The convergence of blockchain technology and artificial intelligence marks a significant evolution in the digital domain, with Morpheus at the forefront of this transformation. Our strategy leverages intelligent agents that require immediate and secure data access, essential for their operational integrity. Opting for Flare Networks is guided by the exceptional capabilities of the FTSO and State Connector, which together provide a robust data environment vital for the agents' complex operations.

We advocate for the adoption of Flare Networks' upcoming FAssets and Layer Cake protocols to enhance interoperability and operational efficiency of blockchain-based smart agents. This strategy will significantly broaden and streamline Morpheus agents' ability to conduct cross-chain transactions, effectively overcoming interoperability barriers.

Layer Cake, in conjunction with FAssets, is designed to facilitate seamless transactions across a variety of blockchain networks, eliminating the traditional barriers that have segmented the blockchain ecosystem. This development will greatly expand the operational reach of Morpheus agents, driving us towards unmatched cross-chain interoperability. Integrating these protocols signifies more than just an enhancement of Morpheus's framework; it is a significant advancement in the evolution of blockchain interoperability, ensuring Morpheus agents lead in the domain of intelligent, autonomous, and adaptable digital agents.

Suggested Launch Platform: Flare Networks
Our strategic recommendation to launch Morpheus on Flare Networks is underpinned by a thorough analysis of its merits, including:

-Secure, Decentralized Infrastructure: Fundamental for deploying intelligent agents, ensuring operational security and autonomy.
https://flare.network/flare-101/

-State Connector: Establishes consensus on data from other blockchains and the web, safeguarding the integrity of smart contracts on Flare.
https://flare.network/stateconnector/

-Flare Time Series Oracle (FTSO): Provides decentralized, accurate time series data, such as cryptocurrency prices, indispensable for the autonomous operation of Flare network's applications.
https://flare.network/ftso/

-Enhancing Interoperability: FAssets and Layer Cake
https://flarelabs.org/

We encourage embracing Flare Networks' FAssets and Layer Cake protocols, groundbreaking innovations poised to reshape blockchain interoperability and significantly benefit Morpheus. FAssets broadens the ecosystem for Morpheus agents by facilitating interactions with an expanded asset spectrum, thereby boosting the MOR token's market appeal and liquidity. Conversely, Layer Cake advances Morpheus into new dimensions of cross-chain communication, enabling operations across numerous networks and reinforcing Morpheus's prominence in the blockchain sphere.

Conclusion
Our recommendation to integrate Morpheus within the Flare Network, making use of the State Connector, FTSO, FAssets, and Layer Cake, goes beyond ordinary enhancements in agent functionality. It places Morpheus at the forefront of innovation, redefining cross-chain interactions and the application of blockchain technology in meaningful, impactful ways. This strategic direction not only elevates Morpheus's capabilities but also has the potential to revolutionize the blockchain interoperability landscape, positioning MOR tokens at the helm of this transformative journey.

Additionally, it's noteworthy to mention that Flare Networks is also delving into the realm of artificial intelligence, with their chief scientist having recently released a paper on “Consensus Learning, a novel decentralised machine learning paradigm.” Link: https://arxiv.org/pdf/2402.16157.pdf

This exploration suggests potential synergies between both projects. While I may not possess the technical expertise to fully ascertain how these synergies could function in collaboration, our ambition to accelerate decentralization fuels this proposal.
The intent of this discussion is to question whether Arbitrum is indeed the optimal network for the launch of Morpheus, or whether we should consider leveraging a network that aligns more closely with our values of decentralization and data integrity. Encouraging dialogue between Morpheus AI and the Flare Networks team could foster innovation in exciting new ways. I am eager to see the fruits of such potential collaboration and how it might propel innovation forward.

Wallet: 0x30CAa43b48B4c54Ea5E36683183Eef75aD603E95

Community Contribution

Couldn't find a way to make a pull request related to 'community' contributions vs. code contributions, but wanted to submit one before May 8th just in case I could qualify for some MOR.

I hosted a Decentralized AI day at SXSW with Gary Sheng and the Morpheus team. Secured funding from ATX DAO and helped promote / coordinate. It included all-day programming and food. Great attendance and talks.

Thanks for all that y'all are doing and looking forward to the release tomorrow!

Instituting downstream applications as upstream guidance is not commensurate

Issue

techno capital machine is a great downstream application. RFC is great to get buy in from existing capital providers and fund seekers. However, downstream applications might not need to be fixed in this matter at this time.

Restructuring docs to improve readability

The current docs structure seems suboptimal -- there is no clear starting point and it's hard to navigate, with information for various stakeholders (and languages!) mixed together.

Would like to propose a new, hierarchical structure where international docs are kept separate. For instance:

• readme.md
• Overview/Concepts
• User Guides
• Morpheus Node
• Contributing
• Architecture/Smart Contracts
• International
  • French
  • Chinese
  • Hindi
  • etc
• Archive

Pending feedback from contributors I'll begin working on a PR that implements this or another clearer structure.

Bug withdrawing stETH from Morpheus Dashboard

Found bug trying to withdraw original stETH amount after staking more stETH. Initially staked 1.2 stETH on fair launch, then another .25 the next day. Fast-forward 2/19/2024; after staking another .25 stETH, unable to withdraw previously staked stETH (~1.5 from previous transactions).

Resolved: The Oracle put in FAQ

Docs typo in image for Morpheus web page -- Specailized instead of Specialized

I found a typo in the image on morpheusai.org 654180_547002.png Instead of Specialized Agents it says Specailized Agents. I didn't find that misspelling in the text.

Metamask

MOR/WETH or MOR/wstETH as MOR's primary trading pair

In reviewing the Morpheus documentation and other writings, as well as the smart contract implementations deployed to Ethereum and Arbitrum, I noticed an inconsistency with regard to what asset MOR will trade against for Protocol-Owned Liquidity.

In some places, the TCM bootstrapping model for Morpheus has its native token MOR trade against WETH; in other places - as well as in the smart contract implementations - it seems MOR will trade against wstETH (wrapped Lido Staked Ethereum).

It would be worth establishing which of these trading pairs is to be used, as some contributors may not be aware of the current implementation.

MOR/WETH or MOR/wstETH?

I believe MOR should trade against WETH, the wrapped ERC20 representation of ETH on Arbitrum. This is the asset of choice for most trading pairs on Arbitrum (see DEXScreener) as users can swap between ETH (the gas token on Arbitrum) and WETH by wrapping/unwrapping without having to worry about slippage. Additionally, since other assets are denominated in WETH, multi-part swaps (e.g. USDC->WETH->MOR) would be cheaper.

I do not see any strong reasons to pair MOR against wstETH, other than the fact the current smart contract implementation seems to support this.

It is worth nothing that there is considerable wstETH/WETH liquidity on Arbitrum, across both Uniswap (~$9.5m liquidity) and Balancer (~15m liquidity) so it would be possible for users to route MOR swaps either way.

Resolution(s)

If the Morpheus community confirms that MOR/wstETH is the preferred trading pair, then it would be enough to update and make consistent the Morpheus documentation and other writings (such as MRC 09: AMM Launch Process) to reflect this.

If MOR/WETH is the preferred pair, I believe modifications would need to be made to the smart contract implementation to enable this.

EDIT: I had assumed there would not be sufficient liquidity to swap wstETH for WETH on Arbitrum, and that it would be necessary to do so on mainnet (see below). However, it appears there is enough liquidity. Nevertheless, the L2TokenReceiver contract responsible for managing PoL does not seem optimized for these swaps. It could be worth adding a dedicated method for wstETH to WETH swaps and adding Balancer support.

For instance, a new function could be added to Distribution that would allow stETH yield to be converted into WETH when called by the Morpheus multisig. In course, the bridgeOverplus function would be modified to bridge WETH to Arbitrum.

To convert stETH into WETH, two methods could be used:

• Swap via DEX
• Unwrap via Lido

While swapping is near instant, it may result in slippage. As a result, it may be best to unwrap stETH directly via Lido, which takes 1-5 days. Although this seems like an inconvenience, it could be made part of a weekly signing schedule:

1. Claim stETH yield in Distribution
2. Begin unstaking stETH yield via Lido
3. Complete unstaking of last week's stETH yield (call claimWithdrawal)
4. Bridge received WETH to Arbitrum

Since the Distribution contract uses an upgradeability proxy pattern, and Capital is held in the Delegator contract, it should be possible to update the implementation contract and thus introduce these features without requiring Capital Providers to migrate.