Exonum 0.10

Internal improvements

• Updated to the Rust-bitcoin 0.14 release (#134).

Breaking changes

• New anchoring implementation is based on native segwit transactions. Acceptance of an
  anchoring transaction still requires the majority of votes of the validators -
  2/3n+1. As the votes are now separated from the transaction body, they do not
  affect transaction hash and, correspondingly, its ID. (#136)

  In this way:

  • Anchoring transactions have become fully deterministic. The problem of transaction
    malleability has,
    thus, been solved. The validators do not have to agree on the latest Exonum
    transaction anchored to Bitcoin blockchain any more to continue the anchoring
    chain.
  • The service can extract the anchoring chain or information on a particular
    anchoring transaction from its database any time by a simple API request. It does
    not need to use a separate observer functionality any more to extract information
    on the latest Exonum anchoring transaction from Bitcoin blockchain and rebuild the
    anchoring chain from of this transaction.
  • There is no need to connect each Exonum node to the bitcoind. The anchoring
    transactions are generated deterministically and independently from the connection
    to the Bitcoin blockchain. New anchoring transactions are monitored by a separate
    method and forwarded to the Bitcoin blockchain whenever they occur.

  For more details on the updated anchoring service operation you can visit the
  readme page.