Part V · Evidence and wrap-up

Appendix C · Glossary and self-check

By KangPublished: Chain snapshot: , block 12117419

If you can answer in your own words, you have really understood it.

Glossary

Term In one line
Block / hash A unit of transaction records, and a content “fingerprint”
Node / consensus A computer that independently validates data, and the rules for jointly deciding which history is accepted
Proof of stake (PoS) Ethereum’s consensus: validators stake ETH and propose and attest to blocks by protocol rules
Wallet / private key A signing tool, and the secret that controls an address
Seed phrase A list of words that restores a whole wallet; even more sensitive than one key
Address A public “house number” you can share
Gas / fee The unit of execution work; fee = gasUsed × effective gas price
Base fee / tip The part that is burned, and the part paid to the validator
Nonce An account’s transaction counter, starting at 0 and rising with each mined transaction
Mempool Where transactions wait before being mined; a hash there is not yet a fact
EVM / smart contract The environment that runs on-chain programs, and rule code deployed on-chain
Revert Undoing all state changes of an execution when a check fails; gas is still paid
eth_call / simulation Read-only execution: no signature, no cost, no change to the chain
ERC-20 The common interface standard for fungible tokens
allowance / approve An amount a spender may use, and the function that sets it; not a payment
transferFrom / burnFrom A spender moving or burning tokens within the allowance
Burn Destroying tokens: lowers both a balance and total supply
Atomicity All operations in one transaction take effect together or not at all
Proxy / implementation A stable entrance, and the replaceable logic behind it
ProxyAdmin The only admin contract that can switch a proxy’s implementation
initialize The run-once setup function that replaces the constructor in upgradeable contracts
Storage layout Where state variables sit in storage slots; upgrades may only append, never reorder
Redenomination / scale Changing the unit of account; in UBOX V3, 10,000 old = 1 new
Dust A remainder too small to show after conversion
Unit / fuzz / invariant tests Specific cases / random inputs / properties after any call sequence
Fork / Sepolia A local copy of chain state for simulation / a public testnet
Source verification / exact match / match Proving source compiles to the on-chain bytecode; metadata also matches / only bytecode matches
GUID A queue ID returned after submitting verification, not a success mark
Faucet A service that gives out free test coins

Self-check (try before looking at the answers)

The first 6 questions come from the original study notes; the last 6 come from the experiments this book adds.

  1. If a supplier is happy to fully trust the platform operator, why might it not need a blockchain?

    Show the answer to question 1

    Because everyone already trusts one record-keeper. A central database is simpler, faster, cheaper and better for privacy. A blockchain earns its cost when several parties who do not fully trust each other must keep one shared ledger; without that, it is rarely worth it.

  2. When a wallet signs a transaction, does the private key get sent to miners or validators?

    Show the answer to question 2

    No. The private key stays on your device and is only used to produce a signature. The network receives the signed transaction and checks the signature against public information.

  3. Does approve(100) immediately take 100 tokens from you?

    Show the answer to question 3

    No. approve only records an allowance — the most the spender may move later. Your balance is unchanged until the spender actually calls transferFrom or burnFrom.

  4. Why can the business rules change even though the proxy address stays the same?

    Show the answer to question 4

    The proxy is only a fixed entrance that forwards calls to an implementation contract. The ProxyAdmin owner can point the proxy at a new implementation, so the rules behind the same address change.

  5. If 49/49 unit tests pass, does that mean there are no vulnerabilities?

    Show the answer to question 5

    No. Tests only show that the cases someone wrote down pass. In P0 all 49 unit tests passed, and the review still recorded 1 Medium, 3 Low and 6 Info findings.

  6. V4 passed a fork simulation. Can we say "V4 is deployed on Sepolia"?

    Show the answer to question 6

    No. A fork simulation sends no real transaction and has no transaction hash. At the snapshot the UBOX proxy still pointed to the V3 implementation 0x16E3D2f25e28253b467C66c462973e4ca86fad28.

  7. After 1,000 MBox were sent to an address with no private key, can they be recovered?

    Show the answer to question 7

    No. Confirmed transactions cannot be undone, and without a private key nobody can sign a transfer out. The 1,000 MBox at the demo address 0x878fFf967331D01E97c8DdCD76C3Dd97333BcA6E are locked forever — do not send anything else there.

  8. Two tokens have exactly the same name and symbol. Are they the same token?

    Show the answer to question 8

    Not necessarily. name and symbol are just strings returned by the contract; there is no registry, and anyone can deploy a look-alike. Identify a token by its contract address.

  9. What is the difference between burn and "transfer to address 0x0"?

    Show the answer to question 9

    burn lowers both the holder's balance and totalSupply. A plain transfer to the zero address (if a contract allows it) only moves the balance and does not reduce supply. Read totalSupply(); do not rely on the Transfer event alone.

  10. You call transferFrom in two separate transactions and the second one fails. Is the first one undone?

    Show the answer to question 10

    No. Two separate transactions are not atomic. Only a batch executed inside one transaction (such as UBOX V2 batchTransfer) is "all or nothing".

  11. After the UBOX redenomination, are the old Transfer events rewritten?

    Show the answer to question 11

    No. On-chain logs cannot be rewritten. The old "100 to B" log in the successful batch still says 100e18 in old units; read as new units it would be 10,000 times too large. After the redenomination B's balanceOf is 0.01.

  12. If a transaction fails (reverted), do you still pay a fee?

    Show the answer to question 12

    Yes. A failed transaction still uses a nonce, consumes gas and appears in the explorer; only its state changes are rolled back. The intentionally failing batchTransfer in the lab used 51,719 gas and cost 3,516,892 wei.