Skip to content

Instantly share code, notes, and snippets.

@melekes
Last active June 1, 2019 03:30
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save melekes/ab7ef05f6cb428cc0a82ce5d28042558 to your computer and use it in GitHub Desktop.
Save melekes/ab7ef05f6cb428cc0a82ce5d28042558 to your computer and use it in GitHub Desktop.
Requirements for a Tendermint client

Requirements for a Tendermint client

Broadcasting transactions

  1. An evil proposer can drop valid transactions (tendermint/tendermint#3322). To ensure tx A will be committed, the client needs to a) send it to multiple nodes b) subscribe for its result https://tendermint.com/docs/app-dev/subscribing-to-events-via-websocket.html or query the result later using /tx API endpoint (requires the tx indexer enabled) https://tendermint.com/rpc/#tx.

  2. Multiple nodes above requirement comes from a simple fact that an evil node can drop your tx.

Quering

TODO: verifying a proof, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment