October 21 update - All systems are go

This month brought several big milestones for GET Protocol, some publicly shared, some saved for this blessed occasion. As is tradition there is no shortage of ground to cover, so in order to keep things somewhat easy to navigate we'll link out to external blogs for in-depth coverage on the bigger topics.

Another Amsterdam Dance Event is in the books, with tens of thousands of partygoers and industry insiders letting loose. As was the case before the pandemic, GET Protocol-integrator GUTS Tickets facilitated on-chain ticketing for thousands of attendees at Audio Obscura's rave-ly reviewed parties.

This wasn't just rave, sleep, repeat. The ADE events also gave an amazing opportunity to battle-test the dynamic pricing feature on the secondary market. Giving ticket holders the possibility to determine the price for which their tickets are put up for sale. Not only does this provide added agency to the individual ticket holder, but this also marks an entirely new business model for white-labels of GET Protocol.

To say that secondary market revenue is a coveted asset would be a laughable understatement. Allowing organisations to tap into this revenue stream that previously flowed out to secondary platforms is a huge deal - and could become a serious component of future business models.

Stadium fever anyone?

Stadium fever anyone? Other familiar names popped up on the radar with the announcement from Dutch rock band Di-Rect that they'll be doing another massive stadium show in 2022 - also ticketed by GUTS and thus using tickets that are fully fuelled by GET.

Similarly, popular duo Suzan & Freek are hitting up the massive Ziggo Dome for their album release. You guessed it, ticketed by GUTS, using GET.

Rotterdam Ahoy, one of the venues for the newly announced GUTS events.

The Seven Digits Club

These and all sorts of other tickets flew off the digital shelves, prompting a huge milestone in GET Protocol's history, as the NFT Ticket Explorer showed that now more than a million on-chain tickets have been issued.

It's been a road to seeing seven digits on the counter, but the recent rise in ticket volume and continuous interest from potential integrators bodes well for the speed of the next million. Read about the milestone in this press release on CoinTelegraph.

Flooding the OpenSea

Oh - by the way, have you seen GET Protocol's updated OpenSea collection? It's already boasting hundreds of thousands of NFTs from recently ticketed events. Quite a sight to behold already, with many more tickets on the way.

GET's on-chain tokenomics are now live!

Staying within the theme of maturity and milestones, we have been happy to report that usage of the protocol's utility token GET is now fully running on-chain. This means that GET used by all organisations that issue tickets using GET Protocol is now flowing through the protocol, as it was designed. From ticket issuer, all the way to the DAO address without any centralised interference - just the way we like it.

To help those interested in closely following along the stats, we have released a subgraph implementation for reading aggregated historical data useful for building charting and analytics applications, as well as a websocket server for receiving real-time information on all usage within the protocol - a great foundation for building bots and data feeds.

Check out the full blog on the on-chain tokenomics launch here.

With the fully live 'DAO' tokenomics in place, we have also come to make an old tradition obsolete: the burn report. We are putting the final calculations together, but due to the manual nature of this task (last time!) and busy days we will publish this, along with some relevant context next week.

With that said, we hope you've still got some appetite left, because we are happy to present another milestone that's been long in the works.

Say hello to our latest team addition: Data Analist Gijs!

A brief introduction from the man himself:

Hi all, my name is Gijs. I live in the Netherlands in a village near Utrecht with my girlfriend and two kids.

My role within GET Protocol as a data analist is to get more insight from the gathered data in a structured way. I have a data science background which mostly focussed on marketing actionables. I’m looking forward to creating an environment/framework where data analytics and machine learning can lead to growing our business and increasing the user experience. 

In my spare time I like to learn new things and I have wide range of interests and hobbies. So I will give you a short impression: I like to improve my guitar skills, record it and play with a looping paddel. Once a week, you can find me in the gym or on a racing bike to keep in shape (it’s more a necessity than anything else…).

After working for many years in the financial industry, I became more and more convinced of the possibilities of blockchain. I met some people from the GET Protocol team a long time ago, and kept following their progressions. I’m really impressed by the progress made by the team, so I am very pleased to be a part of it now!

Announcing the NFT claim function release

We’re delighted to be releasing the highly anticipated GET Protocol collectible functionality over the next week or two, which will open up new opportunities for fostering connections, telling stories and building new revenue models.

Collectibles can be claimed through the white-label application by entering an Ethereum wallet address into the “Claim your tickets as NFTs” section of the app. If an address has been added by the ticket owner prior to an event, the collectible (and any unclaimed past event collectibles) will be automatically sent to the Ethereum address provided when a ticket is checked in.

Like all new features, we'll be closely monitoring how user's interact with the claiming functionality and finding ways to increase the ease of onboarding.

Collectible possibilities unlocked

So now that the claim functionality is on the horizon, what does this mean for GET Protocol's collectibles and what can we expect from the functionality? Well it just so happens that we've prepared another blog exactly on this topic! If you're curious about what a collectible represents in the event lifecycle and what becomes unlocked then read about the 'ember of ticketing' below.

Check out the 'Ember of ticketing, GET Protocol collectibles' blog now.

Following the launch of our NFT claim functionality, we are happily extending an open invitation to all NFT related events to use GET Protocol's NFT ticketing platform, free of charge. It's time for everyone to walk the walk, and we'd gladly be a crutch.

We feel strongly about advancing the use case of mainstream NFT utility through ticketing, which is why we want to take any potential friction off the table. There should be no reason not to use NFT tickets, period. To be clear:

Any event related to NFT technology can reach out to us and make use of our tried-and-tested NFT-based ticketing system for free.

Check out the open invitation blog here for the full details (and some sensible conditions), and feel free to pass it on to any suitable candidates you may come across.

Save the date: Friday 28th January 2022

Here's a little parting gift to you - a new community meetup!

Yes that's right and it will be taking place on Friday 28th January 2022 here in Amsterdam. We'll of course be revealing more details closer to the date.. you won't want to miss it.

The GET Protocol Foundation

Since 2016 we have been building ticketing infrastructure powered by the latest technology to upgrade the experience for all in the ticketing chain.

Ticketing companies of all sizes use our infrastructure to get clearer insights, generate greater revenue and maximise the connection through their tickets.

Digital Twin

Get involved in NFT ticketing easily and without any risk!

Learn About Digital Twin


Isn't it time for a modern ticketing solution?

Learn About White Label

A parting note

Keep up to date with GET Protocol on social media via our Twitter.

© 2021 GET Protocol Foundation


White-LabelDigital TwinDeveloper HubCommunity FAQ