BTA CBDE study plan

Explain how EOAs, contracts, nonces, and account storage differ, writing the distinctions from memory

Trace a signed transaction from RLP encoding through mempool admission to receipt, listing each validation step

Describe the EVM execution model: stack, memory, calldata, storage, and gas accounting per opcode class

Distinguish execution-layer client roles from consensus-layer duties well enough to explain a full block lifecycle

Set up a local node or fork endpoint and query state with raw JSON-RPC calls (eth_getStorageAt, eth_getCode, eth_call)

Write Solidity contracts using value types, mappings, structs, and arrays, and justify each storage-layout choice

Implement visibility, mutability, and modifier patterns correctly in at least three small contracts

Explain ABI encoding rules for dynamic types and verify an encoding by hand for one function call

Implement inheritance, interfaces, and abstract contracts, and resolve a diamond-inheritance linearization by hand

Apply the checks-effects-interactions pattern and reentrancy guards to a payable withdrawal flow

Use events and custom errors appropriately, and explain when each is cheaper than storage writes

Compare upgrade patterns (proxy storage slots, initializers, storage gaps) and justify one choice in writing

Configure a Hardhat or Foundry project from scratch with compiler settings, networks, and env-based secrets

Write deployment scripts that are idempotent and log addresses per chain

Add a linting and formatting step to the toolchain and fix all reported issues

Produce a gas snapshot and explain the two largest cost drivers in your contracts

Build a frontend that connects a wallet, reads contract state, and submits a transaction with pending, success, and failure states

Handle chain switching, wrong-network, and rejected-signature cases explicitly in the UI

Index contract events off-chain with a script or subgraph and display derived data

Explain how RPC providers, signers, and contract instances relate in the client architecture you built

Write unit and integration tests covering happy paths, revert reasons, and access-control failures

Add fuzz or invariant tests for at least one core invariant and interpret a failing counterexample

Perform a manual security review of your own contracts against the common vulnerability classes (reentrancy, access control, oracle and price assumptions, arithmetic, front-running)

Document trust assumptions and admin powers for each deployed contract

Set up a CI pipeline that compiles, tests, and reports coverage on every push

Verify contract source on a block explorer and confirm the published bytecode matches local builds

Simulate a deployment to a testnet with a scripted rollback and post-deploy verification checklist

Practice incident response: given a seeded bug, locate, patch, retest, and redeploy within a time box

Complete a timed full-length practice set and categorize every miss by domain

Re-teach the two weakest domains from notes without consulting references

Refactor the capstone DApp to close the top three self-audit findings and rerun all tests

Write a one-page summary mapping each exam domain to the artifact that demonstrates your competence in it