We got the idea of this project from the necessity of backend in VeChain. We're sometimes in need of backend with internal DB to create interactive frontend. Accessing to personal internal DB would be much faster than accessing Blockchain DB.
What it does
This project describes basically about the backend structure using Connex. We implemented fetching events synchronously from the Smart Contract.
How we built it
The backend system we're introducing is based on Node JS. We used Connex framework for this. We built synchronous backend using endless loop with some delay. And each loop fetched the events happened within the delay filtering with connex.
Challenges we ran into
We had to decode the events we filtered since we could only get encoded events list when filtering. For this, we need to challenge with thor-devkit. Also there was a challenge while applying the filter to get the events list of filter since the method had two parameters required.
Accomplishments that we're proud of
We're proud of the solid backend system we've built using connex, which is the best option for VeChain. We've also tried web3 thorify but it wasn't more solid than connex.
What we learned
We learned how to implement connex to connect to VeChain and thor-devkit library in the backend. Connex in frontend and backend was different in usage.
What's next for Synchronization of Backend in VeChain using Connex
We're going to add more features for the backend system in VeChain.
Built with: Connex, Node JS, Express JS
Log in or sign up for Devpost to join the conversation.