<?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[RADAR - Medium]]></title>
        <description><![CDATA[Building products for our next financial system - Medium]]></description>
        <link>https://medium.com/radartech?source=rss----4b3f39809aee---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>RADAR - Medium</title>
            <link>https://medium.com/radartech?source=rss----4b3f39809aee---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:25:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/radartech" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[RADAR → Blockcap → Core Scientific]]></title>
            <link>https://medium.com/radartech/radar-blockcap-core-scientific-b09d338f9f19?source=rss----4b3f39809aee---4</link>
            <guid isPermaLink="false">https://medium.com/p/b09d338f9f19</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[digital-asset]]></category>
            <category><![CDATA[mining]]></category>
            <dc:creator><![CDATA[Alan Curtis]]></dc:creator>
            <pubDate>Wed, 21 Jul 2021 13:34:44 GMT</pubDate>
            <atom:updated>2021-07-21T13:34:44.798Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jmQATNzO3TF4CCa22Php2g.png" /></figure><p>We’re excited to announce RADAR has been acquired by <a href="https://www.blockcap.com/">Blockcap</a>, one of North America’s largest digital asset miners powering our next financial system. We’re even more excited to announce that Blockcap is pending acquisition by <a href="https://www.corescientific.com/">Core Scientific</a>, the largest North American vertically integrated mining operation. Finally, we’re thrilled that Core Scientific will be <a href="https://www.prnewswire.com/news-releases/core-scientific-the-largest-blockchain-hosting-provider-and-digital-asset-miner-in-north-america-to-list-on-nasdaq-through-merger-with-power--digital-infrastructure-acquisition-corp-301338591.html?tc=eml_cleartime">merging with Power &amp; Digital Infrastructure Acquisition Corp. (Nasdaq: XPDI), a publicly traded special purpose acquisition company</a>.</p><p>Collectively, we have a shared vision for where our next financial system is headed and how we get there. We believe that blockchain is more than just another disruptive technology. It’s an opportunity to reshape our institutions to be more fair, inclusive, and sustainable. Together, we can build, power, and secure our next financial system.</p><p>Thank you to each and every user, every partner, every investor, and of course — our RADAR team and alumni. We are deeply grateful for your collective support, passion, and patience these past four years. We’ve been on quite the journey together, with plenty of peaks and valleys, but our shared commitment and duty to build a better financial system kept us going.</p><p>While we are retiring RELAY and REDSHIFT today, in many ways we’re just getting started, and we can’t wait to show you what’s next! Together, we have unprecedented scale and the platform to meaningfully accelerate the transition to a new financial system.</p><p>Of course, if you want to help build that financial system, we are<a href="http://blockcap.com/careers"> hiring for all roles!</a> For all press inquiries please <a href="https://radar.tech/press">contact us here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b09d338f9f19" width="1" height="1" alt=""><hr><p><a href="https://medium.com/radartech/radar-blockcap-core-scientific-b09d338f9f19">RADAR → Blockcap → Core Scientific</a> was originally published in <a href="https://medium.com/radartech">RADAR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RADAR Retro]]></title>
            <link>https://medium.com/radartech/radar-retro-7585d24a1ed7?source=rss----4b3f39809aee---4</link>
            <guid isPermaLink="false">https://medium.com/p/7585d24a1ed7</guid>
            <category><![CDATA[radar]]></category>
            <category><![CDATA[on-the-radar]]></category>
            <dc:creator><![CDATA[Alan Curtis]]></dc:creator>
            <pubDate>Thu, 31 Dec 2020 16:01:17 GMT</pubDate>
            <atom:updated>2020-12-31T15:59:26.211Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KXq8oE6hz71vwFGK62HuzQ.gif" /></figure><h4>2020</h4><p>Most public companies include a letter to their shareholders alongside their annual report. This letter is a rare opportunity for operators to speak directly to shareholders on vision, milestones, and strategy. This year, we continue that ritual (read <a href="https://medium.com/radartech/radar-retro-15f2d1a1e878">2018</a>, <a href="https://medium.com/radartech/radar-retro-af5be0832dd2">2019</a>). While most of you aren’t shareholders (yet), you’ve invested your time and energy to help us grow. This letter is to you.</p><h3>Our Next Financial System</h3><blockquote>We can’t predict exactly what our next financial system will look like, but we know three things. First, it’s going to be more fair, more transparent, and more inclusive. Second, we know it’s going to rely on peer to peer exchange, peer to peer payments, and a whole lot of new infrastructure. Third, blockchain is the best database to build a new financial system on top of.</blockquote><p>We wrote that in last year’s retro. We stand by our prediction. In fact, we believe we caught a glimpse of what our next financial system <em>could</em> look like this year with DeFi.</p><p>DeFi is unbundling traditional finance and building an open source financial system in its place. One smart contract at a time, DeFi is replacing counterparty risk with technical risk.</p><ol><li>Accessible: DeFi is global and permissionless from day one. The only prerequisite is an Internet connection.</li><li>Composable: DeFi uses open source blockchain smart contracts, not trusted middlemen, that are interoperable, immutable, and auditable.</li><li>Innovative: DeFi isn’t just recreating traditional finance, it’s inventing new financial instruments, incentives, and business models.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uvzHgHIHN92QhEl-" /></figure><h3><strong>Onboarding the World</strong></h3><p>We believe in the power of decentralized exchange, the verb, to create a global participatory market. This year we evolved RELAY into an aggregator with support from 16+ DEXs (thanks to 0x!) and added one-click Margin and Earn (thanks to dYdX!). Stay tuned for new features coming soon!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x46U-G2zO23_uXFo8p_73Q.png" /></figure><h3><strong>Join RADAR</strong></h3><p>One more thing. <a href="https://radar.tech/careers">We’re hiring</a>. We understand that no candidate is perfectly qualified for any job. Experience comes in different forms; many skills are transferable; and passion goes a long way. Even more important than your resume is a clear demonstration of accountability, impact, and the ability to thrive in a fluid and collaborative environment. We expect you to learn new things in this role, and we encourage you to apply if your experience is close to what we’re looking for.</p><p>We know that building a new, more inclusive financial system requires new voices. We understand that diversity of background and thought makes for better problem solving and more creative thinking, which is why we’re dedicated to adding new perspectives to the team.</p><h3><strong>Thank You</strong></h3><p>Thank you to the users, friends, investors, and all of the RADARers (current and former) who have helped us get here. We are so inspired by the collective hope in our community and we can’t wait to show you what’s next! <a href="https://twitter.com/RADARdotTECH">Follow along on Twitter</a>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*hdfKHGu8n5pKazIsns6NUA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7585d24a1ed7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/radartech/radar-retro-7585d24a1ed7">RADAR Retro</a> was originally published in <a href="https://medium.com/radartech">RADAR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Margin Trade on RADAR RELAY]]></title>
            <link>https://medium.com/radartech/margin-trade-on-radar-relay-987644dc1bbb?source=rss----4b3f39809aee---4</link>
            <guid isPermaLink="false">https://medium.com/p/987644dc1bbb</guid>
            <category><![CDATA[radar-relay]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[decentralized-exchange]]></category>
            <dc:creator><![CDATA[Brandon Curtis]]></dc:creator>
            <pubDate>Wed, 19 Aug 2020 18:38:53 GMT</pubDate>
            <atom:updated>2020-08-19T18:38:53.023Z</atom:updated>
            <content:encoded><![CDATA[<h4>one-click margin and short positions with up to 5x leverage</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*On3IHsdpHsjbQzpatZ0FcA.png" /></figure><p>As the range of financial functions available in DeFi continues to expand, simple token swaps at great prices are taken for granted. Traders don’t just want simple trades—they want to trade bigger positions with less capital and make bets on token prices increasing <em>or</em> decreasing. Margin trading enables this, powering leveraged positions that magnify returns and short positions that go up in value when the price of an asset goes down.</p><p><a href="https://relay.radar.tech/"><strong>Margin trading is now available on RADAR RELAY</strong></a><strong>.</strong></p><h3>ETH, DAI, and USDC margin pairs with no minimums</h3><p>At launch, we’re supporting ETH-DAI, ETH-USDC, and DAI-USDC trading pairs with up to 5x leverage, and short positions with up to 4x leverage. There is no minimum trade size.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/467/1*vqTQeM8w7Unzctw83WoKHQ.png" /></figure><h3>Lend ETH, DAI, and USDC</h3><p>Visit the EARN tab to earn interest while lending ETH, USDC, and DAI:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/466/1*uK2wtKSQcZ_cLodYyIcEZw.png" /><figcaption>token lending in RELAY, powered by dYdX margin protocol</figcaption></figure><h3>Margin trade at the best prices with DeFi liquidity</h3><p>Instead of relying on an isolated pool of liquidity managed by a single party, margin trades on RELAY make use of the latest in smart DEX routing to get you the best price prices available in DeFi.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*S4TSy7aKevacuHSGfmUIOw.png" /><figcaption>just like RELAY spot trading, trades execute on Curve, Kyber, Uniswap, Balancer… wherever the best price is!</figcaption></figure><h3>Connecting DeFi building blocks</h3><p>RELAY margin trading combines the deep DeFi liquidity of multiple DEX protocols through <a href="https://0x.org/why">0xAPI</a> with lending and margin capabilities powered by <a href="https://dydx.exchange/">dYdX</a>.</p><p>DeFi strives to bring all of the functions of finance — saving, trading, lending, borrowing, hedging, insuring, and more — to the open Ethereum platform.</p><p>Anyone can innovate, experiment, and improve DeFi’s capabilities by combining these permissionless building blocks into new products. Each addition enhances the value of everything in the DeFi stack.</p><p><a href="https://relay.radar.tech/"><strong>Start margin trading →</strong></a></p><p><em>Margin trading amplifies both potential gains and potential losses. Margin positions can be held open a maximum of 28 days, after which they can be liquidated without notice. Margin positions can also be liquidated without notice if they become undercollateralized. Do your own research and understand the risks. This article is for information purposes only. It is not intended to be and may not be construed or relied upon as investment, financial or legal advice. Please consult a duly licensed professional for investment, financial and/or legal advice.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Faxf9k9%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Faxf9k9&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/394e05f3c9b1becd5068c5679dbd96db/href">https://medium.com/media/394e05f3c9b1becd5068c5679dbd96db/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=987644dc1bbb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/radartech/margin-trade-on-radar-relay-987644dc1bbb">Margin Trade on RADAR RELAY</a> was originally published in <a href="https://medium.com/radartech">RADAR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Relaunching RADAR RELAY]]></title>
            <link>https://medium.com/radartech/relaunching-radar-relay-53718d2996c2?source=rss----4b3f39809aee---4</link>
            <guid isPermaLink="false">https://medium.com/p/53718d2996c2</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[dex]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[radar-relay]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[RADAR RELAY]]></dc:creator>
            <pubDate>Mon, 11 May 2020 12:20:33 GMT</pubDate>
            <atom:updated>2020-05-11T12:26:45.155Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y6n0zwSbj8PvtkM6yt8HxQ@2x.png" /></figure><h4>Now supporting more liquidity sources, wallets, and a better user experience</h4><p>Since RELAY launched two and a half years ago, it has facilitated more than 170,000+ trades with over $300M + trade volume across 175+ countries as the leading open order book relayer on the 0x protocol. Although the platform has experienced incredible growth, RELAY has fallen behind in supporting new features, adapting to protocol changes, and volume. Decentralized exchanges have evolved and RELAY hasn’t.</p><h4>Today we’re proud to relaunch <a href="http://relay.radar.tech/?utm_source=medium&amp;utm_medium=202005&amp;utm_campaign=sti_launch">RADAR RELAY</a>, an evolution of our open order book model with a simple, modern trading experience.</h4><h3><strong>Get the Best Prices in DeFi</strong></h3><p>The era of checking multiple DEXs to find the best price on the assets you want to trade is over. Thanks to the latest 0x upgrades (<a href="https://0x.org/docs/guides/v3-upgrade-guide">v3</a>, <a href="https://blog.0xproject.com/0x-roadmap-2019-part-3-networked-liquidity-0x-mesh-9a24026202b3">Mesh</a>, and <a href="https://blog.0xproject.com/access-all-dex-liquidity-through-0x-api-d5dd9a45af31">0x API bridge orders</a>) RELAY now offers smart DEX routing, giving users access to liquidity from multiple sources. In addition to the 0x orders we’ve always offered, bridge orders afford access to better prices by tapping into liquidity on Curve, Kyber, Uniswap, 0x, and Oasis, with more on the way. RELAY is now your one stop destination for buying and selling Ethereum tokens peer to peer, at the best prices available in DeFi.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2DkwFp2PhvviBh9bptQyAA@2x.png" /><figcaption>Left to right: Curve, Kyber, Uniswap, 0x, Oasis</figcaption></figure><h3><strong>Trade where you want, how you want</strong></h3><p>Mobile support is here! The new RELAY interface is accessible through mobile and desktop. You can now trade via RELAY directly from your favorite wallets, we’ve added support for all injected wallets such as Trust Wallet, Opera Wallet, Coinbase Wallet, Dapper Wallet and more. Thanks to WalletConnect and MetaMask we’ve expanded our wallet options to support 21 different Ethereum software and hardware wallets.</p><figure><a href="http://relay.radar.tech/?utm_source=medium&amp;utm_medium=202005&amp;utm_campaign=sti_launch"><img alt="" src="https://cdn-images-1.medium.com/max/640/1*dpwJpralUVR-R8dV-oQufg.gif" /></a><figcaption>RADAR RELAY Mobile UI</figcaption></figure><p>Limit orders can still be created on our open order book UI, RELAY CLASSIC, at <a href="http://classic.relay.radar.tech/?utm_source=medium&amp;utm_medium=202005&amp;utm_campaign=sti_launch_classic">classic.relay.radar.tech</a>.</p><h3><strong>Don’t worry</strong></h3><p>RELAY will continue to facilitate wallet-to-wallet trading with no sign-ups, no deposits or withdrawals, no accounts, and no trading limits. Transact securely without risking funds or personal information.</p><h3>Roadmap</h3><p>This is our first step in upgrading RELAY into a platform for the best that DeFi has to offer. In the coming months, you’ll see us launch new features such as Simple Margin Trading, Lending, and Trade Execution Guarantees. In the coming years and decades, we’ll continue to invest in building products for our next financial system. We have lots of work to do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SFYpoKBBcl7qZhdCLiR06Q.png" /></figure><h4><a href="http://relay.radar.tech/?utm_source=medium&amp;utm_medium=202005&amp;utm_campaign=sti_launch">Start trading now</a></h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Faxf9k9%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Faxf9k9&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/394e05f3c9b1becd5068c5679dbd96db/href">https://medium.com/media/394e05f3c9b1becd5068c5679dbd96db/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53718d2996c2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/radartech/relaunching-radar-relay-53718d2996c2">Relaunching RADAR RELAY</a> was originally published in <a href="https://medium.com/radartech">RADAR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Submarine Swaps Power REDSHIFT Cross-chain Payments]]></title>
            <link>https://medium.com/radartech/how-submarine-swaps-power-redshift-cross-chain-payments-f24dad53a400?source=rss----4b3f39809aee---4</link>
            <guid isPermaLink="false">https://medium.com/p/f24dad53a400</guid>
            <category><![CDATA[lightning-network]]></category>
            <category><![CDATA[on-the-radar]]></category>
            <category><![CDATA[radar-ion]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[Kevin Mulcrone]]></dc:creator>
            <pubDate>Thu, 05 Mar 2020 18:13:11 GMT</pubDate>
            <atom:updated>2020-03-05T18:13:11.005Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lqpbKBsR6Dk2lCySuhOrqA.png" /></figure><h4>REDSHIFT and Submarine Swaps explained</h4><h3><strong>What is REDSHIFT?</strong></h3><p>RADAR launched <a href="https://ion.radar.tech/redshift">REDSHIFT</a> in November to allow people to use on-chain assets like Bitcoin, Ethereum, and ERC-20 tokens for Lightning Bitcoin payments without signing up for an account or giving up custody of their assets to a third party.</p><p>REDSHIFT provides a new way for people, businesses, and developers to use the Lightning Network via trustless transactions across tokens and blockchains. See our<a href="https://medium.com/radartech/launching-redshift-trustless-cryptocurrency-payments-reinvented-9eb70fb9d4ee"> Introducing REDSHIFT</a> article for more high-level context on what REDSHIFT is and how it works. One thing that we haven’t yet covered is the mechanism that enables the on-chain to off-chain payment; the submarine swap.</p><h3><strong>What is a submarine swap?</strong></h3><p>Submarine swaps are a relatively new technology that has been ushered into the cryptocurrency space with the advent of Bitcoin’s Lightning Network. At their core, submarine swaps are a trustless way for two parties to exchange an on-chain asset such as Bitcoin for an off-chain asset like Lightning Bitcoin.</p><p>The on-chain/off-chain characteristic of the swap is similar to a submarine’s periscope — where part of the submarine exists above the water’s surface while the other half remains hidden in the sea — hence the name Submarine Swap.</p><p>Submarine swaps utilize a type of smart contract called a <a href="https://wiki.ion.radar.tech/tech/bitcoin/hltc#overview">Hash Time Lock Contract (HTLC)</a>.</p><p>HTLCs have been used in the past to atomically swap assets that exist on different blockchains at the base layer. <a href="https://twitter.com/decredproject/status/910224860625780736?">The first one happened between Decred and Litecoin in 2017</a>. On the Bitcoin Lightning Network, HTLCs are essentially programmable escrows that lock up funds on-chain until either:</p><p>(1) they are claimed using the secret returned from paying the specified lightning invoice</p><p>(2) a specified amount of time or blocks has passed.</p><p>In case (1), the payment secret to unlock the funds is only revealed after the corresponding Lightning invoice has been paid. This means that in order to take control of the on-chain funds, the counterparty must pay the Lightning Network invoice that contains the payment hash used in the hashlock.</p><p>If the counterparty does not pay the Lightning Network invoice, then case (2) happens and the funds remain in escrow until the timelock expires. Once the timelock expires, if there are still funds in the escrow, the original sender of the funds can withdraw them by creating another transaction to send them back to themselves.</p><h3><strong>The value of Submarine Swaps</strong></h3><p>Submarine swaps are a powerful tool that enables digital assets on different protocol layers and blockchains to be exchanged <em>without</em> a middleman. These cross-chain swaps don’t require another party to custody assets while a trade is taking place, which eliminates the risk of bad actors stealing funds before trades have completed, delays in service due to exchange outages, or third-party limits and fees.</p><p>More importantly in the context of Bitcoin, submarine swaps improve the liquidity of Bitcoin’s Lightning Network by allowing nodes to increase their <a href="https://ion.radar.tech/channel-capacity">outgoing capacity</a> without having to close and re-open channels with peers; nodes can request more outgoing or incoming capacity from others on the Lightning Network in exchange for an on-chain or off-chain payment respectively. This reduces the total amount of fees spent by 50% since only one transaction is required to participate in a submarine swap instead of two transactions to close and re-open a channel.</p><p>While traditional exchanges are beginning to roll out features that allow users to withdraw their Bitcoin via the Lightning Network, centralized exchanges still have their downsides:</p><ul><li>Account setup and KYC/AML requirements</li><li>Limits and delays on withdrawals</li><li>Deposit/Withdrawal fees</li><li>Risk of hacks or stolen funds</li><li>Shutdowns/outages</li></ul><p>Remember: <em>Not your keys, not your Bitcoin!</em></p><h3><strong>REDSHIFT explained</strong></h3><p>REDSHIFT is the plumbing that connects users looking to exchange their on-chain assets for liquidity on the Lightning Network.</p><p>REDSHIFT receives Lightning invoices from users and pays them in exchange for an on-chain asset. By going through REDSHIFT users are able to:</p><ol><li>Make a Lightning payment without setting up Lightning infrastructure</li><li>Rebalance their existing channels without closing and reopening</li><li>Pay a merchant/app that only accepts Lightning payments with other assets</li></ol><p>Because these two use cases likely have different types of users participating in them, we designed REDSHIFT as a <a href="https://github.com/RadarTech/redshift-monorepo/tree/master/packages/redshift.js">Developer SDK</a> and built a standalone <a href="https://ion.radar.tech/redshift">widget</a> which can be embedded into any website or existing checkout flow.</p><p>Once an invoice is submitted through the SDK or widget, REDSHIFT alerts our network of liquidity providers who respond with a price quote of how much they will charge to pay the invoice. REDSHIFT collects these quote responses, selects the one with the lowest rate, and constructs an HTLC transaction with parameters from the user and liquidity provider which is returned to the user for inspection.</p><p>After the user signs and broadcasts the HTLC transaction, REDSHIFT monitors the transaction and alerts the selected liquidity provider that the HTLC has been fully funded, therefore fulfilling their quoted amount. The liquidity provider then pays the Lightning invoice revealing the invoice payment secret (preimage). With the newly acquired preimage returned from the successful payment, the liquidity provider constructs a transaction to claim the funds held in the HTLC.</p><p>If the liquidity provider can’t pay the Lightning invoice, then the original user can get their funds in the HTLC back after the timelock expires. While invoices are able to be paid in most cases, sometimes a route cannot be found or the receiving party doesn’t have enough inbound capacity.</p><h3><strong>Wrapping Up</strong></h3><p>As the Lightning Network continues to gain adoption and stabilize, we believe submarine swaps will continue to be a critical tool for moving liquidity around the network and allowing invoices to be paid with on-chain assets.</p><p>REDSHIFT connects those looking to sell liquidity on the Lightning Network (liquidity providers) and those with on-chain digital assets (users) by providing: an easy-to-use Developer SDK, standalone widget, and a liquidity marketplace that coordinates the execution of submarine swaps. In contrast to other exchanges and services, the non-custodial nature of submarine swaps allow users to execute trade without compromising their identity while increasing the privacy of the entire network.</p><h4><a href="https://ion.radar.tech/redshift?utm_source=Medium&amp;utm_medium=Medium&amp;utm_campaign=OTRREDSHIFT">Try REDSHIFT today!</a></h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fj84nrj%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fj84nrj&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/d7e8221e0328ecf8fde1162417b44f20/href">https://medium.com/media/d7e8221e0328ecf8fde1162417b44f20/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f24dad53a400" width="1" height="1" alt=""><hr><p><a href="https://medium.com/radartech/how-submarine-swaps-power-redshift-cross-chain-payments-f24dad53a400">How Submarine Swaps Power REDSHIFT Cross-chain Payments</a> was originally published in <a href="https://medium.com/radartech">RADAR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing RELAY V3]]></title>
            <link>https://medium.com/radartech/introducing-relay-v3-abd8158f2771?source=rss----4b3f39809aee---4</link>
            <guid isPermaLink="false">https://medium.com/p/abd8158f2771</guid>
            <category><![CDATA[radar-relay]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[decentralized-finance]]></category>
            <category><![CDATA[0x]]></category>
            <dc:creator><![CDATA[RADAR RELAY]]></dc:creator>
            <pubDate>Fri, 03 Jan 2020 17:01:01 GMT</pubDate>
            <atom:updated>2020-01-03T17:01:01.293Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6wmJpmdjmfW5Ka7WhlYe3g.png" /></figure><p>On Monday January 6th, we are launching RELAY V3. This upgrade brings RELAY onto the latest version of 0x. We’re busy developing some exciting functionality for RELAY, but before we release these new features we need to upgrade the underlying protocol of the platform. There are no visual changes to the application, however <strong>this update affects traders with open orders.</strong></p><p>If you have open orders, here are the steps you’ll need to take:</p><h3><strong>1. Remake orders on RELAY V3.</strong></h3><p>Open orders on 0x v2 will not be valid on 0x v3. Starting Monday, please re-create these orders on the <a href="https://app.radarrelay.com/">new version of the app</a> and continue to use the new version going forward.</p><h3><strong>2. Cancel orders on RELAY V2.</strong></h3><p>If you don’t want your old, V2 orders to stay active after the transition or want to avoid duplicate orders, we recommend canceling your orders on the <a href="http://app-v2.radarrelay.com/">V2 application</a>. Cancelling orders on RELAY is simple; just go to the <a href="http://app-v2.radarrelay.com/account">accounts page</a> where you’ll find a button to “cancel all orders”. Use the bulk cancel functionality to save money on gas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nx2Eb74tAznGLJclPKtTmg.png" /></figure><p>On Monday, V3 will be active on app.radarrelay.com. The V2 version of the app will still available at <a href="http://app-v2.radarrelay.com/">app-v2.radarrelay.com</a> and will remain accessible for an extended period of time. We will make an announcement one week before we deprecate V2 completely.</p><p>You can reach us <a href="https://support.radarrelay.com/en/support/tickets/new">here</a> to answer any questions you may have.</p><p>We’re excited to share new functionality with you shortly! In the meantime, re-add and cancel your orders and stay tuned!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Faxf9k9%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Faxf9k9&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/394e05f3c9b1becd5068c5679dbd96db/href">https://medium.com/media/394e05f3c9b1becd5068c5679dbd96db/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abd8158f2771" width="1" height="1" alt=""><hr><p><a href="https://medium.com/radartech/introducing-relay-v3-abd8158f2771">Introducing RELAY V3</a> was originally published in <a href="https://medium.com/radartech">RADAR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RADAR Retro]]></title>
            <link>https://medium.com/radartech/radar-retro-af5be0832dd2?source=rss----4b3f39809aee---4</link>
            <guid isPermaLink="false">https://medium.com/p/af5be0832dd2</guid>
            <category><![CDATA[on-the-radar]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[radar]]></category>
            <dc:creator><![CDATA[Alan Curtis]]></dc:creator>
            <pubDate>Tue, 31 Dec 2019 16:57:57 GMT</pubDate>
            <atom:updated>2019-12-31T16:57:57.830Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rb1wRfwBjnIu_VECYBKk7g.gif" /></figure><h4>2019</h4><p>Most public companies include a letter to their shareholders alongside their annual report. This letter is a rare opportunity for operators to speak directly to shareholders on vision, milestones, and strategy. This year, we continue that ritual (<a href="https://medium.com/radartech/radar-retro-15f2d1a1e878?">review 2018 here</a>). While most of you aren’t shareholders (yet), you’ve invested your time and energy to help us grow. This letter is to you.</p><h3><strong>Shipping Our<em> </em>Next Financial System</strong></h3><p>We can’t predict exactly what <em>our </em>next financial system will look like, but we know three things. First, it’s going to be more fair, more transparent, and more inclusive. Second, we know it’s going to rely on peer to peer exchange, peer to peer payments, and a whole lot of new infrastructure. Third, blockchain is the best database to build a new financial system on top of.</p><p>This year, we introduced two new products, <a href="https://ion.radar.tech/redshift">REDSHIFT</a> and <a href="https://deploy.radar.tech/">DEPLOY</a>. REDSHIFT uses LN as a payment rail and is being used for merchant integrations and programmatic liquidity management. DEPLOY is the first NodeOps platform, offering developers a simple way to spin up and manage their blockchain infrastructure. Our flagship product, <a href="https://relay.radar.tech/">RELAY</a>, continues to grow with users around the world trading $100m this year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P_VwGoaCRdk2QRSwFHAclw.png" /></figure><h3><strong>Onboarding the World</strong></h3><p>Blockchain is a database. However, we believe it offers something no other database can - programmatic trust.</p><p>We believe <em>our</em> next financial system must shift trust from legacy institutions with opaque incentives to modern technology that mandates transparency. We believe <em>our </em>next financial system must shift trust from predatory platforms to fair protocols. We believe <em>our </em>next financial system must shift trust from the privileged to be globally inclusive.</p><p>In other words, our current financial system needs a database migration.</p><p>Like all new databases, blockchain must endure the difficult journey from education to abstraction. We’re humbled to play our part in creating new language, user actions, and design patterns. This year, we focused on evangelizing the Lightning Network. We created <a href="https://ion.radar.tech/">ION</a>, the homepage of the Lightning Network, an App Store, developer tools, and an onboarding guide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w-93utYK8k28qZGbgvFGEA.png" /></figure><h3><strong>Culturing Culture</strong></h3><p><em>Our </em>next financial system isn’t getting here next week, it’s going to take some time. We are building a durable culture, and on top of it, we are building an enduring, multigenerational company.</p><p>Most companies think about culture only as a noun, “culture is set at the top” or “we have a vibrant culture.” Culture as a noun is necessary but insufficient. We think culture is also a verb, it’s about maintaining conditions for growth. At RADAR culture is described through values, operationalized through principles, reinforced through rituals, and shared through stories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FXwInax3F7jpAV1s-UbgVA.jpeg" /></figure><h3><strong>Return the High Five</strong></h3><p>We are so inspired by the collective hope in our community. Thank you for your support! We can’t wait to show you what’s next!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ft9upq3%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ft9upq3&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/e1f2d459618bfd58454ba1d4cc5bf6fe/href">https://medium.com/media/e1f2d459618bfd58454ba1d4cc5bf6fe/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*7A-xh5ukU-nj2-d6KBPyhw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af5be0832dd2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/radartech/radar-retro-af5be0832dd2">RADAR Retro</a> was originally published in <a href="https://medium.com/radartech">RADAR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lightning Network: The Financial Operations Challenge]]></title>
            <link>https://medium.com/radartech/lightning-network-financial-operations-challenge-4f4df69a97ef?source=rss----4b3f39809aee---4</link>
            <guid isPermaLink="false">https://medium.com/p/4f4df69a97ef</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[lightning-network]]></category>
            <category><![CDATA[accounting]]></category>
            <category><![CDATA[on-the-radar]]></category>
            <category><![CDATA[finance]]></category>
            <dc:creator><![CDATA[Devin Eldridge]]></dc:creator>
            <pubDate>Tue, 22 Oct 2019 17:01:03 GMT</pubDate>
            <atom:updated>2019-11-01T16:26:09.053Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZxDLENTxsokOtf-vmKS07A.png" /></figure><p>At RADAR we believe that the Lightning Network will accelerate blockchain adoption, which is why we created <a href="http://ion.radar.tech/">ION</a> to be the home of the Lightning Network. The Lightning Network, a nascent and powerful solution that enables near instant bitcoin payments, needs the community’s help in building tools to make it better.</p><p>As a CPA working in the blockchain and cryptocurrency sector, I’m often asked about the Lightning Network and its implications for accounting for enterprise users. How can the network stand to benefit financial operations teams, and what are the main drawbacks that still require improvement?</p><p>Our team at RADAR has identified some ways that the community can improve the Lightning Network’s viability for the accounting domain, particularly in the form of enterprise tooling. This post outlines various opportunities for tooling to enable financial operations best practices on the network.</p><h3>What Is the Lightning Network?</h3><p>Excerpts from the Bitcoin and Lightning Network whitepaper abstracts combine to provide us with the following summary:</p><p><em>An instant and scalable peer-to-peer version of electronic cash would allow online payments of any amount to be sent directly from one party to another without going through a financial institution.</em></p><p>With apps like Venmo or Square Cash, users first connect to a banking network to access their banking assets. Banks attempted to solve for privacy by limiting information access to only the parties involved and trusted third parties. Conversely, Bitcoin solves the privacy issue by publishing all of the transactions to ensure the validity of transactions across the system while allowing users to maintain private keys.</p><p>The Lightning Network inherits security attributes of the Bitcoin blockchain and makes it faster, more affordable, and more scalable by enabling instant payments, micropayments, and new transaction types between peers. Lightning adds additional privacy by <a href="https://ion.radar.tech/onboarding#start">allowing peers to transact within off-chain “payment channels”</a>, and thus isolates the visibility of transfers to peers themselves. For paying those with whom a user doesn’t have a direct connection, <a href="https://wiki.ion.radar.tech/tech/lightning/payment-routing">Lightning routing nodes</a> exist.</p><p>One notable difference between “traditional” payment networks and the Lightning Network is the custody and nature of digital assets. With existing payment networks the currency being moved is typically the same (USD), with no state changes, and third parties provide custody. In a Lightning Network transaction, the currency remains the same (BTC), the nature varies between on-chain and off-chain states depending on the status of the channel, and users have the ability to retain custody depending on wallet selection.</p><h3>Financial Operations Opportunities and Challenges on Lightning</h3><p>Combining the Bitcoin and Lightning Networks allows peers to transmit payments, companies to accept digital currency payments, and developers to build infrastructure and tools. It also opens up a vast array of opportunities and challenges for enterprises wishing to engage in this frontier space. To enable enterprise participation in the Lightning Network, new tools are needed.</p><p>Enterprises can both <em>contribute</em> to the Lightning Network and <em>use</em> the network, but they have unique operational and reporting needs in order to fully operate on the network. One of the greater opportunities for enterprise adoption of the Lightning Network is the questions that arise around financial operations and accounting ambiguity.</p><h3>Treasury Management</h3><p>Treasury management within an enterprise comprises functions such as cash and risk management and optimizing for the availability and deployment of funds.</p><p>Each participant in the Lightning Network is responsible for their own asset security or must individually designate a third-party security provider. Actions like multi-signature fund access, verification solutions for digital assets, and limiting amounts accessible by different employees are solutions to securing assets.</p><h3>Financial Planning &amp; Analysis (FP&amp;A)</h3><p>Forecasting for different business activities is complicated by relatively volatile assets. Coupling the current volatility of the price of BTC with Lightning Network growth can compound the problem of determining asset allocation. Limiting funds converted to BTC allows the enterprise to have more stability but may be an opportunity cost on the BTC price and network opportunities.</p><p>We use a conservative approach, ensuring that our funds are accessible for our multiple product roadmaps while closely monitoring and predicting use of our nodes to ensure capital is available. Custom forecasting and treasury management tools will be necessary in order to simplify forecasting, allow for different digital asset usage, and enable full operation within the network.</p><h3>Accounting</h3><p>Transactions on the Lightning Network include opening and closing payment channels, sending and receiving funds off-chain, and routing a payment and collecting an associated fee.</p><p>The Lightning Network presents a trade-off between additional security, speed, and cost savings for public validation and transparency. New types of transactions emerge which create ambiguity around whether any particular transaction will require an accounting transaction to be recorded. With no guidance, there are instances on the Lightning Network that force a decision maker to arbitrarily decide whether or not an accounting transaction even occurred.</p><h3>A Challenge in Practice</h3><p>Putting all of that together, a real-life example where a Lightning Network transaction might result in ambiguity could be the act of opening a payment channel. In this scenario, let’s imagine that BTC is deposited from a BTC wallet into an LN-BTC-enabled wallet.</p><h4>Opening a Channel</h4><ul><li><strong>Treasury management.</strong> Is the resulting LN-BTC automatically in the same custody situation as the BTC was previously? Who now has access to the LN-BTC and what are the risks of the counterparty in the channel being able to maliciously claim funds?</li><li><strong>FP&amp;A.</strong> How much LN-BTC is needed as opposed to BTC? What is the enterprise trying to accomplish with the asset transition and what is the optimal amount?</li><li><strong>Accounting.</strong> Is this deposit a change to the nature of the asset requiring a recorded transaction? If yes, then the basis of the underlying BTC determines a gain/loss on the transition transaction. If no, then the basis of the BTC carries over to the LN-BTC. Further, whoever opened the payment channel must identify and record an associated transaction fee to the network.</li></ul><p>After opening a channel, what does it mean to lock up funds in a multisignature contract with another party? Are these funds in escrow? Are they still assets of the company? When does this change?</p><p>Assets deposited into a channel are now available to transfer to the other channel party. This does not mean any requirements have been met in order for the other party to claim the funds as their own, although the other party can attempt to claim the funds. However, since no business requirements or agreements of transfer have occurred the funds remain on the balance sheet as assets of the depositor.</p><h4>Closing a Channel</h4><ul><li><strong>Cooperative close. </strong>When removing funds from a channel, the respective balance given to each party should equal the amount of the interactions over the lifetime of the channel. However, the accounting transactions have already occurred within the channel. As obligations occurred and balances were updated, both parties should have already accounted for these in the previous time periods. The only accounting updates needed are for amounts paid for the on-chain transaction required to close a channel, if applicable.</li><li><strong>Losing a breach. </strong>A counterparty can attempt to close a channel and report inaccurate balances. The company would effectively lose money due to counterparty fraud, mistake, or negligence. This transaction would be classified as a loss of the corresponding inaccurate amount. However, this would have to be identified as such, which may be difficult if it wasn’t noticed during the occurrence.</li><li><strong>Successfully performing a breach remedy.</strong> If the breach is noticed and flagged as such upon close by the company, all of the funds in the channel will be awarded to the company. This net difference awarded is an extremely unique situation. A new account will be created for Channel Management Revenue on the income statement to account for the rewarded assets.</li></ul><h3>The View from Here</h3><p>Currently, the best solutions for financial operations ambiguity have been implemented on the Lightning network protocol layer itself. The LND Lightning Network client, for example, <a href="https://api.lightning.community/#lnd-grpc-api-reference">provides an API</a> for monitoring activity within a Lightning node. LND uses a permissions system called <a href="https://wiki.ion.radar.tech/tech/research/macaroons">macaroons</a> to securely grant read-only access to specific subsets of the node’s data and functionality and enable a simple accounting function: the ability to answer questions relating to a variety of transactions.</p><p>Isolating the transactions of a single node allows a company to focus on the transactions within the channels operated by the node and ignore the remainder of activity on the network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YU1Nmy4pFe5plTjrzm9T5Q.png" /></figure><p>The growth of peer-to-peer transactions has highlighted a need for better financial operations tools, and we expect to see more needs surfaced as growth continues. Transaction data can assist in surfacing information to provide insight without providing custody, allowing various enterprise functions to operate as long as access to information is provided. As the Lightning Network grows, it will be imperative to develop tools that allow peers and enterprises alike to function in their interactions with the network.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F4lps6u%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2F4lps6u&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252F4lps6u%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/571465b0878cd4f24a9cf19868086215/href">https://medium.com/media/571465b0878cd4f24a9cf19868086215/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f4df69a97ef" width="1" height="1" alt=""><hr><p><a href="https://medium.com/radartech/lightning-network-financial-operations-challenge-4f4df69a97ef">Lightning Network: The Financial Operations Challenge</a> was originally published in <a href="https://medium.com/radartech">RADAR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A practitioner’s guide to Bitcoin scaling solutions]]></title>
            <link>https://medium.com/radartech/a-practitioners-guide-to-bitcoin-scaling-solutions-85f010139a16?source=rss----4b3f39809aee---4</link>
            <guid isPermaLink="false">https://medium.com/p/85f010139a16</guid>
            <category><![CDATA[liquid-network]]></category>
            <category><![CDATA[on-the-radar]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[radar-ion]]></category>
            <category><![CDATA[lightning-network]]></category>
            <dc:creator><![CDATA[caleb tebbe]]></dc:creator>
            <pubDate>Wed, 04 Sep 2019 15:32:49 GMT</pubDate>
            <atom:updated>2019-09-04T15:32:49.003Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y8dtUUlobmDKb5tgYto2Jg.png" /></figure><h4>Exploring the design and trade-offs between Lightning and Liquid networks</h4><h3>Intro</h3><p>It is widely accepted that Bitcoin requires new solutions for use cases that are infeasible to scale on-chain. Operating as the most secure and decentralized proof-of-work (PoW) network comes with its own set of trade-offs: lack of innate scalability, as embodied by transaction costs and time to first confirmation. With these downsides in mind, researchers have designed novel solutions which leverage different aspects of the base layer to solve for speed and cost. Two emerging solutions are Lightning (payment channel) and Liquid (sidechain) networks. In this article we will explore the design of each system and their trade-offs.</p><h4>No free lunch; or why we need scaling solutions</h4><p>A theorem applied to general optimization problems is the <a href="https://en.wikipedia.org/wiki/No_free_lunch_in_search_and_optimization">no free lunch theorem</a>: for discrete problems, a candidate solution which demonstrates elevated performance in one class of problems pays for it in performance over another class. This theorem provides a logical framework to produce related theorems in specified classes of problems such as <a href="http://disi.unitn.it/~montreso/ds/papers/NoFreeLunchDS.pdf">distributed data access systems</a> (CAP) and more recently in <a href="https://github.com/ethereum/wiki/wiki/Sharding-FAQ#this-sounds-like-theres-some-kind-of-scalability-trilemma-at-play-what-is-this-trilemma-and-can-we-break-through-it">blockchain protocol networks</a> (scalability trilemma). (Note: these theorems are not universal and come with several caveats, but they summarize, rather intuitively, that there is no winner-take-all solution to many complex problems.)</p><p>It is intentional that Bitcoin sacrifices relative scalability to optimize for a combination of other features aligned with the design of PoW. Exploring the economics of PoW is outside the scope of this post but others have argued why <a href="https://medium.com/@danhedl/pow-is-efficient-aa3d442754d3">PoW is efficient</a>. In summary, the cost of PoW is a feature, not a bug, and provides economic incentives for the value propositions of Bitcoin (ie. incentivized immutability) enforced by the expenditure of an expensive physical resource (energy). We can see that altering solutions for PoW to optimize for scalability, such as reducing PoW difficulty and/or blocktime, in turn negatively affects Bitcoin’s PoW incentive structure. Due to this selection of trade-offs, Bitcoin adds immutability incentive <a href="https://howmanyconfs.com/">faster</a> than any competing network.</p><p>Since Bitcoin design goals do not optimize for scalability or speed, we must look to off-chain solutions. Two nascent architectures are routed payment channels, as implemented in the Lightning Network, and federated sidechains, as implemented by the Liquid Network. (Note: there has been <a href="https://twitter.com/gakonst/status/1146793685545304064">recent discussion</a> around narrowing the definition of “Layer2” to solutions which do not compromise on the security of the base layer. Under this definition Lightning is a Layer2 solution; however, Liquid is not.)</p><h3>Lightning Network overview</h3><p>The concepts underpinning the Lightning Network date back to the initial release of Bitcoin Core, which included <a href="https://github.com/trottier/original-bitcoin/blob/master/src/main.cpp#L427">sample code</a> to allow users to update a transaction in-memory before it was included in a block (<em>Nakamoto high-frequency transactions</em>), allowing for functionality akin to a payment channel. However, this design did not persist at scale as it can be trivially abused to bloat the network <a href="https://en.bitcoin.it/wiki/Vocabulary#Memory_pool">mempool</a> alongside other consistency issues.</p><p>A payment channel is a set of cryptographic techniques to allow users to make many transactions between them without writing intermediate state to the blockchain; when parties are done transacting, the channel is “closed” and final state is enforced on-chain. Over the years, there have been many iterations of payment channel designs leading up to the <a href="https://lightning.network/lightning-network-paper.pdf">Lightning Network whitepaper</a> (2015) which outlines techniques for structuring payment channels together to create a routed payment channel network. Since then, stakeholders have come together to agree on an evolving <a href="https://github.com/lightningnetwork/lightning-rfc">Basis Of Lightning Technology (BOLT)</a> specification resulting in many client implementations including <a href="https://github.com/lightningnetwork/lnd">Lightning Network Daemon</a>, <a href="https://github.com/ACINQ/eclair">Eclair</a>, <a href="https://github.com/ElementsProject/lightning">C-Lightning</a>, and <a href="https://github.com/nayutaco/ptarmigan">Ptarmigan</a>. Each client implementation maintains relative freedom for architecture design and solutions to the unique problem set posed in Lightning.</p><h4>Entering</h4><p>Joining the Lightning Network involves opening a payment channel with another node (running a BOLT-compatible client) on the network. To open a channel, two parties cooperate to create a multisig, agree which party will fund the multisig, exchange signed transactions that allow either party to spend the respective channel balances to themselves, and finally fund the multisig with an on-chain transaction. After a few confirmations of the multisig funding transaction, which serves to anchor the channel to the blockchain, subsequent payments in the channel happen off-chain. Participants cooperatively change the channel balance by exchanging data to update the state of the channel, and simultaneously updating how the multisig outputs can be spent.</p><h4>Transacting</h4><p>Lightning extends on the channel architecture described above to enable payments between nodes that are not directly connected by a channel. Distant nodes in the network graph can transact by constructing atomic payments that route across multiple nodes, and without requiring intermediate nodes to take custody of funds. A routed payment is established by a payer finding one or more intermediate nodes to the payee who are willing to change two channel balances such that they net a neutral or positive (with fee) balance. Routes are secured using chained <a href="https://wiki.ion.radar.tech/tech/bitcoin/hltc">Hashed Timelock Contracts</a> (HTLCs) acting as a conditional escrow, where the payee reveals the preimage to unlock the Hashlock chain and receive payment. Routed payments are constructed with <a href="https://wiki.ion.radar.tech/tech/lightning/onion-routing">onion routing</a>, meaning an intermediate node only knows about its local channels to route a payment and nothing about the payer or payee. Onion routing provides privacy and censorship resistance to routed payments.</p><h4>Exiting</h4><p><a href="https://wiki.ion.radar.tech/tech/channels/channel-closing">Closing a payment channel</a> can be done collaboratively or unilaterally by either party at any time via an on-chain transaction. A collaborative close involves both parties signing off on final channel state, allowing for the multisig outputs to be immediately spendable. In contrast, a unilateral close involves one party broadcasting a final channel state and waiting for multisig outputs to become spendable. The wait time is a dispute period during which the broadcast channel state can be challenged. This period is agreed upon by the channel parties ahead of time and might be anywhere from a few hours to a few weeks. If the broadcast state is the newest channel state, it is allowed to stand and the parties receive their share of the channel funds on-chain; if the broadcast state is not the newest channel state, this “breach-attempt” can be challenged by broadcasting a more recent valid channel state. If a channel party is caught attempting channel breach fraud, their funds in the channel are automatically forfeited to the other party.</p><h4>Failure modes</h4><p>A failure mode is defined as a condition where a network participant is subject to cost or friction due to an undesirable state. A routed payment channel network like the Lightning Network has several possible failure modes, many of which have mitigations that will be mentioned later:</p><ul><li><strong>Unable to send or receive payments due to network conditions: </strong>Routed payments require changes to the allocation of existing balances within the channels along a route. While the total capacity of a public channel is gossiped and verified by other nodes, the exact allocation of funds between parties is not. A payer attempts to construct a route from their local knowledge of the network, so it is not possible to know beforehand whether a payment of certain size will succeed on a particular route. If the allocation change of any channel leaves either party with a negative balance, the payment cannot be made and another route must be attempted.</li><li><strong>Unable to secure dust transactions: </strong>If a node’s channel balance is less than the cost to close that channel to enforce the respective balance on-chain, this channel’s balance is not economically secure. This is due to all payments being secured by HTLCs which are only enforceable as an output, and transactions creating outputs below the <a href="https://wiki.ion.radar.tech/tech/bitcoin/dust-limit">dust limit</a> are non-compliant and will be rejected by miners.</li><li><strong>Disputable breach-attempt:</strong> A channel participant can close a channel with a breach-attempt; if the corresponding party does not challenge the attempt during the dispute period, for instance because the node is running on hardware with poor uptime such as a mobile device, there is potential for the honest party to lose funds.</li><li><strong>Indisputable breach-attempt: </strong>Each active channel requires persisting of local data for breach-attempt remedy and state updates. If this data is lost or corrupted, a breach-attempt cannot be successfully disputed.</li></ul><h4>Features</h4><ul><li><strong>Key</strong> <strong>value propositions:</strong> final, private, fast, conditional, and cheap payments.</li><li><strong>Each node on the network can be identified using a persistent public key over the lifetime of the node.</strong> This allows for nodes to carry a <em>reputation</em> on the network. For instance, a node which maintains properly balanced channels is a desirable routing target and this can be gossiped to other nodes on the network. Conversely, a node that is poorly routed or performs breach-attempts can be avoided.</li><li><strong>Conditional payment structure allows for </strong><a href="https://wiki.ion.radar.tech/tech/research/hodl-invoice"><strong>new payment flows</strong></a><strong>,</strong> opening the door for revamping existing flows with trustlessness or new novel use cases:<br>- A payee could <em>withhold</em> a preimage from being revealed until some other condition is met.<br>- A payer could generate a payment hash and <em>withhold</em> the preimage until the payee meets some condition before receiving payment.</li><li><strong>Uses Bitcoin’s censorship-resistant immutability incentive and security features as an arbiter for any channel disputes.</strong></li><li><strong>Localized failures:</strong> As a payment channel is only between two parties, any errors or failures within the channel only impact channel participants and not the global network.</li></ul><h4>Open issues</h4><ul><li><strong>Availability constraint: </strong>The network necessitates a liveness constraint to: open a channel; make, route, or receive a payment; collaboratively close a channel; or dispute a malicious unilateral close. This makes up-to-date channel and network state data critical for safe usage. Failure to dispute a breach-attempt results in loss of funds, thus <a href="https://wiki.ion.radar.tech/tech/research/watchtowers">watchtower</a> designs have emerged to incentivize <a href="https://medium.com/@rzurrer/keepers-workers-that-maintain-blockchain-networks-a40182615b66">keepers</a> to watch for and remedy breach-attempts. This constraint also comes with a trade-off gain described in CAP theorem: predictable consistency. A payment, when executed, updates impacted network channels (state) atomically with a known upper bound on time being the HTLC timelock. When a timelock is expired, either the payment route is complete and all parties to the route are consistent with the new state, or all parties remain in the original state. (Note: a theoretical caveat exists where an intermediate node receives a preimage but does not settle upstream HTLCs to the intended payer, however in practice the intermediate node has no incentive to net a negative balance by not completing the route.)</li><li><strong>Liquidity management: </strong>The liquidity architecture of routed payment channels can be reduced to a specialized <a href="https://en.wikipedia.org/wiki/Flow_network">flow network</a>. While flow network semantics and algorithms are not new, Lightning poses some nuances to be worked around due to the opacity of channels. Currently, the maximum possible payment for a node is capped at an upper bound of a node’s largest local channel balance, however, <a href="https://wiki.ion.radar.tech/tech/research/atomic-multi-path-payments">atomic multi-path payments</a> (AMPs) will move this upper bound to adhere to the <a href="https://en.wikipedia.org/wiki/Max-flow_min-cut_theorem">max-flow min-cut theorem</a>. Along the same lines, to route across the network involves intermediary nodes willing to change the balance of two channels, so to be a reliable routing target, a node would need to monitor and maintain a channel balance conducive to routing under ever-changing network conditions. Several cost-incurring techniques are being developed to aid in channel balancing strategies, including circular rebalancing and <a href="https://wiki.ion.radar.tech/tech/research/submarine-swap">submarine swaps</a>, leading to service provider nodes specialized in routing.</li></ul><h3>Liquid Network overview</h3><p>The Liquid Network is an implementation of a federated pegged sidechain whose architecture was first proposed by founding members of Blockstream and others in a <a href="https://blockstream.com/sidechains.pdf">whitepaper</a> (2014). The authors come to similar conclusions as above for the need of off-chain solutions to supplement the intended design of Bitcoin, and propose a system which trades off decentralization for scalability (cost and speed). Liquid operates similar to the Bitcoin blockchain, even including a <a href="https://blockstream.info/liquid/">block explorer</a>, but with a different trust model and additional features. A sidechain validates data from other blockchains, therefore a pegged sidechain allows assets to be moved on and off the sidechain maintaining a two-way peg on each network. The <a href="https://elementsproject.org/">Elements Project</a> develops pegged sidechain clients; one of which is the <a href="https://github.com/ElementsProject/elements">Liquid client</a>.</p><p>To avoid expensive mining requirements or variable blocktimes, a <em>trusted</em> federation is selected to manage the intended operation of the network. Ideally, federation members are also major users of the network so operational incentives are aligned. Each new block is agreed upon by a majority of the federation (11 out of 15 members establish consensus) to eliminate <a href="https://en.bitcoin.it/wiki/Chain_Reorganization">chain reorganizations</a> (reorgs), which are common in Bitcoin, resulting in consistent and final one-minute blocktimes. Additionally, Liquid provides features to users including asset issuance and confidential transactions.</p><h4>Entering</h4><p>Anyone can enter the network by running a Liquid client and depositing BTC (peg-in) into a federation-controlled multisig wallet to mint transferable Liquid-bitcoin (L-BTC). To maintain solvency of the two-way peg, the federation must defend against reorgs, and therefore waits for 102 block confirmations (confirmation period) before considering a Bitcoin <a href="https://en.bitcoinwiki.org/wiki/Simplified_Payment_Verification">simplified payment verification</a> (SPV) proof that mints L-BTC onto the network.</p><p>A peg-in transaction works by a user cryptographically altering the federation public keys (still spendable by the federation private keys) and spending to the newly generated public key. Sometime after the confirmation period, the user can inform the federation what alterations it made to generate a new public key which the federation confirms along with the SPV proof to mint L-BTC. This mechanism affords users privacy from miners and even the federation itself, who do not know a peg-in is available until after the confirmation period. This also allows the user to tie other conditions to their L-BTC at this time.</p><h4>Transacting</h4><p>Transacting on the Liquid Network is semantically similar to Bitcoin since they use the same transaction model such that a transaction is constructed, signed, and submitted to the federation for inclusion in a block. There are other major additional features in Liquid such as confidential transactions and issued assets covered below, however these do not materially change the way transactions are signed or submitted.</p><h4>Exiting</h4><p>Withdrawing requires a request to the federation who approves a burning of L-BTC (peg-out) and spends an output with the corresponding amount of BTC from the federation multisig. (Note: as detailed in this <a href="https://blockstream.com/2018/11/06/en-liquid-full-node-and-wallet-release/">blog post</a>, for security reasons peg-out transactions can only be made to supported exchanges.)</p><h4>Failure modes</h4><ul><li><strong>Censorship potential:</strong> the federation could, in theory, reject all signed transactions from a particular address forbidding transfer or withdrawal.</li><li><strong>Malicious federation: </strong>since a majority of the federation reaching consensus is required to append new blocks or spend from the multisig, the same majority is required to unilaterally change the operating rules of Liquid. For example, in the worst cases the federation could collude to drain the multisig or reorg Liquid to an arbitrary depth with no recourse.</li><li><strong>Consensus failure:</strong> if the federation stops producing blocks all funds are frozen within Liquid. After 28 days of consensus failure, any combination of Blockstream and other emergency key holders (two out of three) can trigger an emergency shutdown allowing users to withdraw funds.</li></ul><h4>Features</h4><ul><li><strong>Private, high-volume, and high-velocity transfers between semi-trusted actors: </strong>We observe the trust model of the federation to infer the relative risk of other actors. The trust of the system is reliant on the honest operation of the federation, and falling back on emergency key holders in the event of a consensus halt. It follows that Blockstream and other emergency key holders have the least amount of downside risk, followed by other federation members, and finally non-federation users incur the highest risk. For users willing to accept this model, the risk incurred is less than that of solutions that take full custody of funds such as exchanges. This makes Liquid a strong network solution for users, and in particular federation members such as exchanges, over-the-counter (OTC) trading desks, and other high-volume traders to perform transactions and <a href="https://www.investopedia.com/terms/a/atomic-swaps.asp">atomic swaps</a> more cheaply, quickly, discreetly, and with a higher certainty of finality than the existing Bitcoin network.</li><li><a href="https://elementsproject.org/features/confidential-transactions"><strong>Confidential transactions</strong></a><strong> make use of </strong><a href="https://link.springer.com/chapter/10.1007/3-540-46766-1_9"><strong>Pedersen commitments</strong></a><strong> to obfuscate transaction amounts from other network participants</strong>, ensuring financial privacy while still guaranteeing valid transaction amounts. A user may optionally reveal their blinding key to another party to decrypt transaction amounts.</li><li><strong>Users have access to a feature called Issued Assets (IA), enabling the creation of new, user-managed assets within Liquid.</strong> Recently, <a href="https://blockstream.com/2019/07/29/en-tether-lands-on-the-liquid-network/">Tether issued USDt</a> on Liquid enabling users to perform private and fast transfers or atomic swaps between L-BTC and USDt.</li><li><strong>Due to Liquid using the same protocol as Bitcoin, parties can construct the same routed payment channels used in Lightning on top of Liquid. </strong>This would allow users to derive the same off-chain benefits of Lightning with fast and private channel creation, but falling back on the federation trust model of Liquid.</li></ul><h4>Open issues</h4><ul><li><strong>Emergency key holder liability: </strong>Blockstream and other’s control of Liquid emergency keys could infer some liability as a network operator. If Liquid consensus fails and two of three key holders are conflicted out of executing the emergency shutdown transaction, users have no native recourse in the system.</li></ul><h3>Network comparison and trade-offs</h3><ul><li>Both networks’ security is predicated on the security of the Bitcoin network in different ways: Lightning falls back on the Bitcoin network as an anchor and arbiter during dispute, while Liquid relies on high-depth SPV proofs to secure the L-BTC peg.</li><li>Both networks allow for rapid experimentation of nascent payment technology (i.e. conditional payments) and cryptographic features too risky or expensive to support directly on Bitcoin (i.e. confidential transactions).</li></ul><p><strong>Safe network operation:</strong></p><ul><li>Lightning safety is predicated on a node’s ability to manage (or outsource) local state data.</li><li>Liquid operates as intended so long as the federation operates as expected.</li></ul><p><strong>Trust dependency:</strong></p><ul><li>Lightning’s trust model falls back to the security of the Bitcoin network.</li><li>Liquid requires multi-party trust of the federation, falling back to emergency key holders.</li></ul><p><strong>Pain points:</strong></p><ul><li>Lightning’s trust-minimized nature comes at the cost of added complexity. Local liquidity is bilaterally managed by channel parties, creating additional economic and coordination costs to perform network-critical tasks such as routing.</li><li>Liquid’s utility is a function of reliable operation of federation members and their respective liquidity in the network. It therefore faces a problem if key target stakeholders (exchanges, OTC desks, etc) do not on-board, and a chicken-and-egg problem such that liquidity is unlikely to show up until liquidity is in the network.</li></ul><h3>Which is better for your use case?</h3><p>While both networks offer similar value propositions, each comes at the cost of vastly different trade-offs. Liquid makes the classic trade-off in centralized network operation to gain feature flexibility and fast finality, and therefore is likely unsuitable for users who value trustlessness. For federation members who are already dealing with high-volume custodian risk at exchange or OTC venues, Liquid can provide cost savings in operational expenses without the additional overhead of Lightning channel management. Lightning, on the other hand, maintains decentralization and the security characteristics of Bitcoin making it an ideal choice for fast, high frequency, and trust-minimized payments at the cost of increased local operational overhead. When selecting an off-chain solution users should consider the trade-off set as it relates to their current operation and problem being solved.</p><p>If you are exploring these networks you can find related topics on the <a href="https://wiki.ion.radar.tech/">wiki</a> and stay updated with <a href="https://twitter.com/radar_ion">ION Twitter</a>.</p><p>Special thanks to <a href="https://twitter.com/bcmakes">Brandon Curtis</a>, <a href="https://twitter.com/hellofrombea">Beatrice Leung</a>, and <a href="https://twitter.com/_prestwich">James Prestwich</a> for feedback on this post.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85f010139a16" width="1" height="1" alt=""><hr><p><a href="https://medium.com/radartech/a-practitioners-guide-to-bitcoin-scaling-solutions-85f010139a16">A practitioner’s guide to Bitcoin scaling solutions</a> was originally published in <a href="https://medium.com/radartech">RADAR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How We’re Building Our Engineering Culture at RADAR]]></title>
            <link>https://medium.com/radartech/how-were-building-our-engineering-culture-at-radar-ad131da627b1?source=rss----4b3f39809aee---4</link>
            <guid isPermaLink="false">https://medium.com/p/ad131da627b1</guid>
            <category><![CDATA[radar]]></category>
            <category><![CDATA[engineering-culture]]></category>
            <category><![CDATA[on-the-radar]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[caleb tebbe]]></dc:creator>
            <pubDate>Wed, 07 Aug 2019 17:19:38 GMT</pubDate>
            <atom:updated>2019-11-01T16:33:56.383Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yLkmDYl7qPRFUsnW4X7opA.png" /></figure><h3>Building Our Engineering Culture at RADAR</h3><h4>Learnings from growing our team the past two years.</h4><p>It’s been two years since the inception of RADAR. Since then, we’ve <a href="https://medium.com/radartech/series-a-55a3ab078720">raised a Series A</a>, brought two products to market (<a href="https://radarrelay.com/">RELAY</a> in September 2017 and <a href="https://ion.radar.tech/">ION</a> in February 2019), and assembled a talented engineering team.</p><p>As we look ahead, continuing to grow our team is essential to RADAR’s success. <a href="https://boards.greenhouse.io/radarrelay">We’re hiring</a>, and investing in a healthy engineering culture allows us to attract and retain the best talent. It’s an ongoing project (and always will be), but we’re committed to putting in the work.</p><p>Here’s how we’re doing it.</p><h3>Remote first</h3><p>RADAR is headquartered in Denver, Colorado, and in addition to on-site engineers, we also have team members in London, San Francisco, and Argentina accounting for 62% of our engineering team. Our remote-first mentality has allowed us to attract a more diverse and talented team than we could have locally, and it enables individuals to choose their own quality of life.</p><p>There are plenty of arguments for semi-remote teams not working: employees end up feeling alienated and left out of key decisions that affect them when off-the-cuff discussions turn into bigger plans; on-site employees resent the relative freedom of their remote counterparts. But these types of stories have not been our experience at RADAR.</p><p>Even in our open workspace, we rely on a strong Slack presence to communicate (which is better for productivity); and if it’s not documented in JIRA or Github, it never happened. We make a concerted effort to plan our daily stand-ups and biweekly retros for times when everyone on the team can participate. This way there’s more transparency and access to decision-making. Also, having high-quality A/V setups in our conference rooms has made it easier to whiteboard and screen share together.</p><h3>Optimize for deliverables, not hours</h3><p>After we’ve hired and onboarded new team members, the best thing we can do is respect their commitment to getting work done. “Hours worked” is not, in itself, a goal. In fact, it’s not even a metric worth tracking. We promote personal accountability, one of our three core values here at RADAR, instead.</p><p>This is where we’ve found a sprint-based approach to project management most useful. Pulling in tickets that you commit to deliver on over the next sprint makes progress and accountability tracking seamless. In sprint review, each team member is given an opportunity to discuss their work accomplished (or not), which encourages team members to hold each other accountable.</p><p>An engineering culture focused on deliverables benefits everyone, and our team is able to thrive within this flexible arrangement. With this process one of our engineers just completed a tour throughout South America as a digital nomad. Instead of micromanaging individual hours, we focus on our primary goal: shipping great products.</p><h3>Run the experiment</h3><p>Through experiments or side projects, our team has often found creative solutions for new problems, and it’s been really exciting to see how this has played out. One of our engineers wanted to figure out how to add a Lightning node to a single-board computer. On his off-time he wrote up some great documentation and bash script to install and run <a href="https://github.com/lightningnetwork/lnd">LND</a> in one command. We liked it so much we’ve used it to create personal nodes for our team.</p><p>At a recent <a href="https://medium.com/radartech/building-on-the-lightning-network-june-24th-3bd8fe104dee">Lightning event that we hosted</a>, we needed to solve for getting 100+ participants access to the Lightning Network to try out applications firsthand. Our Director of R&amp;D experimented with how to support many cloud-hosted Lightning nodes with one Bitcoin core instance and give everyone some sats (<a href="https://en.bitcoin.it/wiki/Satoshi_(unit)">satoshis</a>) to spend at the event. The setup was successful in reducing hosting costs and onboarding time such that an attendee could scan credentials on their phones at the door and get access to a node.</p><p>These were two successful experiments, but they came alongside many more that have failed. Part of encouraging ingenuity is creating a safe place for experimentation. There are no bad outcomes from an experiment that “fails”; if anything, we opt to fail fast and learn.</p><h3>Contribute back</h3><p>The Blockchain industry is built on open source software and the industry’s commitment to contributing back pushes us all forward. While working in this nascent developer ecosystem is exciting, it often comes with sparse and incomplete documentation and tooling. Through our development process we identify resources that could be useful for other developers and try to do our part in contributing back to the space.</p><p>This year alone we’ve released a <a href="https://medium.com/radartech/introducing-anthology-a-modern-scss-framework-for-writing-styles-that-scale-4eeae6f1bbb8">front-end framework</a>, <a href="https://github.com/RadarTech/ln-api-boilerplate">example boilerplate app</a>, and <a href="https://wiki.ion.radar.tech/">knowledge base</a>. On RELAY, we developed a <a href="https://developers.radarrelay.com/libraries/sdk">SDK</a> (software development kit) that allows developers to pull RADAR RELAY liquidity into their own dApps or help enable new use cases like <a href="https://blog.0xproject.com/dydx-and-contract-fillable-liquidity-cb965fc6f7e9">0x contract fillable liquidity</a>. Additionally, with ION we’ve released a popular <a href="https://github.com/RadarTech/lnrpc">TypeScript LND client wrapper</a>. We will continue to contribute towards open source software when possible.</p><h3>Promote individual growth</h3><p>We actively support team members as they grow professional skills and identity. Anyone is welcome to write an <a href="https://medium.com/radartech/tagged/on-the-radar">On the RADAR</a> blog post about a relevant topic of interest, and we support engineers who choose to compete in hackathons and contribute to the developer community. For instance, we’ve had participants at the <a href="https://www.ethdenver.com/">ETHDenver</a> hackathon for the past two years.</p><p>In the interest of hiring and supporting a diverse group of engineers, we seek out people with a broad range of backgrounds. You need to know the skills and use them well, but you don’t have to come to us with a computer science degree. (Our director of R&amp;D, for example, came from a non-CS academic background and is a self-taught coder.)</p><p>All employees at RADAR have access to a yearly stipend that can be used on conferences, certifications, courses, or any other manner of professional development. It’s been interesting to see how this stipend has been used; for instance, one team member wasn’t an engineer and worked in more of a technical support role, but he was interested in engineering and came from a strong math background. We paid for him to take an immersive JavaScript course and he now works on engineering-related tasks.</p><p>In the day-to-day rush, it’s easy to put professional development on the back burner, but folding development plans into performance reviews has already yielded excellent outcomes and serves to reinforce RADAR’s growth-minded culture.</p><h3>Follow best practices</h3><p>Though we value moving fast, we also believe that best practices reduce error, keep productivity high, and return the most optimal results.</p><p>Here’s how we commit to producing quality code:</p><ul><li><strong>Review on a tight loop. </strong>We require at least one review on every pull request before it gets merged into our codebase. We use GitHub as a communication tool as well as source control. Properly maintained documentation in each merge allows us to efficiently perform code reviews.</li><li><strong>Leave it better than you found it. </strong>I use an analogy of a scout going ahead of a caravan. The scout (one member of the team that changes depending on passion) works fast to build out an internal MVP or proof-of-concept, then the rest of the team follows behind to finesse quality and add more long-term sustainability to the project. Many of the codebases we collaborate with are fragmented, so with each feature we use, we aim to provide improvements (or maintain a fork) to contribute a better foundation for the next developer.</li><li><strong>Standardize wherever possible. </strong>We strive to standardize the language, tooling, and architecture that we use across products and services. This allows engineers to crosscut quickly and transfer from one codebase to another with little friction. Enabling pattern standardization reduces the volume of context switching and lets us focus on shipping efficiently.</li></ul><p>Our engineering culture at RADAR will continue to evolve as the company grows. We strive to establish a strong culture and workplace environment where the team can excel while tackling new problems. All the other metrics by which we measure success are a natural byproduct of our commitment to making our company an ideal place to work.</p><h4>Want to grow with us? <a href="https://boards.greenhouse.io/radarrelay">Apply to join the RADAR team!</a></h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ft9upq3%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ft9upq3&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/e1f2d459618bfd58454ba1d4cc5bf6fe/href">https://medium.com/media/e1f2d459618bfd58454ba1d4cc5bf6fe/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad131da627b1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/radartech/how-were-building-our-engineering-culture-at-radar-ad131da627b1">How We’re Building Our Engineering Culture at RADAR</a> was originally published in <a href="https://medium.com/radartech">RADAR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>