-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Solve error logs on T2CR disputes #75
Comments
The two major errors I could find are indeed the following:
Thanks. |
I was able to find more details on this: On my point 2, load "Unsafe Scripts" is not necessary if you are not using the "IPFS Companion" browser plugin. Which means, that the website is breaking under the circumstances of an user using either their own Ethereum node and/or their own IPFS node. Both those things would be considered best practice from the user side. I strongly recommend you use a testing environment, not connected in any way to the development environment, where you use:
Ideally, the Kleros interface should work on IPFS, without any web server. Fixing those issues will get you closer to that goal. |
As for the other error logs: Court policies on ipfs are being loaded with the full url (as opposed to /ipfs/...), so we are trying to re-verify them and this fails. It does not effect the site from loading, but we can fix this by updating the URI format in the Policy Registry. The legacy rate exceeded message comes from using injected web3 from metamask (infura with no api key). It does not seem to effect the site loading, but it would be nice to figure out a way to not rely on injected web3. The issue with this is it would nullify the use of your own node or alternate provider. |
https://court.kleros.io/ does not work when using a personal full node (or I suppose any node at all, aside from Infura). Is Infura hardcoded somewhere? To confirm, I am indeed using a full node. If there's anything I can help troubleshoot, I'm happy to do so. I am currently not able to reproduce the "Load Unsafe Scripts" error, not sure if something got updated somewhere but I will report back if it happens again. |
I am having this issue as well when using a local node. When Metamask is configured to use Infura, it works fine. |
One person did not manage to see case 154 and 153 (token dispute in the t2cr).
Edit: He was running his own node, so this may be where the problem was from, switching to infura solved the issue/
He got some error logs.
When I tried, I also got the same error logs but the dispute was displayed correctly.
Chrome:
Firefox:
Brave:
The text was updated successfully, but these errors were encountered: