Technical considerations for Blockchain networks with AWS

Technical considerations for blockchain
networks with AWS

José Ángel Corral,
Líder Técnico de Arquitectura de
Soluciones en atSistemas, y
Responsable Técnico del área
Blockchain
Organizador de:
Internet de las Cosas, un mundo conectado

Index
Blockchain services at AWS
• Amazon Quantum Ledger Database
• Amazon Managed Blockchain
BaaS
Custom Deployment

• Need for a ledger with centralized trust
• Need for a ledger with decentralized trust

Need for a ledger with centralized trust
DMV
Track vehicle
title history
Manufacturers
Track distribution of a
recalled product
Healthcare
Verify and track hospital
equipment inventory
LEDGERS WITH
CENTRALIZED TRUST
1

Need for a ledger with decentralized trust
2
Financial
institutions
Peer-to-peer payments
Mortgage
lenders
Process syndicated
loans
Supply Chain
Transact with suppliers
and distributers
TRANSACTIONS WITH DECENTRALIZED
TRUST

Amazon Quantum Ledger
Database (QLDB)
Amazon Managed
Blockchain

Fully managed ledger database with a
central trusted authority
Amazon Quantum Ledger Database (QLDB)

Challenges customers face
Building Ledgers with traditional databases
Difficult to
manage and scale
Impossible
to verify
Error prone and
incomplete
Resource
intensive
Blockchain approaches
Designed for a
different purpose
Adds unnecessary
complexity

Amazon Quantum Ledger Database (QLDB)
Maintains a sequenced record
of all changes to your data,
which cannot be deleted or
modified; you have the ability
to query and analyze the full
history
Immutable
Uses cryptography to generate
a secure output file of your
data’s history
Cryptographically verifiable
Easy to use, letting you
use familiar database
capabilities like SQL APIs for
querying the data
Easy to useHighly scalable
Executes 2–3X as
many transactions as
ledgers in common
blockchain frameworks
u Fully managed ledger database
u Track and verify history of all changes made to your application’s data

Amazon Managed Blockchain
Fully managed blockchain service, supporting both
Hyperledger Fabric and Ethereum frameworks

Blockchain builds trust in a network
Eliminates the need for central authority in business networks
Three main components: distributed ledger, consensus mechanism,
and “smart contract” execution environment
Together these elements allow two parties to transact with one another by ensuring other parties consent to
the transaction and record the transaction. This provides immutability and trust

Challenges with existing blockchain solutions
Complicated to
manage
Setup is hard Hard to scale Expensive

Amazon Managed Blockchain
Quickly create blockchain networks
that span multiple AWS accounts.
Easily add or remove members and
monitor the network
Fully managed Choice of Hyperledger
Fabric or Ethereum
Improves reliabilityScalable and secure
Easily scale your blockchain
network as the usage grows. Also,
Managed Blockchain secures your
network certificates with KMS
Choose the right framework for
your needs, whether you are
building a permissioned or public
network
Managed Blockchain improves the
reliability of the “ordering service,”
by replacing the default technology
with QLDB. This improves
durability
u Easily create and manage scalable blockchain networks

How Amazon Managed Blockchain works
Amazon Managed
Blockchain
Create a network
Choose an open source
blockchain framework, set up a
new blockchain network and
your membership in your AWS
account with
just a few clicks
Invite members
Invite other AWS accounts to
join the network
Add nodes
Create and configure blockchain
peer nodes that store a copy of
the distributed ledger
Deploy applications
Create and deploy decentralized
applications
to your network through your
per nodes. Transact with other
members on
the network

BaaS (Blockchain as a Service)

Custom Deployment (Ethereum)
Nodes:
• bootnode
• miner/sealer
• worker
Consensus Protocol: PoW -> PoA
Hardware:
EC2 t2.micro 8Gb / SO Linux Amazon

Custom Deployment (Process)
Software:
• Golang
• Git
• Go-ethereum

Security Group (inbound):
• 22: SSH
• 8545: RPC TCP
• 8546: RPC WebSocket
• 30301: UDP
• 30303: TCP

geth --datadir /var/data account new
puppeth -> genesis.json
geth --datadir /var/data init ./genesis.json
bootnode --genkey=boot.key
bootnode --nodekey=boot.key -> enode

Sealer
sudo ./build/bin/geth --cache=512 --datadir=/var/data --rpc --
mine --unlock ”0xXX" --password "pass.txt" --bootnodes
enode://XXX@IP:30301
Worker
sudo ./build/bin/geth --cache=512 --datadir=/var/data --rpc
--bootnodes enode://XXX@IP:30301

Custom Deployment
Despliegue de una red blockchain privada en tecnología
Ethereum sobre AWS
Enmilocalfunciona.io

And now, what?
Smart Contracts/Chaincodes
• Development: Solidity/Java/Golang/Nodejs
• Patterns: (OpenZeppelin)
• Compiling and testing: truffle, mocha y chai.js
• Vulnerabilities: Porosity
Middleware: Interaction with SCs using java (web3j), js(web3js) or go
(go-ethereum)
Connection with the nodes: IPC, HTTP or WebSocket
DApp: React/Vue/Angular (web3js) Ej: Metamask (Wallet)

atCoin - Metamask (1/3)
Browser extension to manage your accounts (wallet) and
merging the gap between different blockchain networks
Extension for accessing
Ethereum enabled distributed
applications, or "Dapps" in your
browser! (Chrome, FF, Opera y
Brave)
App iOS y Android en beta

Connection to ‘ATCOIN’ Network (Alastria Node or Private
Network) → customized RPC

Adding a customized token.
Paste the ERC20 Token Contract Address and
automatically symbol and precission are completed.

atCoin - Metamask (Login)
MetaMask is more than an
Ethereum wallet.
Injects the Ethereum web3
API into every website's
javascript context, so that
Dapps can read from the
blockchain.
For example, to login using
our own signature.

atCoin - Metamask (Transferencias)

Technical considerations for Blockchain networks with AWS

More Related Content

What's hot

Similar to Technical considerations for Blockchain networks with AWS

More from atSistemas

Recently uploaded

Technical considerations for Blockchain networks with AWS