<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Editor @ Babylon on Medium]]></title>
        <description><![CDATA[Stories by Editor @ Babylon on Medium]]></description>
        <link>https://medium.com/@Cryptonian_S?source=rss-cfaf956ecd0d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*f31dhV6jyWz4TBwf20lsxg.png</url>
            <title>Stories by Editor @ Babylon on Medium</title>
            <link>https://medium.com/@Cryptonian_S?source=rss-cfaf956ecd0d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:39:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Cryptonian_S/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[Babylon Bitcoin Staking Mainnet Launch: Phase-1]]></title>
            <link>https://medium.com/babylonlabs-io/babylon-bitcoin-staking-mainnet-launch-phase-1-9188a2a1bf46?source=rss-cfaf956ecd0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9188a2a1bf46</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[staking]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Editor @ Babylon]]></dc:creator>
            <pubDate>Fri, 16 Aug 2024 11:22:22 GMT</pubDate>
            <atom:updated>2024-08-19T13:55:52.590Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2XwbMD5t5VQXHXku4jD-xA.png" /></figure><h3>1. Phased Launch of Babylon Bitcoin Staking</h3><p>Babylon Bitcoin staking protocol connects bitcoin holders with the demand for network security from Proof-of-Stake systems like PoS chains, L2s, Data Availability layers, oracles, and others. It does so without a trusted intermediary.</p><p>The protocol will be launched in three phases.</p><h4>1.1 Phase-1: Bitcoin Locking</h4><p>During this phase, bitcoin holders initiate the staking process by submitting Bitcoin staking transactions to the Bitcoin blockchain.</p><p>Each transaction locks the designated bitcoins within a secure, self-custodial Bitcoin staking script. Stakers also specify key parameters, including the public key of the finality provider they’ve chosen to delegate their PoS voting power to. This prepares the locked bitcoins to actively participate in PoS consensus validation in the subsequent phases.</p><p><strong>Of note</strong>, if the staker also holds the associated finality provider’s private key, this delegation is considered a self-delegation. In either case, only the voting power is delegated. <strong>The staked bitcoins are not transferred to the finality provider.</strong></p><h4>1.2 Phase-2: Bitcoin Staking Activation</h4><p>In this phase, a Babylon PoS chain will be launched to receive crypto-economic security from the bitcoins locked in Phase-1.</p><p>Upon launch, the finality providers with adequate delegations from Phase-1 will participate in Babylon PoS chain’s consensus by determining the finality of its blocks. The Babylon PoS chain will also enable the <a href="https://arxiv.org/pdf/2207.08392">Bitcoin timestamping protocol</a> for the cross-chain time synchronization needed for the security of Bitcoin staking.</p><h4>1.3 Phase-3: Bitcoin Multi-Staking Activation</h4><p>In this phase, the Babylon Bitcoin staking protocol will evolve into a marketplace for shared security, enabling any PoS systems to utilize Bitcoin staking security.</p><p>Bitcoin holders gain the ability to natively stake the same bitcoins across multiple PoS systems simultaneously, allowing them to earn multiple staking rewards. The Babylon PoS chain will act as the control plane that facilitates Bitcoin staking for all PoS systems.</p><h3>2. Phase-1 Details</h3><h4>2.1 Maximum Staking Time and On-Demand Unbonding</h4><p>During Phase-1, every stake is set with a maximum staking time (i.e., the time-lock in the Bitcoin staking script) of 64,000 Bitcoin blocks , which is approximately 15 months. This means that each stake will automatically expire and become available for withdrawal after this time period.</p><p>However, stakers can unbond their stake on-demand anytime before its expiration. There will be an on-chain unbonding period of 1008 Bitcoin blocks (roughly 7 days and defined in the unbonding Bitcoin script), after which the stake will expire and become available for withdrawal.</p><h4>2.2 Transactions Involved</h4><p>All transactions in Phase-1 are Bitcoin transactions, and include:</p><ul><li>Staking: To stake, Bitcoin stakers generate Bitcoin staking transactions and submit them to the Bitcoin blockchain.</li><li>Unbonding and early withdrawal: To unbond and withdraw a stake before its expiration, a staker will generate an unbonding transaction followed by a withdrawal transaction.</li><li>Automatic expiration and withdrawal: A stake will automatically expire after 64,000 Bitcoin blocks unless it was unbonded previously by the staker. To withdraw an expired stake, a staker will generate a withdrawal transaction.</li></ul><p>There are no other transactions or messages the stakers need to sign in Phase-1.</p><p>In particular, stakers will not sign a consent to PoS slashing. Thus, <strong>there is no slashing of staked bitcoin during Phase-1</strong>.</p><h4>2.3 Initial Total Staking Cap</h4><p>For security reasons, there will be an initial total staking cap of 1,000 bitcoins. This cap will be relaxed as Phase-1 progresses.</p><p><strong>First-come-first-served</strong>: Every stake is accepted on a first come, first served (FCFS) basis based on their order on the Bitcoin blockchain, until the cap is reached.</p><p><strong>Overflow and no-queuing</strong>: Stakes that arrive once the cap is reached will be treated as overflow, and should be unbonded and withdrawn. There is no staking queue, meaning that if the cap reopens once previously accepted stakes are unbonded, overflow stakes will not automatically fill the cap. Instead, new staking transactions must be submitted to refill the newly available cap capacity. This queue-less design is intended to discourage users from keeping overflow stakes in the system.</p><h4>2.4 Limits Per Staking Transaction</h4><p>Along with the initial 1,000 bitcoins total staking cap, there are also limits per staking transaction:</p><ol><li><strong>Minimum stake: 0.005 bitcoins</strong>. This is to ensure that the staking amount can cover the unbonding transaction fee (0.00064 bitcoins which will go to the Bitcoin miner) and withdrawal transaction fee (customizable by the staker).</li><li><strong>Maximum stake: 0.05 bitcoins</strong>. This intentionally small maximum is meant to encourage broad participation. It ensures that the entire cap will need at least a few Bitcoin blocks worth of staking transactions to fill. This prevents a single entity from buying out one Bitcoin block and taking the entire cap, squeezing everyone else out in the process.</li></ol><p>To further promote broad and genuine participation, excessive stake splitting is discouraged.</p><h4>2.5 Point System and Commissions</h4><p>There will be no direct staking reward given during Phase-1 as there is no active PoS chain yet. Instead, a point system will measure each staker’s activities, tracked by the staker’s public key.</p><p>During the initial 1,000-bitcoin cap, 3,125 Babylon points will be allocated per Bitcoin block. <strong>The 3,125 points will be allocated proportionally among all active stakes within that block.</strong> Stakes with a different status, such as overflow, unbonding, unbonded, and withdrawn, will not receive any points.</p><p>For each active stake, both its staker and finality provider will receive points, with the finality provider taking a cut based on its commission rate.</p><p><strong>Example:</strong> Once the 1,000-bitcoin cap is filled, an active stake of 0.05 bitcoins will earn 3,125*0.05/1,000 = 0.15625 points per Bitcoin block. If the finality provider charges a 5% commission, the staker will earn 0.15625*0.95 = 0.1484375 points per Bitcoin block and the finality provider will receive 0.15625*0.05 = 0.0078125 points per block while the stake is active. Over 4,000 Bitcoin blocks (about a month), assuming the cap stays full, then the staker would accumulate 4,000*0.1484375 = 593.75 points and the finality provider would accumulate 4,000*0.0078125 = 31.25 points from this stake.</p><p>The 3,125 points per Bitcoin block only applies during the initial 1,000-bitcoin cap. This, along with the staking cap, may be subject to future adjustments during Phase-1.</p><p><strong>Legal Note: </strong>points are not, and may never convert to, accrue to, be used as basis to calculate, or become any tokens or other digital assets. Points are virtual items with no monetary value. Points do not constitute any currency or property of any type and are not redeemable, refundable, or eligible for any fiat or virtual currency or anything else of value. Points are not transferable, and you may not attempt to sell, trade, or transfer any points, or obtain any manner of credit using any points. Any attempt to sell, trade, or transfer any points will be null and void, except as we may explicitly state otherwise in a written update to these rules on our website. We reserve the right to cancel, change, discontinue, limit, modify, or withdraw our points program (including the frequency, criteria, calculation or eligibility for earning such points), at any time with or without notice and regardless of any particular accumulation of points. Points may not be available in your jurisdiction.</p><p>You agree not to engage in any manipulative, fraudulent, dishonest, or abusive activities in connection with points or any distribution of digital assets by us or our affiliates. This includes, but is not limited to, creating multiple accounts to claim additional points or digital assets, using bots or scripts to automate claiming, or participating in any schemes that artificially inflate the number or perceived value of points or digital assets. We or our affiliates may terminate any or all of your points due to such activities, or for breaching any license granted by us, and may disclose privately and publicly why such action was taken.</p><h4>2.6 Covenant Committee</h4><p>In Phase-1, the covenant committee is a multi-signature verification scheme to secure the on-demand unbonding process. The committee’s task is to co-sign unbonding transactions submitted by stakers, allowing the committee to verify the transaction’s correctness and security.</p><p><strong>Note that, the covenant committee cannot steal the staker’s bitcoins, nor prevent the stake from expiration and becoming withdrawable, even if the committee is compromised</strong>.</p><p>The covenant committee operates as a 6-out-of-9 multi-signature scheme (meaning that 6 out of 9 keys are needed to sign the unbonding transaction after the staker submits an unbonding transaction), with each key being held by reputable entities from different sectors of the industry:</p><ul><li>AltLayer (1 key) — Rollup-as-a-Service provider</li><li>Babylon Labs (3 keys) — The core development team behind the project</li><li>CoinSummer Labs (1 key) — Affiliated with a top staking service provider (StakeFish) and a top mining pool (F2Pool)</li><li>Cubist (1 key) — Secure staking infrastructure provider</li><li>Informal Systems (1 key) — Cosmos ecosystem validator</li><li>RockX (1 key) — PoS validator and liquid staking provider</li><li>Zellic (1 key) — Security auditor</li></ul><h4>2.7 Ways to Stake</h4><p>There are a few ways to stake:</p><ul><li>Official web application: The official Bitcoin staking web application (<a href="https://btcstaking.babylonlabs.io/">btcstaking.babylonlabs.io</a>) provides a list of verified finality providers for stakers to delegate to. For information about how the finality providers register and are verified for Phase-1, please refer to the<a href="https://github.com/babylonlabs-io/networks/blob/main/bbn-1/finality-providers/README.md"> finality provider registration guide</a>.</li><li>Third-party services: such as third-party staking websites, custody solutions and APIs.</li><li><a href="https://github.com/babylonlabs-io/btc-staker/blob/v0.5.x/docs/create-phase1-staking.md">Command-Line Interface (CLI) tools</a>: Suitable for technically inclined users.</li></ul><p>There are also LST (liquid staking token) protocols that will participate in the Babylon Bitcoin staking mainnet. Please note that by participating in LST protocols, you do not directly participate in the Babylon Bitcoin staking mainnet, as the staking and points are both handled by the LST protocols.</p><p>Importantly, we do not review or endorse LSTs, LST code, or any other participants in the ecosystem including any third party services, so exercise caution and do your own investigations and research before using them. As a general rule, stakers must always conduct their own investigations and research before participating in the Bitcoin blockchain or in Bitcoin staking.</p><p>Any use of the web application <a href="https://btcstaking.babylonlabs.io/">btcstaking.babylonlabs.io</a>, or the <a href="https://babylonlabs.io/">Babylon Labs</a> website, or any of the content or materials there will be governed by the Terms of Use posted there at that time.</p><h4>2.8 Eligibility</h4><p>Staking is prohibited, and you will not receive points or staking awards, if you are:</p><p>(a) a resident or agent of, or an entity organized, incorporated or doing business in any country to which the United States, the United Kingdom, the European Union or any of its member states or the United Nations or any of its member states (collectively, the “Major Jurisdictions”) embargoes goods or imposes sanctions; or if you are, or if you directly or indirectly own or control, any person or entity that is listed on any sanctions list or equivalent maintained by any of the Major Jurisdictions; or</p><p>(b) a U.S. Person as defined in 17 CFR § 230.902, or currently or ordinarily located or resident in (or incorporated or organized in) the United States of America, Canada, Australia, or Mainland China.</p><p>This list may be updated from time-to-time without notice.</p><h3>3. Security Audits</h3><p>The Phase-1 codebase has been audited by the following entities:</p><ul><li>Coinspect:<a href="https://docs.babylonlabs.io/assets/files/coinspect-phase1-audit.pdf"> Audit Report</a></li><li>Zellic:<a href="https://docs.babylonlabs.io/assets/files/zellic-phase1-audit.pdf"> Audit Report</a></li><li>Cantina: Through a public security campaign, researchers and engineers reviewed the code and reported bugs and issues for bounties. <a href="https://docs.babylonlabs.io/assets/files/cantina-phase1-competition.pdf">Campaign Report</a></li></ul><p>Please appreciate that plans often need to be updated, revised, modified, or improved after a mainnet launch. Please return here often to check for updates, clarifications, or modifications.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9188a2a1bf46" width="1" height="1" alt=""><hr><p><a href="https://medium.com/babylonlabs-io/babylon-bitcoin-staking-mainnet-launch-phase-1-9188a2a1bf46">Babylon Bitcoin Staking Mainnet Launch: Phase-1</a> was originally published in <a href="https://medium.com/babylonlabs-io">BabylonLabs.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Babylon’s Bitcoin Staking Contract]]></title>
            <link>https://medium.com/babylonlabs-io/babylons-bitcoin-staking-contract-cc1a3d7236d5?source=rss-cfaf956ecd0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc1a3d7236d5</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[btc]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[staking]]></category>
            <dc:creator><![CDATA[Editor @ Babylon]]></dc:creator>
            <pubDate>Wed, 10 Jul 2024 08:23:33 GMT</pubDate>
            <atom:updated>2024-07-10T08:23:33.591Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zCFTOHdQZWrm5ljF.png" /></figure><p>In this article, we use the technical preliminaries introduced in the last article to construct Babylon’s trustless and non-custodial Bitcoin staking contract step-by-step.</p><h3>1.Recap</h3><p>🔸For Bitcoin to be a legit staking asset, it should at least be slashable and lockable, have a slashable unbonding period, and be delegatable.</p><p>🔸Bitcoins are represented as UTXOs. A Bitcoin holder can have multiple UTXOs and specify different spending conditions on different UTXOs using BTC scripts.</p><p>🔸The Schnorr signature algorithm supported by BTC:</p><ul><li>Has the property that the signer’s secret key is extractable if it uses the same nonce to sign two different messages. This makes it a potential EOTS (extractable one-time signature) signature algorithm that prevents equivocation.</li><li>Enables adaptor signature, where to spend a UTXO jointly owned by two persons, person-2 needs to obtain person-1’s Schnorr signature by decrypting person-1’s adaptor signature. But doing so will cause person-2’s Schnorr secret key to be extractable. Adaptor signature thus deters person-2 from spending this UTXO.</li></ul><p>Now, let’s assume a staker named Alice wants to stake 1 Bitcoin. To do so, she should create a UTXO worth 1 Bitcoin and specify its spending conditions through a Bitcoin script. This is effectively a staking contract. We will construct it step-by-step and also version it for easy indexing.</p><h3>2.Locking</h3><p>To achieve locking, Alice can simply apply a time lock to her staking UTXO:</p><pre>// Contract V0: adding a locking condition to Alice&#39;s staking UTXO<br><br>condition-1 (locking): time_lock = 1000 &amp; alice_public_key</pre><p>In the above contract, Alice locks her Bitcoin for 1000 Bitcoin blocks (about one week). Upon the expiration of the time lock, only Alice can spend it.</p><p>This simple condition provides a guaranteed exit for the staker. As long as the BTC network is live, Alice can get her 1 Bitcoin back even if everything else in the world goes offline.</p><h3>3.Slashing</h3><h3>3.1.Naive Slashing</h3><p>To achieve slashing, Alice needs to create a Schnorr key pair as her EOTS key pair <strong>[eots_secret_key, eots_public_key]</strong>. She then creates a new spending condition in the staking contract, and put the <strong>eots_public_key</strong> there:</p><pre>// Contract V1: adding naive slashing<br><br>condition-1 (locking): time_lock = 1000 &amp; alice_public_key; OR<br><br>condition-2 (slashing): alice_eots_public_key</pre><p>Alice can now use this EOTS key pair to provide attestations. For example, to cast her vote for a PoS chain-X at block height-1000:</p><ol><li>Alice generates a pair of <strong>[secret_nonce, public_nonce]</strong></li><li>Alice publicly declares in advance that for chain-X at height-1000, this <strong>public_nonce</strong> is the only one that verifies her vote. This way, no one will accept her vote signed using other pairs of nonces.</li><li>Once Alice verifies block-1000 and is happy with it, she uses the above <strong>secret_nonce</strong> and <strong>eots_secret_key</strong> to sign the block and publish the signature as the vote.</li><li>The public can verify the vote using Alice’s <strong>eots_public_key</strong> and the pre-declared <strong>public_nonce</strong>.</li></ol><p>Now, if Alice is malicous and wants to fork chain-X at height-1000, she will have to vote for another block-1000 using the same <strong>secret_nonce</strong> and <strong>eots_secret_key</strong>. Then whoever sees her both votes can decrypt her <strong>eots_secret_key</strong> and use <strong>condition-2</strong> above to withdraw Alice’s 1 Bitcoin, effectively causing Alice to be slashed.</p><p>In general, the above contract and the pre-declaration requirement, enables an anti-equivocation mechanism. If Alice equivocates in any types of decision making, her 1 Bitcoin can be slashed.</p><p><em>“Wait a second, this mechanism is very buggy!” </em>You may immediately recognize. Yes, it is just the beginning.</p><p>Let’s continue and fix it.</p><h3>3.2.Enforcing Burning</h3><p>A big problem of <strong>contract V1</strong> is that the slashing condition only requires Alice’s EOTS signature. Therefore, Alice can withdraw her 1 Bitcoin anytime via this condition to dodge slashing.</p><p>To solve this problem, we must ensure that when the staking UTXO is spent via the slashing condition, the staked Bitcoin can only be sent to a pre-defined burn address rather than to Alice. A sample burn address is <strong>0000…0000</strong>; no one knows the corresponding secret key, so funds in this address are not spendable.</p><p>Remember the mom figure in Article-2 who ensured that Alice could only send her Bitcoin to her dad before the time lock expired? The same mechanism applies here.</p><pre>// Contract V2<br><br>condition-1 (locking): time_lock = 1000 &amp; alice_public_key; OR<br><br>condition-2 (slashing): alice_eots_public_key &amp; covenant_committee_quorum<br><br><br>// Slashing transaction V0<br><br>inputs:<br>  - input-1: the staking UTXO, spent using condition-2 above<br><br>outputs:<br>  - output-1: value = 0.99 Bitcoin, owner = `0000...0000`<br><br><br>// Pre-approval V0: enforcing burning<br>//<br>// Covenant committee pre-signs the above slashing tx as its pre-approval</pre><p>Here we add a covenant committee quorum to the slashing condition, which is an <strong>M-out-of-N</strong> multi-signature. This means the UTXO is only spendable if at least <strong>M</strong> out of a committee of <strong>N</strong> covenant members agree to it.</p><p>To enforce the burn address, the covenant committee will only sign a slashing transaction that sends Alice’s 1 Bitcoin to the pre-defined burn address. This way, Alice cannot withdraw her 1 Bitcoin and dodge slashing. For this reason, the members should be chosen from the entities that don’t want Alice to dodge slashing, such as the PoS systems’ foundations.</p><p>Indeed, since Alice’s EOTS key is required in the slashing condition, except for enforcing burn address, there is no way the covenant committee can act against Alice:</p><ol><li>the covenant committee cannot steal Alice’s stake;</li><li>the covenant committee cannot cause Alice to be wrongly slashed, because no one except Alice herself knows her EOTS secret key if Alice is honest.</li></ol><p>Thus, Alice does not need to trust the covenant committee at all. Even a compromised covenant committee cannot harm Alice. The only thing it can do is to help Alice withdraw her stake her way.</p><h3>3.3.Enabling Safe Delegation</h3><p>Delegation looks intuitive. Alice can put a third-party validator’s EOTS public key in the slashing condition. This way, if the validator is malicious, Alice can be slashed.</p><p>However, from Alice’s perspective, such delegation is not safe. The delegated validator and the covenant committee may collude and steal her Bitcoin.</p><p>This problem is simple to solve. Alice can play the mom figure in Article-2 against the validator and the covenant committee by adding her own ordinary public key (not an EOTS one) to the slashing condition, too. Alice will only pre-sign a slashing transaction that sends her 1 Bitcoin to the pre-defined burn address, leaving no way for the delegated validator and covenant committee to collude and steal her stake.</p><pre>// Contract V3: enabling safe delegation<br><br>condition-1 (locking): time_lock = 1000 &amp; alice_public_key; OR<br><br>condition-2 (slashing): alice_public_key &amp; validator_eots_public_key &amp; covenant_committee_quorum<br><br><br>// Slashing transaction V0<br><br>inputs:<br>  - input-1: the staking UTXO, spent using condition-2 above<br><br>outputs:<br>  - output-1: value = 0.99 Bitcoin, owner = `0000...0000`<br><br><br>// Pre-approval V1<br>//<br>// Alice pre-signs the slashing tx as her pre-approval.<br>//<br>// Covenant committee pre-signs the slashing tx as its pre-approval.</pre><p>We have now completed the slashing condition of the staking contract. By involving three sets of signatures (staker, validator, covenant committee) in the slashing condition and asking the staker and covenant committee to only sign the slashing transaction that burns the stake, the system ensures that:</p><ul><li>No one can steal Alice’s stake;</li><li>If Alice or the validator she delegates to acts maliciously, her stake is slashed;</li><li>If Alice or the validator she delegates to acts honestly, her stake can never be slashed;</li><li>When slashing happens, the stake can only be sent to a pre-defined burn address rather than being withdrawn.</li></ul><p><em>“Something still seems wrong…” </em>You might feel.</p><p>Yes, you are sharp! There is a final piece of the puzzle: atomic slashing.</p><h3>3.4.Enforcing Atomic Slashing</h3><p>In the case of delegation, once Alice and the covenant committee give their pre-approval, the only signature needed to trigger the slashing condition is the delegated validator’s signature. If the validator goes rogue and has a beef with Alice, it can simply sign the slashing transaction and send it to BTC to get Alice slashed alone. No other stakes delegated to this validator will be affected.</p><p>Adaptor signature comes to the rescue. Alice can further encrypt her signature using the delegated validator’s EOTS public key and use the resulting adaptor signature as her pre-approval. This way, to target Alice, the validator will have to decrypt the adaptor signature using its own EOTS secret key, which will cause its EOTS secret key to be extracted. Once extracted, all the stakes delegated to it become slashable, including its self-delegated stake. Atomic slashing is thus achieved.</p><p>We can also request the covenant committee to sign the adaptor signature. This way, even if Alice is unable to generate adaptor signatures (e.g., due to a lack of wallet support), atomic slashing can still be achieved.</p><pre>// Contract V3<br><br>condition-1 (locking): time_lock = 1000 &amp; alice_public_key; OR<br><br>condition-2 (slashing): alice_public_key &amp; validator_eots_public_key &amp; covenant_committee_quorum<br><br><br>// Slashing transaction V0<br><br>inputs:<br>  - input-1: the staking UTXO, spent using condition-2 above<br><br>outputs:<br>  - output-1: value = 0.99 Bitcoin, owner = `0000...0000`<br><br><br>// Pre-approval V2: enforcing atomic slashing when delegate<br>//<br>// Alice&#39;s pre-approval is an adaptor signature of the slashing tx<br>// she generated using the validator&#39;s EOTS public key.<br>//<br>// Covenant committee pre-signs the slashing tx as its pre-approval.</pre><h3>3.5.Enabling Partial Slashing</h3><p>Slashing the entire stake sounds scary. Luckily, many PoS systems support partial slashing, in which only a small portion of each stake is slashed, and the rest is returned to the staker.</p><p>The refund comes at a delay to mitigate the re-entry attack, which is most prominent when the slashing portion is small. More specifically, malicious stakers could use the slashing mechanism as the exit to get its fund back and then immediately re-enter the system as a staker and attack again. A refund delay will significantly slow down such attacks.</p><p>Enabling partial slashing is simple in Bitcoin staking. Instead of having only one output that sends the entire stake to burn, the slashing transaction can have two outputs: one sends a portion of the stake to the burn address and the other returns the rest to Alice with a pre-defined time lock.</p><p>Below is an example where the slashing percentage is 10% and the refud delay is 500 BTC blocks. 0.9 Bitcoin should be returned to Alice after 500 BTC blocks. The 0.01 Bitcoin surplus there is the transaction fee.</p><pre>// Contract V3<br><br>condition-1 (locking): time_lock = 1000 &amp; alice_public_key; OR<br><br>condition-2 (slashing): alice_public_key &amp; validator_eots_public_key &amp; covenant_committee_quorum<br><br><br>// Slashing transaction V1: enabling partial slashing<br><br>inputs:<br>  - input-1: the staking UTXO, spent using condition-2 above<br><br>outputs:<br>  - output-1: value = 0.09 Bitcoin, owner = `0000...0000`<br>  - output-2: value = 0.9 Bitcoin,<br>              conditions:<br>              - condition-1: time_lock = 500 &amp; alice_public_key<br><br>// Pre-approval V2<br>//<br>// Alice&#39;s pre-approval is an adaptor signature of the slashing tx<br>// she generated using the validator&#39;s EOTS public key.<br>//<br>// Covenant committee pre-signs the slashing tx as its pre-approval.</pre><h3>4.Restaking</h3><p>Restaking means Alice (or her delegated validator) uses her 1 Bitcoin to participate in multiple PoS systems at the same time. If Alice (or her delegated validator) attacks any one of them, she will be slashed and removed from all of them.</p><p>A naive solution is for Alice (or her delegated validator) to use the same EOTS key to participate in all the interested PoS systems. This achieves the restaking slashing goal without changing the staking contract. However, this is extremely unsafe and highly unrecommended by the validator community because the accidental leakage of one single secret key will jeopardise all the delegated stakes of this validator across all the PoS systems secured by it.</p><p>Therefore, every validator should use a different EOTS key for each different PoS system. For example, if three validators validate four PoS systems, then there should be 12 EOTS keys.</p><p>Then, for Alice, restaking becomes simply choosing one EOTS key per PoS system she wants to restake to. To achieve this, we only need to extend the EOTS key field in the staking contract from accepting one key to accepting a list of keys and specify that the EOTS condition is met as long as any one of the keys signs.</p><pre>// Contract V4: Enabling restaking<br><br>condition-1 (locking): time_lock = 1000 &amp; alice_public_key; OR<br><br>condition-2 (slashing): alice_public_key<br>                        &amp; any signature from list [validator_eots_public_key]<br>                        &amp; covenant_committee_quorum<br><br><br>// Slashing transaction V1<br><br>inputs:<br>  - input-1: the staking UTXO, spent using condition-2 above<br><br>outputs:<br>  - output-1: value = 0.09 Bitcoin, owner = `0000...0000`<br>  - output-2: value = 0.9 Bitcoin,<br>              conditions:<br>              - condition-1: time_lock = 500 &amp; alice_public_key<br><br>// Pre-approval V2<br>//<br>// Alice&#39;s pre-approval is an adaptor signature of the slashing tx<br>// she generated using the validator&#39;s EOTS public key.<br>//<br>// Covenant committee pre-signs the slashing tx as its pre-approval.</pre><h3>5. Secure On-Demand Unbonding</h3><p>Article-2 explained that for stake unbonding to be secure, there should be an unbonding period, during which the stake must still be locked and slashable.</p><p>To achieve this, we need to turn Alice’s current stake (which has a long time lock) into a new stake (which has a shorter time lock equal to the unbonding time) and request Alice to pre-sign the corresponding new slashing transaction.</p><p>In addition, to enforce the above correct unbonding, we need to add a third spending condition (the unbonding condition) to the staking UTXO, which requires Alice’s and the covenant committee’s signatures.</p><p>More specifically:</p><ol><li>To prepare for unbonding, Alice will create a unbonding transaction that spends the original staking UTXO via this new 3rd condition. This unbonding transaction has a new staking UTXO that has a time lock equals to the unbonding period and a slashing condition same as the origin.</li><li>Alice then creates a new slashing transaction that spends the new staking UTXO.</li><li>Alice will then publish the unbonding transaction, the slashing transaction, and her pre-approval to the slashing transaction.</li><li>The covenant committee will review the above information and sign both the unbonding transaction and the new slashing transaction.</li><li>When Alice wants to execute the unbonding, she signs the unbonding transaction. Since both Alice’s and the covenant committee’s signatures are in place, Alice can submit the unbonding transaction to BTC to execute the unbonding.</li><li>After the shorter time lock expires, she can withdraw her Bitcoin.</li></ol><pre>// Contract V5: Enabling on-demand unbonding<br><br>condition-1 (locking): time_lock = 1000 &amp; alice_public_key; OR<br><br>condition-2 (slashing): alice_public_key<br>                        &amp; any signature from list [validator_eots_public_key]<br>                        &amp; covenant_committee_quorum<br><br>condition-3 (unbonding): alice_public_key &amp; covenant_committee_quorum<br><br><br>// Slashing transaction V1<br><br>inputs:<br>  - input-1: the staking UTXO, spent using condition-2 above<br><br>outputs:<br>  - output-1: value = 0.09 Bitcoin, owner = `0000...0000`<br>  - output-2: value = 0.9 Bitcoin,<br>              conditions:<br>              - condition-1: time_lock = 500 &amp; alice_public_key<br><br>// Pre-approval V2<br>//<br>// Alice&#39;s pre-approval is an adaptor signature of the slashing tx<br>// she generated using the validator&#39;s EOTS public key.<br>//<br>// Covenant committee pre-signs the slashing tx as its pre-approval.<br><br><br>// Unbonding transaction<br><br>inputs:<br>  input-1: the staking UTXO, spent using condition-3 above<br><br>outputs:<br>  output-1: value = 0.99 Bitcoin<br>            conditions:<br>              - condition-1 (locking): time_lock = 500 &amp; alice_public_key; OR<br>              <br>              - condition-2 (slashing): alice_public_key<br>                                        &amp; any signature from list [validator_eots_public_key]<br>                                        &amp; covenant_committee_quorum<br><br><br>// Slashing transaction of the unbonding transaction<br><br>inputs:<br>  - input-1: the unbonding UTXO, spent using condition-2 above<br><br>outputs:<br>  - output-1: value = 0.08 Bitcoin, owner = `0000...0000`<br>  - output-2: value = 0.9 Bitcoin,<br>              conditions:<br>              - condition-1: time_lock = 500 &amp; alice_public_key</pre><h3>6.Summary</h3><p>Woohoo! This is super intense, but we made it! We constructed a contract that turns Bitcoin into a first-class staking asset with all the properties one could wish for a staking asset: trustless, self-custodial, lockable, slashable (including partial slashing and atomic slashing), delegatable, restakable, and on-demand unbondable!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wZUJf3lLtOxtgUxo.png" /></figure><pre>Table of Contents<br>1. Recap<br>2. Locking<br>3. Slashing<br>  3.1 Naïve Slashing<br>  3.2 Enforcing Burning<br>  3.3 Enabling Safe Delegation <br>  3.4 Enforcing Atomic Slashing<br>  3.5 Enabling Partial Slashing<br>4. Restaking<br>5. Secure On-Demand Unbonding<br>6. Summary</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc1a3d7236d5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/babylonlabs-io/babylons-bitcoin-staking-contract-cc1a3d7236d5">Babylon’s Bitcoin Staking Contract</a> was originally published in <a href="https://medium.com/babylonlabs-io">BabylonLabs.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Babylon Ecosystem Update 2: Expanding Across DeFi]]></title>
            <link>https://medium.com/babylonlabs-io/babylon-ecosystem-update-2-expanding-across-defi-b2648d82926e?source=rss-cfaf956ecd0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2648d82926e</guid>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[ecosystem-building]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Editor @ Babylon]]></dc:creator>
            <pubDate>Fri, 14 Jun 2024 10:17:18 GMT</pubDate>
            <atom:updated>2024-06-14T10:17:18.511Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xxpRdGH474jgALn3.png" /></figure><p>This month, Babylon has launched several key initiatives and formed strategic alliances that are unlocking Bitcoin’s full potential. From making BTC liquidity more accessible to increasing yield and security. Read on as we detail the major happenings for Babylon’s ecosystem!</p><h3>Testnet Progress</h3><p>On May 28, we successfully launched the Babylon Bitcoin Staking Testnet-4 to stress-test the security of staked Signet Bitcoin by evaluating user interactions with the Signet BTC test network. The initial cap was filled in less than 20 minutes!</p><p>More than <a href="https://x.com/babylon_chain/status/1795395963378430459">70 finality providers</a> have been onboarded to strengthen the system and provide steadfast support from the testament and onwards. <a href="https://x.com/babylon_chain/status/1795408112679313832">Six wallets</a> also supported Babylon at the testnet launch.</p><p>To educate our community, we launched a “<a href="https://babylonchain.io/blog/what-is-bitcoin-staking">Bitcoin Staking 101</a>” blog series that details how Bitcoin staking works. We also initiated the <a href="https://babylonchain.io/blog/embark-on-the-bitcoin-staking-chronicles">BTC Chronicles</a>, the community campaign competition from testnet to mainnet, enabling Babylonians to climb the leaderboard, rank, and support Babylon.</p><h3>Strategic Alliances Unleash Bitcoin’s $1T Potential</h3><p>Babylon’s ecosystem continues to gain traction, as major DeFi projects with a deep passion to innovate with and benefit from Bitcoin integrate with Babylon.</p><h3>Bedrock &amp; pStake: Liquid Staking Pioneers</h3><p>Bedrock has <a href="https://x.com/Bedrock_DeFi/status/1790040304193585528">launched</a> uniBTC, a liquid Bitcoin restaking token built on Babylon. This breakthrough allows BTC holders to finally earn rewards on their holdings while maintaining liquidity — a game-changer for unlocking Bitcoin’s $1T capital.</p><p>At the forefront is Bedrock’s uniBTC — a liquid Bitcoin restaking token allowing holders to earn yield while retaining liquidity. Similarly, <a href="https://x.com/pStakeFinance/status/1790729012098023823">pStake</a> aims to catalyze growth in BTCfi by providing BTC holders a path to staking yields through their liquid staking solution on Babylon.</p><h3>Mind Network: Encryption Powers Security</h3><p>Mind Network is <a href="https://x.com/mindnetwork_xyz/status/1791046728030032202">leveraging</a> Babylon’s Bitcoin LSTs combined with their cutting-edge Fully Homomorphic Encryption (FHE). This allows secure, trustless validation of PoS networks and subnets without exposing private keys. FHE is hailed as the “holy grail” of cryptography. It enables computation on encrypted data, a critical innovation for bringing Bitcoin’s unmatched security to consensus layers while preserving decentralization.</p><h3>Chakra: Unlocking $1T With ZK-Proofs</h3><p>The Chakra ZK-Rollup takes Bitcoin security to its network, bringing security to new heights by <a href="https://x.com/ChakraChain/status/1793570757064499639">integrating</a> the Babylon Bitcoin staking protocol. By using ZK-STARK proofs to map staked BTC across any ecosystem, this unprecedented interop unlocks Bitcoin’s $1T-plus liquidity stream.</p><h3>Merlin: Expanding Utility of MerlinBTC</h3><p>The Merlin L2 is <a href="https://x.com/MerlinLayer2/status/1793628288499560541">merging</a> Bitcoin’s security into its chain via the Babylon Bitcoin staking protocol. Merlin users can stake native mBTC via Babylon, extending the foundation of Bitcoin’s immense proof-of-work consensus to bolster the security of any network and chain. This allows Merlin’s ecosystem of Rollups, dApps, and services to tap into the endless stream of security capital from Bitcoin.</p><h3>Cobo: Robust API for Mass Adoption</h3><p>On the infrastructure front, wallets like Cobo have launched the first dedicated APIs to <a href="https://x.com/Cobo_Global/status/1792922210484510834">integrate Bitcoin staking</a> through the Babylon protocol in just 30 minutes! Cobo’s industry-leading MPC wallet solution provides a seamless onramp, accelerating mass adoption as the BTC DeFi summer kicks into high gear.</p><p>Their comprehensive APIs for staking workflows vastly reduce the complexity of joining Babylon’s thriving ecosystem.</p><h3>Game Plus: the Future of Bitcoin Gaming and Social Ecosystem</h3><p>Game Plus is building infrastructure for gaming on the Bitcoin blockchain, <a href="https://medium.com/@gameplus.official/game-plus-collaborates-with-babylon-to-pioneer-the-future-of-bitcoin-gaming-and-social-ecosystem-25a304505963">leveraging</a> the Babylon Bitcoin staking protocol. Their Layer 2 solution uses Optimistic rollups and ZK proofs secured by the Babylon enabled Bitcoin staking. Game Plus provides SDKs to simplify deploying Bitcoin-based games with features like asset management and wallets.</p><h3>Particle Network: Securing their L1</h3><p>Particle Network is a modular Layer 1 blockchain aiming to enable “chain abstraction” by allowing users to interact across multiple chains. They are <a href="https://blog.particle.network/were-joining-forces-with-babylon-to-secure-our-l1/">integrating</a> Babylon’s Bitcoin staking as part of a “Dual Staking” security model where transactions are validated by both native tokens and Bitcoin stakers.</p><h3>Another Wallet Supporting Babylon: Tomo</h3><p>The infrastructure around Babylon continues to grow, with Tomo Wallet being the latest wallet<a href="https://x.com/tomo_social/status/1795038783622316107"> to support the Babylon Bitcoin staking protocol</a>. Tomo has launched its extension wallet integrated with Babylon Testnet, allowing users to stake sBTC (Signet Bitcoin) on Babylon directly from the wallet. Tomo Wallet provides a seamless login experience using Google accounts and prioritizes security by encrypting seed phrases using Shamir’s Secret Sharing.</p><h3>Conclusion</h3><p>With each innovative alliance, Babylon’s vision of unleashing Bitcoin’s vast potential through staking takes another monumental stride. The future utility of the world’s largest cryptocurrency is finally coming into focus!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2648d82926e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/babylonlabs-io/babylon-ecosystem-update-2-expanding-across-defi-b2648d82926e">Babylon Ecosystem Update 2: Expanding Across DeFi</a> was originally published in <a href="https://medium.com/babylonlabs-io">BabylonLabs.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Forkless Rollups with Bitcoin Staking]]></title>
            <link>https://medium.com/babylonlabs-io/forkless-rollups-with-bitcoin-staking-a99eeea595d4?source=rss-cfaf956ecd0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a99eeea595d4</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[staking]]></category>
            <dc:creator><![CDATA[Editor @ Babylon]]></dc:creator>
            <pubDate>Fri, 14 Jun 2024 10:14:48 GMT</pubDate>
            <atom:updated>2024-06-14T10:14:48.160Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VtyhJtjrsTkAMUnU.png" /></figure><p><strong>TL;DR</strong></p><ul><li>Babylon proposes using <a href="https://docs.babylonchain.io/papers/btc_staking_litepaper(EN).pdf">Bitcoin staking</a> to achieve fast finality in rollups.</li><li>The solution entails the sequencer locking up BTC stake that is slashable if they attempt forking attacks.</li><li>It enables faster finality and economic security, unlocking high-value DeFi applications.</li><li>The solution can also lead to a stronger design for decentralized sequencing.</li></ul><h3>Introduction</h3><p><a href="https://docs.babylonchain.io/papers/btc_staking_litepaper(EN).pdf">Bitcoin Staking</a> introduced by the Babylon protocol is poised to be instrumental in enhancing the economic security of Proof-of-Stake (PoS) blockchains while simultaneously providing a way for BTC holders to use their coins. BTC holders contribute to security by staking and delegating to their preferred validator of compatible PoS chains, such as the Babylon chain. While many of these PoS blockchains are independently secured Layer 1s (L1s), not all transactions are suitable to be processed on L1s and there are fundamental limits to scaling blockchains directly without performing the bulk of transactions off-chain (on Layer 2).</p><p>Rollups have emerged as a promising solution to these scalability challenges faced by L1 blockchains like Ethereum. In theory, rollups inherit the security of the L1 by executing transactions off-chain on L2 and committing the resulting state to the main L1 chain for validation and finality. However, rather than waiting for L1 confirmation and validation, which can take minutes for ZK rollups or weeks for optimistic rollups, most users opt to trust transaction confirmations directly from the centralized L2 sequencer. This reliance on the sequencer for fast finality introduces centralization risks and opens the door to potential attacks that threaten the entire system’s integrity.</p><p>In this blog post, we will outline the problem with today’s rollup architectures while introducing the solution enabled through Bitcoin staking.</p><h3>The Sequencer Problem</h3><h3>Rollups Recap</h3><p>The key idea behind rollups is to execute transactions (computation) off-chain while still inheriting the security properties of L1 for data storage and settlement. Doing so reduces the burden on L1, reduces friction, and increases throughput/scalability. The rollup sequencer plays a key role in that, as it is responsible for submitting L2 blocks to L1. Existing rollups require that the sequencer stakes some coins, which are slashed if it submits an invalid block. However, increased throughput shouldn’t come at the expense of security…</p><h3>The Threat of Forking Attacks</h3><p>With current models, i.e., zero-knowledge (ZK) rollups and optimistic rollups, users who require fast finality must not only trust that the sequencer submits valid states to the L1 but also that the states it sends to users match the ones it submits, i.e., that it does not attempt a forking attack. The submission of invalid blocks and forks are all possible safety violations that the sequencer can commit.</p><p>Under a forking attack, the sequencer sends one block version (including a crucial transaction) directly to a specific user while committing a different version (without that transaction) to the L1. Imagine the sequencer including a transaction to pay for a car in the block sent to the user but omitting it in the block committed to the L1 chain. This enables double-spending attacks, as the user sees their transaction included, but the committed state does not reflect it.</p><p>Satoshi Nakamoto introduced Bitcoin as a payment system, the solution to the double-spend problem, stating in the introduction of the Bitcoin Whitepaper:</p><p><em>“Digital signatures provide part of the solution, but the main benefits are lost if a trusted third party is still required to prevent double-spending. We propose a solution to the double-spending problem using a peer-to-peer network.”</em></p><p>However, this exact problem persists with most rollup L2s, leaving us without any progress.</p><p>Existing mechanisms like ZK proofs and dispute periods cannot detect or prevent such attacks by the sequencer. A user’s only protection against forks is to wait for every L2 block to be confirmed on L1 before accepting it as final, which incurs unacceptable latencies of several minutes (e.g., around 12.5 minutes for Ethereum). These lengthy confirmation times preclude many applications.</p><h3>The Centralization Bottleneck</h3><p>For parties that require fast finality and cannot wait for full L1 confirmation, relying on a single, trusted sequencer reintroduces a centralized point of failure and bottleneck. They are exposed to the risks of theft, double-spending, and censorship if the sequencer is malicious, reducing the system’s security guarantees to that of a legacy centralized payment processor. This centralization bottleneck also restricts the types of applications that can be built on top of rollups. High-value applications (such as real-time gambling, high-frequency trading, and high-stakes sports) that require strong security guarantees and fast finality (sub-second latency) will find it risky to deploy on current rollup systems due to the inherent trust assumptions and vulnerabilities introduced by the sequencer model.</p><p>Addressing the problem is crucial for unlocking the full potential of rollups and enabling a wide range of decentralized applications while upholding the core principles of trustlessness and censorship resistance.</p><h3>Reducing Latency with Bitcoin Staking</h3><p>Our protocol aims to improve rollup latency by increasing security assurances for users who consider sequencer blocks final before they are settled on L1. By doing so, we help close the security gap for those who require fast finality (sub-second latency). With staking bitcoins as collateral, we address the sequencer problem and enhance the security of rollups. Slashing mechanisms punish the sequencer for all possible safety violations, namely forks (in the case of optimistic rollups), creating a financial penalty that should disincentivize any sequencer from ever committing such attacks.</p><h3>The Solution in Action</h3><p>Here’s how the proposed solution works, protecting against fork (and subsequent double-spend) attacks:</p><p>The sequencer locks up a predefined collateral on the Bitcoin chain. For each L2 block, the sequencer adds a finality signature. If the sequencer publishes two conflicting blocks for the same height, any party that sees both blocks can extract a secret from the two finality signatures and slash the sequencer. The rollup smart contract on L1 verifies the finality signature before accepting an L2 block, incentivizing the sequencer to publish only one L2 block.</p><p>The proposed solution establishes slashable safety guarantees against forks, introducing economic security and protecting against double-spending. Existing optimistic systems require a non-intrusive code update to the current sequencer and rollup, as the only change to the rollup smart contract on the L1 is adding a verification of the finality signature before accepting a new L2 block.</p><p>Bitcoin Staking allows BTC holders to delegate collateral to the sequencer to provide economic security against forks. Bitcoin holders have the opportunity to earn yield while contributing to the security and faster finality of the rollup instead of waiting weeks for the dispute period to conclude on the L1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8w1v4LhVkiH7E272.jpg" /></figure><p>Because the sequencer is economically disincentivized from dishonest behavior, users achieve finality within seconds. Rollup users can enjoy the usability benefits of fast confirmations without having to fully trust the sequencer. In addition, honest sequencers and their delegators gain yield from providing the collateral.</p><h3>A Path to a More Secure and Decentralized Ecosystem</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YVNiusDNYIZ9ab6n.png" /></figure><p>The solution outlined paves the way for greater security and usability of rollup systems by mitigating the main threat posed by the sequencer, which remained up until now unaddressed. Introducing economic incentives and punishments aligns the interests of the sequencer with those of the users, reducing the need for blind trust. This solution introduces added collateral security with slashability guarantees. To continue in the path of sequencer innovation, rollups can also decentralize the sequencer, creating a set of nodes or finality providers competing with each other to validate information before submitting the data to the L1.</p><h3>Decentralizing the Sequencer with Finality Providers</h3><p>A committee of finality provider (FP) nodes collectively validate and sign off on each L2 block before it can be committed to the L1. If the sequencer proposes two competing blocks, the FPs that sign both will be slashed. Even if the original sequencer is malicious, the committee of FPs provides a holistic checkpoint, ensuring attempts at forking are rejected before being committed on-chain. Consequently, FPs provide the following extra security guarantees to L2:</p><ul><li>Safety: When there are at least 1/3 honest finality providers, there is no forking.</li><li>Slashable safety: If a safety violation, such as a fork, occurs, at least ⅓ BTC stake can be irrefutably identified as adversarial and slashed.</li><li>Protection against invalid blocks: Since FPs should connect to an honest L2 full node to retrieve and sign valid L2 blocks, our design offers extra protection against invalid blocks. When there are at least 1/3 honest FPs, no invalid L2 blocks will be finalized.</li></ul><p>Unlike having FPs individually re-execute transactions (which would increase latency), this design boosts security guarantees with fast finality by making the FPs slashable, retaining better latency than waiting for full L1 confirmation. Distributing this critical responsibility across a decentralized set of economic actors aligns incentives toward consensus on a single canonical chain without putting any centralized party in control.</p><h3>The Key Benefits of Bitcoin Staking for Rollups</h3><ol><li>Fast Finality &amp; Enhanced Security: The solution enables faster finality by introducing a slashing mechanism based on Bitcoin staking that disincentivizes malicious behavior, significantly improving security and protecting users from various attacks, including double-spend attempts. With faster finality, it also makes the rollup more suitable for high-stake applications that require rapid transaction confirmation, such as decentralized finance (DeFi) and gaming applications.</li><li>Decentralization: With the possibility of distributing the responsibility of finality among multiple FPs, this proposed solution reduces the centralization risk associated with a single sequencer, fostering a more decentralized system. Requiring multiple FPs however, does come at the cost of increased latency.</li><li>Democratization: The delegation feature of Bitcoin staking also introduces democratization. More specifically, it allows a broad spectrum of BTC holders to participate in the rollup’s consensus by delegating their voting power to finality providers. With Bitcoin staking for rollups, BTC holders can contribute to the security of rollups on other chains by delegating and increasing the collateral, earning yield in return. This allows for democratization of the sequencer role without incurring the latency costs associated with a fully decentralized sequencer solution. A decentralized committee of sequencer nodes would need to go through a more complex process to agree on each rollup block, inevitably increasing finality times.</li></ol><h3>Conclusion</h3><p>With Bitcoin staking collateral used to enhance rollup security, fundamental issues in the current rollup ecosystem are addressed. By introducing slashing mechanisms and economic incentives, the risk of malicious behaviors can be mitigated, and strong security guarantees can be enabled.</p><p>For those requiring fast finality rather than waiting minutes or weeks, the solution unlocks a new realm of possibilities for high-value applications that demand rapid transaction confirmation and finality. This paves the way for decentralized finance (DeFi), gaming platforms, and other innovative use cases to flourish on top of secure, trustless rollup systems. Stay tuned as Babylon’s BTC Rollups Litepaper will be released, diving deeper into Forkless Rollups.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a99eeea595d4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/babylonlabs-io/forkless-rollups-with-bitcoin-staking-a99eeea595d4">Forkless Rollups with Bitcoin Staking</a> was originally published in <a href="https://medium.com/babylonlabs-io">BabylonLabs.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Babylon Bitcoin Staking Testnet-4 Launch]]></title>
            <link>https://medium.com/babylonlabs-io/babylon-bitcoin-staking-testnet-4-launch-3c7fe3979827?source=rss-cfaf956ecd0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c7fe3979827</guid>
            <category><![CDATA[testnet-launch]]></category>
            <category><![CDATA[staking]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Editor @ Babylon]]></dc:creator>
            <pubDate>Mon, 27 May 2024 08:20:03 GMT</pubDate>
            <atom:updated>2024-05-27T08:20:03.749Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EDAm9ubRYCCWjtWjmF3O0w.png" /></figure><p>We are excited to announce the launch of Babylon Bitcoin Staking Testnet-4 on Tuesday, May 28, 2024.</p><p><strong>Key Dates and Times:</strong></p><ul><li><strong>Staking Web Dapp:</strong> The staking web dapp (<a href="http://btcstaking.testnet.babylonchain.io/">btcstaking.testnet.babylonchain.io</a>) will go live at 7 AM UTC on May 28, 2024. This is to allow users to get familiar with the Dapp and connect wallet.</li><li><strong>Protocol Activation:</strong> Staking will be enabled at Signet BTC block height 197,535, expected at about 9 AM to 10 AM UTC on the same day.</li></ul><p><strong>Testnet Focus:</strong> This testnet aims to focus on the security of staked Signet Bitcoins by testing user interactions with the Signet BTC test network. Key participants, including Bitcoin holders, validator teams, wallet providers, custodians, and liquid (re)staking protocols, will have the opportunity to explore and evaluate Bitcoin staking.</p><p>Please note:</p><ul><li>There will be no PoS test chain, PoS test staking rewards, or slashing.</li><li>Signet Bitcoin is a simulated currency for testing purposes only. It carries any monetary value, and it is not redeemable or tradable.</li></ul><p><strong>Staking Details:</strong></p><ul><li><strong>Staking Period:</strong> Signet Bitcoin holders will be required to stake their assets for a fixed period of ~64 weeks.</li><li><strong>Unbonding Time:</strong> Stakers can unbond and withdraw their stake at any time, with an unbonding period of 7 days.</li><li><strong>Staking Limits:</strong> The initial total staking cap is set at 5 Signet Bitcoin. The minimum stake per transaction is 0.0005 Signet Bitcoin, and the maximum is 0.05 Signet Bitcoin. These limits are set to manage flow control given the limited supply of Signet Bitcoins.</li></ul><h3>Fun to Participate</h3><p>Please use this testnet as a playground to explore Bitcoin staking. We encourage you to try out all the features (stake, unbond, and withdraw). In addition,</p><ol><li>stakers can participate in our Bitcoin Staking Chronicles campaign on Galxe: <a href="https://app.galxe.com/quest/Babylon/GCyyntz73L">Bitcoin Staking Chronicles by Babylon | Galxe</a>.</li><li>security researchers and engineers are welcomed to participate in our Cantina security campaign (<a href="https://cantina.xyz/competitions/b7c7def5-1033-4a4c-809d-08e507fb3583">Competitions | Cantina</a> ).</li></ol><h3>Useful Links</h3><ol><li>Introductory readings: Bitcoin staking 101 series <a href="https://babylonchain.io/blog/what-is-bitcoin-staking">BabylonChain — What is Bitcoin Staking?</a></li><li>Discord Signet Bitcoin faucet: <a href="https://discord.com/invite/babylonglobal">Join the Babylon🔶🔒 Discord Server!</a> (Get verified &amp; gain access to our │faucet-signet-btc channel).</li><li>Finality provider guide: <a href="https://github.com/babylonchain/networks/tree/main/bbn-test-4/finality-providers">networks/bbn-test-4/finality-providers at main · babylonchain/networks</a></li><li>Open-sourced code of the staking web dapp for this testnet: <a href="https://github.com/babylonchain/simple-staking">GitHub — babylonchain/simple-staking: Simple staking application</a></li><li>Wallet integration guide: <a href="https://github.com/babylonchain/networks/blob/main/bbn-test-4/integration/wallet.md">networks/bbn-test-4/integration/wallet.md at main · babylonchain/networks</a></li><li>Specification of all the transactions: <a href="https://github.com/babylonchain/babylon/blob/dev/docs/transaction-impl-spec.md">babylon/docs/transaction-impl-spec.md at dev · babylonchain/babylon</a></li><li>Swagger API doc: <a href="https://github.com/babylonchain/networks/blob/main/bbn-test-4/integration/wallet.md">networks/bbn-test-4/integration/wallet.md at main · babylonchain/networks</a></li><li>Staking backend service build guide: <a href="https://github.com/babylonchain/networks/blob/main/bbn-test-4/integration/staking-backend.md">networks/bbn-test-4/integration/staking-backend.md at main · babylonchain/networks</a></li><li>To provide feedback or report bugs or issues: our Forum: <a href="https://forum.babylonlabs.io/c/testnet/41">🛠️Testnet</a> and our Discord :<a href="https://discord.com/invite/babylonglobal">Join the Babylon🔶🔒 Discord Server!</a> (│feedback &amp; │testnet-support channels).</li></ol><p>We look forward to your participation in this important testnet launch.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c7fe3979827" width="1" height="1" alt=""><hr><p><a href="https://medium.com/babylonlabs-io/babylon-bitcoin-staking-testnet-4-launch-3c7fe3979827">Babylon Bitcoin Staking Testnet-4 Launch</a> was originally published in <a href="https://medium.com/babylonlabs-io">BabylonLabs.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Quest for Utility: BTC Staking Ecosystem Update]]></title>
            <link>https://medium.com/babylonlabs-io/the-quest-for-utility-btc-staking-ecosystem-update-4a6ec7266ff0?source=rss-cfaf956ecd0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a6ec7266ff0</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ecosystem-building]]></category>
            <category><![CDATA[staking]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Editor @ Babylon]]></dc:creator>
            <pubDate>Wed, 15 May 2024 14:07:21 GMT</pubDate>
            <atom:updated>2024-05-15T14:07:21.855Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pdPgA93rBHvVG-56AwWBVg.jpeg" /></figure><p>The pursuit of unlocking Bitcoin’s true potential as more than just a store of value has been a longstanding quest in the crypto realm. For years, the industry has sought to push the boundaries of Bitcoin innovation. Part of this has been exploring ways to harness the power and security of the world’s largest $1 trillion cryptocurrency to drive real-world utility. This quest has led to the Babylon BTC Staking protocol, redefining the role of Bitcoin in the decentralized economy.</p><p>The Babylon Staking Protocol allows Proof-of-Stake (“PoS”) systems such as PoS chains, L2 rollups, Data Availability (DA) layers, and oracles to acquire staking capital from Bitcoin, the largest decentralized crypto asset in the world. Through its modular design and slashing functionality, The Babylon Staking Protocol will enable PoS systems to introduce Bitcoin as a staking asset and enjoy higher crypto-economic security than native tokens can provide. As a result, PoS systems will be able to utilize Babylon’s scalable staking and restaking features to unlock value from the idle, unencumbered $1 trillion Bitcoin ecosystem.</p><p>This blog will highlight our growing ecosystem joining us to enable a Bitcoin-secured decentralized economy. By joining, they are set to unlock the full potential of Bitcoin security.</p><h3>Bedrock, Nomic, and Solv: Liquid Staking Tokens for Staked Bitcoin</h3><p>Bedrock is launching a liquid restaking token called uniBTC on top of The Babylon Staking Protocol. Bedrock aims to build a one-click liquid restaking solution for BTC and WBTC and has already launched a successful liquid restaking solution for EigenLayer and IoTeX.</p><p>Additionally, Solv is a yield and liquidity infrastructure layer backed by Binance Labs and Blockchain Capital that leverages The Babylon Staking Protocol. They are launching SolvBTC, a yield-bearing liquid restaking token for Bitcoin where users will stake Bitcoin to Solv to receive SolvBTC.</p><h3>Lorenzo Protocol: Redefining Bitcoin DeFi</h3><p>Lorenzo Protocol, a project redefining the Bitcoin DeFi landscape, <a href="https://medium.com/@lorenzoprotocol/lorenzo-protocol-integrates-babylonchain-to-build-bitcoin-application-layer-609f6755f331">announced</a> its integration with the protocol as part of its pursuit to build a scalable and performant Bitcoin application layer. This synergy ensures that all Bitcoin assets are compatible with Lorenzo’s modular L2, enabling the use of Bitcoin not only for storing critical asset data but also for providing unparalleled security to users.</p><h3>Persistence One: Maximizing Yield and Security</h3><p>Since April 2023, Persistence One has been a part of Babylon’s Timestamping testnet. Persistence One is a purpose-built Layer 1 on a mission to maximize yield and security through Liquid Staking and Restaking. Their mission perfectly aligns with Babylon, as it greatly improves their ecosystem, bolstering the capital staked and security threshold. With Babylon, Persistent One ensures its ecosystem has the highest level of security.</p><h3>AltLayer &amp; B2 — Consuming Security to Bolster New Use Cases</h3><p>The rapid expansion of Babylon’s ecosystem goes across both the supply and demand side, whereby Babylon’s impact extends beyond just enabling staking. Several projects also tap on the staked Bitcoin to enhance their security and drive further utility. This represents the demand side leveraging Bitcoin’s robust security facilitated by Babylon:</p><p>AltLayer is a decentralized verification layer for rollups, collaborating with Babylon to build rollup infrastructure secured by staked BTC. This allows rollups to achieve decentralized verification, better latency, and improved interoperability. B² network incorporates Babylon’s BTC Staking functionality in the B² Rollup, supporting the BTC LSD and Restaking use cases for Rollups. Additionally, their B² Hub utilizes Babylon’s Bitcoin timestamping protocol to avoid long-range attacks on the PoS consensus mechanism. After the Babylon BTC Staking mainnet launch, B² Rollup will enable users to directly stake their BTC on the Bitcoin network through Babylon to participate in securing the B² Network.</p><h3>Glacier, Automata, Yala and Hana Network: Bolstering Security, Accessibility and Research</h3><p>Other key projects have integrated and collaborated with Babylon to enhance security, accessibility, and research. Glacier Network <a href="https://medium.com/@glacierlabs/babylon-integrates-with-glacier-network-to-build-enhanced-validator-network-564e66496da1">integrated</a> with Babylon to strengthen and expand its validator network using Babylon’s Bitcoin staking. Automata Network has <a href="https://blog.ata.network/automata-collaborates-with-babylon-to-advance-tee-research-and-enhance-multi-prover-security-with-5f49d7d38ace">collaborated</a> to advance Trusted Execution Environment (TEE) research and enhance multi-prover rollup security leveraging staked Bitcoin. Hana Network has integrated to allow seamless Bitcoin restaking through its gateway while benefiting from Babylon’s robust security. The modular Yala layer for Bitcoin has integrated Babylon to build an interoperable Bitcoin ecosystem extending its proof-of-work security to PoS chains and rollups.</p><h3>Conclusion</h3><p>The rapid expansion of Babylon’s ecosystem shows Bitcoin’s untapped potential. By enabling Bitcoin holders to stake their bitcoins securely and earn yields while bolstering the security of PoS systems and more, Babylon is paving the way for a future where Bitcoin’s utility extends far beyond its traditional role as a store of value.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a6ec7266ff0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/babylonlabs-io/the-quest-for-utility-btc-staking-ecosystem-update-4a6ec7266ff0">The Quest for Utility: BTC Staking Ecosystem Update</a> was originally published in <a href="https://medium.com/babylonlabs-io">BabylonLabs.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Babylon Testnet-4 Pre-Launch Announcement]]></title>
            <link>https://medium.com/babylonlabs-io/babylon-testnet-4-pre-launch-announcement-234ea3fa9077?source=rss-cfaf956ecd0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/234ea3fa9077</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[staking]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Editor @ Babylon]]></dc:creator>
            <pubDate>Wed, 15 May 2024 14:05:45 GMT</pubDate>
            <atom:updated>2024-05-15T14:05:45.612Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xs23lTDAj4jUIJ94KYpVKw.png" /></figure><p>The Babylon team plans to launch a new testnet towards the end of May 2024. This announcement explains the purpose of this testnet and how to prepare for it.</p><h3>Why Babylon Testnet-4?</h3><p>Our current testnet, bbn-test-3, allows Bitcoin stakers to engage in a full range of activities including staking, unbonding, withdrawing, claiming rewards, and experiencing the slashing mechanism. We will sunset it at 12PM UTC 16/May/2024. Of course, it is only a testnet and no real BTC were used.</p><p>Community feedback has been very positive on the user experience so far, while also emphasizing a key consideration for participating in such as protocol: the security of their staked Bitcoins. Users want assurance that their Bitcoin won’t be stolen, can unbond and withdraw anytime, and won’t be slashed.</p><p>Therefore, the new testnet (bbn-test-4) will focus on the security of the staked Bitcoins by testing the user’s interaction with the BTC Signet test network.</p><h3>Key Features</h3><p>Here’s what this means for users:</p><ul><li>This testnet will only involve BTC Signet test network without a Babylon PoS test chain.</li><li><strong>Simplified interaction</strong>: Bitcoin stakers can stake, unbond, and withdraw by submitting the corresponding transactions to BTC Signet test network via the staking web dapp.</li><li><strong>No slashing</strong>: Bitcoin stakers are not requested to sign any slashing related authorisations, which means slashing will be disabled.</li><li><strong>No PoS reward</strong>: Since there is no Babylon PoS test chain, the test staking reward feature will not be applicable.</li><li><strong>No voting</strong>: For the same reason, finality providers will only need to publish their EOTS public key to allow stake delegation. They do not need to actively maintain any programs (such as node and finality provider daemons).</li></ul><p>In addition,</p><ul><li><strong>Finality provider registration</strong>: To counter spams while preserving decentralisation, for a finality provider to be included in the initial list of finality providers in the staking web dapp, we request the finality provider to deposit a small amount of Signet Bitcoin and submit a PR to a dedicated Github registry repo before the testnet launch (see instructions below).</li><li><strong>Staking cap</strong>: We will apply gradually increasing staking caps, starting with 5 sBTC, to control Signet Bitcoin ingress while testing the system through security audit and public security campaign.</li></ul><h3>Preparation</h3><p><strong>Bitcoin stakers</strong>: If you are interested in participating, please consider unbonding and withdrawing your Signet Bitcoin from the existing testnet (<a href="http://btcstaking.babylonchain.io/">btcstaking.babylonchain.io)</a>. We will also reopen Discord faucet very soon.</p><p><strong>Finality providers</strong>: Please read this guide (<a href="https://github.com/babylonchain/networks/tree/main/bbn-test-4/finality-providers">networks/bbn-test-4/finality-providers at main · babylonchain/networks</a> ) to register yourself if you would like to appear in the initial finality provider list of the staking web dapp with proper information display (name, logo, etc).</p><h3>Final Notes</h3><p>This testnet is NOT incentivised. Its purpose is to allow interested parties to evaluate and get familiar with Bitcoin staking related operations.</p><p>We would also like to emphasise that Signet Bitcoin is only a simulated Bitcoin for testing that can be used only for the BTC Signet test network. It does not carry any monetary value, and it is not redeemable or tradable.</p><p>We appreciate your continued support and enthusiasm as we work together to refine and secure the future of Bitcoin staking.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=234ea3fa9077" width="1" height="1" alt=""><hr><p><a href="https://medium.com/babylonlabs-io/babylon-testnet-4-pre-launch-announcement-234ea3fa9077">Babylon Testnet-4 Pre-Launch Announcement</a> was originally published in <a href="https://medium.com/babylonlabs-io">BabylonLabs.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Quest for Utility: BTC Staking Ecosystem Update]]></title>
            <link>https://medium.com/@Cryptonian_S/the-quest-for-utility-btc-staking-ecosystem-update-037abca51d84?source=rss-cfaf956ecd0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/037abca51d84</guid>
            <category><![CDATA[staking]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ecosystem-building]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Editor @ Babylon]]></dc:creator>
            <pubDate>Wed, 15 May 2024 13:59:20 GMT</pubDate>
            <atom:updated>2024-05-15T13:59:20.574Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pdPgA93rBHvVG-56AwWBVg.jpeg" /></figure><p>The pursuit of unlocking Bitcoin’s true potential as more than just a store of value has been a longstanding quest in the crypto realm. For years, the industry has sought to push the boundaries of Bitcoin innovation. Part of this has been exploring ways to harness the power and security of the world’s largest $1 trillion cryptocurrency to drive real-world utility. This quest has led to the Babylon BTC Staking protocol, redefining the role of Bitcoin in the decentralized economy.</p><p>The Babylon Staking Protocol allows Proof-of-Stake (“PoS”) systems such as PoS chains, L2 rollups, Data Availability (DA) layers, and oracles to acquire staking capital from Bitcoin, the largest decentralized crypto asset in the world. Through its modular design and slashing functionality, The Babylon Staking Protocol will enable PoS systems to introduce Bitcoin as a staking asset and enjoy higher crypto-economic security than native tokens can provide. As a result, PoS systems will be able to utilize Babylon’s scalable staking and restaking features to unlock value from the idle, unencumbered $1 trillion Bitcoin ecosystem.</p><p>This blog will highlight our growing ecosystem joining us to enable a Bitcoin-secured decentralized economy. By joining, they are set to unlock the full potential of Bitcoin security.</p><h3>Bedrock, Nomic, and Solv: Liquid Staking Tokens for Staked Bitcoin</h3><p>Bedrock is launching a liquid restaking token called uniBTC on top of The Babylon Staking Protocol. Bedrock aims to build a one-click liquid restaking solution for BTC and WBTC and has already launched a successful liquid restaking solution for EigenLayer and IoTeX.</p><p>Additionally, Solv is a yield and liquidity infrastructure layer backed by Binance Labs and Blockchain Capital that leverages The Babylon Staking Protocol. They are launching SolvBTC, a yield-bearing liquid restaking token for Bitcoin where users will stake Bitcoin to Solv to receive SolvBTC.</p><h3>Lorenzo Protocol: Redefining Bitcoin DeFi</h3><p>Lorenzo Protocol, a project redefining the Bitcoin DeFi landscape, <a href="https://medium.com/@lorenzoprotocol/lorenzo-protocol-integrates-babylonchain-to-build-bitcoin-application-layer-609f6755f331">announced</a> its integration with the protocol as part of its pursuit to build a scalable and performant Bitcoin application layer. This synergy ensures that all Bitcoin assets are compatible with Lorenzo’s modular L2, enabling the use of Bitcoin not only for storing critical asset data but also for providing unparalleled security to users.</p><h3>Persistence One: Maximizing Yield and Security</h3><p>Since April 2023, Persistence One has been a part of Babylon’s Timestamping testnet. Persistence One is a purpose-built Layer 1 on a mission to maximize yield and security through Liquid Staking and Restaking. Their mission perfectly aligns with Babylon, as it greatly improves their ecosystem, bolstering the capital staked and security threshold. With Babylon, Persistent One ensures its ecosystem has the highest level of security.</p><h3>AltLayer &amp; B2 — Consuming Security to Bolster New Use Cases</h3><p>The rapid expansion of Babylon’s ecosystem goes across both the supply and demand side, whereby Babylon’s impact extends beyond just enabling staking. Several projects also tap on the staked Bitcoin to enhance their security and drive further utility. This represents the demand side leveraging Bitcoin’s robust security facilitated by Babylon:</p><p>AltLayer is a decentralized verification layer for rollups, collaborating with Babylon to build rollup infrastructure secured by staked BTC. This allows rollups to achieve decentralized verification, better latency, and improved interoperability. B² network incorporates Babylon’s BTC Staking functionality in the B² Rollup, supporting the BTC LSD and Restaking use cases for Rollups. Additionally, their B² Hub utilizes Babylon’s Bitcoin timestamping protocol to avoid long-range attacks on the PoS consensus mechanism. After the Babylon BTC Staking mainnet launch, B² Rollup will enable users to directly stake their BTC on the Bitcoin network through Babylon to participate in securing the B² Network.</p><h3>Glacier, Automata, Yala and Hana Network: Bolstering Security, Accessibility and Research</h3><p>Other key projects have integrated and collaborated with Babylon to enhance security, accessibility, and research. Glacier Network <a href="https://medium.com/@glacierlabs/babylon-integrates-with-glacier-network-to-build-enhanced-validator-network-564e66496da1">integrated</a> with Babylon to strengthen and expand its validator network using Babylon’s Bitcoin staking. Automata Network has <a href="https://blog.ata.network/automata-collaborates-with-babylon-to-advance-tee-research-and-enhance-multi-prover-security-with-5f49d7d38ace">collaborated</a> to advance Trusted Execution Environment (TEE) research and enhance multi-prover rollup security leveraging staked Bitcoin. Hana Network has integrated to allow seamless Bitcoin restaking through its gateway while benefiting from Babylon’s robust security. The modular Yala layer for Bitcoin has integrated Babylon to build an interoperable Bitcoin ecosystem extending its proof-of-work security to PoS chains and rollups.</p><h3>Conclusion</h3><p>The rapid expansion of Babylon’s ecosystem shows Bitcoin’s untapped potential. By enabling Bitcoin holders to stake their bitcoins securely and earn yields while bolstering the security of PoS systems and more, Babylon is paving the way for a future where Bitcoin’s utility extends far beyond its traditional role as a store of value.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=037abca51d84" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Babylon Testnet-4 Pre-Launch Announcement]]></title>
            <link>https://medium.com/@Cryptonian_S/babylon-testnet-4-pre-launch-announcement-be213f621c8f?source=rss-cfaf956ecd0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/be213f621c8f</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[staking]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Editor @ Babylon]]></dc:creator>
            <pubDate>Wed, 15 May 2024 12:20:24 GMT</pubDate>
            <atom:updated>2024-05-15T12:20:24.282Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xs23lTDAj4jUIJ94KYpVKw.png" /></figure><p>The Babylon team plans to launch a new testnet towards the end of May 2024. This announcement explains the purpose of this testnet and how to prepare for it.</p><h3>Why Babylon Testnet-4?</h3><p>Our current testnet, bbn-test-3, allows Bitcoin stakers to engage in a full range of activities including staking, unbonding, withdrawing, claiming rewards, and experiencing the slashing mechanism. We will sunset it at 12PM UTC 16/May/2024. Of course, it is only a testnet and no real BTC were used.</p><p>Community feedback has been very positive on the user experience so far, while also emphasizing a key consideration for participating in such as protocol: the security of their staked Bitcoins. Users want assurance that their Bitcoin won’t be stolen, can unbond and withdraw anytime, and won’t be slashed.</p><p>Therefore, the new testnet (bbn-test-4) will focus on the security of the staked Bitcoins by testing the user’s interaction with the BTC Signet test network.</p><h3>Key Features</h3><p>Here’s what this means for users:</p><ul><li>This testnet will only involve BTC Signet test network without a Babylon PoS test chain.</li><li><strong>Simplified interaction</strong>: Bitcoin stakers can stake, unbond, and withdraw by submitting the corresponding transactions to BTC Signet test network via the staking web dapp.</li><li><strong>No slashing</strong>: Bitcoin stakers are not requested to sign any slashing related authorisations, which means slashing will be disabled.</li><li><strong>No PoS reward</strong>: Since there is no Babylon PoS test chain, the test staking reward feature will not be applicable.</li><li><strong>No voting</strong>: For the same reason, finality providers will only need to publish their EOTS public key to allow stake delegation. They do not need to actively maintain any programs (such as node and finality provider daemons).</li></ul><p>In addition,</p><ul><li><strong>Finality provider registration</strong>: To counter spams while preserving decentralisation, for a finality provider to be included in the initial list of finality providers in the staking web dapp, we request the finality provider to deposit a small amount of Signet Bitcoin and submit a PR to a dedicated Github registry repo before the testnet launch (see instructions below).</li><li><strong>Staking cap</strong>: We will apply gradually increasing staking caps, starting with 5 sBTC, to control Signet Bitcoin ingress while testing the system through security audit and public security campaign.</li></ul><h3>Preparation</h3><p><strong>Bitcoin stakers</strong>: If you are interested in participating, please consider unbonding and withdrawing your Signet Bitcoin from the existing testnet (<a href="http://btcstaking.babylonchain.io/">btcstaking.babylonchain.io)</a>. We will also reopen Discord faucet very soon.</p><p><strong>Finality providers</strong>: Please read this guide (<a href="https://github.com/babylonchain/networks/tree/main/bbn-test-4/finality-providers">networks/bbn-test-4/finality-providers at main · babylonchain/networks</a> ) to register yourself if you would like to appear in the initial finality provider list of the staking web dapp with proper information display (name, logo, etc).</p><h3>Final Notes</h3><p>This testnet is NOT incentivised. Its purpose is to allow interested parties to evaluate and get familiar with Bitcoin staking related operations.</p><p>We would also like to emphasise that Signet Bitcoin is only a simulated Bitcoin for testing that can be used only for the BTC Signet test network. It does not carry any monetary value, and it is not redeemable or tradable.</p><p>We appreciate your continued support and enthusiasm as we work together to refine and secure the future of Bitcoin staking.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be213f621c8f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Technical Preliminaries of Bitcoin Staking]]></title>
            <link>https://medium.com/babylonlabs-io/technical-preliminaries-of-bitcoin-staking-74a42b283d79?source=rss-cfaf956ecd0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/74a42b283d79</guid>
            <category><![CDATA[staking]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Editor @ Babylon]]></dc:creator>
            <pubDate>Tue, 07 May 2024 09:29:16 GMT</pubDate>
            <atom:updated>2024-05-13T10:39:12.191Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SNswJtx1NnGnCcxa.png" /></figure><p>Through this and the next articles, we explain how the Babylon protocol overcomes the Bitcoin protocol’s limited programmability, making trustless and self-custodial Bitcoin staking possible. This article focuses on the technical preliminaries, and the next article focuses on constructing Babylon’s Bitcoin staking contract.</p><h3>1. What Defines a Staking Asset?</h3><p>To turn Bitcoin into a staking asset, we first need to understand what a staking asset is.</p><p>A staking asset is the asset in a PoS (proof-of-stake) system that a participant locks if the participant wishes to make attestations. The most common type of attestation is referred to as a vote. This enables stake-weighted voting protocols, which allow consensus among the participants in a decentralized way. When the decisions are chained, we have a PoS blockchain, and the participants are called validators.</p><p>What does this “collateral“ entail?</p><h3>1.1 Slashing</h3><p><em>“With great power comes great responsibility.“</em></p><p>For a PoS system to be secure, its staking asset should at least have the following two properties:</p><ol><li><strong>Slashable</strong>, meaning that if a staker attacks the PoS system secured by it, its staked asset can be slashed.</li><li><strong>Lockable</strong>, meaning that once staked, the asset cannot be transferred or traded.</li></ol><p>The above two properties go hand in hand: slashability economically deters the staker from acting maliciously, and locking prevents malicious stakers from dodging the slashing (by immediately selling their staked asset after the attack).</p><p>Indeed, most PoS systems impose an <strong>unbonding period</strong><em>.</em> When a staker requests to unbond, its attestation power is immediately dismissed, so it cannot attack the PoS system. Meanwhile, the staked asset will still be locked for a certain period, giving the system enough time to uncover past attacks from the staker and slash it if needed. This unbonding period can be as long as a few weeks.</p><h3>1.2 Delegation</h3><p><strong>Delegation</strong> is particularly important for small stakers. Maintaining an attestation infrastructure (such as a validator node) by themselves could be too difficult or costly. They may prefer to delegate their attestation power to a professional validator, who acts as a proxy and charges a fee from the staking rewards.</p><p>If the delegated validator violates the protocol, itself and all its delegators are subject to slashing. This implies that the slashing is always applied to everyone or no one. In other words, there is no way for a delegated validator to selectively cause some of its delegators slashed . This property is called <strong>atomic slashing.</strong> It allows a professional validator to earn trust from delegators by self-delegating stakes.</p><p>On the other hand, the delegated validator has no direct access or control of the delegator’s stake, meaning it cannot steal from the staker. This fundamental difference separates delegation from custodial arrangements, where the custodian controls the users’ digital assets.</p><p>The above properties define a staking asset. The other properties, such as partial slashing and restakable mentioned in Article-1, are nice-to-have.</p><h3>2. What Does BTC Allow You to Do?</h3><p>To turn Bitcoin into a staking asset, we should also understand what the BTC network allows you to do with it. If you are familiar with the terms UTXO, BTC script, and Taproot Script, you can skip this section.</p><h3>2.1 Bitcoin Transaction and UTXO</h3><p>The Bitcoin protocol is a peer-to-peer, electronic, decentralized, cryptocurrency protocol, and Bitcoin (BTC) is its native digital asset. A Bitcoin transaction is best explained via a real-world cash payment example:</p><p>Alice has a $2 note. Her mom has a $5 note. They use their notes to pay Bob for a $6 ice cream, and the change of a $1 note goes to Alice. This transaction can be described as follows:</p><pre>// ice cream purchase<br>inputs:<br>  - input-1: value = $2, owner = Alice<br>  - input-2: value = $5, owner = Mom<br>outputs:<br>  - output-1: value = $6, owner = Bob<br>  - output-2: value = $1, owner = Alice</pre><p>Bob can then spend his $6 note to purchase $4 of milk from Charlie and receive a change of $2:</p><pre>// milk purchase<br><br>inputs:<br>  - input-1: Bob&#39;s $6 from the ice cream purchase<br><br>outputs:<br>  - output-1: value = $4, owner = Charlie<br>  - output-2: value = $2, owner = Bob</pre><p>A BTC transaction looks very much the same. Each BTC transaction requires:</p><ul><li>A set of inputs, which are the source of the fund to be transacted.</li><li>A set of outputs, which are the destinations of the fund after the transaction.</li></ul><p>The total inputs should be greater or equal to the total outputs. The surplus is the transaction fee.</p><p>The milk purchase transaction under the BTC context will look like the following:</p><pre>// milk purchase transaction on BTC network<br><br>inputs:<br>  - input-1: Bob&#39;s 6 Bitcoins from the ice cream purchase transaction<br><br>outputs:<br>  - output-1: value = 4 Bitcoins, owner = charlie_public_key<br>  - output-2: value = 1.99 Bitcoins, owner = bob_public_key<br><br>// Bob needs to sign the above transaction and submit it to the BTC network.</pre><p>The main difference is that, in Bitcoin network, fund ownership is specified through people’s cryptographic public key. This way, the output can only be spent if the owner cryptographically signs it using their secret key.</p><p>Before an output is spent, it is called an unspent transaction output (UTXO). A person’s balance is the total value of all their UTXOs. Bitcoin transactions are all about spending (and destroying) existing UTXOs and creating new ones. In addition, due to this mode, how one UTXO of a person is spent will not affect the rest of this person’s UTXOs.</p><p>In the above milk purchase transaction, there is a surplus of 0.01 Bitcoin. This is the transaction fee that Bob pays to the miner who mines the BTC block that includes his transaction. More specifically, the miner of this BTC block (called Ming) will create a special <em>coinbase</em> transaction for this block, which looks like the following:</p><pre>// coinbase transaction<br><br>inputs: n.a.<br><br>outputs:<br>  - output-1: value = 6.26 Bitcoins, owner = ming_public_key</pre><p>This special transaction has no inputs because Ming turned his hard work into Bitcoin rather than receiving Bitcoin from someone else. He gets 6.26 Bitcoins, comprising 6.25 Bitcoins of base mining reward (specified by the protocol) and 0.01 Bitcoin of transaction fee (if Bob is the only one paying the transaction fee in this block).</p><p>This is an elegant design. Bob cannot predict who will be the miner that includes his transaction, so he cannot explicitly pay the miner. With this design, he only needs to create a surplus in his transaction to implicitly pay to whomever the miner will be.</p><h3>2.2 Spending Conditions</h3><p>Speaking of spending, BTC has a scripting language that allows you to specify some simple condition(s) under which a UTXO can be spent. Two basic conditions (which we will use) are:</p><ul><li>signature(s), which allow you to specify whose consent is needed to spend a UTXO. The owner public key above is an example where only one consent is needed.</li><li>Time lock, which lets you specify how many BTC blocks a UTXO can be spent later. For example, a time lock of 1000 BTC blocks will make a UTXO temporarily unspendable for about 1000 * 10mins / 60 = 167 hours (roughly a week) after this UTXO’s creation.</li></ul><p>For example, if Alice’s mom wants to give Alice some allowance with the following spending conditions:</p><p><em>“This UTXO is only spendable either 1) after seven days by Alice in whatever way, or 2) in a way that both myself and Alice agree to“,</em></p><p>Alice’s mom can submit the following transaction to BTC:</p><pre>// Mom&#39;s tx to give Alice 4 Bitcoins of allowance, with strings attached.<br><br>Inputs:<br>  - input-1: mom&#39;s 10 Bitcoins<br>             <br>Outputs:<br>  - output-1: value = 4 Bitcoins,<br>              conditions:<br>              - condition-1: time_lock = 1000 &amp; alice_public_key OR<br>              - condition-2: alice public_key &amp; mom_public_key<br>  <br>  - output-2: value = 5.99 Bitcoins,<br>              conditions:<br>              - condition-1: mon_public_key<br>              <br>              <br>// Mom signs this transaction and sends it to the BTC network.</pre><p>Once executed by the BTC network, the UTXO-1 above will carry 4 Bitcoins and can only be spent as specified previously. Mom and Alice will co-own these 4 Bitcoins for 7 days, after which Alice will have full ownership. The UTXO-2 above is mom’s change and has nothing to do with Alice.</p><h3>2.3 Pre-Approval</h3><p>What is even cooler is that Alice’s mom can give Alice her pre-approval. Imagine that mom only allows Alice to send the Bitcoin to her dad (not anyone else) before the 7-day restriction is lifted. To achieve this:</p><ol><li>Mom prepares a BTC transaction, in which the previous UTXO is spent via the 2nd condition above, and the recipient is set to Alice’s dad.</li><li>Mom then signs this transaction and gives Alice her signature.</li><li>If Alice does want to send the Bitcoins to her dad, Alice can simply co-signs it and submits it to the BTC network anytime.</li></ol><pre>// Mom&#39;s pre-approval transaction<br><br>Inputs:<br>  - input-1: The previous UTXO that is worth 4 Bitcoins.<br>             - To be spent via condition-2.<br>             - Signatures needed: alice and mom.<br>             <br>Outputs:<br>  - output-1: value = 3.99 Bitcoins,<br>              conditions:<br>              - condition-1: dad_public_key<br><br>// Mom signs the above tx and gives the signature to Alice as her pre-approval.<br>// Alice can sign the above transaciton later and submits the tx and both<br>// signatures to the BTC network. </pre><h3>3. Cryptographic Voodoo</h3><p>To make slashing happen, we need some doses of “voodoo” from cryptography.</p><h3>3.1 Extractable One-Time Signature (EOTS) Algorithm</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iTVttxGdpBu2zrTNTgajAg.png" /></figure><p>Imagine Alice has received two job offers and should only pick one to sign. Is there a way to deter her from signing both? The answer is yes if Alice can be fined if she does so. There is a cryptographic primitive that can achieve this, called EOTS. It can be constructed from the famous Schnorr signature algorithm natively supported by BTC since the Taproot upgrade.</p><p>In the Schnorr signature algorithm, the signer has a pair of <strong>(secret_key, public_key)</strong>. To sign a new message <strong>M</strong>, the signer:</p><ol><li>Generates a <strong>secret_nonce</strong></li><li>Uses the <strong>secret_key</strong> and the <strong>secret_nonce</strong> to sign the message.</li><li>Computes the corresponding <strong>public_nonce</strong> of the <strong>secret_nonce</strong></li><li>Publish the signature <strong>S</strong> and <strong>public_nonce</strong> to allow the public to verify <strong>S</strong>.</li></ol><p>Here, the <strong>secret_nonce</strong> must be a new one for every new message. If the same <strong>secret_nonce</strong> is used to sign two different messages, then anyone who observes the two signatures can extract the signer’s <strong>secret_key</strong>.</p><p>With an appropriate construction, Schnorr’s above property can deter the signer from equivocation, making it EOTS. For example, if Alice signs two conflicting contracts, her secret key can get decrypted. Alice will think twice before doing so if she has a sizeable asset managed by this secret key.</p><h3>3.2 Adaptor Signature</h3><p>Section 2.3 showed that Alice’s mom can give Alice her pre-approval for a specific fund destination address. Now imagine this address belongs to Alice’s best friend, and mom isn’t a big fan of this person. Mom can say:</p><p><em>“You can send the 4 Bitcoins to your best friend. But if you do so, all your savings will be gone.“</em></p><p>There is a cryptographic primitive that can make this happen, called one-time verifiably encrypted signature (one-time VES) algorithm, a.k.a. adaptor signature. It can also be derived from the Schnorr signature algorithm. It works as follows:</p><ol><li>Alice’s mom signs the message <strong>M</strong>, which is the Bitcoin transaction that will send the 4 Bitcoins to Alice’s best friend. The result is mom’s Schnorr signature <strong>S</strong>.</li><li>Instead of passing <strong>S</strong> to Alice as the pre-approval, mom encrypts <strong>S</strong> using Alice’s public key, <strong>alice_public_key</strong>. The result is called an adaptor signature <strong>A</strong>. Mom publishes <strong>A</strong> so that the public knows it, including Alice.</li><li>If Alice does want to proceed, she can use mom’s adaptor signature A and her own secret key <strong>alice_secret_key</strong> to recover a Schnorr signature <strong>S&#39;</strong>. This <strong>S&#39;</strong> is different from mom’s original signature <strong>S</strong> , but is still a valid Schnorr signature of mom over <strong>M</strong>, as if mom used a different secret nonce to sign <strong>M</strong>.</li><li>Alice submits the Bitcoin transaction <strong>M</strong>, her own signature over <strong>M</strong>, and mom’s <strong>S’</strong> to BTC. BTC will verify and execute this transaction, so that Alice’s best friend will receive 4 Bitcoins.</li><li>Here is the catch: Mom’s Schnorr signature <strong>S’</strong> and adaptor signature <strong>A</strong> allow anyone to decrypt Alice’s secret key <strong>alice_secret_key</strong>.</li><li>If Alice also uses this key to manage her savings, then she will think twice before sending the fund to her best friend — anyone can then steal her savings.</li></ol><p>This is why the adaptor signature is one-time: Alice can use her secret key to open the special treasury box her mom gives her, but after that, her secret key is exposed and won’t be useable anymore.</p><h3>Remark</h3><p>Blockchain security and cryptography are not for everyone, but you have come a long way. Congrats! Now, for our next steps, let’s build a Bitcoin staking contract together!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wPqozf_HBdqSP15Q.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74a42b283d79" width="1" height="1" alt=""><hr><p><a href="https://medium.com/babylonlabs-io/technical-preliminaries-of-bitcoin-staking-74a42b283d79">Technical Preliminaries of Bitcoin Staking</a> was originally published in <a href="https://medium.com/babylonlabs-io">BabylonLabs.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>