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

Import Cardano transactions by sequences of block ranges #1766

Closed
3 tasks done
jpraynaud opened this issue Jun 18, 2024 · 0 comments · Fixed by #1769
Closed
3 tasks done

Import Cardano transactions by sequences of block ranges #1766

jpraynaud opened this issue Jun 18, 2024 · 0 comments · Fixed by #1769
Assignees
Labels
feature 🚀 New implemented feature

Comments

@jpraynaud
Copy link
Member

jpraynaud commented Jun 18, 2024

Why

We need to keep a footprint as low as possible on the machine running a Mithril signer. We have noticed that the current process to import the Cardano transactions does not allow an efficient pruning strategy on the signer: the block range roots are computed only once all the transactions are imported. The import mechanism should be able to compute block range roots along the way in order to allow early pruning and overall low disk space requirements.

What

Compute block range roots as soon as they can be computed by the signer and allow for early pruning on the transaction store.

How

  • During warmup phase on the signer, run the import of transactions with the Transaction importer on a sequence of ranges of block numbers (e.g. every 10 block range root length or 150 blocks)
  • Implement a decorator on the Transaction importer to import by sequence of block ranges
  • Assess the required disk space for a signer node (~100MB with 90M transactions)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature 🚀 New implemented feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants