This document introduces Chainstack, a blockchain as a service platform that allows users to rapidly build, deploy, and manage decentralized networks. It discusses key considerations for choosing a blockchain platform such as supported protocols, deployment options, costs, and ease of use. Chainstack offers flexibility in protocols (Fabric, MultiChain, Quorum, Ethereum, Corda), deployment locations (public cloud, on-premises, hybrid), and aims to simplify complex processes like node deployment and synchronization through its user interface and synchronization technology.

1. How to build your blockchain
project with Chainstack
Jona Smulders Cohen
Product Manager
Alex Khaerov
Development Lead

2. 2
Do you really need a
blockchain?

3. 3
Do you really need a blockchain?
Can you articulate a
real problem?
Do you need a
database?
Do many people need
to write to it?
You might need a blockchain
YES
YES
YES
Do all writers trust
each other?
NO

4. 4
What kind of blockchain do you need?
Do you 1) need to control
read and write access and
2) require highly efficient
transactions?
YES
Public
Permissionless
e.g. Ethereum
Permissioned
e.g. Quorum
Access: Trusted members need
permission to join.
Confidentiality: Read/write access can
be limited amongst different members.
Efficiency: Generally higher efficiency in
transactions.
Trust: Requires some level of trust, so
more efficient because less stringent
consensus
NO
Access: Anyone can join.
Confidentiality: Anyone can read
and write.
Efficiency: Can suffer from low
efficiency of transactions.
Trust: No trust required between
members

5. 5
Building your blockchain project
Public
Permissionless/
Permissioned?
Network
Protocol
Node
Deployment
Read & write access
Transparency
Immutability
Efficiency
Num. parties involved in
consensus

6. 6
Selecting a protocol

7. 7
Selecting a protocol
Maturity
Is it battle tested by thousands of
users or is it experimental?
Does it have solid backing?
Will you encounter stability
issues?
Community
How widely adopted?
Is there a large and active
support network available to:
troubleshoot issues?
develop it further?
Complexity
Is it challenging to build with?
Does it require specific domain
expertise to work with?
Roadmap
What are the plans for the future?
What direction are they heading?
How is it going to change?
Documentation
How extensively documented?
Can you build exclusively based
off of documentation or are you
going to end up trawling forums
for answers?
6 things to consider
Consensus
How do participants reach
agreement on the state of the
ledger?
Efficiency: how does the design
impact the efficiency of
transactions?

8. 8
Comparing protocols
Quorum
Backed by JPMorgan Chase & Co.
Fork of Ethereum, makes use of smart
contracts.
Allows nodes to send encrypted
messages to each other.
Corda
Backed by R3.
Enterprise platform initially built for
financial services industry.
Useful for situations where transaction
privacy is key.
Has smart contract scripting functionality
with legal phrasing built in.
MultiChain
Fork of Bitcoin Core, adapted for
permissioned blockchains.
Stable and simple way to store data
without smart contracts.
Supports confidentiality of transactions.
Hyperledger Fabric
Founded by Linux Foundation. IBM, Intel,
SAP, CISCO, Daimler, AmEx backing
Flexible, with pluggable consensus and
membership.
Channel technology for confidential
transactions.
Ethereum
Go-to for decentralized applications that
prioritizes publicly-verifiable transactions.
Supports a smart contract application
layer.
Suffers from low transactions/sec. (for
now)
PublicPermissioned
Permissioned Permissioned Permissioned
Permissioned

9. 9
Protocol design
1. Consensus Mechanism
How does the network reach
consensus?
2. Scalability, speed and efficiency
Does it require a lot of computation? If
the network increases, will it slow
dramatically?
3. Privacy
How much access does each node
have to view the contents of a
transaction?
Participant A Participant BNotary Node A Node CNode B
Participant A Participant BNotary
Participant DParticipant C Notary
Node A Node CNode B
Node D Node FNode E
Corda Ethereum

10. 10
Read & write access
Transparency
Immutability
Efficiency
Num. parties involved in
consensus
Building your blockchain project
Public
Permissionless/
Permissioned?
Network
Protocol
Node
Deployment
Consensus
Community
Complexity
Maturity
Roadmap
Documentation

11. 11
Shared/Dedicated?
Shared = cheaper, but could
suffer latency issues, slower
at large volume of requests.
Dedicated = unlimited
access, not sharing
resources with other
applications.
Distributed
If not distributed, you could end
up with a network that
becomes centralized, with a
single point of failure.
Node deployment options
Hybrid or completely on
cloud?
Do you need the control of
on-premises nodes, or can
they all be managed by a
cloud provider?
What do your network
members require?
Geographic location
Deploying nodes closer to
your area of operations
gives you faster response
times.
How is your app designed
and where is your
infrastructure?
!
"

