GUTS is a ticketing system which uses blockchain technology to register ownership of SMART-tickets. GUTS makes ticket fraud impossible. The ticket can only be resold at a fixed price, so no more disgraceful prices for (secondary) tickets.
The current state of the GET-protocol as used and implemented by GUTS tickets in the Dutch market. With a marketed and ticketing application which uses blockchain to register ownership and properties of smart tickets.
Phase 1 - The Token Intifada
The second phase of development the GET becomes the only possible method of payment for the transactional and processing fees in the ticketing cycle. Furthermore this phase will introduce the GET-protocol API that can be used by white listed third party ticketing companies worldwide. Every actor in the protocol will have a smart wallet added to their uniquely verified identity, the actors within the protocol will not have full control over the private key.1 This phase would fully introduce the possibility
for actors(especially consumers)to use GET to pay for drink and beverages tokens and other products before and during an event.
Phase 2 - The Boston Token Party
In the third phase of development of the GET-protocol the fully accessible smart-wallet would be added to the users account on the GET-protocol, allowing users to interact with their tokens. End users and event organizers can choose to hold and use GET as a method to store the value of event tickets. As multiple stakeholders in the event ecosystem would hold and use the token, this would add liquidity to the ecosystem. GET acquired on the open market
Phase 3 - Ticket Liberation
The third and final phase of development the full range of functionalities and accessibility will be given to all the actors within the protocol. All aspects of the protocol will be completely on-chain and the economics of the ecosystem as a whole will be self-sustaining. In this phase, GET is the sole store and transfer of value used for storing all event related value. All organizers can create events on the GET-protocol via the public and open sourced API.