msg.value and msg.sender in Blockchain / Solidity - Step-by-Step Execution

Concept Flow - msg.value and msg.sender

Transaction sent

↓

msg.sender set to sender address

↓

msg.value set to sent ether amount

↓

Function executes using msg.sender and msg.value

↓

Contract updates state or transfers ether

↓

Transaction ends

When a transaction calls a contract, msg.sender holds the caller's address and msg.value holds the amount of ether sent. The contract uses these to process logic.

Execution Sample

Blockchain / Solidity

function buy() public payable {
    require(msg.value == 1 ether, "Send 1 ether");
    buyers[msg.sender] = true;
}

This function requires exactly 1 ether sent and records the sender as a buyer.

Execution Table

Step	msg.sender	msg.value (ether)	Condition	Action	State Change
1	0xABC123	1	msg.value == 1 ether	Check condition	Pass
2	0xABC123	1	Condition passed	Set buyers[0xABC123] = true	buyers[0xABC123] = true
3	0xDEF456	0.5	msg.value == 1 ether	Check condition	Fail
4	0xDEF456	0.5	Condition failed	Revert transaction	No state change

💡 Execution stops when condition fails or function completes successfully.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
msg.sender	N/A	0xABC123	0xABC123	0xDEF456	0xDEF456	N/A
msg.value	N/A	1 ether	1 ether	0.5 ether	0.5 ether	N/A
buyers[0xABC123]	false	false	true	true	true	true

Key Moments - 2 Insights

Why does msg.sender always show the caller's address?

Because msg.sender is automatically set by the blockchain to the address that initiated the transaction or call, as shown in steps 1 and 3 of the execution_table.

What happens if msg.value is less than required?

The require condition fails and the transaction reverts, so no state changes happen. This is shown in step 4 where the condition fails and buyers mapping is not updated.

Visual Quiz - 3 Questions

Look at the execution_table, what is msg.sender at step 3?

A 0xABC123

B 0xDEF456

C 0x000000

D Not set

💡 Hint

Check the msg.sender column at step 3 in the execution_table.

At which step does the transaction revert due to msg.value?

A Step 3

B Step 2

C Step 4

D Step 1

💡 Hint

Look for the step where the condition fails and action is 'Revert transaction' in the execution_table.

If msg.value was exactly 1 ether at step 3, what would happen?

A buyers[0xDEF456] would be set to true

B Transaction would revert

C Nothing changes

D msg.sender changes

💡 Hint

Refer to the pattern in steps 1 and 2 where condition passes and buyers mapping updates.

Concept Snapshot

msg.sender is the address calling the contract.
msg.value is the amount of ether sent with the call.
Use msg.value to check payment amount.
Use msg.sender to identify who called.
If msg.value is wrong, revert transaction.
These are set automatically by the blockchain.

Full Transcript

When a blockchain transaction calls a contract, the system sets msg.sender to the caller's address and msg.value to the ether sent. The contract can check msg.value to ensure correct payment and use msg.sender to track who called. If the payment is incorrect, the contract can stop execution and revert changes. This example shows a buy function that requires exactly 1 ether and records the buyer's address. The execution table traces two calls: one with correct payment that updates state, and one with insufficient payment that reverts. Variables msg.sender and msg.value change per call, and the buyers mapping updates only on success. Understanding these helps write secure contracts that handle payments and identify callers correctly.