Again two weeks have past and again it’s time for yet another Blocktix Development Update. Our development team has been busy integrating the My Events page with the blockchain and several further updates to the development side. However we also have some more news before we delve further into the technical side of things.
Exchange Listing
Over the past two weeks our community expressed their wishes of getting added to the Cryptopia Exchange. We are happy to announce we’ve been able to get listed here as per the 10th of October; adding, amongst a Litecoin and Doge pairing, a Bitcoin pairing to Blocktix. You can find the listing over here:
Moving to Discord
Over the past weeks we’ve been looking at different solutions for our current Slack channel. However Slack is a great team chat software we feel it isn’t suited for a crypto-community anymore. Scam and phishing attempts have been a daily nuisance with reaching over 50,000 direct messages a week from scammers on the Blocktix Slack channel. Even working with CAPTCHA on the signup page didn’t do much to keep scammers at bay.
That why, starting this week, we will be moving to Discord, effectively closing down the Slack during the remainder of October. Discord has a lot more options regarding permissions for the Blocktix community itself and users can also easily manage their private messages, making it a lot harder for scam attempts. Join our Discord Channel today!
Development of Blocktix
We’ve been quite busy again over the past two weeks, making good progress on the development process. We are now at a stage where we have started integrating the My Events page with the blockchain. The state service which is capable of determining the difference between data that has already been Published or Mined on the Ethereum Blockchain, and data that’s still pending (or Pending transactions) has been written now.
The IPFS integration has been completed now, as well as storing the hashes in the contracts, and we implemented a transaction queue to keep track of changes that need to be published on events, such as ticketing, information changes, image changes, etc.
A lot of work has gone into the the Ticket Verification and Ticket Redemption parts of Blocktix, where we are far enough along now that we need to catch up on the User Interface for it. The event backing implementation is done, where we allow a single backer to back an event.
We also completed the fund withdrawal on the Event, so once an Event has ended, the promoter will have the ability to Withdraw funds from the Event contract.
Lastly we have been working on the different roles the Event will allow for. This means you can add admins to the Event that will be able to add ticket types, and make changes to the events, as well as introducing the Ticketer role.
The ticketer role will allow ticketers to redeem the Ticket, which has to first be signed by the Account that is currently holding the ticket. The contract will verify that the ticket has been signed by the correct account, and the ticket will be redeemed at this stage.
In Conclusion
In the past two weeks we’ve tackled several hurdles on the development side of things. The groundwork is now mostly finished and we’ll be ramping development up even further.
We’re now starting to close in on a testnet version of Blocktix, where we will have more news on this in the next update.
For those wondering what is happening with the Website update: It’s coming soon; just some last coding and making sure all works as intended and we’ll release it to the public.
