Cryptography-I
Generic cryptography foundations — content in preparation
Cryptography is usually learned as chain-specific trivia instead of as reusable foundations.
Public syllabus
This page answers what Blockchain Mastery contains. BCM follows its own pedagogical order: each chapter exists to remove one specific misunderstanding, in the order an engineer actually needs it. Learning itself is entered through My BCM → Course → Chapter.
Learner can explain foundational Blockchain mechanisms and use basic Blockchain tools safely.
Mentee on-ramp: what BCM is, how the Track works, MIRACLE progression, the DEVISE learning flow, assessments, evidence and support. Content is in preparation.
Identity and learning access are owned by One Great Mentor.
Generic cryptography foundations, deliberately independent of any single chain. Structural placeholders only — content is authored separately.
Identity and learning access are owned by One Great Mentor.
Generic cryptography foundations — content in preparation
Cryptography is usually learned as chain-specific trivia instead of as reusable foundations.
Generic cryptography foundations, part two — content in preparation
Chain-agnostic cryptographic reasoning has to exist before chain-specific application makes sense.
Learner can implement, test, deploy and explain practical Blockchain applications and diagnose common failures.
The Implementer-level foundation course: why Blockchain exists, real public transactions, the engineering problems Bitcoin had to solve, and applied cryptography.
Identity and learning access are owned by One Great Mentor.
The double-spend and shared-truth problem
A group of strangers who do not trust each other, and have no shared clock and no referee, must agree on one history of who paid whom — permanently.
Declared in the BCM sequence and not yet placed into a published Course.
BCM-C06
plannedAgreement Among Untrusted Nodes
Byzantine agreement, proof-of-work and chain selection
BCM-C07
plannedMerkle Trees and Efficient Verification
From leaves to root, and Merkle proofs to SPV
BCM-C08
plannedBitcoin Mechanics
UTXO, script, fees, subsidy and confirmations
BCM-C09
plannedEthereum Architecture
Accounts, state, gas, EVM, proof-of-stake
BCM-C10
plannedSolidity and the EVM
Write, compile, reason about state
BCM-C11
plannedTest, Deploy, Verify
Local VM → tests → Sepolia → verification
BCM-C12
planneddApp Interaction
Web3 libraries, RPC, transfers and contract calls
BCM-C13
plannedPermissioned Blockchain
Hyperledger Fabric: peers, orderers, channels, chaincode, MSP
BCM-C14
plannedAttack Labs
Reentrancy, access control, randomness, oracles, key compromise
BCM-C15
plannedImplementer Capstone
End-to-end: problem → design → contract → tests → Sepolia → evidence
Bitcoin taught as a sequence of engineering problems and the answers the design chose.
Digital cash copies perfectly
Spend outputs, not files
live
Participants cannot be trusted
Independent rule verification by every node
live
Identities are cheap to fake
Weight influence by costly work, not by names
live
No shared clock for ordering
Order by chained, work-backed blocks
coming soon
Competing histories appear
Follow the chain with most cumulative work
coming soon
Why would anyone produce blocks?
Block subsidy plus transaction fees
coming soon
How is supply issued without a central bank?
Scheduled subsidy, halving over time
coming soon
Where do unconfirmed transactions live?
Per-node pending transaction pool
coming soon
How much confidence does inclusion give?
Confirmation depth as probability, not proof
coming soon
Must every user store everything?
Merkle proofs and SPV, with stated trade-offs
coming soon
Hardware speed keeps rising
Difficulty retarget every 2016 blocks
coming soon
Participants join and leave freely
No permanent membership; work is the entry ticket
coming soon