Inside this simulator
Foundational mechanics, made tangible. Assemble blocks, watch a hash change when a single character of input changes, follow how consensus resolves competing chains, and see why confirmation depth is a probabilistic statement rather than a switch that flips.
What you'll do
- Hash arbitrary input and observe the avalanche effect
- Build blocks and see how tampering invalidates every subsequent block
- Follow a fork resolving under proof-of-work consensus
- Relate confirmation count to settlement confidence
Skills you'll evidence
- Explaining immutability in terms a client understands
- Answering 'can the transaction be reversed' accurately
- Distinguishing the ledger from the asset from the wallet
Who it's for
Advisors who want the mechanical grounding before the portfolio, tax, and custody material.
Common questions
- Do advisors really need to understand hashing?
- Not at an engineering level — but the single most common client question is whether a transaction can be undone, and answering that credibly requires knowing why a chain of hashes makes rewriting history expensive rather than impossible.
- How many confirmations is enough?
- It depends on the value at risk and the chain. The point of the exercise is that confirmation depth expresses a probability of reversal, so the right number is a risk decision rather than a fixed convention.