Shay/ticketchain
1
0
Fork 0
mirror of https://github.com/0xShay/ticketchain.git synced 2026-01-11 13:13:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Ashprit Singh Mehra
2024-10-27 10:14:49 +00:00
committed by GitHub
parent a72873f1f8
commit 7beadecdb7
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@@ -12,10 +12,13 @@ Many popular ticket sites exist, that allow customers to browse different upcomi
- When popular events are released, many of these websites can slow down or sometimes even crash, worsening the experience for the end user.
- Single point of failure
- These central services consolidate all of the data and compute for their services in one spot. One possible risk to consider is a cyberattack - if the central organisation is compromised, all customer data is at risk of being stolen and leaked. Another possible risk is the central server going down, meaning ticket services would go down, which is not ideal if thousands of attendees are trying to verify themselves at an event.
- Hidden booking fees
- Centralised platforms often impose high service fees which aren't visible when viewing events. This is a lack of privacy issue because it is unclear how ticket prices are determined, leading to mistrust in customers.
-
## Proposal
We propose to build a solution which tackles these issues head-on. TicketChain is a decentralised website which allows users to browse upcoming events, and book tickets for these events through verifiable, immutable blockchain transactions. This allows users to purchase tickets. Functionality also exists for users to transfer their tickets to other users.
We propose to build a solution which tackles these issues head-on. TicketChain is a decentralised website which allows users to browse upcoming events, and book tickets for these events through verifiable, immutable blockchain transactions. This allows users to purchase tickets, even during higher volumes without performance degradation, all over the world. Functionality also exists for users to transfer their tickets to other users.
This is made possible through the use of smart contracts deployed on the blockchain which expose several public read and write methods, which can be invoked through our front-end user interface. A record of transactions are kept secure on the blockchain, and no central entity can tamper with these transactions.