Tanmay

Related : https://github.com/zeta-chain/node/issues/3464

Consider initially adding a notification through an event or a simple logline before adding the invariant. Invariant, when broken, might lead to a chain halt. We can easily more the...

The changes recommned have already been implemented https://github.com/zeta-chain/zeta-node/blob/ab691b14cbe37a34f5dee66a3f690ad10e14d2e3/zetaclient/chains/bitcoin/client/client.go#L116-L137 We do not automatcially retry all calls if there is an hhtp error , releated to the PRC though . Monitoreing that...

Might be a good idea to add a GitHub code link to the function

It makes sense to have a supplemental goroutine to check for missed outbounds in the zetaclient. It should be easy enough to add and solve the problem to some extent...

@lumtis @CharlieMc0 , please consider this as soon as possible , It would be interesting to check the DB growth before and after this change

> Anyway we can add instruction how to run? Can be added in `docs/development` with a link in the readme c1db4cf4cedc9086d3e3c67a820aea587149f513 I added a simple doc will add more information...

> Can we tweak staking params? > > The staking hook issue was not ported on `develop`: #2968 > > I was curious if setting a unbonding time of 10...

The cointype is not correctly added for revert outbounds https://github.com/zeta-chain/zeta-node/blob/aa81140f78031087d89e0344896d00034fa13dbf/x/crosschain/types/cctx.go#L119-L128 implementing the mentioned changes should also fix this problem

Hi @lumtis Should we revisit this for the next release? We can consider breaking the pr down, into - Change in logic - Migration script And only add the former...