You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the wallent endpoint submits sponsored transaction into the pool that are then broadcasted to the sequencer over p2p.
p2p broadcasting can potentially be flaky, and due to the p2p rules, some txs may never make it to the sequencer, this can happen if a message is dropped internally when channel bounds are enforced for example.
what we can do is periodically rebroadcast these txs to the peers.
this can be done with a helper service that has access to the pool + TransactionHandle and on an interval basis fetches the pooled txs for a given address and then force gossips them:
the wallent endpoint submits sponsored transaction into the pool that are then broadcasted to the sequencer over p2p.
p2p broadcasting can potentially be flaky, and due to the p2p rules, some txs may never make it to the sequencer, this can happen if a message is dropped internally when channel bounds are enforced for example.
what we can do is periodically rebroadcast these txs to the peers.
this can be done with a helper service that has access to the pool +
TransactionHandle
and on an interval basis fetches the pooled txs for a given address and then force gossips them:https://github.com/paradigmxyz/reth/blob/3b8c661ad4e7e7a5b1656d5bebe8073755903b75/crates/net/network/src/transactions/mod.rs#L143-L143
The text was updated successfully, but these errors were encountered: