<?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 Ride (by Fiamma) 🦙🔥 on Medium]]></title>
        <description><![CDATA[Stories by Ride (by Fiamma) 🦙🔥 on Medium]]></description>
        <link>https://medium.com/@Fiamma.io?source=rss-365c2d512dfb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hKMuAYVxgEQYqZsAxSV64w.png</url>
            <title>Stories by Ride (by Fiamma) 🦙🔥 on Medium</title>
            <link>https://medium.com/@Fiamma.io?source=rss-365c2d512dfb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 06:58:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Fiamma.io/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[Fiamma 2025 Annual Review]]></title>
            <link>https://medium.com/@Fiamma.io/fiamma-2025-annual-review-af6cdf80f6a3?source=rss-365c2d512dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/af6cdf80f6a3</guid>
            <dc:creator><![CDATA[Ride (by Fiamma) ]]></dc:creator>
            <pubDate>Wed, 31 Dec 2025 08:41:28 GMT</pubDate>
            <atom:updated>2025-12-31T08:41:28.102Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*opYGkmmmwDfi3mY3brSX1A.jpeg" /></figure><p><strong>From the first production-ready BitVM2 infrastructure</strong></p><p><strong>to FIRE — our debut application built for effortless DeFi.</strong></p><p>2025 marked a pivotal year for Fiamma.</p><p>We began with BitVM2 infrastructure — taking ideas that once lived in research papers and technical discussions — and turned them into a system that can <strong>run in production, scale safely, and be used by real users</strong>. By the end of the year, those capabilities were delivered directly to users through the <strong>FIRE App</strong>.</p><p>Throughout 2025, our direction remained consistent:</p><blockquote><strong><em>Non-custodial · One-click experience · BitVM2-secured </em></strong><em>Complexity stays in the system BTC &amp; stable coin earning, trading across assets from crypto to gold and stocks</em></blockquote><p>This was a year of quiet building — followed by real execution.</p><p>Here is how that journey unfolded.</p><h3>🟠 2025 · Q1</h3><p><strong>From “it works” to “it can run long-term”</strong></p><p>At the start of 2025, Fiamma focused on a single question: <strong>Can BitVM2 actually be engineered for long-term, scalable, real-world operation?</strong></p><p>Through intensive Alpha Testnet operations, we systematically stress-tested BitVM2’s challenge flow, verification efficiency, and operational cost structure — exposing bottlenecks and iterating on them in real time.</p><p>During this phase, we addressed three foundational issues:</p><ul><li><strong>High verification costs</strong> → Redesigning the disprove mechanism, compressing critical transaction sizes by approximately <strong>40×</strong></li><li><strong>Non-engineerable verification flows</strong> → Rebuilding the Challenge Protocol into a system that can operate reliably in production</li><li><strong>Unsustainable operator incentives</strong> → Defining clear slashing boundaries and economic constraints for long-term participation</li></ul><p>By the end of Q1, BitVM2 was no longer just theoretically secure. <strong>It had crossed the line into reality — emerging as the first BitVM2-based infrastructure proven to be engineerable, sustainable, and production-ready.</strong></p><h3>🟠 2025 · Q2</h3><p><strong>From “will the bridge break” to “even if it breaks, you’re safe”</strong></p><p>In Q2, our focus shifted from performance to <strong>systemic risk</strong>.</p><p>The core weakness of traditional BTC bridges is not speed —</p><p>it is that a single compromised role can cascade risk across all users.</p><p>To address this, Fiamma emphasized <strong>Isolated Safe Architecture (ISA)</strong>:</p><ul><li>Each user’s BTC is <strong>architecturally isolated</strong></li><li>Even if committees or operators are compromised, other users’ funds remain untouched</li><li>Users always retain private keys and final control</li></ul><p>Alongside this, <strong>Fiamma Scan</strong> was launched to make every bridge and verification step fully transparent and independently verifiable on-chain.</p><p>At this point, Fiamma Bridge evolved from being “a safer bridge” into: 👉 <strong>A BTC cross-chain architecture where risk cannot spread laterally.</strong></p><h3>🟠 2025 · Q3 The quarter where scale became real</h3><p>Q3 marked Fiamma’s transition from infrastructure to an ecosystem engine through rigorous audit by Oppenzeppline and Bitslab.</p><p><strong>This shift was built on scale already proven during the public testnet:</strong> over <strong>330K users</strong>, <strong>6.4M transactions</strong>, and <strong>15,182.4 sBTC</strong> in total transaction value, with <strong>3.9M deposits</strong> and <strong>2.5M withdrawals</strong> validating real demand and system reliability ahead of mainnet launch.</p><p>Several critical shifts happened simultaneously:</p><ul><li><strong>Fiamma Bridge mainnet is fully live,</strong> enabling native, non-custodial BTC bridging to over 20 chains including Ethereum, Aptos, Arbitrum, Sei, BNB Chain, Base, Polygon, ZKSync, Monad, and Hyperliquid</li><li><strong>Withdrawals stabilized at ~20 seconds</strong>, with deposits reduced to minute-level flows</li><li><strong>Community Operator nodes exceeded 800</strong>, significantly strengthening decentralization</li></ul><p>At the same time, Fiamma began carrying real capital and real usage: <strong>Mission Fiamma Season 1 &amp; 2</strong> went live, collaborating with protocols such as <strong>Hyperion</strong> and <strong>Takara Lend</strong>, with multiple BTC-related pools reaching <strong>100%–135%+ APY</strong> during peak periods.</p><p>The signal was clear: <strong>BTC DeFi was no longer just usable — it was being used at scale.</strong></p><h3>🟠 2025 · Q4</h3><p><strong>Delivering the infrastructure to users</strong></p><p>We realized that trust-minimized infrastructure only has meaning if it can be delivered seamlessly to users. That realization shaped everything we built next. In Q4, all of those layers converged — <strong>resulting in the official launch of the Fire App</strong>.</p><p>For the first time, users could:</p><ul><li>Bridge BTC and configure yield with one click</li><li>Earn BTC and stablecoin yield in a fully non-custodial setup</li><li>View portfolios, manage positions, and switch strategies in one app</li><li>Native BTC lending &amp; borrowing</li></ul><p>With <strong>Perps trading integrated via Hyperliquid liquidity</strong>, FIRE began enabling seamless transitions between <strong>passive vault yield</strong> and <strong>active leveraged trading</strong> — within the same non-custodial environment.</p><p>At this stage, BitVM2 stopped being an infrastructure term —</p><p>it became a capability users interacted with daily.</p><h3>🔮 Looking Ahead: FIRE as a DeFi Super App</h3><p>In 2025, Fiamma validated two core ideas:</p><p>BitVM2’s security model works in the real world</p><p>Bitcoin DeFi does not need to sacrifice safety for usability</p><p>Moving forward, Fiamma will continue expanding along several fronts:</p><ul><li>⚡ <strong>Advanced Perps trading</strong></li><li>🔮 <strong>Prediction markets &amp; social trading</strong>, turning judgment into yield</li><li>🧠 <strong>Smarter vaults and strategy systems</strong>, data-driven and risk-first</li></ul><p>Our goal remains unchanged:</p><blockquote><strong><em>Keep complexity inside the system — deliver simplicity, safety, and certainty to users.</em></strong></blockquote><p>Thank you to every Alpaca who built with us, tested with us, and trusted us in 2025.</p><p>Effortless DeFi is no longer a concept — and it’s only just beginning.</p><p>🔥 <strong>Stay tuned.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af6cdf80f6a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Alpaca Creator Program]]></title>
            <link>https://medium.com/@Fiamma.io/alpaca-creator-program-f7312cef5954?source=rss-365c2d512dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7312cef5954</guid>
            <dc:creator><![CDATA[Ride (by Fiamma) ]]></dc:creator>
            <pubDate>Mon, 10 Nov 2025 10:42:24 GMT</pubDate>
            <atom:updated>2025-11-21T04:57:02.407Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RWC9mvQSvLjkaUx-Ea8BTg.png" /></figure><p><strong>Fiamma’s vision</strong> is simple — to make DeFi smarter.<br><strong>Trade, Borrow, Earn Smarter — powered by Agentic AI.</strong> 🔥</p><p>With the <strong>FIRE App (testing now live)</strong>, Fiamma is reshaping how people interact with decentralized finance, combining security, intelligence, and simplicity in one seamless experience.</p><p>And now, we want to empower a new generation of creators to tell that story.<br> To help the market understand this transformation, we’re launching the <strong>Alpaca</strong> <strong>Creator Program</strong> — a quest-driven initiative designed to unite creators around clear narratives before evolving into a broader ambassador model.</p><h3>📝 Registration Form</h3><p><a href="https://tally.so/r/9qGEkE">https://tally.so/r/9qGEkE</a></p><h3>🌟 Alpaca Tier wise Reward System</h3><ul><li><strong>Tier 1 </strong>— Up to <strong>250 ASP</strong> per quest</li><li><strong>Tier 2 </strong>— Up to <strong>200 ASP</strong> per quest</li><li><strong>Tier 3 </strong>— Up to <strong>150 ASP</strong> per quest</li><li><strong>Tier 4</strong> — Up to <strong>100 ASP</strong> per quest</li></ul><p>Each tier will have <strong>multiple winners</strong>, encouraging fair competition and sustained motivation.</p><p><strong>Performance Bonuses:</strong> Based on efforts, impressions, professionalism etc.<br><strong>Perks:</strong> Exclusive brand opportunities, IRL event invitations, early access to the FIRE App, limited-edition Alpaca merch, and even the chance to be selected as an official Alpaca Ambassador — with future token rewards waiting for top contributors.</p><h3>💡 Key Responsibilities</h3><h4>1. Content Creation</h4><p>Develop and distribute engaging, high-quality content (threads, short videos, memes, infographics) that highlights the unique value of the <strong>FIRE App</strong>.</p><p><strong>Core Platforms:</strong> Twitter (X), TikTok, YouTube, and other relevant social channels.</p><h4>2. Content Direction</h4><p>Every creator must read the instructions carefully written in the quest and work as per requirement. They are also supposed to integrate the following informations in their submissions:</p><ul><li><strong>Why Fire App?</strong> — Share authentic stories about how FIRE App helps users achieve financial freedom.</li><li><strong>Proof of Real Yield</strong> — Showcase verifiable earnings through FIRE App (e.g., screenshots or data insights).</li><li><strong>Community &amp; Events</strong> — Promote and recap community events like AMAs, giveaways, and meetups.</li><li><strong>Product Tutorials</strong> — Create simple, clear guides showcasing FIRE App’s clean UI and one-click experience.</li><li><strong>Creative Freedom</strong> — We encourage your unique style and ideas!</li></ul><h4>3. Content Guidelines</h4><ul><li><strong>Hashtags:</strong> #Fiamma #FIRE #Alpaca</li><li><strong>Logo Usage:</strong> All videos must include the official Fiamma logo.</li><li><strong>Brand Resources:</strong> <a href="https://juvenile-popcorn-9eb.notion.site/Fiamma-Brand-Resource-b464f006e54846d68b60ea19f18806f7">https://juvenile-popcorn-9eb.notion.site/Fiamma-Brand-Resource-b464f006e54846d68b60ea19f18806f7</a></li><li><strong>Core Elements:</strong> Every piece of content should feature at least one key brand element (e.g., Alpaca, FIRE).<br><a href="https://drive.google.com/drive/folders/1j7wQy77mVo4SRlOHiX4EpveoiQjCpnUG?usp=drive_link">https://drive.google.com/file/d/1ezzeCL0tzWcZOwr4vlZ7UqPYtSByIe8H/view?usp=sharing</a></li><li><strong>Quality Standards:</strong></li><li>TikTok/X: Minimum 720p</li><li>YouTube: Minimum 1080p</li><li>Avoid low-resolution or overly filtered visuals.<br>…</li></ul><h4>4. How to Join &amp; Submit Your Work</h4><p><strong>Step 1 — Complete the Registration Form</strong><br> Fill out the questionnaire here 👇<br> <a href="https://tally.so/r/9qGEkE">https://tally.so/r/9qGEkE</a></p><p><strong>Step 2 — Join the Telegram Group</strong><br>Send a join request to FIAMMA CREATORS’ Telegram group. Link is in the announcement (X)post. In the Telegram group, all official creator tasks (Quests) will be posted as <strong>pinned messages</strong>.</p><p><strong>Step 3 — Submit Your Work<br></strong>When you’ve completed a Quest, simply <strong>reply under the pinned message</strong> with your content link — <br>it can be from <strong>X (Twitter)</strong>, <strong>TikTok</strong>, <strong>YouTube</strong>, or <strong>any other creative format</strong> you produce.</p><p>📌 Each Quest will be shared as a pinned message.<br> We’ll review and collect submissions regularly.</p><h4><strong>5. 🧩 Task Types</strong></h4><p><strong>Alpacax Quest</strong> — The main weekly quest (public + private)<br><strong>Fleece Quest</strong> — Short premium tasks, exclusive to private group members (higher reward)<br><strong>Side Quest</strong> — Micro tasks like amplifying co-founder posts or quote-tweet boosts</p><h3>🚀 Join the Movement</h3><p>Become part of the Alpaca Creator family — where creativity meets DeFi freedom.<br>Start creating, sharing, and earning with FIRE. 🔥</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7312cef5954" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Ignite the Future — Join the FIRE Early Access Campaign]]></title>
            <link>https://medium.com/@Fiamma.io/ignite-the-future-join-the-fire-early-access-campaign-4a3192bcdb6b?source=rss-365c2d512dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a3192bcdb6b</guid>
            <dc:creator><![CDATA[Ride (by Fiamma) ]]></dc:creator>
            <pubDate>Fri, 17 Oct 2025 07:40:39 GMT</pubDate>
            <atom:updated>2025-10-17T08:39:32.409Z</atom:updated>
            <content:encoded><![CDATA[<h3>🔥 <strong>Ignite the Future — Join the FIRE Early Access Campaign</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j-TX-k3-Gc-LyYDxZZun2g.png" /></figure><p><strong>Say goodbye to friction.</strong> <strong>Say hello to FIRE.</strong></p><p>Welcome to FIRE by Fiamma. 🦙🔥</p><p>The best yield on BTC &amp; beyond + the best experience + the best security — all in one app.</p><h4><strong>⚡ Why FIRE</strong></h4><p>💰 Earn solid yields — 6%+ on BTC and ~8% on stablecoins — with more 15%+ opportunities on the way</p><p>⚡ One-click, bridgeless deposit experience</p><p>🔒 100% non-custodial, secured by BitVM2</p><p>No complex steps. Just tap and earn.</p><blockquote><em>DeFi shouldn’t feel like coding. With FIRE, it feels like freedom — fast, safe, and human.</em></blockquote><h4>🧩 Join the Early Access Program</h4><p>We’re opening access to a <strong>limited group of early users</strong> who believe in a freer, trustless future for Bitcoin. Your feedback will help refine the<strong> FIRE</strong> experience before its full release.</p><p>🎁 <strong>Early User Perks:</strong></p><ul><li>Whitelisted access to the FIRE app</li><li>Exclusive “🔥 Fire Builder” Discord role</li><li>Claim your Fire Badge on Galxe</li></ul><h4>🚀 How to Join</h4><p>1️⃣ <strong>Submit your whitelist application:</strong> → <a href="https://tally.so/r/woWJ21">https://tally.so/r/woWJ21</a></p><p>2️⃣ <strong>Join our Discord:</strong></p><p><a href="https://discord.com/channels/1245655860252770325/1427987503876411415">https://discord.com/channels/1245655860252770325/1427987503876411415</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UCHShA-k-gmcHxiB1Kr77Q.png" /></figure><h4>🌠 Let FIRE Shine</h4><p>You can also join our <strong>Galxe campaign</strong> to earn your first <strong>🔥 Fire Badge.</strong> Every completed quest brings you closer to the next stage of your FIRE journey.</p><p>✨ <strong>Complete quests. Collect badges. Unlock the mystery.</strong> Those who collect <strong>all badges from Phase 1</strong> will receive an exclusive <strong>“Mystery NFT”</strong> — a symbol of the earliest Fire pioneers.</p><p>🔗 <strong>Join now:</strong> <a href="https://app.galxe.com/quest/HSNdxCoe9kM8RrcreQthJV/GCJwet8pyr">https://app.galxe.com/quest/HSNdxCoe9kM8RrcreQthJV/GCJwet8pyr</a></p><p>Be the spark that starts the FIRE. Apply today, complete your journey, and claim your badge of freedom. 🔥</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a3192bcdb6b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inside the First BitVM2 Challenge Execution: Preparing for Real Bitcoin Verification on a…]]></title>
            <link>https://medium.com/@Fiamma.io/inside-the-first-bitvm2-challenge-execution-preparing-for-real-bitcoin-verification-on-a-0333a385bbe1?source=rss-365c2d512dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/0333a385bbe1</guid>
            <category><![CDATA[bitvm]]></category>
            <category><![CDATA[bticoin]]></category>
            <category><![CDATA[bitvmbridge]]></category>
            <dc:creator><![CDATA[Ride (by Fiamma) ]]></dc:creator>
            <pubDate>Tue, 19 Aug 2025 16:04:30 GMT</pubDate>
            <atom:updated>2025-08-19T16:05:22.953Z</atom:updated>
            <content:encoded><![CDATA[<h3><em>Inside the First BitVM2 Challenge Execution: Preparing for Real Bitcoin Verification on a Production-Ready BitVM2 Bridge</em></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uAFw2JXQk0SEa0AS4s2xVg.png" /></figure><h3>What is an Operator?</h3><p>An Operator is a key role within the BitVM2 Bridge, serving as an essential liquidity provider when users exit.</p><h3>How do Operators provide services to users?</h3><ol><li><strong>During the Deposit phase:</strong> <br>The user, Committee, and Operator pre-sign a series of Bitcoin transactions, forming the foundational transaction graph of the BitVM2 Bridge. These transactions grant the Operator the ability: <em>“As long as the Operator honestly completes a payout for the user, the Operator is entitled to claim the user’s deposited BTC.” </em>This mechanism resembles Ethereum smart contracts, where BTC spending is conditioned — but implemented via pre-signed transactions instead of on-chain code.</li><li><strong>During the Withdrawal phase:</strong> <br>The user burns BTC on the sidechain, and the Operator validates the burn transaction. If valid, the Operator executes the payout to the user.</li><li><strong>After completing the payout:</strong> <br>The Operator redeems the BTC according to the simulated smart contract logic established in the deposit phase.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*pJ6XvWGJIf5agKJQeorqGA.png" /></figure><h3>Why might Operators misbehave, and what are the possible scenarios?</h3><p>Because the deposit phase simulates smart contract logic through pre-signing, Operators gain the ability to claim user-locked BTC. Under normal conditions, they must first complete the payout, then redeem BTC. However, malicious Operators might attempt to exploit loopholes to take the locked BTC at lower or zero cost.</p><p>When redeeming BTC, an Operator must provide two pieces of evidence: the user’s Burn transaction and the Operator’s PegOut transaction. If an Operator tries to cheat, several scenarios may occur:</p><ul><li><strong>Case 1:</strong> Burn.AMT &lt; PegOut.AMT — Operator pays out less BTC but tries to redeem more.</li><li><strong>Case 2:</strong> Burn.target_address ≠ PegOut.target_address — Operator sends BTC to an address not designated by the user.</li><li><strong>Case 3:</strong> Burn is invalid — The Burn transaction does not exist.</li><li><strong>Case 4:</strong> PegOut is invalid — The PegOut transaction does not exist.</li></ul><h3>Purpose of the Demonstration</h3><p>While audit reports validate the protocol’s logic and security, they cannot fully convey real-world risks. By <strong>openly simulating malicious scenarios</strong>, Fiamma Bridge aims to build user trust, gain market recognition, and push the Operator role closer to becoming <strong>permissionless</strong>.</p><p>Since Operators may attempt many forms of misbehavior, we plan to test each scenario publicly. This gives the community both an opportunity to understand Fiamma Bridge’s security model and a chance to earn meaningful rewards.</p><h3>Demonstration Scenario: Case 1</h3><p><strong>Setup:</strong></p><p><strong>Deposit process</strong></p><ol><li>The demo user deposits 0.002 BTC to Ethereum.</li><li>The user pre-signs with two Operators: <em>6 Block</em> and <em>FiaDemo</em>.</li><li>The user receives 0.002 FiaBTC on Ethereum.</li></ol><figure><img alt="Deposit Process" src="https://cdn-images-1.medium.com/max/1024/1*sUIjkyhnCfytFuGXBDm5YA.png" /><figcaption>Deposit Process</figcaption></figure><p><strong>Withdrawal process</strong></p><ol><li>The user initiates a withdrawal, burning all 0.002 FiaBTC on the sidechain.</li><li>Operator <em>FiaDemo</em> processes the request first but only pays out 0.001 BTC.</li><li>Operator <em>FiaDemo</em> attempts to redeem 0.002 BTC.</li><li>The Challenger Group detects this misbehavior and launches a challenge.</li><li>Operator <em>FiaDemo</em> is slashed.</li><li>The successful challenger receives the reward.</li><li>Operator <em>6 Block</em> continues and successfully completes the withdrawal.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3xnaz3PnyqbtkhuXFZpTAQ.png" /><figcaption>Withdraw Process</figcaption></figure><p><strong>Expected Results:</strong></p><ol><li>Operator <em>FiaDemo</em>’s 0.01 BTC collateral is slashed.</li><li>The successful challenger receives the 0.01 BTC reward.</li><li>Operator <em>FiaDemo</em> is removed from the Operator list.</li><li>Operator <em>6 Block</em> successfully completes the user’s withdrawal.</li></ol><h3>How can users participate?</h3><ul><li><strong>Preparation:</strong></li><li>Run the Challenger program: <a href="https://challenge.fiammalabs.io/dashboard">https://challenge.fiammalabs.io/dashboard</a></li><li>Complete at least one mainnet bridge task: <a href="https://app.fiammalabs.io/mission-fiamma">https://app.fiammalabs.io/mission-fiamma</a> <em>(Ensure your BTC address is the same for both the Bridge and the Challenger program)</em></li><li>Have at least $100 worth of BTC remaining in your address (e.g., 0.001 BTC).</li><li><strong>Event time:</strong></li><li>Start: <strong>August 21, 2025, 2:00 PM (UTC+0)</strong></li><li>Duration: ~30 minutes</li><li><strong>Format:</strong></li><li>The team will initiate a malicious withdrawal scenario at the start time.</li><li>Users watch the Challenger dashboard and click to participate when the challenge prompt appears.</li></ul><h3>Tutorial Documentation</h3><p><a href="https://docs.fiammalabs.io/our-product-suite/pragmatically-trustless-bitvm-bitcoin-bridge/user-guides/mainnet/fiamma-challenger">https://docs.fiammalabs.io/our-product-suite/pragmatically-trustless-bitvm-bitcoin-bridge/user-guides/mainnet/fiamma-challenger</a></p><h3>About Fiamma</h3><p>Fiamma is driving the frontier of BitVM development, creating the most trustless, secure Bitcoin bridge with every FIABTC 1:1 backed by BTC, currently living on 12 chains. Beyond unlocking liquidity, we focus on sustainable, high-efficiency use cases — structured yield, lending, and trading strategies. To bring this to everyone, the mobile app Fiamma One delivers a one-click experience to earn, borrow, and pay with BTC and stablecoins.</p><p><a href="https://fiammachain.io/">Website</a> | <a href="https://x.com/fiamma_labs">X (Twitter)</a> | <a href="https://discord.com/invite/8mCBXXjgvA">Discord </a>| <a href="https://t.me/fiammachain">Telegram</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0333a385bbe1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Billions in Bridge Hacks Every Year — But We’ve Finally Found the Cure: Isolated Safe Architecture™]]></title>
            <link>https://medium.com/@Fiamma.io/billions-in-bridge-hacks-every-year-but-weve-finally-found-the-cure-isolated-safe-architecture-7e8196dd0652?source=rss-365c2d512dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e8196dd0652</guid>
            <category><![CDATA[bitcoin-bridge]]></category>
            <category><![CDATA[bitvmbridge]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[Ride (by Fiamma) ]]></dc:creator>
            <pubDate>Mon, 30 Jun 2025 13:58:26 GMT</pubDate>
            <atom:updated>2025-06-30T13:58:26.718Z</atom:updated>
            <content:encoded><![CDATA[<h3>Billions in Bridge Hacks Every Year — But We’ve Finally Found the Cure: <strong>Isolated Safe Architecture</strong>™</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qKgAic_wz-fd7ozf2-X83Q.png" /></figure><p>While you’re still bridging assets across chains, hackers are already on the other end, siphoning off billions — silently.</p><p>From <strong>Ronin</strong> to <strong>Orbiter</strong>, from <strong>Multichain</strong> to <strong>Harmony</strong>, there’s a new high-profile bridge hack nearly every year. And they all share one terrifying truth:</p><blockquote><strong>Hackers only need a few private keys to drain everything.</strong></blockquote><p>These projects had serious teams and funding. So why couldn’t they stop it?</p><p>Is decentralization on blockchain really this fragile?</p><p>We analyzed <strong>5 major bridge exploits</strong> and identified the core vulnerability in traditional multisig systems. More importantly — we’ve built a <strong>new kind of architecture that makes this entire category of exploit obsolete</strong>.</p><p>We call it: <strong>Isolated Safe Architecture™.</strong></p><h3>5 Real Bridge Disasters: From Phishing to Insider Threats</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/948/1*lCWElg_bYysuT_TyBS32xQ.png" /><figcaption>Source: <a href="https://rekt.news/ronin-rekt">https://rekt.news/ronin-rekt</a></figcaption></figure><ol><li><strong>Ronin Bridge｜$625M lost（2022.3）<br>- </strong>Multisig address（5–9 TSS）<br>- Hackers compromised 5<br>- Attack analysis：<a href="https://rekt.news/ronin-rekt">Rekt — Ronin Network — REKT</a></li><li><strong>Multichain｜130M lost（2023.7）<br>- </strong>Multisig address（Parameters Unknown）<br>- Hackers compromised a critical number of SK shares<br>- Attack analysis：<a href="https://rekt.news/multichain-rekt2">Rekt — Multichain — REKT 2</a></li><li><strong>Harmony Horizon｜100M lost（2022.6）<br>- </strong>Multisig address（2–5 TSS）<br>- Hackers compromised 2<br>- Attack analysis：<a href="https://rekt.news/harmony-rekt">Rekt — Harmony Bridge — REKT</a></li><li><strong>Heco Bridge | 99M lost（2023.12）<br>- </strong>Multisig address（Parameters Unknown）<br>- Hackers compromised a critical number of SK shares<br>- Attack analysis：<a href="https://rekt.news/heco-htx-rekt">Rekt — HECO Bridge, HTX — REKT</a></li><li><strong>Orbit Bridge | 81.5M lost （2024.1）<br>- </strong>Multisig address（Parameters Unknown）<br>- Hackers compromised a critical number of SK shares<br>- Attack analysis：<a href="https://rekt.news/orbit-bridge-rekt">Rekt — Orbit Bridge — REKT</a></li></ol><blockquote>What do these bridges have in common?</blockquote><p>👉 They all used <strong>multisig</strong>. And while that sounds secure — it’s dangerously misleading.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*djBviiKMJlgWsDD75yOs1g.png" /><figcaption>Source: <a href="https://rekt.news/multichain-rekt2">https://rekt.news/multichain-rekt2</a></figcaption></figure><h3>🔍 Why Are Traditional Bridges So Easy to Hack?</h3><h4>1. Centralized Multisig Structures</h4><ul><li>Too few validators</li><li>Heavy reliance on team insiders or close partners</li><li>Hackers just need a few “master keys” to unlock everything</li></ul><h4>2. Poor Private Key Management</h4><ul><li>Hot wallets hosted on cloud infrastructure are easily breached</li><li>Rogue employees or ex-founders can act maliciously</li></ul><h4>3. Social Engineering</h4><ul><li>Fake emails, impersonations, approval traps</li><li>Hackers don’t hack code — they hack humans</li></ul><p>Even if you increase multisig thresholds from 3/5 to 10/15, the problem doesn’t go away. <strong>As long as all assets sit in a shared vault, attackers only need to target the weakest few </strong>⚠️</p><h3>Fiamma’s Response: Isolated Safe Architecture™</h3><p>We realized the real fix isn’t just “harder locks.” It’s making sure <strong>there’s no single vault to drain in the first place</strong>.</p><p>Fiamma Bridge is fundamentally different from traditional multisig bridges.</p><blockquote><em>In Fiamma, </em><strong><em>every deposit is isolated and controlled by a different set of multisig signers</em></strong><em>.</em></blockquote><p>This new security paradigm is what we call:</p><h4>👉 Isolated Safe Architecture™</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xeu1_MSNXn-neVAb-sR8PA.png" /></figure><h3>What Is Isolated Safe Architecture™?</h3><p>Put simply:</p><blockquote><strong><em>Every user’s funds are stored in their own personal “safe”</em></strong><em>, co-controlled by </em><strong><em>the user + the bridge committee</em></strong><em>.</em></blockquote><p>This means:</p><ul><li>Each user’s assets are <strong>logically and cryptographically separated</strong></li><li>If a hacker wants to steal User A’s BTC, they <strong>must</strong> compromise User A’s key</li><li>Even if the entire committee is compromised, <strong>your BTC stays safe</strong></li><li>To steal all bridge assets, an attacker must breach <strong>every user</strong> + <strong>every committee key</strong> — a practical impossibility</li></ul><p>That’s why we call it a <em>“</em><strong><em>Safe</em></strong><em>”</em> — because no one else can get inside <strong>your vault</strong>.</p><h3>Visual Comparison: Traditional Multisig vs. ISA</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BmdtM_EbHmYEy0c2LNnoxA.png" /></figure><h3>Final Thoughts</h3><p>Traditional bridges keep repeating the same mistake:</p><ul><li>“The lock is complex, but all the keys are in one place”</li><li>“There are many signers, but the attack path is centralized”</li></ul><p>Fiamma Bridge, powered by <strong>Isolated Safe Architecture™</strong>, flips the model entirely:</p><blockquote><em>It’s not about building taller walls. It’s about making sure </em><strong><em>every door leads to a different room</em></strong><em>.</em></blockquote><blockquote><em>It’s not shared risk — it’s </em><strong><em>no shared attack surface</em></strong><em>.</em></blockquote><p>If legacy bridges are like massive bank vaults, Fiamma is like a sealed grid of <strong>independent personal safes</strong> — where each user holds real power, and no attacker can move your BTC without your consent.</p><p>In this “dark forest” of cross-chain finance, it’s time to protect your assets with a new secure system.</p><h3>About Fiamma</h3><p>Fiamma is redefining the Bitcoin on-chain wealth management experience for everyone. Backed by Lightspeed Faction, we empower anyone to build and grow their Bitcoin reserves through seamless, secure, and trust-minimized infrastructure via our flagship product, Fiamma One — a one-click BTCFi superapp. As a leading BitVM2 developer, Fiamma is the official Bitcoin bridge partner for ecosystems like Babylon and BOB, with our bridge already live on testnets across Ethereum, Arbitrum, BNB Chain, Monad, Solana, etc.</p><p><a href="https://fiammachain.io/">Website</a> | <a href="https://x.com/fiamma_labs">X (Twitter)</a> | <a href="https://discord.com/invite/8mCBXXjgvA">Discord </a>| <a href="https://t.me/fiammachain">Telegram</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e8196dd0652" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fiamma and Succinct Deliver the First Complete Groth16 Verifier on Bitcoin with Blake 3 Hashing]]></title>
            <link>https://medium.com/@Fiamma.io/fiamma-and-succinct-deliver-the-first-complete-groth16-verifier-on-bitcoin-with-blake-3-hashing-b4d50c9905f5?source=rss-365c2d512dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4d50c9905f5</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[succinct]]></category>
            <category><![CDATA[groth16]]></category>
            <category><![CDATA[bitvmbridge]]></category>
            <category><![CDATA[bitvm]]></category>
            <dc:creator><![CDATA[Ride (by Fiamma) ]]></dc:creator>
            <pubDate>Mon, 26 May 2025 20:11:18 GMT</pubDate>
            <atom:updated>2025-05-26T20:11:18.685Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PbZilnheFjf4bvPE.png" /></figure><p>We’re proud to introduce the first complete Groth16 verifier with Blake3 hashing implemented on Bitcoin, built through a deep integration of Fiamma’s BitVM2 infrastructure and Succinct’s SP1 prover. This milestone enables full zero-knowledge proof verification using Groth16 — directly on Bitcoin — with hash integrity checks and full pairing validation.</p><p>To ensure complete commitment verification on Bitcoin, we’ve adopted Blake3 hashing, a crucial upgrade from the previous system, where incomplete commitment verification left the bridge vulnerable to BTC theft by malicious operators. <strong>Fiamma has solved this critical vulnerability</strong> in the current BitVM2 bridge implementations.</p><p>In this article, we’ll explore how it works.</p><h3>What does the complete Groth16 verifier mean, and why is it important?</h3><p>Groth16 is a renowned pairing-based zk-SNARK system. Its principal function is to allow a prover to validate the accuracy of a statement to a verifier, without revealing any additional data. A distinct feature of Groth16 is its succinctness; the proofs generated are concise, occupying minimal storage and transmission space. This characteristic is pivotal for platforms like blockchain systems or privacy-focused protocols, where proof size is paramount.</p><p>At its core, the Groth16 verifier checks whether a multivariable polynomial. <em>t</em> satisfies the condition t(τ, π) = 0, which serves as the fundamental verification test.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/895/1*CwQKkuCXRCQOudd0NELboQ.png" /></figure><p>This equation validates the relationship between the proof [A, B, C], the inputs [a₁, a₂, ... aₘ], and the verifying key VK = [α, β, γ, δ, ...]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/921/1*vSjWyq01E65JTtC-czao0g.png" /></figure><p>The term,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*ETZOZEEKWlHjbX_RVzY37Q.png" /></figure><p>represents the <em>MSM </em>(Multi-Scalar Multiplication) computation. Since elliptic curve operations are computationally expensive on the verifier’s side, an optimization is to reduce their cost by replacing the full <em>inputs </em>with a hash. This allows the value of $$m$$ to be treated as a constant — an approach commonly adopted in many ZKEVM implementations on Ethereum.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1g6sJwjhInwG6sMj.png" /><figcaption>Fig1. Groth16 verification with Hash</figcaption></figure><h3>Ensuring Input Integrity with Digest Verification</h3><p>When the value of <em>m </em>is treated as constant, the actual <em>inputs </em>are designated as <strong>private inputs</strong>, while the corresponding <em>inputs_digest</em> is exposed as a <strong>public input</strong>. However, for verification to remain secure, the verifier must ensure that this digest actually corresponds to the private inputs used in the <em>Proof </em>check.</p><p><strong>It should be noted that if the verifier doesn’t check the </strong><em>inputs_digest</em><strong>, the prover could cheat the verifier. </strong>This is because the verifier only receives the <em>inputs_digest</em> and the Proof — without knowing what the <em>inputs_digest </em>actually represents. For example, the prover may claim to know an input <em>x </em>such that:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*9wBKSvINAsNQWVwipeqXZQ.png" /></figure><p>Clearly, the public input in this case would be [1,4]. But if the verifier only sees a <em>Digest </em>and doesn’t validate that the <em>inputs_digest</em> maps to [1,4], the prover could instead generate a proof for any arbitrary computation. As long as the structure appears valid, the verifier would wrongly accept the proof — compromising correctness.</p><h3>Why is it important for BitVM2 Bridge</h3><p>The completed verifier on Bitcoin could prevent the operator from stealing BTC from the bridge. If we only use digest as input of proof, we can’t ensure that the digest corresponds to the pre-image that it should be. Such as the operator should use transaction Burn A and PEG-OUT A in the claim. However, the operator uses proof of any computation to kick off the Claim transaction. Because on the Bitcoin side, it only checks whether the proof could be passed with the digest, but does not check what the digest is at all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sCH_9jIS87AhDSji.png" /><figcaption>Fig2. Operator steal BTC from Bridge</figcaption></figure><p>So, it’s imperative for us to add additional checks between the digest and the true pre-image. It means that when the operator uses other data which doesn’t correspond to the digest, the operator should be slashed as well.</p><h3>The First Complete Groth16 Verifier on Bitcoin</h3><p>Thanks to the latest <a href="https://docs.succinct.xyz/docs/sp1/generating-proofs/advanced#blake3-public-values-hashing">upgrade </a>of <a href="https://blog.succinct.xyz/bitcoin-sp1/"><strong>SP1</strong></a>, we’ve achieved the <strong>first complete implementation of a Groth16 verifier on Bitcoin</strong>. This advancement makes it possible to verify SP1-generated zero-knowledge proofs directly using <strong>Fiamma’s BitVM2 verifier</strong></p><p>To demonstrate this, the following code illustrates the actual script-level implementation used to perform a full verification. It includes:</p><ul><li><strong>Blake3-based input hashing</strong></li><li><strong>MSM preparation logic</strong></li><li><strong>Pairing checks for proof validation</strong></li></ul><p>These scripts show how all components — from hash verification to pairing logic — are integrated to form a trust-minimized and complete Groth16 verifier, executable on Bitcoin via BitVM2.</p><h4>1. The pseudocode of the Groth16 verification script implementation with Blake3</h4><pre>    pub fn split_verify_proof_with_blake3(<br>        pvk: &amp;PreparedVerifyingKey&lt;Bn254&gt;,<br>        precompute_lines: &amp;Vec&lt;G2Prepared&gt;,<br>    ) -&gt; (Vec&lt;Script&gt;, usize) {<br>        <br>        let blake3_hash_scripts = hash::blake3_u32::split_blake3();<br><br>        let msm_scripts = Self::split_prepare_inputs_optimization_split(pvk);<br><br>        let check_pairing_scripts = Self::split_check_pairing_bucket_split(precompute_lines);<br>        <br>        (<br>            [<br>                blake3_hash_scripts.clone(),<br>                msm_scripts.clone(),<br>                check_pairing_scripts,<br>            ]<br>            .concat(),<br>            blake3_hash_scripts.len(),<br>        )<br>    }</pre><h4>2. The pseudocode of the Groth16 verification script <strong>witness </strong>implementation with Blake3</h4><pre>    pub fn verify_proof_with_blake3_split(<br>        pvk: &amp;PreparedVerifyingKey&lt;Bn254&gt;,<br>        proof: &amp;Proof&lt;Bn254&gt;,<br>        public_inputs: &amp;[Fr],<br>        native_pub_inputs: &amp;[u8],<br>    ) -&gt; (bool, Vec&lt;ScriptBigUintContext&gt;) {<br>    <br>        let mut script_contexts = vec![];<br><br>        let mut sript_inputs = native_pub_inputs.clone().to_owned().to_vec();<br><br>        sript_inputs.reverse();<br><br>        // check 1: pub_hash = Blake3(native_pub_inputs);<br>        let (res, witness) = blake3_public_hash_reduce_fr(&amp;native_pub_inputs, &amp;sript_inputs);<br>        // check 2: public_inputs[1] == Fr::from_be_bytes_mod_order(pub_hash)<br>        assert_eq!(Fr::from_be_bytes_mod_order(&amp;res), public_inputs[1]);<br>        <br>        script_contexts.extend(witness);<br><br>        let (res, witness) = Self::prepare_inputs_split(pvk, public_inputs);<br>        script_contexts.extend(witness);<br><br>        let (res, witness) =<br>            Self::verify_proof_with_prepared_inputs_bucket_split(pvk, proof, &amp;res.into_group());<br>        script_contexts.extend(witness);<br><br>        (res, script_contexts)<br>    }</pre><h4>3. The E2E test example</h4><p>We wrote a Fibonacci instance to test the whole process. The test example:</p><pre>#[test]<br>//Checking https://github.com/fiamma-chain/sp1-bitvm-blake3/ for details<br>    fn test_groth16() {<br>        let fixture_path =<br>            PathBuf::from(env!(&quot;CARGO_MANIFEST_DIR&quot;)).join(&quot;../contracts/src/fixtures&quot;);<br>        let fixture_path = fixture_path.join(&quot;groth16-fixture.json&quot;);<br>        let fixture = std::fs::read_to_string(&amp;fixture_path).unwrap();<br>        let fixture: SP1FibonacciProofFixture = serde_json::from_str(&amp;fixture).unwrap();<br><br>        let proof = hex::decode(&amp;fixture.proof[2..]).unwrap();<br>        let public_inputs = hex::decode(&amp;fixture.public_values[2..]).unwrap();<br><br>        let ark_proof = load_ark_proof_from_bytes(&amp;proof[4..]).unwrap();<br>        let ark_vkey = load_ark_groth16_verifying_key_from_bytes(&amp;GROTH16_VK_BYTES).unwrap();<br>        let ark_public_inputs = load_ark_public_inputs_from_bytes(<br>            &amp;decode_sp1_vkey_hash(&amp;fixture.vkey).unwrap(),<br>            &amp;hash_public_inputs_with_fn(&amp;public_inputs, blake3_hash), // blake3<br>        );<br><br>        // ....Verify proof locally<br>        Groth16::&lt;Bn254&gt;::verify_proof(&amp;ark_vkey.clone().into(), &amp;ark_proof, &amp;ark_public_inputs)<br>            .unwrap();<br>        // ...Verify proof in BitVM2 Verifier<br>        bitvm::groth16::test_tools::subscript_lt_400KB::test_split_script_groth16_verifier_subscript_check_with_blake3_lt_400KB(<br>            ark_public_inputs.into(), ark_vkey, ark_proof,&amp;public_inputs<br>        );<br>    }</pre><h4>The following section highlights some key information:</h4><pre>// Checking https://github.com/fiamma-chain/sp1-bitvm-blake3/tree/main/data for details<br><br>vk: VerifyingKey { alpha_g1: (20491192805390485299153009773594534940189261866228447918068658471970481763042, 9383485363053290200918347156157836566562967994039712273449902621266178545958), beta_g2: (QuadExtField(6375614351688725206403948262868962793625744043794305715222011528459656738731 + 4252822878758300859123897981450591353533073413197771768651442665752259397132 * u), QuadExtField(10505242626370262277552901082094356697409835680220590971873171140371331206856 + 21847035105528745403288232691147584728191162732299865338377159692350059136679 * u)), gamma_g2: (QuadExtField(10857046999023057135944570762232829481370756359578518086990519993285655852781 + 11559732032986387107991004021392285783925812861821192530917403151452391805634 * u), QuadExtField(8495653923123431417604973247489272438418190587263600148770280649306958101930 + 4082367875863433681332203403145435568316851327593401208105741076214120093531 * u)), delta_g2: (QuadExtField(19629295988673812457237747993086053613709181874324227239033635205670891327060 + 17270349666695681994109533429817368669497520119106681015856196115021033411091 * u), QuadExtField(7606452412506804803120568203841502737122216991812443942893981403980455929856 + 9671211007953687162466560247240578603884908824862104008754446926069546380089 * u)), gamma_abc_g1: [(6712036353136249806951869451908368653566549662781372756321174254690599374583, 18149145036868871064182651529802275370638950642742152190925800889169295968585), (12384021290558951773126140100379496012525836638155233096890881157449062205923, 16530732960917040406371332977337573092100509754908292717547628595948196259098), (18749839173537272836199384751191600551090725238737491530604969678014545165197, 1828450848853234449784725988911172793808451038026258152543319358376349553777)] }<br>proof: Proof { a: (17757616286716265014907054195283507789878982270674072626866207773207292138096, 19858877562716308546494927946695717921085897663102371031171615544173707138429), b: (QuadExtField(16303356530394076424879343181474124406422425147274245545524407172356548774729 + 6386312428882894434341180845506592827580655629766259705878349136187769496682 * u), QuadExtField(2503015776023087686495886374740149237115497565780397567085084229496483568976 + 21863620051757457899730673946306128916915850889511753328806851867881512571113 * u)), c: (7412412751397267725059539974243720891206689881407746287876365489943010772952, 4749626842206354936057137191670727674590575345747365445525739916512900832447) }<br>public input: [BigInt([2081010597440243391, 8933620997411816115, 14244448838099968857, 876476526593916]), BigInt([6568716051497370742, 7772415922033085877, 8208084356351775240, 1563921272962275877])]<br>native public input: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 20, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 26, 109, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 42, 194]<br>...<br>blake3 script len: 2<br>...<br>blake3 contains 2 sub_scripts<br>groth16::split_verify_proof contains 14820 sub_scripts, <br>msm contains 510 sub_scripts<br>...<br>witness_15331, witness_len:25 input_len:24, output_len:1<br>subscript[15331] size = 2275 bytes<br>subscript[15331] runs successfully!<br>...<br>max_nb_stack_items = 614<br>max_input_len:12, min_input_len:2<br>max_output_len:6, min_output_len:0<br>max_witness_len:14, min_witness_len: 4<br>...<br>total chunks size: 15332</pre><h3>About Succinct</h3><p><a href="https://www.succinct.xyz/">Succinct </a>is building a protocol on Ethereum that coordinates a distributed network of provers to generate zero knowledge proofs for any piece of software. This protocol creates a two-sided marketplace between provers and requesters, enabling anyone to receive proofs for applications such as blockchains, bridges, AI agents, games, and more.</p><h3>About Fiamma</h3><p><a href="https://fiammalabs.io/">Fiamma</a><strong> </strong>is unlocking real-world use cases for Bitcoin, transforming it into a dynamic asset and the foundation for a decentralized internet and financial system. Backed by Lightspeed Faction and L2IV, Fiamma leads innovation with the first BitVM2-powered infrastructure , including a trust-minimized Bitcoin bridge, Bitcoin settlement layer, and a non-custodial, seamless “one-click” experience for both end users and institutions to utilize native Bitcoin.</p><p>With deep integration and strategic support from Babylon, BOB, Arbitrum, Satlayer, and RiscZero, Fiamma is building the ultimate Bitcoin gateway and shaping the future of decentralized systems.</p><p><a href="https://fiammachain.io/">Website</a> | <a href="https://x.com/fiamma_labs">X (Twitter)</a> | <a href="https://discord.com/invite/8mCBXXjgvA">Discord </a>| <a href="https://t.me/fiammachain">Telegram</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4d50c9905f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BBBB Blog 004: Challenge Protocol]]></title>
            <link>https://medium.com/@Fiamma.io/bbbb-blog-004-challenge-protocol-15153d318671?source=rss-365c2d512dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/15153d318671</guid>
            <category><![CDATA[bbbb]]></category>
            <category><![CDATA[bitcoin-bridge]]></category>
            <category><![CDATA[bitvmbridge]]></category>
            <dc:creator><![CDATA[Ride (by Fiamma) ]]></dc:creator>
            <pubDate>Thu, 23 Jan 2025 06:25:39 GMT</pubDate>
            <atom:updated>2025-01-23T07:22:24.234Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YrRYuhgdv5yAGlOHm-ipyg.png" /></figure><p>From previous blogs, we understand that the Challenger plays the most crucial role in the Bridge protocol. The entire protocol’s security is predicated on having at least one honest Challenger. Given the importance of Challengers, we aim to increase the number of active Challengers in the operation of the Bridge. To achieve this goal, we propose:</p><ol><li>Lowering the barriers to entry for becoming a Challenger;</li><li>Incentivizing the honest actions of Challengers:</li></ol><ul><li>Including verification of true claims;</li><li>Including challenges to false claims;</li></ul><p>3. Allowing sufficient time for Challengers to identify malicious behavior and initiate challenges.</p><p>This article will primarily analyze the challenge design within the Bridge.</p><h3>Why is a Challenge Needed?</h3><p>BitVM2 is a core module in Trust-minimized Bridges, supporting fraud-proof verification of ZKPs on Bitcoin. The main use case for fraud-proof mode comes from Ethereum’s Optimistic Rollup mode, such as Arbitrum. As seen in Arbitrum’s <a href="https://docs.arbitrum.io/how-arbitrum-works/bold/bold-economics-of-disputes#the-dispute-period">developer documentation</a>, since Ethereum cannot directly verify the correctness of the state on the sidechain Arbitrum (unlike ZK Rollups, where Ethereum can verify the state through proof validation), when a validator on Ethereum claims a state from Arbitrum, a challenge period is required to allow other nodes sufficient time to detect and penalize any fraudulent behavior by the validator.</p><p>In Trust-minimized Bridges, the Operator needs to initiate a PEG-OUT transaction, paying users in advance with their own BTC and generating a ZK proof to demonstrate “a user has successfully initiated a Burn transaction on the Sidechain and the Operator has successfully completed a PEG-OUT transaction as a proxy.” The Operator claims this proof is true, and to prevent Operator malfeasance, a robust challenge mechanism is necessary to ensure:</p><ol><li>If the Operator acts maliciously, there must be an honest challenger who can initiate a challenge and penalize the Operator;</li><li>If the Operator is honest, they must be able to retrieve the user’s locked BTC.</li></ol><h3>Key Points in the Challenge Protocol</h3><p>To achieve a production-ready challenge protocol, several critical aspects must be considered:</p><ol><li>Hardware requirements for challengers: Lower hardware barriers allow more challengers to participate in claim verification;</li><li>Motivation for challengers to participate: Certain behaviors of challengers should be incentivized to ensure active challengers are always active in the protocol;</li><li>Complexity of the challenge protocol: A complex challenge process extends the challenge period and decreases challengers’ motivation to initiate challenges, also affecting user experience;</li><li>Appropriate reward and penalty mechanisms: An effective challenge protocol should have minimal incentives for validators to act maliciously, while providing sufficient incentives for challengers to verify claims and initiate challenges;</li><li>Reasonable challenge period: To ensure protocol security (allowing challengers sufficient time to verify claims) while maintaining user experience.</li></ol><h3>Hardware Requirements</h3><p>If a user wants to become a challenger, they might hope to verify validator claims in real-time, but only need to run a very lightweight node, such as a mobile app, a chrome extension, or a PC program, requiring minimal hardware resources. This design is extremely user-friendly. In the design of the Trust-minimized Bridge, we hope challengers can promptly verify Operator claims: “the verification result of a certain Proof is true.” Challengers need to recompute the Proof verification locally to check if the Operator’s claim is correct. Fortunately, ZK verification computations are concise and can be performed in milliseconds on a standard smartphone. This allows us to confidently develop corresponding applications for challengers, such as mobile apps, web plugins, etc., enabling any user to become a Bridge challenger at low cost.</p><h3>Incentivizing Challengers</h3><p>Even if we can lower the hardware barriers for becoming a challenger, without effective incentives, users will not be motivated to become challengers. If we hope to penalize a malicious Operator, it is essential that many active challengers are first to complete the verification. In the overall design of the Bridge protocol, challengers undertake two main tasks:</p><ol><li>Locally verify the correctness of claims;</li><li>If there is a dispute, initiate a challenge and penalize the Operator. Clearly, if a challenger successfully initiates a challenge, they should be incentivized; but should those who perform step a also be incentivized? The answer is affirmative. If step 1 is not incentivized, considering the infrequency of Operator misconduct, challengers will slowly become less active over time, diminishing in number to the point where few are available to respond when an Operator does act maliciously. If these few challengers are persuaded by the Operator to collaborate in malfeasance, the security of the Bridge will be significantly compromised. Therefore, challengers’ local verification actions should be incentivized to keep them actively engaged.</li></ol><h3>Protocol Complexity</h3><p>We know that when there is a dispute over a claim result, the final handling of the dispute occurs on-chain. If it is Arbitrum, it happens on Ethereum; if it is a Bridge, it happens on Bitcoin. Considering cost, we only want the smallest disputable computation unit to be processed on-chain, hence finding this smallest unit becomes the most complex module of the protocol, which we call the Bisection protocol. For more detailed principles, refer to Arbitrum’s <a href="https://docs.arbitrum.io/how-arbitrum-works/fraud-proofs/challenge-manager">developer documentation</a>.</p><p>In the Arbitrum protocol, the dispute resolution period is one week, dependent on the underlying complex protocol design, which requires finding the disputable block from many blocks based on binary search, then finding the disputable instruction from within that block.</p><p>In the design of the Trust-minimized Bridge, the dispute resolution period is very short, capable of identifying the disputable sub-script (of which there are only about 1000) within seconds. This not only significantly reduces the challenge period but also enables challengers to more quickly receive benefits, further motivating them to initiate challenges.</p><h3>Reward and Penalty Mechanisms</h3><p>In the paper “<a href="https://arxiv.org/pdf/2308.02880">Incentive Schemes for Rollup Validators</a>,” two roles are defined:</p><ol><li>Asserter: make a claim for a computation that is true or false.</li><li>Checker: check the result of computation made by the Asserter.</li></ol><p>And several important metrics to consider during the challenge protocol design process are provided:</p><ol><li>C: Cost for users to check the computation,</li><li>R: Cost staked by the Asserter, which should be completely forfeited if the Asserter acts maliciously. A portion goes to the challenger as an incentive, and another portion is sent to a black hole address;</li><li>L: Cost for a Checker to become a challenger. We always hope the protocol contains active honest challengers, so these funds can be forfeited if there is a liveness issue;</li><li>U: Maximum potential benefit the Asserter could receive if they successfully commit misconduct</li></ol><p>In the design of the Trust-minimized Bridge, the Operator plays the role of the Asserter, and Bridge challengers are the Checkers. For the Operator, we hope U &lt; R, so the Operator has no incentive to commit misconduct; for the Checker, we hope the value of C is small enough, meaning anyone can verify the Operator’s Claim at a low cost.</p><p>For the Trust-minimized Bridge, we believe three additional metrics should be considered:</p><ol><li>K: Cost for a user to initiate a challenge;</li><li>D: Reward for a user successfully challenging;</li><li>N: Reward for a user submitting verification results;</li><li>A: Cost for the Operator to cooperate with the challenge</li></ol><p>To incentivize more users to become challengers and to continuously check the Operator’s claims and initiate challenge transactions at critical moments, we should meet:</p><ol><li>N &gt; C: Ensure more users can become challengers and conduct local verifications；</li><li>D &gt; C + K: The incentive a challenger receives for initiating and successfully completing a challenge should exceed the costs;</li><li>K &gt; A: Malicious challenges increase the Operator’s on-chain expenses, so the malicious challenger’s funds should compensate the Operator, thus deterring challengers from initiating malicious challenges.</li></ol><h3>Challenge Period</h3><p>In fraud-proof mode, the challenge period is typically set to 7 days due to a specific attack known as the <a href="https://dl.acm.org/doi/pdf/10.1145/3631310.3633493">Fraud Proof Denial</a> attack, which is defined as:</p><p>“For optimistic rollups, preventing a validator from submitting a fraud proof would result in the incorrect outcome of the challenge game. If this can be achieved by flooding the underlying layer one with transactions with high gas fees such that the fraud proof is never included in a block until the timeout expires, the rollup will suffer from an incorrect-but-final outcome on the proof. In turn, the system state may not be one that could be achieved by honest actors; this is why optimistic rollups have a seven day challenge period.”</p><p>This is a type of censorship attack, where the attacker tries to delay the confirmation time of the fraud-proof transaction, making it exceed the challenge period, thus ensuring that malicious behavior is not punished. Fortunately, Bitcoin is a fully decentralized network and a censorship-resistant network. Attackers cannot control Bitcoin miners to refuse to package a certain coin transaction.</p><p>Therefore, in the design of the Trust-minimized Bridge, based on all previous designs, we have:</p><ol><li>Sufficiently many active challengers;</li><li>These challengers are sufficiently motivated to verify and initiate challenge protocols;</li><li>Transactions will not be censored by the Bitcoin network; Thus, we can entirely design a shorter challenge window, such as within 24 hours.</li></ol><h3>What’s Next?</h3><p>Challenge protocols still have many open problems that need further discussion, such as finding a balance between incentives and penalties. We believe this is a long-term topic and will vary depending on the product form. We look forward to more discussions with the community. In subsequent blogs, we will continue to describe the core module design of the Bridge:</p><ol><li>Light Client Design Issues in the Bridge;</li><li>Cost and Incentive</li><li>Detailed design of the Forced Exit Mode in the Bridge</li></ol><p>Stay tuned.</p><h3>About Fiamma</h3><p>Fiamma is unlocking real-world use cases for Bitcoin, transforming it into a dynamic asset and the foundation for a decentralized internet and financial system. Backed by Lightspeed Faction and L2IV, Fiamma leads innovation with the Fiamma Bridge and Fiamma Layer, the first products to implement BitVM2. These foundational technologies are just the beginning, as Fiamma continues to develop protocols that expand Bitcoin’s potential across programmable blockchains and real-world applications. With a growing network of strategic partners, including Babylon, BOB, Satlayer, and RiscZero, Fiamma is shaping the future of decentralized systems.</p><p><a href="https://fiammachain.io/">Website</a> | <a href="https://x.com/fiamma_labs">Twitter</a> | <a href="https://discord.com/invite/8mCBXXjgvA">Discord </a>| <a href="https://t.me/fiammachain">Telegram</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15153d318671" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BBBB Blog 003: Fungible Bridge]]></title>
            <link>https://medium.com/@Fiamma.io/bbbb-blog-003-fungible-bridge-99894ed018af?source=rss-365c2d512dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/99894ed018af</guid>
            <category><![CDATA[bitcoinbrid]]></category>
            <category><![CDATA[bitvmbridge]]></category>
            <category><![CDATA[fiammabridge]]></category>
            <category><![CDATA[bbbb]]></category>
            <dc:creator><![CDATA[Ride (by Fiamma) ]]></dc:creator>
            <pubDate>Thu, 02 Jan 2025 13:10:23 GMT</pubDate>
            <atom:updated>2025-01-02T13:10:23.870Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3L4YCf6iEN9_jFpAWmwPQA.png" /></figure><p>In our blogs, <a href="https://medium.com/@Fiamma.io/bbbb-blog-001-security-analysis-4c239cc0b4db">BBBB Blog 001: Security</a> and <a href="https://medium.com/@Fiamma.io/bbbb-blog-002-liveness-c36ac972f980">BBBB Blog 002: Liveness</a>, we conducted a thorough analysis of the most critical attributes of the Bridge protocol. Similarly, we aim to provide the best user experience regarding the asset transfer functionality of the Bridge.</p><p>This article primarily addresses the issue of fungibility within the Bridge, building on our previous analyses. Users encounter several challenges during the PEG-OUT process:</p><ol><li><strong>Amount Inflexibility</strong> <strong>Issue</strong>: When the amount users wish to PEG-OUT is not in the Operator-maintained PEG-IN amount list, they cannot directly proceed with the exit.</li><li><strong>Asset Locking Issue</strong>: If some operators go offline, leading to some assets not being able to be withdrawn without permission, two methods can be utilized:</li></ol><ul><li><strong>Centralized Method</strong>: Requires individual signatures from the committee and the user to assist in user PEG-OUT.</li><li><strong>Decentralized Method</strong>: Users proceed through the Forced Exit Module (the details of this solution is still under discussion).</li></ul><h3>Order Book-Based Bridge &amp; Liquidity Market Making</h3><p>Currently, the PEG-OUT mode of the BitVM2 Bridge operates like an order book exchange. If we consider all user PEG-IN assets as buy orders, then the user’s PEG-OUT process resembles placing a sell order. Transactions can only be completed when the amounts of PEG-IN and PEG-OUT match. However, the amounts for PEG-IN and PEG-OUT are likely not to match, requiring a role similar to that of market makers (MM). When users have varying amounts of PEG-OUT, MMs can actively PEG-IN an equivalent amount of BTC assets. We define this role as<strong> Bridge Liquidity Market Maker (LMM).</strong></p><p>For the Bridge to achieve fungibility:</p><ol><li>mamaBTC can be transferred to anyone.</li><li>The PEG-OUT amount can be any amount.</li></ol><p>The first feature is naturally supported by the BitVM2 bridge. Next, we will analyze how to support users in PEG-OUTing any amount.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H-XxUqUU6gDRUEmi5Am6Ew.png" /></figure><p>There are 4 scenarios that we have to consider:</p><ol><li>Normal case: Mike could PEG-OUT successfully with 10 BTC</li><li>Abnormal case 1: The amount that Jane wants to PEG-OUT exceeds the maximum value (102 BTC &gt; 100 BTC)</li><li>Abnormal case 2: The amount that Bob wants to PEG-OUT doesn’t exist currently (0.5 BTC does not exist)</li><li>Abnormal case 3: Some wrapped BTC were transferred to the Burn address (0.5 BTC in the Burn address)</li></ol><p>Then how can we solve these problems?</p><h3>Abnormal case 1</h3><p>This case could be easily solved. We set up the maximum limitation for the PEG-IN process. But maybe one user on the sidechain might get more wrapped BTC and then plan to PEG-OUT.</p><p>So, for this case, the user has to PEG-OUT all the wrapped BTC with a few separate transactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aaDL4CZ_Hv8HNsl5ZzpYmQ.png" /></figure><p>However, we will provide an additional approach (liquidity provider) to improve the user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-zL88FAuC3UN7OuH1d7FqA.png" /></figure><p>So, in this approach, the user could directly peg-out with the help of LP (liquidity provider). The LP should get more fees and the users should pay it.</p><h3>Abnormal case 2</h3><p>Ideally, we hope that the amount distribution between bitcoin and sidechain should be like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-R7ifBYy1xspsXseRSu1LA.png" /></figure><p>In this scenario, everyone could PEG-OUT smoothly. But in the real case, most of the amount is not the same</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JreEqrPXkxeYtFq6hdqTMA.png" /></figure><p>To solve this problem, we use a few ways:</p><ol><li>Support a wider range of amount types;</li><li>Introduce the roles of liquidity providers — they could get some tokens and additional fees as rewards;</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ILlsidb8XOQmb8Cs8gRZjA.png" /></figure><p>There is a little difference between Abnormal Case 2 and Abnormal Case 1.</p><p>In Abnormal Case 2: the user does not need to pay additional fees for the LP.</p><p>In Abnormal Case 1: the user does need to pay additional fees for the LP.</p><p>Now, the overall flow should be like in the following picture:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*spLwE_s96y0ivoZU-geDQQ.png" /></figure><h3>Abnormal case 3</h3><p>If there is some wrapped BTC transferred to a burn (black hole) address by accident. This means that there will be some BTC locked in Bridge.</p><p>The good thing is that the LPs can also help users take BTC back only if they can provide proof to prove that they really transferred some wrapped BTC to this address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ofQiQ9sgvdiGAEpc6mpnyA.png" /></figure><p>In this case, we have to ensure the burn address is a black hole address, like the 0x00…000 address.</p><h3>Forced exit module with fungible case</h3><p>In the normal case, the receiver (operator) is deterministic at the pre-signed phase and each operator will maintain a transaction list (all transactions that the receiver is himself) to know how much BTC he can take.</p><p>For example:</p><p>Operator A could take 100 BTC</p><p>Operator B could take 50 BTC</p><p>It means there are 150 wrapped BTC in the sidechain total, but now operator A is offline.</p><p>So for operator B, it could only pay 50BTC. For other users, they cannot PEG-OUT successfully unless Operator A is online again.</p><p>To solve this problem, we introduce the forced exit module for users. The general idea is the user will pre-sign a few additional transactions with the bridge committee but not specify the receiver (<a href="https://wiki.bitcoinsv.io/index.php/SIGHASH_flags"><strong>SIGHHASH_NONE</strong></a>). But the condition is, that the user has to provide a valid proof for the burn transaction, otherwise, he cannot take the BTC back.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yagNRj8ly_oGtEuNdL1Ngg.png" /></figure><p><strong>A more radical approach:</strong></p><p><strong>In the normal case, the receiver (operator) is non-deterministic at the pre-signed phase and all operators share a common BTC pool they can take.</strong></p><p>For example:</p><p>Operator A could take 100 BTC</p><p>Operator B could take <strong>the same</strong> 100 BTC as well</p><p><strong>So the advantage is that only one operator is honest. All users could peg out smoothly</strong></p><p><strong>But let’s assume all operators are offline, we should support forced exit module as well.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*42yCO_Nm34Z9J3Dgr8_euw.png" /></figure><h3><strong>What’s Next?</strong></h3><p>The LP model can enhance the user experience for exits but also brings a longer exit time, which is a trade-off for users. The Fiamma Bridge will support two modes for users to choose their exit method. Fiamma Bridge is currently live on the testnet and welcomes users to experience it. In upcoming blogs, we will continue to describe the core module design of the Bridge:</p><ul><li>Challenge Period Timing in the Bridge</li><li>Light Client Design Issues in the Bridge</li><li>Cost and Incentive Analysis in the Bridge</li><li>Proposed Forced Exit Mode in the Bridge</li><li>…</li></ul><p>Stay tuned.</p><h3>About Fiamma</h3><p>Fiamma is unlocking real-world use cases for Bitcoin, transforming it into a dynamic asset and the foundation for a decentralized internet and financial system. Backed by Lightspeed Faction and L2IV, Fiamma leads innovation with the Fiamma Bridge and Fiamma Layer, the first products to implement BitVM2. These foundational technologies are just the beginning, as Fiamma continues to develop protocols that expand Bitcoin’s potential across programmable blockchains and real-world applications. With a growing network of strategic partners, including Babylon, BOB, Satlayer, and RiscZero, Fiamma is shaping the future of decentralized systems.</p><p><a href="https://fiammachain.io/">Website</a> | <a href="https://x.com/fiamma_labs">Twitter</a> | <a href="https://discord.com/invite/8mCBXXjgvA">Discord </a>| <a href="https://t.me/fiammachain">Telegram</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99894ed018af" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BBBB Blog 002: Liveness]]></title>
            <link>https://medium.com/@Fiamma.io/bbbb-blog-002-liveness-c36ac972f980?source=rss-365c2d512dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/c36ac972f980</guid>
            <category><![CDATA[bbbb]]></category>
            <category><![CDATA[fiamma]]></category>
            <category><![CDATA[bitcoin-bridge]]></category>
            <category><![CDATA[fiammabridge]]></category>
            <dc:creator><![CDATA[Ride (by Fiamma) ]]></dc:creator>
            <pubDate>Tue, 24 Dec 2024 10:42:03 GMT</pubDate>
            <atom:updated>2024-12-24T10:42:03.749Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cc4WhzqJKuLuugtv5x9pWw.png" /></figure><p>In <a href="https://medium.com/@Fiamma.io/bbbb-blog-001-security-analysis-4c239cc0b4db">BBBB Blog 001</a>: Security, we outlined how to ensure the financial security of the Bridge. This entails keeping the funds within the Bridge secure at all times and ensuring users always receive the correct amount of BTC or mamaBTC. mamaBTC is the tokenized BTC minted in a trust-minimized way via Fiamma Bridge. While BBBB Blog 001: Security addresses whether users receive the correct quantity of BTC or mamaBTC, this article focuses on whether users can actually obtain the accurate quantity of BTC or mamaBTC.</p><p>This article primarily discusses the liveness issues within the Bridge and the roles involved:</p><ol><li><strong>Minter</strong>: Calls the mint contract function to send mamaBTC to users on the Sidechain.</li><li><strong>Operator</strong>: Helps users exit quickly and earns a fee in the process.</li><li><strong>Challenger</strong>: Monitors and verifies whether the Operator is acting maliciously.</li><li><strong>Relayer</strong>: Syncs block header information.</li><li><strong>Prover</strong>: Generates ZK light client proofs and ZK inclusion proofs.</li></ol><p>Ideally, even if there are liveness problems with the Bridge, users should still be able to achieve their goals. Here, we’ll discuss how to balance the liveness issues concerning these roles in engineering.</p><h3><strong>Minter Liveness</strong></h3><p>The role of the Minter is primarily during the PEG-IN process, assisting users by calling the mint contract method on the Sidechain to mint an equivalent amount of mamaBTC. From the article on Bridge safety, we know it is impossible for the Minter to act maliciously, but if the Minter refuses to provide services, how can users continue to receive the correct amount of mamaBTC on the Sidechain? We can make the mint function of the contract open to anyone who provides valid data, PEG-IN transaction information, and Merkle proof information, which effectively prevents the attack arising from Minter’s denial of service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*usi49GjYLf-zxekufvGWew.png" /><figcaption>Fig 1. Minter Liveness</figcaption></figure><h3><strong>Operator Liveness</strong></h3><p>In the design of the Bridge, the Operator role helps users complete exits more quickly. This is because the Operator verifies the validity of the user-initiated Burn transaction and pays the user in advance using their own BTC, then initiates a Kick-off transaction to take an equivalent amount of BTC from the Bridge pool, earning transaction fees as part of the profits. Before analyzing Operator liveness, we need a simple explanation of how Operators work in the BitVM2 bridge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b2v-S9Cfb_4-0hgw5c2s9Q.png" /><figcaption>Fig 2. Operator PEG-IN List</figcaption></figure><p>For ease of understanding, let’s assume there are two operators in the Bridge. When a user initiates a PEG-IN request, an operator can choose whether to accept this user request based on their needs. In the design of the BitVM2 Bridge, when a user pre-signs some transactions with the Bridge Committee, it is already determined which operator will be the future recipient of this locked BTC. This means that each operator is entitled to a different total amount of BTC. The total amount of BTC that all operators can take should be equal to the total amount of mamaBTC issued on the Sidechain. Let’s assume that Operator_2 has a Liveness issue and cannot serve the user’s PEG-OUT, what happens then?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PhKR9JN9yEF-gBtUU7yQmg.png" /><figcaption>Fig 3. Operator_2 Liveness</figcaption></figure><p>Since Operator_1 can only take a total of 10 BTC from the bridge pool, Operator_1 can only handle PEG-OUT requests worth a total of 10 BTC. These users could be User 2, or Users 1 and 3 (note, we are temporarily not discussing inconsistent amounts, which will be introduced in a separate article later). Operator_1 has no incentive to accept more user PEG-OUT requests, as they cannot take over Operator_2’s quota. This gives us the direction for our next iteration:</p><ol><li>How can all operators share a PEG-IN list, so even if an operator experiences a Liveness issue, the operators still providing services still have the incentive to provide PEG-OUT services to users;</li><li>In extreme cases, if all operators refuse to provide services, how can users normally exit from the Sidechain and take away the BTC locked on Bitcoin?</li></ol><p>The above two issues will be discussed in more detail when we describe the Bridge’s forced exit module (currently, feasibility and security are still under assessment).</p><h3><strong>Challenger, Relayer, &amp; Prover Liveness</strong></h3><p>As mentioned in the article on bridge safety, challenger liveness can determine the entire bridge’s security and is the only means to prevent both operators and users from successfully acting maliciously. During the entire challenge period, as long as there is at least one honest challenger, the entire bridge is secure.</p><p>The relayer’s role in the bridge is mainly to store necessary block data and proof data for the Bitcoin chain or sidechains in the light client. Since the light client itself will verify the validity of these data, the BitVM2 bridge protocol can operate normally as long as there is at least one honest relayer node.</p><p>The Prover’s role in the Bridge is mainly to generate relevant ZK proofs, including ZK light client proofs, ZK inclusion proofs, aggregate proofs, etc. Only one honest prover is needed for the BitVM2 Bridge protocol to operate normally.</p><p>Although these three roles play different roles in the Bridge, they share common characteristics:</p><ol><li>Permissionless: Anyone can become these three roles, therefore, under reasonable incentives, the scale of these roles will continue to grow;</li><li>1-N honest: As long as there is at least one honest node, the entire Bridge protocol is secure and stable.</li></ol><p><strong>What’s Next?</strong> In subsequent product iterations, we will gradually open applications for the above roles, progressively realizing the decentralization of the entire Bridge product. We aim to provide users with sustainable bridge services that will not be interrupted by any role’s liveness issues. In subsequent blogs, we will continue to describe the core module design of the Bridge:</p><ul><li>Fungibility Issues in the Bridge</li><li>Challenge Period Timing in the Bridge</li><li>Light Client Design Issues in the Bridge</li><li>Cost and Incentive Analysis in the Bridge</li><li>Proposed Forced Exit Mode in the Bridge…</li></ul><p>Please stay tuned!</p><h3>About Fiamma</h3><p>Fiamma is unlocking real-world use cases for Bitcoin, transforming it into a dynamic asset and the foundation for a decentralized internet and financial system. Backed by Lightspeed Faction and L2IV, Fiamma leads innovation with the Fiamma Bridge and Fiamma Layer, the first products to implement BitVM2. These foundational technologies are just the beginning, as Fiamma continues to develop protocols that expand Bitcoin’s potential across programmable blockchains and real-world applications.</p><p><a href="https://fiammachain.io/">Website</a> | <a href="https://x.com/fiamma_labs">Twitter</a> | <a href="https://discord.com/invite/8mCBXXjgvA">Discord </a>| <a href="https://t.me/fiammachain">Telegram</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c36ac972f980" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fiamma announces $4M seed round led by Lightspeed Faction and L2 Iterative Ventures]]></title>
            <link>https://medium.com/@Fiamma.io/fiamma-announces-4m-seed-round-led-by-lightspeed-faction-and-l2-iterative-ventures-747995d56804?source=rss-365c2d512dfb------2</link>
            <guid isPermaLink="false">https://medium.com/p/747995d56804</guid>
            <category><![CDATA[fundraising]]></category>
            <category><![CDATA[bitvm]]></category>
            <category><![CDATA[bitcoin-bridge]]></category>
            <category><![CDATA[bitvmbridge]]></category>
            <category><![CDATA[fiamma]]></category>
            <dc:creator><![CDATA[Ride (by Fiamma) ]]></dc:creator>
            <pubDate>Tue, 24 Dec 2024 05:50:12 GMT</pubDate>
            <atom:updated>2024-12-24T05:53:04.505Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This article is brought to you by COINTELEGRAPH. For the original article, please visit: </em><a href="https://cointelegraph.com/press-releases/fiamma-announces-4m-seed-round-led-by-lightspeed-faction-and-l2-iterative-ventures"><em>https://cointelegraph.com/press-releases/fiamma-announces-4m-seed-round-led-by-lightspeed-faction-and-l2-iterative-ventures</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LZkcdSJUhLuCSN1LpEkAVQ.jpeg" /></figure><p>Fiamma, a Bitcoin and ZK infrastructure company transforming Bitcoin into a dynamic and programmable asset, today announced an oversubscribed $4M seed round investment led by Lightspeed Faction and L2IV. Additional participating investors include Astera Ventures, Contribution Capital, Sats Ventures, Chapter One, and FoundersHead. The investment also includes participation from key strategic investors in the Bitcoin infrastructure space, such as BOB (Build on Bitcoin), alongside various angel investors such as the founders of Satlayer and Daedalus.</p><p>The company plans to utilize this investment to scale Fiamma’s operations, accelerate product development, and drive adoption of its foundational technologies; Fiamma Bridge, the first trust-minimized Bitcoin bridge, and Fiamma Layer, the first ZK verification layer on Bitcoin powered by BitVM2.</p><p>Yovela Luo, co-founder and CEO of Fiamma, states:</p><blockquote><em>“Bitcoin is one of the world’s most valuable assets, yet over 98% of it remains idle. At Fiamma, we’re activating this dormant asset, utilizing it in the most trustless and secure manner. This ushers in a Bitcoin renaissance, seamlessly weaving it into everyday life.”</em></blockquote><p>Fiamma’s innovations represent the first implementations of BitVM2, a breakthrough that enables Bitcoin to not only scale but also interact with other programmable blockchains in the most trustless way. The company pioneered the development and implementation of the most efficient and smallest verifiers in Bitcoin script (Fflonk and Groth16). This innovation lays the groundwork for highly optimized ZK verification, with a continued commitment to advancing and refining these verifiers.</p><p>Cyimon Chen, co-founder and CTO of Fiamma, remarks:</p><blockquote><em>“With seven years as a ZK enthusiast and inspired by the BitVM paper, we quickly harnessed our expertise to develop the first functional ZK verifiers for Bitcoin.”</em></blockquote><p>Bitcoin’s unmatched security and decentralized nature have long been underutilized for real-world applications. Fiamma’s groundbreaking technology unlocks Bitcoin’s potential to power programmable financial systems, including but not limited to stablecoins, payments, lending platforms, decentralized applications, pragmatically trustless cross-chain interoperability, DeFi protocols, and other innovative use cases — all while maintaining a trust-minimized and secure architecture.</p><p>As part of a broader ecosystem effort, Fiamma is working closely with strategic partners including the ones in the ZK and Bitcoin space. These collaborations will accelerate innovation and adoption while positioning Bitcoin as the backbone of the decentralized internet and financial systems. To celebrate this milestone, Fiamma is launching The Mama Code <a href="https://test-bridge.fiammachain.io/register">testnet campaign</a>, inviting users to engage with the Fiamma Bridge and explore its innovative capabilities. Early adopters can participate and earn rewards.</p><h3>Investor Quotes</h3><p>Clara Boh at Lightspeed Faction, said:</p><blockquote><em>“trustless bridging infrastructure is needed to maximize the utility and functionality of Bitcoin. Fiamma’s implementation of BitVM2 via its Bitcoin-secured ZK proof verification network paves the way for trustless bridging, scalability and Bitcoin-native applications. We are excited to support the Fiamma team as they strive to refine new opportunities for the Bitcoin ecosystem.”</em></blockquote><p>Kevin Lee and Weikeng Chen at L2IV, added:</p><blockquote><em>“Fiamma represents a groundbreaking step forward in bringing additional functionality to Bitcoin. Its unique architectural design seamlessly integrates advanced off-chain computation and verification through BitVM2, unlocking programmability and scalability without compromising Bitcoin’s core security and decentralization principles. By leveraging this innovative framework, Fiamma enables features such as trustless smart contracts and composable DeFi, previously thought unattainable on Bitcoin.</em></blockquote><blockquote><em>The introduction of BitVM2 is particularly transformative — it pushes the boundaries of Bitcoin’s scripting capabilities, allowing for more expressive and flexible execution of decentralized applications. This not only enhances the utility of Bitcoin but also redefines its role within the broader blockchain ecosystem. At L2 Iterative Ventures, we are proud to lead this financing round, recognizing Fiamma as a catalyst for innovation and a pivotal force in reshaping Bitcoin’s future. Their solution positions Bitcoin as a true hub for decentralized applications, making it a cornerstone for the next wave of blockchain adoption.”</em></blockquote><h3>About Fiamma</h3><p>Fiamma is unlocking real-world use cases for Bitcoin, transforming it into a dynamic asset and the foundation for a decentralized internet and financial system. Backed by Lightspeed Faction and L2IV, Fiamma leads innovation with the Fiamma Bridge and Fiamma Layer, the first products to implement BitVM2. These foundational technologies are just the beginning, as Fiamma continues to develop protocols that expand Bitcoin’s potential across programmable blockchains and real-world applications. With a growing network of strategic partners, including Babylon, BOB, Satlayer, and RiscZero, Fiamma is shaping the future of decentralized systems.</p><p><a href="https://fiammachain.io/">Website</a> | <a href="https://x.com/fiamma_labs">Twitter</a> | <a href="https://discord.com/invite/8mCBXXjgvA">Discord </a>| <a href="https://t.me/fiammachain">Telegram</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=747995d56804" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>