yihuang

> My application is basically a websocket subscription on monitoring every block, and I read particular tx data only. I ain't very sure it's because of the websocket subscription slowed...

Random ports might make more sense running tests in CI. But fixed ports do have the advantage of being predictable development, currently, some testing codes depend on that to know...

we have upgraded many nodes, it works fine. I need to understand more about the user's report to understand why. I guess it's due to misconfiguration on the user side....

replace cronosd binary and restart, just like 0.6 -> 0.7.

> Btw, do you have snapshots https://quicksync.io/networks/cronos.html there are plenty here.

> I have to use 0.6.* to sync to some block and then switch to v0.8? 0.6 -> 0.7 -> 0.8

> > > I have to use 0.6.* to sync to some block and then switch to v0.8? > > > > > > 0.6 -> 0.7 -> 0.8 >...

Totally agree, some of the points that are improved in v0.7.0: > O(N) log messages The burn/mint logs are removed in v0.7.0, and all the logs during contract execution are...

> One requirement / discussion to add is a timeout for the batch. Say if a batch has been unchanged for say n hours, the relayer should still submit the...

> I think what calvin mentioned by timeout is the maximum time transaction needs to "wait" before being send to ethereum even if they specify low value or zero fee...