GUTS logo



GUTS is a ticketing platform that facilitates fair-use and a good user-experience.

IMPORTANT: By investing in this business you agree to our Disclaimer. All information including our rating, is provided merely for informational purposes. CryptoTotem does not provide investment advice.


Project industryEvents & Entertainment

Technical details

Ethereum ERC20 standard token.

What is GUTS

The Guaranteed Entrance Token (GET)-protocol, initiated by GUTS Tickets, is a smart ticketing protocol that will facilitate the sale of tickets by issuing smart tickets to wallet addresses on the blockchain.


Public sales: Nov 13, 2017 - Dec 12, 2017
Soft cap: 2,725,040USD (fiat)
Raised: 7,520,874 USD

Token info

Ticker: GET
Token price in USD: 1 GET = 0.1 USD
Accepted currencies: ETH
Token distribution:
Token allocation: Get-protocol development - 55% Operational costs - 17% External contractors - 13% Marketing and sales - 12% Contingency - 3%

GUTS Roadmap

Phase 0 - Token Mutiny

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.

Project team

Maarten Bloemers
Maarten Bloemers
CEO & Legal
Maarten Bloemers linkedin
Tom Roetgering
Tom Roetgering
CCO & Sales
Tom Roetgering linkedin
Ivo van der Wijk
Ivo van der Wijk
CTO & Lead Developer
Ivo van der Wijk linkedin
Frans Twisk
Frans Twisk
Product Designer & Front-end Developer
Frans Twisk linkedin
Izel Nakri
Izel Nakri
Front-end Developer
Izel Nakri linkedin
Stavros Champilomatis
Stavros Champilomatis
Back-end Developer
Stavros Champilomatis linkedin
Mark Arts
Mark Arts
Back-end Developer
Kasper Keunen
Kasper Keunen
Blockchain Developer
Kasper Keunen linkedin

Social media

GUTS web-siteGUTS RedditGUTS MediumGUTS TelegramGUTS BTCTalkGUTS TwitterGUTS FacebookGUTS SlackGUTS Github

User rating:

5/5 ( 1 )

GUTS rating

Claim admin rights for this project
ICObench3.4 / 5GUTS (GET) icobench
ICOholder3.7 / 5GUTS (GET) icoholder
ICObench7.9 / 10GUTS (GET) icomarks

How To get a verified Project status

To pass the verification you need to place a our logo on the main page of your website and make an announcement of the listing in your social network accounts. Send us the email in reply with confirmation of the link placement.

Height: 50 px
Width: 160 px

Leave a Reply

Your email address will not be published. Required fields are marked *