Unauthorized Chain in Tier

Question

Unauthorized Chain in Tier

Closed this issue 2 years ago · 7 comments

Using chain id 1337 for localhost in hardhat config ... is it related ?

Answer 1 · 2022-06-23T04:34:23.000Z

Hey @pvdyck I am looking in to this. It might be due to some recent server changes.

Answer 2 · 2022-06-24T00:46:03.000Z

In the meantime, you can add a function to handle errors when initializing via the onerror parameter and just ignore that error as local networks do not use the WebSocket connection to our server.

Answer 3 · 2022-06-30T23:10:22.000Z

@pvdyck This was indeed a server issue and should now be fixed.

Answer 4 · 2022-07-01T16:46:25.000Z

@aaronbarnardsound thanks a lot

Answer 5 · 2022-07-04T16:55:40.000Z

hey @aaronbarnardsound
we are currently facing the same issue with BSC (chain id 56)
could check if it's also something wrong on your server?

Answer 6 · 2022-07-04T23:32:49.000Z

Hey @goums this error is introduced due a change on our backend infrastructure. BSC is no longer supported on our free tier and requires a production 2 plan due to the expensive nature of supporting BSC notifications.

Answer 7 · 2022-07-05T06:54:07.000Z

thanks for your reply @aaronbarnardsound
make sense given the high cost of BSC nodes