<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Carlo P. Las Marias on Medium]]></title>
        <description><![CDATA[Stories by Carlo P. Las Marias on Medium]]></description>
        <link>https://medium.com/@carlolm?source=rss-cce4c8f96ef2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9SfexzhgFGwZbOZalfLsIw.jpeg</url>
            <title>Stories by Carlo P. Las Marias on Medium</title>
            <link>https://medium.com/@carlolm?source=rss-cce4c8f96ef2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 07:52:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@carlolm/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Exchange types explained: CLOB, RFQ, and Automated, oh my!]]></title>
            <link>https://medium.com/hummingbot/exchange-types-explained-clob-rfq-and-automated-oh-my-4d63fbb1ed78?source=rss-cce4c8f96ef2------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d63fbb1ed78</guid>
            <category><![CDATA[algotrading]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[trading]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[Carlo P. Las Marias]]></dc:creator>
            <pubDate>Wed, 24 Apr 2019 18:14:21 GMT</pubDate>
            <atom:updated>2019-04-24T19:03:09.494Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*z9GZ9bRg5gAw2_qnnwQLTw.png" /></figure><p>Since Hummingbot is an open source bot platform that connects to many different exchanges, we have developed a deep understanding of the nuances between various exchange types.</p><p>In this post, we discuss the three main methodologies that digital asset exchanges use to facilitate asset transactions. We hope that this post helps crypto traders and developers choose the right exchange for their needs.</p><h3>TL;DR</h3><p>Exchanges perform the fundamental role in free markets of bringing together and coordinating buyers and sellers. Exchanges provide a venue for these parties to discover one another, negotiate and agree terms, and ultimately transact. Exchanges have adopted multiple methodologies to achieve this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qxPEAZkPsKvXTstfcZ4sCQ.png" /></figure><p>We also discuss the degrees of decentralization of each methodology. CLOB exchanges, as the name suggests, are centralized (even “decentralized exchanges” using CLOB have some degree of centralization) since exchange operators can control the flow of order information and access, whereas RFQ and automated exchanges allow for more or nearly full decentralization.</p><p><strong>For the full blog, please visit: </strong><a href="https://www.hummingbot.io/blog/2019-04-crypto-exchange-types/"><strong>Hummingbot Blog: Exchange Types</strong></a><strong>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s4cHcgtOa9G4s_9c6Lkx7g.png" /><figcaption>Excerpt from the full blog @ <a href="https://www.hummingbot.io/blog/2019-04-crypto-exchange-types/">https://www.hummingbot.io/blog/2019-04-crypto-exchange-types/</a></figcaption></figure><p><strong>To learn more about Hummingbot:</strong><br>Check out our website <a href="https://www.hummingbot.io/?utm_source=medium&amp;utm_medium=blog">http://www.hummingbot.io</a>;<br>Join the conversation on Discord: <a href="http://discord.hummingbot.io/">http://discord.hummingbot.io</a>;<br>Follow us on Twitter: <a href="https://twitter.com/hummingbot_io">https://twitter.com/hummingbot_io</a>; <br>Follow our blog: <a href="https://medium.com/hummingbot">https://medium.com/hummingbot</a>;<br>For business/partnership inquiries, contact <a href="/service/mailto:partnerships@hummingbot.io">partnerships@hummingbot.io</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d63fbb1ed78" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hummingbot/exchange-types-explained-clob-rfq-and-automated-oh-my-4d63fbb1ed78">Exchange types explained: CLOB, RFQ, and Automated, oh my!</a> was originally published in <a href="https://medium.com/hummingbot">Hummingbot Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Essential Crypto Regulations for Decentralized Finance + CoinAlpha’s KYC-Enabled Basket Protocol]]></title>
            <link>https://medium.com/hummingbot/essential-crypto-regs-for-decentralized-finance-10a99e3b13ac?source=rss-cce4c8f96ef2------2</link>
            <guid isPermaLink="false">https://medium.com/p/10a99e3b13ac</guid>
            <category><![CDATA[regulation]]></category>
            <category><![CDATA[decentralized]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[financial-regulation]]></category>
            <dc:creator><![CDATA[Carlo P. Las Marias]]></dc:creator>
            <pubDate>Sun, 14 Oct 2018 18:13:21 GMT</pubDate>
            <atom:updated>2018-10-14T18:29:39.747Z</atom:updated>
            <content:encoded><![CDATA[<h3>Essential Crypto Regulations for Decentralized Finance | CoinAlpha’s KYC-Enabled Basket Protocol</h3><p><em>Disclaimer: I am not a legal advisor. My comments below are based on my understanding of the current regulatory environment, after significant research and discussions with multiple, global law firms (and incurring an unthinkable amount of associated legal bills); the content below also only skims the surface. You are advised to confer with your own counsel before acting, and please comment if you have any differing views.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mJW96QkBvL7PqpPpWjCW9w.jpeg" /></figure><h3>TL;DR</h3><ul><li><a href="#8c3d"><strong>Blockchain technology and cryptocurrencies create the possibility for decentralized finance</strong></a>, a vision that has fueled recent ICOs and company creation…but unsurprisingly<strong>, this future faces regulatory challenges</strong></li><li><a href="#a8ee"><strong>The main regulations that concern cryptocurrency companies</strong></a> are (1) <strong>know your customer / anti-money laundering </strong>and (2) transactions dealing with <em>“</em><strong><em>securities</em></strong><em>”</em>; messing either of these up, even if <em>inadvertently</em>, has severe repercussions</li><li><a href="#49d8"><strong>Companies have adopted different approaches</strong></a><strong> </strong>for operating their companies and technologies in light of regulatory uncertainty; alternatives, examples, and risks are discussed</li><li><strong>Some companies in the sector are creating or </strong><a href="#2e02"><strong>adapting technologies for regulatory compliance</strong></a></li><li><a href="#cb97"><strong>CoinAlpha released a KYC-enabled version of its Basket Protocol</strong></a><strong> </strong>that conforms the protocol to KYC/AML and securities regulations</li></ul><p><a href="https://coinalpha.com/"><em>CoinAlpha</em></a><em> is part of a community called </em><a href="https://www.meetup.com/DeFi-Decentralized-Finance-Workshops-SF/"><em>DeFi</em></a><em> that is working on decentralized finance projects on the blockchain. On September 12, 2018, we hosted a meeting at our offices to discuss regulatory and compliance matters. Clearly, this is a topic of high importance and of concern for the community. Our thoughts and discussion of some of the key points follows.</em></p><h3>Preface: Decentralized Finance vs. Cryptocurrency Regulations</h3><p>The rise of blockchain technology and cryptocurrencies has emboldened visions of financial freedom and deregulation through decentralization. Over the past two years, we have seen successful ICOs and the creation of companies focusing on decentralized versions of exchanges, lending platforms, financial products, crowd funding, and prediction markets. Recently however, the idealists have had to come back down to Earth (a bit) due to increasing scrutiny from regulators (<a href="https://decryptmedia.com/2018/10/10/sec-tightens-the-noose-on-ico-funded-startups/">SEC</a> and FinCEN), who have been working to keep up with the developing technologies and have event recently been t<a href="https://www.lexology.com/library/detail.aspx?g=1d08099e-da08-4293-a99f-9dfbda5f4e0e">aking enforcement actions</a> against companies in the sector.</p><p>The reality is, we still live in a fiat world. Companies who want to create traditional corporations and establishments are not free from the grasp of regulators. The primary challenge of operating a cryptocurrency company in the current regulatory environment arises from the lack of clear rules and regulations. In the U.S. for example, all we have are <a href="https://medium.com/finance-3/cryptobaskets-hosho-security-audit-bug-bounty-program-24311c22a9d6">vague statements from the SEC Chairman</a>, while determining whether or not a digital asset is a “security” based on the <a href="https://en.wikipedia.org/wiki/SEC_v._W._J._Howey_Co.">Howey Test</a> is subject to interpretation.</p><p>While jurisdictions such as Malta and Thailand have been moving forward to create cryptocurrency regulatory frameworks, most of the world’s major jurisdictions have yet to take definitive action. Any company looking to operate in multiple jurisdictions is faced with the additional complication of having to navigate disparate regulatory regimes.</p><p>Of course, there are bad actors in the crypto space, which justifies a lot of this regulatory scrutiny. But (optimistically) there are many more companies who want to comply with rules, but have their hands tied due to uncertainty. So where do we go from here?</p><h3><strong>KYC/AML and Securities Regulations</strong></h3><p>First, we must understand what the main regulations are concerning companies dealing with cryptocurrencies. The overriding regulations are (1) know your customer / anti-money laundering (“KYC/AML”) requirements, such as those imposed by the U.S.’ FinCEN and its equivalent in most major, reputable jurisdictions, and (2) distribution of and transactions in <strong><em>securities</em></strong>, which, in the U.S., falls under the jurisdiction of the SEC.</p><p><strong><em>Messing up KYC/AML can land you in jail, while tripping up on securities regulations can result in hefty fines, companies being shut down, and being personally barred from securities markets and serving on corporate boards.</em></strong></p><p><strong>Anti-Money Laundering</strong></p><p>Due to their secretive nature as well as their ease of transmission, cryptocurrencies serve as an ideal conduit for laundering money. Sending Bitcoin or Ethereum is easy and instantaneous as compared to say moving around bags of ill-gotten money in brown paper bags. Naturally, they pose a high risk for abuse and therefore garner regulators’ attention.</p><p>Anti-money laundering regulation applies to companies operating “<strong><em>money transmitter businesses</em></strong>”, which may include transacting and trading in cryptocurrencies with customers. Such companies are required to know who their customers are prior to engaging in any transactions. Potential customers must be screened against sanction lists (such as OFAC) to avoid dealings with known terrorists, money launders, or politically-exposed persons. Other requirements include ongoing monitoring of customers to flag any suspicious or unusual transactions and periodically checking to ensure that existing customers have not been added to any sanction lists.</p><p><strong>Securities Regulations</strong></p><p>Regulators such as the SEC regulate securities because they want to protect investors from harm and potential loss on their investments through wrong-doing on the part of the security issuer, market manipulation, or from lack of understanding (or disclosure) about risks.</p><p>For social reasons, regulators are particularly concerned about protecting <em>unsophisticated</em>, “<strong>retail</strong>” investors; for example, they don’t want your grandparents losing all of their retirement savings from buying some scammy ICO.</p><p>Regulators are less concerned about “<strong>accredited investors</strong>”, which are investors deemed to be well-off enough to be able to tolerate investment losses or educated/professional enough to understand the risks of potentially speculative investments. The bar to qualify as an accredited investor <em>in the U.S.</em>: either (a) $200,000 annual income (or $300,000 jointly with a spouse), or (b) $1 million of assets excluding primary residence.</p><p>Since digital token issuers are typically newer companies (many of whom have only whitepapers and zero actual commercial progress), they present a higher risk for investors and, rightfully, raise red flags with regulators.</p><p><strong><em>What do “securities” have to do with cryptocurrencies?</em></strong></p><p>Some digital assets may be deemed “securities”. It’s easy to see that any digital tokens that have characteristics similar to equity (representations of ownership or claims to shares of profits), debt (tokens with rights to interest or repayment), or investment schemes (tokens with claims to investment participation) are “securities”. What’s less clear are tokens initially distributed as “utility” tokens but whose values are in some way tied to the performance and activities of the issuer. Also unclear are tokens that were potentially sold by the issuer under the pretext of an <em>investment.</em> From the SEC Chairman’s point of view, essentially <em>all</em> ICOs issued have been “securities”.</p><blockquote>Herein lies a major fundamental problem for companies transacting in cryptocurrencies; as mentioned above, determination of whether or not a digital asset is a “security” is not always clear.</blockquote><p><strong><em>What does this imply for my cryptocurrency transactions?</em></strong></p><p><strong>For token issuers</strong>, if your token might be deemed a security, you must comply with securities offering regulations. In the U.S., this means you must register the offering with the SEC (which is quite an involved process, requiring substantial disclosure and ongoing public filings) or otherwise rely on an exemption from registration.</p><p>Examples of exemptions are as follows:</p><ol><li>144A private placement open to accredited investors only</li><li>Reg S (sales outside of the U.S. to non-U.S. persons)</li></ol><p>Extending from these exemptions are <strong>transfer restrictions </strong>that would<strong> apply to all parties transacting with cryptocurrencies</strong>:</p><ul><li>For 144A private placements, limitation on the transfer of assets over the first year following issuance</li><li>Reg S securities: digital assets issued outside of the U.S. may not be distributed to U.S. persons.</li></ul><p>Due to the SEC’s currently lack of clarity in what digital assets constitute a “security”, digital assets issued outside of the U.S. that may be deemed as “utility” tokens or cryptocurrencies (i.e. <em>not</em> securities) in their respective jurisdictions may still be deemed a <em>security </em>by the SEC. Therefore, transfer of any such digital assets to U.S. persons may run afoul of U.S. securities regulations.</p><h3><strong>Regulatory Approaches for Cryptocurrency Companies</strong></h3><p>Anti-money laundering requirements are relatively clear; if you are operating a <em>money transmitter business</em>, you need to perform KYC/AML.</p><p>The main uncertainty for dealing with cryptocurrencies are related to securities regulations. Given this lack of clarity, what alternatives do companies have to launch and/or continue to operate their technologies and work in the crypto space? Below are some alternatives of what some companies are doing.</p><p><strong>Alternative 1. Business as usual; accept regulatory uncertainty (and risk)</strong></p><p>Some companies are operating and <em>comfortable</em> occupying a gray area…for now. They generally acknowledge operating with a some level of risk.</p><p><strong><em>Example: OTC Market Makers<br></em></strong>Some of the most profitable companies in the industry are companies that assist cryptocurrency holders to trade their cryptocurrencies: OTC market makers. Unlike public exchanges, OTC market makers have networks of clients, manage their order books privately, and discreetly facilitate larger “block” trades.<br> <br><strong>Regulatory risk</strong>: acting as an unregistered broker-dealer of <em>securities</em></p><p><strong>Risk level</strong>: varies depending on activities<br> <br><strong>What they are doing: </strong>most OTC market makers operate without licenses and are not registered with FINRA as broker dealers. The general rationale for this is that the SEC has not provided clear guidance on cryptocurrencies.</p><p>Operating in this manner does carry with it varying degrees of risk: trading in Bitcoin and Ethereum only is pretty low risk, since those are the only two cryptocurrencies that the <a href="https://www.cnbc.com/2018/06/14/bitcoin-and-ethereum-are-not-securities-but-some-cryptocurrencies-may-be-sec-official-says.html">SEC have actually given more clear guidance <em>are not</em> securities</a>. However, many OTC market makers do also transact in other cryptocurrencies, e.g. ERC20/ICO tokens.</p><p>The risk of this approach is that the SEC can shut down or fine such companies, if it deems some of the digital assets they are transacting in as “securities”. Some OTC market makers and counsels are optimistic that if (or when) the SEC begins to enforce regulations, it may give market participants time to become compliant (such as a grace period for registering with FINRA/SEC) or give advance notice to cease operations. But these are just guesses. To some degree, many OTC market makers acknowledge the possibility that they may be forced to shut down at any time.</p><p><strong>Alternative 2. Provide the protocol technology only</strong></p><p><strong>Risk level</strong>: low</p><p><strong>Regulatory risk</strong>: conducting or facilitating unregulated parties to conduct regulated activities (e.g. transacting in <em>securities</em>)</p><p>Some companies have chosen to provide decentralized technologies only and distance themselves from the activities conducted using their technologies. For an example of this, read Augur’s <a href="https://www.augur.net/terms-of-service/">Terms of Service</a> and <a href="https://www.augur.net/faq/">FAQs</a>. By not acting as parties to the transactions (i.e., not using the technologies themselves) conducted on their platforms, these companies <em>reduce</em> the risk of contravening regulations. Examples of this are decentralized exchanges (such as <a href="https://0xproject.com/">0x Protocol</a>) and <a href="https://www.augur.net/">Augur</a>. Augur has created a protocol for prediction markets, which are basically “contracts-for-differences” that very clearly have characteristics of derivatives/securities. To get comfortable with their regulatory position, Augur only provides and maintains the true peer-to-peer software only.</p><p>That being said, this approach is not without risk. One counsel has advised us that there is a possibility (even if remote) that providing technology to enable <em>unlawful</em> activities (which unregulated companies engaging in regulated activities is) may implicate the technology provider as well.</p><p><em>On a side note, regulatory considerations aside, one major downside of this approach is that it limits potential users and adoption. (1) Larger institutions may not be able to use these platforms because they are not regulated, and funds / institutional investors / registered money transmitter businesses may not be able to trade on DEXs because there is no KYC/AML enforced. (2) Separately, having to install local software, update local nodes: quite a lot of hoops to jump through for a potential user. (3) Lastly, the company itself has to rely on others to generate activity on its platform. “If you build it, they will come” 🙏…<br>A lot of headwinds, from a business perspective.</em></p><p><strong>Alternative 3. Partner with regulated entities</strong></p><p>One of the technologies that we have developed is the ability to create diversified portfolios of cryptocurrencies and efficiently make markets in the aggregate portfolios and their underlying cryptocurrencies. However, due to the regulatory uncertainty surrounding this activity, we have chosen to <a href="https://blocktelegraph.io/millions-raised-coinalpha-sharespost-blockchain/">partner with a U.S. registered broker-dealer</a>, <a href="https://sharespost.com/">Sharespost</a>. In this arrangement, we provide Sharespost with cryptocurrency expertise and our trading technologies. Since Sharespost is a registered broker-dealer, they are conducting regulated activities within the scope of their registration. It’s a win-win; we provide them with a new crypto product to offer their investors, and we get to deploy and implement our technologies.</p><p><strong>Alternative 4. Modify technologies to allow for regulatory compliance</strong></p><p>Companies are developing new technologies that are regulatory compliant, or modifying their existing technologies.</p><p>One of the most clear examples of this is the developing security tokens market. Companies are developing security token exchanges (such as <a href="https://www.tzero.com/">tZERO</a>, <a href="https://www.openfinance.io/">OpenFinance Network</a>) and security token protocols (e.g. <a href="https://www.polymath.network/">Polymath</a>, <a href="https://harbor.com/">Harbor</a>, <a href="https://www.securitize.io/">Securitize</a>), purpose-built to control the users of protocols and the methodology for the creation/issuance of digital assets, as well as to enforce transfer and any other related restrictions.</p><p>For our Basket Protocol, we have taken this approach and created a version of our protocol that allows for user control and transfer restrictions on Basket Tokens. Separately, our <a href="https://github.com/CoinAlpha/fund-protocol">Fund Protocol</a>, in which only whitelisted addresses are able to send subscription requests, also enables KYC/AML control.</p><h3><strong>KYC Enabled Basket Protocol</strong></h3><p>We have created a <a href="https://github.com/CoinAlpha/kyc-basket-protocol">KYC-enabled version</a> of our <a href="https://github.com/CoinAlpha/basket-protocol">Basket Protocol</a> by introducing a new module, the <a href="https://github.com/CoinAlpha/kyc-basket-protocol/blob/master/contracts/KYC.sol">KYC.sol</a> smart contract, which implements token holder whitelisting and transfer restrictions. Only whitelisted Ethereum wallet addresses are allowed to hold Basket Tokens; transfers to non-whitelisted addresses will fail. Similarly, any attempts to create or fill buy or sell orders that would result in non-whitelisted addresses receiving Basket Tokens will also fail. These restrictions are enforced at the protocol level.</p><p>This allows users of the protocol to add an off-chain KYC/AML verification step when using the protocol. The protocol administrator or a designated KYC Admin address may whitelist or unwhitelist Ethereum addresses. The main functions are summarized below:</p><pre>// Query if an address is whitelisted</pre><pre>function isWhitelistedHolder(address _holder) public view returns (bool)</pre><pre>// Function to whitelist an Ethereum address</pre><pre>function whitelistHolder(address _addressToWhitelist) public onlyOwnerOrAdmin returns (bool)</pre><pre>// Function to remove an address from the whitelist</pre><pre>function unWhitelistHolder(address _addressToUnwhitelist) public onlyOwnerOrAdmin returns (bool)</pre><p>The contracts which involve potential transfers of baskets tokens (namely the Basket and the BasketEscrow contracts) connect to the KYC module to verify validity of the recipient Ethereum address before allowing for the execution of token transfers.</p><p><strong>What do users do if they want to transact with parties other than those whitelisted in the protocol?</strong></p><p>The Basket Protocol is built on the premise that the Basket Token holder retains ultimate control of the underlying cryptocurrencies contained in the Baskets.</p><p><em>So doesn’t restricting transfers to whitelisted holders prevent this?</em></p><p>Actually, no. While a holder of a basket token may not transfer his basket token holdings to an address that is not whitelisted, the holder continues to have the ability to “debundle” basket tokens and take ownership of the underlying tokens. Once debundled, the underlying tokens can be individually transacted or transferred just like any other tokens. Most importantly, because a debundled basket token ceases to exist, basket tokens cannot be used in ways not permitted by the protocol administrator. Our protocol not only helps token holders, it does so in a way that works within existing regulatory frameworks.</p><blockquote>One of our core values at <a href="https://coinalpha.com/">CoinAlpha</a> is a belief that blockchain and cryptocurrency-related technologies have the potential to revolutionize many industries such as the financial and asset management sectors, which continue to operate with inefficient, age-old processes and procedures. It’s of utmost importance to carry on with our mission of proving out the underlying technologies. As a startup, we simply don’t have the luxury of time to wait around for clearer guidance from regulators; we need to start generating revenue today.</blockquote><blockquote>While this does dampen the realization of a fully decentralized financial system today, it does create a near-term path for us to move forward with our company. One step forward…</blockquote><h4>To learn more about <a href="https://coinalpha.com/">CoinAlpha</a>:</h4><ul><li>Check out our website <a href="https://coinalpha.com/">https://coinalpha.com</a>;</li><li>View our open sourced repos on GitHub: <a href="https://github.com/coinalpha">https://github.com/coinalpha</a></li><li>Join the conversation on telegram: <a href="https://t.me/coinalphainc">https://t.me/coinalphainc</a>;</li><li>Follow us on Twitter: <a href="https://twitter.com/CoinAlphaInc">https://twitter.com/CoinAlphaInc</a>;</li><li>Follow our blog: <a href="https://medium.com/finance-3">https://medium.com/finance-3</a>.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10a99e3b13ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hummingbot/essential-crypto-regs-for-decentralized-finance-10a99e3b13ac">Essential Crypto Regulations for Decentralized Finance + CoinAlpha’s KYC-Enabled Basket Protocol</a> was originally published in <a href="https://medium.com/hummingbot">Hummingbot Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DApp Infastructure Design (Part I)]]></title>
            <link>https://medium.com/hackernoon/ethereum-dapp-infrastructure-2b4f1e6bfa38?source=rss-cce4c8f96ef2------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b4f1e6bfa38</guid>
            <category><![CDATA[ethereum-kubernetes]]></category>
            <category><![CDATA[ethereum-parity]]></category>
            <category><![CDATA[ethereum-docker]]></category>
            <category><![CDATA[ethereum-event-tracking]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Carlo P. Las Marias]]></dc:creator>
            <pubDate>Tue, 14 Aug 2018 11:51:01 GMT</pubDate>
            <atom:updated>2019-04-24T07:16:39.176Z</atom:updated>
            <content:encoded><![CDATA[<h3>DApp Infrastructure Design (Part I): Reliable Ethereum Event Tracking with Kubernetes, Docker, and Parity</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1xg0rrwznNbGSqb5hKs3aQ.jpeg" /></figure><p><em>Learning Solidity and writing a smart contract is relatively easy, but we’ve found that the harder technical challenge is designing a </em><a href="https://hackernoon.com/tagged/dapp"><em>DApp</em></a><em> backend infrastructure that is secure, scalable, and snappy. Unlike traditional apps, DApps rely on the inherently probabilistic nature of </em><a href="https://hackernoon.com/tagged/blockchain"><em>blockchain</em></a><em> state and utilize Ethereum components that are relatively new and under active development. This is Part I of a series of articles about the architectural patterns and practices we’ve learned that might benefit other DApp developers.</em></p><p>Among the earliest lessons for anyone developing DApps on Ethereum is that logging events in smart contracts is an efficient way to report state changes and keep track of actions performed. Since events are emitted on the blockchain and can be replayed, while at the same time are technically not being stored in expensive blockchain state (i.e. memory or storage), they are a cost effective workaround for “storing” blockchain data. Events are also emitted real-time, allowing for real-time discovery and reporting of actions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/324/0*-8KzLW6P1NUzJe6p.gif" /></figure><blockquote>Events sound great! Everyone should use events!</blockquote><p>Hold on, not so fast… Another early, and potentially painful, lesson for DApp developers is that event watching is unreliable: <strong>an event is only useful if your DApp detects it when needed</strong>.<strong> </strong>If you need real-time data, but event discovery is delayed or events are missed altogether, this could result in a poor user experience or complete DApp failure.</p><blockquote><strong>Our solution: DApp developers who need reliable event tracking should consider adding Kubernetes/Docker to their toolkit. While these technologies do come with a bit of a learning curve, they neatly solve very specific problems in the current Ethereum technology ecosystem, mainly arising from reliability.</strong></blockquote><h3><strong>Problems with current Ethereum infrastructure technology</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G1Y940vVl27alNKggL8Wog.png" /><figcaption>CoinAlpha Node Monitor</figcaption></figure><p>At <a href="https://coinalpha.com/">CoinAlpha</a>, we have been running a lot of experiments and research on Ethereum infrastructure and reliability to support our product. We have been using different cloud providers such as AWS, Google Cloud, and Digital Ocean to host nodes in addition to running our own local nodes. We have set up node monitors that allow us to track node performance and reliability, as the sample screen shot shows.</p><p>Since our projects require as close to real-time event tracking as possible, we have had to come up with solutions to address the current issues with Ethereum infrastructure:</p><ol><li><strong>Ethereum nodes continually drop peers</strong>: For a number of reasons, Ethereum nodes periodically fail; they either stop syncing or fall behind, failing to have the latest blockchain information. The main cause for this is a <strong>drop in peer count</strong>, a kiss of death for any node. Drops in peer count can occur at any time, usually because a node gets stuck on a “bad” block that has been reorganized or ends up on a sidechain. Ethereum nodes work like the popular kids’ table; if your node ends up on a bad block, your node gets blacklisted or tainted, and all peers will try to drop it and prevent it from reconnecting.</li><li><strong>Infura websockets are unreliable</strong>: A few months ago, <a href="https://infura.io/">Infura</a> released the capability for web sockets connectivity to support event tracking. This provides the ability for developers to track events without having to run their own nodes. While this was a substantial improvement over <a href="https://ethereum.stackexchange.com/questions/25451/infura-web3-provider-for-events-get-watch">not supporting events at all</a>, it is still not a perfect solution. Infura’s web sockets are not able to maintain a constant connection and will drop connections every few minutes. Anyone who used the first versions of the <a href="https://github.com/AugurProject/augur-app">Augur desktop client</a>, which used Infura to build and maintain a database of Augur-related events, probably noticed this effect.</li><li><strong>Live event watching using </strong><strong>watch() can miss events</strong>: Nodes regularly fall behind in syncing, by a few blocks. One main reason for this is hard drive read/write speed. Paying up for high speed SSD drives is a possible mitigant, but with the current Ethereum mainnet database exceed ing100GB, cloud hosting bills begin to snowball pretty quickly. In addition, this still doesn’t address the drop in peer-dropping problem. If your node falls behind and then does a syncing catch-up, we have found that live events may be missed.</li></ol><h3>Solution: Redundancy and Monitoring</h3><p>A fault-tolerant Ethereum event watching system is one that can detect failures, conduct triage, and continue operating as if nothing happened. Here’s how we design ours:</p><ol><li><strong>Node redundancy</strong>: We run multiple Ethereum nodes, each with attached event trackers, to provide redundancy in the event of single or multiple node failures/delays.</li><li><strong>Event replays</strong>: Since live event tracking is unreliable, we cycle our event watchers to replay events, and stagger the replay timing between nodes. For added efficiency, we daisy-chain replays; we note the current block number at the time of each replay, so that the subsequent replay will only replay from that previous current block number.</li><li><strong>Event aggregator</strong>: Our event watchers report events to a centralized event aggregator. Our event aggregator keeps track of events it has already seen, and dispatches newly discovered and unique events to the different services we have that need to handle that event.</li></ol><p>The result is we have an architecture that looks like the following, with additional discussion of components below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lcq6VQm97dTfAf3bNC4lqQ.jpeg" /><figcaption>Ethereum event watcher architecture with Kubernetes and Docker</figcaption></figure><blockquote><strong>Below are some explanations and discussion on some of our architecture choices.</strong> And just some of the cool things we like about Kubernetes. I understand there are many ways you can address the problems I’ve raised. If you have any comments, questions, or suggestions, you can contact our team on our <a href="https://t.me/cryptobaskets">CryptoBaskets telegram group</a> or <a href="/service/mailto:dev@coinalpha.com">send us an email</a>.</blockquote><h4>Why Dockerize?</h4><p>For our application, the benefit of using docker is that we are able to add on additional services that need access to the blockchain simply by launching new containers that can link to our parity instances. Each container runs independently, so changes, additions, and upgrades can all be completed without disrupting any of the other existing running containers/services.</p><p>In the example above, we only have three containers connecting to the parity data: (1) the node monitor, (2) an event watcher for App 1, and (3) an event watcher for App 2. But we can easily add more containers, as and when our needs change.</p><h4>Why Kubernetes?</h4><p>Managing multiple node clusters (Ethereum clients and their connected services) can get pretty complicated and messy quickly. Not only are there multiple services that are linked and dependent on each other, updating and maintaining configurations as well as managing secrets (such as API keys) requires coordination and creates potential security vulnerabilities. In addition, monitoring servers and services for failures and restarting failed containers can get challenging in increasingly larger systems. That’s where Kubernetes comes in; it handles all of these issues.</p><p>Below are some of the features that we find particularly useful:</p><ul><li><strong>Replicas / scaling</strong>: Kubernetes is great for redundancy since it has built in scalability. You can automatically replicate node clusters (Ethereum clients and their attached services) by default, or through a single command line instruction. No need to configure each cluster separately.</li><li><strong>Adding on new services</strong>: You can simply add on new services or trackers that need access to your Ethereum node by adding containers to your Kubernetes deployment or stateful set.</li><li><strong>Persistent Volumes with Stateful Sets</strong>: Docker containers are ephemeral in nature. For syncing an Ethereum node, you don’t really want to sync a 100GB+ database every time your node fails and you have to restart. Kubernetes allows you to create Persistent Volumes, which is a segregated data store that maintains its data and state. If your Ethereum client is restarted, it will re-connect to the Persistent Volume and resume from where it last left off.</li><li><strong>Security</strong>: Using Kubernetes secrets are a neat way for storing API keys and any other sensitive data. The sensitive data is only exposed upon secret creation; once a secret it created, it is encrypted. The secrets can then be mounted as as a volume for any container that needs access to it; the original, unencrypted data does not have to be re-shared.</li><li><strong>IPC connections for added security and access control</strong>: By clustering services together and providing each access to a shared volume (such as the Persistent Volume), services that need a connection to parity can access it via IPC (<a href="https://en.wikipedia.org/wiki/Inter-process_communication">inter-process communication</a>) through the cluster’s file system. This creates additional security by helping to prevent unauthorized access to the Ethereum client. By default, most developers will connect to web3 providers using an RPC (<a href="https://en.wikipedia.org/wiki/Remote_procedure_call">remote procedure call</a>) http connection <em>web3.httpProvider() </em>over the internet<em>. </em>Unlike a connection via IPC, an RPC connection is potentially open to the general public and internet, creating the risk of unauthorized users discovering and connecting to your RPC web3 provider and overloading your client. Worst case, someone connecting via RPC web3 from the internet would be able to send transactions from any account that may have inadvertently been unlocked.</li><li><strong>Liveness and readiness probes</strong>: Kubernetes allows you to create monitors that restart or take pods out of service that have failed or are not yet ready. For example, you can use a readiness probe to prevent an Ethereum client from accepting any incoming connections if it has not yet been fully synced.</li><li><strong>Live, rolling updates / no down-time</strong>: When deploying updates to live apps, kubernetes neatly creates new <strong>pods</strong> before destroying the old, existing pods. While the new pods are being created and prepared (awaiting the <em>readiness</em> probe), existing pods remain in service. Only once the updated pods are ready and put into service, will the old pods be destroyed.</li><li><strong>Nginx ingress controllers</strong>: Kubernetes allows for the setup on an nginx ingress controller to direct traffic to different services on the cluster, which are routed by the URL address used. In your domain manager, you simply direct all subdomains to your ingress address, so you don’t have to manage each separately in case your servers’ IP addresses change. The nginx ingress controllers also manage https routing and TLS certificates. In the DApp ecosystem, this can also be applied to creating web3 providers for front-end applications. By default, Ethereum clients provide only insecure http connections.</li></ul><h4>Parity vs. Geth</h4><p>Despite the company’s previous missteps (<a href="https://paritytech.io/the-multi-sig-hack-a-postmortem/">multi-sig hack</a>, <a href="https://paritytech.io/a-postmortem-on-the-parity-multi-sig-library-self-destruct/">library hack</a>), the one thing Parity has going for it is they have created one reliable Ethereum client (ok…let’s also ignore the <a href="https://paritytech.io/parity-ethereum-client-issue-report/">consensus vulnerability</a> for now). While most developers start out using the Go implementation of Ethereum “<a href="https://github.com/ethereum/go-ethereum/wiki/geth">Geth</a>”, a quick google/stack exchange search will reveal a lot of frustration and problems for syncing Geth. We’ve found that in practice, Geth nodes take longer to sync and fall behind more often than Parity nodes (which you can even see in our node monitor dashboard screenshot above). On the other hand, we have found that Parity nodes will sync from scratch and are available for use within a few hours to a day.</p><p>Being relatively new technologies, Ethereum clients like Parity and Geth are constantly being updated and improved, which is why we maintain both types of nodes.</p><h3>Conclusion</h3><p>Decentralized applications have a bright future, but given the nascency of the technology stack for them, substantial back-end work is necessary to make them feel as responsive and reliable as centralized web and mobile applications. Luckily, we’ve found that a careful, intentional approach to architectural design makes this feasible, and we’ll publish posts about other important aspects such as security in the future.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b4f1e6bfa38" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/ethereum-dapp-infrastructure-2b4f1e6bfa38">DApp Infastructure Design (Part I)</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Basket Protocol: Hosho Security Audit + Bug Bounty Program]]></title>
            <link>https://medium.com/hummingbot/cryptobaskets-hosho-security-audit-bug-bounty-program-24311c22a9d6?source=rss-cce4c8f96ef2------2</link>
            <guid isPermaLink="false">https://medium.com/p/24311c22a9d6</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[cryptobaskets]]></category>
            <category><![CDATA[solidity]]></category>
            <dc:creator><![CDATA[Carlo P. Las Marias]]></dc:creator>
            <pubDate>Wed, 25 Jul 2018 00:44:52 GMT</pubDate>
            <atom:updated>2018-10-09T16:50:38.278Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V7OEuTC0YN4SBcx-2_nNJA.jpeg" /></figure><p>Security is of paramount importance in the blockchain world. Millions of dollars of value residing in open-source, immutable smart contracts accessible to anyone in the world can be a recipe for disaster. Past smart contract vulnerabilities have led to events such as the <a href="https://www.wired.com/2016/06/50-million-hack-just-showed-dao-human/">DAO $50 million hack</a> and the Parity <a href="https://www.coindesk.com/startup-lost-160-million-still-wants-shake-ethereum/">$160 million loss</a>.</p><p>At CoinAlpha, we take seriously the responsibility of securing our contracts and protecting the users of our protocols. While we have implemented rigorous testing and undergone security audits for our Basket Protocol, we recognize that issues may still arise, so we are announcing a bug bounty program to leverage and incentive the efforts of our community.</p><h3>Basket Protocol</h3><p>CoinAlpha, Inc. has developed and open-sourced its <a href="https://github.com/coinalpha/basket-protocol">Basket Protocol</a> which enables <strong>decentralized, non-custodial asset management</strong>. We have deployed a version of this protocol onto the Ropsten Ethereum test network, on top of which we have created the decentralized application <a href="https://cryptobaskets.io/">CryptoBaskets</a>.</p><h4>Development Practices for Security</h4><p>In developing the protocol, we aimed to follow Ethereum development best practices, building off of industry standards such as <a href="https://openzeppelin.org/">OpenZeppelin</a>’s smart contracts framework and following <a href="https://github.com/ConsenSys/smart-contract-best-practices">ConsenSys’ Smart Contract Best Practices</a>. Some of the training and certifications completed by members of our team include the <a href="https://consensys.net/academy/3">ConsenSys Academy Developer Program</a> and <a href="https://www.b9lab.com/">B9lab</a>’s <a href="https://academy.b9lab.com/courses/course-v1:B9lab+ETH-QA-5+2018-07/about">Ethereum QA Engineer Course</a>.</p><p>One of our company’s core values is emphasizing the importance of testing. We have tested the basket protocol code thoroughly, currently achieving <a href="https://coveralls.io/github/CoinAlpha/basket-protocol"><strong>97% test coverage</strong></a>. Our protocol currently includes <strong>1675 lines of code written for testing (</strong><a href="https://github.com/CoinAlpha/basket-protocol/tree/master/test"><strong>protocol tests</strong></a><strong>).</strong></p><h4><strong>Third-Party Security Audit by </strong><a href="https://hosho.io/"><strong>Hosho</strong></a></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/1*xAk5Y59diBitcRrOy-RaWw.png" /></figure><p>In June 2018, we engaged <a href="https://hosho.io/">Hosho</a>, a global leader in Blockchain Security, to complete a security audit. Items covered include:</p><ol><li>Appropriate and effective implementation of ERC-20 Token standards;</li><li>Documentation and code comments match logic and behavior;</li><li>Distributes tokens in a manner that matches calculations;</li><li>Follows best practices in efficient use of gas, without unnecessary waste;</li><li>Uses methods safe from reentrance attacks; and</li><li>Is not affected by the latest vulnerabilities.</li></ol><p><strong>Our code successfully passed with only </strong><a href="https://github.com/CoinAlpha/basket-protocol/pull/44/files"><strong>minor optimizations</strong></a><strong>. You can find the full report here: </strong><a href="https://github.com/CoinAlpha/basket-protocol/blob/master/files/hosho-basket-audit.pdf"><strong>Hosho Security Audit Report</strong></a>.</p><h3>Basket Protocol Bug Bounty Program</h3><p>Despite all the precautions and efforts we make to secure our protocol, we recognize that security is always an ongoing risk.</p><p>While we continually monitor the latest developments relating to security and industry best practices, we hope to work with the community to help make the Ethereum ecosystem safer by collaborating on security and coding best practices. To that end, we are launching the Basket Protocol Bug Bounty program.</p><h4>Scope of the Bug Bounty</h4><p>CoinAlpha’s <a href="https://github.com/coinalpha/basket-protocol">Basket Protocol</a> @ <a href="https://github.com/coinalpha/basket-protocol">https://github.com/coinalpha/basket-protocol</a>, all contracts named <strong><em>Basket__.sol</em></strong>.</p><h4>Bounty Evaluation</h4><p>CoinAlpha will use <a href="http://www.owasp.org/">OWASP</a>’s <a href="https://www.owasp.org/index.php/OWASP_Risk_Rating_Methodology">Impact and Likelihood risk framework</a> to help in evaluating bounties.</p><h4><strong>Bounty Rewards</strong></h4><p>Accepted bounties are awarded based on the following guidelines:</p><ul><li>Critical: up to $10k</li><li>High: up to $5k</li><li>Medium: up to $2.5k</li><li>Low: up to $1k</li></ul><p>All bounties and awards will be subject to the sole discretion of the CoinAlpha team. The quality and completeness of your report will be factored into determining the reward amount.</p><h4>Bounty Rules and Guidelines</h4><ul><li>Bounties are awarded on a first-report basis.</li><li>Take responsibility and act with extreme care and caution.</li><li>Do not use vulnerabilities you discover for purposes other than your own investigation.</li><li>Do not publicize or disclose to any third parties any details of vulnerabilities until after confirmation and approval from the CoinAlpha team.</li><li>Do not use social engineering to gain access to a system.</li><li>Non-security issues are not eligible.</li><li>Evaluations of eligibility, severity, and all terms related to a bounty and award are at the sole and final discretion of the CoinAlpha team.</li></ul><h4>Submission Guidelines</h4><ul><li>Submit reports to: <a href="/service/mailto:security@coinalpha.com">security@coinalpha.com</a>.</li><li>Please include detailed descriptions of the vulnerability or security issue, steps to reproduction, supporting artifacts, and suggested fixes (if any).</li><li><strong>Your privacy</strong>: we will only use your personal details to take action based on your report. We will not share your personal details with others without your express permission.</li></ul><h4>Evaluation Procedure</h4><p>The CoinAlpha team will investigate your report and will contact you to discuss the weakness, how you found it, and any follow-up action.</p><h3>Program Updates</h3><ul><li>July 30, 2018: <strong>First reward paid! </strong>A reader and blockchain developer looked into our protocol in detail and provided us with some code optimizations. While the multiple points raised were not security issues, we appreciate the detailed review and comments</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24311c22a9d6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hummingbot/cryptobaskets-hosho-security-audit-bug-bounty-program-24311c22a9d6">Basket Protocol: Hosho Security Audit + 🐞Bug Bounty Program</a> was originally published in <a href="https://medium.com/hummingbot">Hummingbot Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CBOE’s Bitcoin Futures: LIBOR Fixing Scandal 2.0?]]></title>
            <link>https://medium.com/hummingbot/bitcoin-futures-libor-fixing-scandal-2-0-51ae0c1b1d75?source=rss-cce4c8f96ef2------2</link>
            <guid isPermaLink="false">https://medium.com/p/51ae0c1b1d75</guid>
            <category><![CDATA[trading]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[Carlo P. Las Marias]]></dc:creator>
            <pubDate>Sun, 10 Dec 2017 10:42:11 GMT</pubDate>
            <atom:updated>2018-07-25T01:03:18.308Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Disclaimer: I am a cofounder of </em><a href="http://coinalpha.com/"><em>CoinAlpha</em></a><em>, a company that manages blockchain-native, quantitative cryptocurrency hedge funds that, amongst other currencies, trade Bitcoin. This discussion is for information and illustrative purposes only. It is not, and should not be regarded as investment advice or as a recommendation regarding a course of action.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kpp_6tIm0m3YlfmuwYAkSg.jpeg" /></figure><p>We stand on the eve of a major milestone in the history of Bitcoin and digital currencies. Within a few hours, the <a href="http://cfe.cboe.com/cfe-products/xbt-cboe-bitcoin-futures">Chicago Board Options Exchange (CBOE)</a> will open the trading of Bitcoin futures. Not long thereafter, the <a href="http://www.cmegroup.com/media-room/press-releases/2017/12/01/cme_group_self-certifiesbitcoinfuturestolaunchdec18.html">CME Group</a> will launch its own futures, with <a href="https://www.bloomberg.com/news/articles/2017-11-29/nasdaq-is-said-to-plan-bitcoin-futures-joining-biggest-rivals">Nasdaq</a> following suit in 2018.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*asxkusdtgA3QrXoWRZBzOQ.png" /><figcaption>Bitcoin price trajectory in 2017</figcaption></figure><p>These events are a testament of the increasing mainstream acceptance of digital currencies. Prices have surged on the optimism that these futures will for the first time enable the <a href="https://en.wikipedia.org/wiki/Global_assets_under_management">$139 trillion institutional asset base</a> to access the cryptocurrency asset class en masse. This optimism is compelling, as the cryptocurrency market has posted outsized returns and offers an attractive new alternative for asset managers to diversify and optimize their portfolios.</p><p>But in all the excitement of the run up in Bitcoin over the past week, mixed with ongoing debates into how the the opposing forces of enabled institutional access versus “<a href="http://business.financialpost.com/investing/the-next-big-short-hedge-funds-ready-to-bet-against-bitcoin-1">one of the greatest shorting opportunities ever</a>” will play out, the mechanics of the futures themselves largely went unnoticed.</p><p>As someone who previously spent many years in investment banking structuring various types of financial derivatives and poring over their minute details, I note some concerns with the CBOE Futures.</p><h4>Issues with the CBOE Bitcoin Futures Contract</h4><p>Payment terms for futures, as with all other financial derivatives, are determined by reference to a pre-determined index. In the case of the CBOE Bitcoin Futures (<a href="http://cfe.cboe.com/cfe-products/xbt-cboe-bitcoin-futures/contract-specifications">CBOE Bitcoin Futures specifications</a>), the reference rate for the price of Bitcoin is an auction rate published by <a href="https://gemini.com/">Gemini Trust Company</a>, a major New York-based cryptocurrency exchange.</p><p>Initially, I wasn’t surprised because I knew that Gemini was one of the only exchanges that even had an official price fixing. But the more I started to think about this, the more troubling it became.</p><blockquote>How can an exchange which has barely over 1% of the Bitcoin market volume, be used to set the price of a potentially major Bitcoin futures contract?</blockquote><p>This is eerily reminiscent of a major financial scandal that I witnessed firsthand in the traditional finance world: <strong>the LIBOR fixing scandals that were uncovered during the 2008 financial crisis and had allegedly occurred since 1991</strong>.</p><h4>Background to the LIBOR Scandals <strong>(</strong><a href="https://en.wikipedia.org/wiki/Libor_scandal"><strong>Wikipedia</strong></a><strong>)</strong></h4><p>LIBOR (London Interbank Offered Rate) is an interest rate set by leading banks in London based on the average rate at which each bank quotes to lend money amongst each other. While its use for interbank lending is a fundamental element of the financial system, LIBOR is used as a reference rate for <strong>$350 trillion of commonly used derivatives</strong> in the market, such as interest rates swaps, cross currency swaps, in addition to various types of loans, including mortgages and company loans.</p><p>A conflict of interest (no pun intended) therefore arises because these very same banks setting the LIBOR rate are also parties to trillions of dollars of other financial transactions whose own value and payments depends on that very rate.</p><p>For example, a bank could quote a low interest rate for LIBOR even though they could potentially lose money on interbank lending, but could profit materially on their other derivatives transactions with their clients. Ultimately, big banks were prosecuted for this and ended up paying billions of dollars of fines.</p><blockquote><strong>Problem: a coterie has exclusive influence over the outcome of financial contracts in which they stand to gain depending on that outcome</strong></blockquote><p>This problem is even more pronounced in the cryptocurrency market due to (1) clear delineation between the “physical” market (Bitcoin) and the derivatives market (CBOE futures), (2) cryptocurrency market segmentation, and (3) limited liquidity of the cryptocurrency market.</p><h4><strong>Gemini Price Auction Mechanics</strong></h4><p>As mentioned above, as of writing, <strong>Gemini exchange garnered only </strong><a href="https://coinmarketcap.com/currencies/bitcoin/#markets"><strong>1% of all Bitcoin transaction volume</strong></a><strong> over the past 24 hours.</strong> Granted, it is the weekend and the exchange was down several hours today (which itself can be regarded as another red flag), but even on normal trading days, its market share of volume is relatively low.</p><p>Even more surprising and what most people probably do not know, participation in the actual Gemini price auctions themselves is diminutive. Below is a table of recent fixings from this past week:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*pv73Pq0ZgDqN33ffkqi1-w.png" /></figure><p><strong><em>Source: </em></strong><a href="https://gemini.com/auction-data/"><em>https://gemini.com/auction-data/</em></a></p><p>Admittedly, to date, these fixings have not really been used for anything substantial, as far as I know. Nonetheless, this raises concern as the reference rate to be used for setting the CBOE Bitcoin Futures settlements was recently set by as little as 0.02 units of Bitcoin (or around ~$233.62)! On the Friday before the launch of the CBOE Futures, participation in the auction peaked for the week, but even then, participation only amounted to 245 Bitcoins (~$3.73 million).</p><p>Participation in the auction is open to Gemini customers only, which leads to another fundamental problem. If institutions are to use futures to access the Bitcoin market, would they knowingly enter into these contracts whose settlement terms are set by Gemini account holders only? Accounts holders which are less likely to be major financial institutions such as themselves, and are more likely to be small hedge funds? This is on top of the fact that the volume seen on the Gemini exchange represents only a relatively small portion of the market.</p><p>In addition, there is a wide variance of Bitcoin prices across exchanges due to market segmentation. Prices currently range from $13,247.40 to $14,250, representing a 7.6% price differential, from the top 16 most active exchanges (note that 16 was chosen only so as to include Gemini):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xqdX7epanbcRUgMSGk2rZA.png" /></figure><p><strong><em>Source</em></strong><em>: </em><a href="https://coinmarketcap.com/currencies/bitcoin/#markets"><em>https://coinmarketcap.com/currencies/bitcoin/#markets</em></a></p><p>This exchange segmentation exists for a number of reasons, such as the difficulty of setting up different exchange accounts, exchanges being globally distributed with different investor bases, and limitations on trading across exchanges due to the difficulty of moving fiat currencies (e.g. US Dollars) between exchanges.</p><p>This means that the Gemini Bitcoin price can easily diverge from the broader Bitcoin market, even if only during the time of the rate fixing. Again this opens up the Gemini Bitcoin price for manipulation.</p><h4><strong>Theoretical Example of How This Could Be Exploited</strong></h4><p>It would be all too easy for a hedge fund to exploit the CBOE Bitcoin Futures. A hedge fund that trades on the CBOE could realize arbitrage profits as follows:</p><ol><li><strong>Buy Bitcoin in Gemini and push prices higher</strong>: given the low liquidity in Gemini, a hedge fund could put in a large buy order in Gemini, pushing prices higher and driving the value of the futures higher</li><li><strong>Short position in CBOE Futures: </strong>enter into a short position in the Bitcoin futures that references the higher price</li><li><strong>Close the position upon expiration of the futures</strong>: the hedge fund could dump its Bitcoin in Gemini immediately before the price fixing, pushing the price lower in the auction, benefiting the payout on its Bitcoin futures</li></ol><p>This is possible because of the limited liquidity in the Gemini exchange and the ease of moving prices with a relatively small amount of Bitcoin.</p><h4><strong>What Does this Mean for Bitcoin Futures?</strong></h4><p>Investors looking at the CBOE futures as a way to access Bitcoin should best proceed with caution. I would expect any informed institutional investor who has done its homework would probably stay away, at least for now given their mechanics and the current state of the market.</p><p>It’s more likely that the early participants in these futures will be speculators looking to take advantage of a new way to monetize Bitcoin price volatility and are less motivated by fundamental investment thesis.</p><p>New investment will definitely be coming in; it just may not be from whom you expected or hoped it would come.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51ae0c1b1d75" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hummingbot/bitcoin-futures-libor-fixing-scandal-2-0-51ae0c1b1d75">CBOE’s Bitcoin Futures: LIBOR Fixing Scandal 2.0?</a> was originally published in <a href="https://medium.com/hummingbot">Hummingbot Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>