<?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 Alanna Fischer on Medium]]></title>
        <description><![CDATA[Stories by Alanna Fischer on Medium]]></description>
        <link>https://medium.com/@alannafischer?source=rss-ccac530addf6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lEGc1CgdZU6OQ354xxvyyQ.png</url>
            <title>Stories by Alanna Fischer on Medium</title>
            <link>https://medium.com/@alannafischer?source=rss-ccac530addf6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 05:00:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alannafischer/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[Announcing transaction traces on evm.storage]]></title>
            <link>https://blog.smlxl.io/announcing-transaction-traces-on-evm-storage-3a4e66e312fc?source=rss-ccac530addf6------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a4e66e312fc</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[transactions]]></category>
            <category><![CDATA[search]]></category>
            <dc:creator><![CDATA[Alanna Fischer]]></dc:creator>
            <pubDate>Wed, 08 Nov 2023 17:56:28 GMT</pubDate>
            <atom:updated>2023-11-29T17:19:48.150Z</atom:updated>
            <content:encoded><![CDATA[<p>A couple of weeks ago, <a href="https://blog.smlxl.io/making-public-computers-more-transparent-accessible-and-useful-57bc163bd0b2">we came out of stealth</a>, extended our <a href="https://blog.smlxl.io/announcing-bytecode-generated-storage-layouts-on-evm-storage-96761758d397">support for unverified contracts</a>, open-sourced our <a href="https://github.com/smlxl/storage-layout-extractor">storage layout extractor</a>, and launched transaction pages. Today, we’re adding transaction traces.</p><p>In this post, we discuss our design goals and thinking behind the product and give a quick walkthrough. We wrap up by sharing a bit more about our upcoming roadmap.</p><h4>Approaching our tracer</h4><p>It’s important to us that our tracer adds value over existing solutions. While other tracers have done a great job with advanced gas profiling, code integration, and flow of funds, we felt we could add value in the following areas:</p><ol><li><strong>Streamlined workflow</strong>: Explore even the most complex executions via our expansible trace tree and trace-specific tabs. Navigate between traces and the involved contracts and variables (and soon accounts), without needing multiple windows and tools.</li><li><strong>Storage-driven</strong>: We show you the logs and events, but we’re not reliant on them. Our balance changes component tracks actual storage changes, not logs that can be “<a href="https://evm.storage/eth/0x7f3971f670967fd73a6c4038112136064d299437d6205dd8c54c588704befef8">spoofed</a>” or not <a href="https://evm.storage/eth/0x83715db2b25d78dd13f43db38610a5f379fbc58b3e3b27cef0040a600920b140">emitted</a> at all, fooling other tracers. We also show the SLOADS and SSTORES, as well as SHA3 hashing operations, complete with their pre-images.</li><li><strong>Mobile and fast: </strong>We have a dedicated mobile presentation for smaller screens that we’ll continue to improve. Performance is important to us, and we’re working on making the tracer faster and more useful for all devices and connections.</li></ol><h4>A streamlined tracing workflow</h4><p>Our streamlined workflow emerged out of the key design challenge we encountered in building a tracer: <strong>how do we allow the user to consume a transaction at their desired depth?</strong></p><p>Some users may want to drill into every argument’s values, while others just want an overview of the key execution logic. To serve both, we had to enable users to easily move in and out of detailed views, without losing sight of the bigger picture.</p><p>The solution we aligned upon is the expansible tree representation of traces paired with trace tabs, allowing the user to click into any trace to explore it in a format structured specifically for that type of trace. This allows users to maintain their position within the transaction page and the full traces while diving into richer insights in the trace details tabs. The ability to switch between tabs, close tabs out, and refer back to the main invocation flow as a home base reflects the way users interact with this data in their workflows.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F882582699%3Fapp_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F882582699&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F1750695890-d506122928a0018b4d3f747b3f3bdf324c081be056f4c21e29c776358a8e5df5-d_1280&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1207" frameborder="0" scrolling="no"><a href="https://medium.com/media/a249f8f41fb4bec581c8f35f28f3a1a9/href">https://medium.com/media/a249f8f41fb4bec581c8f35f28f3a1a9/href</a></iframe><h4>A walk-through</h4><p>Let’s illustrate the new features with <a href="http://evm.storage/eth/0x9557b6d8f6de42a77fa4f92787b60c7f880d4e3a526392ab3c051bac2fa60a7e">an example transaction</a>. In this transaction, a user provides ~13 USDC and 0.01 ETH to the <em>Uniswap V2: USDC</em> liquidity pool. Our invocation flow helps illustrate how that transaction was executed.</p><figure><img alt="This image shows the “Full trace” tab in the invocation flow on evm.storage." src="https://cdn-images-1.medium.com/max/1024/1*cNJQjv87gyX0s5hWCjq0Hw.png" /><figcaption>The “Full trace” tab in the invocation flow</figcaption></figure><p>The sender sends 0.01 ETH to <em>UniswapV2Router02</em>, calling <em>addLiquidityEth</em>. The router then performs the following:</p><ul><li>1: It staticcalls <em>UniswapV2Factory</em> to find the liquidity pool for the given pair.</li><li>7: It staticcalls that liquidity pool (named, rather unhelpfully, <em>Uniswap V2</em>) to get the current reserves.</li><li>11: It calls <em>USD Coin</em> to transfer 12.815313 from the sender to the liquidity pool.</li><li>42: It calls <em>Wrapped Ether</em>, depositing/wrapping the 0.01 ETH it received from the sender.</li><li>47: It calls <em>Wrapped Ether</em> a second time to transfer the WETH to the liquidity pool.</li><li>57: It calls the liquidity pool to mint the pool’s ownership token, assigning the balance to the sender.</li></ul><p>We described only a few of the traces. We have two ways to dig deeper:</p><ul><li>Click on the chevron next to any trace to show its child traces.</li><li>Click on any trace to open up a tab with complete details for that trace.</li></ul><p>Let’s use both of these tools to learn more about what happens when we deposit to <em>Wrapped Ether</em>. Expanding the children of trace 42 with the chevron reveals traces 43–46:</p><figure><img alt="Clicking the chevron next to trace 42 reveals child traces 43–46" src="https://cdn-images-1.medium.com/max/1024/1*A2Xmk8qcEVV-XIx3QeoDHQ.png" /><figcaption>Clicking the chevron next to trace 42 reveals child traces 43–46</figcaption></figure><p>Let’s skip 43 and come back to it. 44 shows an SLOAD storage read where the <em>Wrapped Ether</em> contract looks up the current balance of the router’s address–it’s 0, as routers typically won’t carry a balance between transactions. The <em>Wrapped Ether</em> contract needs to know this value to add it to the deposited amount to construct the new balance, which it then writes to storage in the SSTORE of trace 45. Finally, it emits a <em>Deposit</em> log, which contains the depositor and the amount deposited.</p><p>So what’s going on with the SHA3 in 43? Clicking into it reveals its trace page (see video below). SHA3 is a hashing operation that takes inputs (also known as preimages) of arbitrary length and hashes them into a 32-byte output. In this case, we see two 32-byte inputs. The first is just the 20-byte address of the depositor padded at the left with zeros. The second is 0x00…03, which is the slot corresponding to the <a href="https://evm.storage/eth/15724108/0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2/balanceOf#map">balanceOf</a> mapping in <a href="https://evm.storage/eth/15724108/0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2#map">Wrapped Ether</a>’s storage. This is the standard way to find the slot of a given mapping entry: you concatenate the key with the slot of the mapping and hash it. We actually covered this in <a href="https://blog.smlxl.io/how-does-ethereum-manage-data-3ee85263134b#e494">a previous blog post</a>. So the purpose of this hashing operation was simply to find the slot in <em>Wrapped Ether</em>’s storage associated with the router’s balance.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F882582714%3Fapp_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F882582714&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F1750695627-d390bcc468b14973ba068039c535e995e401ce96482fbdc9911e580665e9a501-d_1280&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1213" frameborder="0" scrolling="no"><a href="https://medium.com/media/69d22da518079bacf447c1d318b107fa/href">https://medium.com/media/69d22da518079bacf447c1d318b107fa/href</a></iframe><p>Alright, we got a little technical there–sorry! We anticipate most users won’t want to inspect transaction execution at this depth, but it also has to be available to users who do, as we discussed above.</p><p>We mentioned in the introduction the value of being able to navigate between transactions and the involved entities. As an example of that, suppose you want to know whether the user still provides liquidity to this pool? Use the link to navigate to <a href="http://evm.storage/eth/18479772/0xb4e16d0168e52d35cacd2c6185b44281ec28c9dc/balanceOf.0x65c3b4439434bf053aa9c5ab547a6f7e742b68df">their balance in the liquidity pool</a> and review the storage history: turns out they pulled out a month later.</p><h4>The roadmap</h4><p>What’s next?</p><p>We’re working to make transaction pages even more useful:</p><ol><li><strong>A graphical representation of balance changes</strong> (see image below).</li><li><strong>Decoded actions, </strong>i.e., a short semantic description of the transaction’s impact.</li><li><strong>Improved coverage for traces involving precompiled contracts</strong>.</li><li><strong>Trace search and filtering, </strong>and expanded controls on how traces are rendered.</li><li><strong>Better address resolution/linking + improved ability to view and copy raw values.</strong></li></ol><figure><img alt="A preview of the Flow representation of balance changes." src="https://cdn-images-1.medium.com/max/1024/0*2FGKFrBAmhNt57m-" /><figcaption>A preview of the Flow representation of balance changes</figcaption></figure><p>We also have two big launches unrelated to transaction pages coming to <a href="http://evm.storage/">evm.storage</a> in the next few weeks:</p><ol><li><strong>Externally Owned Account (EOA) pages: </strong>See any EOA’s token balances and transactions.</li></ol><figure><img alt="A preview of our EOA pages" src="https://cdn-images-1.medium.com/max/1024/1*MN0LCc_QO_QX2HMBNw8Dlw.png" /><figcaption>A preview of our EOA pages</figcaption></figure><p>2.<strong> ABI component on contract pages: </strong>View a contract’s functions, interact with them, and simulate transactions.</p><figure><img alt="An image that shows a form that enables a user to interact with a contract and simulate transactions. Also includes a “generate template” button so the user can generate a template for an interaction from a past transaction." src="https://cdn-images-1.medium.com/max/1024/0*y0f90hR7vx_gA_3g" /><figcaption>Our ABI component will enable interaction with contracts and txn simulation</figcaption></figure><p>From the design side, as we expand our coverage, we are exploring how we can better show semantic data, relationships between entities, and visualizations that help users break down complex data into digestible parts. If you have ideas or feedback, please <a href="https://t.me/+c0fPe4sYCKMwNzYx">join our Telegram group</a>.</p><figure><img alt="A plain blue image, used as a footer." src="https://cdn-images-1.medium.com/max/1024/1*4oovdvyicqfK8bXJkCY9RQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a4e66e312fc" width="1" height="1" alt=""><hr><p><a href="https://blog.smlxl.io/announcing-transaction-traces-on-evm-storage-3a4e66e312fc">Announcing transaction traces on evm.storage</a> was originally published in <a href="https://blog.smlxl.io/">smlXL</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>