Making dApps great again.
EGGE.GG The Future Of Esports Competition Team Members: Robbie Weinel Hayder Sharhan Somesh K S Status.im ID for Each Team Member (we will use this to contact you and your team) Robbie: https://get.status.im/user/0x044be687b9a8c52a2af4911a35737f20d834a0c836dd5c202413ab72f36106ef1349aceda14cccacb1463c198bce118be74d7d5338ec27a0101c785483739d0060 Somesh: https://get.status.im/user/0x04aa9d02a29de468e40419a22bf2bed01645ec082ab1682efe38fbae1c5bd0ba8ac5141be0ad2d2b96ec1d7b4a7d5b705fc115bf234ac712e3445
For those just starting to use Kotlin + Web3
Are you sick of web3js? I know I am! We are still forced to use it on the frontend but that doesnt mean that our backend event listeners and backend contract interactions have to go through this pile of poorly documented crap. I want to introduce you to a great alternative that Ive been using to write the backend of my dApps. First create a spring boot application: https://start.spring.io/ Pick Maven + Kotlin + latest version (Im using 2.1.4) + you can leave the names as is or give it something
For those looking to improve their Kotlin+Web3 skills
One of the greatest things that a web3 enabled browser gives us is saying goodbye to our primal ways of authenticating users with a username & password combination. If youre looking to authenticate users using a metamask or any web3 wallet then continue reading this article or simply explore the minimal code here: https://github.com/hshar7/springsecurity-web3-jwt-auth-demo You can checkout the code and follow along, or start fresh from spring initializer and start fresh, or add whatever you lear
It might be hard to roll your own implementation of a resilient web3 event consumer! You should if you have the time for it, but if you want something reliable