Closed goldsquid closed 3 weeks ago
It’s a non working example URL because I obfuscated the api key.
On Thu, 24 Oct 2024 at 19:20, Gavin Yu @.***> wrote:
Is https://flashy-practical-river.quiknode.pro/58dd38bb48734ea713fdd6e0a898d8c8747d3261/eth/v1/config/spec you expected?
— Reply to this email directly, view it on GitHub https://github.com/taikoxyz/simple-taiko-node/issues/342#issuecomment-2435139202, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDFLZD42UQDWTXYKX3WNRQLZ5DQZTAVCNFSM6AAAAABQQLOAWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZVGEZTSMRQGI . You are receiving this because you authored the thread.Message ID: @.***>
Yes, the format is like https://flashy-practical-river.quiknode.pro/xxx/eth/v1/config/spec
Yes and the log output from the docker container is missing the /
On Thu, 24 Oct 2024 at 19:49, Gavin Yu @.***> wrote:
Yes, the format is like https://flashy-practical-river.quiknode.pro/xxx/eth/v1/config/spec
— Reply to this email directly, view it on GitHub https://github.com/taikoxyz/simple-taiko-node/issues/342#issuecomment-2435206101, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDFLZD3264I3DXMBMCOEPEDZ5DUEBAVCNFSM6AAAAABQQLOAWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZVGIYDMMJQGE . You are receiving this because you authored the thread.Message ID: @.***>
Should have been fixed, could u give v1.8.1 a try?
Let's wait for a while
@goldsquid You can have a try now, thanks for your feedback!
I managed to pull container us-docker.pkg.dev/evmchain/images/taiko-client:sha-52a9362
and it contained the fix. thank you so much for your support.
On Thu, Oct 24, 2024 at 8:01 PM Gavin Yu @.***> wrote:
@goldsquid https://github.com/goldsquid You can have a try now, thanks for your feedback!
— Reply to this email directly, view it on GitHub https://github.com/taikoxyz/simple-taiko-node/issues/342#issuecomment-2435235304, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDFLZD2WZ3AGQLCDDZMVAKLZ5DVTJAVCNFSM6AAAAABQQLOAWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZVGIZTKMZQGQ . You are receiving this because you were mentioned.Message ID: @.***>
Describe the bug
Using Quicknode as Beacon REST API gives you a URL like
https://flashy-practical-river.quiknode.pro/58dd38bb48734ea713fdd6e0a898d8c8747d3261/
But using this will result in the client driver to try to connect to
https://flashy-practical-river.quiknode.pro/eth/v1/config/spec
which fails as UNAUTHORIZED
Steps to reproduce
use a free quicknode endpoint as rest api and start the client driver. check the logs.