Closed HAOYUatHZ closed 1 week ago
For follower nodes, sometimes we have >500 txs for
case event := <-h.txsCh: h.BroadcastTransactions(event.Txs)
But for signer we only have a few.
We add more logs to investigate tx-broadcast issue.
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:
Has the version in params/version.go been updated?
params/version.go
Does this PR have the breaking-change label?
breaking-change
1. Purpose or design rationale of this PR
For follower nodes, sometimes we have >500 txs for
But for signer we only have a few.
We add more logs to investigate tx-broadcast issue.
2. PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:
3. Deployment tag versioning
Has the version in
params/version.go
been updated?4. Breaking change label
Does this PR have the
breaking-change
label?