First music festival turns to blockchain

Wonder how they process the tickets at the gate without causing delay through ticket validation ?

Wonder how they process the tickets at the gate without causing delay through ticket validation ?

Validation of a purchase is a very fast process. A fraction of a second.

More questions, sorry. What would someone actually show at the gate? Is it possible to give a ticket to someone else? For example, you want to buy a ticket for your grandparents to see a Tom Jones concert.

How would the validation work though, say In order to avoid copies of the same Ticket for example.... ?

This article might as well left out any mention of what goes behind putting together concerts/fesitvals, because they ultra simplify it to the point of it being total bs. It's a hell of a lot more than 2 people sitting at a desk - it's about a baker's dozen and that's just to get the ball rolling.

Lineups aren't going to be so easily swayed just because people have amassed cryptocurrency (or even buckets of cash). It has to do with album cycles, current avails, tour routing, and a plethora of other metrics.

Promoters don't need to "ask the fans" because they use Pollstar, Ticketmaster and some other tools to know how many tickets were sold in any given city/state/country and venue and can gauge how well an artist will do in any given market (A, B, C), hard ticket vs soft, and so forth.

I see no major issue with using blockchain compared to paper/electronic ticketing. But it's not going to sway pwoer away from Live Nation/Ticketmaster or AEG who collectively own (or buy up) most of the major/indie festivals and large venues you go to nowadays.

How would the validation work though, say In order to avoid copies of the same Ticket for example.... ?

Blockchain works on a series of private and public keys. The public key is out there for everyone to see. A private key needs to be kept private. The hash that identifies a transaction (likely the purchase of a ticket in this scenario) will be made up through a combination of the hash for the ticket itself, and the public key of the user who owns the ticket (the purchaser). When combined with the private key of the user, it results in the transaction hash that links the owner (public key) with the ticket (ticket hash). This is why validation is so quick. It's pretty much impossible (at this point in time) to reverse engineer the private key (that's the whole point of keys), but it's very easy to verify if a given private key is correct or not.

The mobile app will likely handle the private/public keys for the purchasers. The blockchain aspect of it will not be visible to the users of the app, it will just be the back-end technology to manage tickets.

And that everyone can see everyone else who bought tickets? That seems unlikely and unsafe. I hope I’m misunderstanding what this means.

Well, you can see that ticket number 2343242 is owned by someone with the public key dsfk434ssddf23k2lsdfaksjfoeksa. But that won't tell you who dsfk434ssddf23k2lsdfaksjfoeksa is.