12. 12
Read & write access
Transparency
Immutability
Efficiency
Num. parties involved in
consensus
Building your blockchain project
Public
Permissionless/
Permissioned?
Network
Protocol
Node
Deployment
Consensus
Community
Complexity
Maturity
Roadmap
Documentation
Distributed
Hybrid or completely on
cloud
Cloud provider
Cloud region
Speed
Access and privacy

13. 13
§ Cost of time and resources wasted spent building an unnecessary solution from
the ground up.
§ Lack of planning results in time spent experimenting with different protocols.
§ Complex protocol takes time to get up and running with a functional proof of
concept.
§ Deployments that are hard to maintain will require ongoing time and effort to
keep stable.
§ Cost of investing heavily into one solution when you could be exploring other
opportunities.
§ Privacy issues that arise from choosing the wrong consensus mechanism
§ Inability to scale appropriately.
§ Deploying a network that doesn't support all consortium members’ need.
§ Choosing a protocol with a poorly defined roadmap, little backing and not enough
community support that ends up becoming obsolete or unsupported.
...
Lots of choices with lots of
consequences…
Every choice impacts the
time and money
spent building the right
solution.

14. 14
Introducing Blockchain as a
Service

15. 15
Introducing: Blockchain as a Service
A Platform as a Service that empowers
businesses and developers to rapidly
build, deploy and manage decentralized
networks and services.
Why do you need it?
Reduce the complexity and
challenges involved in working
with blockchains.
Less need for hard-to-find
technical skills.
Security built in from the
start.
Scalable for any
requirements.
Low set up and
maintenance costs.
Extremely short time to
get started managing
networks.

16. 16
Introducing: Blockchain as a Service
Who is it for?
Looking to quickly start prototyping with
blockchains and building their own
DApps.
Enterprise developers
Partners
(ISVs, SIs, ISPs, Consultants)
Independent developers
Interested in offering blockchain solutions
to their clients.
Looking to explore and experiment
blockchain solutions for their companies.
Need a secure platform to scale and
maintain an existing blockchain proof of
concept. Want to deploy dedicated nodes on
public blockchains like Ethereum.

17. 17
1. Which protocols do they support?
2. What deployment options do
they have?
3. How much does it cost and how do
they charge?
4. How easy is it to set up and build
on. (Essential for rapid prototyping)
How to choose the right platform to manage
your blockchain network?

18. 18

19. 19
The Chainstack solution
Developers should be free to leverage the right
protocol for their needs.
Chainstack offers the flexibility to experiment
with multiple protocols, all from a single
dashboard.
Multi-protocol
FabricMultiChainQuorum
EthereumCorda
More
coming
soon

20. 20
You might want your nodes on the public cloud, or
deployed on-prem.
Chainstack gives you the choice to deploy
blockchains where you need them and across
hybrid environments.
Cloud agnostic, hybrid deployment
The Chainstack solution
Google Alibaba
Amazon DigitalOcean
Microsoft
On-Premises

21. 21
The Chainstack solution
Deploying and maintaining
enterprise blockchains doesn’t
have to be a complicated
process.
Chainstack’s UI removes
complexity in deploying and
managing blockchains so that
anyone can do it.
Easy to Use
Managing and getting started with
blockchain can take a long time,
from complex DevOps to
synchronizing nodes.
Chainstack takes care of all of
this, getting you running
smoothly in minutes rather than
hours or days.
Fast
Developing a blockchain network
can be require significant up-front
investment that continues over its
lifetime.
Chainstack’s solution provides a
more cost effective way to build
and manage a network yourself.
Cost-effective

22. 22
Rapid node synchronization
technology

23. 23

24. 24
Node synchronization
made quick and painless
Chainstack’s patented node-
synchronizing technology let’s you
deploy new nodes blazingly fast.
No need to spend hours or even
days deploying and synchronizing
new nodes.
Never worry about interrupted or
failed deployments.
320x faster node deployment
and synchronization
Avg. time to fast sync
a Geth node
34h 18m
6m 23s

25. 25
Demo

26. 26
console.chainstack.com
Multi-cloud, multi-protocol Platform as a Service.
Rapidly build, deploy, and manage decentralized
networks and services.
For enterprises and developers.
TRY IT NOW FOR FREE
@ChainstackHQ
Alex Khaerov
Jona Smulders Cohen