Blockchains are a system for creating shared multi-master application state. TMSP is a socket protocol enabling a blockchain consensus engine, running in one process, to manage a blockchain application state, running in another.

For more information on TMSP, motivations, and tutorials, please visit our blog post.

• Arguments:
  • TxBytes ([]byte)
• Returns:
  • RetCode (int8)
• Usage:
  Append and run a transaction. The transaction may or may not be final.

• Returns:
  • RetCode (int8)
  • Hash ([]byte)
• Usage:
  Return a Merkle root hash of the application state

• Returns:
  • RetCode (int8)
• Usage:
  Finalize all appended transactions

• Returns:
  • RetCode (int8)
• Usage:
  Roll back to the last commit

• Arguments:
  • EventKey (string)
• Returns:
  • RetCode (int8)
• Usage:
  Add event listener callback for events with given key.

• Arguments:
  • EventKey (string)
• Returns:
  • RetCode (int8)
• Usage:
  Remove event listener callback for events with given key.

• Usage:
  Flush the response queue. Applications that implement types.Application need not implement this message -- it's handled by the project.

• Returns:
  • Data ([]string)
• Usage:
  Return an array of strings about the application state. Application specific.

• Arguments:
  • Key (string)
  • Value (string)
• Returns:
  • RetCode (int8)
• Usage:
  Set application options. E.g. Key="mode", Value="mempool" for a mempool connection, or Key="mode", Value="consensus" for a consensus connection. Other options are application specific.