Skip to content
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

Validators should be able to determine if URI is preValidated #14

Open
satello opened this issue Jan 11, 2019 · 0 comments
Open

Validators should be able to determine if URI is preValidated #14

satello opened this issue Jan 11, 2019 · 0 comments

Comments

@satello
Copy link
Contributor

satello commented Jan 11, 2019

URI's from protocols such as IPFS guarantee file integrity (if fetched from a trusted gateway). Therefore Archon does not need to re-validate these file. At the moment the higher level functions (e.g. getEvidence) tell the utility functions whether or not the URI needs to be validated. validateFileFromURI should be able to handle this on it's own, so that ipfs links can be seamlessly fetched in the same workflow as classic links.

  • IPFS gateways are passed to the arbitrator and arbitrable classes so utils do not have access to them.
  • This would not solve the case where a URI is passed that already includes the gateway. The uri would have to follow the format /ipfs/... in order to be marked as prevalidated, since not all gateways are trusted by the user
  • Possibly add the ability to revalidate ipfs links? It is a bit tricky since ipfs by default does file transformations before hashing, so that would have to be replicated. And it can be opted out of in some cases so it would be difficult for Archon to know the format.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant