Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Per-block vs entire-chain accumulator? #42

Open
SilentCicero opened this issue Oct 26, 2023 · 1 comment
Open

Question: Per-block vs entire-chain accumulator? #42

SilentCicero opened this issue Oct 26, 2023 · 1 comment

Comments

@SilentCicero
Copy link

I'm still trying to understand the design here, but would it be that you have a single accumulator per block or would it be feasible to have a single accumulator for the entire chain?

Over the entire chain seems like better UX but less ideal as locating primes in that fashion feels very heavy.

Can the developers share any insights here?

@Davidson-Souza
Copy link
Collaborator

Hi @SilentCicero.

but would it be that you have a single accumulator per block or would it be feasible to have a single accumulator for the entire chain?

I'm not sure if I get this question. There's only one accumulator that represents the utxo set at a given height.

Over the entire chain seems like better UX but less ideal as locating primes in that fashion feels very heavy.

Could you please clarify what you mean here? Do you mean finding a node inside the forest? We keep an index of node hashes and node positions to help with that.

Davidson-Souza added a commit to Davidson-Souza/rustreexo that referenced this issue Jun 8, 2024
While we don't leave ibd, this code wouldn't shutdown if requested
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants