-
Notifications
You must be signed in to change notification settings - Fork 282
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
Flashbot bundle is not included because "isSendToMiners" is false? #123
Comments
Hi Thank you for your report. After the merge, the field |
Hi, thanks for your answer! I tested it again and this time I set the priority gas price to 500Gwei on Goerli to make sure builders will be likely to consider these bundles. I sent bundles in turn to target blocks from 8560814 to 8560816. As you can see, the first bundle was considered and sealed by some builders. According to https://collective.flashbots.net/t/flashbots-bundle-relay-api-upgrades/896, a bundle being sealed indicates a builder built a full block containing that bundle. Since it had been successfully sealed on block 8560814, why did it not be included? Is it the competition between the builders that causes the validators didn't select these blocks? If I further increase gas price, would that increase the probability of being included in the first block? Or because of the network problem, it is too late when builders received the bundle. In this case, reducing the network delay may solve the problem. Looking forward to your opinion. Thanks!
|
@Neronjust2017, hi, I am currently facing the same issue, i was wondering if you managed to solve it |
I'm trying to send a flashbot Bundle with several transactions. I use the following code to sign and send a bundle:
The simulation is successful. However, In order to ensure that the bundle can be included, I for loop 10 times to send a new bundle in case the previous bundle fails. It seems that the bundles are not included because they are not sent to the miners(isSentToMiners is false). Why does this happen?
The text was updated successfully, but these errors were encountered: