In 2002 the Oakland A’s shook the baseball world to its core. They did so by completely rethinking assumed baseball truths and executed on it. As an underdog they successfully challenged the dominant big-money competition, thereby changing the game forever.
The evident problems in the event industry have been stagnant for decades — irregardless of all drastic technological progress, ticket scalping has somehow gotten worse. Traditional ticketing thinking is medieval. We believe we are on the cusp of a “Moneyball”-like revolution for the entertainment and event space. Welcome to Ticketball.
By Kasper Keunen, blockchain developer at the GET Protocol Foundation.
The story of Moneyball
The movie Moneyball tells the story of Billy Bean the general manager at the Oakland Athletics around the year 2002. His approach to managing his team flipped traditional baseball-thinking on its head — changing the sport forever. …
It has been 3 months since the last buyback report, which means it is time for a new burn! If you are interested in the mechanics and logic behind the buyback, I encourage you to read the blog linked below.
Don’t trust, verify!
If you want to verify the state change count for yourself, I encourage you to run the numbers for yourself with the simple script available on the GET Protocol Github. The following command will import all IPFS batches between 28th of December and 27th of March:
python import_IPFS.py --startheight 11539000 --stopheight 12120640output: 216163 statechanges
Summary Q1 statechanges
The GET Protocol processed a…
By Kasper Keunen blockchain developer at the GET Protocol Foundation.
This blog is an excerpt from the January update blog.
Subjects to cover:
- On being blockchain agnostic
- Overview of blockchain partners
- Launch of Flusher & getNFT
“GET is blockchain agnostic” (???)
Over the years we have often described the GET Protocol as being ‘blockchain agnostic’. This isn’t a fancy way of saying we haven’t made up our mind yet. It is a fundamental design principle.
When interacting with a ticket issued by a ticketing company using the GET Protocol, a user doesn’t casually encounter any hashes, crypto addresses or 12 word seed backups. Our product…
By blockchain developer at the GET Protocol Foundation Kasper Keunen.
This blog is an excerpt of the February update blog.
Overview of covered subjects
- Flusher is live!
- Managing ticket transparency & user privacy
- getScan API overview
- Smart contract update — upgradability!
Ticket-back-log minting
After a full year of focusing on testing locally the first getNFT mints have finally hit the public ledger over the last weeks. Over the last 72 hours more than 35 000+ getNFTs have been minted by GETs ‘playground’ runner.
This runner is only the mocking the back-filling of 120 000 backlogged tickets in our system. …
It has been 3 months since the last buyback report, which means it is time for a new burn! If you are interested in the mechanics and logic behind the buyback, I encourage you to read the blog linked below.
Don’t trust, verify!
If you want to verify the state change count for yourself, I encourage you to run the numbers for yourself with the simple script available on the GET Protocol Github. The following command will import all IPFS batches between 28th of September(12:01) and 28th of December(12:00):
python import_IPFS.py — startheight 10950849 — stopheight 11539000Summary Q4 statechanges
The GET Protocol processed a total…
It has been 3 months since the last buyback report, which means it is time for a new burn! If you are interested in the mechanics and logic behind the buyback, I encourage you to read the blog linked below.
Don’t trust, verify!
If you want to verify the state change count for yourself, I encourage you to run the numbers for yourself with the simple script available on the GET Protocol Github. The following command will import all IPFS batches between 25th of July(12:00) and 28th of September(12:00):
python import_IPFS.py — startheight 10338066 — stopheight 10950848 Summary Q3 statechanges
221 211
The GET Protocol processed…
It is a well known fact that the primary and secondary ticket market are highly inefficient. At times it seems that ever actor involved in the market is getting the short end of the stick.
- Fans are getting scalped and scammed from all sides.
- Artists are missing out on resale market profits while still getting flack for allowing their tickets to be scalped in the first place.
- Resale market corrupts the validity of the customer data set of the ticket issuer(as secondary sales go undetected).
- Supply and demand on the secondary market is fractured and badly coordinated.
The only actors…
NFTs are all the rage at the moment. As is tradition in crypto the term ‘NFT’ is being massively overloaded. It is becoming harder and harder to distinguish a legitimate usage of NFTs with ‘going along with the latest fad’ NFT use-case.
The aim of this blog is to make clear that the usage of NFT technology by the GET Protocol to revolutionize smart ticket isn’t just window dressing.
By blockchain developer at the GET Protocol Foundation Kasper Keunen
Introducing getNFTs — Summary/TLDR
For almost half a year now the blockchain development team has been working a building a large scale custodial/non-custodial crypto-wallet infrastructure…
For the last couple of months we have been working hard on adding a new feature set to our protocol. In this blog I’ll provide a high level overview of what we are building in regards to DeFI and why we believe it to fit the markets needs.
Disclaimer. Most of the features and subjects discussed in this blog are still in development. Hence none of what is stated should be considered set in stone. All concepts, figures and processes are subject to change or could be eventually not pursued at all!
The DeFi craze of 2020
DeFi has been all the rage in crypto…
It has been 3 months since the last buyback report, which means it is time for a new one! If you are interested in the mechanics and logic behind the buyback, I encourage you to read the blog linked below.
Important note! The data in this blog has been changed (15 July)
Due to a bug in the state change counter the initial burn report used a faulty state change count(109k instead of 164k). Resulting in a discount rate that was too low(31% instead of 54%). I want to thank Deofex for noticing this error! This mistake was caused by operator error (me not noticing a bug).
We have taken several measures…
