I’d like to get your thoughts on something rather pedantic and semantic.
I’d like to explore what it might look like if we view “Polywrap” and “The WRAP Protocol” as two correlated concepts. Let me explain
Polywrap aims to enable the quick integration of SDKs into all types of applications. It does this through the WRAP protocol. Polywrap is a collection of tools that aid developers in leveraging the WRAP protocol.
WRAP stands for:
W - WebAssembly
R - Random
A - Access
P - Protocol
This acronym highlights the primary innovation that Polywrap technology leverages. The fact that at run-time you can random access WebAssembly modules using WRAP URIs.
These warppers can be persisted anywhere on the decentralized web, including the WRAP network which specializes in this functionality.
Additionally the WRAP network can help with other necessary features for a healthy ecosystem of wrappers:
- named & versioned registry
- version validation
- source code verification
- persistence & availability
That is the WRAP protocol.
I believe that making this distinction between product and standard through more refined semantic terminology will help us in the long run. It can help builders better understand the layers in our stack, as well as help them leverage different parts of our technology.