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
When a transaction is submitted to the Mina node, it gets to the transaction pool of this node and is immediately broadcasted in Mina network. Transactions that are not included into a block, are re-sent by the rebroadcast loop on an 10-minute interval.
However rebroadcast loop stops picking up a transaction for rebroadcast approximately after 50 minutes from initial transaction submission. Only way to trigger this Mina node to re-submit transaction to the network is to restart this Mina node.
Pre-Berkeley there was also a possibility to submit the transaction another time using GraphQL API which would reset the rebroadcast mechanism's "timer". This stopped working in Berkeley which causes trouble for community members.
When a transaction is submitted to the Mina node, it gets to the transaction pool of this node and is immediately broadcasted in Mina network. Transactions that are not included into a block, are re-sent by the rebroadcast loop on an 10-minute interval.
However rebroadcast loop stops picking up a transaction for rebroadcast approximately after 50 minutes from initial transaction submission. Only way to trigger this Mina node to re-submit transaction to the network is to restart this Mina node.
Pre-Berkeley there was also a possibility to submit the transaction another time using GraphQL API which would reset the rebroadcast mechanism's "timer". This stopped working in Berkeley which causes trouble for community members.
Original discussion in Discord: https://discord.com/channels/484437221055922177/849711546023936050/1248005560138203258
The text was updated successfully, but these errors were encountered: