Svyatoslav Nikolsky

Details: https://github.com/bitcoincashorg/bitcoincash.org/pull/94 - [X] Remove topological transaction order constraint, and enforce canonical transaction order (see [this paper](https://blog.vermorel.com/pdf/canonical-tx-ordering-2018-06-12.pdf)). Notes: affects mining code. - [X] Enable OP_CHECKDATASIG and OP_CHECKDATASIGVERIFY opcodes (see [this...

Hardfork/upgrade trigger

3

Case: BCH Nov2018 HF adds new consensus rule - all transactions must have a serialized size > 100 bytes. If memory pool contains some transactions of size < 100 bytes...

Just not to forget lessons I've learned using this wifi: - [x] requests to sync peers should be ordered. let scheduled_queue = [b0, b1, b2, b3]. let fast_peers = [p0,...

Proper fix for `verification::Deployments` panic

1

Originally code in `support_segwit` branch had a panic here: https://github.com/paritytech/parity-bitcoin/blob/2cacae099ead6b8240a570e4b9226e4007843be5/verification/src/deployments.rs# This was fixed (temporarily?) by this commit: https://github.com/paritytech/parity-bitcoin/commit/9e58d50d9124c2c6ce89bed0705292ce20c387e5#diff-39fbf28d89d87ddaff46695c971ec50fR142 But: 1) looks like it is fix of side-effects, not the original...

In-memory storage for headers

1

from slack: guys, for `getblock` RPC method I need `chainwork` for the block. I have found two approaches to get this. First one is to store this with block in...

MemoryPool::iter is too slow

2

MemoryPool was designed to support fast removal, but not fast read => now it's time to get rid of `remove_by_strategy` in favor of `read_by_strategy`

To select transactions from MemoryPool for mining instantly

=> while working on the top of blockchain it will continue to hold old unmined transactions forever suggesting limits: num of transactions + memory allocated for transactions removal strategy: FIFO

Verification of in-block transaction with many inputs takes too long

1

Verification of transactions: https://blockchain.info/ru/tx/6bb9c31f15c6940d4bd664054e398e420425339aadc65e8c491cf1151fe7ff4b https://blockchain.info/tx/b9d69463c500b81dc2ff600d0b528b15fb816c4dab11e424151de0bcbea7f26f takes ~10-15s on my PC. While verification of most others takes < 1/20s. Maybe we could profile this in tests && check if we could...

Reminder to myself. Comment: https://github.com/paritytech/parity-bitcoin/pull/396/files/b1b8619592ff4b9367ed3f5551d04390e3c7b052#r111335643