Find out more about the processing system that fuels ticketing operations through GET Protocol
Since GET Protocol’s inception in 2016, our ethos has been to keep complexity hidden from the end user experience. With every application and tool that we’ve built, we’ve poured many hours into ensuring we could adhere to this rule and create seamless experiences that feel natural to the end user.
After all, part of the appeal of emerging technology such as the blockchain, is the wealth of new possibilities it presents, yet one of the greatest barriers to adoption is complexity and the user experience. To provide the greatest impact to every single person these new tools should be used appropriately and fit into larger systems that put the end user first.
By extension of this ethos, we’ve kept simplicity in mind right down to the granular level of how costs are handled for ticketing operations through GET Protocol. To do that we’ve built a ticketing dashboard that allows both white-labellers and digital twin integrators to manage ticketing costs at the click of a button.
When you say top up, what exactly is being topped up?
To fuel ticket operations through GET Protocol, there’s an underlying cryptocurrency system operating in the background called GET. Think of GET as the fuel that keeps all ticketing operations running smoothly and empowers every step of a ticket’s journey. For the technical folk reading, GET is an ERC-20 token that lives on the Ethereum blockchain.
The beauty of GET is that all you need to know in order to use the protocol is how to top it up in the dashboard and the protocol handles the rest. Top ups are priced and paid for using traditional payment currencies in your local currency. Of course, we’re not in the business of hiding information for the sake of obscurity, we hide GET for the sake of simplicity, but all the information is readily available and transparent for you to read and digest both in this overview and in our technical documentation here.
To compare GET to other applications in the real world, think of it as a credit in an arcade machine, or gas for your car. We’ll continue using the gas analogy through the rest of this article as we feel like it’s the best method of comparison.
Why does GET exist then?
As we mentioned, we’re enthusiastic for developing simplistic to use, but powerful tools that go above and beyond in ways that make sense and feel easy to utilise. By having GET as the underlying payment system, we can allow both existing ticketing enterprises and prospective new companies to make use of our avant-garde ticketing infrastructure powered by the latest technology - we’re looking at you blockchain technology.
GET Protocol offers two different products that encompass a wide range of utilities, but just like how two cars require different amounts of fuel for the same journey’s length, the amount of GET needed to fuel a ticket on its journey comes down to differences based upon the product in use.
Our White-Label solution makes use of a full tooling infrastructure that builds on top of our blockchain and NFT layer. This solution includes mobile applications, dashboard, ticket shop and event organiser support systems. It’s a battle tested complete infrastructure that allows any fledgling ticketing company to go from no ticketing to scalable ticketing with just a quick setup time.
Meanwhile the Digital Twin is a non-invasive, easily integratable blockchain and NFT layer, that enhances existing ticketing operations at no risk to current business operations for the integrating party. Since the digital twin is meant as a lightweight add-on, it uses significantly less resources than our white-label.
The potency of GET is that it enables both products to utilise our robust infrastructure in different ways and a Digital Twin integrator or white-labeller doesn’t need to calculate or deal with the differences in fueling operations that are typically common with blockchain technology.
As mentioned earlier, the dashboard is the only point of contact needed for dealing with GET Protocol costs.
So how does each ticket actually utilise GET?
As a ticket moves through GET Protocol, it encounters what we call ‘interactions’, these are points in a ticket’s life cycle where a specific event occurs, these are:
Sold Resold Scanned Claimed Invalidated
When a ticket goes through an interaction, a percentage of the GET that is fueling the ticket is used as a fee in order to pass on to the next point in the ticket’s life cycle. This is where the analogy of fuel in a car and fuel for a GET Protocol ticket differs, whereas a car uses fuel continuously throughout its journey, our tickets use fuel at these interaction points in order to keep fees accountable at every step of the way.
But you don’t need to worry about this as it’s all processed behind the scenes and the calculations are accounted for at the beginning of a ticket’s journey. If you’ve topped up your GET through the dashboard then the protocol handles all of this behind the scenes.
We hope this article has provided you with a better understanding for the behind the scenes technicalities of GET Protocol. In an effort to ensure that technical depth is measured across all our platforms, our granular tokenomic and technical resources, are available via our documentation hub:
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.
Keep up to date with GET Protocol on social media via our Twitter.