Closed lukeskinner closed 4 years ago
One unfortunate side effect of this will be that the mainnet backend sync will not successfully start again if it's restarted for any reason (server reboot etc or process crash). Having the latest smart contracts is required during startup to avoid runtime issues.
I think this might just be Infura tricking me with their rate limiting... holding off on this for now but leaving it open just in case.
The issue I had on my local copy was the README on this repo had the old hub smart contract address (mainnet server had the correct one already).
Closing as I'm pretty confident Infura was tricking me with their limits.
Get Latest Contracts fails only on the mainnet. It appears decoding the data in the event returns null, unsure as to the exact cause at the moment.
I saw this in my local mainnet copy of othub on 05/09/2020 and it started to happen on the real mainnet sometime after that too. No immediate knock on impact as long as smart contracts aren't changing for mainnet in the next week (need to confirm this).
Possible causes: