Cannot broadcast transaction in KSM network

[theo-learner]

Hi. When broadcasting transactions on the Kusama network(9030), it sometimes stops though node is running well.

short code:

async signRawTransaction(txParams: any): Promise<any> {
  this.logger.debug("Raw Transaction:", txParams.transfer.toString());

  const signedTx = await txParams.transfer.signAsync(this.wallet[txParams.from])

  await txParams.transfer.send();
  this.logger.debug('Signed Transaction:', signedTx.toString())

  return signedTx

}

In the short code, when it stops broadcasting transaction, the debug log message is not printed from "Signed Transaction: ~~".
I found the release v4.12.1 (https://github.com/polkadot-js/api/releases) it is included changes "Added 9030 upgrade blocks for Kusama & Westend"

Will this error disappear if I upgrade polkadot-js to v4.12.1? Please let me know if you find the reason other than using the latest polkadot-js SDK.

[jacogr]

If it is today, check the tx pool. A number of nodes, based on the number of txs flowing, have been loaded and got to points where they stopped accepting txs.

[theo-learner]

Thanks. There are several questions.

1. When did the tx stop sending occur?
2. How do I check the tx pool status?
3. Will this error disappear if I query the nonce using rpc.system.accountNextIndex? (https://polkadot.js.org/docs/api/cookbook/tx/#how-do-i-take-the-pending-tx-pool-into-account-in-my-nonce)

[theo-learner]

++(add) When broadcasting tx, we found that an RPC(curl) error occurred while connecting SDK and KSM nodes.
errno: 52, data: Empty reply from server

[jacogr]

No, there has been multiple reports where RPC servers just stopped accepting any new transactions. You can always monitor the queues on telemetry. As of this morning, it actually seems like the spam has stopped.

[Swader]

This was due to the RMRK.app NFT emote contest. It is over now and shouldn't happen again any time soon, plus this should fix it: paritytech/substrate#8963

[theo-learner]

Thanks. I can check best block, finalized block, avg time, block time, and status of validators on the telemetry in real time (https://telemetry.polkadot.io/#list/Kusama)

@jacogr

1. Is there any way to monitor tx pool status?

@Swader

1. When did RMRK.app NFT emote contest start and when did it finish?
2. Transaction pool: Ensure that we prune transactions properly paritytech/substrate#8963 will be merged next polkadot-js release. it it right?

[jacogr]

The PR will be in the 0.9.4 release (as planned), it has no API dependencies, it is client only.

[Swader]

When did RMRK.app NFT emote contest start and when did it finish?

@boohyung it lasted throughout April and May, but it ramped up in the last few days of May due to people discovering scripting. It's calm now.

[theo-learner]

Thanks. @jacogr @Swader I look forward to applying it to the next release(polkadot v0.9.4) to improve the stability of txpool.

[polkadot-js-bot]

This issue has been open for 21 days with no activity and is not labelled as an enhancement. It will be closed in 7 days.

[polkadot-js-bot]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.