CBCP Smart Contracts and dApps 4

Question 1

What is the 'ABI' (Application Binary Interface) in the context of Ethereum smart contracts?

Accepted Answer

A JSON description of a contract's functions and events used to encode/decode interactions

Answer

The ABI is a JSON specification that defines how to encode function calls and decode return values when interacting with a deployed smart contract.

Question 2

In Solidity, what is the difference between 'storage' and 'memory' variable locations?

Accepted Answer

Storage is permanent and persists on-chain; memory is temporary and exists only during execution

Answer

Storage variables are written to the blockchain and persist between transactions, while memory variables are temporary and discarded after function execution ends.

Question 3

What distinguishes a 'pure' function from a 'view' function in Solidity?

Accepted Answer

Pure functions neither read nor modify state; view functions can read but not modify state

Answer

A pure function promises to neither read nor write contract state, while a view function may read state but not modify it.

Question 4

Which attack vector exploits a smart contract that uses block.timestamp for randomness or time-sensitive logic?

Accepted Answer

Timestamp manipulation by miners within a small window

Answer

Miners can adjust block.timestamp by a few seconds, making it an unreliable source of randomness or precise time measurement in smart contracts.

Question 5

What is 'tokenomics' in the context of DApp design?

Accepted Answer

The economic model governing a token's supply, distribution, incentives, and utility within an ecosystem

Answer

Tokenomics describes the economic design of a token system including total supply, emission schedule, staking rewards, and incentive structures that drive participant behavior.

CBCP - Certified Blockchain Professional Practice Test

CBCP - Certified Blockchain Professional Practice Test

CBCP Smart Contracts and dApps 4