<?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[boltzhq - Medium]]></title>
        <description><![CDATA[⚠️ Moved to blog.boltz.exchange ⚠️ - Medium]]></description>
        <link>https://medium.com/boltzhq?source=rss----30d0837e45db---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>boltzhq - Medium</title>
            <link>https://medium.com/boltzhq?source=rss----30d0837e45db---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 04:50:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/boltzhq" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Recap 2020 — A look at lightning and Boltz]]></title>
            <link>https://medium.com/boltzhq/recap-2020-a-look-at-lightning-and-boltz-5a57e0906c2d?source=rss----30d0837e45db---4</link>
            <guid isPermaLink="false">https://medium.com/p/5a57e0906c2d</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[atomic-swap]]></category>
            <dc:creator><![CDATA[Ankur]]></dc:creator>
            <pubDate>Mon, 04 Jan 2021 16:29:41 GMT</pubDate>
            <atom:updated>2021-01-04T16:29:41.749Z</atom:updated>
            <content:encoded><![CDATA[<h3>Recap 2020 — A look at lightning and Boltz</h3><p><strong>TLDR;</strong> A lot happened this year — this post aims to distill down the progress.</p><p>2020 has been a rather taxing year in every sense of the word, and we are all looking forward to a better 2021. But when it comes to the lightning ecosystem, the pace of progress didn’t halt. Lightning is considerably more robust and secure now than before. Fulgur ventures published a detailed <a href="https://medium.com/@fulgur.ventures/building-an-overview-of-the-lightning-network-ecosystem-a93be2343f61">overview</a> on the state of lightning ecosystem — Infrastructure projects like Boltz along with #LiFi are the largest categories. It further consolidates our hope that slowly but surely, we are moving in the right direction. Ryan Gentry from Lightning labs tweeted a great year-in-review thread on lightning’s 2020 progress:</p><h3></h3><p>Here&#39;s my 8 tweet year-in-review thread on the #LightningNetwork&#39;s 2020. 1) Public network capacity grew from 854 BTC ($6.2M) on Jan 1 to 1,071 BTC ($24.8M) today. That&#39;s a 25% increase in BTC terms, and a 300% increase in USD terms. 🐂🐂🐂(better volume metrics soon ™️) pic.twitter.com/fKqvu81HXe</p><p>Without further ado, let us dive right into how the year has been for Boltz and what we hope to achieve in 2021. For the uninitiated, Boltz product offerings has two facets — First, we are a privacy first, account-free crypto exchange. And second, we are a LSP (Lightning service provider). Various apps like Breez, Thunderhub, and Electrum have integrated Boltz lightning services in their apps — which enabled a frictionless user experience for their end users. With the release of landmark features like <a href="https://medium.com/boltzhq/a-landmark-boltz-release-creating-lightning-channels-on-the-fly-%EF%B8%8F-94896854b681?source=friends_link&amp;sk=4312bc3e5f97d64a089c0daf29a5a5c3">on-the-fly channel creation swaps</a>, we focused on LSP offering in the first half of 2020. The second half of of the year we worked hard on bringing more assets to the exchange side of Boltz offering. We added <a href="https://medium.com/boltzhq/tether-efill-your-lightning-channels-31e40e46164d?source=friends_link&amp;sk=cd5e33dc2933a065201af4c7c51511ea">Tether(USDT) </a>— which enabled our users to atomically swap USDT and lightning Bitcoin. While we grew together with the lightning ecosystem and learned a lot in the process, we have few more goodies to unwrap from our roadmap in coming months that we are excited to share with you guys:</p><ul><li><strong>Ether Integration</strong>: We have now added support for Ether in the current Boltz release. You can hop on to <a href="https://boltz.exchange/">https://boltz.exchange</a> and swap your lightning Bitcoins with Ether and vice versa. The integration of second largest crypto by market capitalization will increase <em>optionality</em> for our users and as an exchange service, that’s one of our main value proposition.</li><li><strong>RTL Integration:</strong> This has been long in works and after months of efforts sorting out every single little detail — we are psyched to announce that next RTL release will feature an optional opt-in Boltz support. We’d like to thank Suheb and Shahana from the RTL team for escalating this RTL release. It further manifests what is possible when teams with shared values collaborate together.</li><li><strong>No Ether required to claim:</strong> For account-based chain like Ethereum, the luxury of being able to store the state on-chain means that we can build tools with better user experience. Our current architecture requires that user should already have some ether in their Metamask wallet to pay for miner fee when receiving Ether or USDT from a Boltz swap. During the swap process, Boltz client does a sanity check for if the wallet has enough Ether or not. We have been brainstorming better ways to tackle this, including small custodial invoice (worth $1 for instance) that the user can pay to cover the fee before the swap process resumes. This protocol will make swapping on Boltz an even more seamless experience.</li><li><strong>WalletConnect</strong>: Adding more Web3 providers is also something we are looking forward to in coming months. This would make swapping ETH and USDT on mobile phones easier.</li><li><strong>Support for c-lightning: </strong>Boltz is a lightning node implementation agnostic project and we plan to add support for c-lightning and Eclair down the line in our<a href="https://github.com/BoltzExchange/boltz-lnd"> boltz-lnd cli tool</a>. We hear our users are most excited for this so rest assured, we are sure to push this up on our priority list.</li><li><strong>Chain to Chain swaps:</strong> For Boltz to become a fully fledged digital asset exchange platform, it’s important that we do offer cross chain layer one swaps. Once shipped, Boltz would be a full blown viable alternative to current custodial exchanges like Shapeshift.</li></ul><p>Did we miss anything? Would you like to suggest a feature that you’d like us to work on? Feel free to hop on our <a href="https://discord.gg/kceBPe3DpM">Discord</a>. We are all ears.</p><p>We wish everyone a happy new year! Stay safe and happy swapping!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a57e0906c2d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boltzhq/recap-2020-a-look-at-lightning-and-boltz-5a57e0906c2d">Recap 2020 — A look at lightning and Boltz</a> was originally published in <a href="https://medium.com/boltzhq">boltzhq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tether-efill your lightning channels]]></title>
            <link>https://medium.com/boltzhq/tether-efill-your-lightning-channels-31e40e46164d?source=rss----30d0837e45db---4</link>
            <guid isPermaLink="false">https://medium.com/p/31e40e46164d</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[lightning-network]]></category>
            <category><![CDATA[tether]]></category>
            <category><![CDATA[dex]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Ankur]]></dc:creator>
            <pubDate>Mon, 30 Nov 2020 13:21:05 GMT</pubDate>
            <atom:updated>2020-11-30T13:21:05.328Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>TLDR;</strong> Boltz adds support for Tether, enabling users to atomically swap USDT for lightning Bitcoin and vice versa.</p><h3>Rewind</h3><p>Boltz started as a simple <a href="https://medium.com/boltzhq/submarine-swaps-c509ce0fb1db">submarine swap</a> service that allowed users to refill and withdraw from their Bitcoin lightning channels across layers in a self custodial manner. This naturally attracted lots of early lightning adopters to use our service. We slowly added API support, which enabled apps like Breez to integrate Boltz reverse swap service, and also launched <a href="https://medium.com/boltzhq/a-landmark-boltz-release-creating-lightning-channels-on-the-fly-%EF%B8%8F-94896854b681">Channel Creation swaps</a>, which made it easy for new users of lightning to get a fully balanced ready-to-transact lightning channel with inbound liquidity. Over time Boltz had evolved into a full fledged lightning service provider (LSP for short). While we will continue to work on other LSP features and integrations with various lightning apps that are currently in the pipeline, we felt it was time to give the “exchange” side of the Boltz offering some attention. We are starting this today by adding Tether (USDT).</p><h3>The Tether conundrum</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*aCuSl8ja9wPolb6Fy_Gfvw.png" /><figcaption>The Tether Money Printing Machine</figcaption></figure><p>Tether has been a controversial topic of debate in the Bitcoin community. Many are apprehensive of it, and rightly so. After all, how could an inherently pro privacy and economically libertarian community endorse Tether? The entity behind the Tether cryptocurrency is accused of <a href="https://news.bitcoin.com/tether-freezes-millions-of-dollars-usdt-40-addresses/">freezing assets</a> and <a href="https://www.newsbtc.com/news/tether-continues-issue-new-usdt-alarming-rate/">issuing tokens</a> on a whim, which according to many is an antithesis of what the community stands for. But for the better or worse, Tether has proven to be quite successful and resilient to regulations. In this ongoing crypto bull run, <a href="https://twitter.com/glassnodealerts/status/1316472739117633538">Tether’s commutative transaction volume went above $600B</a>. With first mover advantage, Tether has benefited from building a network effect around its stablecoin before anyone else even got started. The rationale behind us deciding to add it is that Boltz is an exchange service and it cannot function as one without offering popular asset pairs. The popularity and adoption of the BTC/USDT pair has been able to garner in the past few years is evident by the success of companies like Binance. As a <strong>privacy first </strong>and<strong> lightning first </strong>project, we enabled the LN-BTC/USDT pair only with one particular use case in mind: providing our users an option to refill their lightning channels with USDT.</p><h3>Technology</h3><p>Since inception, we at Boltz have worked towards building a cross chain and cross layer atomic swap solution using native assets. It is not only practical but also adheres with the core principals of privacy and self-custodianship. Tether offering adds another feather to the cap. BTC-LN to USDT and USDT to BTC-LN swaps on Boltz uses the same HTLC powered concept prevalent in other cross layer swaps already offered by Boltz. HTLCs, or hashed timelocked contracts, are integral to the architecture of the lightning network, and are standardized on the Bitcoin blockchain. This doesn’t hold true for account-based blockchains like the Ethereum network — which means to add support for ERC20 tokens like Tether, you guessed it — we needed to <em>write a smart contract</em>.</p><p>Building a smart contract for Boltz swaps required us to focus on two main aspects: security and transaction costs. Security of the user’s funds is of utmost importance to us. We were obsessed about making sure that the smart contract is written with industry grade best practices. We also undertook rounds of in-house penetration testing. These steps were important for making sure that the smart contract is production ready before deployment. With all these frequent DeFi hack news, we are proud to say that we <a href="https://twitter.com/andrecronjetech?lang=en">don’t test in prod</a>.</p><p>The second important aspect of our focus was the transaction cost. With heavily fluctuating gas prices on the Ethereum network, it’s important for us to optimize our smart contract for gas use, so that our users can save on transaction fee. There’s a simple rule when it comes to gas costs on the account based blockchains: computation is cheap, storage is expensive. We were able to considerably bring down the transaction fees by storing as little data in the global state of the Ethereum network as possible.</p><p>The novelty of the Ethereum smart contract allowed us to eradicate the need for users to download the refund files for USDT to LN-BTC swaps — which is a necessity for swaps UTXO based chains. All the data needed to refund the locked coins from the contract can be queried via an Ethereum node. This resulted in a smart contract that not only offers great user experience on Boltz but is also secure, cheap, and easily auditable with rudimentary understanding of the Solidity language.</p><p>In the spirit of open source and complete transparency, <a href="https://etherscan.io/address/0x98f59b661de7afbb9c5cb01d262cec9caeca4ffe#code"><strong>here</strong></a> is the Boltz contract for the swap that is verified on Etherscan. The code is publicly available in the <a href="https://medium.com/r?url=https%3A%2F%2Fgithub.com%2FBoltzExchange%2Fboltz-core%2Ftree%2Fmaster%2Fcontracts"><strong>Boltz Github repo</strong></a>.</p><h3>Demo</h3><p>The following is the video demonstration of how users can use their USDT to refill their lightning channels using Boltz</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FSEv0RSHdPPQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DSEv0RSHdPPQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FSEv0RSHdPPQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6af64d9d932a73bbf02c6128df31ef5d/href">https://medium.com/media/6af64d9d932a73bbf02c6128df31ef5d/href</a></iframe><h3>Summary</h3><p>USDT integration was in the works for quite a while now and we couldn’t be more stoked to finally ship this. We hope that our users would be as excited as we are for this new asset that can be used to refill and rebalance lightning channels. Like always, hit us up on <a href="https://discord.gg/BrR7gab">Discord</a> if you have any feedback or just want to say Hi. Stay healthy and <a href="https://boltz.exchange/">Boltz on</a> ⚡</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31e40e46164d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boltzhq/tether-efill-your-lightning-channels-31e40e46164d">Tether-efill your lightning channels</a> was originally published in <a href="https://medium.com/boltzhq">boltzhq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unmixed CoinJoin change? Boltz to rescue.]]></title>
            <link>https://medium.com/boltzhq/unmixed-coinjoin-change-boltz-to-rescue-39e6efacfad0?source=rss----30d0837e45db---4</link>
            <guid isPermaLink="false">https://medium.com/p/39e6efacfad0</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[atomic-swap]]></category>
            <category><![CDATA[coinjoin]]></category>
            <dc:creator><![CDATA[Ankur]]></dc:creator>
            <pubDate>Wed, 04 Nov 2020 18:42:30 GMT</pubDate>
            <atom:updated>2020-11-04T18:42:30.684Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>TLDR;</strong> Users can use Boltz submarine swaps to funnel their unmixed CoinJoin change output into lightning, resulting in increased privacy.</p><p>Bitcoin is a decentralised monetary protocol. All on-chain Bitcoin transactions are public, traceable, and permanently stored in the blockchain. Anyone can see the balance and all transactions of any address. While this transparency is great for lots of stuff that makes Bitcoin valuable, like transaction verifiability, privacy isn’t one of them. Once a Bitcoin address is used, it becomes tainted with the history of all transactions it was ever involved with. All Bitcoin transactions are composed of at least one input (where the BTC come from) and at least one output (where the BTC are sent to). Additionally, Bitcoin transactions are constructed in such a way that it includes the information about previous transactions. For example, if you received 1 BTC in an address, and intend to send 0.4 BTC to your friend, you’d need to construct a Bitcoin transaction of 1 BTC, where 0.4 BTC will be sent as payment and remaining 0.6 BTC will be returned to you as a <strong>change</strong>. This means that every single Bitcoin transaction leaves a trail that can be exploited to trace the movement of Bitcoin across the blockchain. The unspent transaction output (UTXO), as the name suggests, is the result of a transaction that a user receives and can spend in the future. Learn more about UTXOs <a href="https://komodoplatform.com/whats-utxo/">here</a>.</p><h4><strong>Cometh CoinJoin..</strong></h4><p>CoinJoin, which was first <a href="https://bitcointalk.org/?topic=279249">proposed by Gregory Maxwell</a> in 2013, attempts to improve the privacy of Bitcoin transactions. Using CoinJoin, multiple users combine their UTXO into one large transaction with multiple inputs and multiple outputs. Each CoinJoin mixed outputs are of a fixed same amount. This breaks the traceability of the transactions and makes them indistinguishable on the blockchain, so that Uncle Sam can’t spy on you. The three main ready-to-use software CoinJoin implementations are <a href="https://wasabiwallet.io/">Wasabi Wallet</a> , <a href="https://github.com/Joinmarket-Org/joinmarket-clientserver">JoinMarket</a>, and <a href="https://samouraiwallet.com/whirlpool">Samurai Whirlpool</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/481/1*q0d1oHiTlscrnT4QmxT2NQ.png" /><figcaption>Credits: @peartobear</figcaption></figure><h4>Problem: Unmixed CoinJoin Change</h4><p>While CoinJoin helps to increase the anonymity of a Bitcoin transaction, it comes with a caveat — change outputs, that are <strong><em>not</em></strong> of a fixed same amount, remain unmixed and can potentially break the anonymity. As explained in previous section, change output is the fundamental part of how Bitcoin transactions work. However, when you send the coins which are the change from a previous transaction, receivers and blockchain observers can easily deduce that you were involved in the previous transaction that generated the change. Identifying change based of such heuristics is one of the many methods surveillance companies like <a href="http://www.chainalysis.com/">Chainalysis</a> use to spy on users. A common pitfall is sending unmixed coins and mixed ones to the same address, which can effectively result in user’s identity getting leaked. There are <a href="https://docs.wasabiwallet.io/using-wasabi/ChangeCoins.html#your-options-to-use-change-privately">few different ways</a> to deal with unmixed Bitcoin change, we will focus on how Boltz can be used as a tool to counter this risk.</p><h4>Solution: Swap unmixed change using Boltz</h4><h3></h3><p>Just tried @Boltzhq on testnet.Sending a whole @wasabiwallet #CoinJoin change coin to the swap provider, and instantly receiving sats in my #LightningNetwork channel.Find out where my sats went :)https://t.co/mjXtQvM65M</p><p>Boltz submarine swap service offering can help users mitigate the risk caused by the unmixed CoinJoin change. By atomically swapping the CoinJoin change for refilling lightning channels using Boltz, the user can eliminate the risk of clean coins getting tainted by accident. The Lightning network has relatively potent <a href="https://arxiv.org/abs/2003.12470">privacy properties</a>. And it is not yet being tracked to the extent that on-chain coins are, this makes Boltz swaps an easy and effective way to deal with CoinJoin changes. Since the user is creating the lightning invoice that Boltz will pay in this swap process, Boltz will know the user’s node public key and the lightning channel Boltz sent the funds to. Hence, this is not a <em>perfect </em>solution since Boltz could cluster your change output and your lightning node. We do however hope that <a href="https://lists.linuxfoundation.org/pipermail/lightning-dev/2018-November/001498.html">rendezvous routing</a>, when integrated to the lightning spec, will make this an even more effective solution.</p><h4>Demo</h4><p>Below is the demonstration of swapping unmixed CoinJoin change from Wasabi (marked with a red shield) to lightning Bitcoin through Boltz.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F1UkaJY1gERM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D1UkaJY1gERM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F1UkaJY1gERM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/dde80768a7f9ec015305b314380f6afb/href">https://medium.com/media/dde80768a7f9ec015305b314380f6afb/href</a></iframe><h4>Related Readings:</h4><ul><li><a href="https://en.bitcoin.it/wiki/CoinJoin#:~:text=CoinJoin%20is%20a%20trustless%20method,paid%20which%20recipient%20or%20recipients.">Bitcoin Wiki — CoinJoin</a></li><li><a href="https://docs.wasabiwallet.io/using-wasabi/CoinJoin.html">Wasabi docs — CoinJoin</a></li><li><a href="https://www.coinjoinsudoku.com/advisory/">CoinJoin Sudoku</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39e6efacfad0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boltzhq/unmixed-coinjoin-change-boltz-to-rescue-39e6efacfad0">Unmixed CoinJoin change? Boltz to rescue.</a> was originally published in <a href="https://medium.com/boltzhq">boltzhq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recap: Past few months @ Boltz]]></title>
            <link>https://medium.com/boltzhq/recap-past-few-months-boltz-5f25f2bd21c?source=rss----30d0837e45db---4</link>
            <guid isPermaLink="false">https://medium.com/p/5f25f2bd21c</guid>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[lightning-network]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[atomic-swap]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[Ankur]]></dc:creator>
            <pubDate>Wed, 15 Jul 2020 12:10:42 GMT</pubDate>
            <atom:updated>2020-07-15T10:02:49.835Z</atom:updated>
            <content:encoded><![CDATA[<h3>⏪ Recap: Past six months @ Boltz</h3><p><strong>TL;DR:</strong> We’ve been heads down shipping at Boltz. This post is a pause-and-reflect on how far we’ve come and what we need to do to build upon the momentum we have gained in the past six months.</p><p>A lot has happened in these past months. Amidst the world going through a pandemic, FED <a href="https://brrr.money/">brrrinting money</a> like it’s nobody’s business, stocks making the crypto market look like a day at grandma’s house, and Kanye running for president, 2020 continues to bemuse us. The Bitcoin lightning community, however, knows that <a href="https://a16z.com/2020/04/18/its-time-to-build/">it’s time to build</a>, and has made silent, but significant progress. There are more than 13k public LN nodes now with about 1k BTC in channel capacity. These numbers inspire confidence for the future of the Lightning network and motivate many like us to continue building towards the common goal to create the money and payment system of the future.</p><blockquote>Make measurable progress in reasonable time</blockquote><p>Measuring progress is an important part of a startup’s journey. If we can quantify and analyze our progress, we can precisely gauge our efficiency and holistically judge how far off we are from achieving our goals. To do so in a transparent manner, we’ve listed six major achievements we have unlocked in the past six months.</p><h3>1. <a href="http://boltz.exchange/">Boltz.exchange</a> got a facelift 🎉</h3><h3></h3><p></p><p>We shipped a new and revamped frontend for Boltz with a much-improved user interface across desktop and mobile platforms. This was one of our main focuses in the past few months. One of the support issues we had to repeatedly deal with was users not being able to immediately refund in case of a swap failure. The lightning network is still in its nascent stage and routing errors are a common cause of failed swaps. In such cases of failed normal submarine swaps (on-chain to LN), the user could use the refund file downloaded during the swap to claim back the on-chain coins that they sent. Due to the nature of hashed time-locked contracts, the refund could only be triggered after a certain number of blocks were mined, which resulted in confused users trying to refund a swap immediately after the failure, but to no avail. We fixed this in our revamped website, where the users are now acutely made aware of the number of blocks and approximate time they need to wait before they can initiate a refund. The frontend also saves the refund files of the latest swaps in localstorage of the browser. We ironed out many prevalent issues like these and other points of friction in the user journey — which significantly improves our net NPS score. The revamped Boltz website is a progressive web app, which makes using Boltz on mobile a native app-like experience. We will continue to iterate on the feedback we have received to build on our promise of providing the best user experience while retaining the non-custodial and private nature of Boltz swaps.</p><h3>2. RTL integration of Boltz — PR ready 🥳</h3><p><a href="https://github.com/Ride-The-Lightning/RTL/pull/361">WIP: Add Boltz as additional swap provider by dejankocev · Pull Request #361 · Ride-The-Lightning/RTL</a></p><p>As a Lightning Service Provider, one of our goals is to partner with projects in the space and provide value to their end-users. Ride the Lightning (RTL) is a full-function, device-agnostic, web user interface to help manage lightning node operations. People running LND, c-lightning, or eclair node implementation of the lightning network can access their node via a web interface to actively manage it. We realized that Boltz can add a lot of value to these lightning power users who want an easy way to on and off-ramp themselves from the lightning economy in a self-custodial and trust minimized manner. Our integration with RTL adds the Boltz channel deposit and withdrawal feature and as an additional choice to the lightning loop integration. Channel creation swaps, our novel, and self-custodial way to obtain a balanced lightning channel with a simple on-chain transaction is coming to RTL soon as well. See #6.</p><h3>3. Electrum integrates Boltz ✌</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y1YgoMCGgE7v9EkMOoNekg.png" /></figure><p>Electrum, one of the oldest Bitcoin wallets, released a <a href="https://github.com/spesmilo/electrum/releases/tag/4.0.2">new version</a> of the wallet, which supports Boltz submarine swaps out of the box. This is a huge win for privacy in Bitcoin. We worked closely with the Electrum team to get this shipped by adding needed features and improving documentation on the way. <a href="http://docs.boltz.exchange/">Our API</a> is now more robust than ever before and ready for devs to hack around with.</p><h3>4. We were featured on Fulmo’s PotzBlitz podcast 👁️</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FkAOl123EXBg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DkAOl123EXBg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FkAOl123EXBg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9da5795fcee6ee03a069f6850dd27402/href">https://medium.com/media/9da5795fcee6ee03a069f6850dd27402/href</a></iframe><p>Fulmo’s PotzBlitz is a weekly lightning talk podcast while the world is in lockdown. Its purpose is to create a sense of community, update the viewers on the latest developments in the lightning world, and give creators a platform to showcase their project. We were honored to be invited to talk about running a privacy first, account-free crypto exchange. We talked about everything from our vision to technology and went deep into the architecture of submarine swaps. We would like to thank Jeff from Fulmo and Dennis from Bitwala for hosting us. <a href="https://github.com/BoltzExchange/slides/blob/master/boltz-fulmo-pptfinal.pdf">Here</a> are the slides from this talk.</p><h3>5. Decentralized liquidity aggregator Exchange Union’s daemon integrates Boltz — making it default choice to power lightning deposits 😎</h3><p><a href="https://github.com/ExchangeUnion/xud-docker/commit/c81ecf46130163cc29bb0b60e439acd74d17b761">feat: add Boltz daemon (#532) · ExchangeUnion/xud-docker@c81ecf4</a></p><p><a href="https://www.exchangeunion.com/">Exchange Union</a>, is an open-source project building <a href="https://github.com/ExchangeUnion/xud">xud</a> — the reference implementation powering <a href="https://opendex.network/">OpenDEX</a>, which is a decentralized exchange built on top of the <a href="https://lightning.network/">Lightning</a> and <a href="https://connext.network/">Connext</a> network. <a href="https://github.com/ExchangeUnion/xud">xud</a> brings individual traders, market makers, and exchanges onto OpenDEX to form a single global trading network and liquidity pool, in a bid to counter fragmented liquidity problem persistent across modern-day exchanges.</p><p>Using Boltz, market makers running the <a href="https://github.com/ExchangeUnion/xud-docker">XUD docker</a> environment can directly get balanced channels and deposit or withdraw from their lightning channels using a simple command or upcoming WebUI interface.</p><h3>6. An epic feat: Channel Creation Swaps 🎊</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F3u28Cnub_r4%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D3u28Cnub_r4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F3u28Cnub_r4%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7caa8875424320cd0da2a0635e25af38/href">https://medium.com/media/7caa8875424320cd0da2a0635e25af38/href</a></iframe><p>Our latest Boltz <a href="https://github.com/BoltzExchange/boltz-backend/releases/tag/v2.3.0">Ragnarok release</a> bundles a landmark feature: Channel Creation swaps. We published a detailed <a href="https://medium.com/@lightningboltzmann/a-landmark-boltz-release-creating-lightning-channels-on-the-fly-%EF%B8%8F-94896854b681">post</a> on it. The fact that the user can now get a balanced lightning channel from the get-go while retaining the self custodial and private nature of the Boltz swaps is quite revolutionary in itself. Channel creation swaps are a <em>type</em> of normal submarine swap — which means that lapp developers can build a seamless user experience on top of the same API endpoint primitive. Some wallets and projects are in the final stages of integrating it, which makes this feat a highlight of our past few months at Boltz.</p><h3>What’s next</h3><p>As the world recovers from the pandemic and the economy bounce back, we are hopeful that the lightning projects will gain even more momentum. This building streak of the past few months has given us lots of headways and we plan to capitalize on it by carrying on with the shipping mode. Our next major release will feature the integration of a BTC/USDT pair. This will increase our targeted userbase as an exchange. A stablecoin integration means Boltz traders will be able to use Boltz to shield themselves from the volatility of the market. If you have any questions, feel free to hit us up on <a href="https://twitter.com/Boltzhq">Twitter</a> or <a href="https://discord.gg/Uu3vXWa">Discord</a>.</p><p>Until next time, happy swapping!</p><p>Team Boltz</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f25f2bd21c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boltzhq/recap-past-few-months-boltz-5f25f2bd21c">Recap: Past few months @ Boltz</a> was originally published in <a href="https://medium.com/boltzhq">boltzhq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Landmark Boltz release: Creating lightning channels on the fly! ✈️]]></title>
            <link>https://medium.com/boltzhq/a-landmark-boltz-release-creating-lightning-channels-on-the-fly-%EF%B8%8F-94896854b681?source=rss----30d0837e45db---4</link>
            <guid isPermaLink="false">https://medium.com/p/94896854b681</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[atomic-swap]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[lightning-network]]></category>
            <dc:creator><![CDATA[Ankur]]></dc:creator>
            <pubDate>Tue, 07 Jul 2020 16:49:05 GMT</pubDate>
            <atom:updated>2020-07-07T10:17:14.478Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>TL;DR: </strong>Boltz now provides a self-custodial way to get a balanced lightning channel without manual actions required from the end-user.</p><h3>Primer</h3><p>Bitcoin’s lightning network has been under constant limelight since it was conceptualized by Poon et al. in a <a href="https://lightning.network/lightning-network-paper.pdf">2015 paper</a>. It’s touted as a solution to the scaling problem of the Bitcoin network. By acting as a second layer, the lightning network enables faster settlements of transactions without compromising with the censorship-resistant properties of the underlying blockchain. But it comes with a fair share of tradeoffs. <a href="https://www.youtube.com/watch?v=RiVxj0cfrBU">Lightning skeptics</a> have long argued that the Lightning Network is essentially hard to use and the way it is architectured results in a user experience that doesn’t pave a friendly road for users who want to take part in the lightning economy.</p><p>By building products and tools that help improve its usability for lightning users, we at Boltz as a Lightning service provider (LSP) have contributed towards fixing these aforementioned issues. Our new flagship offering: <strong><em>Channel Creation Swaps</em></strong>, is another step towards that goal.</p><h3>Introduction</h3><p>As the name implies, Boltz Channel Creation Swap is another tool in the ever-growing Boltz arsenal that allows the users to get a balanced lightning channel in the easiest and most frictionless way possible. This is an important landmark for Boltz and the lightning ecosystem at large because it makes it easy for users to get up and running with lightning in a matter of minutes. There are few other providers that offer such a channel creation swap server, namely: <a href="https://www.bitrefill.com/buy/lightning-channel/?hl=en">Bitrefill’s Thor</a> and Eclair’s <a href="https://github.com/ACINQ/phoenix">Pheonix wallet</a>, but Boltz offering distinguishes itself by keeping the self custodial and atomic nature of the channel creation service intact. This is revolutionary because there’s always a fine line between trading off the trustless nature or letting users deal with the UX friction. Boltz Channel Creation Swap finds a great balance between the two — which makes this offering an attractive proposition for developers trying to onboard users to their lightning wallets and apps, without worrying about which service to trust as these swaps retain the atomicity principle, i.e, swaps either complete in full or the user funds get refunded.</p><h3>User Story</h3><p>A normal user flow of setting up a self-custodial lightning wallet comes riddled with friction. After downloading the wallet and funding it with on-chain coins, the user has to open a channel and find a way to get inbound liquidity to the nodes he intends to transact with. This increases the user churn as it is the antithesis of promised fast payments via the lightning network.</p><p>By using a wallet or app that integrates Boltz Channel Creation service, end-users can now send the on-chain funds to Boltz, and in return, Boltz opens a fully balanced ready-to-transact lightning channel to the user’s node with inbound liquidity. This adheres to the ubiquitous and intuitive deposit flow in Bitcoin wallets that users are already familiar with — making this whole experience of going from installing the wallet to doing the first transaction as seamless as possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/707/1*KbTRvkvvhLMBQ9k2xNW1ew.png" /><figcaption>High-level flowchart</figcaption></figure><p>At the architectural level, Boltz Channel Creation Swaps are a kind of normal <a href="https://medium.com/boltzhq/submarine-swaps-c509ce0fb1db">submarine swap</a> (on-chain to off-chain) but with an additional feature — If there exists no route between the user and Boltz node, Boltz will open a channel on the fly and deposit the amount that the user sent on-chain minus the fee, to the newly created channel. This means that for a Channel Creation Swap to get triggered: There shouldn’t be an existing route between the user and Boltz with a cumulative inbound capacity greater than or equal to the intended on-chain deposit amount. The perk of channel creation swap being a <em>type</em> of normal submarine atomic swap is that the user doesn’t need to trust Boltz or any other lightning service provider offering this service — making it a truly transformative UX improvement for people using the lightning network.</p><h3>Demo</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FemWAVKurV3k%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DemWAVKurV3k&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FemWAVKurV3k%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/218ff239656cc07895fe43956519d436/href">https://medium.com/media/218ff239656cc07895fe43956519d436/href</a></iframe><p>This is a step-by-step demo of the channel creation swap.</p><h3>Summary</h3><p>Boltz channel creation swap is an important milestone for Boltz and the lightning ecosystem. It’s planned integration with popular node management tools and wallets would further bring down the UX barrier. We plan to continue working on building tools that will enable more users to partake in the lightning economy and empower them to join the movement of reclaiming our financial sovereignty.</p><p>Until next time, Boltz on!</p><p>Team Boltz.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94896854b681" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boltzhq/a-landmark-boltz-release-creating-lightning-channels-on-the-fly-%EF%B8%8F-94896854b681">A Landmark Boltz release: Creating lightning channels on the fly! ✈️</a> was originally published in <a href="https://medium.com/boltzhq">boltzhq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Brewing @ Boltz: Hold Reverse Swaps]]></title>
            <link>https://medium.com/boltzhq/brewing-boltz-hold-reverse-swaps-fea0fadbf041?source=rss----30d0837e45db---4</link>
            <guid isPermaLink="false">https://medium.com/p/fea0fadbf041</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[lightning]]></category>
            <category><![CDATA[atomic-swap]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[Ankur]]></dc:creator>
            <pubDate>Mon, 13 Jan 2020 16:09:52 GMT</pubDate>
            <atom:updated>2020-01-13T16:09:52.449Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>TL;DR:</strong> This post attempts to distill the idea of hold reverse submarine swaps, what we are working on behind the scene, and what the future holds for us.</p><h4><strong>Cutting the Jargon</strong></h4><p>An altruist reader of our blog rightly pointed out that lightning to on-chain swaps on Boltz has one major flaw, which we were aware of and actively working to counter.</p><p><a href="https://medium.com/@leondo/what-prevents-a-user-from-locking-up-all-of-the-boltz-funds-by-opening-a-lot-of-reverse-swaps-2fe8cc395b08">What prevents a user from locking up all of the boltz funds by opening a lot of reverse swaps…</a></p><p>To summarize the issue in layman’s terms — Boltz was locking funds (the coins the user intended to buy) before the user paid the invoice (the coins the user intended to sell). It opened up Boltz to a spam vector, wherein, any motivated malicious third party could repeatedly start a swap and bail out before paying the invoice. This would result in Boltz locking up on-chain funds over and over again while losing a few satoshis on on-chain fee every single time. Moreover, Boltz also pays the opportunity cost of locked-up funds for the duration of the swap timeout.</p><h4><strong>When it rains, it pours</strong></h4><p>As if these vulnerabilities weren’t enough of the trouble already, the reverse swap flow also had an inherent design flaw: the sweeping, or the claiming of funds by the user client had to work<em>,</em> or the user could lose funds.</p><p>We encountered many instances where we had to manually refund back the coins to the user because their browser failed to claim the fund. It could be caused by an unstable internet connection, browser crash, or any of the million things gone wrong on the client-side. For a non-custodial crypto exchange like Boltz, safeguarding the user fund is the bread and butter, so solving this issue was extremely important. We brainstormed many methods to counter this, including now-defunct <a href="https://github.com/BoltzExchange/boltz-backend/issues/170">Protocol 11</a>, but we wanted a solution that didn’t break the atomicity of the swap, so we kept looking.</p><h4><strong>Till it finally dawned on us</strong></h4><p>A different kind of lightning invoice — hold invoice, have the potential to solve our problem. Folks at lightning labs were quick to detail the new swap architecture enabled by hold invoices in a <a href="https://blog.lightning.engineering/technical/posts/2019/04/15/loop-out-in-depth.html">blogpost</a>.</p><p>Hold invoice is simply a lightning invoice with an added quirk: instead of locking and settling the HTLC (<a href="https://en.bitcoin.it/wiki/Hash_Time_Locked_Contracts">hashed time-locked contracts)</a> immediately when the payment arrives, the HTLC is <strong>only locked, not settled. </strong>This enables an interesting flow on the receiver’s end — they can choose whether to settle or cancel the HTLC. From the sender’s perspective, a hold invoice looks identical to a regular lightning invoice, which makes it compatible with all existing lightning wallets. There have been many interesting use cases of hold invoice now in production — that extended the lightning implementation to accommodate new flows, which in turn improved the user experience by orders of magnitude. For example, our friends at Breez used hold invoices to build <a href="https://medium.com/breez-technology/introducing-lightning-rod-2e0a40d3e44a">Lightning Rod</a>, which enables asynchronous lightning payments.</p><h4>Let Bob send the preimage first</h4><p>Cutting to the chase, our new reverse submarine swap architecture made use of hold invoices in such a manner that the user now creates the preimage and locks up the lightning funds <em>before</em> Boltz, which means there is now a non-negligible cost of locked funds when deciding to bail out from a swap. This significantly reduces the spam attack vector, since it’s simply not for free anymore to bail out from a swap. The following picture depicts our new swap flow and gives a high-level idea of the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/905/1*oIC3S2zLgo707rA5y5nGaQ.png" /></figure><p><strong>Step 1:</strong> Bob creates a hash of the locally generated preimage and sends it with the “start swap” HTTP request to the Boltz server.</p><p><strong>Step 2:</strong> Boltz makes use of the said hash to create a hold invoice. Boltz then sends the invoice to Bob.</p><p><strong>Step 3: </strong>Bob receives the invoice and pays it with her lightning wallet. What really happens is, that the signed HTLC from Bob’s wallet is sent to Boltz, but the payment is held by Boltz and not executed at this point because it is still missing Bob’s preimage to do so.</p><p><strong>Step 4: </strong>Boltz then locks up the on-chain coins using a swap script that requires Bob to reveal the preimage when claiming.</p><p><strong>Step 5: </strong>Bob claims the locked on-chain funds that subsequently reveals the preimage.</p><p><strong>Step 6:</strong> Boltz then uses that preimage to unlock the lightning payment.</p><p>This new reverse submarine swap dramatically reduces the spam attack vector and also eradicates the problem of the user losing funds when claiming fails client-side. It substantially improves the user experience of Boltz. If you are a developer, you can look at our documentation for the <a href="https://docs.boltz.exchange/en/hold-reverse-swaps/lifecycle/">new swap flow lifecycle</a>. You can also hack around with our <a href="https://docs.boltz.exchange/en/hold-reverse-swaps/api/#creating-reverse-swaps">new endpoint for creating reverse swaps</a>. Shoutout to our friends at Breez for helping us to test and improve our new endpoint!</p><h4>What’s brewing next</h4><p>A lot is happening at Boltz, and we cannot wait to reveal what’s next. We have some exciting announcements to make, which will be huge for the community as a whole and us. Non-custodial and private trading of digital assets remains our core ethos, and we will continue to work towards making it a reality.</p><p>Till next time, Adios and happy swapping!</p><p>Team Boltz.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fea0fadbf041" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boltzhq/brewing-boltz-hold-reverse-swaps-fea0fadbf041">Brewing @ Boltz: Hold Reverse Swaps</a> was originally published in <a href="https://medium.com/boltzhq">boltzhq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing: Boltz API release⛱]]></title>
            <link>https://medium.com/boltzhq/announcing-boltz-api-release-548b1452fcd5?source=rss----30d0837e45db---4</link>
            <guid isPermaLink="false">https://medium.com/p/548b1452fcd5</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[dex]]></category>
            <category><![CDATA[lightning]]></category>
            <category><![CDATA[exchange]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[Ankur]]></dc:creator>
            <pubDate>Tue, 03 Sep 2019 21:20:12 GMT</pubDate>
            <atom:updated>2019-09-03T21:16:27.638Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>TLDR;</strong> The well documented <a href="https://docs.boltz.exchange/en/latest/">Boltz API</a> will now enable developers to integrate non-custodial cryptocurrency swaps into their lightning apps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*uxvlEbQmrZGr4fdx_xRlPw.gif" /></figure><p>We believe that developers are very core to what makes a platform and the ecosystem as a whole succeed. So today, we couldn’t be more proud to announce the official release of the Boltz API with the associated documentation. Let’s go through some use cases to hack around with the Boltz API, shall we?</p><p><strong>⛓ </strong>⚡ <strong>Trust-minimized on-chain on-ramp</strong></p><p>Integrating Boltz with your lightning app enables you to on-board users who might not be using any lightning wallets yet. Boltz will provide a trust minimized way to use lightning apps with on-chain coins, which will curb the UX friction by enabling your lapp users to get outbound liquidity with an on-chain deposit.</p><p><strong>⚖ </strong>⚡<strong> ️Balancing or Rebalancing Lightning Channels</strong></p><p>Developers of different wallets can provide a native and trust-minimized way to balance or rebalance their user’s lightning channels with the Boltz API.</p><p><strong>💸 </strong>⚡ <strong>Withdrawing from Lightning Channels</strong></p><p>Wallet developers can also use the Boltz API to provide an option for the user to withdraw from their lightning channels.</p><p>💰 ⚡ ️<strong>Depositing into Lightning Channels</strong></p><p>In times of high fees, Boltz integration will allow you to empower your lapp users with the choice of using on-chain Litecoin to deposit into your ⚡-Bitcoin channels, as described by Charlie Lee. All this without trading off the non-custodial nature of your lightning app.</p><p>📥 ⚡ <strong>Bootstrapping initial inbound liquidity</strong></p><p>For people not having <em>enough</em> inbound liquidity or new users having no lightning channels, a trust-minimized channel opening service can be built on the top of Boltz, similar to <a href="https://www.bitrefill.com/thor-lightning-network-channels/?hl=en">Bitrefill’s Thor</a>. The service can account for the channel opening and service fee in the on-chain amount received from the user during the swap.</p><p><strong>🔁 ⚡️ Trading LTC/BTC</strong></p><p>By integrating Boltz, developers can also add the feature to swap different assets in their lightning apps, akin to Shapeshift but without all the baggage of KYC and different trust assumptions. This will, however, get even more interesting with new assets being added to Boltz.</p><p><strong>Check the documentation of the Boltz API 👉 </strong><a href="https://docs.boltz.exchange/en/latest/"><strong>here</strong></a><strong> 👈</strong></p><p>Our endpoints are stable and no breaking changes are planned. In an unlikely situation where we have to change the endpoints for any reason, we will be quick to give developers advanced notice so they have adequate time to make updates. Stay tuned to our <a href="https://twitter.com/boltzhq">Twitter feed</a> or chat with us on <a href="https://discordapp.com/channels/547454030801272832/557981576676245504">Discord</a>!</p><p>Stay #reckless and happy hacking!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=548b1452fcd5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boltzhq/announcing-boltz-api-release-548b1452fcd5">Announcing: Boltz API release⛱</a> was originally published in <a href="https://medium.com/boltzhq">boltzhq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bingo! Announcing 0-conf support for Boltz]]></title>
            <link>https://medium.com/boltzhq/bingo-announcing-0-conf-support-for-boltz-7fee1e7450b9?source=rss----30d0837e45db---4</link>
            <guid isPermaLink="false">https://medium.com/p/7fee1e7450b9</guid>
            <category><![CDATA[lightning]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[exchange]]></category>
            <category><![CDATA[dex]]></category>
            <dc:creator><![CDATA[Ankur]]></dc:creator>
            <pubDate>Tue, 27 Aug 2019 14:22:23 GMT</pubDate>
            <atom:updated>2019-08-27T14:22:23.382Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>TL;DR:</strong> This new feature will allow for instant swaps without having to wait for confirmations of on-chain transactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*HRNyMYe9KKx4PW5wlPs7tQ.gif" /><figcaption>Demo of a swap using 0-conf, completed in ~10 seconds</figcaption></figure><p>We are excited to announce a new feature update which will make the trading experience on Boltz as seamless and instant as ever. User experience is paramount to our cultural ethos at Boltz and when our users speak, we ardently listen; based on the feedback we decided to empower our users with an option to fast track the trade using 0 confirmation if certain preconditions are met, which are further described in this article.</p><h3>Introduction</h3><p>As the name implies, 0-confirmations are transactions that have been broadcasted but did not receive any confirmations yet i.e. the state where the transaction is yet to be included in a block. In the current architecture, an on-chain bitcoin to lightning-bitcoin swap flow follows these intuitive steps:</p><ol><li>The user enters the swap amount and initiates the trade. In the successive window, she pastes the lightning invoice of the ⚡bitcoin she is ought to receive.</li><li>User is prompted to download the <em>refund.json </em>file and is successively presented with a bitcoin on-chain address to send the funds to.</li><li>After <strong>one confirmation </strong>on the Bitcoin’s blockchain, which takes ~10 minutes, the user receives the equivalent ⚡bitcoin in her lightning wallet.</li></ol><p>It is rather apparent why, in many cases, the current flow might not make for ideal user experience. The user often wouldn’t have the patience to wait for 10 minutes to receive her funds and she could, in principle, choose to use any of the centralized alternatives for this very reason. We found that empowering the end-user with an option to receive the funds even before the transaction receives one-confirmation, by trading off a small amount of trust, results in orders of magnitude improvement of swap experience and therefore helps us avoid user churn.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/1*FwfuKzLClN7aCVmny17opg.png" /><figcaption>Satoshi on how merchants can lower the 0-conf risk, credit: bitcointalk.org</figcaption></figure><p>In the famous quote replying to now EOS CTO Daniel Larimer (not sure he got it) Satoshi provided a framework and reinforced that a payment processor can verify the payments “well enough” in 10 seconds or less. This also reinforces the notion that if handled properly, low-value 0-conf transactions are not only safe but encouraged.</p><h3>Caveats</h3><p>We will start by explaining a very important feature of the Bitcoin protocol — <a href="https://en.bitcoin.it/wiki/Replace_by_fee">Replace-by-Fee (RBF)</a></p><p>In laymen terms, it allows for the replacement of a transaction with a new version of the transaction, which is useful if the first transaction is stuck in the mempool because of low fees. The new version of the transaction can (and has to) pay more fees which will increase the probability of being included in a block. While this may be very useful for the free market that the Bitcoin protocol is hedging for, it comes with a serious drawback — a malicious actor can hypothetically double-spend the unconfirmed transaction using RBF. Because when a transaction is replaced with RBF it can not only change the amounts it is sending to the outputs but also change the outputs completely and redirect the unconfirmed transaction that way.</p><p>Consider a hypothetical scenario where Alice is a malicious actor who decides to scam Boltz. Alice initiates the swap of one ⚡bitcoin for one on-chain bitcoin. As explained in the Introduction section of this article, Alice sends the on-chain bitcoin to Boltz’s bitcoin address with a 0.0005 bitcoin as transaction fee. Boltz’s server notices the unconfirmed transaction and pays the user’s ⚡bitcoin invoice. Alice receives the ln payment and then goes forward and replaces the transaction from her wallet with her own address but with a higher fee of 0.001 bitcoin. Now since this replaced transaction has higher fees, miners are incentivized to include it in the block before the legitimate transaction. This results in Alice swapping 1 ⚡bitcoin from Boltz for merely 0.0015 bitcoin in transaction fees instead of the actual 1 bitcoin.</p><p><strong>How does Boltz hedges against this risk?</strong></p><p>To avoid the swindle as described in the aforementioned hypothetical case, Boltz employs a couple of precautionary measures: It checks for whether the transaction is signaling RBF (inherited or otherwise), in which case, the Boltz server would not pay the lightning invoice unless the legitimate transaction at least gets one confirmation. With the tradeoff for waiting longer (10 minutes in this case), Boltz could protect itself from malicious behavior from Alice. The second precautionary measure that would potentially discourage the use of this attack vector is a check by the Boltz server to concur if the fees are high enough for the transaction to be included in the next block. This eliminates the possibility where the attacker doesn’t even need to double-spend, but just send the transaction with very low fees that stay in mempool <em>forever </em>without getting mined.</p><p><strong>Are users at risk?</strong></p><p>As described before, when using Boltz for swapping on-chain coins for ⚡ lightning coins, the risk<em> </em>while very small, is on side of Boltz. If however, when the user decides to swap lightning coins for the on-chain coins, the minimal risk switches to the side of the user. Boltz also has a maximum threshold in place, which is currently <strong>1 million satoshis and 125 million litoshis (currently ~100 USD), </strong>it further mitigates the risk as users sending transactions above these amounts won’t have an option to use the 0-conf feature.</p><h3>Summary</h3><p>The 0-conf feature allows us to empower users with a choice, a choice to trade off a small risk with a roughly <strong>600x </strong>improvement in speed. Users who are not comfortable with this trade-off; stick with regular 1-confirmation on-chain transactions.</p><h4><strong>Further readings</strong></h4><ol><li><a href="https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki">BIP 125: Opt-in Full Replace-by-Fee Signaling</a></li><li><a href="https://bitcointalk.org/index.php?topic=1395427.0">Bitcointalk</a> discussion on RBF (Replace-by-Fee)</li><li>A <a href="https://coinatmradar.com/blog/support-zero-confirmation-transactions-at-bitcoin-atm/">breakdown</a> of the infamous bitcoin ATM hack that exploited 0-conf attack vector</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fee1e7450b9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boltzhq/bingo-announcing-0-conf-support-for-boltz-7fee1e7450b9">Bingo! Announcing 0-conf support for Boltz</a> was originally published in <a href="https://medium.com/boltzhq">boltzhq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Problem with Free Options]]></title>
            <link>https://medium.com/boltzhq/the-problem-with-free-options-69f9f59a2d48?source=rss----30d0837e45db---4</link>
            <guid isPermaLink="false">https://medium.com/p/69f9f59a2d48</guid>
            <category><![CDATA[lightning-network]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[dex]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[Ankur]]></dc:creator>
            <pubDate>Fri, 26 Jul 2019 21:10:33 GMT</pubDate>
            <atom:updated>2019-07-26T21:10:33.232Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>TL;DR: </strong>There might not be any such thing as a free lunch but in cryptoverse, there is something called <a href="https://lists.linuxfoundation.org/pipermail/lightning-dev/2018-December/001752.html">the free options problem</a> that pushed us to the state of quandary. This blog post details how we, at Boltz, fell prey to that. The brief timeline goes over what transpired at Boltz and how we recovered from it.</p><h3>Introduction</h3><p>Suppose that Alice agrees to sell 10 Litecoin for 1 ⚡Bitcoin to Bob, so the trade gets executed in the following steps:</p><p><em>Step 1)</em>Bob will create an invoice for 1 ⚡Bitcoin and sends it to Alice</p><p><em>Step 2)</em>Alice will generate a redeem script and address based on the hash of the preimage of the invoice</p><p><em>Step 3)</em>Bob will send the on-chain Litecoin to this address</p><p><em>Step 4)</em>Alice will pay the aforementioned invoice of Bob to get the preimage in order to be able to claim those 10 Litecoin</p><p>The aforementioned steps illustrate how a submarine swap between ⚡Bitcoin and Litecoin (buying ⚡Bitcoin by sending on-chain Litecoin) works. But there’s a catch, during that period of time, Bob can choose to delay sending his Litecoin to Alice’s address, for as long as Alice is annoyed enough to bail out of the agreement because the onchain HTLC times out. If the exchange rate changes in Litecoin’s favor, Bob would wait until the onchain timelock expires and keep his “more valuable Litecoin”. If however, the exchange rate tilts in Bitcoin’s favor, Bob would settle the payment and receive the Bitcoin at a discounted rate. Evidently, this gives an unfair advantage to Bob since Alice is left prone to Bob delaying his payment and take advantage of exercising his option to let the swap expire. Completely free of charge. This proves that the method of trade described above depends on the altruism of Bob and hence isn’t a foolproof system.</p><p>This problem is well studied in modern cryptography. Many research papers like <a href="https://eprint.iacr.org/2014/129.pdf">How to Use Bitcoin to Design Fair Protocols</a> have proposed workarounds. But a solution to the free options problem, which is a subset of the broader fair exchange problem, has been <a href="https://www.cs.utexas.edu/~shmat/courses/cs395t_fall04/pagnia.pdf">found</a> to be impossible to solve so far without the use of a trusted third party. In the context of lightning powered exchanges, Corné Plooy, a researcher who earlier created a related <a href="https://lists.linuxfoundation.org/pipermail/lightning-dev/2018-May/001292.html">thread</a> pertaining to this on Lightning-Dev mailing list, proposed a <a href="https://bitonic.nl/public/slowdown_prevention.pdf">solution</a> that lowers the amount of trust needed to be placed on the third party in this scenario. This proposed solution, according to Plooy’s own admission, is far from perfect but we think that this is a step in the right direction and departure from the <a href="https://lists.linuxfoundation.org/pipermail/lightning-dev/2018-December/001752.html">belief</a> that a multi-asset lightning network and in turn exchange of different assets via lightning may not be economically viable.</p><h3>How did this affect us at Boltz?</h3><p>Simply put, <em>WE GOT REKT</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*fOeAqjrGnK8pFc3OVlodxQ.gif" /></figure><p>We started to observe suspicious bot trading activity on Boltz (albeit quite late) on the BTC/LTC pair. The attacker was making use of the free option exploit and waiting for the rate to sway to his favor, at which point, the attacker would go forward with the trade to churn out a profit. The Litecoin price increase in the month of May complemented this strategy and made it a lucrative exploit. We deployed our SWAT team to research this and realized that regular submarine swaps (paying ⚡ invoice via on-chain tx) on Boltz did not have a timeout. This major bug made it very easy for the malicious actor to carry out this attack as s/he could quite literally delay the release of the preimage <em>forever. </em>We quickly deployed a fix that made Boltz abort the normal swap when the on-chain timeout expired.</p><p><em>But the draining continued…</em></p><p>The fix proved to be inconsequential to our cause as the funds keep getting drained out. It turned out that, the block timeout, which was ~10 blocks for the Bitcoin’s blockchain, gave enough room to the attacker to continue with the offensive. In the process, a bug was discovered, which opened another attack vector: we miscalculated our fees. We were finally able to control the damage by fixing these two bugs. We decided to invest time building better internal toolings i.e robust warning system and periodic statistics updates that can help us track and deter any potential exploit earlier than we did this time around. We decided to move away from CryptoCompare for rates, and built a new rate calculation mechanism that takes the rates from the APIs of five popular exchanges, namely, Binance, Bitfinex, Coinbase Pro, Kraken, and Poloniex and averages them out to get a more “fair” rate for our users.</p><p>We apologize for any inconvenience caused by the downtime Boltz experienced in the past weeks. The code is now more robust than ever before and we are excited about a new big feature launch soon. Please watch out this space for more on it.</p><h3>Further Readings on Free Option Mitigations</h3><ol><li>A <a href="https://bitonic.nl/public/slowdown_prevention.pdf">solution</a> on preventing transaction delays with a Lightning routing service, for preventing abuse in a Lightning-based peer-to-peer exchange.</li><li>Another <a href="https://bitonic.nl/public/latencymonitor.pdf">proposal</a> on a trusted latency monitor service</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69f9f59a2d48" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boltzhq/the-problem-with-free-options-69f9f59a2d48">The Problem with Free Options</a> was originally published in <a href="https://medium.com/boltzhq">boltzhq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WebLN integration with Boltz]]></title>
            <link>https://medium.com/boltzhq/webln-integration-with-boltz-e33a4e7b2f82?source=rss----30d0837e45db---4</link>
            <guid isPermaLink="false">https://medium.com/p/e33a4e7b2f82</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[atomic-swap]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[lightning-network]]></category>
            <category><![CDATA[litcoin]]></category>
            <dc:creator><![CDATA[Ankur]]></dc:creator>
            <pubDate>Fri, 07 Jun 2019 20:33:15 GMT</pubDate>
            <atom:updated>2019-06-07T15:49:57.186Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“WebLN is a library and set of specifications for lightning apps and client providers to facilitate communication between apps and users’ lightning nodes in a secure way. It provides a programmatic, permissioned interface for letting applications ask users to send payments, generate invoices to receive payments, and much more”</blockquote><p>Source: <a href="https://webln.dev/">webln.dev</a></p><p>Inspired by Ethereum’s <a href="https://web3js.readthedocs.io/en/1.0/">web3</a> standard, <a href="https://github.com/wbobeirne">William O’Beirne</a> set out to make a similar standard for lightning which could improve the experience on the web. Since then, it has gained noticeable traction in the community with lots of different lightning apps like<a href="https://lightningjoule.com/"> Lightning Joule</a> now supporting it. At Boltz, we constantly obsess about user experience and brainstorm ideas around making Boltz easier to use for the end users. Integrating WebLN was a no-brainer. Boltz integrates WebLN in a client-agnostic manner and follows the recommended <a href="https://webln.dev/#/ux-best-practices">UX best practices.</a> Integration of WebLN makes a lot of processes like generating and paying invoices a little easier, as depicted in the gif below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*f8JE4uIAALyyFWcqhFHI_g.gif" /><figcaption>Using Boltz with Joule</figcaption></figure><p>There are, however, other attempts to standardize the use of lightning on the web, notably by <a href="https://www.coindesk.com/the-new-effort-to-get-bitcoins-lightning-network-in-every-browser">W3C</a>. Nevertheless, we believe that WebLN is best poised and ticks all the boxes as of right now.</p><p>The different lightning browser extensions, notably <a href="https://lightningjoule.com/">Joule</a>, have been instrumental in making lightning easier to use. It lightning-charges any browser, which gives the user the ability to pay and create invoices without leaving their browser. We also like the idea of a lightning public key being used as a means of authentication on the internet, no PII required. <a href="https://github.com/fiatjaf/kwh">Kwh</a> is another WebLN powered browser extension with the same goal as Joule, but for different implementations of the lightning network: lightningd/eclair/ptarmigan. The fast-paced development of the lightning protocol and UX improvements is happening simultaneously which is opening up the floodgate of possibilities to build useful lapps. We are more excited than ever to continue taking an active part in building an exciting and easy-to-use product for end users.</p><p>Happy Swapping :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e33a4e7b2f82" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boltzhq/webln-integration-with-boltz-e33a4e7b2f82">WebLN integration with Boltz</a> was originally published in <a href="https://medium.com/boltzhq">boltzhq</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>