@stephancill

hacking on ethconfig and private data some more today a need is emerging to differentiate between a URL being the value and a URL that resolves to the actual value i propose the following: prefix values that need to be fetched from a url with "resolve:" e.g. `resolve:https://values.steer.fun/user/0xd64c1c77739ce4cace1b95582b10a0b76d12c4c5/secret-url`. a client would then make a request to GET the url after the `resolve:` segment which should respond with the actual value here's a demo of resolving 3 values from an ENS name using this convention - a plain url - a public url from a pointer - a private url from a pointer (required auth not present)

4 replies

1 recast

8 reactions