Access control with OpenZeppelin in Blockchain / Solidity - Step-by-Step Execution

Concept Flow - Access control with OpenZeppelin

Contract starts

↓

Import AccessControl

↓

Define roles as bytes32

↓

Assign roles in constructor

↓

Function called

↓

Check if caller has role

↓

Execute

↓

End function

This flow shows how a contract imports OpenZeppelin's AccessControl, defines roles, assigns them, and checks roles before running functions.

Execution Sample

Blockchain / Solidity

import "@openzeppelin/contracts/access/AccessControl.sol";

contract MyContract is AccessControl {
    bytes32 public constant ADMIN_ROLE = keccak256("ADMIN_ROLE");

    constructor() {
        _grantRole(ADMIN_ROLE, msg.sender);
    }

    function adminFunction() public onlyRole(ADMIN_ROLE) {
        // admin-only logic
    }
}

This contract sets up an ADMIN_ROLE and restricts adminFunction to callers with that role.

Execution Table

Step	Action	Role Checked	Caller	Has Role?	Result
1	Contract deployed	ADMIN_ROLE	Deployer	Yes	Assign ADMIN_ROLE to deployer
2	Call adminFunction	ADMIN_ROLE	Deployer	Yes	Function executes
3	Call adminFunction	ADMIN_ROLE	Other user	No	Revert: AccessControl: account is missing role

💡 Execution stops when caller lacks required role and function reverts

Variable Tracker

Variable	Start	After Deployment	After Call 2	After Call 3
roles[ADMIN_ROLE][Deployer]	false	true	true	true
roles[ADMIN_ROLE][Other user]	false	false	false	false

Key Moments - 2 Insights

Why does the function revert when called by a user without the ADMIN_ROLE?

Because the execution_table row 3 shows the role check fails (Has Role? = No), so AccessControl reverts the call to prevent unauthorized access.

How is the ADMIN_ROLE assigned to the deployer?

Row 1 in execution_table shows that during deployment, _grantRole assigns ADMIN_ROLE to the deployer, setting roles[ADMIN_ROLE][Deployer] to true.

Visual Quiz - 3 Questions

Look at the execution_table, what happens at step 2 when the deployer calls adminFunction?

A The function reverts because the deployer lacks ADMIN_ROLE

B Nothing happens, the call is ignored

C The function executes because the deployer has ADMIN_ROLE

D The function executes but with limited permissions

💡 Hint

Check execution_table row 2 where Has Role? is Yes and Result is Function executes

At which step does the contract assign ADMIN_ROLE to the deployer?

A Step 1

B Step 2

C Step 3

D Never assigned

💡 Hint

Look at execution_table row 1 where Result says Assign ADMIN_ROLE to deployer

If we call adminFunction from a user without ADMIN_ROLE, what will the roles mapping show for that user?

A true

B false

C undefined

D null

💡 Hint

See variable_tracker row for roles[ADMIN_ROLE][Other user] which remains false

Concept Snapshot

AccessControl from OpenZeppelin manages roles.
Define roles as bytes32 constants.
Assign roles with _grantRole.
Use onlyRole modifier to restrict functions.
Calls revert if caller lacks role.
Secure and simple role-based access.

Full Transcript

This example shows how to use OpenZeppelin's AccessControl in Solidity. First, the contract imports AccessControl and defines a role ADMIN_ROLE as a bytes32 hash. In the constructor, the deployer is given the ADMIN_ROLE using _grantRole. When adminFunction is called, the onlyRole modifier checks if the caller has ADMIN_ROLE. If yes, the function runs; if no, the call reverts with an error. The execution table traces deployment and calls, showing role assignments and checks. The variable tracker shows how roles mapping changes. Key moments clarify why calls revert without roles and how roles are assigned. The quiz tests understanding of role checks and assignments. This pattern helps secure smart contracts by controlling who can call sensitive functions.

Practice

1. What is the main purpose of using onlyRole modifier in OpenZeppelin's Access Control?

easy

A. To restrict function access to accounts with a specific role

B. To automatically assign roles to all users

C. To allow anyone to call the function without restrictions

D. To log all function calls for auditing

Solution

1. Step 1: Understand the purpose of onlyRole

   The onlyRole modifier is used to limit access to functions so only users with a certain role can execute them.

2. Step 2: Analyze the options

   To restrict function access to accounts with a specific role correctly states that it restricts function access to accounts with a specific role. Other options describe unrelated behaviors.

3. Final Answer:

   To restrict function access to accounts with a specific role -> Option A

4. Quick Check:

   Access control = restrict by role [OK]

Hint: Remember: onlyRole means only users with that role can call [OK]

Common Mistakes:

• Thinking onlyRole assigns roles automatically
• Believing onlyRole allows open access
• Confusing onlyRole with event logging

2. Which of the following is the correct way to declare a role constant in OpenZeppelin Access Control?

easy

A. address constant ADMIN_ROLE = 0x123;

B. string public ADMIN_ROLE = "ADMIN_ROLE";

C. uint256 constant ADMIN_ROLE = 1;

