We would not have been able to build a matching algorithm that later can be generelazed to address all possible perspectives accorss all possible value sets without using HGTP as a data validation layer. Adding HGTP message signing to Metamask via a Snap made it possible.
If the vision of a truly generalized matching engine is realized, we don't need money anymore. THIS is a public good. And after studying HGTP and IEML for quite a while now, I'm pretty sure there exists econoies that are more efficient and humane than money. A job market is just the first use case. HGTP: Hypergraph Transfer Protocol: https://docs.google.com/document/d/1QAQJxoxYjxNW0i3dyPzWqqReI-J7ANePUygQNR_Qfh4/edit IEML: Information Economy MetaLanguage: https://intlekt.io/ieml
Over time, more and more projects will be realized on this platform, basically producing a track record of the internet. And further, when crypto protcols are specified in IEML, we literally have a map of crypto projects. Because protcol designers are force to *really know what they are talking about*, otherwise you can't specifiy it in IEML (Information Economy MetaLanguage).
Adding HGTP to Metamask increases the reach of both ecosystems.
It's a job market.
The Hypergraph Transfer Protocol is the next evolution of messaging systems. Since it can model **any** data type, all forms of identity can be defined with it. We built a Metamask Snap that can derive DAG-addresses from MetaMask key material.
Once our solution is built out into a generalized job market, many people will find opportunities they never even know existed.
One IEML (Information Economy MetaLanguage) is used to specify projects, impact can be formally derived from it. That's because IEML is a closed transformation group that based on just five semantic primitives can address all meaning there is. And all qualities can be defined with it, and put in relation with any given project specification on the platform. In our opinion those qualities should be user defined and the protcol should not have any further oppinion on this.
The core problem we are approaching is multidimensional matching. As a first use case, we've built Crowdwork, a platform for founders, builders, and inestors to find each other.
There are two aspects our protocol design is unique:
Proximity proofs of matches allow for a permissionless matching market, where anyone can search and submit matches. This makes such matching computationally practical.
Automated quality-control of matches, so users know their matches are actually the best ones available.
First, founders put their projects out there.
Next, founders get matched with builders, depending on the projects requirements and skills of available builders.
After a team is formed, the project is matched with investors.
Each of the three roles in Crowdwork, the founder, builder, and investor, has a different perspective on the matching process.
Founders specify what they do and what need to do it.
Builders specify what they are good with and what they want to work with.
Investors specify their topics of interest.
By collecting information in this structured way, the platform is able to produce high-quality matches.
And by modelling structured data in IEML (Information Economy MetaLanguage), this mechanism can be generalized into a solution for arbitrary matching problems, and further, social coordination as a whole.
To validate message-exchange in the protocol, we use HGTP (Hypergraph Transfer Protocol) as a flexible base layer of data. For this, we integrate with Metamask to sign data using Metamask key material from within a MM-Snap.
This generalization will lead to a new job market, and ultimately to an economy without money. Because semantically interoperable information (via IEML) and verifiable structured conversations around it (HGTP) enable coordination schemes way more wholesome than money allows for.