Blockchain Technology
Basics
1
Anjum Naveed, PhD (UNSW Australia)
Copyright © 2018 by ITROOS (Pvt.) Ltd
All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic
or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other
noncommercial uses permitted by copyright law. For permission requests, write to the publisher at the address below.
ITROOS
info@itroos.net
www.itroos.net
Topics Covered
Conventional Storage
Issues with conventional storage
Introduction to Blockchain
Blockchain: Addressing the issues
Usecases of Blockchain
Blockchain Application Eco system
2
Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
Conventional Storage
Databases
SQL
noSQL
Files
Structured
Unstructured
Variations
In memory
3
Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
Issues with Conventional Storage
Data Modifications
Who changed what and when?
In general, record of modifications does
not exist
Trust
Since I last accessed my system, has the
data changed or it is same?
No change guarantee does not exist
4
Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
Issues with Conventional Storage
Transparency
Linked to “who changed what?”
Can I trace back all modifications to a
specific record?
How can we achieve such guarantees?
5
Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
Blockchain: Rising from Conventional Data Storage
6
Database/File
Record 1
Record 2
Record 3
.
.
.
.
.
.
.
.
.
Record n
Change Log/Transaction Log on Data Store
Record 1, Name field changed to ABC by Z
Record 4, Make field changed to PDC by Q
.
.
.
.
Record 7, User field changed to XYZ by N
.
.
.
.
.
.
.
.
.
.
Block 1
Block 5
Block 97
Block 997
Technology 1: Maintain Change Log
On the data (Who did What)
Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
Blockchain: Blocks and Chain
7
Change
Log }
Hash
Change log
}Hash
Change
Log
Database/File
Record 1
Record 2
Record 3
.
.
.
.
.
.
.
.
.
Record n
Blocks
Chaining of blocks through hash
Technology 2: Use hashes to ensure the log entries
are not changed (Securing change log)
Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
Blockchain: Computation Power
Single Hash computation time?
(100) microseconds
8 hashes computation time?
8 * (100) microseconds
2^22 hash computation time?
2^22 (100) microseconds ~ 7 minutes
This is average time required to compute the
hash with specific form
0000 0000 0000 0000 0000 00XXXXXXXXXXXXX
8
Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
Blockchain: Computation Power
9
Change log
Nonce
}
Hash
Correct
form? YesNo
New
Nonce
HashTechnology 3: Computation power to
enhance security of change log (Immutability)
Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
Blockchain: Peer Consensus
Save entire chain and
data at every
participating node
Verify before saving,
verify before extending
If one node acts malicious
or is attacked, others will
still have valid copies
If ‘x’ nodes produce
corrupt new blocks, stop
the operation and fix
before resuming
operation
10
Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
Blockchain: Issues addressed
Immutability
Once a block is created out of change
log entries, distributed among peers
and goes a few blocks deep, it is
virtually impossible to change the
entries in block
11
Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
Blockchain: Issues addressed
Immutability
Once a block is created out of change
log entries, distributed among peers
and goes a few blocks deep, it is
virtually impossible to change the
entries in block
Who changed what and when?
??????
12
Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
Blockchain: Issues addressed
Immutability
Once a block is created out of change
log entries, distributed among peers
and goes a few blocks deep, it is
virtually impossible to change the
entries in block
Trust? Can we trust our data? (not the
change log)
??????
13
Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
Blockchain: Issues addressed
Immutability
Once a block is created out of change
log entries, distributed among peers
and goes a few blocks deep, it is
virtually impossible to change the
entries in block
How to achieve transparency?
??????
14
Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
Blockchain:Additional Issues addressed
Verifiability of data
Distributed Computation
Third party elimination
15
Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
Blockchain Application Eco system
16
GUI
Backend
Server
Blockchain
API
Blockchain
Business
Logic
Blockchain
Network
Blockchain
Blockchain
Cryptographic
Support
Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
Next
Blockchain Security
17

01 - Blockchain technology - Basics

  • 1.
    Blockchain Technology Basics 1 Anjum Naveed,PhD (UNSW Australia) Copyright © 2018 by ITROOS (Pvt.) Ltd All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law. For permission requests, write to the publisher at the address below. ITROOS info@itroos.net www.itroos.net
  • 2.
    Topics Covered Conventional Storage Issueswith conventional storage Introduction to Blockchain Blockchain: Addressing the issues Usecases of Blockchain Blockchain Application Eco system 2 Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
  • 3.
  • 4.
    Issues with ConventionalStorage Data Modifications Who changed what and when? In general, record of modifications does not exist Trust Since I last accessed my system, has the data changed or it is same? No change guarantee does not exist 4 Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
  • 5.
    Issues with ConventionalStorage Transparency Linked to “who changed what?” Can I trace back all modifications to a specific record? How can we achieve such guarantees? 5 Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
  • 6.
    Blockchain: Rising fromConventional Data Storage 6 Database/File Record 1 Record 2 Record 3 . . . . . . . . . Record n Change Log/Transaction Log on Data Store Record 1, Name field changed to ABC by Z Record 4, Make field changed to PDC by Q . . . . Record 7, User field changed to XYZ by N . . . . . . . . . . Block 1 Block 5 Block 97 Block 997 Technology 1: Maintain Change Log On the data (Who did What) Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
  • 7.
    Blockchain: Blocks andChain 7 Change Log } Hash Change log }Hash Change Log Database/File Record 1 Record 2 Record 3 . . . . . . . . . Record n Blocks Chaining of blocks through hash Technology 2: Use hashes to ensure the log entries are not changed (Securing change log) Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
  • 8.
    Blockchain: Computation Power SingleHash computation time? (100) microseconds 8 hashes computation time? 8 * (100) microseconds 2^22 hash computation time? 2^22 (100) microseconds ~ 7 minutes This is average time required to compute the hash with specific form 0000 0000 0000 0000 0000 00XXXXXXXXXXXXX 8 Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
  • 9.
    Blockchain: Computation Power 9 Changelog Nonce } Hash Correct form? YesNo New Nonce HashTechnology 3: Computation power to enhance security of change log (Immutability) Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
  • 10.
    Blockchain: Peer Consensus Saveentire chain and data at every participating node Verify before saving, verify before extending If one node acts malicious or is attacked, others will still have valid copies If ‘x’ nodes produce corrupt new blocks, stop the operation and fix before resuming operation 10 Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
  • 11.
    Blockchain: Issues addressed Immutability Oncea block is created out of change log entries, distributed among peers and goes a few blocks deep, it is virtually impossible to change the entries in block 11 Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
  • 12.
    Blockchain: Issues addressed Immutability Oncea block is created out of change log entries, distributed among peers and goes a few blocks deep, it is virtually impossible to change the entries in block Who changed what and when? ?????? 12 Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
  • 13.
    Blockchain: Issues addressed Immutability Oncea block is created out of change log entries, distributed among peers and goes a few blocks deep, it is virtually impossible to change the entries in block Trust? Can we trust our data? (not the change log) ?????? 13 Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
  • 14.
    Blockchain: Issues addressed Immutability Oncea block is created out of change log entries, distributed among peers and goes a few blocks deep, it is virtually impossible to change the entries in block How to achieve transparency? ?????? 14 Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
  • 15.
    Blockchain:Additional Issues addressed Verifiabilityof data Distributed Computation Third party elimination 15 Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
  • 16.
    Blockchain Application Ecosystem 16 GUI Backend Server Blockchain API Blockchain Business Logic Blockchain Network Blockchain Blockchain Cryptographic Support Confidential- ©Copy Rights ITROOS(Pvt) Ltd 2018
  • 17.