D. bytes32 public constant ADMIN_ROLE = keccak256("ADMIN_ROLE");

Solution

1. Step 1: Recall role declaration syntax

   OpenZeppelin uses bytes32 constants with keccak256 hash of a string to define roles.

2. Step 2: Check each option

   bytes32 public constant ADMIN_ROLE = keccak256("ADMIN_ROLE"); matches the correct pattern. Options B, C, and D use wrong types or formats.

3. Final Answer:

   bytes32 public constant ADMIN_ROLE = keccak256("ADMIN_ROLE"); -> Option D

4. Quick Check:

   Role constants use bytes32 + keccak256 [OK]

Hint: Roles are bytes32 constants hashed with keccak256 [OK]

Common Mistakes:

• Using string instead of bytes32 for roles
• Assigning numeric or address types to roles
• Forgetting to use keccak256 hash

3. Given the following Solidity code snippet, what will happen if an account without the ADMIN_ROLE calls secureFunction()?

contract MyContract is AccessControl {
    bytes32 public constant ADMIN_ROLE = keccak256("ADMIN_ROLE");

    constructor() {
        _grantRole(ADMIN_ROLE, msg.sender);
    }

    function secureFunction() public onlyRole(ADMIN_ROLE) {
        // critical logic
    }
}

medium

A. The function executes normally

B. The call reverts with an access control error

C. The function executes but emits a warning

D. The function executes only if the caller is the contract owner

Solution

1. Step 1: Understand the onlyRole modifier behavior

   The onlyRole(ADMIN_ROLE) modifier restricts access to accounts with ADMIN_ROLE. If the caller lacks this role, the call reverts.

2. Step 2: Analyze the scenario

   The constructor grants ADMIN_ROLE only to msg.sender at deployment. Any other account calling secureFunction will trigger a revert due to missing role.

3. Final Answer:

   The call reverts with an access control error -> Option B

4. Quick Check:

   Missing role causes revert [OK]

Hint: Only accounts with role can call; others revert [OK]

Common Mistakes:

• Assuming function runs without role
• Thinking warnings are emitted instead of revert
• Confusing role with ownership

4. Identify the error in this OpenZeppelin Access Control code snippet:

contract MyContract is AccessControl {
    bytes32 public constant ADMIN_ROLE = keccak256("ADMIN_ROLE");

    constructor() {
        _grantRole(ADMIN_ROLE, msg.sender);
    }

    function restricted() public onlyRole(ADMIN_ROLE) {
        // restricted logic
    }

    function grantAdmin(address user) public {
        _grantRole(ADMIN_ROLE, user);
    }
}

medium

A. The grantAdmin function lacks access control and can be called by anyone

B. The _setupRole function is deprecated and should not be used

C. The onlyRole modifier is missing from grantAdmin

D. The ADMIN_ROLE constant is incorrectly declared

Solution

1. Step 1: Review access control on grantAdmin

   The grantAdmin function calls _grantRole but has no modifier restricting who can call it.

2. Step 2: Identify security risk

   Without access control, anyone can call grantAdmin and assign ADMIN_ROLE to themselves or others, breaking security.

3. Final Answer:

   The grantAdmin function lacks access control and can be called by anyone -> Option A

4. Quick Check:

   Grant functions need access control [OK]

Hint: Always protect grantRole functions with onlyRole [OK]

Common Mistakes:

• Ignoring missing access control on grant functions
• Thinking _grantRole is protected like grantRole
• Confusing role declaration syntax

5. You want to create a smart contract where only users with the MINTER_ROLE can mint tokens, and only the contract owner can assign the MINTER_ROLE. Which OpenZeppelin pattern correctly enforces this?

hard

A. Use Ownable and allow only the owner to mint tokens directly without roles

B. Use AccessControl but allow anyone to assign MINTER_ROLE to themselves

C. Use AccessControl with MINTER_ROLE and add onlyRole(DEFAULT_ADMIN_ROLE) modifier to the role assignment function, granting DEFAULT_ADMIN_ROLE to the owner

D. Use AccessControl and assign MINTER_ROLE to everyone by default

Solution

1. Step 1: Understand role assignment control

   To restrict who can assign MINTER_ROLE, use AccessControl's DEFAULT_ADMIN_ROLE for admin rights and protect assignment functions with onlyRole(DEFAULT_ADMIN_ROLE).

2. Step 2: Connect owner with DEFAULT_ADMIN_ROLE

   Grant DEFAULT_ADMIN_ROLE to the contract owner so only they can assign MINTER_ROLE to others.

3. Final Answer:

   Use AccessControl with MINTER_ROLE and add onlyRole(DEFAULT_ADMIN_ROLE) modifier to the role assignment function, granting DEFAULT_ADMIN_ROLE to the owner -> Option C

4. Quick Check:

   Admin role controls role assignment [OK]

Hint: Use DEFAULT_ADMIN_ROLE for owner to control role assignments [OK]

Common Mistakes:

• Allowing anyone to assign roles
• Using Ownable without roles for minting
• Assigning roles to everyone by default