Pacing of the updates

We have decided to publish protocol specific updates once a month, an adoption/business update blog will also be published once every month.

We will always do all we can to hit the update targets we have set. Unfortunately it can happen that due to events, sprints and unexpected issues/tasks we are unable to publish these on time. Don’t read this as an excuse for keeping our community in the dark about what is going on, but more as context for why we might not be always able to hit every mark we set.

The Big Short. It ain’t what you don’t know what gets you into trouble. It’s what you know for sure that just ain’t so.

Changes to the roadmap

In the roadmap we stated that we would publish the ‘GET Protocol Yellow Paper’ in April of this month. This was a classic example of putting too much hay on our fork. A lot of progress has been put in formalizing actor incentive, social choice and all that other lovely mathematical mumble jumble. We now pause these efforts and will focus on confirming the underlying assumptions with market data.

As it seems, real life is a lot more nuanced than math. Not only does this become evident when making attempts to make a good impression on a girl in a bar (like I would know right haha.. ?). Complexity also tends to pop his head around the corner when defining strategies and goals for the two event and ticketing sector .

No formal proofs but practical proofs.

Due to these conclusion we have decided to move the publishing of the protocol yellow paper back to Q4. Instead of focusing on LateX we will dedicate our time and resources on ensuring our token to do some actual work. With this real life data and experience we expect to gain even more insights in how this token can help us shape ticketing for the better. This will mean that the GET Protocol GitHub will be made public in Q2 of 2018.

This means that the first GET acquisitions by event organizers will take place in upcoming months. Stay tuned for more information about this exciting first!

At the end of the day we believe that, now more than ever, it’s time for crypto to come out of the theoretic and academic shade and start executing its potential. Let’s give 100 000 crypto oblivious consumers an Ethereum wallet and use tokens to secure and facilitate the smart tickets they hold. I reckon that is what adoption looks like.

Targets

If you are still reading this good on you. If this text is still here you can shoot me an email at kasper@guts.tickets with your Ether address and the words ‘I actually read text walls’. I’ll send a token of appreciation your way!

The reason I write these long posts is that I want to take people along in our way of thinking about this industry and the problem we are solving. With the non-stop war for attention and hype going on in the crypto scene, people sometimes forget that building and causing change that is sustainable isn’t the equivalent of just writing code and collecting checks. By taking you along with our contemplation we hope to provide our community with enough context to think along and help us get there.

We truly believe that building and maintaining a community and awareness about our solution is crucial in making our goals reality. Without our community we are just another software company kicking and screaming against humongous competitors for a piece of the action. Empowering and informing our community is therefore very important to us. Recently we have made several changes to how we approach our community by hiring two new community managers. While most of their efforts still have to take root it is clear (for me at least) that we are going in the right direction.

We have started splitting up the GUTS Tickets and GET Protocol project identities, starting with social media presence and overall communication.

Targets we are going to hit:

Continue splitting the marketing and material on GUTS Tickets and the GET Protocol.

Produce & publish high-end explanation video for the GET Protocol.

Produce & publish 10 short explanatory videos (>2 minutes) in which a team member answers a frequently asked and crucial questions.

Launch an own stand-alone website for the GET Protocol.

Centralized exchanged listing.

Public GitHub repository.

Put the GET token to work ASAP, start buy backs for event cycles.

Ideas? Feedback? Let us now! We need you.