MEM
WebsiteLabsGuides
  • โš—๏ธMolecular Execution Machine
  • ๐Ÿ‘‹Introduction
    • What is MEM?
    • MEM features
    • MEM vs alternatives
    • Technical architecture
    • Use-case examples
  • โšกQuickstart
    • Quickstart guide
  • ๐Ÿ“–MEM Specifications
    • Function syntax
    • Function specs
    • Transaction specs
    • Supported languages
    • About MIPs
  • โš›๏ธMolecules
    • Overview
    • Multichain authentication
    • Using APIs
    • API reference
  • ๐ŸงชMEM IDE
    • Overview
    • Function ABI
  • โš’๏ธMEM Carbon Testnet
    • Overview
    • Deploy to testnet
    • Interact with testnet functions
  • โš™๏ธMEM SDK
    • SDK Usage
  • ๐Ÿ–ฅ๏ธMEM CLI
    • Function deployment
    • Function interaction
  • ๐Ÿ—๏ธMEM API
    • Overview
    • Write operations
    • Read operations
  • โš›๏ธ3EM-MEM
    • Overview
    • EXM API
    • Key-Value Storage (KVS)
  • ๐ŸงฉExamples
    • Pastebin clone
    • Query onchain data
Powered by GitBook

mem.tech ยฉ 2023

On this page
  1. MEM Specifications

About MIPs

About MEM Improvement Proposals

PreviousSupported languagesNextOverview

Last updated 1 year ago

MIP stands for MEM Improvement Proposal. A MIP is a design document providing information to the MEM community, or describing a new feature for MEM or its processes or environment. The MIP should provide a concise technical specification of the feature and a rationale for the feature.

We intend MIPs to be the primary mechanisms for proposing new features, collecting community input on an issue, and for documenting the design decisions that have gone into MEM. The MIP author is responsible for building consensus within the community and documenting dissenting opinions.

Because the MIPs are maintained as text files in a versioned repository, their revision history is the historical record of the feature proposal.

Check the MEM Improvement Proposals (MIPs) repository:

๐Ÿ“–
https://github.com/decentldotland/MIPs