bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 3쪽 중 2쪽
ice oracle. This is
valuable for the decentralized peg, removing the need for an external oracle, as described in the
companion paper about the peg. More information about PoX consensus is available here.
Stacks uses Clarity, a much more secure language than Ethereum’s popular Solidity
language, for the Stacks main layer and the decentralized Bitcoin peg. Clarity is a decidable
language (not Turing-complete), meaning that you can know, with certainty, from the code
6
itself what the program will do, and code correctness can be verified by software. Clarity is an
interpreted rather than compiled language, so the source code of smart contracts is visible on
the blockchain for verification by human beings, and it has post-conditions that provide
additional execution safety.
Using the Stacks layer, developers can build any application they can build on other smart
contract platforms—like Ethereum, Solana, Avalanche, etc. — but using BTC as their
asset/money and settling their transactions on the Bitcoin blockchain. They will be able to do
this in Clarity on the Clarity VM or — using subnets ( Section 3.1 ) — in Solidity or other
languages on the EVM or other virtual machines. Users can also swap BTC natively for assets
like stablecoins and NFTs directly from the Bitcoin chain.
In the rest of this section, we first examine how the Stacks layer rates with regard to the
properties of hypothetical native Bitcoin smart contracts that we discussed earlier, and touch
upon how it provides higher performance. We discuss how the fact that Stacks has a native
token helps Bitcoin rather than hurting it. We then describe the decentralized two-way Bitcoin
peg a little further (a detailed description is available in the sBTC paper [1]), and we discuss the
related security and forking rules of the Stacks chain in the new release. Finally, we discuss
additional capabilities for performance and versatility, including subnets, future EVM
compatibility, and the potential for ZK-rollups.
2.1. Stacks and “Native Bitcoin” Smart Contracts
The Stacks layer comes close to providing all the properties that native smart contracts on
Bitcoin would, if they were available.
• Bitcoin finality and security: Stacks blocks that have about a day of confirmations achieve
Bitcoin finality; i.e., they are secured by the Bitcoin blockchain and the entire hash power
of Bitcoin (not only that of Stacks miners, and not like in merged mining). Beyond that
point, the Stacks layer does not allow forks, so to reorganize the Stacks transactions would
require successfully attacking Bitcoin with a deep reorg attack, which is extremely
expensive and logistically difficult to pull off. It is worth noting that because Stacks blocks
are recorded on Bitcoin blocks, information about them is publicly visible on the Bitcoin
blockchain as they are produced, making it easy to detect attacks and reorgs and take
countermeasures, and making hidden block attacks (such as selfish mining) much more
difficult than on Bitcoin itself.
• Smart contracts being triggered by Bitcoin transactions: Smart contracts on the Stacks
layer can read Bitcoin state and can be triggered by standard Bitcoin transactions. This is
because Stacks nodes also run Bitcoin nodes as part of consensus, and they read and index
Bitcoin state eagerly.
• Bitcoin writes: The sBTC Bitcoin peg mechanism can write Bitcoin transactions to the
Bitcoin chain in a trustless manner . Stacks also allows applications to deploy BTC
directly from the Bitcoin chain; e.g., users can perform trustless atomic swaps between
BTC and other assets (like stablecoins) on the Stacks layer. For faster performance, the
Stacks layer also supports decentralized, non-custodial peg-outs and peg-ins of a 1:1
pegged BTC : BTC can be pegged in to the Stacks layer, smart contracts and other
operations can operate upon it faster there, and it can be pegged back out onto the Bitcoin
7
main chain. Unlike the derived assets of sidechains, like L-BTC in Liquid and RBTC in
RSK, this peg is not reliant on a fixed federation or a federation of multisig hardware
wallets for its peg-out. Rather, it achieves economic security through an open-membership
set of signatories, in a manner integrated with the Stacks consensus protocol. Using sBTC
with faster blocks and subnets allows smart contracts to operate with much lower latencies
and higher throughputs than using BTC directly on the Bitcoin blockchain.
• Settlement and verification on Bitcoin. Hashes of all Stacks layer smart contracts and
transactions settle on the Bitcoin blockchain . This is a necessary consequence of the
operation of Stacks' PoX consensus protocol, and it happens dynamically, every Bitcoin
block, as part of consensus.
• Forking with Bitcoin. The PoX protocol also gives the Stacks layer the desirable property
of forking with Bitcoin. Bitcoin forks are naturally adapted to and "taken in stride" by the
Stacks layer, such that the canonical Stacks chain is always found on the canonical Bitcoin
chain, and smart contracts, transactions and the peg automatically stay in sync and
uncorrupted even if Bitcoin forks. As a result of these properties, any suggested version of
the Stacks ledger can be fully, independently verified by looking at the Bitcoin main chain,
including and accounting for all forks, thus providing an additional layer of security and
durability. That is, a user can independently verify which fork history of Stacks is correct
simply by running an independent Bitcoin node.
The trustless Bitcoin peg enables much higher performance than could be achieved by native
Bitcoin smart contracts. It does this by having smart contracts run on the faster Stacks layer,
which provides faster-confirming, lower-latency blocks (still using Bitcoin as the asset and with
final settlement on the Bitcoin chain), as well as through aggregation of thousands of Stacks
transactions to a single hash for settlement.
2.2. Synergies versus Competition with Bitcoin
The Stacks Bitcoin layer clearly relies on Bitcoin in a fundamental way. At the same time, the
argument can be made that because it has its own token (STX), it pulls value away from
Bitcoin. While this may be true of other tokens that directly compete with Bitcoin, it is not true
of STX as the Stacks layer helps grow the Bitcoin ecosystem rather than compete with Bitcoin.
We mentioned earlier that the STX token is not merely a governance or speculative token, but it
is necessary to the PoX consensus mechanism of the Stacks Bitcoin layer and essential for two
key functional purposes: (i) incentivizing mining Stacks blocks with a new block subsidy,
which is critical since transaction fees are not enough to sustain a ledger at least in the early
days (as is the case with Bitcoin itself), and (ii) serving as the liveness incentive and the basis
for the economically secured decentralized Bitcoin peg.
The token is thus essential to the goal of building and growing decentralized applications that
make Bitcoin productive and more useful. Such applications increase demand for Bitcoin
block space and make Bitcoin more valuable. These applications and other activities that can
be performed on Bitcoin using the Stacks layer also result in higher transaction fees for
Bitcoin miners , in two ways: (a) the applications directly cause more transactions on the
Bitcoin chain, which generate fees, and (b) Stacks mining and settlement on Bitcoin result in
high-fee BTC transactions. These transaction fee incentives for Bitcoin miners become
8
increasingly important as the Bitcoin coinbase rewards (or "new block subsidies") are reduced
with "Bitcoin halvings" every four years and Bitcoin miners must rely more on transaction fees.
Finally, enabling decentralized applications with Bitcoin gives users fewer reasons to use other
chains and monetary assets that compete with Bitcoin.
The Stacks project was started by developers and computer scientists who have a long history
of building in the Bitcoin ecosystem (some early developers of Stacks built the largest used
early OP_RETURN based on-chain Bitcoin protocols [10]).
2.3. The Decentralized, Permissionless Two-way Bitcoin Peg
Smart contracts that run on Bitcoin layers and truly use BTC as their asset must be able to not
only read but also modify Bitcoin state. This means the signing of Bitcoin transactions with
private keys by external software must be managed somehow. This “Bitcoin write” problem is
difficult for transactions initiated by (external) smart contracts. Also, to perform all individual
transactions and state updates on the Bitcoin chain in this way would be very slow and lead to a
lot of long waits for transactions to complete. For performance, we should reduce the number
of times transactions must be sent on Bitcoin and wait for completion.
Pegged Bitcoin assets aim to achieve these goals. A user locks an amount of BTC in a "peg
wallet" on the Bitcoin chain and an equivalent amount of the pegged asset is issued on the other
chain/layer (the "peg-in" operation). The pegged asset is used as often as desired on that layer
(which maintains its own state), including by smart contracts, modifying state on that layer with
higher performance. When desired, an amount of the pegged asset is destroyed and an
equivalent amount of BTC released back on Bitcoin, i.e., unlocked from the peg wallet and sent
to a specified Bitcoin address (the "peg-out"). The peg-out implements "Bitcoin writes" and the
overall structure greatly improves performance.
Because of signature management, the peg-out is a challenging operation. Pegged assets are
implemented on other blockchains and Bitcoin layers, including wBTC on Ethereum, RBTC on
RSK, and L-BTC on Liquid. However, in all those cases the pegs are entrusted to and managed
by a centralized custodian or a federation of trusted and permissioned entities that sign the
Bitcoin peg-out transactions (using multisig methods). wBTC, on Ethereum, has ranged from
$5-$15B in usage, even though it is entrusted to a single custodian and hence antithetical to
Bitcoin ethos. Reliance on centralized custodians or federations is unacceptable, especially for
large amounts of BTC (e.g., hundreds of billions of dollars).
sBTC[1] is a decentralized pegged Bitcoin asset on the Stacks layer, pegged 1:1 to BTC, that
does not rely on centralized or pre-determined entities for its management. Rather, it is
maintained in a decentralized manner by a permissionless, open-membership group of
dynamically changing entities that can start or stop contributing to peg maintenance as they
please, but who—as a result of the design—have a clear economic incentive to properly
maintain the peg. These entities are the Stackers of the PoX consensus protocol, who lock, or
"Stack" STX and perform peg-out signing and other consensus-critical tasks; in return, they are
rewarded in BTC proportionally to the STX they stack. The decentralized peg is integrated into
the Stacks consensus protocol (Proof of Transfer or PoX), and it relies on PoX and its native
STX token for the needed incentive engineering. Such a decentralized Bitcoin peg has been an
unsolved, "holy grail" problem. It allows BTC to be made a productive asset in smart contracts
9
without entrusting it to centralized entities, and to be deployed in applications like
decentralized Bitcoin lending, Bitcoin-backed stablecoins, etc. with high performance and with
the decentralized security that Bitcoin holders critically desire.
Anybody can become (or unbecome) a Stacker and hence a signer of peg-outs, just as anyone
can become (or unbecome) a Stacks miner. The stacking of STX serves as collateral, and the
BTC rewards as incentive, for the honest behavior of Stackers in signing proper peg-outs and
not signing improper ones. The protocol provides incentive-compatible economic guarantees
for a successful ledger and peg: For Stacks miners, it is always incentive-compatible to mine on
the canonical fork, and for Stackers, it is always most profitable to faithfully maintain the peg.
In keeping with Bitcoin’s PoW ethos, Stackers are rewarded for their positive contributions to
the system and inhibited by economic disincentives from behaving poorly (but they are not
"slashed" for the latter, as in Proof of Stake systems).
Peg-outs use a threshold signature mechanism: Liveness persists as long the Stackers of 70% of
stacked STX sign the peg-outs, and safety is preserved (BTC cannot be stolen) as long as
Stackers of at least 31% of the stacked STX do not sign unauthorized peg-outs (which are
easily detected). Given the incentive compatibility, to compromise the peg wallet, a lot of
Stackers would have to maliciously collude as well as behave economically irrationally. Peg-
outs of arbitrary size are fulfilled within about 24 hours, and faster exchange of BTC/sBTC can
be achieved through trustless atomic swaps. The STX token is essential to the economic
guarantees that secure the sBTC Bitcoin peg in a permissionless setting. Existing sidechains
(RSK, Liquid) that lack a native token cannot support a permissionless, decentralized peg and
must rely on centralized, federated approaches. As Stacking incentives compensate the Stackers
that maintain the peg, sBTC does not need users to pay "wrapping fees" , a key advantage
over other pegged assets, including wBTC.
The peg also inherits all the other properties and benefits of the Stacks Bitcoin layer.
2.4. Security and Forking Rules
The Stacks layer will receive a major upgrade to its security model with the Nakamoto
release. The current version of Stacks has a separate security budget from Bitcoin. This
security budget is defined by the BTC capital spent by Stacks miners. With the Nakamoto
release, most of the Stacks chain history will have Bitcoin finality, regardless of the Stacks
mining budget: 100% of Bitcoin mining power will secure the immutability of the Stacks
layer, except for the last 150 blocks . Specifically, after approximately 150 block
confirmations, a Stacks layer block (and hence forks) will follow Bitcoin finality, and only the
blocks less than 150 confirmations old will have a different security budget. Even for those
recent blocks, the security budget will increase from being just the BTC spent by miners to
including the capital locked by Stackers (which is in the hundreds of millions of dollars today).
Stacks security therefore has a step function:
• Forks are allowed within six Bitcoin settlement confirmations, the amount that exchanges
and others wait to consider Bitcoin blocks finalized anyway. Such short-lived forking can
be valuable, as they are in Bitcoin.
• To attack the recent history (within 150 blocks), e.g., to execute a double-spend attack on
the Stacks layer, an attacker needs both a majority of Stacks mining power and at least 71%
10
of Stackers to allow a fork carrying out the attack. Stackers typically do not allow forks
unless they see on the Bitcoin chain that something very bad is happening (which they can
see because of Stacks' early and ongoing visibility on the Bitcoin chain, and because alarms
will therefore be raised). Getting more than 70% of Stackers to agree to such a fork is,
therefore, very difficult and requires hundreds of millions in capital today: Stackers will
only sanction it in this window if it is a fork designed to overcome something very bad
happening on the Stacks layer.
• By far the vast majority of block history on the Stacks layer (blocks with about 150 or more
confirmations, i.e., about a day’s worth) follow Bitcoin finality and are secured by 100% of
Bitcoin’s hash power. To attack the Stacks history, e.g., to alter any transaction more than
about a day old, an attacker will need to do a deep reorg of Bitcoin which is extraordinarily
difficult given the current security budget of Bitcoin and how decentralized Bitcoin mining
is.
This new security model is a major upgrade for the Stacks layer and is highly differentiated
from methods like merged mining or federated designs. The forking rules of Stacks are
designed to minimize the possibility of forks in general while retaining the flexibility for
miners to create forks under certain conditions to repair the chain as a response to specific
attacks. More specifically, Stacks layer follows the following rules:
• Fast blocks are produced as a single sequence in-between two settlement blocks and they
don’t fork. A sequence of fast blocks of size M gets settled in the next settlement Stacks
block. The miner that mines the settlement block can include a sequence of fast blocks of
length 0 to M but there is only one sequence of fast blocks to consider for every settlement
block. Miners of settlement blocks are economically incentivized to include the longest
sequence of fast blocks i.e., the longest valid sequence that the miner has seen at the time of
mining the settlement block. If a settlement block miner settles a smaller sequence then the
miner is leaving money on the table.
• Forking rules only apply to settlement blocks, as a sequence of fast blocks is included
within a settlement block. We can think of a settlement block as packaging all the
transactions of the corresponding sequence of fast blocks.
• If (a) a Stacks settlement block reaches 150 Bitcoin block confirmations and (b) sBTC peg-
out requests settled in that Stacks block successfully get processed by Stackers then that
Stacks settlement block and all parent blocks will always be on the canonical Stacks fork.
In other words, a Stacks block is “finalized” i.e., it can never be forked out of the canonical
fork as soon as these two conditions are met. All parent blocks of a finalized block are also
automatically finalized (even if any parent blocks did not have any sBTC peg-out requests
in them). A finalized Stacks settlement block reaches Bitcoin finality, meaning that the only
way to modify the chain history of finalized Stacks blocks is to do a deep reorg of Bitcoin.
All fast blocks settled in a finalized settlement block also become final. No action at the
Stacks layer can modify the chain of finalized Stacks blocks.
• Building Stacks forks from finalized Stacks blocks is not allowed with one exception: the
latest finalized block i.e., the block that contains the last successfully-processed peg-out
request can be used to build a new fork only if a majority of Stackers (70% or more)
explicitly give permission to do so. This permission to create a fork from a Stacks block is
called “Stacker blessing”.
11
• There can only be zero or one Stacker blessings present in the system at any given time.
Stacker blessings can be overridden but there can be only one active Stacker blessing at
max. The Stacker blessing disappears when the fork using the blessed block becomes the
canonical fork, or it becomes impossible for miners to build on it due to the block
becoming incompatible with the canonical fork.
• Miners can freely build new forks using Stacks blocks with depth 6 or less as parents.
Miners cannot build forks using Stacks blocks with depth 7 to the latest finalized block as a
parent, unless they have an explicit “blessing” from Stackers to initiate such a fork. Miners
can never build forks from finalized blocks (minus the exception of the latest finalized
block with a Stacker blessing).
The summary of forking rules is that:
1. Stacks fast blocks: no forks
2. Stacks settlement blocks depth 1 to 6: miners are free to create forks using these blocks.
3. Stacks settlement blocks depth 7 to the latest finalized block are “frozen”: miners can only
initiate forks through a Stacker blessing to “unfreeze” a block.
4. No other forking is allowed i.e., all finalized blocks (except the latest finalized block) can
never be used as a parent of a Stacks fork.
Typically, users should not expect to see forks deeper than 6 settlement blocks. That should be a
rare occurrence where the chain is actively under attack and Stackers allow the honest miners to
recover the chain to a healthy프로젝트로 돌아가기