Why functions define contract behavior in Blockchain / Solidity

Introduction

Functions in a contract tell the blockchain what actions the contract can do. They are like instructions that define how the contract behaves.

When you want to create a rule that others can follow on the blockchain.

When you need to let users interact with your contract, like sending or receiving tokens.

When you want to organize your contract’s logic into clear steps.

When you want to make sure certain actions happen only when specific conditions are met.

Syntax

Blockchain / Solidity

function functionName(parameters) public returns (returnType) {
    // code to execute
}

Functions are blocks of code that perform specific tasks inside a contract.

The 'public' keyword means anyone can call this function.

Examples

This function lets anyone see the current balance stored in the contract.

Blockchain / Solidity

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

This function allows users to send money to the contract and updates the balance.

Blockchain / Solidity

function deposit() public payable {
    balance += msg.value;
}

Sample Program

This contract has two functions: one to deposit money and one to check the balance. It shows how functions define what the contract can do.

Blockchain / Solidity

pragma solidity ^0.8.0;

contract SimpleBank {
    uint private balance;

    function deposit() public payable {
        balance += msg.value;
    }

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

Important Notes

Functions are the main way to interact with a contract on the blockchain.

Each function can have different access levels like public, private, or internal.

Functions can change the contract’s data or just read it.

Summary

Functions tell the contract what actions it can perform.

They organize contract behavior into clear, reusable steps.

Functions allow users to interact with the contract safely and predictably.

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