WebSocket on Mainnet not listening to Events emitted

[jingxuan98]

Describe the bug

Baiscally I'm not able to listen and subscribe to mainnet Events Logs, but it works fine on testnet

It was working like 1 week ago when i started my node but now its not working

To Reproduce
Steps to reproduce the behavior:

1. The script i use to test can be found at https://github.com/jingxuan98/cronos-mainnet-eventIssue
2. Clone the repo and go get the packages and run go run main.go
3. Deploy a ERC20 Token at Testnet and Mainnet and Test accordingly (RMB to change the token addresses adn WSS address)

Expected behavior

1. Able to Listen to the Events on Testnet when a "transfer()" function is invoke follow by an "Transfer" event emitted, but not on Mainnet

Screenshots
Listening on Testnet

But for Mainnet its not listening

Macbook Pro M2
Golang 1.19

[JayT106]

Hi @jingxuan98 , it might relate to this tendermint issue tendermint/tendermint#6729, we will check our mainnet node settings to ensure the value is setup properly.

[jingxuan98]

Ok thanks for the reply @JayT106 , btw just some add-ons that we face this issue with emitting even just a few events instead of 100 like the OP of tendermint/tendermint#6729. Hope the issue can be solved soon, thanks!

[mmsqe]

@jingxuan98 I find it hard to reproduce the issue, I tried one case might no response at all is pass outer contract address instead of inner address, may I ask the contract address you subscribe with?

[jingxuan98]

@mmsqe basically in the test above I just deploy a simple ERC20 on mainnet using remix and listen to the transfer event and transfer the tokens among accounts to test that, the token contract address i use is 0x926f2e39eab3c828215d7bd807659af5672a11a6

[mmsqe]

@mmsqe basically in the test above I just deploy a simple ERC20 on mainnet using remix and listen to the transfer event and transfer the tokens among accounts to test that, the token contract address i use is 0x926f2e39eab3c828215d7bd807659af5672a11a6

Subscription might get cancell for slower client like ci fail when set smaller iterations, while current long-poll enhancement process more and much faster.

[jingxuan98]

I'm still facing this issue, any workarounds? @mmsqe @JayT106

[mmsqe]

fixed by #1239