Reduce quantity of data queries to Ethereum/NEAR nodes. about rainbow-bridge-client HOT 4 CLOSED

I like the idea about doing one transfer, then estimating the amount of time until the next expected change and repeat.

This will work fine for multi-hour transaction, and for fast transactions.

For transactions that depends on the event relayer finalizing them, we can do the same, since relayer is running in a loop, and it should be picking new tx as they appear. However it is possible for several reasons that relayer fails. To avoid oversaturating our endpoints we can exponentially increase the time we wait between calls up to a reasonable, but large amount. Start with 1 second and increase up to 10 minutes?

from rainbow-bridge-client.

I'm also towards 1.b solution! I know that the amount is crazy as I was able to reach those limits quite easily in Alchemy, for example, during some hard testing of the bridge.

I also like the idea that @mfornet mentioned, this is a quite popular solution to reduce the number of redundant calls. I.e. we estimate that TX will take up to 10 minutes to complete, then we multiply that time by some factor (e.g. 1.5 * 10 minutes = 15 minutes) and during this time we expect to have the constant time of checking, e.g. 30 seconds. When this time ends up but the TX is not yet finalized, we increase the interval twice. And then this interval increases up to some limit, e.g. 10 minutes.

from rainbow-bridge-client.

Currently during checkSync (called every 5 secs) of Ethereum -> Aurora transfers, findEthProof is called to check whether a transfer was finalized by the event relayer. So a proof is built every 5 secs and building a proof requires querying all the transaction receipts in a block individually:

from rainbow-bridge-client.

This is less of an issue on bridgetonear.org because checkSync will stop running if the event relayer didn't finalize within 10 blocks and fallback to the user's NEAR wallet to finalize the transfer. But on aurora.dev checkSync will loop forever until the transfer is finalized by the event relayer.

from rainbow-bridge-client.