The One Question bounty closes Thursday 10 December.

Join in
We Them Media logo We Them Media Support us

Team MsgSender Shares Their Insight on Dapps, What They Learned, and Built

The picture loads from YouTube. The player loads only when you press Play. Turn on captions in the player if you need them.

Victoria Adedayo and teammates from team NFT recap a week on dApps at Web3 Bridge. They describe a get and set message contract and a simple registry contract, explain why verifying a contract builds user trust, and list the tools used: Hardhat, React and Ethers.js.

Not by We Them Media Channel: Web3Bridge. Published Monday 25 March 2024.

Titles are the owner’s. It plays from their channel.

Transcript

This transcript may contain errors. This video belongs to Web3Bridge. Letters mark each change of speaker.

These are the speakers’ own words. We have not checked their claims.

0:23 A: Hi everyone, my name is Victoria Adedayo. Welcome to another week at Web3 Bridge. I'm here with my team members,

0:32 B: Daniel

0:32 A: Adianty, Samson Patrick. We are team NFT members. We're here to talk about what we've learned throughout the past week, and the thing we want to talk about is dApps. So a dApp is just basically a frontend connected with a smart contract.

0:47 B: So, um, talking about dApps, um, last week at Web3 Bridge, I was- I built- we built a dApp. A smart contract which is the getMessage contract. And basically what that does is that it has 2 functions which is getMessage and setMessage. So how it works is that, okay, a user is able to input a message and that message is being sent to the blockchain. And when the user clicks on getMessage function, the contract is able to retrieve that message the particular message from the blockchain back to the user.

1:22 A: So yeah, there's another contract we built which is the simple registry contract. So this contract takes 2 global variables which are the name and the age, and we have 3 functions that update the name, update the age, and another function that gets all the entities which are the name and the age. So it gets everything, retrieves it, and sends it to the frontend for the user. So, and also, I also went ahead to verify the smart contract because I've learned that it's good to verify your smart contract because it helps the users, you know, trust your smart contract. Because in the wallet where you're about connecting, you'll see something like, this contract is not verified, go ahead if you trust the contract and all. But if your contract is verified, you don't need- they don't- they won't give you that message because the contract is already like verified. So

2:10 C: Yeah, basically what they have talked about wouldn't have been possible without us using Hardhat. We made use of the Hardhat, which is a development environment for our Ethereum software, which gives us the ability to- or will provide components for us to deploy our contracts, test our contracts, and even compile our contracts. On compilation of our smart contract, an API is built on it, which is the Application Binary Interface. which have been generated on compilation. And then we make use of these APIs for our frontend, and our frontend is made use of React. And then we installed Ethers.js, which helps us interact with our blockchain. And also it makes it possible for us to- when you see a button and then you click a button, it pops up the wallet for us. So all this is being made possible with Ethers.js. Which help us connect. So basically what they have talked about, the get message and the simple registration, we made use of these tools, the Hardhat and then the Etherscan, to make all this possible.

3:14 A: So yeah, you heard all this, all what we learned this week, and it's been a really exciting week. So this is us signing off for now. See you next week. Bye!

More from this hub

Something wrong, or a video you want off this page? Write to wethem.xyz@gmail.com and it is fixed or taken down within 48 hours.