You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, Ropsten sometimes undergoes huge re-orgs, specifically between 2020-08-26 9:54:22 PDT and 2020-08-25 16:23:30 PDT it re-orged 16k blocks. When this happens the following things happen:
Infura websocket interface stops working;
The bridge has to backtrack significant numbers of blocks;
If reorgs extends past initialization of NearOnEthClient then this contract gets deleted
Solution
To address this problem we need to do the following;
Indicate clearly in the documentation that it is not advised to use websockets for Ethereum node URLs;
Examine our code base and make sure we are not using websocket-specific features, like subscriptions to events;
_threshold` configurable parameters that can be passed through a command line;
Compute the amount of NEAR tokens we need to stake for EthOnNearClient to be able to handle finalized_gc_threshold=50k. Make sure we initialize EthOnNearClient with at least this number of tokens using near-client-init-balance parameter
Make finalized_gc_threshold and `hashes_gc
Add a parameter to init-near-contracts command that allows to initialize the client using the block from far in the past, because the current block might be easily revertable;link
The text was updated successfully, but these errors were encountered:
Add a parameter to init-near-contracts command that allows to initialize the client using the block from far in the past, because the current block might be easily revertable;
If the current block is reverted, then client code is erased, so this doesn't solve the problem of block begin reverted.
Background
Unfortunately, Ropsten sometimes undergoes huge re-orgs, specifically between 2020-08-26 9:54:22 PDT and 2020-08-25 16:23:30 PDT it re-orged 16k blocks. When this happens the following things happen:
Solution
To address this problem we need to do the following;
_threshold` configurable parameters that can be passed through a command line;
finalized_gc_threshold
andhashes_gc_threshold
should be set to 50k each;finalized_gc_threshold=50k
. Make sure we initialize EthOnNearClient with at least this number of tokens usingnear-client-init-balance
parameterfinalized_gc_threshold
and `hashes_gcAdd a parameter tolinkinit-near-contracts
command that allows to initialize the client using the block from far in the past, because the current block might be easily revertable;The text was updated successfully, but these errors were encountered: