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

Databases: Allow kaspad to run with an optional txindex database #2092

Open
D-Stacks opened this issue Jun 18, 2022 · 0 comments
Open

Databases: Allow kaspad to run with an optional txindex database #2092

D-Stacks opened this issue Jun 18, 2022 · 0 comments

Comments

@D-Stacks
Copy link
Contributor

D-Stacks commented Jun 18, 2022

Ideally this should run in a similar fashion to the utxoindex. It shoud store the txID as the key, and the accepting blockhash as the value. The accepting blockhash can be used to get blockdata assoiated with the txID from the consensus database. Storing the whole block will probably cause too much data bloat under heavy network usage, since each block will be stored multiple times for each tx in it.

This can be used to query tx data via rpc, calculate confirmations, and so on.

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