<?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 Matt Cutler on Medium]]></title>
        <description><![CDATA[Stories by Matt Cutler on Medium]]></description>
        <link>https://medium.com/@mcutler?source=rss-36a9da84bd67------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QtTFKLGefoxNskkdVAl0hA.jpeg</url>
            <title>Stories by Matt Cutler on Medium</title>
            <link>https://medium.com/@mcutler?source=rss-36a9da84bd67------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 15 Nov 2026 23:58:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mcutler/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[Evidence of Mempool Manipulation on Black Thursday: Hammerbots, Mempool Compression, and…]]></title>
            <link>https://medium.com/hackernoon/evidence-of-mempool-manipulation-on-black-thursday-hammerbots-mempool-compression-and-61c01a765e15?source=rss-36a9da84bd67------2</link>
            <guid isPermaLink="false">https://medium.com/p/61c01a765e15</guid>
            <category><![CDATA[blocknative]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[makerdao]]></category>
            <category><![CDATA[mempool]]></category>
            <dc:creator><![CDATA[Matt Cutler]]></dc:creator>
            <pubDate>Wed, 22 Jul 2020 20:23:37 GMT</pubDate>
            <atom:updated>2020-07-22T20:26:28.589Z</atom:updated>
            <content:encoded><![CDATA[<h3>Evidence of Mempool Manipulation on Black Thursday: Hammerbots, Mempool Compression, and Spontaneous Stuck Transactions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*exaenX4oszdHUH0U43PlpA.png" /></figure><h3>Blocknative has uncovered evidence that the MakerDAO liquidations on <a href="https://www.coindesk.com/ether-suffers-record-setting-33-drop-amid-global-market-turmoil">March 12 and 13 </a>were an engineered event . This evidence is derived from the <a href="https://blog.blocknative.com/blog/mempool-intro">mempool</a>, the pre-chain area miners use to create blocks. The mempool is an often overlooked — and commonly under-appreciated — aspect of the Ethereum ecosystem .</h3><p>As mempool specialists,<a href="https://www.blocknative.com/"> Blocknative</a> operates a global network of Geth and Parity (OpenEthereum) nodes in a variety of configurations. This infrastructure powers <a href="https://docs.blocknative.com/webhook-api">our real-time transaction monitoring services</a> so that we can capture, normalize, and archive the otherwise ephemeral state changes of the mempool. Blocknative captured over 30 million rows of data over the course of Black Thursday, enabling an open-ended investigation that has so far uncovered several ‘vulnerabilities’ that appear to have been exploited.</p><p>While much has been written about the outcomes of Black Thursday, in this post we will publicly explore data from Blocknative’s Mempool Archive for the first time, bringing both new data and theories to the process. We are also making our underlying forensic mempool data set for this time period available to the ecosystem for others to review (see below).</p><p><em>If you are a security researcher who would like to learn more about our findings, or to explore other potential mempool anomalies, </em><a href="https://www.blocknative.com/request-a-demo"><em>please get in touch</em></a><em>.</em></p><h3>Summary</h3><p>Blocknative’s forensic mempool investigation surfaced three major contributing mempool factors to the events on March 12 and 13:</p><ol><li><strong>Stuck Transactions </strong>— mempool congestion significantly increased stuck transaction rates, effectively blocking subsequent transactions from the same address.</li><li><strong>Mempool ‘Compression’ </strong>— a dramatic reduction in the marketable portion of the mempool (that is, transactions with sufficient gas to be considered by miners), which can bias gas price estimates.</li><li><strong>‘ Hammerbots’ </strong>— Automated transaction systems that magnified congestion, and hence compounded mempool compression.</li></ol><p><strong>We are publishing this analysis and the associated data set in efforts to raise awareness of the dynamic transaction risks that can rapidly emerge during periods of Blockchain network congestion</strong>.</p><h3>Context: Black Thursday Overview</h3><p>On March 12, 2020, the crypto markets saw one of their biggest sell-offs in history, with the price of ETH falling 43% — and BTC falling 39% — in a matter of hours. As prices fell, a negative feedback loop emerged that reduced liquidity and forced liquidations from various DeFi contracts. This downward pressure created real challenges for every entity attempting to transact on the network during this period .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*PxKuLb_a_wUlgc0V.png" /><figcaption><em>Hourly weighted average ETH prices from March 12 through March 13, 2020 UTC. Source: cointelegraph.com.</em></figcaption></figure><p>The rapid price change caused sustained congestion in the Ethereum mempool, as automated transaction systems, such as trading bots, programmatically reacted to the volatility .</p><p>One negative consequence of this congestion were ‘zero bid auctions’ on liquidated <a href="https://defipulse.com/blog/what-is-a-cdp/">MakerDAO CDPs</a>. Of the 3,994 liquidation auctions associated with Black Thursday, 1,462 or 36.6% were won by zero bids. Over a roughly 12 hour period, $8.32 million in aggregated locked CDP value was lost to these zero bid auctions. More on this below and via MakerDAO’s original <a href="https://blog.makerdao.com/the-market-collapse-of-march-12-2020-how-it-impacted-makerdao/">The Market Collapse of March 12–13, 2020: How It Impacted MakerDAO</a> post.</p><h3>1. Stuck Transactions Driven By Mempool Congestion</h3><p>The rapid price change in ETH on March 12 created congestion in the mempool. This was exacerbated by price-triggered bot activity .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*lWUR8ej-eYWDOahE.png" /><figcaption><em>Hourly count of new pending transactions arriving into the mempool versus confirmed transaction count.</em></figcaption></figure><p>The result was a surge of transactions propagating through the network which forced nodes with default mempool configurations to actively protect their system resources by:</p><ol><li>Evicting, or dropping, many valid transactions.</li><li>Rejecting, or ignoring, many valid transactions.</li></ol><p>Mempools generally evict the transactions with the lowest associated fees. And although these transactions are not truly ‘lost’ across the entire network, evicted transactions may be significantly delayed until network conditions normalize.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*Fj08eP3TeNXc3XT1.png" /><figcaption><em>Hourly count of evicted, or dropped, transactions along with new stuck (not processable) transactions arriving for March 11, 2020 through March 14, 2020.</em></figcaption></figure><p>Critically, evictions have a side effect of increasing the likelihood of stuck transactions.</p><p><strong>When a transaction is evicted, the node does not remember any details about the transaction</strong>, such as the sending address <em>or the transaction nonce</em>. Therefore, when a new transaction arrives with the next nonce, the node may detect a nonce gap and will be unable to process the new transaction. Impacted transactions are then placed in the unprocessable Queued portion of the node’s mempool<em>.</em> <strong>These transactions become stuck regardless of their associated transaction fees (that is, gas prices).</strong></p><p><em>[For more on this, please see our prior post covering transaction ordering: </em><a href="https://blog.blocknative.com/blog/mempool-nodes"><em>A Note On Nodes: Your Gateway To The Mempool</em></a><em>.]</em></p><p>Meanwhile, network congestion caused rapid increases in the minimum gas price needed to be admitted to a mempool, so the original transactions were now rejected as underpriced. And since the previously evicted transactions were unable to get back into the mempool, they could not span the transaction nonce gap. In fact, some node implementations actively ignore these rejected transactions for a while in efforts to prevent spamming over the peer-to-peer network. The nonce gap effectively locked addresses out of completing new transactions.</p><p>Stuck transactions were more likely to impact addresses that issue many new transactions, including automated trading systems, payment networks, and possibly even exchanges. These systems attempted to course correct, often compounding congestion as more and more transactions are delayed.</p><blockquote><strong><em>The only solution? You must first proactively detect when one of your transactions might be stuck.</em></strong><em> This can be challenging, as your transaction may only be stuck on some — but not all — nodes on the network. Then, you must identify the first missing transaction in the nonce gap and immediately </em><a href="https://blog.blocknative.com/blog/speed-up-transactions"><em>speed up</em></a><em> that transaction with a marketable gas price. Finally, you must continue to monitor the original stuck transaction to ensure that it has been moved from the Queued to the Pending portion of the mempool and has successfully proceeded to finalization. If your transaction remains stuck, repeat the process above until you can confirm that all transactions in the nonce gap have been successfully resolved. And yes, this is one of the many reasons why we built and operate our </em><a href="https://docs.blocknative.com/webhook-api"><em>Notify API</em></a><em>.</em></blockquote><h3>2. Compressing the Marketable Portion of the Mempool</h3><p>The increase in network congestion — and the resulting increase in stuck transactions — caused the marketable portion of the mempool to shrink.<strong> We call this ‘mempool compression’.</strong></p><p>Miners are incentivized to maximize revenue through block reward and gas utilization at the highest price. Mining operations make decisions on which block templates — that is, candidate blocks — to mine based on the offered gas prices of transactions in the mempool.</p><p>Due to congestion, several behaviors contributed to compressing the mempool so that a much smaller portion remained relevant to miners:</p><ol><li><strong>Exhausted resources: </strong>Depending on node implementation, the dramatic increase in stuck transactions consumed substantial mempool resources. This in turn reduced available node resources for processing valid pending transactions.</li><li><strong>Escalating gas price: </strong>The falling ETH price triggered many ‘high urgency’ transactions that were structured to be confirmed before the value of ETH fell even lower. This drove both individual users and automated bots to rapidly escalate gas prices. Since not all participants were paying close attention to the congestion, the aggregate profile of pending mempool transactions included an unusually large number of underpriced — and hence unmarketable — entries.</li><li><strong>Insufficiently responsive pricing algorithms</strong>: The gas price distribution of pending transactions in the mempool, and of those confirmed in recently mined blocks, could distort gas price Oracle calculations. This effectively underpriced gas for broad swaths of new transactions, further exacerbating pending transaction gas price disparities.</li></ol><p>As mempool congestion rose, the gas price required to be mined and get on-chain climbed as expected. However, since the rapid rise was not tracked equally by all participants — including, critically, some gas price Oracles — <strong>the average price to get mined began to diverge from the average price of transactions entering the mempool</strong>. And typical fee bumping was insufficient to keep up with the rate of price increases.</p><p>On March 12, our data platform detected significant separation of transaction fee pricing. Instead of the expected lag in offered gas price between some portion of the mempool and the marketable transactions — as seen with similar gas price changes on March 13 — <strong>pricing on March 12 between mined and un-mined transactions effectively bifurcated.</strong></p><p>The typical behavior we observe is that unmarketable transactions are adjusted to become marketable, usually with a simple upward fee adjustment. However, on March 12 this was not the case. <strong>Instead, significant mempool resources were consumed by underpriced transactions resubmitted at nearly identical prices.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*DpLSDfQ6-9GgFlSj.png" /><figcaption><em>Box plot of gas prices each hour of March 12–13, 2020. For each hour, the box is bounded by the 1st and 3rd quartile values, a line inside shows the median, and the whiskers indicate minimum and maximum. Outliers are ignored (1.5 IQR).</em></figcaption></figure><p>Does this reflect organic behavior? Or might these underpriced transactions have been intended to flood the mempool? And if so, why?</p><h3>3. Hammerbot Transactions Engineered Mempool Distortion</h3><p>Our forensic mempool archive data indicates that bots successfully increased congestion and distorted the gas price distribution in the mempool without any corresponding increase in transaction fees.</p><p>This had the net effect of increasing the stuck transaction rate and skewing gas price Oracles. This resulted in anomalous mempool conditions, which would ultimately favor certain transactions — namely, increasing the probability that a liquidated CDP position could be won at auction with a zero bid.</p><p>The bots hammered the mempool with transactions that were never intended to be finalized.<strong> These ‘Hammerbots’ consumed mempool resources by issuing extremely high rates of replacement transactions without any corresponding increase in gas.</strong> <em>But how can transactions be replaced without the required minimum 10% fee increase designed to prevent precisely this sort of activity?</em></p><p>The simple answer: node amnesia caused by abnormally high rates of transaction eviction (see above).</p><p>The Hammerbots waited for — or simply anticipated — the eviction of their own transactions from the mempool and then immediately sent new replacement transactions with identical, or even reduced, underpriced gas fees. Having ‘forgotten’ the previously evicted transaction, nodes dutifully accepted the replacements as valid new transactions. Of course, this had the effect of further compounding congestion.</p><p>The <a href="https://bloxy.info/tx/0x5b00c13020b82c9e8a098393564feca976dbbd2e8da6c54263f6e492be56fbfb">Hammerbot transaction payloads themselves</a> appear to be malformed in a distinctly ‘automated’ fashion, with each replacement including slightly modified contract inputs. Thus, each Hammerbot transaction had a unique hash and therefore could bypass the peer-to-peer network protocol spam filtering protections in each node.</p><p>As the pink overlays in the diagrams below highlight, starting at exactly 09:00 UTC on March 12, our mempool data platform detected a rapid increase in pending transactions that would never be mined . The rate of these then doubled approximately 35 minutes later, only to then drop off into a linear escalation pattern at approximately 10:00 UTC .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/0*jrNONw5bPMrKGCZW.png" /><figcaption><em>Per minute count of transactions entering the mempool from 08:00 UTC to 10:00 UTC on March 12. The blue line counts transactions that eventually finalized on-chain. The orange line counts transactions that are never finalized on chain.</em></figcaption></figure><p>Given that there appeared to be no intention of these transactions getting on-chain, the gas prices for these never-mined Hammerbot transactions remained abnormally low: almost always 5 Gwei when the market required ~30 Gwei or more. Hammerbot transactions efficiently consumed mempool resources without the normal ramping of gas price typical of speedup transactions used by arbitrage bots.</p><p>When viewed in aggregate, even though the volume of transactions entering the mempool increased dramatically, the gas price of a significant portion of the mempool collapsed to an artificially low value .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*yB1QKuWv_XSu_n6f.png" /><figcaption><em>Box plot of gas prices each minute from 08:00 UTC to 10:00 UTC on March 12. The blue line counts transactions that eventually finalized on-chain. The orange line counts transactions that are never finalized on chain.</em></figcaption></figure><p>Exploring a sample Hammerbot transaction, in this case nonce 3070, is illustrative. Here is the final transaction hash:</p><p><a href="https://etherscan.io/tx/0x5b00c13020b82c9e8a098393564feca976dbbd2e8da6c54263f6e492be56fbfb">0x5b00c13020b82c9e8a098393564feca976dbbd2e8da6c54263f6e492be56fbfb</a></p><p>Looking up this transaction in your favorite block explorer will not reveal much insight beyond its final confirmation on-chain. On the surface, this transaction appears unremarkable. But Blocknative’s mempool data platform detected 418 unique replacement transactions preceding this nonce. This occurred in under an hour, with a replacement transaction every 6.86 seconds on average, with a gap of less than 0.1 seconds between some replacements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*eVcJoGhhUnIOqcS4.png" /><figcaption><em>Same nonce unique transaction count per minute across 4 nonces for address 0x5cf2fa4e0c84e71fd2e4fa86d2fa64b7a50a6fc0 that started at 09:00 UTC.</em></figcaption></figure><p>Most of these replacement transactions used an identical gas price, with the Hammerbot relying on mempool eviction mechanics to successfully enter each node’s mempool as a ‘new’ transaction. Only the last replacement required a higher gas price in order to be marketable and therefore become finalized in a mined block.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*KfuqASC5a31o74r0.png" /><figcaption><em>Same nonce average gas price each minute across 4 nonces for address 0x5cf2fa4e0c84e71fd2e4fa86d2fa64b7a50a6fc0 that started at 09:00 UTC.</em></figcaption></figure><p>These patterns make it difficult to dismiss Hammerbot transaction behavior as accidental or unintentional. In fact, our systems recorded more than 20 unique candidate Hammerbot addresses active during the 60 second period starting at 9:05 UTC.</p><h3>The Effect of Mempool Vulnerabilities on MakerDAO</h3><p>MakerDAO’s <a href="https://blog.makerdao.com/say-goodbye-to-cdps-and-hello-to-maker-vaults/">collateralized debt positions</a> (CDPs) allow anyone to borrow DAI by locking ETH into a smart contract. Your locked ETH acts as collateral for your DAI debt. Since ETH is a volatile asset, while DAI seeks to maintain a price of exactly $1.00, the amount of collateral required to maintain an open CDP position constantly changes.</p><p>When the price of ETH collapsed on March 12, a large number of CDPs immediately became undercollateralized and eligible for <a href="https://community-development.makerdao.com/makerdao-scd-faqs/scd-faqs/liquidation">forcible liquidation</a>. MakerDAO and the Ethereum ecosystem are incentivized to operate various <a href="https://developer.makerdao.com/keepers/">Keeper bots</a> in order to ensure a competitive marketplace for liquidated CDP positions. Such liquidations occur in <a href="https://github.com/makerdao/auction-keeper">auctions</a>.</p><p>Any Keeper can participate in an auction with an <em>on-chain</em> bid, and any other Keeper can submit a higher counter-bid <em>on-chain</em> within 10 minutes. When a new bid is received, a fresh 10 minute bid window starts. If no higher bids are received within that 10 minute window, the auction is closed, and the last bid wins. <em>[Note: In the aftermath of Black Thursday, MakerDAO increased the auction period from 10 minutes to 6 hours.]</em></p><p><strong>However, when miner nodes were dropping transactions at an unusually high rate due to network congestion and mempool compression, many Keeper transactions were adversely impacted by stuck transactions and thus were delayed in successfully placing CDP liquidation auction counter-bids on-chain.</strong> The end result was that Keepers were unable to reliably compete in the time-windowed auctions initiated by a zero bid, even though Keeper bots correctly detected the zero bid auction start and responded with a much higher bid.</p><p>As a result of the congestion and fee confusion, Keepers failed to appropriately interpret the rapid gas price increases and Keeper transactions were thus evicted from miner mempools. This created the conditions for transaction nonce gaps to emerge in default configuration miner nodes. <strong>All subsequent bids for additional auctions by the Keeper bots then became stuck, essentially blocking the Keepers from participating in the 10-minute auction window and allowing the zero bid transactions to win out.</strong></p><p>Here is an example sequence for auction #1866 illustrating the above behavior:</p><ol><li>A ‘zero bid bot’ initiated the auction with a zero bid submitted at 15:59:50 UTC with a gas price of 200 Gwei. This transaction was confirmed and successfully went on-chain 26 seconds later. And the 10 minute bid countdown began.</li><li>A ‘good faith Keeper bot’ submitted a counter bid transaction at 16:08:01 with a gas price of 450 Gwei. This transaction was within the 10 minute bid window — 8 minutes and 11 seconds — and had 2.5x the gas price of the original zero bid transaction. If confirmed within the next one minute and 49 seconds, Auction #1866 would have proceeded as expected. However, this bid was effectively blocked by a nonce gap caused by an earlier evicted bid from the good faith Keeper bot.</li><li>The good faith Keeper bot sent a follow-up counter-bid with a 4,500 Gwei (!!) gas price at 16:15:31. The 10x gas price increase had no effect because the sending address remained stuck by the nonce gap created by the earlier evicted transaction. Furthermore, this counter-bid was sent outside the 10 minute auction window and would have failed once it became unstuck.</li></ol><p>This pattern was repeated probabilistically throughout the day, resulting in $8.32 million in aggregated CDP holder losses. It is worth noting that much of the Hammerbot activity appears to have occurred earlier in the day, thus creating the congested conditions that later interfered with Keeper bot transactions.</p><p>The rapid increase in gas price, and the distortion of gas price estimation due to mempool compression, also negatively impacted other price Oracles. This caused further confusion with pricing and likely delayed re-collateralization attempts by CDP holders at risk of liquidation.</p><h3>Summary and In-Process Findings</h3><p>In summary, our forensic mempool investigation into the events of Black Thursday indicates the following:</p><ol><li>Multiple Hammerbots saturated mining operation mempools. This increased and accelerated Ethereum network congestion.</li><li>Sending many same-gas-price replacement transactions created significant overhead in both the peer-to-peer gossip layer and the nodes themselves.</li><li>This impeded normal transaction propagation, causing a large number of transactions to be evicted or rejected from miner mempools.</li><li>This in turn led to an increased likelihood of creating a nonce gap and the associated stuck transactions. This also skewed gas price calculations.</li><li>While automated trading systems are often designed to programmatically increase the gas price of transactions, many such trading systems do not handle nonce gaps well — if at all.</li></ol><p>The above are in-process findings. Our data set may yet reveal additional evidence and/or new findings that support or undermine our conclusions.</p><p>To accelerate the discovery process, we are now making a sample of our Mempool Archive data for those two days available to the community (see below). We hope this catalyzes further exploration into the role of the mempool in the events of Black Thursday and in other Ethereum network anomalies .</p><h3>Recommendations: Protect Yourself and Your Users</h3><p>The mempool is a critical — yet ephemeral and often overlooked — element of the blockchain ecosystem. As such, mempools present many ‘unknown unknowns’ to builders and users alike.</p><p>At this stage, we do not know how often techniques like these are exploited in the wild — only that they appear to be actively exploited. And we do not know how many related exploits exist — only that sophisticated exploits appear to have been demonstrated to be effective in the real-world.</p><p><strong>As a result, we recommend that all exchanges, protocols, wallet providers, and traders:</strong></p><ol><li><strong>Constantly monitor mempool conditions</strong>, with a focus on 1) detecting when mempool congestion begins to build and 2) changes in transaction eviction and rejection rates.</li><li><strong>Understand the nuances of transaction nonce ordering</strong>. And how even properly constructed transactions can become stuck in portions of the network.</li><li><strong>Proactively watch for stuck transactions</strong>. And know which prior transaction(s) must be sped up in order to unblock a given address.</li><li><strong>Calculate gas prices based on the marketable portion of the mempool</strong>. And be knowledgeable about the algorithms used by the gas price Oracles you rely on.</li><li><strong>Do not assume predictable pending transaction behavior during periods of high congestion</strong>. Instead, monitor each and every transaction for the factors described here, including insufficient gas, dropped transactions, stuck transactions, front-running, and more.</li></ol><p>These issues are exceptionally challenging, time-consuming, and expensive to address on your own. Blocknative’s global data platform has been designed expressly to capture and normalize decentralized mempools — addressing each of the above recommendations along the way. <strong>Our infrastructure and APIs provide real-time mempool monitoring to keep your transactions flowing reliably, resiliently, and predictably.</strong></p><p>If you are handling real value and want to start protecting yourself and your stakeholders from mempool manipulations like those described here, please <a href="https://www.blocknative.com/request-a-demo">contact us</a>.</p><h3>Dive into the Forensic Mempool Archive</h3><p>To help raise visibility into mempool mechanics in the real world, we are now publishing a sample of our forensic mempool archive describing Black Thursday. We invite the community to explore this data set and to collaboratively share and publish your findings.</p><p>You can download the data from our public S3 buckets here:</p><p><a href="https://bnc-mainnet-2020-03-12.s3.amazonaws.com/readme.txt">https://bnc-mainnet-2020-03-12.s3.amazonaws.com/readme.txt</a></p><p><a href="https://bnc-mainnet-2020-03-13.s3.amazonaws.com/readme.txt">https://bnc-mainnet-2020-03-13.s3.amazonaws.com/readme.txt</a></p><p>Each day has its own bucket. The data within each day is further divided into hourly files. See the readme.txt files for details on formats and interpretation. If you have questions about the data, please join the <a href="https://discord.gg/KZaBVME">Blocknative Discord</a> for support.</p><p><strong>A special thanks to the many members of the ecosystem who reviewed prior drafts of this post</strong>, including <a href="https://twitter.com/starsoup7"><strong>Sarah Baker-Mills</strong></a><strong>, </strong><a href="https://twitter.com/dberenzon"><strong>Dmitriy Berenzon</strong></a><strong>, </strong><a href="https://twitter.com/cremedelacrypto?lang=en"><strong>Spencer Bogart</strong></a><strong>, </strong><a href="https://twitter.com/nic__carter"><strong>Nic Carter</strong></a><strong>, </strong><a href="https://twitter.com/hsinjuchuang"><strong>Hsin-Ju Chuang</strong></a><strong>, </strong><a href="https://twitter.com/tomusdrw?lang=en"><strong>Tomasz Drwięga</strong></a><strong>,</strong><a href="https://twitter.com/awaygray"><strong>Andy Gray</strong></a><strong>, </strong><a href="http://twitter.com/hudsonjameson"><strong>Hudson Jameson</strong></a><strong>, </strong><a href="https://twitter.com/sixletterman"><strong>Jon Kol</strong></a><strong>, </strong><a href="https://twitter.com/cjliu49?lang=en"><strong>Calvin Liu</strong></a><strong>, </strong><a href="http://twitter.com/jmart_199"><strong>Justin Mart</strong></a><strong>, </strong><a href="https://twitter.com/gavinmcdermott"><strong>Gavin McDermott</strong></a><strong>, </strong><a href="https://twitter.com/tayvano_"><strong>Taylor Monahan</strong></a><strong>, </strong><a href="https://twitter.com/mavensights"><strong>Andra Nicolau</strong></a><strong>, </strong><a href="https://twitter.com/_charlienoyes"><strong>Charlie Noyes</strong></a><strong>, </strong><a href="https://twitter.com/Sim_Pop"><strong>Simona Pop</strong></a><strong>, </strong><a href="https://twitter.com/apruden08"><strong>Alex Pruden</strong></a><strong>, </strong><a href="https://twitter.com/austinrobertsiv"><strong>Austin Roberts</strong></a><strong>, </strong><a href="https://twitter.com/cuysheffield"><strong>Cuy Sheffield</strong></a><strong>, </strong><a href="https://twitter.com/lsukernik"><strong>Larry Sukernik</strong></a><strong>, </strong><a href="https://twitter.com/whinfreychris"><strong>Chris Whinfrey</strong></a><strong>, </strong>and others. We deeply appreciate your feedback, insight, and guidance.</p><p><em>Originally published at </em><a href="https://blog.blocknative.com/blog/mempool-forensics"><em>https://blog.blocknative.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61c01a765e15" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/evidence-of-mempool-manipulation-on-black-thursday-hammerbots-mempool-compression-and-61c01a765e15">Evidence of Mempool Manipulation on Black Thursday: Hammerbots, Mempool Compression, and…</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[Ethereum Speed Up Transactions: How They Work And What They Mean For Dapps]]></title>
            <link>https://medium.com/thecapital/ethereum-speed-up-transactions-how-they-work-and-what-they-mean-for-dapps-6d4ba1068580?source=rss-36a9da84bd67------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d4ba1068580</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Matt Cutler]]></dc:creator>
            <pubDate>Fri, 04 Oct 2019 16:14:12 GMT</pubDate>
            <atom:updated>2019-10-05T03:59:31.398Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dAZsn-lRTKC00NqP5sS6DA.png" /></figure><h4>By <a href="https://medium.com/u/36a9da84bd67">Matt Cutler</a> on ALTCOIN MAGAZINE</h4><p>Recently, we published a post covering <a href="https://blog.blocknative.com/blog/canceled-transactions">Canceled Transactions and How They Break Dapp UX</a>. Based on the positive feedback we received from the community, we are excited to dive into the world of Ethereum Speed Up Transactions — what they are, how they are different than Cancels, and the implications for your Dapp. [We recommend first reviewing our <a href="https://blog.blocknative.com/blog/canceled-transactions">Cancel Post</a>.]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1qN44mkx8K_lMTDPez1-Ow.png" /></figure><h4><strong>What Are Speed Up Transactions?</strong></h4><p>Speed Up transactions are virtually identical to Cancel transactions — with one critical difference. Specifically:</p><ul><li>On Ethereum, a Speed Up transaction is an attempt to overwrite a currently pending transaction with a new transaction.</li><li>Just like Cancels, Speed Ups are a convention and not a standard.</li></ul><p>The big difference?</p><blockquote>Whereas a Cancel transaction is an attempt to overwrite a pending transaction with a <em>zero value</em> replacement, a Speed Up is an attempt to accelerate a pending transaction.</blockquote><p>In other words, you still want the transaction to happen; you just want it to happen <em>faster</em>. Therefore, a typical Speed Up transaction will have:</p><ol><li>An identical nonce,</li><li>From the same Wallet address,</li><li>At least a 10% higher gas fee, and</li><li><strong>The identical value</strong>, plus</li><li>Gets signed-and-successfully-submitted before the original transaction is confirmed.</li></ol><p>You might notice that step 4 is the only difference between a Cancel and a Speed Up. They both work on the identical principle: since miners are incentivized to prioritize transactions with more gas, the identical nonce Speed Up transaction <em>should</em> be confirmed before the original transaction — even though it entered the mempool later. In other words, Speed Up transactions are kind of like probabilistic <a href="https://en.wikipedia.org/wiki/Afterburner">afterburners</a>.</p><h4><strong>How Are Speed Up Transactions Created?</strong></h4><p><a href="https://metamask.io/">MetaMask</a> is the best-known (only?) end-user wallet with <a href="https://metamask.zendesk.com/hc/en-us/articles/360015489251-Slow-and-Stalled-Transactions">an explicit UI to initiate a Speed Up</a>. Other wallets, including <a href="http://mycrypto.com/">MyCrypto</a> and <a href="http://myetherwallet.com/">MyEtherWallet</a>, offer knowledge-base articles that provide instructions for manually constructing and submitting both Speed Up and Cancel transactions. But these are not for faint of heart.</p><p>To issue a Speed Up on MetaMask, click on a currently pending transaction shown in the Queue. This will reveal the transaction details and the Cancel button. Don’t see the Speed Up button? Just wait. It usually shows up after a few seconds. See below for this behavior in action:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/0*XbU_jURWmBQX1ARG.gif" /></figure><p>The Speed Up user experience in MetaMask 7.2.1.</p><p>As you can see, Speed Ups are an advanced capability and meant to be used by sophisticated users. You might expect them to be relatively uncommon.</p><blockquote>However, we find that — during periods of network congestion — <strong>more than 10% of the entire mempool consists of Speed Ups and Cancels.</strong> 😲</blockquote><p>Where do they come from?</p><h4><strong>Which User Segment(s) Generate All Of These Speed Ups?</strong></h4><p>We’ve learned from experienced builders (more precisely, our <a href="https://blog.blocknative.com/blog/gu-cards">customers</a> and <a href="https://blog.blocknative.com/blog/pillar-wallet">partners</a>) that frequent use of Speed Ups and Cancels is correlated with the transaction volume. In other words, whales and traders. As in, the most active — <em>and presumably profitable</em> — users in the ecosystem.</p><p>This is not that much of a surprise. The more transactions someone is conducting, the more susceptible they are to changing gas prices. This is not just the Gas fees themselves, but also the losses that can accrue from delayed transaction confirmations. In fact, sophisticated traders have built custom bots to automatically manage gas in efforts to ensure that all of their trades are quickly executed.</p><h4><strong>How Are Speed Ups And Cancels Different?</strong></h4><p>Speed Ups and Cancels are similar in that they originate from the wallet and use the same nonce as the transaction that was originally sent. Aside from that, they are ‘normal’ Ethereum transactions that have been crafted to achieve a specific outcome. Which is where things can start to get fun:</p><ul><li>Yes, you can Speed Up a Cancel.</li><li>Yes, you can Speed Up a Speed Up.</li><li>Yes, you can Cancel a Speed Up.</li><li>And yes, you can even Cancel a Cancel. 🤔</li></ul><p>Go ahead. Try it.</p><p>Just remember that Speed Ups and Cancels are purely probabilistic. <em>They represent an attempt and not a guarantee</em>. The original transaction can get confirmed despite your best efforts to replace it. However, the consequences of this are wildly different depending on the context:</p><ul><li>If your Speed Up fails to replace the original transaction, you save a little gas. And that’s it. Because you wanted the original transaction to confirm quickly. Outcome: No problem!</li><li>However, if your Cancel fails to replace the original transaction… well, the original transaction is confirmed, and of course, all of the associated value moves with it. Which is precisely what you were trying to avoid by attempting to Cancel in the first place. Outcome: Ouch.</li></ul><p>So the next time your transaction is stuck, and you are not sure what to do, issue a Speed Up. Easy enough. For the User? Sure. For the Dapp? Not so much.</p><h4><strong>How Do Speed Ups Impact Dapp UX?</strong></h4><p>Speed Ups and Cancels both originate at the wallet. They both reuse a nonce. But because they change constituent elements of the transaction — the gas fee specifically — these replacements transactions will have <em>new transaction hashes.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/485/1*2GzSXEVAiB4p0qj3hm8IWg.png" /><figcaption>How Dapps Get Confused by Speed Up and Cancel Transactions</figcaption></figure><p>Since Dapps are out-of-the-loop when a Speed Up or Cancel gets created, the Dapp has no way to connect-the-dots between the two transaction hashes. This tends to break the Dapp UX because the new transaction hash is not picked up by the UI. For the end-user, that usually means the Dapp will show their transaction as permanently. And the new transaction hash, once it is Confirmed, will not be displayed on the Dapp.</p><p>😑</p><p>As transactions on Ethereum increase, we can expect Speed Ups will become more common. So it is important for Dapps to build a robust front-end that can handle these situations cleanly.</p><h4><strong>Blocknative Can Help!</strong></h4><p>Blocknative operates a robust Ethereum transaction monitoring platform that provides real-time notifications via our lightweight <a href="https://blog.blocknative.com/blog/notify-api">Notify API</a>. Built for Dapp developers and wallet providers, Notify emits API events describing every state change for every relevant transaction, including:</p><ul><li>New pending transactions detected.</li><li>Pending transaction confirmed.</li><li>Pending transaction failed.</li><li>Pending transaction <a href="https://blog.blocknative.com/blog/canceled-transactions">Canceled</a>.</li><li>Pending transaction Sped Up.</li><li>And much more.</li></ul><p>To accomplish this, we run a global node monitoring infrastructure that is high scale, high availability, and low latency.</p><blockquote>We built Notify to help you connect the dots for your users. So you can focus on delivering a great experience and your users can transact with confidence.</blockquote><p>Providing your users real-time updates on the full spectrum of blockchain transactions increases engagement, improves retention, and drives growth.</p><p>To learn more, <a href="https://www.blocknative.com/request-a-demo">click here</a> to schedule a live demo.</p><p><em>This post was co-authored by </em><a href="https://twitter.com/mcutler"><em>Matt Cutler</em></a><em>, </em><a href="https://twitter.com/aseoconnor"><em>Sean O’Connor</em></a><em>, and </em><a href="https://twitter.com/ChrisMeisl"><em>Chris Meisl</em></a><em>. If you’ve encountered a Dapp that does a great job of handling Speed Up transactions, please let us know.</em></p><p><em>Originally published at </em><a href="https://blog.blocknative.com/blog/speed-up-transactions"><em>https://blog.blocknative.com</em></a><em>.</em></p><p><a href="https://twitter.com/Alt__Magazine">Altcoin Magazine</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><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d4ba1068580" width="1" height="1" alt=""><hr><p><a href="https://medium.com/thecapital/ethereum-speed-up-transactions-how-they-work-and-what-they-mean-for-dapps-6d4ba1068580">Ethereum Speed Up Transactions: How They Work And What They Mean For Dapps</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[Real Blockchain Customers with Real Blockchain Needs Often Means Real (Satisfying) Work]]></title>
            <link>https://medium.com/@mcutler/real-blockchain-customers-with-real-blockchain-needs-often-means-real-satisfying-work-270c659ec8e4?source=rss-36a9da84bd67------2</link>
            <guid isPermaLink="false">https://medium.com/p/270c659ec8e4</guid>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blocknative]]></category>
            <category><![CDATA[pillar-project]]></category>
            <dc:creator><![CDATA[Matt Cutler]]></dc:creator>
            <pubDate>Fri, 27 Sep 2019 23:25:26 GMT</pubDate>
            <atom:updated>2019-09-27T23:25:26.753Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2CD-k5TBFxulBC76" /></figure><p>We recently introduced our <a href="https://preview.hs-sites.com/blog/notify-api">new Notify API for programmable real-time transaction notifications</a>. This new API represents an exciting step forward for Blocknative’s cycle of ideate, build, test, learn, and refine . And one thing I’ve learned in two decades of founding and running startups is that successful organizations are constantly searching for customers to say three magical words:</p><p>This new development was only possible because we worked with a great partner — <a href="https://pillarproject.io/">Pillar Wallet</a> — who said those three magical words. Read on to learn how we identified the opportunity, what it took to build the API, and why it might matter to your blockchain-based business .</p><p><strong>Why a Real-Time Transaction Notification API for Wallets?</strong></p><p>Imagine my excitement after our first call with <a href="https://twitter.com/drewharding?lang=en">Drew Harding</a>, the Chief Product Officer at <a href="https://pillarproject.io/">Pillar</a>. During the call, I ran through an end-to-end demo of our framework for Dapp developers — showcasing at least two dozen unique features… but Drew focused on one feature in particular: <strong>transaction notifications</strong>.</p><p>So when Drew shared that real-time transaction notifications were an area where he thought we could integrate with Pillar Wallet, I realized that this was a great opportunity and that the team had a lot of work to do. Why?</p><ol><li>Integrating with a Wallet is an entirely different process than integrating with a Dapp.</li><li>Because Pillar is a multi-asset wallet, we needed to detect transactions involving ERC-20 and ERC-721 tokens in addition to ETH — with more contracts, such as swaps, to follow.</li><li>As strong proponents of great wallet UX, Pillar needed the ability to notify the user of both outbound <em>and inbound transactions</em>. So we needed to extend our node monitors to track specific addresses in addition to transaction hashes.</li><li>Pillar was already hard at work building their next-generation wallet platform, which involves a transition to a smart contract wallet architecture. So, in addition to their current installed base of non-custodial private-key wallets, we needed to add support for smart contract wallets.</li><li>As part of their next-generation platform, Pillar is also incorporating payment channels via the <a href="http://abridged.io/">Abridged</a> SDK. We needed to add support for state channels in general and payment channels specifically.</li><li>Because Pillar is a native smartphone app, they control the entire UX. So everything above needed to be provided via a lightweight API whereby they let us know what they care about and we emit events describing every state change for every transaction related to everything they care about.</li><li>Because Pillar serves a global user base, our API needs to be highly available. This requires new levels of operational redundancy, which increases technical complexity.</li><li>Due to the inherent vagaries and inconsistencies of the global mempool (another topic we plan to cover in a future post), we needed to ensure that our mempools were configured to accept and retain as many transactions as possible. We also needed to diversify our node peering relationships as well as develop a roadmap for further geographically distributing our node monitors</li><li>And a lot more that’s not worth mentioning here</li></ol><p>See that list? <em>This is the hard part</em>.</p><p>This is also why the best product ideas often require someone from the outside to spot the obvious opportunity. Drew noticed one of our many features and said: “ <strong>We want that</strong>.” We assumed he had no way of knowing that this would cascade into this laundry list of features and infrastructure enhancements.</p><p>But the team certainly did. Which is why we hadn’t seriously considered building this capability. We were too close to the problem. All of that would be too time-consuming to build on a speculative basis. Except this wasn’t speculative. We had a real partner who wanted this functionality.</p><p><strong>The Twist</strong></p><p>After determining that we might have an opportunity to integrate, Drew introduced us to <a href="https://twitter.com/pyvitor?lang=en">Vitor Py</a>, Pillar’s CTO. Early in the conversation, Vitor told us that he and his team had already built a system to handle real-time notifications.</p><p>😳</p><p>We were more than a little surprised.</p><p>But Vitor went on to tell us:</p><blockquote><em>At first glance, this seems like a straightforward problem. But the infrastructure required to capture the data is complex and expensive to operate. And we had multiple engineers involved in building and maintaining it. There aren’t any shortcuts. Doing it reliably, at scale, was becoming a huge distraction to my team.</em></blockquote><p>Based on his experience, Vitor came to appreciate that notifications are too big of a problem to tackle as a side project. Instead, they require the dedicated attention of a focused, full-time development team.</p><p>When we showed Vitor what we had already built, he lit up. He was excited about the prospect of outsourcing this functionality. From there we dove into Pillar’s technical requirements and how they wanted to consume the event stream from our API. Over several weeks our teams collaborated to extend the Blocknative API to meet the needs of Pillar and other Wallets.</p><p><strong>The Solution</strong></p><p>Blocknative now offers our Notify API, a production-ready service built specifically for Wallet providers and sophisticated Dapps who want to deploy real-time blockchain notifications.</p><p>Y ou and your team can benefit from all of the investment we put in to satisfy Pillar’s requirements. We’ve been fortunate to find a partner to help us find this next step in our product development.</p><p>To see our notifications in action, download Pillar’s <a href="https://apps.apple.com/app/apple-store/id1346582238">iOS</a> or <a href="https://play.google.com/store/apps/details?id=com.pillarproject.wallet">Android</a> app and send some Mainnet transactions.</p><p><strong>How to Get Started</strong></p><p>Wallet providers and sophisticated Dapps can now leverage this infrastructure to power real-time notifications. Those who are interested in learning more about Blocknative can visit our <a href="https://www.blocknative.com/wallets">Wallet page</a>.</p><p><em>Originally published at </em><a href="https://blog.blocknative.com/blog/pillar-wallet"><em>https://blog.blocknative.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=270c659ec8e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Everything You Need to Know About Canceled Transactions — and How They Break Dapp UX]]></title>
            <link>https://medium.com/@mcutler/everything-you-need-to-know-about-canceled-transactions-and-how-they-break-dapp-ux-bd202d5712c6?source=rss-36a9da84bd67------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd202d5712c6</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[Matt Cutler]]></dc:creator>
            <pubDate>Thu, 08 Aug 2019 17:37:14 GMT</pubDate>
            <atom:updated>2019-10-05T03:59:50.697Z</atom:updated>
            <content:encoded><![CDATA[<h3>Everything You Need to Know About Canceled Transactions — and How They Break Dapp UX</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2IRgKgVaEdJLSNTPQdT9iw.jpeg" /></figure><p>Since the start of the year, we have conducted more than 30 <a href="https://blog.blocknative.com/blog/dapp-transaction-audit-template">Dapp Transaction Usability Audits</a>. Every Audit involves more than 50 unique quantitative metrics and qualitative evaluations. One surprising finding: we have yet to audit a Dapp that cleanly handles either <em>Canceled </em>or <em>Sped Up transactions</em>. Why?</p><p>Before we dive into the problems Canceled transactions cause and why most Dapps don’t address them, let’s first cover the basics. <em>[Note: This post focuses on Canceled transactions. We’ll cover the ins-and-outs of Sped Up transactions in a future post.]</em></p><h3><strong>What Are Canceled Transactions?</strong></h3><p>On Ethereum, a Cancel transaction is an attempt to overwrite a currently pending transaction with a new transaction. It’s important to note that Canceled transactions are a convention and not a standard. Typically, a Cancel transaction will have:</p><ol><li>An identical nonce,</li><li>From the same Wallet address,</li><li>At least a 10% higher gas fee, but</li><li>Zero value, and</li><li>Gets signed-and-successfully-submitted before the original transaction is confirmed.</li></ol><p>The core of the idea is that, since miners are incentivized to prioritize transactions with more gas, the cancel transaction <em>should</em> be confirmed before the original transaction — even though it entered the mempool later. In other words, Cancel transactions are kind of like probabilistic <a href="https://en.wikipedia.org/wiki/Mulligan_(games)">mulligans</a>.</p><h3><strong>How Do I Cancel A Transaction?</strong></h3><p>Many, but not all, Ethereum wallets can help you cancel a transaction. In the case of <a href="https://metamask.io/">MetaMask</a>, you must first find and click a pending transaction to show the transaction detail and then click the Cancel button. Like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*OFtliyro2yo5Jpa9.gif" /><figcaption>How to Cancel a transaction in MetaMask.</figcaption></figure><p>While the Cancel function might seem somewhat buried, it turns out to be a commonly used feature among more sophisticated and engaged Dapp users. These users make a habit out of carefully monitoring their transactions and proactively managing gas costs.</p><p>Straightforward enough… right? Not so much.</p><p>A critical piece of the puzzle is missing when it comes to Cancel transactions: your Dapp. While a user will engage with your Dapp to start a transaction, any Cancel activity occurs between that user and his or her wallet. Effectively, <em>you and your Dapp are out of the loop.</em></p><h3><strong>How Can I Identify A Cancel Transaction?</strong></h3><p>Can you <a href="https://www.highlightskids.com/games/double-check/check-and-double-check-balloon-museum">spot the key differences</a> in the fourth and fifth transactions in the illustration below?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f_1if72NJhWAph7gqaSMqA.png" /><figcaption>A Canceled Transaction: Illustrated</figcaption></figure><p>While the nonces are the same, the second transaction has:</p><ul><li>More gas.</li><li>Zero value.</li><li>A different timestamp.</li><li><strong>A different transaction hash</strong>.</li></ul><p>The first three are central to what makes a Cancel transaction a cancel. The fourth one, however, is a headache for you and your Dapp.</p><h3><strong>How Do Canceled Transactions Affect Dapp UX?</strong></h3><p>Because the original and the Cancel transaction have different hashes, and the fact that your Dapp was not part of creating the Cancel transaction, your Dapp has no mechanism to connect the dots. This typically results in a transaction that will always show as pending<em>. </em>Here’s an illustrative example captured from a Dapp that we recently audited:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/349/0*hxA0AAiU986zRV0Z.png" /><figcaption>The first transaction was Canceled — and is permanently shown as “Pending”.</figcaption></figure><p>The first transaction was pending on Mainnet but then was canceled and replaced by a new transaction. Because of this, the Dapp displays the status for a transaction that will never confirm nor fail. Instead, the original transaction will show as pending — permanently. Bummer.</p><p>As the Ethereum network grows, Canceled transactions are becoming increasingly common. So Dapps need to build a robust front-end that can handle these situations cleanly.</p><h3><strong>Blocknative can help!</strong></h3><p>We’re not going to leave you hanging. We’re happy to report that the Blocknative API now includes an <a href="https://www.staples.com/Staples-Global-Easy-Button/product_953889">Easy Button</a> to solve the Cancel transaction UX headache. How? Our unique mempool monitoring framework detects Cancel transactions — in real-time. And, based on customer feedback, we recently extended our API to return the original transaction hash along with the Cancel transaction hash.</p><p>The Blocknative API can connect the dots for you and your Dapp. This lets you give your users real-time updates on the full spectrum of blockchain transactions — increasing engagement, improving retention, and driving growth. To learn more, Join our <a href="https://discord.gg/De9sCqD">Discord server</a> to connect with our team.</p><p><em>This post was co-authored by </em><a href="https://twitter.com/aseoconnor"><em>Sean O’Connor</em></a><em>, </em><a href="https://twitter.com/ChrisMeisl"><em>Chris Meisl</em></a><em>, and </em><a href="https://twitter.com/mcutler"><em>Matt Cutler</em></a><em>. If you’ve encountered a Dapp that does a great job of handling Canceled transactions, please let us know.</em></p><p><em>Originally published at </em><a href="https://blog.blocknative.com/blog/canceled-transactions"><em>https://blog.blocknative.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd202d5712c6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons Learned: The Role of Community in a Successful Dapp Launch]]></title>
            <link>https://medium.com/@mcutler/lessons-learned-the-role-of-community-in-a-successful-dapp-launch-e11bb99cefde?source=rss-36a9da84bd67------2</link>
            <guid isPermaLink="false">https://medium.com/p/e11bb99cefde</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[games]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[Matt Cutler]]></dc:creator>
            <pubDate>Wed, 07 Aug 2019 17:16:53 GMT</pubDate>
            <atom:updated>2019-08-07T17:30:06.734Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*edAoyXB8fesf4KALlR4gKw.png" /></figure><p><a href="https://cryptominerworld.com/">CryptoMiner World</a> is a crypto-collectible game where players can dig up crypto treasures from beneath a virtual landscape. Players find tradable in-game assets like silver, gold, gems, and more. Hidden throughout the world are keys to rare chests that contain anywhere from 10 to 2,000 ETH. <em>Yes, that’s more than $400,000!</em></p><p>In many ways, CryptoMiner World is a next-generation blockchain game.</p><p><a href="https://twitter.com/john_b_butler">John Butler</a> (a.k.a. Amethyst), the founder Sophophilia Studios, the studio behind CryptoMiner World, invested heavily in building his community in parallel to developing the game. He spends hours each day engaging with the community, answering questions, and revising the game experience based on real-world feedback. As a result, John and his team relentlessly focus on combining ease-of-use with enticing game mechanics.</p><blockquote><em>We designed CryptoMiner World to have staying power. We want our players to have fun and stay engaged for years, not weeks.</em></blockquote><p>John told us that a core part of building community is helping users get onboard and playing successfully. To help users better understand what was happening when working with the on-chain elements of the game, the team at CryptoMiner World started to build their own notification infrastructure. But, ahead of the launch, John was introduced to Blocknative:</p><blockquote><em>We were only weeks away from the launch and I was concerned that it might be too late to integrate. But Assist.js turned out to be so simple that we ended up integrating everything before launch. It covered all of our target use cases and much more.</em></blockquote><p>CryptoMiner World integrated all of the <a href="https://www.blocknative.com/readiness-assessment">capabilities</a> of Assist.js, including onboarding support and transaction notifications. Replacing their existing notification code even helped the team to clean up their transaction codebase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YnO73Nm-PjtHQOFJW-2CxA.gif" /><figcaption>Blocknative’s Wallet Check capability helps users select the correct network.</figcaption></figure><p>At launch, the community that John had carefully built showed up to support the game — to the tune of several hundred transactions per minute at the peak.</p><p>And this, of course, is just the start. The next step in the journey involves the launch of new gems, including the recent release of Special Country Gems. These help players speed up mining times and improve the chances of finding keys to rare chests.</p><p>We asked John for any advice he could give to others building blockchain-based games:</p><blockquote><em>The key is building an authentic community. And one of the best things you can provide that community is real-time feedback whenever and wherever they engage. This is why we are excited to be working with Blocknative.</em></blockquote><p>While the game is off to an impressive start, we’re looking forward to learning more as the long- term game design continues to drive community engagement. We invite you to <a href="https://cryptominerworld.com/">explore CryptoMiner World</a> to find some genuine crypto treasures and see Blocknative Assist in action along the way.</p><h3>Are you launching a Dapp? Do you want to maximize user engagement?</h3><p>Blocknative is the notification framework for Dapps and wallets. With Assist.js, you can give your users real-time updates on blockchain transactions — which boosts confidence, increases engagement, and improves retention.</p><p>Join our <a href="https://discord.gg/De9sCqD">Discord server</a> to connect with our team and learn more about how Blocknative can help.</p><p><em>Originally published at </em><a href="https://blog.blocknative.com/blog/cryptominer-world"><em>https://blog.blocknative.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e11bb99cefde" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Guessing A Private Key: Beyond Chainsplaining Part IV]]></title>
            <link>https://medium.com/thecapital/guessing-a-private-key-beyond-chainsplaining-part-iv-7b6a2272b9e9?source=rss-36a9da84bd67------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b6a2272b9e9</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Matt Cutler]]></dc:creator>
            <pubDate>Wed, 26 Jun 2019 15:18:20 GMT</pubDate>
            <atom:updated>2019-06-27T02:38:15.025Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G_OQB488Pliq05t9988_Eg.png" /></figure><h4>By <a href="https://medium.com/u/36a9da84bd67">Matt Cutler</a> on ALTCOIN MAGAZINE</h4><p>What if I told you that you could control a crypto account with hundreds of millions of dollars in value <em>just by guessing a single number</em>?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w2U0BMmxREjnCmWMz0ptxw.jpeg" /></figure><p>Well, it turns out that you can. Because in the world of blockchain, private keys determine ownership. And, as we explored in our last post, you can <a href="https://blog.blocknative.com/blog/hold-every-private-key-in-the-palm-of-your-hand-beyond-chainsplaining-part-iii">hold every private key in the palm of your hand</a>. So how hard can it be to guess… right?</p><p>For the most part, the crypto-curious react with a combination of surprise and intrigue. Typically the first question is something along the lines of: <em>“If it were really that easy… wouldn’t someone else have already done it!?!!”</em></p><p>To answer this question, we need to dive into the relative odds of guessing a 256-bit private key.</p><blockquote>The greatest shortcoming of the human race is our inability to understand the exponential function. — Albert Allen Bartlett</blockquote><p>In the <a href="https://blog.blocknative.com/blog/tag/beyond-chainsplaining">Beyond Chainsplaining series</a>, we explore metaphors and stories you can use to help explain blockchain. Inspired by Michael Kerbleski’s excellent <a href="https://medium.com/@kerbleski/a-dance-with-infinity-980bd8e9a781">Guess My Bitcoin Private — A Dance with Infinity </a>post, we created a new tool to help you to explain just how hard it is to guess a private key: every power of 2 from 1 to 256 on a single sheet of (double-sided!) A3 11x17 paper.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/341/0*Pt6OZHwZW05y0F5x.png" /></figure><p>On this template, we’ve marked both the power of 2 and some of the corresponding approximate odds, including :</p><ul><li>2¹ – 1 in 2, or the odds of guessing a coin toss.</li><li>2⁵ – 1 in 32, or the odds of guessing the correct number in roulette.</li><li>2²⁸ – The approximate odds of winning the Powerball or MegaMillions lottery.</li></ul><p>When discussing this, people generally acknowledge that while winning the lottery is highly improbable, it is objectively not impossible. After all, people win large lotteries on a regular basis.</p><ul><li>2⁵⁶ – The approximate odds of winning <em>both</em> the Powerball or MegaMillions in the same week.</li></ul><p>Here the conversation veers into a contemplation of the impossible. While people might win a single lottery, nobody has ever won both of the largest lotteries <em>in the same week.</em> However, it still seems possible that it might happen. So let’s keep going.</p><ul><li>2⁶³ – The number of possible NCAA basketball brackets.</li><li>2⁷⁰ – The estimated number of stars in the observable universe.</li><li>2¹⁶⁶ – The approximate number of atoms on Earth.</li></ul><p>About now is when folks start to throw up their hands and acknowledge we’re in the realm of the impossible. After all, your current surroundings contain an unfathomable number of atoms… let alone the entire Earth.</p><p>Yeah, this one surprised us too, but it turns out <a href="https://www.mcgill.ca/oss/article/did-you-know-infographics/there-are-more-ways-arrange-deck-cards-there-are-atoms-earth">there are more ways to shuffle a deck of cards than there are atoms on Earth</a>.</p><ul><li>2²³¹ – The approximate number of atoms in the Milky Way galaxy.</li><li>2²⁵⁶ – The number of possible 256-bit private keys.</li></ul><p>You can decide for yourself at what point the scale veers from the merely improbable to the effectively impossible. But when your closest point of comparison is the number of atoms in a galaxy… let’s just say that even the crypto-skeptics understand that the hundreds of millions of dollars in value in that single crypto account are not really at risk of having the private key be randomly guessed.</p><p>The scale that we are dealing with beyond the general range of human cognition. As it turns out, research has consistently shown that <a href="https://onlinelibrary.wiley.com/doi/pdf/10.1111/cogs.12388">humans have a very hard time understanding big numbers</a><em>. </em>I’ve found that it all becomes more approachable when I anchor the relative odds in terms that people can understand.</p><p><strong>Want to download a PDF file of the powers of 2 from 1 to 256? </strong><a href="https://discord.gg/KZaBVME"><strong>Click here to join our Discord community</strong></a><strong>. </strong>You can find the PDF on the<strong> </strong>#downloads channel.</p><p>As always, let me know your thoughts about how best to introduce complex and often mind-bending blockchain concepts to the crypto-curious. You can tweet me <a href="https://twitter.com/mcutler">@mcutler</a>.</p><p><em>Originally published at </em><a href="https://blog.blocknative.com/blog/guessing-a-private-key"><em>https://blog.blocknative.com</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aiwMNSYLnJucU3XzuRZa4A.png" /></figure><p><a href="https://twitter.com/Alt__Magazine">Altcoin Magazine</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><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b6a2272b9e9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/thecapital/guessing-a-private-key-beyond-chainsplaining-part-iv-7b6a2272b9e9">Guessing A Private Key: Beyond Chainsplaining Part IV</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[Case Study: Nifty Football Delivers State-of-the-Art Dapp UX on Mobile and Desktop]]></title>
            <link>https://medium.com/coinmonks/case-study-nifty-football-delivers-state-of-the-art-dapp-ux-on-mobile-and-desktop-64a9000cac7a?source=rss-36a9da84bd67------2</link>
            <guid isPermaLink="false">https://medium.com/p/64a9000cac7a</guid>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[dapps]]></category>
            <dc:creator><![CDATA[Matt Cutler]]></dc:creator>
            <pubDate>Wed, 05 Jun 2019 18:08:59 GMT</pubDate>
            <atom:updated>2020-08-26T12:54:23.013Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hPIo_JJtbqMrRH9kQXM20g.png" /></figure><p>We’re happy to share that <a href="https://niftyfootball.cards/">Nifty Football</a> has deployed <a href="https://www.blocknative.com/transaction-awareness">Blocknative Assist</a> into their Dapp, providing the Ethereum ecosystem with a live example of state-of-art transaction usability.</p><p>Nifty Football is a- Ethereum powered football — or ‘soccer’ for those of you in the US and Canada — crypto-collectible trading card game with provably scarce assets. The team behind Nifty Football is experienced in the space, having previously worked at KnownOrigin, CryptoKaiju, and BlockCities.</p><p>The team’s deep understanding of how to build successful, engaging Dapps led them to focus on providing a clear, easy-to-understand user experience from the outset. Look no further than the Dapp’s streamlined front-end to see how simple it is to use. After connecting with the Blocknative team, the Nifty Football leadership realized that they had an immediate opportunity to extend this clarity and simplicity into their onboarding and transaction flows. According to <a href="https://medium.com/@awaygray">Andy Gray</a>, the co-founder of Nifty Football:</p><blockquote><em>“A full 50% of Nifty Football transactions happen on mobile. We wanted to help our customers understand the status of their transactions — regardless of their device of choice. By providing real-time visibility at every step of the transaction, Blocknative Assist improves our user experience at the most critical moments of engagement.”</em></blockquote><p>The experience begins when users land on the site. If they’re on an unsupported browser; Nifty Football and Assist.js will direct users to a Web3-compatible browser:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_9LjY51pJow8C0GA.gif" /></figure><p>When users access Nifty Football without wallet installed, Blocknative Assist guides them through — and verifies their progress in real-time! — the process of wallet installation, logging in, authorizing Nifty Football, selecting the correct network, and more:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OOxWF8qB0CPGGWgG.gif" /></figure><p>This ensures that as many users as possible are ready and able to transact, all in an effort to maximize the active user base and transaction volume.</p><p>Whenever users initiate a transaction, Blocknative Assist is there to help them understand what’s going on with each and every step of the transaction, from Waiting for Approval to Pending to Confirmed. And with easy-to-understand alerts that appear in line with the Dapp itself, users are no longer forced to dig through wallet settings or navigate away to a third-party block explorer:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SCYTN3bF60IR_dTm.gif" /></figure><p>Critically, these transaction notifications work just as well on mobile Dapp browsers:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/308/1*_6twVA6QDjwdyqri5_R5Nw.gif" /></figure><p>The combination of a clean user interface, onboarding support, and transaction notifications puts Nifty Football well-ahead of the pack in Dapp usability. <strong>Want to experience it for yourself?</strong> Go <a href="https://niftyfootball.cards/buy">buy some cards</a> to experience Nifty Football’s industry-best UX in action.</p><h4>Major Improvements to Nifty’s Transaction Usability Audit (TUXA) Score</h4><p>By deploying Assist.js into their Dapp, Nifty Football drove a major improvement in their Dapp Transaction Usability Audit Score — now ranking among the best Dapps that we have encountered on Mainnet. You can quickly assess your TUXA score with Blocknative’s <a href="https://blog.blocknative.com/blog/dapp-transaction-audit-template">recently open-sourced Audit Template</a>.</p><h4>Integrating Assist.js into Nifty Football</h4><p>The team at Nifty Football chose to engage Blocknative to deploy Assist.js via our ‘white glove’ integration service. We kicked things off with a private channel on <a href="https://discord.gg/z4ZQCe2">Blocknative’s Discord</a> so that everyone involved, including our CTO and integration team, could collaborate fluidly. Deploying Blocknative Assist requires just a handful of steps:</p><ol><li>Create an API Key: This uniquely identifies your Dapp and enables <a href="https://www.blocknative.com/performance-analytics">Performance Analytics</a></li><li>Initialize Blocknative Assist: Add Assist.js to the first page of your Dapp.</li><li>Initialize the library.</li><li>Call Onboard.</li><li>Decorate your contract: This adds the <a href="https://www.blocknative.com/transaction-awareness">Transaction Awareness</a> capabilities described above.</li></ol><p>And that’s it, after 5 steps Nifty Football was up and running with Blocknative Assist. <strong>The initial deployment took our team about a day to set up</strong>. Along the way, we received useful product feedback and invested additional cycles to design and implement several of the features included in our recent Assist.js 0.8 release. We’re excited to be playing a part in helping Nifty Football and the broader Dapp ecosystem improve Web3’s UX.</p><h4>Want to improve your Dapp’s transaction UX?</h4><p>Blocknative is on a mission to improve the UX of the Web3 ecosystem. Our embeddable javascript widget makes it easy for Dapp developers to improve the onboarding and transaction experience for their end-users.</p><p>If you want to connect with the team, <a href="https://discord.gg/z4ZQCe2">join our Discord</a> — which contains free Downloads like our Dapp UX Audit Template. You can also sign up for a free account at Blocknative.com and begin integrated Assist.js into your Dapp in minutes.</p><blockquote><a href="https://coincodecap.com/?utm_source=coinmonks">Get Best Software Deals Directly In Your Inbox</a></blockquote><figure><a href="https://coincodecap.com/?utm_source=coinmonks"><img alt="" src="https://cdn-images-1.medium.com/max/584/0*OJ-qb5G6i863msBB.png" /></a></figure><p><em>Originally published at </em><a href="https://blog.blocknative.com/blog/nifty-football"><em>https://blog.blocknative.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64a9000cac7a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/coinmonks/case-study-nifty-football-delivers-state-of-the-art-dapp-ux-on-mobile-and-desktop-64a9000cac7a">Case Study: Nifty Football Delivers State-of-the-Art Dapp UX on Mobile and Desktop</a> was originally published in <a href="https://medium.com/coinmonks">Coinmonks</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Holding Every Private Key in the Palm of Your Hand: Beyond Chainsplaining Part III]]></title>
            <link>https://medium.com/hackernoon/holding-every-private-key-in-the-palm-of-your-hand-beyond-chainsplaining-part-iii-6bf1a1361927?source=rss-36a9da84bd67------2</link>
            <guid isPermaLink="false">https://medium.com/p/6bf1a1361927</guid>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[wallet-recovery]]></category>
            <category><![CDATA[chainsplaining]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Matt Cutler]]></dc:creator>
            <pubDate>Thu, 16 May 2019 16:38:27 GMT</pubDate>
            <atom:updated>2019-05-16T18:05:18.040Z</atom:updated>
            <content:encoded><![CDATA[<h3>Holding Every Private Key Out There in the Palm of Your Hand: Beyond Chainsplaining Part III</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oQMFC0q_4v6rubBN1v4nUg.jpeg" /></figure><p>Our objective with the Beyond Chainsplaining series is to explore metaphors and stories you can use to help explain blockchain. In our last post, we built out our first ‘metaphor of the moment’: <a href="https://blog.blocknative.com/blog/bricks-in-a-wall">Blockchains as Brick Walls</a>.</p><p>In this post, we’ll introduce a new and different ‘metaphor of the moment’ — <strong>how to hold virtually every possible private key in your hands. On a single sheet of paper.</strong></p><p>Anyone who has created an Ethereum wallet is familiar with carefully writing down a sequence of seemingly random words — <em>the seed recovery phrase</em>. They are typically 12 words long, though 24 word seed phrases are also used.</p><p>Have you ever wondered where those words come from? Or how they were selected to safeguard your tokens? Well, we did. And here’s what you need to know:</p><ol><li><a href="https://en.bitcoin.it/wiki/Seed_phrase">Seed phrases</a> are based on the <a href="https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki">BIP 39</a> standard. What’s a BIP?</li><li>BIP is an acronym for <em>Bitcoin Improvement Proposal</em>. Just like Ethereum’s ERC <em>(Ethereum Request for Comments)</em> process, BIP’s are how the Bitcoin development community considers new features and functionality for the Bitcoin blockchain.</li><li>BIP 39 uses mnemonic phrases <em>(aka pseudo random sentences)</em> to generate a master private key, from which a <a href="https://en.bitcoin.it/wiki/Deterministic_wallet">hierarchical deterministic (HD) wallet</a> can be derived.</li><li>The surprising part? You can’t use just any word as part of your seed phrase. Instead, BIP 39 specifies a dictionary of just 2,048 possible words.</li><li>Wait? That’s it? Just over two thousand words? That turns out to be less than 1.2% of the words in the English language. But those 2,048 words create enough permutations and combinations of seed phrases to generate virtually every possible private key.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/652/1*guoKCwI9vh7E4UiD-1oo0w.png" /></figure><p><em>Which begs the obvious question: </em><strong><em>is it possible to squeeze the entire BIP 39 English dictionary on a single sheet of paper?</em></strong></p><p>Yes! Though if you want it to be readable you must print it on an A3 (11x17) sheet of paper. Here’s a thumbnail:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/270/0*5zQjvMOLjscqRpgy.png" /></figure><p>To download the full PDF, just <a href="https://discord.gg/yz43Pbb"><strong>click here to join our Discord server</strong></a>. Then head over to the #downloads channel. We’ll be posting other downloadable assets there in the future.</p><p>Printouts like this have proven to be powerful props when we’re explaining the notion of wallets and seed phrases to the crypto-curious. Holding every possible private key in your hands somehow makes the complex concepts behind wallets and seed phrases more relatable. Which is critical when you’re trying to get Beyond Chainsplaining.</p><p>This then <strong>sparks a conversation</strong> that helps your audience understand why Seed Phrases are important<em>. </em>Sometimes we can almost see folks make the subtle-yet-supremely-gratifying internal shift from “I’m in way over my head” to “I think I can do this.”</p><p>As your conversation progresses, your audience may ask a version of: <em>“So this all fits on a single sheet of paper… shouldn’t every wallet have been hacked by now?”</em></p><p>That’s a great question. As it turns out, the odds of guessing a private key are really slim. Really really slim. For all intents and purposes <strong>impossibly slim.</strong></p><p>Curious to learn just how slim? Stay tuned for our next post in our Beyond Chainsplaining series. We’ll have some fun exploring <strong>Power Laws</strong> and the relative probability of guessing a private key. With props!</p><p>Having fun? Please follow <a href="https://twitter.com/blocknative">@blocknative</a> on twitter, subscribe to our email list, join our <a href="https://discord.gg/TyVJkg4">Discord</a> to contribute to the conversation, and see the next post in our <a href="https://blog.blocknative.com/blog/tag/beyond-chainsplaining">Beyond Chainsplaining Series</a>.</p><p><em>Originally published at </em><a href="https://blog.blocknative.com/blog/hold-every-private-key-in-the-palm-of-your-hand-beyond-chainsplaining-part-iii"><em>https://blog.blocknative.com</em></a><em>.</em></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=6bf1a1361927" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/holding-every-private-key-in-the-palm-of-your-hand-beyond-chainsplaining-part-iii-6bf1a1361927">Holding Every Private Key in the Palm of Your Hand: Beyond Chainsplaining Part III</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[Beyond Chainsplaining Part 2: Blockchains as Brick Walls and Other Ways to Light the Lightbulb]]></title>
            <link>https://medium.com/hackernoon/beyond-chainsplaining-part-2-blockchains-as-brick-walls-and-other-ways-to-light-the-lightbulb-b24cd701ac51?source=rss-36a9da84bd67------2</link>
            <guid isPermaLink="false">https://medium.com/p/b24cd701ac51</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Matt Cutler]]></dc:creator>
            <pubDate>Thu, 09 May 2019 14:09:04 GMT</pubDate>
            <atom:updated>2019-05-09T19:29:58.411Z</atom:updated>
            <content:encoded><![CDATA[<h3>Beyond Chainsplaining Part II: Blockchains as Brick Walls and Other Ways to Light the Lightbulb</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ojWr0khjBTneOsiT0uQR0w.jpeg" /></figure><p>Our recent <a href="https://blog.blocknative.com/blog/enough-with-the-chainsplaining">Enough with the Chainsplaining</a> post seemed to strike a nerve — in a positive way! — within the Ethereum community. Ecosystem thought-leaders and crypto-newbies alike have reached out to encourage us to continue on this theme. We clearly have good company in our quest to figure effective ways to discuss the foundational concepts that make blockchain technology so compelling.</p><p>Given this feedback, today we’re kicking off this <strong>Beyond Chainsplaining</strong> series. It will explore the vocabulary and metaphors that help make blockchain concepts more accessible. We invite you to be part of this journey. Provide feedback. Engage in dialogue. And contribute your ideas and experiences to help drive adoption of this ecosystem.</p><p>In our <a href="https://blog.blocknative.com/blog/enough-with-the-chainsplaining">last post</a>, we provided a high-level overview of the dangers of Chainsplaining, including this simple definition: “mansplaining cryptocurrency and/or blockchain technology.” Instead, we encouraged blockchain enthusiasts and insiders to approach the topic with empathy by 1) forgetting the tech 2) leading with a story 3) using examples and metaphors people already understand 4) knocking your audience off-balance with unexpected insights.</p><blockquote><em>Walking the crypto-curious through a relatable metaphor like ‘blockchains as brick walls’ can help those interested begin to make sense of this new world.</em></blockquote><p>In this post, we’d like to further expand one of our favorite metaphors for illustrating what makes blockchain technology both interesting and challenging: <strong>blockchains as brick walls</strong>. Here’s a high-level outline of the narrative:</p><ol><li><strong>In the Fiat world, the money moves.</strong> If I want to pay you $20, I take a $20 bill out of my wallet and hand it to you. You then place the $20 bill in your wallet. Possession of the bill determines who controls the value. And the money literally moves out of my wallet and into your wallet. Or, similarly, out of my bank account and into yours.</li><li><strong>In the Crypto world, money is like bricks in a wall.</strong> In the world of blockchain, money is more like a brick in a wall. Each brick has a recognized value. But that brick will never be inside my wallet because, of course, it is fixed in place in the wall. If someone were to attempt to pry the brick out, doing so would damage the surrounding bricks and make it obvious that the wall had been tampered with.</li><li><strong>Each brick has ‘permissions’ associated with it. </strong>While you can’t put that brick in your wallet, you can prove that you control it. Each brick has ‘permissions’ which let you use them in transactions.</li><li><strong>To move the value, change the permissions. </strong>In the Crypto world, I can pay you the equivalent of $20 by changing the permissions on one of the bricks that I control. But, critically, the bricks still don’t move. It was never in my wallet. And it will never be in your wallet. The change in permissions is effectively instantaneous* so, unlike a normal $20 bill, it can never be in transit between wallets. So while control over the value has changed, the value itself remains perfectly fixed.</li><li><strong>The consequence: Ownership Without Possession (OWP)</strong>. Unlike the Fiat world, ownership in the Crypto world is divorced from possession. In fact, the absence of any notion of possession is among the most surprising aspects of blockchain technology. It is also intellectually and emotionally challenging to internalize.</li><li><strong>The wall is growing. At a predictable pace.</strong> While the bricks are fixed in the wall, the wall itself is growing at a predictable rate. New bricks get created and added to the wall at a regular cadence. And each of these new bricks behaves exactly like the existing bricks.</li><li><strong>There are many identical walls. And they all agree with each other.</strong> To continue the ‘blockchains as brick walls’ metaphor, it turns out there are many identical copies of the wall. They are located all over the world. And they are perfectly synchronized. Each wall contains exactly the same bricks, in the same order, with the same permissions, and new bricks get added at precisely the same moment. If someone tries to make a fraudulent wall that contains bricks in a different order, or (more likely) with different permissions, it is easy to spot — and hence ignore — the one wall that is out of sync.</li><li><strong>There are different networks of walls. Each with different rules and behaviors.</strong> There are different types of walls, each representing an independent blockchain — Bitcoin, Ethereum, Litecoin, Ripple, Zcash, Dogecoin, and many more. While each type of wall has its own particular set of rules and behaviors, in general, they share most of the above characteristics.</li><li><strong>Some walls have a single type of brick</strong>. Many walls consist of a single type of brick — such asBitcoin. The Bitcoin blockchain supports the Bitcoin cryptocurrency alone.</li><li><strong>Other walls include different types of bricks.</strong> Other walls support many different types of bricks — like Ethereum. Ethereum supports a native cryptocurrency as well as Smart Contracts. Because Ethereum is a programmable blockchain, it also allows for the creation of new bricks (ERC20, ERC721, and beyond).</li></ol><p>Walking the crypto-curious through relatable metaphors can help them begin to make sense of this new world. And to internalize the more fundamental implications of this new ecosystem, we must also unlearn some deeply held notions.</p><p>What do you think? Have you tried this out? If so, I’d love to learn how it went. What worked? Where did you stumble? Did your audience lean in and start asking questions? If so, what were they? Do you use different analogies?</p><p>Let’s learn from each other. The easiest way to find me is Twitter <a href="https://twitter.com/mcutler">via @mcutler</a>.</p><p><em>Originally published at </em><a href="https://blog.blocknative.com/blog/bricks-in-a-wall"><em>https://blog.blocknative.com</em></a><em>.</em></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=b24cd701ac51" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/beyond-chainsplaining-part-2-blockchains-as-brick-walls-and-other-ways-to-light-the-lightbulb-b24cd701ac51">Beyond Chainsplaining Part 2: Blockchains as Brick Walls and Other Ways to Light the Lightbulb</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[Enough with the Chainsplaining (Part 1): How to Talk Blockchain Empathtically]]></title>
            <link>https://medium.com/hackernoon/enough-with-the-chainsplaining-part-1-how-to-talk-blockchain-with-empathy-a6ca65910aad?source=rss-36a9da84bd67------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6ca65910aad</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[mansplaining]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Matt Cutler]]></dc:creator>
            <pubDate>Sun, 07 Apr 2019 14:04:05 GMT</pubDate>
            <atom:updated>2019-04-09T14:32:08.709Z</atom:updated>
            <content:encoded><![CDATA[<h3>Enough with the Chainsplaining (Part 1): How to Talk Blockchain Empathetically</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NMNzpB60V421iLNkz19j6w.jpeg" /><figcaption><strong><em>mansplain: verb: (of a man) explain (something) to someone, typically a woman, in a manner regarded as condescending or patronizing.</em></strong></figcaption></figure><p>Chainsplaining starts innocuously enough. Maybe you’re at a cocktail party or a neighborhood gathering, and blockchain happens to bubble up in casual conversation.</p><blockquote><em>“Blockchain? That’s like Bitcoin right?”</em></blockquote><blockquote>Or <em>“Yeah, I’ve read a bit about Crypto but I still don’t get it…”</em></blockquote><blockquote>Or <em>“Didn’t everyone lose a bunch of money on ICOs?”</em></blockquote><p>You might be bursting at the seams to explain, describe, and demystify the layers of blockchain. And in the beginning, your audiences will probably greet this with a mixture of feigned curiosity, FOMO, surveillance unease, and disdain for yet another over-hyped techno-fad.</p><p>But — before you know it — you’re twenty minutes deep into a tirade about the illusory root value of fiat currency, the inefficiencies of government bureaucracy, and the promises of a crypto-utopian future… that seems so close you can almost touch it.</p><p>Meanwhile, your previously just-being-polite audience is looking for the exit.</p><p>Sound familiar?</p><p>Yep. You’ve been chainsplaining.</p><p>Or maybe this is just me… 🤔😅</p><p>Whether you’ve been a fellow-chainsplainer or a victimized chainsplainee, it’s not a great place to be. It’s tempting to try and share everything you’ve ever learned about blockchain in the time that it takes the ice in your drink to melt… but for the crypto-curious or the crypto-skeptical, chainsplaining is ineffective and awkward.</p><blockquote><strong><em>Chainsplain</em></strong><em>: to mansplain cryptocurrency and/or blockchain technology.</em></blockquote><p>However, blockchain <em>does</em> come up in social settings these days. And it deserves a thoughtful dialogue since it’s so new and often counterintuitive. How might we describe blockchain without someone excusing themselves to refresh their beverage…again?</p><p>While I can’t claim to have mastered the art of explaining blockchain, along my own adventures down the rabbit hole I’ve stumbled across a few non-technical ways to help describe things so that people actually have a fighting chance of lighting the lightbulb. This is a big topic, but here are a few top-level lessons-learned to help keep things on the rails. So take a read and keep me honest.</p><h4>Empathize with your audience, and try to remember they’re new to all this</h4><p>Chainsplainers can be unbearable because they launch straight into blockchain technology — name-dropping new terms and complicated concepts — to an audience who often doesn’t have the slightest idea what they’re talking about. And an audience that feels overwhelmed and disoriented will soon want to get the heck outta dodge.</p><p>That’s why before I get into <em>here’s how this grand machine works</em>, I try my best to lead with <em>why any of this might be interesting to you.</em></p><h4>Forget the tech, instead start with a story</h4><p>People learn through stories. Our brains naturally seek out a narrative structure with a beginning, a middle, and an end. Stories are how we receive new information. Stories provide the metaphorical maps that enable us to navigate new experiences. And stories are also how we recall information to share with others moving forward. When I start to introduce the complex concept of blockchain, I do my best to do so in a familiar narrative with relatable concepts to make my audience feel a little more comfortable.</p><h4>Use an example they already understand</h4><p>For better or worse, analogies involving money tend to work well, as most people naturally associate cryptocurrencies with blockchain.</p><p>Simple props help. For instance, I might take my wallet out of my back pocket and explain, “In the fiat world, if I want to give you $20.00, I take a twenty dollar bill out of my wallet, hand it over to you, and then you put that money inside your wallet. In this world, the money moves. It changes hands. It can be in transit. And critically it changes possession in a tangible, physical sense.”</p><p>At this point in my conversation, people’s heads are nodding slowly as they begin to wonder why I’m bothering to be precise over something so familiar. Which is the perfect opportunity to surprise them.</p><h4>Knock them off balance</h4><p>“Nothing we’ve just said is true — or even possible — in the world of blockchain. My crypto wallet will never ‘contain’ $20.00 worth of cryptocurrency in the same way that my physical wallet contains this $20.00 bill. I literally cannot ‘hand’ cryptocurrency to you. And your crypto wallet will never have $20.00 worth of cryptocurrency inside of it.”</p><blockquote><em>My crypto wallet will never ‘contain’ $20.00 worth of cryptocurrency in the same way that my physical wallet contains this $20.00 bill.</em></blockquote><p>At this point, folks tend to lean in, squint their eyes, and maybe tilt their heads. “Wait… what?” This is not where they expected the conversation to start. And, significantly, they have just asked their first exploratory question.</p><p><strong><em>Pro-tip:</em></strong><em> the presence (or absence) of curious questions is the easiest and most immediate method to gut-check if you might be mansplaining, chainsplaining, or any other *splaining.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/1*SLwHNNEQ2oJkE0AkciAhjA.jpeg" /></figure><p>“In the crypto world, the ‘money’ is fixed in time and space. Sort of like bricks in a wall. Imagine that each brick is worth $20.00. I can prove that I control a specific brick. And I can transfer control of that brick to you. Now it is your brick. However, that brick was never in my wallet. And it will never be in your wallet. It’s just a brick on a wall that you can prove that you control. When you transfer control over it, it switches to the next person almost instantly.</p><p>So… in the crypto world, the money doesn’t move. Only the permissions move. I can transfer the value, but it was never inside my wallet, and it will never be inside of your wallet. This one concept has profound implications: at a relatively fundamental level, blockchain technology enables digital ownership but explicitly does not allow any notion of possession. Ownership without possession. This changes almost everything.”</p><p>I’m watching for folks to look away, defocus their eyes a bit, and say something along the lines of “Whoa… nothing I’ve read about so far mentions anything like this.”</p><h4>Acknowledge that the learning journey is difficult</h4><p>Learning about blockchain is hard because everyone has expectations about how things work. The word ‘wallet,’ for example, has an existing meaning. Most people think of it as a container that holds cash and cards. In blockchain, the word ‘wallet’ means something else entirely — and new learners are confronted with countless counterintuitive terms like this. But before explaining a new concept, it’s much easier if we first acknowledge and begin to break down preconceived notions and baseline assumptions.</p><p>That’s one of the hardest parts of the blockchain journey: in order to make heads or tails of this new world, people must first <em>unlearn</em> a whole bunch of deeply held notions. Notions that are so second-nature as to barely be recognized as assumptions at all. And that’s really, really tough.</p><blockquote><em>In order to learn make heads or tails of this new world, people must first unlearn a whole bunch of deeply held notions.</em></blockquote><p>But this is where the ocean meets the shore. And where the descent down the blockchain rabbit hole needs to begin if new users are going to be interested enough to explore further, and persistent enough to work through the inevitable moments of frustration and confusion that come with this territory.</p><h4>Interested in upcoming chapters in this narrative?</h4><p>At this point in their journey, my audience is usually both curious and confused… and starting to be compelled to stick around to learn more.</p><p>In future posts, I hope to share additional narrative techniques that I’ve found help continue the blockchain conversation in language and metaphors that bring the key concepts alive and help people light the lightbulb.</p><p>In the meantime, give it a shot and let me know how it goes. I’d also love to learn about the stories that you find effective when talking blockchain. <a href="https://twitter.com/mcutler">You can find me on Twitter via @mcutler</a>.</p><p><em>Big thanks to </em><a href="https://twitter.com/starsoup7"><em>Sarah Mills</em></a><em>, </em><a href="https://twitter.com/tayvano_"><em>Taylor Monahan</em></a><em>, </em><a href="https://twitter.com/seth"><em>Seth Goldstein</em></a><em>, and the </em><a href="http://twitter.com/blocknative"><em>Blocknative</em></a><em> team for providing feedback on earlier drafts of this post!</em></p><p><em>Originally published at </em><a href="https://blog.blocknative.com/blog/enough-with-the-chainsplaining?hsCtaTracking=917be600-da80-49c0-8522-3e9ba2c4ed45%7C1832f47a-4bd1-4021-bc11-aa6c81d70ec1"><em>blog.blocknative.com</em></a><em>.</em></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=a6ca65910aad" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/enough-with-the-chainsplaining-part-1-how-to-talk-blockchain-with-empathy-a6ca65910aad">Enough with the Chainsplaining (Part 1): How to Talk Blockchain Empathtically</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>
    </channel>
</rss>