Blockchain and transactions

EN source master · P01-L01 · 30 minutes estimated · needs_review

Read-only study. No wallet connection, real money, seed phrase, private key, signature or live trade. Duration is an editorial estimate; visual assets are specifications, not deployed components.

A screenshot saying ‘sent’ can describe an application action rather than an accepted ledger event. Research starts by deciding which claim the available record can actually answer.

A ledger is a scoped record

A blockchain orders records according to a network's validation and consensus rules. Validation checks whether a record follows the network rules; consensus determines which valid history the network accepts. A transaction proposes changes; broadcast is not the same as inclusion. Bitcoin records spending of previously unspent transaction outputs (UTXOs), which are amounts created by earlier transactions, while Ethereum transactions carry signed instructions. These are different accounting models [BTC, TX]. This lesson uses a deliberately simplified fictional ledger to practice the distinction, not to imitate either network's full format.

Ask a smaller question

‘Did transfer T appear in block B on network N?’ can be answered by an appropriately sourced record. ‘Did the person Alice pay Bob for goods?’ adds several claims: who controls each address, whether the transfer was a payment and what agreement existed. None follows merely from an address pair. A familiar name beside an address is an annotation until its basis is established.

Keep the transaction identifier, network and record context together. A hash copied without its network may lead to an irrelevant lookup. A block height alone may not uniquely identify a block during a fork. A screenshot may omit both, leaving only a claim about what a screen displayed.

Separate stages

Use three columns: submitted, included, and interpreted. A node accepting a request tells you something about that node at that time. A preserved inclusion record adds ledger context. A story about why the transaction occurred belongs in a separately justified interpretation column. Do not silently fill a missing stage because a later screenshot looks plausible.

The lesson's four evidence states apply to a particular claim. OBSERVED means directly visible in the supplied record. INFERRED means a conclusion with stated assumptions. UNKNOWN marks an unavailable fact. INSUFFICIENT EVIDENCE answers a tested claim that the material cannot establish. In a fictional exercise, OBSERVED is always scoped to the exercise, never to a real chain.

Build a reproducible sentence

Use the pattern: ‘In record R, network N shows event E at context C; identity and purpose are not established.’ Another reader should be able to find R and check E. If the record only shows a request, replace ‘shows event’ with ‘reports submission’. Precision is more useful than confident language.

• Ledger: network records and state governed by validation rules.
• Hash: a cryptographic fingerprint used to identify a record; it does not identify a human.
• Transaction: proposed instruction or spending record.
• Inclusion: appearance in a specified block.
• Attribution: connecting an account role to an entity.

ILLUSTRATIVE conceptual cards, not blockchain captures. R1: SIM-NET, SIM-TX-A submitted at T0. R2: same SIM-TX-A included in SIM-BLOCK-40 at T1, transferring 7 SIM units from ACCOUNT-A to ACCOUNT-B. R3: an unverified caption calls ACCOUNT-A ‘Alice’. T0/T1 are fictional order markers.

Transaction timeline: R1 at T0, R2 at T1; separate R3 caption lane with no ownership edge. Caption: Fictional stages, no human attribution. Alt: submission precedes stipulated inclusion; a name label is unverified.

The supplied cards distinguish a request from an included movement.

A real-chain event, beneficial ownership, intent, delivery of goods or asset safety.

• Treating ‘submitted’ as settled.
• Repeating an explorer label as a verified person.
• Writing a commercial story from a transfer alone.

Make a three-row evidence table for submission, inclusion and human identity. Then assess the sentence ‘Alice bought goods from Bob’. Name two missing facts and rewrite the sentence.

Submit a short evidence table and reasoning, using only the provided material. Suggested allocation: study 12 min, inspection/calculation 8 min, correction/quiz 10 min.

• Name the network and full record locator.
• Identify which stage is actually shown.
• Separate address roles from people.
• Attach limits to the finding.

A screenshot saying ‘sent’ can describe an application action rather than an accepted ledger event. Research starts by deciding which claim the available record can actually answer. The supplied material supports the supplied cards distinguish a request from an included movement. It does not establish a real-chain event, beneficial ownership, intent, delivery of goods or asset safety.

• Separate submission, inclusion and interpretation.
• Write a ledger statement without inventing a person.

P01-L02 after reviewing this exercise and its prerequisites.

NONE. The authoritative catalog requires no product access for this lesson. Use the frozen/offline material.

• [BTC] Bitcoin developer guide — Block chain — Valid blocks, UTXOs, work and forks; not historical fixture authentication. Checked 2026-10-01.
• [TX] Ethereum transactions — Signed instructions and execution; inclusion differs from broadcast. Checked 2026-10-01.

Synthetic values are author-created exercise inputs. Historical values, if any, must use the linked dataset and its narrower provenance. Source inspection is not independent editorial acceptance.