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

bfgapi: add pagination to pop-txs-for-l2-block #193

Open
1 task done
joshuasing opened this issue Aug 2, 2024 · 0 comments
Open
1 task done

bfgapi: add pagination to pop-txs-for-l2-block #193

joshuasing opened this issue Aug 2, 2024 · 0 comments
Labels
area: bfg This is a change to BFG (Bitcoin Finality Governor) area: bss This is a change to BSS (Bitcoin Secure Sequencer) type: enhancement This improves existing functionality type: refactor This refactors existing functionality

Comments

@joshuasing
Copy link
Contributor

Confirmation

  • I have checked for similar issues.

Problem

The pop-txs-for-l2-block response becomes large when there is a lot of active PoP Miners broadcasting transactions.

Suggested solution

I think we should add pagination to the pop-txs-for-l2-block request/response, so that BSS can request the all of the transactions in several requests. This should make this a lot more table, while reducing the overall size of each response, preventing us from exceeding the read limit.

Additional Information

No response

@joshuasing joshuasing added type: refactor This refactors existing functionality type: enhancement This improves existing functionality area: bfg This is a change to BFG (Bitcoin Finality Governor) area: bss This is a change to BSS (Bitcoin Secure Sequencer) labels Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: bfg This is a change to BFG (Bitcoin Finality Governor) area: bss This is a change to BSS (Bitcoin Secure Sequencer) type: enhancement This improves existing functionality type: refactor This refactors existing functionality
Projects
None yet
Development

No branches or pull requests

1 participant