DEV Community: Romain @devvnomad

How I made a Web3 app to reward my community with tokens

Romain @devvnomad — Tue, 15 Feb 2022 07:20:53 +0000

When I started my web3 journey I got a freelance contract: Add web3 features to an existing app and reward the users with our token.

The point of rewarding the community was:

To motivate the community to do something to earn a token.
The brand wanted to have its own token to improve branding.
Rewarding the user with tokens is becoming more and more common these days.

Our users should get 5 tokens when completing their profile (bio, curriculum, social media links, etc.).

But we could imagine rewarding users for many other kinds of actions, such as: commenting on a post or sharing a post on social media.

Create a token ⚒️

The first major task was to create a token.

After some research and discussions with other DEV, I decided to use an ERC-20 token.

I made one million token supplies and decided to lock half of it using a time lock contract.

Locking tokens is for purpose to give trust to your tokens to your users.

Get the wallet public ID of the user 🆔

Then, I had to connect my front-end to Metamask API (or to wallet connect)

The goal is to get the wallet public ID of my users.

With this wallet public ID I will be able to transfer to theses users my reward’s tokens.

I also needed to add our token to their Metamask wallet. Which was something I could handle with the Metamask API.

I then simply saved the wallet public ID on the user table. I will use this public ID later.

Reward the users when they complete their profile 👏

When a user completes his profile on the app we need to send him 5 tokens.

Firstly I made a « reward » table on the back-end. I want to know whether that specific type of reward was already given to this user.

Then on my back-end, I needed to make an endpoint that would trigger a function to make a token transaction.

To make a transaction I used etherJs on my NodeJs app. When the conditions are met, I make a new transaction from my wallet ID to the user walletID.

I also pay the gas fee using my wallet automatically. My server can access my wallet using my wallet’s private key.

When a transaction is successful, the user will get a notification and the token will appear in his wallet.

Deploy our token to the Polygon network 🕸

Using Ethereum network is expensive when it comes to pay gas fee. That’s one of the reasons we decided to go for Polygon Matic.

Polygon is also a part of the blockchain network. However, the cost to operate is well cheaper than on Ethereum.

On localhost I was using a Testnet network. A fake network, that I set up with HardhatJs.

I now needed to push my ERC-20 token to Polygon network.

I used again HardhatJs in order to deal with this.

Security concerns 🔒

When it comes to Web3 and Blockchain, I had to make sure that my setup was safe 😀

By safe I mean:

I don’t want bots to be able to make thousands of transactions.
I don’t want people to use my wallet ;)

This is what I did for this app:

I stored the wallet private key on the environment global variables of my server.
That wallet contains only a few Ethers. Enough to pay a few months of gas fee
That wallet contains only 1% of the tokens we created.
A user cannot get multiple reward tokens for the same type of reward. For example, the type of reward was « set-up-profile-reward ».
Only logged users will get a reward.
We verify that the user is the right one by signing the bearer token. We stored the signature of that bearer token on the server.

This is how that process looks:

What’s Next?

I’m planning in the future, to release Saas App using Web3 and to accept more freelance contract using that technology.

👉 You can follow me there on Twitter, as I continue to document my journey.

How I became a Web3 dev in just 7 days and got my first 8000$ Web3 contract

Romain @devvnomad — Fri, 04 Feb 2022 08:32:54 +0000

A few weeks ago I got a Web3 project. I have 6 years of full-stack development, and I was a CTO for half a year.

However, I never had to deal with Blockchain or Web3 before

But, I like being challenged! And I know to learn stuff when I need it.

This is how I successfully learnt Web3 from scratch, and I delivered that contract.

This is how you can also proceed and become a Web3 developer.

Day 1-2 - Mass learning 📚

During the 2 first days, I learnt in mass. That period had for purpose to understand the basics of Web3 and Blockchain.

First, I started to go on Youtube to watch videos about it.

When I don’t get a new word or a concept I write it in my list. Then I will try to find new videos or articles about these terminologies.

Example: Gas fee, Smart Contract, DAO, Dapp, DEX, ERC-20, non-fungible token, Gwei, ICO ...

I write new concepts in my list and I will check them later

Each video gives me an average of 5-8 new terms.

Watching 5 videos will already give me a new list of 25 other concepts to understand later…

I made a notion page, where I wrote everything I understood. I will never reread these notes. I write for the sake of memorization.

I spent around 7 hours by day for 2 days to do just that. In the subway, office, or when walking (podcast).

My goal was simple:

To submerge myself in this web3 world, to get lost.

I will most of the time not understand more than 60% of what I'm watching or reading. But that’s all fine at this point.

That knowledge will come back later on in some way...

The goal 🎯: to submerge myself into web3.

After 2 days, I feel like I have reached a rabbit hole. I knew it would happen. Each concept brings a new concept. It’s endless...

However, I know that I need to pass to the next phase at this point. I need to put into practice the few things I understood.

🔨 The next step: to put in practice all that knowledge

Here is a list of the resources I used during that period:

Day 3 - To define the scope of the Web3 project I will work on

I got a freelance project with some requirements: I checked the specs and tried to summarize them as much as I could with my current knowledge of Web3:

👉 We need to make our own token.
👉 When a user does something on the website (share an article, complete his profile), we send him our token.
👉 The user needs to be able to add his wallet to our website.
👉 We need to deploy that token on the Polygon Matic network.
👉 When sending a token to the user, we need to automatically pay the gas fee.
👉 For that, we need to allow our backend to pay that gas fee with our wallet.

Scoping the project allowed me to think more clearly about the next steps.

Then for each of these items I tried to understand which library and logic I would have to implement.

I spent 4-5 hours searching on Google and writing pseudo-code.

Then I asked a senior blockchain DEV if my plan looked credible to him.

I also asked him some points I was confused about. For example, what would be the best way to automatically pay the gas fee.

That discussion was fruitful, but I knew I still had a lot to learn and understand!

Now I needed To see how other people are making Web3 app

Next, let’s get my hand dirty, let’s practice and understand things by doing.

Day 4-5-6: Make my hand dirty with other Github repositories. 🔨

That’s when I started to look on GitHub for Web3 repositories having similar functionality to what I wanted to achieve.

When I find a repository, I look at the code. I analyze it and try to make it work.

I then take some piece of that code and try to make it work on a new project.

By doing that, I start to understand more clearly the thing I watched on YouTube or read on some blog.

This is when I have some moment of: « Oh yeah, this is why…! » 😀

By playing with Web3 repo, the theory starts to make sense.

Here is a list of the resources I used during that period:

Day 7: To assemble the puzzle 🧩 and to re-scope my project

Right, after 2 days of playing with repositories and making code snippets, I started to understand what needed to be done for my Web3 project.

I updated a little bit of my plan. And made it simpler and more secure than before.

Then again, I asked another blockchain DEV to check it out. « Better! »

I’m ready to go and I will spend 2-3 weeks to finish that project.

What I learnt so far during this week: 📕

To set up smart contracts with Solidity and use Openzeppelin.
To handle user’s wallet with Metamask API and Wallet connect.
To set up a Testnet environment with HardhatJs.
To interact with my smart contract and make transactions on the back-end using etherJs
To deploy smart contract into Polygon Matic.
To make timelock smart contracts.
A minimum of security when it comes to set-up blockchain’s features
...

I made a PDF with all the resources I have been using in my web3 journey: check it out here

What’s Next?

I’m planning in the future, to release Saas App using Web3 and also to accept more freelance contracts using that technology.

👉 You can follow me there on Twitter, as I continue to document my journey.