Skip to main content

Understanding URIs

Deployed wrappers are identified using custom URIs (Uniform Resource Identifier). For example:


Polywrap URIs have 3 parts: a protocol, an authority, and a path.


Polywrap URIs use the wrap protocol. Including wrap:// in your URI is optional in practice.


For example:

  • ens/ for resolving ENS domains
  • ipfs/ for resolving IPFS content
  • fs/ for resolving content on the local filesystem


For example:

  • api.domain.eth for an ENS domain
  • QmaLbZnnnHbcRRo3wNBQ2MhugmBGL9R2YYeBvj6Nk2QumP for an IPFS file/directory
  • ./build for a local directory

ens/ and ipfs/ URI resolution is supported in all Polywrap clients by default. Adding custom URI resolvers is possible. More documentation on how to do this will be released soon.