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.
#
ProtocolPolywrap URIs use the wrap
protocol. Including wrap://
in your URI is optional in practice.
#
AuthorityFor example:
ens/
for resolving ENS domainsipfs/
for resolving IPFS contentfs/
for resolving content on the local filesystem
#
PathFor example:
api.domain.eth
for an ENS domainQmaLbZnnnHbcRRo3wNBQ2MhugmBGL9R2YYeBvj6Nk2QumP
for an IPFS file/directory./build
for a local directory
tip
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.