The conversation every parent dreads - how to talk to your kids about the blockchain
summary
Focuses on B2B use cases and gives concrete criteria: avoid swapping a central DB for a blockchain, require a consortium with direct node access, and never store PII on-chain. Shows three working prototypes: Webjet’s reconciliation system turned into a shared smart-contract booking ledger (productized as a reservation chain) that cuts reconciliations, a Blacktown City Council pilot using IPFS + Ethereum for plans and approvals with each agency running nodes (built in four days), and a Minecraft demo using ERC-721 land tokens, Azure Functions and a server mod to enforce on-chain ownership (also built in four days).
AI-written summary · about
chapters (31)
- 0:00Intro
- 1:20Agenda
- 2:12When were you doing a blockchain
- 2:42Why would we do this now
- 4:30What is the blockchain
- 5:02Trusting the blockchain
- 5:34Common use cases
- 6:00Public private key cryptography
- 7:30Hashing
- 8:17attestation
- 10:09provenance
- 11:16asset ownership
- 15:14smart contracts
- 16:58Ethereum interfaces
- 19:04Token ownership matters
- 19:59Blockchain patterns
- 20:37Antipattern
- 22:42Red flags
- 27:43Key pillars
- 29:59Medical data
- 33:12Medical scenario
- 33:56Webjet example
- 40:03Partners
- 41:25IPFS
- 49:36Architecture
- 50:23Minecraft
- 51:14Problems
- 52:06What a player would do
- 53:53How the server works
- 55:11Architecture slide
- 56:32Recap
related talks
01h 02mBlockchain is Cyberpunk
51mDemystifying Blockchain: Infrastructures, Smart Contracts & Apps
30mPlatform & Scalability Ⅰ
04mRebuilding trust through blockchains and open source
01h 07mBlockchain for Developer - What's behind the hype?
40mBlockchain and smart contracts explained (and simplified)
01h 07mBlockchain for Developer - What's behind the hype?
40mWhy you don't see Blockchain in your Everyday Life…yet
