Link Search Menu Expand Document

How to find other participant’s ORGiD?

There are two ways to find other participants:

  • Using a User Interface
  • Using a GraphQL Node
  • Interacting with the ORGiD smartcontract

Using the Marketplace User Interface

Winding Tree hosts a user-friendly interface where it is possible to explore the various organizations participating in the Winding Tree marketplace.

You will need to have an Ethereum wallet such as Metamask.

Using a Graph Node

We provide a subgraph mapping compatible with The Graph project, allowing to query a simple GraphQL endpoint.

The hosted playground for this subgraph is available below:

Using this subgraph you can easily explore the content of the marketplace and retrieve the details from Ethereum and IPFS.

For detailed explanations, see the dedicated GraphQL section.

Implementing your own indexing/caching mechanism

Use Cases

Interacting directly with the ORGiD smartcontract and ecosystem allows to create a snapshot of all participants at a given time. Since it is ressource extensive, it is typically used to build a cache in the following cases:

  • I am an innovative Travel Agency and I want to keep track of all available hotels along with private data.
  • I am an airline and I want to associate my negotiated rates with the proper Corporate’s ORGiD identifier.

Using the ORGiD Smartcontract

Using the smartcontract, it is possible to gather all details of the organizations participating to the marketplace.

Before you start, make sure you are able to connect to an Ethereum node and have retrieve the contract ABI.

Building a cache

Using the organization details stored in the smartcontract, it is possible to retrieve the associated JSON document that contains all the details of the organization.

The process would be as follow:

  1. Retrieve all organizations from the ORGiD smartcontract using the getOrganizations method
  2. For each organization, use the getOrganization method to retrieve the JSON document URIs and the associated fingerprint hash
  3. For each organization, using the JSON document URI, retrieve the document, verify its compliance with the JSON Schema and verify the file signature against the fingerprint hash
  4. Do some extra validation on the trust proofs provided
  5. Store the data in a Database or other cache mechanism

Note: The steps 1-4 are implemented in the open-source ORGiD Resolver