Training for Gemeente Leiden at Hubspot Leiden March 14 2018

1. Blockchain Workspace www.blockchainworkspace.com 1
Municipalities and
blockchains: any shared
interest?!
@henkvancann
Feb 12 2018

2. Blockchain Workspace www.blockchainworkspace.com 2
Blockchain - trustworthy proofs
Example SHA-256 HASH:
ca978112ca1bbdcafac231b39a23dc4da786eff8147c4e72b9807785afee48bb
Famous HASH:
000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f
+ =
Repeat of essence of public blockchains:
Encryption {key}
Timestamping and consensus {stamp}
Verification {check}
000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f Genesis block #0 (Jan 3, 2009, 10 leading zeros)
Expert question: What is the accidental part of the blockchain discovery? -> Answer: The (later customized ‘op_return’) data field of a
transaction.

3. Blockchain Workspace www.blockchainworkspace.com 3
Blockchain - Hash calculation
http://www.xorbin.com/tools/sha256-hash-calculator

4. Blockchain Workspace www.blockchainworkspace.com 4
Blockchain - Hash calculation
http://www.xorbin.com/tools/sha256-hash-calculator

5. Blockchain Workspace www.blockchainworkspace.com 5
Blockchain - Hash calculation
http://www.xorbin.com/tools/sha256-hash-calculator

6. Blockchain Workspace www.blockchainworkspace.com 6
Blockchain - Hash calculation
http://www.xorbin.com/tools/sha256-hash-calculator

7. Blockchain Workspace www.blockchainworkspace.com 7
Tip: Understand the inner working of the technology you use

8. Blockchain Workspace www.blockchainworkspace.com 8
Blockchain - trustworthy proofs
000000000000048b95347e83192f69cf0366076336c639f9b7228e9ba171342e
Block 210000 July 2nd 2016 (1Megabyte)
‘a’ (1 character)
ca978112ca1bbdcafac231b39a23dc4da786eff8147c4e72b9807785afee48bb
000000000000048b95347e83192f69cf0366076336c639f9b7228e9ba171342e Block 210000 July 2nd 2016 (starting with 13 zeros)
0000000000000000002f215bdc88c918a39f36002b2237a0f8fd57a9198fae7f Block 513158 (starting with 18 zeros)

9. Blockchain Workspace www.blockchainworkspace.com
1. Trust in IT, bitcoin protocol
2. Divisible units
3. Transfer (TCP/IP)
4. Globally
5. Inter operability
Why Component 1 IT network / Internet?
Serves
Blockchain apps

10. Blockchain Workspace www.blockchainworkspace.com
1. Privacy
2. Control
3. Trust
Why Component 2 Cryptography?
Serves
Blockchain apps

11. Blockchain Workspace www.blockchainworkspace.com
1. Fairness
2. Randomness
3. Mining
4. Anyone can participate and leave
Why Component 3 Gaming theory?
Serves
Blockchain apps

12. Blockchain Workspace www.blockchainworkspace.com
1. Store of value
2. Digital scarcity
3. Get rid of centralised service infusion
4. Reduce traceability
5. Automatic tax collection, fee dispensing etc…
Why 3 Components together are stronger then its parts?
Suddenly possible to
Blockchain apps

13. Blockchain Workspace www.blockchainworkspace.com
1. Existence
2. Status
3. Identity
4. Compliance
5. Location
6. Ownership
7. Purchase
“ESIALOP”
Delivers proofs of…
Blockchain apps

14. Blockchain Workspace www.blockchainworkspace.com
“ATOMIC”
Blockchain touches…
1. Assets
2. Trust
3. Ownership
4. Money
5. Identity
6. Contracts

15. Blockchain Workspace www.blockchainworkspace.com 15
REGULATIONS - privacy, tax, …
David Chaum:
• de slechteriken moeten we perfect kunnen traceren
• alle goede mensen moeten perfect niet-traceerbaar zijn.
AVG en GPDR:
• grote verantwoordelijkheid bij gegevens bijhouder
David Chaum heeft in 2016 als mede-grondlegger van anonimiteit kort opschudding veroorzaakt met Privategrity: een idee om federatie in te stellen die als de nood aan de man komt privé sleutels moet kunnen kraken.
… omdat hij vindt dat :
de slechteriken moeten we perfect kunnen traceren en alle goede mensen moeten perfect niet-traceerbaar zijn.

16. Blockchain Workspace www.blockchainworkspace.com 16
1.shared db,
2.multiple writers,
3.mistrust,
4.disintermediation,
5.interdependent transactions,
6.set rules,
7.validators,
8.asset backing
Eight conditions to avoid senseless blockchain applications -
Nov 2015 article :
1st out of 8 conditions to avoid pointless blockchain projects: Blockchains are a technology for shared databases, do you need one?!
2nd out of 8 conditions to avoid pointless blockchain projects: there needs to be more than one entity which is generating the transactions that modify the database. Do you know who these writers are?
3rd out of 8 conditions to avoid pointless blockchain projects: there also needs to be some degree of mistrust between those entities; it can also exist within a single large organization, for example between departments or the operations in different countries.
4th out of 8 conditions to avoid pointless blockchain projects: disintermediation, is there any good reason to take away (the service of) a middleman?!
5th out of 8 conditions to avoid pointless blockchain projects: Blockchains truly shine where there is some interaction between the transactions created by these writers. Interdependencies wanted!
6th out of 8 conditions to avoid pointless blockchain projects: This isn’t really a condition, but rather an inevitable consequence of the first 5 points: the database must contain embedded rules restricting the transactions performed.
7th out of 8 conditions to avoid pointless blockchain projects: a blockchain’s job is to be the authoritative final transaction log, on whose contents all validators provably agree, do you know them and trust them?
8th out of 8 conditions to avoid pointless blockchain projects: Is there anyone standing behind the assets represented on the blockchain? If the database says that I own 10 units of something, who will allow me to claim those 10 units in the real world?