Shared Libraries - Core MM Wallet

[desi]

2024/Q1/O1/KR1 Description: MVP Definition, POC and Technical Proposal Define and plan MVP for MM Wallet Library. [boolean] Much of the core wallet functionality is managed by specific libraries known as “controllers”. Most of these controllers now live in the core monorepo, but it is up to each client to wire them up in order to fully initialize the client. It is also up to each client to stay up to date on updates to each controller. To make this easier, we want to build a wallet library. There are a number of other reasons that such a library would be beneficial and since the majority of the pre-requisite work has been completed we’d like to begin planning what the next iteration would look like.

The following is a list of all benefits:

• Improved developer experience for the client platform teams (e.g. easier to use, easier to audit, to update, etc.)
• Additional platform capabilities (automatically get anonymized state, persisted state)
• Reduced maintenance for DevEx team (shared RPC pipeline between clients)
• Allows us to more easily write e2e tests and performance benchmarks, improving overall quality/stability and performance
• Helps to establish clearer roles/responsibilities between Shared Libraries and other teams

Deliverables for this would be:

• Technical proposal written and passed (early Q1)
• POC
• MVP defined
• Project plan / roadmap / strategy defined