bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 7쪽 중 1쪽
POLKADOT: VISION FOR A HETEROGENEOUS MULTI-CHAIN FRAMEWORK
DRAFT 1
DR. GAVIN WOOD
FOUNDER, ETHEREUM & PARITY
GAVIN@PARITY.IO
Abstract. Present-day blockchain architectures all suffer from a number of issues not least practical means of extensi-
bility and scalability. We believe this stems from tying two very important parts of the consensus architecture, namely
canonicality and validity, too closely together. This paper introduces an architecture, the heterogeneous multi-chain,
which fundamentally sets the two apart.
In compartmentalising these two parts, and by keeping the overall functionality provided to an absolute minimum
of security and transport, we introduce practical means of core extensibility in situ. Scalability is addressed through
a divide-and-conquer approach to these two functions, scaling out of its bonded core through the incentivisation of
untrusted public nodes.
The heterogeneous nature of this architecture enables many highly divergent types of consensus systems interop-
erating in a trustless, fully decentralised “federation”, allowing open and closed networks to have trust-free access to
each other.
We put forward a means of providing backwards compatibility with one or more pre-existing networks such as
Ethereum. We believe that such a system provides a useful base-level component in the overall search for a practically
implementable system capable of achieving global-commerce levels of scalability and privacy.
1. Preface
This is intended to be a technical “vision” summary
of one possible direction that may be taken in further de-
veloping the blockchain paradigm together with some ra-
tionale as to why this direction is sensible. It lays out in
as much detail as is possible at this stage of development
a system which may give a concrete improvement on a
number of aspects of blockchain technology.
It is not intended to be a specification, formal or oth-
erwise. It is not intended to be comprehensive nor to be a
final design. It is not intended to cover non-core aspects
of the framework such as APIs, bindings, languages and
usage. This is notably experimental; where parameters
are specified, they are likely to change. Mechanisms will
be added, refined and removed in response to community
ideas and critiques. Large portions of this paper will likely
be revised as experimental evidence and prototyping gives
us information about what will work and what not.
This document includes a core description of the pro-
tocol together with ideas for directions that may be taken
to improve various aspects. It is envisioned that the core
description will be used as the starting point for an initial
series of proofs-of-concept. A final “version 1.0” would be
based around this refined protocol together with the ad-
ditional ideas that become proven and are determined to
be required for the project to reach its goals.
1.1. History.
• 09/10/2016: 0.1.0-proof1
• 20/10/2016: 0.1.0-proof2
• 01/11/2016: 0.1.0-proof3
• 10/11/2016: 0.1.0
2. Introduction
Blockchains have demonstrated great promise of util-
ity over several fields including “Internet of Things”
(IoT), finance, governance, identity management, web-
decentralisation and asset-tracking. However, despite the
technological promise and grand talk, we have yet to see
significant real-world deployment of present technology.
We believe that this is down to five key failures of present
technology stacks:
Scalability: How much resources are spent globally
on processing, bandwidth and storage for the sys-
tem to process a single transaction and how many
transactions can be reasonably processed under
peak conditions?
Isolatability: Can the divergent needs of multiple
parties and applications be addressed to a near-
optimal degree under the same framework?
Developability: How well do the tools work? Do
the APIs address the developers’ needs? Are ed-
ucational materials available? Are the right inte-
grations there?
Governance: Can the network remain flexible to
evolve and adapt over time? Can decisions be
made with sufficient inclusivity, legitimacy and
transparency to provide effective leadership of a
decentralised system?
Applicability: Does the technology actually ad-
dress a burning need on its own? Is other “mid-
dleware” required in order to bridge the gap to
actual applications?
In the present work, we aim to address the first two
issues: scalability and isolatability. That said, we believe
the Polkadot framework can provide meaningful improve-
ments in each of these classes of problems.
Modern, efficient blockchain implementations such as
the Parity Ethereum client [17] can process in excess of
3,000 transactions per second when running on perfor-
mant consumer hardware. However, current real-world
blockchain networks are practically limited to around 30
transactions per second. This limitation mainly origi-
nates from the fact that the current synchronous consen-
sus mechanisms require wide timing margins of safety on
the expected processing time, which is exacerbated by the
1
POLKADOT: VISION FOR A HETEROGENEOUS MUL TI-CHAIN FRAMEWORK DRAFT 1 2
desire to support slower implementations. This is due to
the underlying consensus architecture: the state transi-
tion mechanism, or the means by which parties collate
and execute transactions, has its logic fundamentally tied
into the consensus “canonicalisation” mechanism, or the
means by which parties agree upon one of a number of
possible, valid, histories.
This applies equally to both proof-of-work (PoW) sys-
tems such as Bitcoin [15] and Ethereum [5,23] and proof-
of-stake (PoS) systems such as NXT [8] and Bitshares [12]:
all ultimately suffer from the same handicap. It is a simple
strategy that helped make blockchains a success. However,
by tightly coupling these two mechanisms into a single unit
of the protocol, we also bundle together multiple different
actors and applications with different risk profiles, differ-
ent scalability requirements and different privacy needs.
One size does not fit all. Too often it is the case that in a
desire for broad appeal, a network adopts a degree of con-
servatism which results in a lowest-common-denominator
optimally serving few and ultimately leading to a failing
in the ability to innovate, perform and adapt, sometimes
dramatically so.
Some systems such as e.g. Factom [21] drop the state-
transition mechanism altogether. However, much of the
utility that we desire requires the ability to transition state
according to a shared state-machine. Dropping it solves
an alternative problem; it does not provide an alternative
solution.
It seems clear, therefore, that one reasonable direction
to explore as a route to a scalable decentralised compute
platform is to decouple the consensus architecture from
the state-transition mechanism. And, perhaps unsurpris-
ingly, this is the strategy that Polkadot adopts as a solu-
tion to scalability.
2.1. Protocol, Implementation and Network. Like
Bitcoin and Ethereum, Polkadot refers at once to a net-
work protocol and the (hitherto presupposed) primary
public network that runs this protocol. Polkadot is in-
tended to be a free and open project, the protocol speci-
fication being under a Creative Commons license and the
code being placed under a FLOSS license. The project is
developed in an open manner and accepts contributions
where ever they are useful. A system of RFCs, not unlike
the Python Enhancement Proposals, will allow a means of
publicly collaborating over protocol changes and upgrades.
Our initial implementation of the Polkadot protocol
will be known as the Parity Polkadot Platform and will
include a full protocol implementation together with API
bindings. Like other Parity blockchain implementations,
PPP is designed to be a general-purpose blockchain tech-
nology stack, neither uniquely for a public network nor for
private/consortium operation. The development of it thus
far has been funded by several parties including through
a grant from the British government.
This paper nonetheless describes Polkadot under the
context of a public network. The functionality we envi-
sion in a public network is a superset of that required in
alternative (e.g. private and/or consortium) settings. Fur-
thermore, in this context, the full scope of Polkadot can
be more clearly described and discussed. This does mean
the reader should be aware that certain mechanisms may
be described (for example interoperation with other pub-
lic networks) which are not directly relevant to Polkadot
when deployed under non-public (“permissioned”) situa-
tions.
2.2. Previous work. Decoupling the underlying consen-
sus from the state-transition has been informally proposed
in private for at least two years—Max Kaye was a pro-
ponent of such a strategy during the very early days of
Ethereum.
A more complex scalable solution known as Chain
fibers, dating back to June 2014 and first published later
that year1, made the case for a single relay-chain and mul-
tiple homogeneous chains providing a transparent inter-
chain execution mechanism. Decoherence was paid for
through transaction latency—transactions requiring the
coordination of disparate portions of the system would
take longer to process. Polkadot takes much of its ar-
chitecture from that and the follow-up conversations with
various people, though it differs greatly in much of its de-
sign and provisions.
While there are no systems comparable to Polkadot
actually in production, several systems of some relevance
have been proposed, though few in any substantial level of
detail. These proposals can be broken down into systems
which drop or reduce the notion of a globally coherent
state machine, those which attempt to provide a globally
coherent singleton machine through homogeneous shards
and those which target only heterogeneity.
2.2.1. Systems without Global State. Factom [21] is a sys-
tem that demonstrates canonicality without the according
validity, effectively allowing the chronicling of data. Be-
cause of the avoidance of global state and the difficulties
with scaling which this brings, it can be considered a scal-
able solution. However, as mentioned previously, the set
of problems it solves is strictly and substantially smaller.
Tangle [18] is a novel approach to consensus systems.
Rather than arranging transactions into blocks and form-
ing consensus over a strictly linked list to give a glob-
ally canonical ordering of state-changes, it largely aban-
dons the idea of a heavily structured ordering and instead
pushes for a directed acyclic graph of dependent trans-
actions with later items helping canonicalise earlier items
through explicit referencing. For arbitrary state-changes,
this dependency graph would quickly become intractable,
however for the much simpler UTXO model2 this becomes
quite reasonable. Because the system is only loosely co-
herent and transactions are generally independent of each
other, a large amount of global parallelism becomes quite
natural. Using the UTXO model does have the effect
of limiting Tangle to a purely value-transfer “currency”
system rather than anything more general or extensible.
Furthermore without the hard global coherency, interac-
tion with other systems—which tend to need an absolute
degree knowledge over the system state—becomes imprac-
tical.
1https://github.com/ethereum/wiki/wiki/Chain-Fibers-Redux
2unspent transaction output, the model that Bitcoin uses whereby the state is effectively the set of address associated with some value;
transactions collate such addresses and reform them into a new set of addresses whose sum total is equivalent
POLKADOT: VISION FOR A HETEROGENEOUS MUL TI-CHAIN FRAMEWORK DRAFT 1 3
2.2.2. Heterogeneous Chain Systems. Side-chains [3] is a
proposed addition to the Bitcoin protocol which would al-
low trustless interaction between the main Bitcoin chain
and additional side-chains. There is no provision for any
degree of ‘rich’ interaction between side-chains: the in-
teraction would be limited to allowing side-chains to be
custodians of each other’s assets, effecting—in the local
jargon—a two-way peg 3. The end vision is for a frame-
work where the Bitcoin currency could be provided with
additional, if peripheral, functionality through pegging it
onto some other chains with more exotic state transition
systems than the Bitcoin protocol allows. In this sense,
side-chains addresses extensibility rather than scalability.
Indeed, there is fundamentally no provision for the va-
lidity of side-chains; tokens from one chain (e.g. Bitcoin)
held on behalf of a side-chain are secured only by the
side-chain’s ability to incentivise miners to canonicalise
valid transitions. The security of the Bitcoin network
cannot easily be transitioned to work on behalf of other
blockchains. Furthermore, a protocol for ensuring Bitcoin
miners merge-mine (that is duplicate their canonicalisa-
tion power onto that of the side-chain) and, more impor-
tantly, validate the side-chain’s transitions is outside the
scope of this proposal.
Cosmos [10] is a proposed multi-chain system in the
same vein as side-chains, swapping the Nakamoto PoW
consensus method for Jae Kwon’s Tendermint algorithm.
Essentially, it describes multiple chains (operating in
zones) each using individual instances of Tendermint, to-
gether with a means for trust-free communication via a
master hub chain. This interchain communication is lim-
ited to the transfer of digital assets (“specifically about to-
kens”) rather than arbitrary information, however such in-
terchain communication does have a return path for data,
e.g. to report to the sender on the status of the transfer.
Validator sets for the zoned chains, and in particular
the means of incentivising them, are, like side-chains, left
as an unsolved problem. The general assumption is that
each zoned chain will itself hold a token of value whose in-
flation is used to pay for validators. Still in the early stages
of design, at present the proposal lacks comprehensive de-
tails over the economic means of achieving the scalable
certainty over global validity. However, the loose coher-
ence required between the zones and the hub will allow
for additional flexibility over the parameters of the zoned
chains compared to that of a system enforcing stronger
coherence.
2.2.3. Casper. As yet no comprehensive review or side-
by-side comparison between Casper [6] and Polkadot
have been made, though one can make a fairly sweeping
(and accordingly inaccurate) characterisation of the two.
Casper is a reimagining of how a PoS consensus algorithm
could be based around participants betting on which fork
would ultimately become canonical. Substantial consider-
ation was given to ensuring that it be robust to network
forks, even when prolonged, and have some additional de-
gree of scalability on top of the basic Ethereum model. As
such, Casper to date has tended to be a substantially more
complex protocol than Polkadot and its forebears, and a
substantial deviation from the basic blockchain format. It
remains unseen as to how Casper will iterate in the future
and what it will look like should it finally be deployed.
While Casper and Polkadot both represent interest-
ing new protocols and, in some sense, augmentations of
Ethereum, there are substantial differences between their
ultimate goals and paths to deployment. Casper is an
Ethereum Foundation-centered project originally designed
to be a PoS alteration to the protocol with no desire to
create a fundamentally scalable blockchain. Crucially, it is
designed to be a hard-fork, rather than anything more ex-
pansive and thus all Ethereum clients and users would be
required to upgrade or remain on a fork of uncertain adop-
tion. As such, deployment is made substantially more dif-
ficult as is inherent in a decentralised project where tight
coordination is necessary.
Polkadot differs in several ways; first and foremost,
Polkadot is designed to be a fully extensible and scalable
blockchain development, deployment and interaction test
bed. It is built to be a largely future-proof harness able to
assimilate new blockchain technology as it becomes avail-
able without over-complicated decentralised coordination
or hard forks. We already envision several use cases such
as encrypted consortium chains and high-frequency chains
with very low block times that are unrealistic to do in
any future version of Ethereum currently envisioned. Fi-
nally, the coupling between it and Ethereum is extremely
loose; no action on the part of Ethereum is necessary to
enable trustless transaction forwarding between the two
networks.
In short, while Casper/Ethereum 2.0 and Polkadot
share some fleeting similarities we believe their end goal
is substantially different and that rather than competing,
the two protocols are likely to ultimately co-exist under a
mutually beneficial relationship for the foreseeable future.
3. Summary
Polkadot is a scalable heterogeneous multi-chain. This
means that unlike previous blockchain implementations
which have focused on providing a single chain of varying
degrees of generality over potential applications, Polkadot
itself is designed to provide no inherent application func-
tionality at all . Rather, Polkadot provides the bedrock
“relay-chain” upon which a large number of validatable,
globally-coherent dynamic data-structures may be hosted
side-by-side. We call these data-structures “parallelised”
chains or parachains, though there is no specific need for
them to be blockchain in nature.
In other words, Polkadot may be considered equiva-
lent to a set of independent chains (e.g. the set containing
Ethereum, Ethereum Classic, Namecoin and Bitcoin) ex-
cept for two very important points:
• Pooled security;
• trust-free interchain transactability.
These points are why we consider Polkadot to be “scal-
able”. In principle, a problem to be deployed on Polka-
dot may be substantially parallelised—scaled out—over
a large number of parachains. Since all aspects of each
parachain may be conducted in parallel by a different seg-
ment of the Polkadot network, the system has some ability
to scale. Polkadot provides a rather bare-bones piece of
3as opposed to a one-way peg which is essentially the action of destroying tokens in one chain to create tokens in another without the
mechanism to do the converse in order to recover the original tokens
POLKADOT: VISION FOR A HETEROGENEOUS MUL TI-CHAIN FRAMEWORK DRAFT 1 4
infrastructure leaving much of the complexity to be ad-
dressed at the middleware level. This is a conscious de-
cision intended to reduce development risk, enabling the
requisite software to be developed within a short time span
and with a good level of confidence over its security and
robustness.
3.1. The Philosophy of Polkadot. Polkadot should
provide an absolute rock-solid foundation on which to
build the next wave of consensus systems, right through
the risk spectrum from production-capable mature designs
to nascent ideas. By providing strong guarantees over se-
curity, isolation and communication, Polkadot can allow
parachains to select from a range of properties themselves.
Indeed, we foresee various experimental blockchains push-
ing the properties of what could be considered sensible
today.
We see conservative, high-value chains similar to
Bitcoin or Z-cash [20] co-existing alongside lower-value
“theme-chains” (such marketing, so fun) and test-nets
with zero or near-zero fees. We see fully-encrypted,
“dark”, consortium chains operating alongside—and even
providing services to—highly functional and open chains
such as those like Ethereum. We see experimental new
VM-based chains such as a subjective time-charged wasm
chain being used as a means of outsourcing difficult com-
pute problems from a more mature Ethereum-like chain
or a more restricted Bitcoin-like chain.
To manage chain upgrades, Polkadot will inherently
support some sort of governance structure, likely based
on existing stable political systems and having a bicam-
eral aspect similar t프로젝트로 돌아가기