Last modified: Fri Aug 16 2019 11:27:04 GMT+0000 (Coordinated Universal Time)

How to choose Runtime Environment

The centerpoint of Winding Tree platform runtime environment is the Ethereum Smart contract called Winding Tree Entrypoint. It serves as a decentralized registry of Segment Directories of participating service providers (hotels, airlines, ...) and the tooling is configured to use it.

The tooling for an environment might consist of one or more REST APIs operated either as a service or on-premise - it typically depends on the necessary security measures. The ecosystem is intentionally open, so you can swap Winding Tree reference implementation and architecture with something completely different that suits your particular use case better. The APIs are not actively developed anymore and we encourage the community to take over.

Active environments

Winding Tree team is currently operating several environments.

Mainnet environment

Addresses of the Organization Factory and Segment Directories can be read from the Entrypoint contract.

Test environment - Ropsten network (codename Madrid)

Addresses of the Organization Factory and Segment Directories can be read from the Entrypoint contract. This will be the last version with an official support for the REST APIs.

Lisbon hackathon environment - ORG.ID (will be discontinued)

This was the first live, albeit test, release of ORG.ID powered platform used for 2019 Lisbon Hackathon. We intentionally did not upgrade it to let the hacks live for a certain period of time. It's documentation is on https://developers-lisbon.windingtree.now.sh.

Addresses of the Organization Factory and Segment Directories can be read from the Entrypoint contract.

Playground - A legacy Winding Tree hotel Index (will be discontinued in 2019)

This was the original environment used on 2018 Prague Hackathon that was using the idea of Winding Tree Index. That idea has since been superseded by ORG.ID.

How to run another environment?

If you, for some reason, need to run a fresh and separate environment, the key to do it is to deploy your own Entrypoint and Segment Directories and run all of the necessary tools with the appropriate configuration.

How to reset an existing environment

Since you are not able to delete any data on behalf of the users, the only way to reset an environment is to deploy a new Entrypoint and Segment Directories and reconfigure every other tool to point to the new location.

Where to next