Co-authored-by: Ori Newman <[email protected]>

Co-authored-by: Ori Newman <[email protected]>

Co-authored-by: Ori Newman <[email protected]>

Co-authored-by: Ori Newman <[email protected]>

Co-authored-by: Ori Newman <[email protected]>

Co-authored-by: Ori Newman <[email protected]>

apply_proof only inserts parent entries for a header from the proof into
the relations store for a level if there was GD data in the old stores
for that header.

This adds a check to filter out parent records not in relations store

…cient root

This happens when there's not enough headers in the pruning proof but it satisfies validation

relations.get_parents on GD gets extra parents that aren't in the
current GD store. so get_blue_work throws an error

next, ORIGIN was mising from the GD so add that

…nt_proof

The new prefixes added are compatible with the old version. We don't want to trigger a db delete with this change

It's already on there

This prevents the case where new root is an anticone of old root

- Keep using old root to minimize proof size. Old root is calculated
  using the temporary gd stores
- fix the off-by-one in block_at_depth and chain_up_to_depth
- revert the temp fix to sync with the off-by-one

This reverts commit bc56e65.

This experimental commit requires a bit more thinking to apply, and
optimization can be deferred.

Recreates the GD stores for the current consensus by checking existing proof

… the root

As opposed to applying only to level 0

Add back the panic if we couldn't find the required block and our headers are done

Add explanation in comment for why trying anyway if finished_headers is acceptable

explain logic for the two root calculation

When building pruning point proof ghostdag data, ignore blocks before root

…t#573)

* bump tonic, prost versions
update middlewares

* use unbounded channel

* change log level to trace

* use bounded channel

* reuse counts bytes body to measure bytes body

* remove unneeded clone

* replace statrs and statest deps.

* remove todo in toml.cargo and fmt & lints.

* do a run of `cargo audit fix` for some miscellaneous reports.

* use maintained alt ks crate.

* add cargo.lock.

* update

* use new command

* newline

* refresh cargo lock with a few more version updates

* fix minor readme glitches

---------

Co-authored-by: Michael Sutton <[email protected]>

* sighash reused trait

* benches are implemented

* use cache per iteration per function

* fix par versions

* fix benches

* use upgreadable read

* use concurrent cache

* use hashcache

* dont apply cache

* rollback rwlock and indexmap.

* remove scc

* apply par iter to `check_scripts`

* refactor check_scripts fn, fix tests

* fix clippy

* add bench with custom threadpool

* style: fmt

* suppress warnings

* Merge branch 'master' into bcm-parallel-processing

* renames + map err

* reuse code

* bench: avoid exposing cache map + iter pools in powers of 2

* simplify check_sig_op_counts

* use thread pool also if a single input
1. to avoid confusion
2. since tokio blocking threads are not meant to be used for processing anyway

* remove todo

* clear cache instead of recreate

* use and_then (so map_err can be called in a single location)

* extend check scripts tests for better coverage of the par_iter case

---------

Co-authored-by: Michael Sutton <[email protected]>

* Parallelize MuHash calculations

MuHash calculations are additive and can be done in chunks then later combined

* Reimplement validate tx with muhash as a separate fn

* Use smallvec for muhash parallel

Co-authored-by: Michael Sutton <[email protected]>

* Add independent rayon order test

* Filter some data

* Use tuple_windows for test iter

---------

Co-authored-by: Michael Sutton <[email protected]>

…#581)

* semantic: add `from` ext methods

* muhash from txs benchmark

* optimization: in u3072 mul test if lhs is one

* extract `parallelism_in_power_steps`

* comment

- use BlueWorkType
- fix some comments

* rust 1.82 fixes

* sig op count std check

Co-authored-by: Michael Sutton <[email protected]>

Co-authored-by: Michael Sutton <[email protected]>

Co-authored-by: Michael Sutton <[email protected]>

Co-authored-by: Michael Sutton <[email protected]>

Co-authored-by: Michael Sutton <[email protected]>

Co-authored-by: Michael Sutton <[email protected]>