The One Question bounty closes Thursday 10 December.

Join in
We Them Media logo We Them Media Support us

Web3bridge Students (cohort 11) Share What They’ve Learned: Transaction

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

A student explains Ethereum transactions: the three types, which are value transfer, contract deployment and contract execution, and their parts such as sender, recipient, nonce and gas limit. They cover hashing, how a transaction waits in the mempool, gets batched into a block and becomes harder to reverse as more blocks follow.

Not by We Them Media Channel: Web3Bridge. Published Tuesday 8 October 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:04 A: Hey, hi, I'm Shogun Olale. I'll be talking about transactions. Transaction in Ethereum is a cryptographically signed instruction that takes place on an account, and it is used to basically update the state of the Ethereum network. From transactions, we can see that transactions have various types, and they include value transfer, contract deployment transaction, as well as execution of contract. The value transfer is basically a form that involves sending or carrying out an activity from an account and to another account within the Ethereum network, literally, while the Contract deployment transaction is literally a form of transaction where a to is not specified. And this literally means you're not sending to an address within the Ethereum network, literally. So this is basically used in terms of, you know, just as the name is smart contract, you're trying to deploy a smart contract on the network. Execution of transaction, literally. is literally initiating some sort of interaction with the contract that has been deployed. So that's literally what the types of Ethereum transactions are. Then we also have different components that like build up the transaction, and we have factors such as from, to, nonce, gas, gas limits, max fee, priority per gas and base fee per gas as well. So from literally, um, expatiates on where is this, where is this transaction coming from? So what wallet address or so is it coming from? And to specifies who am I sending it to? Just the same way we do in our everyday traditional means of carrying out transactions within our mobile banking. So the nonce is a form of iterating variable counter that keeps check of how many transactions that has been made, and it literally provides a form of unique ID for every transaction. And the gas limit is you specifying the maximum amount that you intend to use to carry out that transaction.

2:44 B: So transaction hash can also be called transaction ID because it is just like a unique identifier that comes with each and every transaction. One of those ways with which blockchain, you know, enables privacy and security, with which blockchain achieves that, is by using the concept of hashing, Merkle tree, private and public key. But I'm going to be concentrating more on the hashing, on the concept of hashing. And it has to do with using, you know, cryptographic hash function in order to convert transaction data into a string of fixed length. And once the transaction has been, you know, converted into a string of fixed length, so it gives, um, it makes that, um, transaction to be secure, as hashing comes with this, um, nature of, you know, when something is being hashed, it's not going to be reversible again. So it gives security to to the data. And also, it's one of those things that the hashing does is, is just like to serve as a proof of existence for a particular transaction. So through the transaction hash or the transaction ID, you can easily get access, you know, to the transaction. You know the genesis, where it is coming from, and also you, you know the, the destination. So with all these, the, the data is going to be, you know, secure, and also there's going to be transparency and trust.

4:18 C: So after a transaction has been propagated to the network, it gets caught up, it's stored in the mempool. So it's kind of a queuing. So once it's been queued, the next thing is that a node picks it up and executes that transaction. So once the transaction is executed, it's batched into a block. So it's batched alongside other transactions, then it's batched into a block. So that proposal, the node that executes it, forwards it to the other nodes. So what those nodes do is to run the transactions that are in that node, in that block, to make sure that what the proposer is giving back to the network is valid. So once they do that and it's valid, it's okay, it's added to the chain, to the chain of blocks. So that's the process, that's what happens in that sequence. It happens in that sequence. So the next thing is that And to ensure that, to ensure that a block cannot be reversed, the more blocks are added, the more, the more, the more the blocks are added, you know that these blocks cannot be, cannot be reverted again. It cannot- there's no reversibility that can happen again. So basically that's what happens. So the more blocks are mined, or rather added to the chain, the more secured and the more you know that these transactions are hitting finality. So basically that's the entire lifecycle for transactions on the chain. So stay tuned and like, subscribe to our YouTube channel.

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.