Why functions define contract behavior in Blockchain / Solidity - See It in Action

Why Functions Define Contract Behavior

📖 Scenario: Imagine you are creating a simple blockchain contract that manages a digital wallet. This wallet can receive and send tokens. To control how tokens move, you use functions. Each function defines a specific behavior of the contract, like depositing or withdrawing tokens.

🎯 Goal: Build a basic Solidity contract with functions that define how tokens are deposited and withdrawn. Learn how functions shape the contract's behavior.

📋 What You'll Learn

Create a Solidity contract named SimpleWallet

Add a state variable balance of type uint to store tokens

Write a function deposit that increases the balance by a given amount

Write a function withdraw that decreases the balance by a given amount if enough tokens exist

Print the balance after transactions

💡 Why This Matters

🌍 Real World

Blockchain contracts control digital assets and define rules for transactions. Functions are the building blocks that let users interact with these assets safely.

💼 Career

Understanding how functions define contract behavior is essential for blockchain developers creating secure and reliable smart contracts.

1

Create the contract and state variable

Write a Solidity contract named SimpleWallet and inside it declare a public uint variable called balance initialized to 0.

Blockchain / Solidity

contract SimpleWallet {
    // Declare public uint variable balance initialized to 0
    // Your code here
}

Hint

Use contract SimpleWallet {} to start and inside declare uint public balance = 0;

2

Add the deposit function

Inside the SimpleWallet contract, write a public function named deposit that takes a uint parameter called amount and adds it to balance.

Blockchain / Solidity

contract SimpleWallet {
    uint public balance = 0;

    // Write public function deposit(uint amount) that adds amount to balance
    // Your code here
}

Hint

Define function deposit(uint amount) public and inside add amount to balance.

3

Add the withdraw function with check

Inside the SimpleWallet contract, write a public function named withdraw that takes a uint parameter called amount. It should subtract amount from balance only if balance is greater than or equal to amount.

Blockchain / Solidity

contract SimpleWallet {
    uint public balance = 0;

    function deposit(uint amount) public {
        balance += amount;
    }

    // Write public function withdraw(uint amount) that subtracts amount from balance if balance >= amount
    // Your code here
}

Hint

Use an if statement to check balance >= amount before subtracting.

4

Test the contract behavior

Add a public view function named getBalance that returns the current balance. Then, simulate calling deposit(100) and withdraw(40) and print the result of getBalance().

Blockchain / Solidity

contract SimpleWallet {
    uint public balance = 0;

    function deposit(uint amount) public {
        balance += amount;
    }

    function withdraw(uint amount) public {
        if (balance >= amount) {
            balance -= amount;
        }
    }

    // Add public view function getBalance() that returns balance
    // Your code here
}

// Simulate calls and print balance
// Your code here

Hint

Define getBalance() to return balance. Simulate calls by comments or test framework.

Practice

1.

Why do functions define contract behavior in blockchain programming?

easy

A. They specify what actions the contract can perform

B. They store data permanently on the blockchain

C. They create new blockchain networks

D. They control the blockchain consensus mechanism

Solution

1. Step 1: Understand contract behavior

   Contract behavior means what the contract can do or how it responds to calls.

2. Step 2: Role of functions in contracts

   Functions define specific actions users can trigger, shaping contract behavior.

3. Final Answer:

   They specify what actions the contract can perform -> Option A

4. Quick Check:

   Functions = Define contract actions [OK]

Hint: Functions show what contract can do [OK]

Common Mistakes:

• Confusing functions with data storage
• Thinking functions create blockchains
• Mixing contract behavior with consensus

2.

Which of the following is the correct syntax to define a function named transfer in a Solidity contract?

easy

A. function transfer[] {}

B. def transfer() {}

C. func transfer() {}

D. function transfer() public {}

Solution

1. Step 1: Identify Solidity function syntax

   Solidity uses the keyword function followed by the name and parentheses.

2. Step 2: Check each option

   function transfer() public {} matches Solidity syntax; others use Python or invalid forms.

3. Final Answer:

   function transfer() public {} -> Option D

4. Quick Check:

   Solidity functions start with 'function' [OK]

Hint: Solidity functions start with 'function' keyword [OK]

Common Mistakes:

• Using Python or other language syntax
• Missing parentheses after function name
• Using brackets [] instead of parentheses ()

3.

Consider this Solidity function inside a contract:

function getBalance() public view returns (uint) {
    return address(this).balance;
}

What does calling getBalance() return?

medium

A. The total supply of tokens

B. The balance of the caller's address

C. The balance of the contract's address in wei

D. The number of transactions made

Solution

1. Step 1: Analyze the function code

   The function returns address(this).balance, which is the contract's own balance.

2. Step 2: Understand what address(this).balance means

   It gives the amount of ether held by the contract in wei (smallest ether unit).

3. Final Answer:

   The balance of the contract's address in wei -> Option C

4. Quick Check:

   address(this).balance = contract's ether balance [OK]

Hint: address(this).balance returns contract's ether balance [OK]

Common Mistakes:

• Thinking it returns caller's balance
• Confusing balance with token supply
• Assuming it counts transactions

4.

Identify the error in this Solidity function that should transfer ether:

function sendEther(address recipient, uint amount) public {
    recipient.transfer(amount);
}

medium

A. Cannot call transfer on address type directly

B. Missing payable keyword on function

C. Amount should be in wei, not uint

D. Function must be private

Solution

1. Step 1: Examine the transfer call

   recipient.transfer(amount) where recipient is typed as address.

2. Step 2: Solidity ether transfer rules

   transfer is a method only on address payable. Must use payable(recipient).transfer(amount).

3. Final Answer:

   Cannot call transfer on address type directly -> Option A

4. Quick Check:

   transfer requires address payable [OK]

Hint: Solidity transfer requires payable address [OK]

Common Mistakes:

• Assuming transfer works without payable
• Confusing address types for transfer
• Thinking function visibility causes error

5.

You want to create a function in a smart contract that only allows the owner to change a stored value. Which function behavior best defines this contract logic?

hard

A. A private function that anyone can call

B. A public function with a check that only the owner can update the value

C. A public function that updates the value without restrictions

D. A function that automatically updates value every block

Solution

1. Step 1: Understand access control in contract functions

   To restrict actions, functions must check caller identity (e.g., owner).

2. Step 2: Identify function behavior that enforces owner-only update

   A public function with an owner check allows controlled access while being callable.

3. Final Answer:

   A public function with a check that only the owner can update the value -> Option B

4. Quick Check:

   Owner check in function controls access [OK]

Hint: Use owner check inside public function [OK]

Common Mistakes:

• Making function private but callable by anyone
• Not restricting access in public functions
• Assuming automatic updates enforce ownership