The problem CryptoBookings-A Web3-Based Event Booking platform solves

• CryptoBookings is a pioneering web3-based booking platform that aims to revolutionize the ticket purchasing and refund process. The problem it addresses is the delay and inconvenience users face when withdrawing tickets on traditional platforms, where the refund process involves waiting for days for the organizer and the bank to process it. CryptoBookings offers an innovative solution where, upon ticket withdrawal, the refund is immediately deposited into the user’s account, providing a seamless and efficient user experience. This immediate transaction process sets CryptoBookings apart from other platforms, making it a game-changer in the event booking industry.

• User Adoption: Convincing users to adopt a new technology, especially one as relatively complex as blockchain, can be difficult. It requires significant efforts in user education and interface design to ensure a smooth user experience. This is why CryptoBookings implements zK-Login through which users are familiar with the transactions as the complex layer is hidden behind the zK-transactions.

Challenges I ran into

• Varying Versions: One of the major challenges is dealing with varying versions of the technology. This can lead to compatibility issues and errors, requiring constant updates and maintenance to ensure smooth operation.
• Blockchain Scalability: The scalability of the blockchain can be a challenge. As the number of transactions increases, it can lead to slower transaction times and higher costs. The Avalanche Subnet (may be applied later) that this contract will be working on would need to be able to handle high amount of transactions especially during popular events and rush hours.
• Lack of Documentation: There aren’t enough guides or instructions to help understand how to use new technology like blockchain. This can make it hard for a solo developer to learn and use the technology correctly.
• Integration with frontend: Integrating the smart contract with the project proved to be a difficult task due to ambiguous errors for which the answers could not be found.
• Lack of Testing methods: Although Remix is present as the premier testing ground for smart contract, it still struggles with a lack of UI based testing and support for openzepplin contracts and imports support.