Abstract contracts in Blockchain / Solidity

Introduction

Abstract contracts help you create a base template for other contracts. They define functions without full details, so others can build on them.

When you want to define common rules for many contracts without writing full code each time.

When you want to force other contracts to implement certain functions.

When you want to organize your code better by separating shared logic from specific details.

Syntax

Blockchain / Solidity

abstract contract ContractName {
    // Declare functions without implementation
    function functionName() public virtual;

    // You can also have implemented functions
    function implementedFunction() public {
        // code here
    }
}

An abstract contract cannot be deployed directly.

Functions without implementation must be declared without a body and marked as virtual.

Examples

This abstract contract defines a function startEngine without details. Other contracts must provide the details.

Blockchain / Solidity

abstract contract Vehicle {
    function startEngine() public virtual;
}

Here, area is abstract and must be implemented. description has code and can be used as is.

Blockchain / Solidity

abstract contract Shape {
    function area() public virtual returns (uint);
    function description() public {
        // This function has implementation
    }
}

Sample Program

This program shows an abstract contract Animal with an abstract function sound. The Dog contract implements this function. The Test contract creates a Dog and gets its sound.

Blockchain / Solidity

pragma solidity ^0.8.0;

abstract contract Animal {
    // Abstract function without implementation
    function sound() public virtual returns (string memory);
}

contract Dog is Animal {
    // Implementing the abstract function
    function sound() public override returns (string memory) {
        return "Woof!";
    }
}

contract Test {
    function getDogSound() public returns (string memory) {
        Dog dog = new Dog();
        return dog.sound();
    }
}

Important Notes

Time complexity depends on the functions implemented in child contracts, not the abstract contract itself.

Abstract contracts save space by avoiding repeated code and enforce rules for child contracts.

Common mistake: Trying to deploy an abstract contract directly will cause an error.

Use abstract contracts when you want to force other contracts to implement certain functions, unlike interfaces which only declare functions without any code.

Summary

Abstract contracts define functions without full code to be completed by child contracts.

They cannot be deployed alone but help organize and enforce rules.

Child contracts must implement all abstract functions.

Practice

1.

What is the main purpose of an abstract contract in blockchain programming?

easy

A. To define functions without implementation that child contracts must complete

B. To deploy a contract directly on the blockchain

C. To store data permanently without functions

D. To create a user interface for blockchain apps

Solution

1. Step 1: Understand abstract contract role

   Abstract contracts declare functions without full code, acting as templates.

2. Step 2: Identify deployment capability

   They cannot be deployed alone but require child contracts to implement missing parts.

3. Final Answer:

   To define functions without implementation that child contracts must complete -> Option A

4. Quick Check:

   Abstract contract = function templates [OK]

Hint: Abstract contracts declare incomplete functions for children [OK]

Common Mistakes:

• Thinking abstract contracts can be deployed directly
• Confusing abstract contracts with interfaces
• Believing abstract contracts store data only

2.

Which of the following is the correct syntax to declare an abstract contract in Solidity?

?

easy

A. contract MyContract abstract { function foo() public; }

B. abstract contract MyContract { function foo() public virtual; }

C. abstract MyContract contract { function foo() public; }

D. contract MyContract { abstract function foo(); }

Solution

1. Step 1: Check abstract contract declaration

   In Solidity, use 'abstract contract' before the contract name.

2. Step 2: Verify function declaration

   Abstract functions are declared with 'virtual' and no body.

3. Final Answer:

   abstract contract MyContract { function foo() public virtual; } -> Option B

4. Quick Check:

   Correct abstract syntax = abstract contract MyContract { function foo() public virtual; } [OK]

Hint: Use 'abstract contract' and 'virtual' for abstract functions [OK]

Common Mistakes:

• Placing 'abstract' after 'contract'
• Missing 'virtual' keyword on abstract functions
• Trying to define function body in abstract contract

3.

Given the following Solidity code, what will be the output when child.getValue() is called?

abstract contract Parent {
    function getValue() public virtual returns (string memory);
}

contract Child is Parent {
    function getValue() public override returns (string memory) {
        return "Hello from Child";
    }
}

medium

A. Compilation error due to missing function body in Parent

B. "Hello from Parent"

C. "Hello from Child"

D. Runtime error because Parent is abstract

Solution

1. Step 1: Understand abstract function in Parent

   Parent declares getValue() as abstract (no body), so Child must implement it.

2. Step 2: Check Child's implementation

   Child overrides getValue() and returns "Hello from Child" string.

3. Final Answer:

   "Hello from Child" -> Option C

4. Quick Check:

   Child's override runs = "Hello from Child" [OK]

Hint: Child must implement abstract functions; output from child method [OK]

Common Mistakes:

• Expecting Parent's abstract function to run
• Thinking abstract contracts cause runtime errors
• Confusing compilation errors with runtime errors

4.

Identify the error in this Solidity code snippet:

abstract contract Base {
    function doSomething() public virtual;
}

contract Derived is Base {
    // Missing implementation of doSomething
}

medium

A. Derived contract must implement doSomething() or be declared abstract

B. Base contract should not have virtual functions

C. Derived contract cannot inherit from abstract contracts

D. doSomething() must have a function body in Base

Solution

1. Step 1: Check abstract function in Base

   doSomething() is abstract (no body), so Derived must implement it or be abstract.

2. Step 2: Analyze Derived contract

   Derived does not implement doSomething() and is not abstract, causing error.

3. Final Answer:

   Derived contract must implement doSomething() or be declared abstract -> Option A

4. Quick Check:

   Abstract functions require implementation in non-abstract children [OK]

Hint: Non-abstract child must implement all abstract functions [OK]

Common Mistakes:

• Assuming virtual means implemented
• Forgetting to mark Derived as abstract if no implementation
• Thinking abstract contracts can be instantiated

5.

You want to create a contract system where multiple child contracts share a common function signature but implement it differently. How should you design the parent contract?

hard

A. Use an interface with implemented functions

B. Use a regular contract with fully implemented functions

C. Use a library instead of a contract

D. Use an abstract contract with the function declared as virtual and no body

Solution

1. Step 1: Understand shared function signature need

   Multiple children must share function names but implement differently.

2. Step 2: Choose abstract contract design

   Abstract contracts declare functions without bodies, forcing children to implement them.

3. Step 3: Exclude other options

   Regular contracts have implementations, libraries can't enforce function signatures, interfaces can't have implementations.

4. Final Answer:

   Use an abstract contract with the function declared as virtual and no body -> Option D

5. Quick Check:

   Abstract contract enforces function signature for children [OK]

Hint: Abstract contracts enforce shared function signatures [OK]

Common Mistakes:

• Using regular contracts which fix implementation
• Confusing interfaces with implemented functions
• Trying to use libraries for function enforcement