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

Own Transaction might not fit into the Transaction Pool #146

Open
SurfingNerd opened this issue Dec 10, 2024 · 1 comment
Open

Own Transaction might not fit into the Transaction Pool #146

SurfingNerd opened this issue Dec 10, 2024 · 1 comment
Assignees

Comments

@SurfingNerd
Copy link
Collaborator

On Adding transactions to the transaction pool, it can happen, that the pool is already filled with transactions.
this is especially harsh for own Service Transactions, because they can never get communicated in the network.

we could kick out other transactions from the pool, in order to fit in the service transactions in this case.

@cryptonit
Copy link

cryptonit commented Dec 10, 2024

is this maybe solved best as part of logic for random transaction shuffeling?

so first service transactions

then sender addresses based on random shuffeling

and based of random shuffeling all transactions that exceed blockgaslimit

are not includet in the block

@dforsten whats ur opinion?

@SurfingNerd SurfingNerd moved this to Todo in Diamond Beta Dec 12, 2024
@SurfingNerd SurfingNerd self-assigned this Dec 12, 2024
@SurfingNerd SurfingNerd moved this from Todo to In Progress in Diamond Beta Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

3 participants