bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 3쪽 중 2쪽
ol
and
market
participants
and
provide
a
sense
of
reliability.
As
the
Polygon
ecosystem
continues
to
grow,
this
should
contribute
to
establishing
POL
as
an
attractive
and
reliable
digital
asset,
which
subsequently
could
further
ignite
adoption
and
reliability,
thus
creating
a
virtuous
circle.
6
Staking
Layer
Realizing
the
vision
of
the
Value
Layer
of
the
Internet
will
eventually
require
the
Polygon
network
to
host
billions
of
users
and
millions
of
Web3
applications.
To
enable
this
vast
level
of
activity,
hundreds
or
thousands
of
Polygon
chains
will
be
running
in
parallel,
secured
by
tens
or
hundreds
of
thousands
of
validators.
In
order
to
coordinate
all
Polygon
chains
and
validators,
the
redesigned
Polygon
protocol
architecture
introduces
the
Staking
Layer.
The
Staking
Layer
is
a
one-of-a-kind
programmable
multi-chain
coordinator
protocol.
By
orchestrating
all
Polygon
validators
and
chains,
it
enables:
●
Unlimited
scalability
of
the
ecosystem;
●
Simple,
automated
access
to
dedicated
Web3
infrastructure
to
any
Web3
project.
The
Web3
industry
was
started
by
Bitcoin,
the
first
successful
blockchain
with
a
single
application
–
digital
currency.
As
new
applications
and
use
cases
were
being
proposed,
they
were
normally
launching
their
own
blockchains,
which
was
slow
and
complex.
This
was
addressed
by
the
second
major
breakthrough
of
Web3
–
Ethereum,
a
programmable
blockchain
that
can
support
any
application
or
use
case.
Despite
being
a
huge
paradigm
shift,
the
main
limitation
of
Ethereum
is
that
it
is
not
able
to
scale
to
support
mainstream
adoption.
To
mitigate
this
limitation,
the
Ethereum
community
turned
to
Layer
2
chains
–
blockchain
architectures
that
offer
higher
scalability
without
sacrificing
security.
With
the
introduction
of
Staking
Layer,
Polygon
becomes
capable
of
supporting
a
practically
unlimited
number
of
Layer
2
chains,
each
fully
programmable
both
on
the
application
and
the
configuration
level.
We
believe
this
can
be
the
third
most
important
breakthrough
since
the
commencement
of
Web3,
given
the
magnitude
of
innovation
and
adoption
it
enables.
12
Describing
and
specifying
the
Staking
Layer
in
detail
is
out
of
the
scope
of
this
paper.
Instead,
and
in
order
to
get
better
understanding
of
this
POL-powered
layer
and
its
potential,
we
provide
an
overview
of
its
following
aspects:
●
Design
and
implementation;
●
Polygon
chains
management;
●
Validator
management.
6.1
Design
and
implementation
As
mentioned
above,
the
Staking
Layer
is
a
programmable
multi-chain
coordinator.
It
manages
two
main
logical
components:
1.
Validator
registry:
Maintains
the
up-to-date
registry
of
validators,
with
their
corresponding
POL
stakes
and
chains
they
are
subscribed
to;
2.
Chain
registry:
Maintains
the
up-to-date
registry
of
Polygon
chains,
with
their
corresponding
configurations.
The
main
feature
the
Staking
Layer
requires
is
full
programmability;
it
allows
it
to
support
and
coordinate:
●
Arbitrary
configurations
of
Polygon
chains;
●
All
validator-related
operations;
●
Arbitrary
supporting
operations
and
applications,
e.g.
staking
derivatives.
The
optimal
way
to
achieve
programmability
is
by
utilizing
EVM
(Ethereum
Virtual
Machine),
since
it
provides
a
number
of
benefits:
●
Turing-completeness;
●
Maturity
of
the
EVM,
higher
level
languages
(e.g.
Solidity)
and
tooling;
●
Developer
base
etc.
Practically,
this
means
that
the
Staking
Layer
will
be
implemented
as
a
set
of
EVM
smart
contracts.
These
smart
contracts
can
be
deployed
on
any
EVM
blockchain,
likely
on
Ethereum
or
Polygon
zkEVM
rollup,
given
that
both
offer
a
high
level
of
security.
6.2
Polygon
chains
management
The
Staking
Layer
can
support
a
practically
unlimited
number
of
Polygon
chains,
each
with
arbitrary
features
and
configuration,
and
provide
them
the
required
level
of
decentralization.
13
The
main
service
that
the
Staking
Layer
provides
to
Polygon
chains
is
the
management
of
their
validator
requirements
and
validator
sets
established
according
to
those
requirements.
Validator
requirements
are
specified
in
a
config
smart
contract
that
every
Polygon
chain
deploys
in
order
to
get
initiated.
This
smart
contract
can
define
arbitrary
validator
requirements,
including
but
not
limited
to:
●
Maximal
validator
number:
Specifies
the
maximum
number
of
validators
the
chain
accepts
in
its
validator
set.
●
Minimal
validator
number:
The
minimal
number
of
validators
required
to
initiate
the
chain.
●
Slashable
offenses:
On-chain
attributable
validation
offenses
that
cause
slashing
of
the
stake;
●
Validator
criteria:
The
only
common
criteria
for
all
validators
in
the
Staking
Hub
is
a
stake
in
POL.
Arbitrary
additional
criteria
can
be
specified,
such
as
authorization
by
a
third
party,
additional
stake
in
other
tokens
(e.g.
native
tokens
of
individual
Polygon
chains)
etc.
In
addition
to
the
ability
to
configure
validator
requirements,
Polygon
chains
can
arbitrarily
configure
all
other
parameters
and
features
of
their
architecture.
These
are
not
defined
on
the
Staking
Layer
level,
but
instead
in
the
client
code
of
Polygon
chains.
Some
notable
parameters
and
features
are:
●
Native
token:
Chains
can
create
their
native
tokens
which
can
be
used
for
various
purposes,
e.g.
transaction
fees,
user
incentivization
etc.
●
Fee
management:
Chains
can
decide
how
to
manage
transaction
fees.
Normally,
transaction
fees
would
be
passed
to
validators
in
their
entirety,
but
other
distribution
models
are
possible,
e.g.
burning
a
portion
of
fees
and
passing
the
remaining
portion
to
validators.
●
Additional
rewards:
All
Polygon
validators
receive
base
protocol
rewards
(as
described
in
§
4.2)
and
normally
transaction
fees
from
Polygon
chains
they
validate.
In
order
to
attract
more
validators,
Polygon
chain
can
offer
additional
rewards
on
top
of
these.
These
rewards
will
likely
often
be
in
native
tokens
of
those
chains.
●
Block
time
and
size:
It
is
possible
to
configure
the
frequency
and
size,
i.e.
gas
limit
of
blocks.
●
Checkpoint
time:
Validator
sets
provide
fast,
local
finality
for
Polygon
chains.
In
addition
to
this,
all
Polygon
chains
periodically
generate
and
submit
zero-knowledge
proofs
to
14
Ethereum,
thus
leveraging
its
high
security.
The
frequency
of
these
checkpoints
can
be
configured
(e.g.
every
5
minutes).
●
Data
availability:
The
data
availability
model
can
also
be
specified.
Chains
can
decide
to
leverage
Ethereum
(rollup
model)
or
their
own
validator
sets
or
other
external
data
availability
service
(validium
model).
With
the
proposed
framework,
launching
a
new
Polygon
chain
practically
boils
down
to
writing
and
deploying
the
aforementioned
config
smart
contract.
Once
the
contract
gets
deployed
to
the
Staking
Layer,
validators
can
start
subscribing
to
it.
When
the
minimal
required
number
of
validators
is
reached,
the
chain
gets
launched.
We
believe
that
this
simple
way
of
configuring
and
launching
chains
can
usher
a
new
era
of
innovation
and
adoption.
The
game-changing
design
decision
of
Ethereum
was
to
not
try
to
predict
what
applications
and
use
cases
developers
will
want
to
build.
Instead,
it
offered
a
Turing-complete
programmable
environment
that
can
support
any
application
or
use
case.
With
the
Staking
Layer,
Polygon
is
taking
the
same
approach
for
launching
new
chains
–
it
supports
practically
any
chain
design,
in
a
programmable
manner
and
without
scaling
limitations.
6.3
Validator
management
The
Staking
Layer
can
support
a
practically
unlimited
number
of
validators.
It
manages
validators
throughout
their
whole
lifecycle
and
enables
them
to
secure
different
types
of
incentives
for
performing
useful
work.
There
are
four
possible
phases,
i.e.
statuses,
in
the
validator
lifecycle:
1.
Activation:
Validators
get
initiated
as
part
of
the
validator
pool
by
depositing
POL
into
the
staking
contract
on
the
Staking
Layer.
Once
initiated,
validators
become
eligible
to
receive
base
protocol
rewards
(described
in
§
4.2).
2.
Subscription:
Once
initiated,
validators
are
allowed
to
subscribe
to
validate
any
Polygon
chain.
3.
Validation:
If
a
validator
meets
all
the
criteria
of
the
Polygon
chain
it
subscribed
to,
it
becomes
a
member
of
that
chain’s
validator
set.
Validators
can
validate
multiple
chains,
and
their
POL
stake
is
acknowledged
on
each
of
those
chains.
If
a
validator
gets
slashed
for
a
predefined
slashable
offense
on
one
of
the
chains,
its
POL
balance
gets
updated
and
reflected
on
all
chains
it
validates.
The
validation
and
subscription
phases
can
15
overlap;
a
single
validator
can
be
in
the
subscription
phase
on
one
Polygon
chain
and
in
the
validation
phase
on
another.
4.
Retirement:
Validators
can
leave
the
validator
pool
at
any
point.
Once
the
retirement
is
initiated,
a
predefined
waiting
period
commences,
allowing
for
potential
pending
slashing.
After
the
waiting
period,
validators
are
able
to
withdraw
their
POL
stake
from
the
deposit
contract.
In
return
for
validating
Polygon
chains,
validators
can
establish
at
least
three
incentive
streams:
1.
Protocol
rewards:
As
described
above,
every
active
Polygon
validator
is
receiving
base
protocol
rewards.
The
total
POL
emission
for
validator
rewards
(described
in
§
5.2),
is
distributed
to
active
validators
proportionally
to
their
POL
stake.
2.
Transaction
fees:
Validators
are
allowed
to
validate
any
number
of
Polygon
chains.
In
return,
these
chains
will
normally
award
the
entirety
or
a
portion
of
transaction
fees
to
validators.
3.
Additional
rewards:
As
mentioned
above,
some
Polygon
chains
can
choose
to
introduce
additional
rewards
to
attract
more
validators.
These
rewards
can
be
in
any
token,
including
but
not
limited
to
POL,
stablecoins
or
native
tokens
of
those
Polygon
chains.
As
we
describe
validator
incentives,
it
is
worth
noting
that
the
concept
of
validation
in
Polygon
is
broader
than
the
usual,
narrow
definition.
This
further
improves
the
value
proposition
of
the
validator
role
–
in
addition
to
validating
multiple
chains,
validators
can
also
perform
multiple
roles
on
a
single
chain.
The
most
common
roles
will
likely
be:
●
Validation
in
the
narrow
sense:
Accepting
user
transactions,
determining
their
validity
and
generating
blocks;
●
Proving:
Producing
zero-knowledge
proofs
of
transaction
validity;
●
Data
availability:
Providing
guarantees
that
transaction
data
is
published
and
publicly
available.
7
Community
Treasury
The
Polygon
ecosystem
and
the
whole
Web3
industry
are
still
in
the
early
adoption
and
heavy
development
phase.
To
remain
on
the
current
growth
trajectory,
the
Polygon
ecosystem
will
need
ongoing
economic
support
in
years
to
come.
16
To
address
the
need
for
ongoing
ecosystem
support,
we
propose
the
Community
Treasury,
an
in-protocol,
community-governed
ecosystem
fund.
It
introduces
at
least
three
major
benefits
to
the
Polygon
ecosystem:
●
Ongoing,
self-sustainable
economic
support
for
as
long
as
required;
●
Increased
decentralization
by
reducing
dependency
on
the
Polygon
Foundation;
●
Achieving
the
next
level
of
transparency
and
community
inclusion.
As
described
in
§
5.2,
the
Community
Treasury
is
funded
by
a
predetermined
emission
of
POL.
The
emission
rate
dedicated
to
this
purpose
is
1%
per
year,
or
≈100
million
POL
in
absolute
terms,
and
can
not
be
changed
for
10
years.
This
guarantees
strong
ecosystem
support
during
this
period,
critical
for
development,
growth
and
positioning
of
Polygon.
Once
the
Polygon
ecosystem
and
Web3
reach
maturity,
the
ecosystem
will
likely
not
need
significant
economic
support
anymore.
At
that
point,
the
community
should
intervene
and
decrease
or
discontinue
the
emission
for
the
Community
Treasury.
In
an
optimistic
scenario,
where
maturity
is
reached
before
the
10-year
period
of
guaranteed
funding
expires,
the
Community
Treasury
might
end
up
having
more
funds
than
the
ecosystem
realistically
needs.
In
that
case,
the
community
should
decide
how
to
utilize
this
excess
POL.
For
example,
a
decision
can
be
made
to
burn
it.
As
mentioned,
and
as
the
name
indicates,
the
Community
Treasury
should
be
governed
by
the
community,
via
an
agreed
upon
governance
process.
The
governance
process
and
the
wider
Polygon
governance
framework
are
being
designed
and
established
as
part
of
the
Polygon
2.0
effort,
and
explaining
them
in
detail
is
out
of
the
scope
of
this
paper.
Instead,
we
give
a
brief
overview
of
its
two
likely
concepts:
1.
Polygon
Funding
Proposals
(PFPs):
Formal
proposals
for
funding
or
other
activities
or
improvements
related
to
the
Community
Treasury.
PFPs
can
be
submitted
by
anyone,
and
should
be
publicly
available
and
discussed.
Similar
concepts
can
be
observed
in
other
prominent
governance
frameworks
4
,
5
.
2.
Consensus
gathering:
The
process
of
making
a
decision
on
a
specific
PFP.
The
decision
can
be
made
in
a
direct
manner,
where
every
community
member
can
participate,
or
via
delegates
who
represent
the
community.
As
mentioned
in
§
4.3,
POL
should
be
technically
enabled
to
hold
governance
rights,
so
it
can
potentially
be
utilized
5
https://docs.aave.com/governance/
4
https://uniswap.org/governance
17
as
part
of
the
consensus
gathering
or
the
delegate
election
process.
POL
holders
are
directly
economically
incentivized
to
approve
good
proposals
and
reject
the
bad
ones,
which
makes
the
decision
making
process
more
likely
to
benefit
the
ecosystem.
We
simulated
ongoing
Community
Treasury
inflows
in
§
9.
8
Migration
Given
that
POL
is
being
proposed
as
the
successor
of
MATIC,
the
current
native
token
of
Polygon,
migration
from
the
old
to
the
new
token
would
need
to
take
place.
The
initial
supply
of
POL
proposed
in
§
5.1
matches
the
current
supply
of
MATIC
and
was
proposed
to
simplify
the
migration
process
as
much
as
possible.
For
self-custodying
MATIC
holders,
the
migration
would
require
a
simple
action
–
swap
from
MATIC
to
POL,
using
the
swapping
smart
contract
that
should
be
created
for
that
purpose.
The
swapping
contract
should
accept
MATIC
from
any
address
and
return
the
equivalent
amount
of
POL
to
the
same
address.
For
MATIC
holders
who
keep
their
tokens
with
centralized
crypto
exchanges
and
custodians,
the
migration
would
normally
be
automatic,
i.e.
would
not
require
any
action.
Every
MATIC
holder
should
be
able
to
swap
their
tokens
for
POL,
including
those
who
have
MATIC
“locked”
for
multiple
years
in
various
DeFi
or
vesting
contracts,
or
the
uninformed
holders
who
find
out
about
POL
at
some
point
in
the
future.
For
this
reason,
the
migration
should
be
allowed
to
happen
during
a
prolonged
period
of
time
(e.g.
4
years),
if
not
indefinitely.
The
migration
should
be
voluntary,
i.e.
it
cannot
be
forced.
However,
if
POL
is
accepted
by
the
majority
of
the
community
as
the
new
native
token,
there
will
be
little
to
no
reason
to
hold
MATIC
instead
of
POL.
In
this
situation,
it
is
reasonable
to
expect
that
the
migration
will
practically
be
fully
executed,
i.e.
the
vast
majority
of
MATIC
will
be
migrated.
9
Model
Based
on
the
design
of
POL
and
the
Staking
Layer,
we
propose
a
model
to
simulate
important
performance
indicators
of
the
POL-powered
ecosystem,
provide
required
inputs
and
analyze
the
results
of
simulations.
18
9.1
Hypothesis
The
purpose
of
the
model
is
to
validate
the
hypothesis
that
the
proposed
POL-powered
ecosystem
can
simultaneously
meet
the
following
goals,
derived
from
§
3:
●
Sufficient
ecosystem
security:
We
measure
security
through
POL
staking
ratio,
i.e.
percentage
of
the
POL
supply
staked
by
validators.
The
minimal
satisfactory
ratio
is
30-40%,
roughly
equivalent
to
the
current
staking
ratio
on
the
Polygon
PoS
chain
6
.
●
Sufficient
validator
incentives:
To
estimate
sufficiency
of
validator
incentives,
we
introduce
Return
on
Work
(ROW),
the
measure
of
total
validator
earnings
relative
to
the
value
of
staked
POL.
The
minimal
satisfactory
return
is
4-5%;
lower
returns
are
not
considered
attractive
enough,
considering
the
work
being
performed,
the
risks
and
the
opportunity
costs.
●
Sufficient
ecosystem
support:
We
measure
ecosystem
support
through
yearly
inflow
to
the
Community
Treasury.
The
minimal
satisfactory
inflow
is
$50-100
million,
and
it
is
determined
based
on
the
current
level
of
economic
support
the
Polygon
ecosystem
needs.
We
explicitly
define
these
indicators
(staking
ratio,
validator
returns
and
treasury
inflow)
in
§
9.3.
9.2
Inputs
In
this
chapter
we
outline
the
required
model
inputs
and
estimate
their
respectable
values.
First,
we
define
three
growth
scenarios,
projecting
the
abstract
number
of
chains
in
the
Polygon
ecosystem
during
the
initial
10-year
period.
We
refer
to
the
number
of
chains
as
abstract
because
it
is
not
necessarily
expressing
the
exact
number
of
Polygon
chains
(although
that
might
be
the
case),
but
more
the
cumulative
level
of
activity,
i.e.
transactions
in
the
ecosystem.
6
Source:
https://staking.polygon.technology/
19
Figure
3.
10-year
growth
scenarios
The
rationale
for
the
growth
scenarios
is
based
on
the
following
data
and
observations:
●
Current
growth
trajectory.
Since
the
inception
in
2020,
the
Polygon
ecosystem
has
grown
to
thousand
of
applications
and
3
million
daily
transactions
7
.
If
this
trend
even
remotely
continues,
the
proposed
growth
scenarios
seem
realistic.
●
Web2
app
marketplaces:
The
App
Store
hosts
around
1.8
million
applications
8
and
Google
Play
around
2.7
million
9
;
both
were
introduced
around
14
years
ago.
It
could
be
reasonable
to
expect
a
comparable
level
of
adoption
for
Web3
in
a
comparable
timeframe.
●
Supernets
adoption:
At
the
moment
of
writing
this
paper,
one
year
since
the
introduction
of
Supernets,
there
are
more
than
100
Supernets
candidate
projects,
many
of
them
under
active
development.
Based
on
this,
the
proposed
growth
scenarios
for
Supernets
seem
realistic,
especially
given
that
Supernets’
deployment
should
become
significantly
easier
once
the
Staking
Layer
(described
in
§
6)
is
introduced.
Additionally,
it
is
noticeable
that
the
trend
of
interest
in
Supernets
is
stronger
in
relative
terms
than
the
one
for
public
chains.
For
this
reason,
we
are
assuming
the
same
for
the
proposed
growth
scenarios.
To
further
justify
this,
a
meaningful
parallel
with
Web2
adoption
history
can
be
drawn.
In
the
earlier
days
of
Web2,
shared
application
hosting
–
Web2
equivalent
to
public
chains
–
was
much
more
common
than
nowadays.
As
the
industry
matured,
9
Source:
https://www.appbrain.com/stats/number-of-android-apps
8
Source:
https://www.apple.com/newsroom/2022/04/report-finds-third-party-apps-see-global-success-on-the-app-st
ore/
7
Source:
https://polygonscan.com/chart/tx
20
dedicated
hosting
–
Web2
equivalent
to
Supernets
–
became
the
norm
for
every
application
with
a
meaningful
user
base
and
level
of
activity.
Again,
the
number
of
Polygon
chains
is
an
abstract
concept
in
our
model;
in
conjunction
with
the
number
of
transactions
per
chain,
it
should
primarily
reflect
the
level
of
economic
activity
in
the
ecosystem.
Similarly,
the
prevalence,
i.e.
ratio
of
Supernets
compared
to
public
chains,
is
an
abstract,
conservative
assumption.
If
it
would
turn
out
that
public
chains
are
more
popular
relative
to
Supernets,
the
results
of
the
simulation
presented
in
§
9.4
would
look
similar
or
better,
due
to
their
respective
transaction
fee
levels.
To
complement
the
aforementioned
growth
scenarios,
we
estimate
the
following
inputs:
●
Initial
supply
of
10
billion
POL,
as
described
in
§
5.1;
●
Yearly
emission
rate
of
1%
for
validator
incentives,
as
described
in
§
5.2;
●
Yearly
emission
rate
of
1%
for
the
Community
Treasury,
as
described
in
§
5.2;
●
$5
average
POL
price
during
the
10-year
period;
●
38
transactions/second
on
average
per
public
chains,
comparable
to
current
Polygon
PoS
chain
usage
10
;
●
19
transactions/second
on
average
per
Supernet,
an
estimate
based
on
the
requirements
of
Supernet
projects;
●
$0.01
average
transaction
fee
on
public
chains,
an
estimate
based
on
current
average
fees
on
Polygon
PoS
chain;
11
●
$0.001
average
transaction
fee
on
Supernets,
conservative
estimate
given
abundant
blockspace
and
a
“race
to
the
bottom”
that
it
will
likely
cause
for
transaction
fees;
●
100
validators
on
average
per
public
chain,
equivalent
to프로젝트로 돌아가기