Svyatoslav Nikolsky
Svyatoslav Nikolsky
Adrian is the best person to answer here, but imo let's make it similar to other APIs perhaps - i.e. deal with leafs?
I can't say much - @andresilva was there when it was designed that way (offchain worker) - maybe there's some strong reasoning behind that. But do you want to keep...
Definitely some `--verification-level=none` -related issue. Will try to reproduce, but as I mentioned before - this level should never be used in any production system. No verification at all means...
So I have synchronized to ~250k about 20 times without validation in last 3 days. Haven't seen any issue. Code analysis shows that this error occurs when: 1) block which...
Also it would be great if you could reproduce this with `RUST_LOG=sync=trace,verification=trace,db=trace` env var set. This should help to find a reason.
Thanks for your interest in parity-zcash! :) I was talking about parity-zcash there, in #36 . And since parity-zcash shares most of functionality with parity-bitcoin, I'd insist that the `CpuMiner`...
(1) && (5) are fixed in #451 && #452
They **should not**, but right they are staying in current implementation. We only remove transactions that are included in the block && transactions that are relying on inputs that are...
Source code reference: https://github.com/paritytech/parity-bitcoin/blob/master/sync/src/synchronization_chain.rs#L379
Thank you for the report! This could be solved by simply updating `jsonrpc` references. But it isn't that simple now - we are too far beyond master oof a lot...