BLEPM study plan

Explain how hash functions, Merkle trees, and digital signatures combine to make ledger records tamper-evident, using a hand-drawn example

Distinguish public, permissioned, and consortium ledgers by naming who may read, write, and validate

Compare the trust and failure assumptions of a distributed ledger against a centralized database in a written paragraph

Define the terms block, transaction, node, state, and finality without notes

Map the reference architecture layers (membership, ordering, ledger, peer, chaincode) of a permissioned enterprise platform to their responsibilities

Contrast the runtime models of at least two enterprise platforms on identity, state storage, and transaction lifecycle

Trace a single transaction through endorsement, ordering, and commit, labeling each component it touches

Select a platform for a stated business scenario and justify the choice in writing

Explain crash-fault-tolerant versus Byzantine-fault-tolerant consensus and state the fault tolerance each provides for a given node count

Describe ordering service behavior and what finality means for a committed transaction

Write a small smart contract or chaincode function that enforces an access check and emits an event

Identify common contract vulnerabilities such as reentrancy, unchecked returns, and timestamp dependence in code samples

Explain deterministic execution requirements and why nondeterminism breaks endorsement

Decompose a business process into steps and mark which steps gain traceability, disintermediation, or shared truth from a ledger

Quantify a baseline process cost and estimate the post-ledger delta for one scenario

Identify three processes where a ledger adds no value and articulate why

Draft as-is and to-be process maps for one supply-chain or trade-finance scenario

Design a permissioning model with organizations, roles, and endorsement policies for a multi-party network

Explain how certificate authorities, enrollment, and revocation work across a member lifecycle

Distinguish privacy techniques such as private data collections, zero-knowledge proofs, and channel isolation by their trust assumptions

Map data-protection obligations to ledger design choices, including what must never be written on-chain

Threat-model a network and rank at least five attack vectors by likelihood and impact

Design an integration pattern that connects a legacy system of record to a ledger using events, APIs, or an oracle

Explain how to handle the boundary between an off-chain database and on-chain state, including reconciliation

Compare interoperability approaches such as cross-network protocols, relays, and asset bridging by trust model

Specify idempotency, retry, and failure-recovery behavior for a ledger write triggered by a legacy event

Summarize the regulatory themes that touch enterprise ledgers, including data protection, financial recordkeeping, and digital-asset treatment, and flag where local counsel is required

Draft network governance rules covering membership admission, voting, upgrade approval, and dispute resolution

Explain how consortium governance differs from single-organization governance in decision rights

Produce a compliance checklist that maps obligations to concrete network controls

Build a phased implementation roadmap covering pilot, production, and operations with named owners and exit criteria

Define operating metrics such as transaction throughput, endorsement latency, and node availability with target thresholds

Rehearse a timed mixed-domain question set and log every miss by domain

Review weak domains from your error log and close the top three gaps