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

Improve block transaction download by using a better algorithm #6

Open
andreabadesso opened this issue May 24, 2021 · 1 comment
Open

Comments

@andreabadesso
Copy link
Collaborator

That's impossible by design. Blocks must have their parent block as first element in the parent list.

Hum, I'm still a little concerned because the DAG can get really deep sometimes. Maybe add a protection that will fail and report a problem or move to a DFS implementation using a stack (instead of a recursion).

Originally posted by @msbrogli in #1 (comment)

@andreabadesso
Copy link
Collaborator Author

Another potential solution for this issue is to use an API that returns all transactions that were confirmed by a given block

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

1 participant