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
  • Function DA Transaction Tags
  • MEM Functions Source Code Arweave Transaction Data
  1. MEM Specifications

Function specs

MEM function specifications

Similar to transactions, MEM functions must adhere to specific rules to ensure compatibility with the MEM specifications.

Function DA Transaction Tags

  • Content-Type : the function source code type (MIME type)

  • App-Name : EM

  • Type : Serverless-Function

  • EM-Bundled : true

  • Size : the contractSrc array length

MEM Functions Source Code Arweave Transaction Data

{
  "contentType": "$MIME_TYPE",
  "contractSrc": [], // array of character codes
  "initState": "{}" // the stringified JSON initial state
}
PreviousFunction syntaxNextTransaction specs

Last updated 1 year ago

๐Ÿ“–