Hey everyone! We are happy to announce that we published the details concerning our GET ICO! Straight out of our
blog post:
Details of the ICO Date: Mid/end of November
Duration of ICO: 14 days
Total amount of tokens : 90 million tokens minted
Min. cap: €2.3 million (lowered value)
Max. cap: €15.0 million (lowered value)
Public Crowdsale | 41% |As can the diagram shown above, 41% of the total tokens minted will be sold to contributors during the ICO period. Tokens that remain unsold after this period will be destroyed.
User growth fund | 30% |The user growth fund promote protocol usage by rewarding both event organizers and consumers for using the GET-protocol.
GET Stability Fund | 14% |
The GET stability fund will act as an stabilizing buffer for event organizers to acquire GET so they can use the GET for their events. The stability fund acts as a siphon and will buy back GET from the market. This means that there will always be approximately 14% of the total amount of issued tokens in this fund.
Team and advisers | 13% |Of the total amount attributed to GUTS Tickets team members 6% is distributed after the ICO, the remaining 7% is set aside for future team members. For each issuance there will always be a standard vesting period of minimally 12 months before the tokens become spendable.
Contingency | 2% |Amount of raised funds is set aside for unexpected expenses.
ICO price tiers
The amount of tokens sold per tier will be announced at a later date. The queuing and tiering contract infrastructure will both be dynamically managed by GUTS own smart ticketing system.
Mechanics of the crowd saleAs crowd sales in the past have been riddled with chaos and uncertainty. During the GET-protocol ICO we want to prevent this type of network cluttering and general chaos from occurring. Therefore GUTS Tickets has decided to self-built queuing application.
Dynamic ICO queuing applicationTo manage the contributions during the ICO a custom version of the ticket queuing module will be utilized. This queuing application, which will be a customized version of our own tested and operational smart ticketing application, will serve every contributor with a unique contribution instructions at a certain time. By using this application we are able to showcase our tech while at the same ensuring that scammers can’t copy or mirror our front-end in an attempt to lure contributors.
ICO contract publication & audit
The contracts used during the ICO will be made public in the weeks preceding the ICO this will be accompanied with a bug-bounty campaign. GUTS Tickets will only use audited and tested contracts.
Details on the GET presaleA portion of tokens sold to the public have been sold to strategic partners of GUTS Tickets. These pre-sale token contributors share long term goals with GUTS Tickets and in some cases will only receive these tokens if they have delivered on a certain ticketing volume.
At the moment of publication of this blog post the GUTS Tickets advisers and partnerships have not been announced to the public yet. Subscribe to our medium blog or join our Slack channel to keep up to date with the latest developments in our quest to revolutionize the ticketing industry.
The wallet address containing the funds raised during the strategic presale will be made public.
Buy-back guaranteeWe believe that the GET-protocol ICO contributors deserve a certain level of certainty for their investment in the development and roll-out of the GET-protocol. This certainty is provided by the buy-back mechanism, this mechanism enables token holders to sell their GET back to the event organizer when so that the tokens can be used in the protocol as a store of value for the event ticket value during the event cycle.
The GET-Protocol buy-back mechanism
The protocols token, the GET, has to be acquired by event organizers in order to use the protocols smart ticketing contracts that are able to transact with the consumers smart wallets. The event organizer(EO) is not able to directly acquire GET from the open market, the EO purchases the GET needed to ticket a certain event from the stability fund(SF). The price the EO will pay per GET to the SF is dependent on the market GET price average provided by the GET price Oracle (GPO). The SFs programming dictates that the price per GET will not be lower than €0.50 per GET (even if the GPO indicates that the GET price on exchanges is lower). As the EO will pay at least €0.50 per GET it buys from the stability fund, the SF will always offer the open market token holder with at least that same price.
If the average price on the exchanges listing GET is for example €2.50, the EO will have to pay the same amount in FIAT but will receive less GET in return from the SF. A higher GET price thus won't hurt the competitiveness of the ticketing protocol as the net costs (in FIAT) for the EO aren't effected by the price inflation of the token. This mechanism provides the EO with a stable protocol price while providing the token holder on the open market with a certain level of investment security.
GET price on the open market
It is important to note that the €0.50 price pegging is only internal and arbitrage between the internal GET and the open market is not possible. The GET price on the exchanges is allowed to valued in anyway the market sees fit.
Diagram displaying the fiat/GET/ETH flow during an event cycle. After the GET purchase of the EO the stability fund will buy the GET back from the market for the price provided by GPO. Source: GET-protocol
white paper.
The GET price oracle (GPO)The function of the GPO is to assess for the stability fund what a fair value
for the GET is at the moment a EO needs GET to run an event. The oracle makes this price evaluation on the basis of data input of a set of curated exchanges that list GET.
Making sense of the buy-back mechanismFrom an ICO investor point of view a case can be made that this guaranteed minimal buy-back price of €0.50 ”is too good to be true”. At face value this seems like a logical conclusion as the guarantee of the GET-protocol basically promises that there is little to no risk of monetary loss. Since the investor will always be able to recoup his initial investment with profits by means of a buy back mechanism of the stability fund. This mechanism will buy GET back for a price minimal price of €0.50 / GET.
This buy-back promise doesn’t seem to make any economic sense from the perspective of the protocol itself as the buy-back price is higher that the price the protocol received for a GET at the ICO. Thus creating a net-loss from the perspective of the protocol. From this assessment one could come to the conclusion that this buy-back promise of the protocol must be simply untrue or at least unsustainable in the long run. However, this conclusion would be false, as one would have failed to distinguish the difference between the GET-protocol and the actor using the protocol; the ticketing company. This company is using the GET-protocol to serve their customers (event organizers / venue owners etc.) The ticketing company only uses the GET-protocol as a back bone/infrastructure cost to add the convenient features of smart tickets to the service they provide. The margins of the ticketing company lie in offering this full-service package to its clients, not in speculating in crypto tokens. The ticketing company, at the moment that they acquire GET, has already landed a client and thus ensured event specific revenue. As such the company won’t lose money paying €0.50/GET price as minimum fee as this base fee is just a vehicle for company to acquire the margin they make on the service they are providing.
Allocation of the raised fundsAll of the funds raised during the ICO will be managed by the GET foundation. In future blogs further information will be published about the legal structuring of this foundation and how this entity will be managed and held accountable for the progress that is made in the realization of the road map targets.
More about the GET-protocol ICO
If you want know more about the GET Initial Coin Offering, read our
white paper, visit
ICO website, sign up for our
Slack or get yourself a smart event ticket in our
sandbox environment.
-the GUTS team