Why Virtual and override keywords in Blockchain / Solidity? - Purpose & Use Cases

The Big Idea

What if you could change parts of your blockchain contract without breaking everything else?

The Scenario

Imagine you are building a blockchain smart contract system where different contracts share some common functions but need to customize certain behaviors. Without special keywords, you have to rewrite entire functions for each contract or risk unexpected results.

The Problem

Manually copying and changing code for each contract is slow and error-prone. If you forget to update one place, your blockchain logic might break or behave inconsistently, causing costly bugs.

The Solution

The virtual keyword lets you mark functions that can be changed later, and override lets you safely replace those functions in child contracts. This makes your code clear, safe, and easy to maintain.

Before vs After

✗ Before

contract Base {
  function calculate() public returns (uint) {
    return 1;
  }
}

contract Child is Base {
  // manually copied and changed calculate()
  function calculate() public returns (uint) {
    return 2;
  }
}

✓ After

contract Base {
  function calculate() public virtual returns (uint) {
    return 1;
  }
}

contract Child is Base {
  function calculate() public override returns (uint) {
    return 2;
  }
}

What It Enables

You can build flexible blockchain contracts that share logic but customize behavior safely and clearly.

Real Life Example

In a blockchain voting system, a base contract defines a voting method, but different elections override the method to apply special rules like weighted votes or time limits.

Key Takeaways

Virtual marks functions that can be changed later.

Override safely replaces those functions in child contracts.

This helps build clear, flexible, and safe blockchain code.