Marek Kotewicz

first hashing occurs during verification: https://github.com/ethcore/parity-bitcoin/blob/591a6421216097eb60b3eb5c1ca9b455c2275deb/verification/src/chain_verifier.rs#L97 second one during insertion to mempool: https://github.com/ethcore/parity-bitcoin/blob/591a6421216097eb60b3eb5c1ca9b455c2275deb/miner/src/memory_pool.rs#L678 imo, it would be good not to use `chain::Transaction` at all. As soon as we deserialize transaction,...

https://github.com/paritytech/parity-bitcoin/pull/385#pullrequestreview-30979276

republishing transactions

1

It may happen, that relayed transaction are not included in a block, or an authority responsible for relaying them is malicious and hasn't done that. In such case, we should...

create documentation (with examples) for encoding and decoding

1

the documentation should be placed above ethabi `encode` and `decode` functions related #69

in no other constructor is present

tests for issue fixed in #71

Add optional call variant which uses futures

1

related https://github.com/paritytech/ethabi/pull/62#issuecomment-341708679