The problem BVENT(Blockchain+EVENT) solves

Hi all, we’ll going to present our brand new blockchain events review platform called Bvent which allowing users to get involved in rating or writing reviews about attended blockchain events and conferences

Before get started, we would like to give a brief background that why we chose to provide and create this service. As u see in this slide, the number of blockchain conferences has been tripled in 2022 compare to 2017, but yet, there is no such application that mainly focused on blockchain events or conferences that can share quality of conference reviews, schedules and attendee experience. Moreover, those who are not able to attend conference on site must get to consider the time difference if they are participating from abroad.

So Bvent has created in order to solve aforementioned problems. Bvent is mainly concentrated on three key functions which are time difference helper, review aggregator, and review compensation, targeting as our key users on those who participating global blockchain conferences, researchers or reporters who need conference information with details, and those who hosting blockchain events as organizers and sponsors

Our ultimate goal is increasing up to 1,000 of major blockchain events in the globe including 3,000 of small-sized events in annual by 2025, and by doing so, we provide quality of information to blockchain congregates, contributing to global blockchain ecosystem ultimately.

Here u see a visualized Bvent ecosystem that we pursue. So basically, we will accumulate users by operating bvent service. Users who write their reviews or rate on particular conferences will be compensated with tokens and those tokens are swappable to Bvent Dao governance SBT. The reason we set up SBT is to prevent arbitrage trading. Once users get this SBT, they will be authorized to make vote for which fine side-event to institute as a sub-DAO.

Challenges we ran into

Challenges Encountered

There were two major huddles worth highlighting:

1. Opening up 10+ endpoints for the client, and establishing a standard for APIs
2. Using and deploying a Python main server as well as a NodeJS-based Google Cloud Function for Comment Token transactions.

Challenge 1. Endpoints

Challenge: Our product has multiple services available. Therefore, the server is required to open 10+ endpoints and the client is required to follow the specifications required by the server. Keeping, managing, and testing the endpoints in one place was very challenging.

Solution:
We used (1) A standard API documentation system that denotes required HTTP method / fields / expected results and (2) An API testing solution based on Postman.

API Documentation

API Testing:

Challenge 2. Server and Google Cloud Functions

Challenge:

The language that we used for the main server(Flask, python) was not compatible with the language used for establishing transactions with the Comment Token (NodeJS). Therefore, we had to devise a convenient way establish a NodeJS server for token transaction.

Solution:

We used Google Cloud Functions (GCF) to create a lightweight HTTP endpoint. GCF would respond to the server's request to proceed a transaction.

However, because we weren't quite familiar with Google Cloud Functions, there were additional issues. Finally after (1) changing the request type to application/json (doesn't support multipart/form); (2) adding all requirements to package.json; and (3) changing the HTTP req,res to comply with async/await required for the transaction, it was functional!

Also, as there was latency issues (~30s) for transaction, server used threads for calling GCF.