Shift - Right now, you're already on the decentralized web
Shift is capable of serving dynamic content with performance that rivals or surpasses heavy servers. Shift also includes advanced capabilities for running an entire decentralized application ecosystem, not just the Phantom dApp, and Shift can deliver tokenized services with smart revenue models.
STO/ICO Status
Claim this listing and publish updates.
Basics
| Platform | N/A |
|---|---|
| Type | N/A |
| Accepting | Others |
| Circulating Supply | N/A |
| KYC | N/A |
| Restricted Areas | N/A |
| Homepage | Website URL |
| White Paper | View/Download |
About
Phantom
Shift’s first official dApp, called Phantom, is a user interface for file management over the IPFS network on Shift’s cluster. Data can be pinned — based on a smart revenue model — to be permanently stored on the cluster. Phantom also contains a wizard that enables decentralized web hosting and supports the management of real top level domains.
Sidechains
Phantom will soon have its own chain, as a sidechain tied to Shift’s main chain. The Phantom sidechain will have its own rules and transaction types, allowing endless possibilities. The prototype, which is a pre-beta, is already functional at Shift’s testnet. This very website is already powered by our storage nodes.
Smart revenue model
The cluster consists of a swarm of storage nodes (peers). Every token holder is able to join the cluster, and can provide disk space (storage capacity) to the Shift cluster. In 2018, Shift will present a smart revenue model which will make it economically beneficial to join the cluster.
Shift tokens can also be used for making a request to use a certain part of the available disk space that is provided by the cluster. Data can be published and pinned on the cluster. This means it will be stored permanently on the cluster — as long as the content publisher holds tokens as Proof-of-Storage.
Complimentary file transfers
It is also possible to send files (free of charge) outside the cluster, to all peers that are connected to the cluster but which are not part of it. However, these peers running an IPFS daemon will likely have a garbage collector that removes stored files occasionally, creating a cache.