Marek
Marek
## Motivation Zebra currently estimates that it is close to the tip if the average number of synced blocks in the last four batches drops below 20. The decision is...
## Motivation In order to implement #4824, the non-finalized state needs to store history trees by their height, so that it can send the history tree corresponding to the root...
## Motivation When the checkpointer commits a block, the finalized state fetches the history tree and note commitment trees from the database, recomputes the trees, and stores them back in...
## Motivation When Zebra commits a finalized block, it re-calculates all the note commitment and history trees. This uses a lot of extra CPU. Zebra also fetches these structures from...
Storing only the first tree state in each identical series of tree states saves memory, and makes `Chain` cloning cheaper. ### Possible Implementation We can access the deduped trees using:...
## Motivation When a user attempts to run multiple simultaneous instances of Zebra without specifying a different database path for each, all instances except the first one panic because they...
## Description I noticed four issues when running the tests for the `main` branch locally on my machine: - the test `zebra_rpc_conflict` often fails with: ``` conflicted node2 was still...
This PR closes #170. I couldn't figure out why the CRT implies that a group with composite order has proper subgroups. I'd be glad if anyone could give me a...
## Motivation We recently updated `inferno`, which depends on `num_format`, which depends on `arrayvec` and `itoa`, and running ```bash cargo deny --all-features check bans ``` started producing the following warnings:...
feat(test): Check that the state service handles errors correctly when committing finalized blocks
## Motivation We recently refactored the process of committing blocks to the finalized state. This PR tests if Zebra handles errors correctly. ## Solution In this PR, we trigger a...