<?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 Rebecca Aspler on Medium]]></title>
        <description><![CDATA[Stories by Rebecca Aspler on Medium]]></description>
        <link>https://medium.com/@rebecca.aspler?source=rss-14724730c1de------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*857-foe_Wub5NHnjsHAieA.jpeg</url>
            <title>Stories by Rebecca Aspler on Medium</title>
            <link>https://medium.com/@rebecca.aspler?source=rss-14724730c1de------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:14:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rebecca.aspler/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[Custody Solutions: Minimizing Hardware, Maximizing Security]]></title>
            <link>https://medium.com/@rebecca.aspler/custody-solutions-minimizing-hardware-maximizing-security-fd3f52cbf7e2?source=rss-14724730c1de------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd3f52cbf7e2</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[mpc]]></category>
            <category><![CDATA[security-token]]></category>
            <category><![CDATA[cold-wallet]]></category>
            <category><![CDATA[custody]]></category>
            <dc:creator><![CDATA[Rebecca Aspler]]></dc:creator>
            <pubDate>Wed, 03 Jul 2019 09:48:04 GMT</pubDate>
            <atom:updated>2019-11-05T10:24:36.338Z</atom:updated>
            <content:encoded><![CDATA[<h3>The golden era of hardware is on its way out</h3><p>When it comes to secure custody solutions for digital assets, the golden era of hardware is on its way out.</p><p>On the surface, HSMs remain popular for institutional cryptographic key custody, blockchain or not — and cold wallets reign supreme in crypto-enthusiast culture on Twitter and Google alike.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/1*qPuW4-dFZeCILwlDcxc8vA.png" /></figure><p>But, prepare yourselves — hardware’s downfall is coming. Recent hardware wallet hacks, the movement of cryptography <a href="https://www.unboundtech.com/software-defined-cryptography-four-stage-approach/;">from hardware-defined to software-defined</a>, and the overall trend of digital transformation are the first signs. (For more on this in-depth, check out our article <a href="https://www.unboundtech.com/crypto-asset-protection-with-mpc/">here</a> on HSMs, Multi-sig, and MPC).</p><p>We’ve explored this phenomenon in-depth for exchanges; you can find more information on that <a href="https://www.unboundtech.com/cold-wallets-meet-software/">here</a>. Custodial solutions face different issues; for that — read on.</p><h3>Custodial Solutions: High Security, High Compartmentalization</h3><p>Institutional custody of digital assets (cryptocurrency and security tokens) is a different business than exchanges. Exchanges need <strong>liquidity</strong> to provide a variety of services at top speed; Custodial services<strong>’ </strong><em>raison d’etre</em> is to keep assets stored safely — and as such, institutional and/or individual clients typically keep larger sums in their custodial accounts than they would in an exchange. With this in mind, security becomes prioritized over liquidity as a business model.</p><p>In practical terms, this means the following:</p><p>The custodial <strong>client</strong> will prioritize a <strong>secure</strong> custody solution over an <strong>accessible</strong> one — and hardware’s primacy in the public consciousness re: secure asset protection impacts consumers during the decision-making process.</p><p>The <strong>custodial institution </strong>sets up their co-wallet strategy and overall security infrastructure on a completely different paradigm than exchanges.</p><p>In exchanges’ case, assets of one particular kind are usually aggregated into one cold wallet (wallet by token), and small amounts are transferred to users’ hot wallets on-demand for transactions and transfers.</p><p>Custodians may keep one hot <em>and</em><strong><em> </em></strong>cold wallet <strong>per customer</strong> to further ensure asset security, even at the compromise of access and liquidity. In this case, wallets are <strong>by customer</strong> and will hold multiple assets. An alternative strategy of a custodian would be to maintain an internal ledger for the order management layer and cold wallets per asset or per a group of customers.</p><h3>Revisiting cold wallets</h3><p>Cold wallets have stayed cool in the security world due to the reputation of hardware-based methods as a reliable cryptographic key management solution for enterprises and for cryptographic keys of all kinds — blockchain or non-blockchain. When hardware is offline, the logic goes, it’s harder to access — not just by hackers online, but physically by any malicious actors on the ground.</p><p>Hardware’s downsides are catching up to it, however — particularly in the age of digital transformation. Among them:</p><p><strong>Hardware, on its own, only protects against malicious key <em>access, </em>not malicious key <em>usage</em>. </strong>In practice, hardware solutions don’t protect against <a href="https://www.unboundtech.com/crypto-hacks-the-rise-of-the-rogue-insider/">attacks from rogue insiders</a> — an increasing problem in the exchange world, and one <a href="https://www.unboundtech.com/crypto-hacks-the-rise-of-the-rogue-insider/">recently brought to light</a> by the QuadrigaCX scandal. A workaround is possible by putting multi-sig on top of a hardware solution; multi-sig has limitations, however, as we noted <a href="https://www.unboundtech.com/crypto-asset-protection-with-mpc/">here</a>. The main one: low quorum availability and high overall TCO.</p><p><strong>The co-wallet strategy still leaves keys vulnerable during the “transfer” stage — once coins are moved from “cold storage” to “hot storage” for completing the transaction</strong>. This is a general problem with the co-wallet strategy, not just for custodial solutions; any connection to a network leaves the keys at risk in a “hot” wallet, even if they exist in the hot wallet for a short period of time. With the immutability principle of blockchain, there’s no do-overs for cryptocurrency transfers; a few seconds is all it takes to steal the assets, leaving a gaping hole in the “hardware is safer” argument. With cold wallets or co-wallets, the assets are only as safe as the protection measures taken to secure them once it’s connected to the network. Safe transfer — not safe storage alone — is the key to safe cryptocurrency transactions.</p><p><strong>Hardware vulnerabilities are notoriously difficult to fix — and they’re only getting more prolific. </strong>From <a href="https://www.unboundtech.com/malware-wild-real-implications-spectre-meltdown/">Spectre/Meltdown</a> to <a href="https://www.unboundtech.com/foreshadow/">Foreshadow</a> to Intel’s recent SGX vulnerability, hardware exploits are only getting more common — and can take months, if not years, to resolve. Often, a hardware patch involves replacing physical components. For a digital asset service, a hardware vulnerability could be the kiss of death to a business.</p><p>Custodial solutions prioritize customers’ trust, even at the expense of velocity. A careful buying public, the focus on individualized accounts and asset management as a <em>modus operandi </em>for custodians, and the greater need to fulfill compliance regulations all point to one solution for the custodial digital asset manager: a distributed trust platform.</p><h3>MPC: Trust Enabled by Security — Throughout the Transaction Lifecycle</h3><p>We can’t stress any more that MPC provides the security custodians need with the flexibility of software.</p><p>MPC is a mathematically based system of software-defined cryptography in which cryptocurrency keys exist as multiple key shares, distributed among multiple servers and endpoints to create a decentralized authorization method. Only if a certain threshold of participants approve the use of their key share, the key can be used. Importantly, a key never exists as a whole in one place, even while in use — thus keys can be protected by ensuring key shares remain separate, without requiring hardware-based physical security.</p><p>Unbound’s Crypto Asset Security Platform (CASP) provides all of the benefits of MPC, with the flexibility and agility needed for an ultra-secure custodial solution.</p><p>From a security perspective, CASP is the only solution on the market as of this writing which has received official FIPS 140–2 Levels 1 &amp; 2 certification. (More on that <a href="https://www.unboundtech.com/unbound-receives-fips-140-2-certification/">here</a>.) CASP’s m-of-n approval structures are infinitely scalable — and it’s the only solution which verifies quorum transactions on the cryptographic level.</p><p>As a software-only security solution, your cryptographic keys can be accessed at any time, from anywhere — desktop, server, or mobile. It’s a full locus of control for custodial solutions keeping up with the volatile digital asset market.</p><h3>Example of a Custodial Approval Policy</h3><p>A large quorum can be set up to ensure that each transaction not only meets compliance and regulation requirements, but also passes through approval from multiple customers and trustees of the account.</p><p>Consider the example below: Each transaction must be carried out only after 9 approvals from 4 groups: 1 out of 2 trustees, 2 of 3 customers, 2 of 4 custody managers — and all 4 custodial approvers required to check the transaction for compliance and regulation breaches:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/437/1*ymmMWxVw4Rw0qWgQcOJTqA.png" /></figure><p>Additional safeguards can include implementing a series of risk-based policies which would enlarge or reduce the quorum based on the USD value of the digital assets at the time of the transaction. CASP remains the only solution on the market which cryptographically verifies the quorum size based on risk level.</p><p>This solution not only ensures the custodial service maintains full control over the assets, but the customer becomes a key player in transaction approval. It’s a win-win for both custodian and client.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd3f52cbf7e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Next Generation Security for Blockchain Wallets — Now Open Source]]></title>
            <link>https://medium.com/thecapital/next-generation-security-for-blockchain-wallets-now-open-source-ed5328b2e14d?source=rss-14724730c1de------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed5328b2e14d</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Rebecca Aspler]]></dc:creator>
            <pubDate>Wed, 28 Nov 2018 13:14:51 GMT</pubDate>
            <atom:updated>2018-11-29T14:17:09.757Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C_CqumckRXSdnmm-bdPwQQ.png" /></figure><h3>Next Generation Security for Blockchain Wallets — Now Open Source</h3><h4>By <a href="https://medium.com/u/14724730c1de">Rebecca Aspler</a> on <a href="https://medium.com/altcoin-magazine?source=logo-4c740d51d3f2---c4037b4d8519">ALTCOIN MAGAZINE</a></h4><h4>Introduction — Blockchain Security is Still a Challenge</h4><p>Blockchain is radically changing the transaction-based industries. Protecting these crypto asset transactions, requires the protection of a private key that is a must have, in order to sign every transaction. It is interesting to note that regardless of the transaction type, whether its a cryptocurrency, a smart contract on a user’s identity, a voting transaction or the metadata of a supply chain package — all of these transactions rely on the very basic ability of the owner to securely sign the transaction with their private key.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*fsfvFdztBVOaF5b-GUl7xA.jpeg" /></figure><p>This embedded vulnerability of having to protect a private key which is a single point of compromise, is still a largely unsolved challenge. It is enough to take just one look at the total amount of hacks, as expressed in the following image, and it is easy to understand investors’ anxiety whenever it comes to keeping their cryptocurrencies safe.</p><p>In the traditional banking world, there are various ways in which banks can protect transactions of consumers and investors, including the callback of money that fellow banks respond to respectfully. That is not the case with blockchain assets and hence the greater need to protect these assets and hence their keys.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v0jaS5SM8-WipxIc_HHRwA.jpeg" /></figure><h4>Alternative Blockchain Security Solutions</h4><p>Today’s blockchain security solutions are either free and insecure, or secure but costly and complicated to develop, operate and use. An open source library that Unbound Tech has recently released, is now addressing this challenge.</p><p>With blockchain assets (i.e. keys and seed secrets) being a single point of compromise, they are a highly vulnerable and lucrative target when stored in memory, even if using methods such as white-box cryptography, which were proven easy to break (e.g. in the <a href="https://whibox-contest.github.io/">CHES 2017 Capture the Flag Challenge</a>, where 94 white-box implementations were all broken, most of them within less than a day).</p><p>More secure methods like Multi Sig introduce significant management complexity and development overhead, as (i) more keys need to be managed and (ii) they are heavily ledger dependent, thereby requiring constant coding efforts in order to support new and existing assets, as well as for maintaining sophisticated approval policies.</p><p>Dedicated cryptographic hardware-based solutions such as hardware tokens and HSMs need to support blockchain cryptography (specifically BIP32 and the relevant signing algorithms), otherwise very limited security value is provided; for example, using a mobile device’s secure enclave (assuming it doesn’t support BIP32 in the hardware) provides marginal value, as the BIP32 seed will appear in the clear in the unprotected OS memory when generated and while in use — where it is highly vulnerable.</p><p>The alternative of using secure hardware trusted execution environment (TEE) such as Intel SGX sounds tempting, however it was proven to be broken by software side channel attacks over and over in the past few years, so it’s security guarantees are questionable at best.</p><p>Moreover, the common problems with all hardware-based solutions such as high cost, platform availability, maintenance and lost devices make it a secure but a highly inconvenient, inflexible and non-crypto agile choice.</p><h4>Securing Blockchain Wallets — Now Open Source</h4><p>Committed to support blockchain security and the open source community, the newly released Blockchain Crypto MPC library provides <strong>all</strong> the cryptography needed in order to secure crypto assets — while being as or more secure than dedicated cryptographic hardware — for<strong> </strong>free.</p><p>Contents wise, the open source library consists of:</p><p>1. Support for two-party ECDSA secp256k1 — key generation and signing</p><p>2. Two-party EdDSA ed25519 — key generation and signing</p><p>3. Two-party BIP32 — generation, hard derivation and normal derivation.</p><p>4. Key share refresh</p><p>5. Zero-knowledge backup</p><p>Leveraging MPC for the protection of cryptographic keys and secrets, the blockchain security open source library can be characterized by the following critical security-features:</p><p>1. <strong>No single point of compromise</strong> — Compromising the seed or key material requires the attacker to compromise both the server and the endpoint simultaneously. Sensitive keys and secrets are shared as two random shares, which are stored on separate, segregated machines (‘machine’ stands for any computing device). Each of these shares alone tells nothing whatsoever about the key material.</p><p>2. <strong>No key or seed material ever appears in the clear throughout its lifecycle, including while in use and during generation.</strong> All cryptographic operations performed throughout the key lifecycle are performed without ever combining these 2 shares together. This includes signing, derivation and even generation. Bottom line — no key material or secret in the memory, ever. It is proven mathematically that obtaining the key material requires access to both key shares, thereby requires compromising both machines. A single machine, even if completely compromised and controlled by an attacker, can reveal nothing about the key material — simply because the key material never resides in any single machine.</p><p>3. <strong>Key shares refresh</strong>: The key shares are continually modified, and this modification is done without modifying the key itself. It is computationally efficient and can be performed very frequently — thus forcing the attacker to compromise both machines at virtually the same time in order to obtain key material.</p><p>4. <strong>Guaranteed non-repudiation</strong>; the application server cannot sign any transaction without cooperation from the endpoint device.</p><p>5. <strong>Resilient to side-channel attacks</strong>.</p><p>6. <strong>Milliseconds performance speed</strong> (assuming you are using bots to approve transactions. Humans can take as long as they wish).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/535/1*h03PTi32gPGyOnBBJOr63g.jpeg" /><figcaption>Multi Party Computation (MPC). The key never exists as one entity.</figcaption></figure><h4>What are the Typical Use Cases?</h4><p>How can you leverage this open source library? We thought of two typical use cases where wallets would find this open source library useful:</p><p><strong>Endpoint/Server Use Case</strong> — This use case is common for wallet service providers. The user has a mobile wallet on their endpoint device, typically their mobile phone or laptop. The wallet application communicates with a server application. The BIP32 seed and all signing keys are always split between the end user’s device (participant 1) and the service provider (participant 2). Performing any cryptographic operation on the seed or private key requires cooperation of both participants (and communication between them).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OyEpwYVmkp1yLKjOvAmrsA.png" /></figure><p><strong>Mobile/Laptop Use Case — </strong>This is a use case involving two end-user devices that typically belong to the same user. For example, a mobile phone and a laptop. Each device runs an app and both participants collaborate to create a secure blockchain wallet and sign transactions.<strong> </strong>The BIP32 seed and all signing keys are always split between the mobile device (participant 1) and the laptop (participant 2). Performing any cryptographic operation on the seed or private key requires cooperation of both participants (and communication between them).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k63qpBH0Hvz3UORQr5kLqA.png" /></figure><h4>Don’t Forget Key Backup. A Challenge on its Own.</h4><p>Backup is one of the most challenging aspects of crypto asset key management. This section briefly describes the backup functionality that the MPC open source library supplies you with and two potential usage scenarios.</p><p>The open source library includes a unique backup mechanism that introduces zero-knowledge backup: an encrypted cold backup that allows public verifiability. This property is significant, as it allows both participants to verify the correctness of the backup at any point in time without decrypting it. It therefore makes this verification secure and prevents a situation where a wrong backup was generated and stored.</p><p>1. <strong>User-Managed</strong> <strong>Backup</strong>- This is a common form of backup, with the role of backup management mostly on the end-user. An encrypted backup of the wallet can be stored in multiple locations for redundancy (for example, it can be stored by the service provider as described in the Endpoint/Server use case). The private key for this backup should be in the user’s sole possession, preferably in a cold backup. The backup recovery process should be used only for disaster recovery.</p><p><strong>2.</strong> <strong>Service Provider and Trusted 3rd Party, Managed Backup — </strong>The following scenario is an expansion of the Endpoint/Server use case that includes a 3rd party trustee service. The trustee service is used only when either the user’s device and/or the service provider have lost their respective key shares.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/1*oRT4M_feTmdXVnNXoamDpw.png" /></figure><p>This model creates a user-transparent backup, effectively similar to a 2-of-3 scenario: each quorum containing 2 of the 3 participants noted above would suffice to perform a cryptographic operation. This is performed by creating three different random share pairs upon wallet and seed generation. In the diagram, key share A is used by the user’s device and the Trustee Service, key share B is used by the user’s device and the Wallet Service Provider, and key share C is used by the Wallet Service Provider and the Trustee Service. It’s important to highlight that each of these pairs is completely independent, each is effectively a backup of the same seed.</p><h4>Bringing it all Together</h4><p>Unbound Tech is releasing this open source library — helping blockchain developers resolve the ongoing challenge associated with crypto asset and blockchain applications: the protection of cryptographic signing keys and seed secrets. It is our commitment to drive the blockchain security forward, committed to blockchain advancement and to the open source community.</p><p>For more details and for the code and documentation, go to <a href="https://github.com/unbound-tech/blockchain-crypto-mpc">Unbound GitHub</a> now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*psF2pEuUHsGgg7GB2w6GNQ.png" /><figcaption><a href="https://altcoinmagazinemastermindevent.eventbrite.com/">https://altcoinmagazinemastermindevent.eventbrite.com</a></figcaption></figure><p>Before moving on, make sure to press follow, leave a clap or 46, share today’s highlight and if you missed the last article, click <a href="https://medium.com/altcoin-magazine/ethershift-founder-explains-his-day-with-his-startup-advisor-john-mcafee-8e614f5a274">here</a>.</p><p>Read about the Altcoin Magazine Mastermind Event <a href="https://altcoinmagazinemastermindevent.eventbrite.com/">here</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F3c1144%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2F3c1144%2F&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/4b37fd61c8660dc2cbfe8232dfa683e2/href">https://medium.com/media/4b37fd61c8660dc2cbfe8232dfa683e2/href</a></iframe><p>Follow us on <a href="https://twitter.com/Alt__Magazine">Twitter</a>, <a href="https://www.investfeed.com/Altcoinmagazine?rec=90e98ef">InvestFeed</a>, <a href="https://www.facebook.com/Altcoin-Magazine-302454903822750/">Facebook</a>, <a href="https://www.instagram.com/altcoin_magazine/">Instagram</a>, <a href="https://www.linkedin.com/company/altcoin-magazine/">LinkedIn</a>, and join our <a href="https://discord.gg/DkwPvH5">Discord</a> and <a href="https://t.me/AltcoinMagazine">Telegram</a>.</p><p>The purpose of ALTCOIN MAGAZINE is to educate the world on crypto and to bring it to the hands and the minds of the masses.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed5328b2e14d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/thecapital/next-generation-security-for-blockchain-wallets-now-open-source-ed5328b2e14d">Next Generation Security for Blockchain Wallets — Now Open Source</a> was originally published in <a href="https://medium.com/thecapital">The Capital</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Challenges that are Embedded into the Co-Wallet Strategy of Cryptocurrency Exchanges]]></title>
            <link>https://medium.com/@rebecca.aspler/3-challenges-that-are-embedded-into-the-co-wallet-strategy-of-cryptocurrency-exchanges-7fc5a159a526?source=rss-14724730c1de------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fc5a159a526</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[exchange]]></category>
            <dc:creator><![CDATA[Rebecca Aspler]]></dc:creator>
            <pubDate>Thu, 15 Nov 2018 14:29:57 GMT</pubDate>
            <atom:updated>2019-11-05T10:36:39.564Z</atom:updated>
            <content:encoded><![CDATA[<p>Most exchanges — fiat or cryptocurrency — maintain an operational strategy that involves aggregation of funds from multiple consumers’ accounts into a single higher-level account. In the cryptocurrency space this is known as a ‘co-wallet’ strategy. By means of introduction, the co-wallet strategy assumes that an exchange doesn’t keep consumers’ money in a dedicated wallet per consumer, but rather in a wallet that includes funds of multiple consumers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Irwu1QLpOVD7UKEQarrWIQ.jpeg" /></figure><p>In a practical implementation, this means that consumers of an exchange don’t hold a key to a wallet but only online authentication means (e.g. a password and/or two-factor authentication) to an account’s balance and sell-buy order requests. The exchange, on the other hand, holds the keys to two types of wallets: hot wallets that keep a very small percentage of the exchange’s assets (typically up to 5%) and cold wallets, that hold the rest of the assets.</p><p>Whenever a consumer places a sell-buy order, a balance management layer will check if that account has enough balance to complete the sell-buy order. If the consumer’s balance is enough, an order management layer will trigger <em>a withdrawal order</em> from a coin specific hot wallet (for the ‘buy’ order) into the consumer’s pre-defined address and <em>a deposit order</em> into the exchange hot wallet address (for the ‘sell’ order).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*1SvjUkPfC7VyGjLRJOHylw.jpeg" /><figcaption>Co-Wallets Strategy</figcaption></figure><p>Behind the scenes, the cold-to-hot transfers enable the exchange to respond swiftly to consumers’ orders. The hot-to-cold transfers, on the other hand, ensure that most of the assets are kept offline and safe. The safety level of the cold wallets is usually achieved by several means, including permanent placement in an offline location, several people that multi-sign each transaction, hardware tokens.</p><p>This very brief introduction of crypto exchanges’ operational co-wallet strategy sets the stage for discussing the various challenges this strategy imposes.</p><p><strong>Challenge 1 — Security at the expense of velocity</strong></p><p>By keeping most of the assets in cold wallets and having to populate the hot wallets with enough funds to meet consumers’ demand, the exchange is always confronted with the need to decide how much money it is risking by keeping it in a hot wallet.</p><p>The transfer from cold to hot is purposely cumbersome — requiring several people to arrive physically at one or more locations, the use of dedicated hardware tokens, and the very temporary operation of a usually-offline server. Naturally, such a cumbersome process happens only a few times per day and certainly not in real-time. Based on demand, the larger exchanges may go through these cold to hot transfers 3 times per day and the smaller ones may complete this type of transfer only once every few days.</p><p>One can only imagine the operational toll that this co-wallet strategy has on the average exchange — both process-wise and time-wise. The bottom line is that most exchanges, while trying to reduce the number of times that their executives physically go to the cold wallets’ location to handle the cold-to-hot transfers, are bound to have less money in the hot wallets to reduce risk, and hence respond to consumers sell-buy orders slower than the business really demands. This relative slowness is perceived today as a built-in challenge into the exchanges’ mode of operation. Everyone would agree that when it comes to currency trading, velocity is second priority to security, and there is a tight tradeoff between the two.</p><p><strong>Challenge 2 — Minimizing the risk for an insider attack</strong></p><p>Cryptocurrency exchanges, very much like traditional banks, need to minimize the risk of insider employees that can very easily empty worthwhile wallets. With cryptocurrency exchanges, the risk is even greater than with fiat money, since there are no call backs and tracing the money trail effectively is almost impossible.</p><p>It is easy to imagine an employee sitting in an airplane, at the airport, easily signing a transfer order of millions worth of dollars to his address and just minutes afterward taking off to the Bahamas, to live his life fully and pleasantly.</p><p>Exchanges mitigate this risk by leveraging that co-wallets strategy that was described above. In addition, exchanges — certainly the big ones — define and operate large quorums of approving parties, often involving multiple people from the company’s C-level executives; A cumbersome and time-consuming approval process that puts a massive operational burden on the exchange.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qk9W3oHEJ9Q7EdBz99sZWA.png" /><figcaption>A typical approval policy of a sell-buy order</figcaption></figure><p><strong>Challenge 3 — Maintaining the co-wallet strategy for hundreds of cryptocurrencies</strong></p><p>This type of challenge can be compared to the proud home cook that is able to prepare a great dinner for a group of 8 people and the incomparable challenge of running a restaurant that feeds 150 people every evening.</p><p>Maintaining a co-wallet strategy for hundreds of cryptocurrency pairs, serving millions of customers, employing dozens of (can be trusted?) employees and managing it all securely and smoothly, responding to consumers orders in a near-real-time manner, is an enormous challenge — security-wise and operations-wise. The challenges that have been described above are multiplied by factors of magnitude when having to deal with hundreds of hot and cold wallets, millions of USD worth of money that should be transferred daily and dozens of employees that have inside information as to the signing workflows and approval policies.</p><p><strong>Bringing it all together: How are exchanges securing their assets?</strong></p><p>The traditional banking system has been building various security and operations mechanisms for the past 150 years. Cryptocurrency exchanges, a new entity in an emerging and fast-moving market, are facing greater challenges compared to banks, because of the complete digitization of the blockchain assets, the key-dependency and the irreversible nature of the cryptocurrencies’ transactions.</p><p>It is not surprising that up until recently, crypto exchanges have mostly taken the safe road and managed most of their assets <strong>offline, </strong>keeping only a fraction of the assets in hot wallets. This is the reason that most of the world’s cryptocurrencies (in terms of value) are still stored in air-gapped computers or HSMs that are kept offline in heavily guarded facilities.</p><p>This piece described the mitigation strategy that helps exchanges serve their consumers on a daily basis: the <strong>co-wallet strategy</strong>; a secure enough strategy with the toll of a slow response when demand exceeds the amounts that are stored in the hot wallets.</p><p>Considering the challenges that cryptocurrencies exchanges must deal with, it is easy to understand the offline and the co-wallets paradigms. However, the security platforms that can protect cryptocurrencies have evolved considerably in the last few years, offering new security solutions that enable the magic of a hot wallet which is as secure (if not more) than a cold wallet. If you are operating an exchange, imagine how your business would look like with 20%, 30% or even 50% in a hot wallet? The business and operational gains are immense. More on this in a future <em>Block to Basics</em> post…</p><p><em>For more thought leadership about digital asset protection, </em><a href="http://bit.ly/2C52XsO"><em>click here</em></a><em>.</em></p><p>More about exchanges in <em>Block to Basics</em>:</p><ul><li><a href="https://medium.com/block-to-basics/crypto-exchanges-why-are-they-being-hacked-so-often-b4346f281deb">Crypto Exchanges: Why are They being Hacked so Often?</a></li><li><a href="https://medium.com/block-to-basics/control-of-cryptocurrency-keys-how-exchanges-and-consumers-can-meet-each-other-halfway-7d294c108e1c">Control of Cryptocurrency Keys: How Exchanges and Consumers Can Meet Each Other Halfway</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fc5a159a526" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Securing Blockchain Transactions]]></title>
            <link>https://medium.com/@rebecca.aspler/protecting-blockchain-transactions-56d80204ddbd?source=rss-14724730c1de------2</link>
            <guid isPermaLink="false">https://medium.com/p/56d80204ddbd</guid>
            <category><![CDATA[multi-party-computation]]></category>
            <category><![CDATA[multi-sig-bitcoin]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Rebecca Aspler]]></dc:creator>
            <pubDate>Mon, 05 Nov 2018 13:19:19 GMT</pubDate>
            <atom:updated>2019-09-15T18:23:44.152Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Comparing MPC to Multi-Sig</strong></h3><p><em>(Editor’s note: The original title of this article cited 6 parameters, not 7. We added the seventh parameter due to user feedback. Found one we missed? Let us know after the jump.)</em></p><p>Multi-Sig and HSMs have become the default choices for businesses and institutions that want to protect cryptocurrencies and blockchain transactions. Both are known and well-documented but have many disadvantages, especially when compared to Multi-Party Computation (MPC). This blog post will compare specifically the Multi Sig feature to MPC, but before diving into the ‘unrightfully’ Chekhov’s Gun<a href="#_edn1">[i]</a> teaser, it is worthwhile explaining how Multi Sig has evolved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*4kqUVpDo3cG-N4isl2bsVw.jpeg" /></figure><p><strong>What is Multi-Sig?</strong></p><p>In simple terms, a multi-signature address is (usually a Bitcoin) address which is linked to more than one private key. Multi-signature addresses emerged in early 2012 when Bitcoin had presented an alternative to single key addresses.</p><p>Around that time, a new type of address called pay-­to-­script-­hash (P2SH) was defined and standardized. P2SH addresses can be recognized by the fact that they begin with a “3” instead of a “1.” Among the functionality supported by P2SH addresses is the ability to require multiple private keys to transact, known as multi-­signature, or more commonly, multi-­sig.</p><p><strong>Why has Multi-Sig evolved?</strong></p><p>If you run a business that deals in cryptocurrencies in large volumes, multi-signature security offers a familiar and accepted fiat-money-like way to process payments. Multiple people who manage the finances of the company can be provided a private key and act as approvers using multi-signature functionality. Every time you need to process a payment, the transaction will occur only if the multiple approvers sign the transaction per a defined policy.</p><p>The easiest real-­world analogy for explaining multi-­sig is a safe deposit box with 2 keys, one held by the customer, the other held by the bank. To open the box, both keys are required, making a safe deposit box analogous to a 2-­of-­2 multi-­sig address.</p><p>A P2SH address can support arbitrary sets of N keys, any M of which are required to transact — this is commonly referred to as “M-­of-­N.” In practice, the blockchain does enforce some limits as to the size of N, and by far the most typical multi-­sig implementations are of the form 2-­of-­2 or 2-­of-­3; and hence, a single-­key address would be considered 1-­of-­1.</p><p>To explain how Multi Sig compares to Unbound MPC, it is worthwhile to first recap what MPC is all about — and how Unbound has applied MPC to transform key management using our Distributed Trust Platform.</p><p><strong>What is MPC — and how does it eliminate the single point of failure?</strong></p><p>MPC enables a distributed model of trust based on splitting secrets across multiple entities, with a strong yet elastic and agile pure-software platform. In the case of blockchain transactions, MPC is used for securing the vault (wallet) keys and executing the sign operation.</p><p>Unbound’s Distributed Trust Platform generates multiple random key shares for any given private key. The key-shares are stored separately in different locations and each random share alone reveals no information whatsoever about the actual key.</p><p>The key shares are stored in different servers and/or end points that are strongly segregated, for example between different clouds, in a hybrid-cloud constellation or between endpoint devices and one or more servers, to ensure the utmost security. The key shares are never combined at any point in time: all operations are carried out without ever uniting the key shares, including key generation and key usage (i.e. signing).</p><p>Unbound leverages its distributed trust platform to create a blockchain security platform. Unbound Crypto Asset Security Platform (CASP) has been designed with tier-1 banks to meet their highest security requirements for protecting crypto-currencies.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FBpa1yvwmrKI%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DBpa1yvwmrKI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FBpa1yvwmrKI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/49fbb9a46a34a6752ef46c340e15646e/href">https://medium.com/media/49fbb9a46a34a6752ef46c340e15646e/href</a></iframe><h4>Seven Parameters to Consider When Comparing MPC to Multi-Sig</h4><p>This is where we return to that Chekhov’s Gun that was mentioned in the first paragraph.</p><p>When looking at Multi-Sig from the bird’s eye view, it does seem good. At least good enough. However, MPC has many advantages over Multi-Sig that people may not be aware of.</p><p><strong>Reason 1 — Ledger-agnostic</strong> — Multi-Sig solutions are usually ledger-dependent. The reliance on such solutions inevitably requires you to rely on custom code that will be created per ledger and per your needs. It’s ineffective, time-wise and cost-wise.</p><p><strong>Reason 2 — Easy definition of more than 2 of 3 approvers</strong> — You want an easy way to define and change a large approval quorum that will adhere to your regular approval workflows. With CASP, you can add define any number of approvers using the platform’s built-in capabilities — no need to write single line of code. You do not want to be dependent on custom coding and on the IT people to code the definition, or in adding or disabling the approvers, in your Multi-Sig approval policy.</p><p><strong>Reason 3 — Flexible approval policies</strong> — Financial institutions and service providers want to change the approval policy per customer, per amount, per hour of the day — in an easy and code-less manner. With cryptographically-enabled MPC, that is not limited to static 2 of 3 multi signers, this flexibility can be achieved.</p><p><strong>Reason 4 — Simple script resulting in timely processing and lower transaction fees</strong> — Multi-Sig solutions, when requiring more than two participants, typically require customized coding and a more complicated code than the usual in-transaction signature. One may not acknowledge that at first, but people are usually not aware of the fact the Multi- Sig is Bitcoin targeted and with any other asset, currency or token, the Multi-Sig functionality will require the custom coding of the various signatures. Such complicated scripting is processed by blockchain nodes more slowly and will require higher fees to be processed. It’s ineffective, time-wise and cost-wise.</p><p><strong>Reason 5 — Seamless user experience </strong>— With MPC, key shares are transparent to the participants. When receiving a notification to review a blockchain transaction, they go through the MFA, review the transaction and approve or decline it. All of that is happening without them being aware of the share being used.</p><p><strong>Reason 6 — Frequent refreshes of the key share</strong> — With Multi-Sig, the keys stay static and hence almost call for a breach. With MPC, key shares are random and refresh every few minutes or after each operation. Such a refreshing mechanism is an additional layer of security, ensuring that there is no single point of failure.</p><p><strong>Reason 7 — Privacy — </strong>In m-of-n multi-sig transactions, the policy — of who is “m” and who is “n” — is exposed on the blockchain. Because MPC involves keeping separate key shares but signing with one coherent signature, the signatories’ identities remain safe and out of the public’s view. <em>(Thank you to astute reader </em><a href="https://medium.com/u/366ee75f554"><em>Omer Shlomovits</em></a><em> for adding this to our list.)</em></p><p>To summarize, even though Multi-Sig has become the more known technique to protect blockchain transactions, it is worthwhile diving into the advantages of MPC and only then deciding which is your preferred key protection strategy.</p><p><a href="http://bit.ly/2QzwO1M">Learn more about Unbound Crypto Asset Security Platform</a></p><p><a href="#_ednref1">[i]</a> ‘Chekhov’s Gun’ is a concept that describes how every element of a story should contribute to the whole. It comes from Anton Chekhov’s famous book writing advice: ‘If in the first act you have hung a pistol on the wall, then in the following one it should be fired. Otherwise don’t put it there.’</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56d80204ddbd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enterprises are Embracing Blockchain — Supply Chain Management is on the Front Line]]></title>
            <link>https://medium.com/@rebecca.aspler/gathering-the-weekly-blockchain-news-877255edd37d?source=rss-14724730c1de------2</link>
            <guid isPermaLink="false">https://medium.com/p/877255edd37d</guid>
            <category><![CDATA[walmart]]></category>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[enterprise-technology]]></category>
            <category><![CDATA[supply-chain-management]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Rebecca Aspler]]></dc:creator>
            <pubDate>Fri, 26 Oct 2018 12:41:03 GMT</pubDate>
            <atom:updated>2018-10-28T06:06:15.892Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VsDppJ69xQRlBiBGui9HIw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/QqerMOz6DnE?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Logan Stephens</a> on <a href="https://unsplash.com/search/photos/supply-chain?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Looking at the various publications of this week, it is easy to see the increasing amount of enterprise blockchain initiatives that are moving on from the concept or POC phase onto final testing stages. If names such as IBM, Oracle, SAP, Walmart etc. are starting to realize the benefits of Blockchain, the revolution is indeed a successful one.</p><p>One might argue that there are better technological alternatives to blockchain for these enterprise organizations; for example, distributed databases, but the supply chain market is so fragmented and by essence, any shipment crosses at least 3 owners, that blockchain here indeed is the best thing that could happen to this market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*LBVzO9c02BwwQvKm6Obkxg.gif" /><figcaption>Image Credit: <a href="http://www.iibmindialms.com/library/management-basic-subjects/retail-management/supply-chain-management-logistics/">http://www.iibmindialms.com/library/management-basic-subjects/retail-management/supply-chain-management-logistics/</a></figcaption></figure><p>Want to look at the proof that is in the pudding? Here are some of these initiatives:</p><p><a href="https://www.coindesk.com/abn-amro-samsung-sds-partner-for-blockchain-trade-pilot/"><strong>ABN AMRO, Samsung SDS Partner for Blockchain Trade Pilot</strong><br></a>The pain is real and blockchain is the only alternative for a consortium of companies with no one fully owning the data. “Using a blockchain system, the partners ultimately intend to move away from the current paper documentation surrounding international container shipments, including payments and administration.”</p><p>— — — — — — — -</p><p><a href="https://cointelegraph.com/news/oracle-releases-suite-of-blockchain-based-software-for-supply-chain-managemen"><strong>Oracle has accelerated their transition from a software vendor to a SaaS provider by way of its Oracle Blockchain Cloud Service.</strong></a></p><p>It’s not surprising that Oracle is leveraging their experience with enterprise applications in their initial forays. “This blockchain platform will give [customers] a platform to extend their services beyond their enterprise bundle, which means they can extend them outside to their business partners, advantage customers and so on.”</p><p>— — — — — — -</p><p><a href="https://www.verdict.co.uk/your-food-chain-on-blockchain-a-shakeup-is-coming/"><strong>From tracking supply chains to tracking food chains.</strong></a></p><p>The inherent immutability of blockchain technologies lends itself to these applications.</p><p>“Based on its ability to provide enhanced visibility into the contracts and connections that make-up complex food supply chains, blockchain can help producers and retailers guarantee the originality and quality of produce; can help to combat fraud and illegality within the food chain; and can facilitate the tracking and recall of defective or contaminated goods.”</p><p>— — — — — — —</p><p><a href="https://cointelegraph.com/news/ibms-blockchain-patents-from-food-tracking-and-shipping-to-iot-and-security-solutions"><strong>Not to be left out, Big Blue has begun leveraging five years of blockchain research to provide a range of industries with targeted blockchain-based solutions.</strong></a></p><p>Clearly, the industry has come to appreciate the value of, and how blockchain technologies can enable unfettered access to their operational data. “The way forward is decentralized as opposed to a supplier getting into a centralized database and putting data in there and the central authority owning the data. In this blockchain ecosystem, if you get into it and give data, it is your data, you own it.”</p><p><a href="https://cryptobriefing.com/walmart-blockchain-improve-food-safety/"><strong>IBM blockchain solutions are already being leveraged by Walmart.</strong></a></p><p>“Walmart announced that<a href="https://news.walmart.com/2018/09/24/in-wake-of-romaine-e-coli-scare-walmart-deploys-blockchain-to-track-leafy-greens"> all suppliers</a> of fresh, leafy greens will be required to install IBM enterprise blockchain and give its North American food supply chain end-to-end traceability. Given its leadership position as the biggest company in the Fortune 100, the new requirement is expected to be a game changer in the $1.5 trillion U.S. food industry.”</p><p>— — — — — — — — —</p><p><strong>Just for laughs:</strong></p><p><a href="https://www.theonion.com/the-onion-s-guide-to-blockchain-technology-1829819640"><em>The Onion</em> answers common questions about blockchain technology.</a></p><p><a href="https://www.salon.com/2018/10/22/some-folks-believe-blockchain-will-save-the-universe-inside-alex-winters-trust-machine/">Bonus: Bill &amp; Blockhain’s Excellent Adventure</a></p><p>Co-written by Rebecca Aspler and Allan Konar</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=877255edd37d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>