Jure Bogunovic

I don't think wrap.info should contain URI information. Instead we could add this info at resolution time in the client, so that the Wrapper class knows about it's URI

I think we could maybe replace the current method name, and args with Context This means it'd be preencoded. Also, when talking about wrapper URI and caller URI we need...

Branch with example test: nerfzael-ipfs-content-verification IPFS content hash verification does not work out of the box with ipfs-http-client, or with the js-ipfs SDK Any content verification that happens, happens inside...

I don't think this feature makes sense, since we are trying to phase out plugins from the client Even if it did, why not do `client.getPlugin()` then get the config...

Couple of questions: 1. What networks does this apply to? (mainnet, rinkeby, ropsten). I wanna say mainnet, but wanted more opinions on this 2. Does free persistence imply that we're...

Blocked by: - [ ] #1102

LGTM

> @nerfZael probably is something related to the constraints defined in wrappers.io regarding package validation? I think this is an issue with the express.js server settings on the persistence node...

So far it's been pretty convenient for users of @polywrap packages to bump all packages when they bump one. It's easier to know which package is compatible with which. I...

> @nerfZael do you think this can be closed now that #1169 is merged? No, handling the resolver extension errors will be a separate PR (similar to how resolver extension...