The One Question bounty closes Thursday 10 December.

Join in
We Them Media logo We Them Media Support us

Web3bridge Students (Cohort XI) Share What They’ve Learned: Intro to REACT

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

A Web3 Bridge Cohort 11 student introduces React and compares Web2 with Web3: Web2 keeps data on central servers, while Web3 stores it on a blockchain through smart contracts. They explain that a front end talks to a wallet, which signs transactions sent to a node holding a copy of the chain, with node providers supplying the endpoints.

Not by We Them Media Channel: Web3Bridge. Published Tuesday 17 December 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:00 A: This video is proudly brought to you by Breakthrough Bridge with Lix, our official sponsors for Cohort 11.

0:08 B: React is actually a JavaScript library used for building a frontend for user interfaces whereby users can come and see whatever is happening on

0:30 C: Web2 basically uses database, a centralized database, and data is stored on centralized servers. For the Web3, which has a decentralized nature, is stored on the blockchain, the blockchain technology, and we look into how data is actually stored. So from the front end to the back end where data is seen on the client to the server. That is for Web2. On Web3, data is being stored on the blockchain in a decentralized nature, and we make use of smart contracts on the Ethereum blockchain to store data. So basically, those are the core areas in which Web2 differs from Web3.

1:12 D: Other characteristics of Realities is it does not use the normal DOM, it uses a virtual DOM. It is also a component-based architecture and it allows proper state management through hooks.

1:30 E: So as the architecture goes, the frontend-facing UI would communicate with a wallet, be it MetaMask or Connect Wallet or whatever wallet it may be. Now that wallet will handle signing transactions that were made to a node which has a copy of a particular blockchain, any particular L1s. There are Ethereum, Bitcoin, whatever respective L1s that there are. So what a node is basically is that it's a dedicated system that actually runs a replica of a particular blockchain. That is, it has the respective- first off, it has the needed software that it needs that's required to actually have a replica of all the data that's being stored in a particular blockchain and then grants the respective users access to communicate with that particular blockchain, be it reading data from it or writing data to it, or basically interacting with a particular smart contract via that node and also carrying out transactions on that node, serving as a distributed replica for that particular blockchain. So for that to be carried out, the respective node service providers out there, the usual suspects will be out Kemi and Infura, they already grant like an endpoint to frontend applications that communicate with them and then in turn communicate to, communicate with the respective information that's being held by that node, copies of the particular blockchain that it's serving or running a replica for.

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.