In order to be found on the marketplace, a participant should register on the marketplace and create its own ORGiD.
There are two ways to register an ORGiD:
- Using a web browser, Winding Tree hosts a user-friendly interface:
- Interacting with the Smart Contract directly. This is relevant for travel businesses looking to register a large number of organizations (eg: Hotel Chains or Technology Providers).
A Travel Business that wishes to participate directly on the Winding Tree ecosystem is represented by a set of two components:
- An ORGiD Identifier: This is a unique 64-bytes hexadecmial string identifier, similar to a registration number provided by a country’s business registry. This identifier is normally created by the ORGiD smartcontract automatically, but it can be chosen if is not yet in used.
- An associated JSON document: This is a machine-readable file that contains all the details of the travel business. It is not stored on the blockchain for performance and costs reasons, but rather hosted by a traditional webserver.
The JSON document provides a structured representation of the travel business. It contains elements that can be found in a business registry, enriched with information that allows developers to interact with the business:
- Details of the legal entity, such as the legal name and address
- List of services exposed, such as availability and booking services and their format.
- Associated authentication public keys
- A set of assertions (or “proofs”) allowing another party to validate that the contract is indeed associated to the travel business entity.
The ORGiD contract mainly references the JSON document, but it also provides mechanisms to update it and verify its integrity. The ORGiD content is fully owned by the travel business, the ownership being provided by the Ethereum blockchain.
The above repository contains two examples of JSON document.
Make sure your file is valid as per the schema, otherwise other participants will not be able to discover or interact with your organization.
Once it is created, it can be stored in any place as long as it can be served over HTTP. Since it might be retrieved very often by other participants, it is important to store it in a place where the availability is ensure and that can handle a large amount of requests.
- Git repository
- CDN / Cloud Hosting provider
The smartcontract allows to provide three external links with your JSON file: one main location and two additional backup locations.
Having the document stored outside the Ethereum chain, there is a risk that a third party could alter its content without the owner knowing it. To protect the integrity of the document, and allow third parties to verify the document has been created by the owner of the organization, a hash of the document is stored in the ORGiD smartcontract.
The expected hashing mechanism is
Keccak256, this hash mechanism is widely used in Ethereum and standardized as SHA-3 by NIST. This hashing mechanism is built-in in the Ethereum ecosytem.
Now that you have all elements, you can publish the organization in the ORGiD smartcontract.
The registration is made by calling the
createOrganization() function from the ORGiD smart contract.