<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>blueyard</title>
        <link>https://paragraph.com/@blueyard</link>
        <description>BlueYard Capital Tech Writing</description>
        <lastBuildDate>Sun, 22 Nov 2026 14:36:14 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[When Does a New Chain Make Sense?]]></title>
            <link>https://paragraph.com/@blueyard/when-does-a-new-chain-make-sense</link>
            <guid>9Taq03jJLCgQbn1PB4VE</guid>
            <pubDate>Fri, 27 Feb 2026 01:14:42 GMT</pubDate>
            <description><![CDATA[Most new blockchains shouldn't exist. The ones that should share a common trait: their domain logic must live at the consensus layer, not the application layer. Here's a framework for telling them apart.The ProblemBetween 2021 and 2023, the industry launched dozens of alternative Layer 1 blockchains. Most were general-purpose EVM-compatible chains differentiated by marginally different parameters—faster block times, cheaper gas, a slightly different consensus algorithm. Few had a structural r...]]></description>
            <content:encoded><![CDATA[<p><em>Most new blockchains shouldn't exist. The ones that should share a common trait: their domain logic must live at the consensus layer, not the application layer. Here's a framework for telling them apart.</em></p><hr><h2 id="h-the-problem" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">The Problem</h2><p>Between 2021 and 2023, the industry launched dozens of alternative Layer 1 blockchains. Most were general-purpose EVM-compatible chains differentiated by marginally different parameters—faster block times, cheaper gas, a slightly different consensus algorithm. Few had a structural reason to exist. They were fundraising vehicles first and infrastructure second.</p><p>But not every new chain is unjustified. Hyperliquid, Filecoin, Celestia, and Arweave all have defensible reasons for being separate chains. The question is how to distinguish the ones that need to exist from the ones that don't.</p><h2 id="h-the-framework" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">The Framework</h2><p>A new chain is justified when the domain logic must live at the consensus layer, not the application layer. Three criteria, in descending order of strength:</p><h3 id="h-c1-the-consensus-mechanism-is-the-domain" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">C1 — The consensus mechanism is the domain.</h3><p>Block production or validation encodes domain-specific work that can't be expressed as a smart contract. Filecoin miners prove they're storing data. Helium nodes prove physical wireless coverage. This is the strongest justification for a separate chain, because it is the one criterion that an L2 or rollup cannot satisfy by definition—rollups inherit their consensus from the base layer.</p><blockquote><p>If you removed the domain logic, there would be no consensus mechanism left.</p></blockquote><p><strong>Diagnostic:</strong> If validators stopped performing domain-specific work during block production, would the system still function? If yes → does not meet C1.</p><h3 id="h-c2-the-state-model-is-incompatible-with-general-purpose-vms" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">C2 — The state model is incompatible with general-purpose VMs.</h3><p>The chain's core data structures cannot be efficiently represented as contract storage on an existing chain. Concrete indicators: the domain requires non-account-based indexing (provenance graphs, spatial-temporal data), protocol-level privacy defaults (state that is encrypted by default rather than public), custom cryptographic primitives baked into the state layer, or data velocity so high that a general-purpose chain would treat the traffic as spam.</p><p><strong>Diagnostic:</strong> Would representing this domain's state as contract storage on a general-purpose VM be either technically infeasible or economically irrational? If no → does not meet C2.</p><h3 id="h-c3-vertical-integration-is-existential-for-correctness" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">C3 — Vertical integration is existential for correctness.</h3><p>The application requires co-optimizing block times, transaction ordering, and throughput in ways impossible as a tenant on another chain. "Existential" means the system would produce incorrect results, lose solvency, or fail under normal peak conditions—not that it would merely be slower or less profitable. Two variants: app-specific C3, where a single application needs to own the entire stack (Hyperliquid), and general-purpose C3, where the execution environment itself is re-engineered for all applications (Monad).</p><p><strong>Diagnostic:</strong> Would deploying this system on an existing fast chain cause it to fail—not underperform, <em>fail</em>—under normal peak conditions? If no → does not meet C3.</p><h3 id="h-on-l2s" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">On L2s</h3><p>The conventional counter-argument is that application-specific rollups can serve many of these needs. There is a structural limitation: an L2 inherits its consensus from the base layer by definition. C1 is therefore impossible to satisfy with a rollup. If the domain requires validators to do something specific during block production, no amount of L2 engineering can deliver it.</p><p>For domains that require only C2 or C3, the question is whether the rollup architecture delivers the needed properties without introducing equivalent trade-offs—centralized sequencers, fragmented liquidity, bridge risk. In many cases, deploying on an existing fast L1 is simpler and achieves the same result.</p><h3 id="h-the-disqualifying-test" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">The Disqualifying Test</h3><p><strong>If the domain logic can be fully expressed as a smart contract on an existing performant chain, and running it on a separate chain primarily improves the token story rather than the user experience, it doesn't need a chain. It needs a protocol.</strong></p><p>Most things that feel like they need a chain actually need a protocol that <em>uses</em> chains for the parts where chains add value—identity, settlement, persistence—and conventional infrastructure for everything else. Chat doesn't need a chain. Social media doesn't need a chain. Most DeFi protocols don't need a chain.</p><p>If a protocol depends on owning transaction ordering as a core economic primitive, it must meet the C3 bar: an existing fast chain would cause the system to fail under normal peak conditions, not merely that controlling the sequencer is commercially advantageous.</p><hr><h2 id="h-existing-chains-evaluated" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Existing Chains, Evaluated</h2><p>Two axes matter when evaluating existing chains: whether the architecture justifies a separate chain, and whether the execution has validated the architecture. These are orthogonal. A chain can be architecturally justified and fail in practice, or succeed commercially without structural justification.</p><table style="min-width: 150px"><colgroup><col><col><col><col><col><col></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Chain</p></th><th colspan="1" rowspan="1"><p>Domain</p></th><th colspan="1" rowspan="1"><p>Criteria</p></th><th colspan="1" rowspan="1"><p>Justification</p></th><th colspan="1" rowspan="1"><p>Architecture</p></th><th colspan="1" rowspan="1"><p>Outcome</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Hyperliquid</strong></p></td><td colspan="1" rowspan="1"><p>Onchain orderbook</p></td><td colspan="1" rowspan="1"><p>C3</p></td><td colspan="1" rowspan="1"><p>A matching engine requires sub-second finality, deterministic ordering, and burst throughput during liquidation cascades. Being a tenant introduces latency that is existential for a trading platform. App-specific C3: the chain exists to serve one demanding use case.</p></td><td colspan="1" rowspan="1"><p>Strong</p></td><td colspan="1" rowspan="1"><p>Validated</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Filecoin</strong></p></td><td colspan="1" rowspan="1"><p>Incentivized storage</p></td><td colspan="1" rowspan="1"><p>C1, C2</p></td><td colspan="1" rowspan="1"><p>Proof-of-spacetime consensus requires miners to continuously prove they are storing data. The consensus mechanism is storage verification. State tracks storage deals, sectors, and proofs—not token balances.</p></td><td colspan="1" rowspan="1"><p>Strong</p></td><td colspan="1" rowspan="1"><p>Mixed</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Arweave</strong></p></td><td colspan="1" rowspan="1"><p>Permanent storage</p></td><td colspan="1" rowspan="1"><p>C1, C2</p></td><td colspan="1" rowspan="1"><p>SPoRA consensus rewards miners for storing and retrieving data. The blockweave—where blocks reference both the previous block and a random historical block—is a data structure no EVM could natively handle.</p></td><td colspan="1" rowspan="1"><p>Strong</p></td><td colspan="1" rowspan="1"><p>Validated</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>AO</strong></p></td><td colspan="1" rowspan="1"><p>Parallel compute on Arweave</p></td><td colspan="1" rowspan="1"><p>C2</p></td><td colspan="1" rowspan="1"><p>Hyper-parallel compute using holistic process state rather than global shared state. Processes communicate via async messages; Arweave serves as the immutable log. A fundamentally different computation model than shared-state VMs.</p></td><td colspan="1" rowspan="1"><p>Moderate</p></td><td colspan="1" rowspan="1"><p>Early</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Celestia</strong></p></td><td colspan="1" rowspan="1"><p>Data availability</p></td><td colspan="1" rowspan="1"><p>C1, C2</p></td><td colspan="1" rowspan="1"><p>Data availability sampling is a distinct consensus concern. The chain exists to answer one question: was this data published? It deliberately has no execution layer. Its state isn't a ledger—it's a timestamped bulletin board for blobs.</p></td><td colspan="1" rowspan="1"><p>Strong</p></td><td colspan="1" rowspan="1"><p>Early</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Monad</strong></p></td><td colspan="1" rowspan="1"><p>High-performance EVM</p></td><td colspan="1" rowspan="1"><p>C3</p></td><td colspan="1" rowspan="1"><p>Pipelined execution, async I/O, and optimistic parallel execution require re-engineering the runtime from scratch. General-purpose C3: the argument is that the EVM should be faster for everyone, not that a specific application needs to own the stack.</p></td><td colspan="1" rowspan="1"><p>Moderate</p></td><td colspan="1" rowspan="1"><p>Pre-launch</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Story Protocol</strong></p></td><td colspan="1" rowspan="1"><p>Programmable IP</p></td><td colspan="1" rowspan="1"><p>C2</p></td><td colspan="1" rowspan="1"><p>IP provenance graphs, licensing DAGs, derivative work relationships, and automated royalty flows require non-account-based indexing that is alien to EVM state. Consensus-level argument is weaker—validators don't do anything IP-specific during block production.</p></td><td colspan="1" rowspan="1"><p>Moderate</p></td><td colspan="1" rowspan="1"><p>Early</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Helium</strong></p></td><td colspan="1" rowspan="1"><p>Wireless DePIN</p></td><td colspan="1" rowspan="1"><p>C1</p></td><td colspan="1" rowspan="1"><p>Proof-of-coverage requires nodes to verify physical wireless hotspot presence. Domain logic is inherently physical-world. Migrated token layer to Solana—domain proofs needed custom infrastructure, settlement did not.</p></td><td colspan="1" rowspan="1"><p>Strong</p></td><td colspan="1" rowspan="1"><p>Hybrid</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Berachain</strong></p></td><td colspan="1" rowspan="1"><p>Liquidity-secured DeFi</p></td><td colspan="1" rowspan="1"><p>C1</p></td><td colspan="1" rowspan="1"><p>Proof-of-liquidity embeds DeFi incentive distribution into block production. Validators direct emissions to liquidity pools as consensus-level behavior. Non-transferable governance token enforced at protocol level.</p></td><td colspan="1" rowspan="1"><p>Strong</p></td><td colspan="1" rowspan="1"><p>Struggling</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Render</strong></p></td><td colspan="1" rowspan="1"><p>Distributed GPU compute</p></td><td colspan="1" rowspan="1"><p>C1</p></td><td colspan="1" rowspan="1"><p>Proof-of-render verifies GPU output quality. Job scheduling and bandwidth optimization are domain-specific. Like Helium, migrated settlement to Solana.</p></td><td colspan="1" rowspan="1"><p>Moderate</p></td><td colspan="1" rowspan="1"><p>Hybrid</p></td></tr></tbody></table><p>The Helium and Render migrations are instructive. Both concluded that domain-specific proofs justified custom infrastructure, but token settlement did not require a bespoke chain. This suggests a hybrid model for many C1 domains: custom consensus where domain logic demands it, existing fast L1s for everything else.</p><p>Berachain's architectural justification is strong—proof-of-liquidity genuinely requires its own chain. Its execution has been poor: TVL dropped from $3.5B to under $150M, the token fell 96%, and the PoL flywheel reversed. Architecture and outcome are separate questions.</p><p>Filecoin's architecture is also strong, but adoption has been underwhelming relative to thesis. The network is technically functional—real miners, real storage deals, real revenue—but most stored data has been incentivized through Filecoin Plus rather than organic demand. The vision of becoming a decentralized alternative to S3 hasn't materialized at scale.</p><hr><h2 id="h-chains-that-dont-have-winning-implementations-yet-but-could-justify-it" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Chains That Don't Have Winning Implementations Yet but Could Justify It</h2><table style="min-width: 125px"><colgroup><col><col><col><col><col></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Concept</p></th><th colspan="1" rowspan="1"><p>Domain</p></th><th colspan="1" rowspan="1"><p>Criteria</p></th><th colspan="1" rowspan="1"><p>Why It Would Need Its Own Chain</p></th><th colspan="1" rowspan="1"><p>Hard Problem</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Proof-of-Inference</strong></p></td><td colspan="1" rowspan="1"><p>Verifiable AI</p></td><td colspan="1" rowspan="1"><p>C1, C2</p></td><td colspan="1" rowspan="1"><p>Consensus verifies bounded correctness of AI inference via fraud proofs or probabilistic verification. State tracks model hashes, inference proofs, and audit trails. Slashing challenges for incorrect inference need consensus-level adjudication to prevent chain halts during heavy GPU verification.</p></td><td colspan="1" rowspan="1"><p>Floating-point non-determinism across hardware and driver versions makes exact reproducibility infeasible. Fraud proof systems for inference are an open research problem.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Genomic Data</strong></p></td><td colspan="1" rowspan="1"><p>Privacy-preserving biodata</p></td><td colspan="1" rowspan="1"><p>C2, C1</p></td><td colspan="1" rowspan="1"><p>State stores encrypted genomic sequences, consent graphs, and computation permissions—private by default rather than public by default. Consensus requires ZK proofs to verify that queries executed correctly on encrypted data without validators seeing plaintext. Protocol-level privacy as a requirement, not an option.</p></td><td colspan="1" rowspan="1"><p>Fully homomorphic encryption is too slow for practical use. Regulatory frameworks don't yet recognize on-chain privacy guarantees.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Physical Attestation</strong></p></td><td colspan="1" rowspan="1"><p>IoT sensor truth</p></td><td colspan="1" rowspan="1"><p>C1, C2</p></td><td colspan="1" rowspan="1"><p>Consensus verifies physical-world sensor data through cross-attestation of hardware enclaves. State is a spatial-temporal graph of attested measurements. Data velocity is high and per-datum value is low—general-purpose chains would treat the traffic as spam.</p></td><td colspan="1" rowspan="1"><p>Hardware trust assumptions are fragile. Sybil resistance for physical sensors is unsolved.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Energy Grid</strong></p></td><td colspan="1" rowspan="1"><p>Real-time energy markets</p></td><td colspan="1" rowspan="1"><p>C1, C3</p></td><td colspan="1" rowspan="1"><p>Consensus validates metered energy production and consumption. Validators are also grid nodes, enabling the chain to reject transactions that violate physical constraints—a general-purpose chain has no concept of line loss, reactive power, or thermal limits. The consensus layer must be physics-aware.</p></td><td colspan="1" rowspan="1"><p>Utility regulation. Grid operators are unlikely to cede control to decentralized consensus.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Spectrum Allocation</strong></p></td><td colspan="1" rowspan="1"><p>Dynamic RF management</p></td><td colspan="1" rowspan="1"><p>C1, C3</p></td><td colspan="1" rowspan="1"><p>Consensus coordinates real-time radio frequency allocation across geographic regions. Block production is spectrum assignment—validators verify non-interference. Requires sub-second finality tied to physical propagation constraints.</p></td><td colspan="1" rowspan="1"><p>Regulatory capture by telcos. Licensed spectrum bands require government cooperation.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Identity / Reputation</strong></p></td><td colspan="1" rowspan="1"><p>Portable reputation</p></td><td colspan="1" rowspan="1"><p>C2</p></td><td colspan="1" rowspan="1"><p>State is a graph of attestations, credentials, and reputation scores with selective disclosure. Needs native ZK primitives for proving attributes without revealing them. Reputation decay and context-dependent scoring don't map to EVM patterns.</p></td><td colspan="1" rowspan="1"><p>This is the weakest case in the set. It meets only C2. To justify an L1, it would need mandatory ZK proofs for every state transition or consensus-level revocation enforcement—neither of which is proven necessary. This may be a protocol on a fast chain, not a chain.</p></td></tr></tbody></table><p>Several hypothetical domains—IoT attestation, energy, spectrum—share overlapping physical-world verification requirements. They might converge into a single "cyber-physical consensus" chain rather than existing separately. That convergence is itself a useful signal: if two proposed chains overlap heavily, neither may need to exist independently.</p><hr><h2 id="h-summary" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Summary</h2><p>The framework reduces to three diagnostic questions, applied in order:</p><p><strong>First:</strong> if validators stopped performing domain-specific work during block production, would the system still function? If not, the domain needs its own chain. This is C1, and no rollup can satisfy it.</p><p><strong>Second:</strong> would representing this domain's state as contract storage on a general-purpose VM be either technically infeasible or economically irrational? If so, there is a case for a separate chain—though the case is weaker if C1 is not also met.</p><p><strong>Third:</strong> would deploying this system on an existing fast chain cause it to fail under normal peak conditions? If the answer is merely "it would be slower" or "it would be less profitable," C3 is not met.</p><p>Everything that fails all three tests is an application. A protocol deployed on a fast chain. Not a new chain with a token and a pitch deck.</p>]]></content:encoded>
            <author>blueyard@newsletter.paragraph.com (Chad Fowler)</author>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/d4c71dc06c19f08dfad7cc5fb8ce626aa318026203ea4e7f6aab4f35de484091.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[Tokens Coordinate Resources. That’s It.]]></title>
            <link>https://paragraph.com/@blueyard/tokens-coordinate-resources-thats-it</link>
            <guid>b23fP4o0rZbOYFUFsQEO</guid>
            <pubDate>Wed, 19 Nov 2025 13:10:54 GMT</pubDate>
            <description><![CDATA[We’ve spent a decade arguing about categories. DeFi. DePIN. DAOs. RWAs. Infrastructure. Every few months someone draws new boxes and insists—again—that this time we’ve mapped the terrain. None of it matters. There’s one fact that explains everything worth paying attention to in crypto: Tokens coordinate scarce resources under adversarial conditions. That’s the whole game. Everything else is just different substrates running the same pattern. Look at what actually succeeds: Infrastructure toke...]]></description>
            <content:encoded><![CDATA[<p>We’ve spent a decade arguing about categories. DeFi. DePIN. DAOs. RWAs. Infrastructure. Every few months someone draws new boxes and insists—again—that this time we’ve mapped the terrain.</p><p>None of it matters.</p><p>There’s one fact that explains everything worth paying attention to in crypto:</p><p>Tokens coordinate scarce resources under adversarial conditions.</p><p>That’s the whole game. Everything else is just different substrates running the same pattern.</p><p>Look at what actually succeeds:</p><p>Infrastructure tokens coordinate the network’s own machinery. Validators stake capital, produce blocks, earn rewards. The system bootstraps and maintains itself.</p><p>DeFi tokens coordinate financial risk and capital allocation. Liquidity providers front capital, borrowers take leverage, liquidators enforce solvency. The market keeps itself honest.</p><p>TCOCS (Token-Coordinated Off-Chain Systems) coordinate everything outside the chain: physical hardware, compute, bandwidth, storage, mobility, human labor, data collection, location proofs, reputation.</p><p>This last category is where we’ve been blurry. We treat DAOs, DePIN, and other off-chain coordination systems as different species. They’re not. A validator set, a mesh network of hotspots, and a collective of open-source maintainers are all running the same loop:</p><p>Stake something. Do verifiable work. Get rewarded. Repeat.</p><p>Only the substrate changes. The pattern doesn’t.</p><p>TCOCS forces the real question; maybe the only question that matters:</p><p>What off-chain resource are you coordinating, and why does blockchain coordination beat the existing alternative?</p><blockquote><p>Not "is this decentralized?"</p><p>Not "does this need a token?"</p><p>Just: what resource, what coordination failure, why this mechanism?</p></blockquote><p>Most projects can’t answer that cleanly. They bolt on tokens because it vibes like crypto, or because investors expect it, or because they assume composability is magic even when there’s nothing worth composing.</p><p>But when the answer is clear, when you’re dealing with a real resource, real adversarial dynamics, and a real coordination failure that no centralized actor can solve at scale—then TCOCS stops being a category and becomes foundational infrastructure.</p><p>The next decade won’t be about new acronyms. It’ll be about pushing this pattern into every domain where coordination breaks down. Crypto is not about decentralization for its own sake; it’s about coordinating real-world resources with the same elegance DeFi brought to capital markets.</p><p>Not because it’s ideological. Because the old ways keep failing, and now we have another tool.</p>]]></content:encoded>
            <author>blueyard@newsletter.paragraph.com (Chad Fowler)</author>
            <category>depin</category>
            <category>crypto</category>
            <category>web3</category>
            <category>incentives</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/8cec8c12b171f5892268dc0297b68d063ad83955e299d8199afb794b72ac5847.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[How Crypto could take over real world payments]]></title>
            <link>https://paragraph.com/@blueyard/how-crypto-could-take-over-real-world-payments</link>
            <guid>FtAvagnwZa6JG8ijWdTq</guid>
            <pubDate>Thu, 04 Sep 2025 14:11:08 GMT</pubDate>
            <description><![CDATA[Over the last few months I've talked to dozens of startups working on solving real world payments with crypto. Though many are promising there is little cohesion and standards between them. To take on TradFi we need more cooperation. Let's explore all of the strengths and weaknesses crypto has, and eventually how crypto can win over merchants and consumers to be the default global payment rails. This quest begins with a simple, free, open source platform called FreePay.What is FreePayFreePay ...]]></description>
            <content:encoded><![CDATA[<p>Over the last few months I've talked to dozens of startups working on solving real world payments with crypto. Though many are promising there is little cohesion and standards between them.</p><p>To take on TradFi we need more cooperation. Let's explore all of the strengths and weaknesses crypto has, and eventually how crypto can win over merchants and consumers to be the default global payment rails.</p><p>This quest begins with a simple, free, open source platform called FreePay.</p><h2 id="h-what-is-freepay" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">What is FreePay</h2><p>FreePay is an open standard for in-person crypto payments. It is a set of specifications and software that will allow any user with any crypto wallet on any chain to pay for goods and services with a single NFC tap at any participating merchant.</p><p>FreePay is as free as possible being MIT licensed open source, having zero fees or middlemen, and enforcing no restrictions on the end user of the software.</p><h2 id="h-motivation" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Motivation</h2><p>Despite payments being the earliest use-case for crypto, in-person payments has struggled to take off. A large reason for this is many small startups were working on it each in their own way with their own tradeoffs and lock-in to certain chains/tokens/wallets.</p><p>There is little chance of taking on the billion dollar incumbents with a set of small startups if these startups don't even work together.</p><p>FreePay is an attempt to create a set of open standards, software, and hardware, that are completely wallet/chain/token agnostic. This way any company working in the crypto payments space can build towards a common specification instead of reinventing the wheel time and time again.</p><h2 id="h-in-person-payments" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">In Person Payments</h2><h3 id="h-where-traditional-payments-fail" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Where traditional payments fail</h3><p>Legacy payment systems incur high costs, slow settlement times, chargeback risks, and require layers of manual setup and authorization.</p><p>From a customer perspective in-person payments are fast and efficient, however from a merchants perspective they are a costly and cumbersome exercise. Credit card payments can take days to finalize and remain subject to reversal for months. They also charge high fees, often up to 3 - 5% of the cost of an item, which could be over 50% of the margin.</p><p>Additionally, traditional systems present significant barriers to financial inclusion, leaving approximately 1.4 billion people unbanked and without access.</p><h3 id="h-where-past-attempts-at-crypto-payments-failed" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Where past attempts at crypto payments failed</h3><p>There have been many attempts at real world crypto payments, most of which failed. Let’s cover some of the reasons why, which we should attempt to avoid if we want to succeed.</p><p><strong>Building a payment terminal and wallet that only work together</strong> - this is easier to implement, but distribution is vastly more work. You have to first onboard merchants without a customer base, then onboard customers to something new too. Even if it does work they're locked into a single network and company/app, which is hardly better than using the existing networks.</p><p>An even worse version of this is <strong>using a custom token for payments</strong>.</p><p><strong>Locking to one chain</strong> - Crypto has become huge and with it there have been an explosion of chains. Many people have funds on a number of chains and want to use their favorite chain when shopping. This doesn't mean you need to support all chains - Just Bitcoin, Ethereum and Solana would probably cover 90% of the crypto space. But locking to just one is like being a company that only accepts Visa and everyone with Mastercard is unable to pay.</p><h2 id="h-cryptos-unique-strengths" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Crypto's unique strengths</h2><p>There are a few areas I think crypto really excels at which we should be embracing:</p><p><strong>There are hundreds of wallets already</strong>, with hundreds of millions of users. We can leverage this and allow people to pay with what they already have rather than trying to introduce yet another thing.</p><p><strong>Open Source and Open Standards are our friends</strong> - Crypto is all about open source, open access, open networks, the more open we can be the more support we get from those who believe in freedom and opportunity (which is most people).</p><p><strong>Stablecoins</strong> make everything much easier to understand. Not only do people generally trust and like them more than crypto tokens, because crypto is such a great remittance device many people in developing countries already have them and can start their own local economies using the coins and wallets they already have.</p><h2 id="h-how-freepay-works" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">How FreePay works</h2><p>FreePay consists of a Merchant Terminal application (available in Android or NodeJS) and a Customer App (Android only). The customer app essentially acts as a bridge between the user's wallet and the merchant terminal. In the future wallets can adopt the FreePay specifications themselves and then the user won't need the FreePay customer app.</p><p>To use FreePay a merchant must already have a crypto address, this could be a self-hosted wallet they control, or an exchange. They initialize their device with this address as well as an Alchemy API key (which is free). They can optionally choose a set of chains and token addresses they will accept, by default it accepts all supported tokens on all supported chains.</p><p>When charging a customer the merchant first enters the total amount requested and clicks charge. The customer then taps their phone to the terminal. In the background the merchant's wallet requests the customer’s address, looks up what tokens they hold, determines the best token for payment and sends the user a payment request for that token in the exact amount they need. The user confirms payment and once the payment hits the chain the merchant's terminal will appear with a green "approved" screen (Fig 1)</p><p>The best token is chosen by the following algorithm:</p><ul><li><p>Stablecoins &gt; Base Currency</p></li><li><p>Cheaper Chains &gt; Expensive Chains</p></li></ul><p>Stablecoins are always prioritized as they have the most bridging options, cheapest fees, and most liquidity, and most merchants prefer being paid in a stable currency. If they are not available ETH or BTC can be used and it can be auto swapped to stablecoins if a merchant desires and sets their terminal up in that way.</p><br><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/66727f924f228cefa17a157d2dd6df07.png" alt="fig1" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAWCAIAAAAuOwkTAAAACXBIWXMAAAsTAAALEwEAmpwYAAACA0lEQVR4nJ1VobLDIBDkK+Iia2srz57FYqNPR2PR8eh4NJoPQOPx5/vmcW8ylLbTvK7IZC6E5fZuD3U/Ae+91npZFmMMER1xbhgWDxEloVpr/+HMnyehmJmIVENuSCkppRCRmUtDrdVaq5S6Xq+llJRSKWXfd601IoYQaq0551KKc+52u4UQjh/Vvu/GGESU9AXGGACYpmme58vlYoyx1opKtgMiaq2ttc45iRARAKzrKpEQwq9EtdaUUp9XrXXfd+ccAAh9jDHnPKgkx+wjzJxzfpBI1qWUuEMphYj2hhCC917e+zX3+10k7XeXs/Yl/MtgoK21OueWBtOAiNbaoYBnM3hH4Jw7zi583xMMNWBmObvWWp4A0DvgfwTMLDWMDTnnEIJ0zrquRCRafS8RMyOiNIxumKYpxjhslx6zfEcwLPuTKMa4risAICIRPVfl/oag1vqZgJm99+LnaZqwQWhijKlBBBwIxL2fJTqa95hCpRREVI8AAFksOAbJKYme21Qa1Hu/bZv33jlHRD3rPM/btj2331kfPNcghCBkW4P3flkW0a13+PcE6VWRY4xEJL0HAMuyOOdGAlFzyFScvG3b8bTWDveEDG1phBijpDjY5XUG4gyZxrqZGRoOcbz3IQThlq1loshw/JzBeYlKKX1a/+iir432elQ81+DMnXzm0v8BxE3IFAcdCPAAAAAASUVORK5CYII=" nextheight="800" nextwidth="1167" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>It is possible for wallets to integrate with FreePay directly, so their users don't need to install the customer app to use FreePay payment terminals. When this is done the payment flow looks like (Fig 2). I've created a POC with Rabby Mobile wallet and it worked successfully end-to-end.</p><br><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/44a68011afa1cdf36b53c9055b672778.png" alt="fig2" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAeCAIAAADCaIt+AAAACXBIWXMAAAsTAAALEwEAmpwYAAACrElEQVR4nK2WK5DkIBCGY0ePi4yKRCKRSGQkFovEjsWisehYLBrbHotenaujd1PZPPY2V/OJqcoEaP5+plsaH18s3/lopJTmeY6NnDP+/rBl+9jt1q2P2z9VwxgjhFBKUUqttafrj0d1y7KUUqSUQgjO+dZ+CIFz7r3f3XFZFu89mjTG7F6llLz3OedPBc65aZq6L6SUtuGcI4R0XUcpjTHOG7z3WuupIYTA9btdwzBIKZ1zHfoUvVxrTY3cKKUAgFKKMcY5Z4zhoQBQaw0hpJRKKfk7AOC9TylhqP66CL2UUjq6AgByziml1+ultbbWaq3neV6WJedcaz1uQS+trv40UGtdvbYlxkgIsdZihKZpopQOw6CUklKWUk4NxBj3Bn5QIISYpklKqbXGc40xlFIp5TFHbysoLcE45xg65PF4cM4ppe9REELIORtjxg0xRqXUlYEbCgBgzT/fwDgLIfq+B4DfGlgV7KofAIZhGMcRY0spRXeN48gYu4oBNpITBXg6Jh+uSCkxxqy1mKav18t7j2q01jdiAAB4qaFBCGGM9X3PGLs65V4dpJQIIaGxbQnGmK3rtu0spXRl4ERBrTXGaIyRUmKySykBALsFrsE9qwFsGL9VUErB7rgmO+c8hCCEiDHeddF5HWDz2+K9xzLmnAshMDDY9TjnWuv3VLIQAjX1ff9oPJ9PfLyagPM8/7aSc87OuW0Px+YaY9Ra1wbeD/N7jf+NSoaLco0x4rAax/H5fKK4ruuUUtM03ehFuRk+pimOORSEzPMcQkCr6wn/ryC1cXb16oYCY4xzbp262CqwedzrRac3BQCc+wghhFI6juMwDH3f4xA9sv3U+LeLnHO7/MGMstbi3D8SQrihAO7H4N5Ey2fK3vZVURqnp/zQ7ABgb2CdM2/nD/LQINeDRx+/AAAAAElFTkSuQmCC" nextheight="789" nextwidth="850" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>Each wallet will have its own unique AID (Application Identifier), this is a requirement of NFC tap to pay systems. FreePay loops through all known AID's to find what wallet the user has installed, then proceed through the standard process of requesting a wallet address and sending a payment request exactly as it would with the FreePay customer app.</p><p>The reason the terminal requests the users assets before sending a payment link is to reduce friction, so the customer and merchant don’t have to manually negotiate tokens and chains, it's all handled in software.</p><h2 id="h-the-benefits-over-traditional-finance" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">The benefits over Traditional Finance</h2><h3 id="h-merchant-benefits" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Merchant Benefits</h3><p>FreePay's primary beneficiaries are merchants. For the longest time they've been straddled with high fees, long settlement times, and the possibility of malicious chargebacks. Many merchants are completely unable to get a credit card facility because they work in domains the big credit card companies consider undesirable.</p><ul><li><p>Payments settle instantly onchain, eliminating chargebacks and disputes.</p></li><li><p>No reliance on banks or third-party approvals, ensuring global, permissionless access.</p></li></ul><p>By removing these roadblocks we unlock finance for the billions of unbanked businesses and allow them to keep more of what they make.</p><h3 id="h-customer-benefits" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Customer Benefits</h3><p>Customers also have many benefits. They are able to hold the currency of their choice and have it auto converted at payment time, instead of needing to always hold local cash. They are in complete control of their money with zero risk of being de-banked, and can spend it wherever they like, similar to cash. Merchants may also give more rewards or discounts to customers paying with FreePay because it saves them so much in processing fees.</p><h3 id="h-micropayments-made-possible" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Micropayments made possible</h3><p>Because of the zero fee overhead and tiny blockchain fees FreePay opens up many new possibilities for micro transactions. Now a hardware store is able to sell individual washers or fittings for a few cents, and many of the small farmers markets and fruit stands especially in developing countries are able to sell small amounts of items, without worrying about their payment infrastructure overhead.</p><p>FreePay has all the benefits of cash for merchants and consumers, but is available globally and with your choice of currency.</p><h2 id="h-distribution" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Distribution</h2><p>This article won't go into too much detail on distribution, as the aim of FreePay is to provide an open source, free core others can build upon. It could be taken to market by a DAO, a corporation, or another type or organization.</p><p>What is crypto's strength here? There is an army of profit seekers in crypto, let's get them distributing something the world wants.</p><p>A DePIN network would be a good model to copy. Many have achieved a supply surplus from token incentives, and are waiting for demand to show up. Now we have a payment device with demand but we need more supply.</p><p>The simplest way would be a referral scheme, though it would require some tracking so needs to be done by some semi-centralized org. Users could sign up merchants and in return they get:</p><ul><li><p>Some cut of the merchants fees (if this org decides to add fees on top of the device)</p></li><li><p>Token incentives</p></li><li><p>Future Airdrops</p></li></ul><p>If there was some small fee it would make distribution far easier because users know every merchant they signup is a passive income stream built on real transactions. The token incentives and airdrops would be the cherry on top.</p><p>Prior to scaling up distribution, FreePay will focus on setting standards and ensuring all the most commonly used wallets support FreePay payments. It makes sense to do this first as there is little downside to wallets implementing these standards, only developer time. There is a large downside to scaling too early before wallets are ready as users will experience poor UX and may never try it again.</p><h2 id="h-other-startups-building-great-products" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Other startups building great products</h2><p>Luckily FreePay isn't the only attempt to take crypto payments mainstream. Here are some others on the same mission:</p><p>PayWithCrypto - A startup out of Southeast asia has created a new crypto payment terminal which uses QR codes. They've already rolled out to many merchants. The downside is you need to select your chain and token before paying so it's a little more cumbersome than tap to pay.</p><p>YodlPay - Rather than working on merchant terminals or adding a credit card YodlPay allows you to pay using the existing QR code networks, sending payments directly from your wallet to merchant.</p><p>I've also seen quite a few hackathon projects building payment terminals which is great, however most were unfortunately limited to just one chain/token.</p><h2 id="h-conclusion" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Conclusion</h2><p>If we want to make crypto in-person payments globally successful it must be as friction free and open access as possible. We also must work together on setting open standards and systems to build composable and compatible pieces. FreePay is laying the groundwork to make this happen. It's a big mission but it can be done.</p>]]></content:encoded>
            <author>blueyard@newsletter.paragraph.com (Tim Robinson)</author>
            <category>crypto</category>
            <category>payments</category>
            <category>freepay</category>
            <category>pos</category>
        </item>
        <item>
            <title><![CDATA[Building a Crypto Payment Terminal]]></title>
            <link>https://paragraph.com/@blueyard/building-a-crypto-payment-terminal</link>
            <guid>fWhbI6Ao10VxWDojLsX0</guid>
            <pubDate>Wed, 02 Jul 2025 08:28:38 GMT</pubDate>
            <description><![CDATA[The most obvious use‑case for crypto is everyday payments, yet we still cant pay for every day goods and services without middlemen. I spent some time exploring exactly what's stopping this future. My goal: let anyone pay for goods or services, in any currency they choose, with no intermediaries — and make the user experience (UX) at least as smooth as tapping a bank card.]]></description>
            <content:encoded><![CDATA[<p>The most obvious use‑case for crypto is everyday payments. Cash is all but dead in developed countries, causing credit card issuers to have a de-facto 2% tax on the worlds commerce. Despite this we still cant pay for every day goods and services without middlemen, the original promise of crypto. </p><p>I spent some time exploring exactly what's stopping this future. My goal: let anyone pay for goods or services, in any currency they choose, with no intermediaries — and make the user experience (UX) at least as smooth as tapping a bank card. No one should have to sacrifice UX for decentralization.</p><p>So I built a payment terminal:</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/97feee929717589e6d73e36c47c38537.jpg" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAYCAIAAAAUMWhjAAAACXBIWXMAAAsTAAALEwEAmpwYAAAHdUlEQVR4nE2UaYgkZxmAa3fO3Z2Znt6e6aumj+n+unr6nJ6jj+qurrO/r+6qPqa7uucwOzubybgmyyZoViJuDEbwiqDEoK6LB4IQMIg/hEBA3F8L6i/FHyYmYoKoRCEmihD1k+qZjcJDUb+e533fHx9BgdxWrgg5XuVbqiipoqiKoi4JusRrEqdKnCaxmshqYlMVGVmoK2Nk3kXh64hvyFxD5RoKz8h8A3FNxLGI5SDLtpqs1OSI7XxJ5kRNhLoINQlqoqRLkiZJOuQ1F04VWUVsKmJDFuqIp2WeRhyNuNoD6pCty1wdsYzYqIoNWqzTPF3jajWuRjPlKoE4QRWhKkIdIh0iTXTtloJMuaVBXoe8gXgdcorYUMSGLjGaxOiQ0SUXTWI0t82oAiPWK/Wt9Y3MWimd3i7kK8ViOV/czBYId2qI3K8EdQg1STLlFlOp8kzDlEVFZMul4nom06yVy6Vc0B9cCYUjJBmLrCSi0VQikQYgm6ayaaq0lt7KZUL+ABkMxcmVxEokR1H5VHoccA8CdejOrkE3UMzkS/liW2sxlfIaSNXLG+u5bCFDEcQ0cW6WODfjQpxx7twsQUwuehY3MulkJBLw+TLJxCpJrgTJDEgRrlSSDIR0BM8ykK9slpo0vV0qFTP5UIBMxOI+X2Bu3js9szA1Pf9/XJqccjk/cWFhbiGfSuUAiIbDoeXlDACh5UAGAMJA0EDIlOVTujpianSzRiOejUUT8Ri47AsvLYXm573zC77JqYXJqblJVz3+mfogMHvxwkI2BdIglk4mAr6lZCRKBoM5AAgdIlOGpiwbCHV1TRFFkMyXS+UslQ0GEsEQ8Phi0Sgo5rN+P3l+enFixnN+emHccDkLTF6Ynr60BlbTyVgmmQj7/SG/P06S+VSKMMZ2S1E6mqZKMJ0q1Mu0xLDVciNfqNbK9OxiYmEpmc0WYnFATHoveYKLS6THG5ycmpuYvHR+4uKY2YmJmTRYzYFkDiTjZNgzv5COx7MAEJaC2mO7Icu17cZ2oZqhNlUIN9cbOSqbilEzF8Nzl4KhMFgKpTyLwVB0NRSLB8jIkj/s9fq8Xt/i4uWZmfnoCtmolOitAr1VzIBkOBBktjfo9RLR1Y2OZvRNm6MFvi6aUG81YSovheqHnuY1j/pk1PlM9uQOeXh31kslkhTiy3Q2kwhHIisr0SgZTUY21tdafAVyVaGx3axtltdzQX9gDQCVa7TqdaJvdQdWd2B2mbLI1WBb7cFGa3nrYO8+/vZ7+POv4y+8gV/G+OlX8fkgtxxeFajiPlnohtJGMIWCQAgkc5FohgKFTKqQSYNYLBImKQAkpqbxTY1jiYG141j9YadvKx2mgpo1FTaVNH/12i/x3b/j26/ij/0K334dX72PJ0AnEkujXMUJrDme6MgT2VtKPBwpVeIgkUxkqdR6Jr1ZzLVY2pQFQ+J0kTVEbhxo95z2wLEcx3J2LKdvdAB39egX+Cvv4Kf/gL/0Nv7E7/Gt3+GprZPA8mqTVTVWtSXLkEx9szkM59li3lDdZ0ORGENmDcSpEqtLnCFxhsgTA7s3sHuO5fTN/o4x6FuOAY1I7aHDn+EX3sVPvYmf+zN+8g38ubdxSHuWDFECqJrHH9m5+UTv8Y9aR9cHiU1hI68rjIaaOmJ1yOqIMyBvQM6UOFPgCae941jO0HYG1mDHHDidUYvRE/Th0X189z387B/xnXfwY7/Gn/0TXuh8PXiZUlKNnYc/fHDj8YPrJ8Nrj9jJrVZlw1R4HbIGYk2ZNxFvQsGEvAUFU5II9zi249jDgem4AXtXYoz4ev/g3r++8w/8zFv4a3/FT7+Fv4Vx6JGXPLMJI82K7cP+1UePbz21f3zDihRgo2KrvCHzrl0WLPQ/zgLDB4G+5QysXQN215ij43v//u7f8Kd+i5/7C77xA/y95/9TMH8UmAe2eUW//nHr8KY2OFF61xBVVtmaeRYQDFkwz+yiBSVDEoih7QztoWM7fdsN9M3dvtGv6zcf++n7P8H4q2/iFzH+xvPv/1x/TRNeDvpLUqONlNGVw0ebG1VVsTRWR82aqYqGLFiyaLqM7Ug4O9HQHg7bw1F75C7RHvbtUd8cSPYTg5f++enXsP4KRvdw6psYfBFHjt+NkhX/UnpxjlyYWfJe8PpmLmeilKmKpiJaimu3ThlvYELBcjcY20ed3b3u/ilDa2Q7t5Iv4PQPMfUipr6PwZdx8pM4uPOb9RwncQJDNyMRwDH16vYWx1TbGrSUlqW02qfILRuKpyeyoEQ4neGwuzvqje29g73uQyN7tH90O3n8SuLox6B3JwmfyTdOMsVOKsVsbdIbhQ0Qp7g63TNRR4dtDZqKu0FbaXXG9rbcsuTWacCUIOF0RqPe3l7/4JSD/sFuZ39v96RtOAbU2qreUdWupnV0vcULzVqdqdZaPNfRkam0TtWn47sbjO02ghaEFkQWhG5g2N1/oL7yoYHL/uDKqLfndHZ32sOe7fTsQcfsdUy7Z1od0+gZRldX2xpqq/ADLAW2FWgjZMmyiZAFkekGZAOi/wIcvW+qjIw5XgAAAABJRU5ErkJggg==" nextheight="1118" nextwidth="1485" class="image-node embed"><figcaption htmlattributes="[object Object]" class=""><em>It's not pretty but it works</em></figcaption></figure><p>Even when both customer and merchant have crypto wallets, the current flow is a hassle: decide on a chain, agree on a token, scan a QR code, wait for confirmation, then reconcile sales manually because none of it plugs into the merchant’s point‑of‑sale (POS) system. This device strips that friction away.</p><p>The merchant sets up their shop address and WiFi beforehand. To accept payment they simply input the amount you're paying, you tap your phone, and it automatically negotiates how to get payment to the merchant. </p><p>Even this is easier said than done. In testing I discovered only two wallets have the full capability of making this work - Coinbase and Metamask, and they don't have any native NFC integration so I needed to build a companion app.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/d1c097060482026a440500136ca2ad1b.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAA8AAAAgCAIAAABCTrX+AAAACXBIWXMAAAsTAAALEwEAmpwYAAAA33RFWHRSYXcACmdlbmVyaWMgcHJvZmlsZQogICAgICA5Ngo0OTQ5MmEwMDA4MDAwMDAwMDIwMDMxMDEwMjAwMDcwMDAwMDAyNjAwMDAwMDY5ODcwNDAwMDEwMDAwMDAyZTAwMDAwMDAwMDAwMDAwNDc2ZjZmNjc2YzY1MDAwMDAyMDAwMDkwMDcwMDA0MDAwMDAwMzAzMjMyMzAwMzkwMDIwMDE0MDAwMDAwNGMwMDAwMDAwMDAwMDAwMDMyMzAzMjM1M2EzMDM3M2EzMDMxMjAzMjMwM2EzMTMzM2EzMDM3MDAKr4vstwAAA6lJREFUeJzNlM9v22QYx9+ktG7TRE7apHY87CpxmzR2kjbzjzj2a9c/4vhHkjqt29I2naBIQyCNQcWB9oQEgk3bxDiUI+K4Cyd24S8Y50mMf4DLDnDbFQW5yTYxdtgR6aNH3/fRV++r9/u8ekEWBRtM0dKaBhSJLJKMAXT6XyRioMlVRI7B0nGwMAfyC9MknqRwdCkVLf8LiSVILLEwBwCRndGkqiHXVZEV6ytctTCGr9FjMW7yNZrIzoBlPLkfmMeh++6+37ObzibvbPKeIbga5xmCZwhGi1XFit6qUngCUFgi8PS+Z1qbkmupusJrMm/AptbidEXQFaFRK1fWisJGicISgMgiN4+NH74Ivz8fXJz379xs3/q4feuGffvT9t1POvdOnfufuRdn3Y/eUfPZGZBLI48fXB89uzt6+vXoz9ujP74cPTmP+O3zSP91Z/T0m9Gze7//9CE6PwUwNAY5emAxgVkZM7DYwGJfLC87DORWogTxdGyNzhfJHE0t0ctYkcoV3n4NqwUMQwGg8ORwu3Ny2H9v379+HPQsSRVYXaq+gtGqU3gSUHhi4MJre17gwP2+2bMVmSsr/NorqCIbZUJhiYGjhD7smqKtNhS+JHNlmSu3LusYqVGCAjPJ27OUnmtsuaZnq5os9Dtw24Nhd7Nry4EDtxxl4KquIZK5WZBfQL664f5yce3hd0cP7x/+/O1w1xVVqdaGDb1V11t1Q143olonsVmwlEYe/fj+6MnZ349OR7+ejh6ffbAn8/WSKlagwLzgcvJJgKGAoXGhSvIMJa0vX10j14p5liZYmmBWJoKl8+wqESWYX4hfrRbWK4UNpsCuXinT+Wr5CrtKTKAntVYi8Uw8eoMHg/bJYf/koBc4iiHXLdiwNc6EGybcsDWuDRsmXNcneWMJ32yGXX3LgTu+NgzdHV/r2bJvNj1TjDLpKL4laVI1uiWFJwJXHe66w9Adhs4wdHZ8zTNE32p2bck1BKlRkhql59OJ3HC46x5td462O8PQORjYw9A93vX2+sZez9j2tMCBniFGe5O5Wd9s9mx5fHrXkrqW5FtS4EC9VZUapfHkocBE00kjYCkFsvMRSymQuxTjiqEAz8RxFERk4mkERH9AauqNQKcv3W8O+J+708jr9Us1CyYXR6fBW8/7qamXOnLn5iIWEcDQBJGJLyIATwG+toKnomYejfTYk5sDAJuPWESAwjMUNruIACIT69qQyMQWEUDmZvoddezB5sE/H+D2/xVD6MAAAAAASUVORK5CYII=" nextheight="1118" nextwidth="516" class="image-node embed"><figcaption htmlattributes="[object Object]" class="">You only need to select your wallet once</figcaption></figure><p>The app auto‑detects installed wallets and allows you to select what wallet you want to pay with (ahead of time). The goal is to get wallets to add native support, so this app won't be necessary.</p><h2 id="h-how-it-works" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0">How it works</h2><p>When you tap the terminal it first requests the wallet address, fetches your balances on all chains the merchant supports using Alchemy, and crafts a payment link with whatever token makes the most sense - stablecoins first, ETH second. This then makes the screen pop up with the payment request and you hit pay. Payment only takes a few seconds.</p><p>Here's the full demo of it in action:</p><div data-type="youtube" videoid="dx5Wy1SSTvg">
      <div class="youtube-player" data-id="dx5Wy1SSTvg" style="background-image: url('https://i.ytimg.com/vi/dx5Wy1SSTvg/hqdefault.jpg'); background-size: cover; background-position: center">
        <a href="https://www.youtube.com/watch?v=dx5Wy1SSTvg">
          <img src="https://paragraph.com/editor/youtube/play.png" class="play">
        </a>
      </div></div><h2 id="h-the-flaws" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0">The flaws</h2><p>Here's every flaw I've found so far:</p><ul><li><p>There is no function to request the wallet address immediately, hence the need for the companion app. Reading the wallet address is necessary to read all the users tokens and create a transaction immediately. Otherwise you're back to negotiating chains/tokens. This could be solved with <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://eip.tools/eip/7811">ERC-7811</a> or <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://eip.tools/eip/2256">ERC-2256</a> but no wallets have implemented them yet.</p></li><li><p>Most wallets don't correctly support <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/ethereum/ercs/blob/master/ERCS/erc-681.md">ERC-681</a> links, either stalling or doing nothing.</p></li><li><p>No wallets support auto swapping before sending, this would be useful when you are on the same chain as the merchant but don't have any currencies they support.</p></li><li><p>No wallets support auto bridging before sending, this would be useful when you have tokens on another chain (this is less of a problem as a merchant can just support most of the common chains).</p></li></ul><p>If you're building a wallet and want to add these features, let me know!</p><h2 id="h-try-it-yourself" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0">Try it yourself</h2><p>All the code is open‑sourced, and the terminal repo ships with a script that burns a Raspberry Pi image so you can test with your own wallet today.</p><ul><li><p>Merchant Terminal App: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/FreePayPOS/merchant-app">https://github.com/FreePayPOS/merchant-app</a> </p></li><li><p>Customer Companion App: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/FreePayPOS/customer-android-app">https://github.com/FreePayPOS/customer-android-app</a></p></li></ul><p>Now the next big problem is obviously distribution - how would we get these payment terminal or payment code distributed globally? This is what I'll be diving into next article, along with other failed attempts at in person payments we've seen over the years.</p>]]></content:encoded>
            <author>blueyard@newsletter.paragraph.com (Tim Robinson)</author>
            <category>crypto</category>
            <category>payments</category>
            <category>pos</category>
            <category>terminal</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/8ebbf4c924ec60abe003369d89a31f7e.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[What's Actually Going to Make Crypto Mainstream?]]></title>
            <link>https://paragraph.com/@blueyard/whats-actually-going-to-make-crypto-mainstream</link>
            <guid>r7ftBkHCWH5K9wdqD5UP</guid>
            <pubDate>Tue, 29 Apr 2025 09:25:43 GMT</pubDate>
            <description><![CDATA[The first step to crossing the chasm isn't infrastructure or UX improvements, it's getting enough people to care. My overarching theory: Crypto democratizes wealth creation. It allows more people to invest in far more things, which gives creators access to more investors to build more great products. ]]></description>
            <content:encoded><![CDATA[<p>This is part 2 of the "How Crypto can cross the chasm" series. <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://paragraph.com/@blueyard/how-crypto-can-cross-the-chasm">See the first part here</a></p><p>The first step to crossing the chasm isn't infrastructure or UX improvements, it's getting enough people to care. Most things never cross the chasm into mainstream usage, because most things aren't useful to mainstream society, so why is crypto any different?</p><p>My overarching theory: <strong>Crypto democratizes wealth creation</strong>. It allows more people to invest in far more things, which gives creators access to more investors to more easily become wealthy from their talents.</p><p>Today you can invest in stocks, some ETFs, a house (which you have to buy one at a time). Maybe baseball cards, gold, or art if you're really esoteric. In a blockchain native world everything can be financialized - every game, movie, band, toy, building, company, product. Everything!</p><p>Crypto at it's full potential can allow anyone anywhere to invest in anything anywhere, as well as agree on investment terms and details up front, and permanently etch them online so everyone knows what they're agreeing to.</p><p>All of Crypto's most successful use cases were aligned with this - ICO's, DeFi, NFT's, DePIN and Memecoins. These had issues with scams and excessive jubilance, but the problem wasn't lack of wealth or investing desire, there were simply too many investors chasing too few good projects. This is a good thing! It shows there is appetite for this and not enough creators taking advantage of it.</p><p>If we cross the chasm into a world where all kinds of creators are building products and using crypto to allow anyone to invest and participate we'll be in a much better place.</p><h2 id="h-crypto-is-participatory-finance" class="text-3xl font-header">Crypto is participatory finance</h2><p>For most of human history there was zero participation in wealth creation, you were born into it or not. Since the enlightenment age some people with skills and connections could build a company that creates wealth, but most normal folk can only passively invest in big established companies. Most employees and workers receive no benefit when the company they work for grows in value. They also aren't able to invest at the earliest stages when a company needs funds the most, or have much influence over the outcome of their investment.</p><p>With Crypto you have direct ability to influence your wealth, and contribution is encouraged. You don't need coding skills, exceptional talent or management ability to improve your wealth. You can be a community member who evangelizes or connects with other fans, or a hipster who has an eye for new trends before the rest of the world realizes, and you'll grow your own wealth while supporting the things you enjoy.</p><p>This is also why DePIN and staking rewards are such powerful concepts. Projects no longer need to raise millions of dollars and hire thousands of employees to build out a network of nodes to power a service. Instead they can issue a token to reward participants and grow organically from people wanting to contribute, and everyone wins together.</p><h2 id="h-the-rise-of-the-indie-investor" class="text-3xl font-header">The rise of the Indie Investor</h2><p>Isn't it weird you can put $10 into a stock but you generally can't be an angel investor for less than $5k? This is an effect of legacy systems which have too many costs and overheads to allow for thousands or millions of early investors. Crypto unlocks pre-angel micro investing. <strong>This is the rise of the indie investor.</strong></p><p>Most of these projects won't have venture scale returns, and many will fail, but this is totally fine, because this additional capital will help plenty succeed where it wasn't previously possible. Through the democratization of investing we're going to see a lot more creative experiments in the world and a lot more people helping push them through the early stages when the going is tough and most companies fail.</p><p>It's company evolution on steroids, where we have a pool of millions of experiments happening every day, the best ones succeed and attract attention and capital, and the rest fade away. But this model of democratized wealth will give 100x more people the chance to build something great than they were able to before.</p><p>I work at BlueYard Capital, a Venture Capital firm, why am I advocating for this open access to investing? Won't this hurt our returns?</p><p>BlueYard operates at the seed and pre-seed stage of investing, and our minimum check size is $500k. It would be extremely beneficial for us to have more companies survive to this stage of growth and have a more passionate community and investor base behind them when they do. We'd also like to work with the best indie investors to help companies they believe are great get to the next level, it's a win-win setup.</p><h2 id="h-is-this-all-crypto-unlocks" class="text-3xl font-header">Is this all Crypto Unlocks?</h2><p>There are still plenty of other potential activities cryptocurrencies can enhance, but being able to invest and participate in wealth creation and have it tie in with the things you do in your every day life is a big shift in society and could easily take crypto across the chasm all by itself.</p><p>If you're working on platforms that enable anything mentioned above, allowing peer to peer investments or open participation, I'd love to have a chat! You can reach me at tim@blueyard.com or ping me on Twitter / Farcaster/ Telegram at @timjrobinson</p>]]></content:encoded>
            <author>blueyard@newsletter.paragraph.com (Tim Robinson)</author>
            <category>investing</category>
            <category>wealth</category>
            <category>crypto</category>
            <category>mainstream</category>
            <category>crossing</category>
            <category>chasm</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/3f7095c28b3162b9e47ff43e5884c87d.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[How Crypto can Cross the Chasm]]></title>
            <link>https://paragraph.com/@blueyard/how-crypto-can-cross-the-chasm</link>
            <guid>Yt07Iii9sXq138E11Xe1</guid>
            <pubDate>Wed, 23 Apr 2025 08:42:27 GMT</pubDate>
            <description><![CDATA[Crypto is attempting to cross the chasm into mainstream society and is stalling out, but why? Why don't we live in a world where value flows as easily as information and anyone can pay or invest in anyone at any time? 

Over the next month I'll be releasing a series of articles covering the improvements necessary to cross this chasm and take crypto mainstream.]]></description>
            <content:encoded><![CDATA[<p>Crypto is clearly attempting to cross the chasm into mainstream life and is stalling out, but why? Why don't we have a world where value flows as easily as information and anyone can pay or invest in anyone at any time?</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/b53d04ddd8111f0dfe8706e53a1366f1.png" alt="chasm-modified" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAASCAIAAAC1qksFAAAACXBIWXMAAAsSAAALEgHS3X78AAADJ0lEQVR4nLWUW0gUURjHPyLwoaDoQlJSUD5IUNZzCApB9BTlpRJFM7M08t0H8aVeFLGSxIekQKItE3U1W9tVMzS2NXUcd5zVNXfbvK5a28xexjNz5sTM2fWybSJBf/YyM+c73+/8v3PmA/KfBfQPY4wQ4nne4XCwLCuKIiFkcXHR4XBwHIcQojEYY0JIIBBgWdZut/M8zzDM1NQUjqV1gByRT9fKyookSbIsB4NBjuPm5uboKEJI+yIkSdIPXTTY5/OtB0REr8MAhNAacKM2xhGiEhKJiRUcJVqSdQcxARpYUXSASpNiFJRDfjqqKsrWgG05wNpCVrUYv3ei8XJ/GZTt2FN9OnmeGday/J2xLQe0mgpWZb/X9mBnZxZYiuA2wCWAPIBJc9cWjE2ALR0QGa2O1CR1XoPuIjAXQzFAFkA6wA2A2eEhGvZvJVJXpRAhxPmmkGa3FIYB6QDXAa4AlAII3oWYjOgS0SpRqdqeaj90Gvv4jCkXum9tAmQBXAXIAMhOvTA1u6ivUla36YDGhSThlaUiIIfG61NMOTEAGQCFAAdhNyScsnMTkYXiGA5WERphGOugzWq1sl+Ggj7BtcCUN6QVVB6QVMzVxQakA+QDJO5LAE3xNXUNkdThU7PJgV8U5ZAU9PsNtoHsxqqblYczK+DewyRJVbi6c6YcPXuBBrijp86MAI7uigeI0xlw/Gxas9GEFRztgBDi/rlS9ckMj8oh9zyUXCytTSyqPlRae1ID1KeY8+HDXegrBksJlOjZ83QT+QAn9h7RAfv1DwDEHUtOvV/5xPnVTTOHN5mZ9zy39tT1dHZN2pl595hzoO9z+6RbO4Uhr+PbYMu0rdU92Ca4BmZs1tF2o/nZ06HW5u8DH0eHmPe9/QZD08sXr5vftBkMTR1dPca3FoYdXy8R3WEnz/eauui12+VubelYWloO+/PMdLzrHh1z0Fvv0nKT0ej2eOitFAzOulw8OzphH5uZno46r+ESqYRIkiSIgqKfVNpZaRG1XcP4l94yCVa0VxdjURBkvVMpGCv6mgRRDAQChBD6ZFO73qbW5mxs938ORTn4DTAMkE2PKX13AAAAAElFTkSuQmCC" nextheight="720" nextwidth="1280" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><br><p>Over the next month I'll be releasing a series of articles covering the improvements necessary to cross this chasm and take crypto mainstream.</p><p>As I see it now, the two biggest problems are UX and Safety.</p><p>UX is the obvious one - we continually have more apps on more chains in more places, causing the UX of most crypto wallets to be way too complicated.</p><p>Why do we still have this UX complexity? At first, it seems like a technical issue, we need better devs building more chain abstraction and intent networks to carry out user demands. This is a good start, but after talking to a number of wallets, I've realized there's a deeper issue: user safety.</p><p>Most wallets don't want to simplify and hide the underlying tech, because there are many risks involved in doing so - chain failures, hacks, user errors. Wallets don't want to have user funds disappear and be held responsible for it.</p><p>If you think about any wallet wanting to abstract away the chains, a number of problems surface:</p><p>First, the user issues:</p><ul><li><p>What's the best chain to keep funds on? Should it be the most secure chain? Should it be the cheapest to use? Should it be the one with the most bridges?</p></li><li><p>What if users send funds on a chain the wallet doesn't support? How do users know what chains the wallet supports? How can they tell if their friends wallets are compatible?</p></li></ul><p>Secondly, there are the chain risks:</p><ul><li><p>What happens if a chain fails? Do users lose all their funds?</p></li><li><p>If a wallet wants to add DeFi applications or even simple ways to earn interest, how does it ensure users funds aren't hacked or lost in the process?</p></li></ul><p>What are the solutions? Here's a quick overview:</p><ul><li><p>UX Solutions</p><ul><li><p>Better interop standards:</p><ul><li><p>Addresses that include destination chain information so wallets can make informed decisions before sending funds</p></li><li><p>Solver / Intent networks</p></li><li><p>Bridge aggregators</p></li></ul></li><li><p>Just in Time Bridging - Where apps can accept funds from any chain, and they are bridged/swapped automatically to the correct token on the correct chain.</p></li><li><p>Better connections between app and wallet:</p><ul><li><p>Much of the friction can be attributed to the exponential number of new apps and wallets, and their inability to talk to each other correctly. Wallets should know how to inform an app about tokens available on other chains.</p></li></ul></li><li><p>SDK's that handle all of the above, so we're not re-inventing the UX wheel with every single app.</p></li></ul></li><li><p>Safety Solutions</p><ul><li><p>Better insurance:</p><ul><li><p>Easier integration points, so users can purchase coverage for all their assets with one click.</p></li><li><p>More coverage of more protocols - how can this be done seamlessly, can aggregators make this happen?</p></li><li><p>Cheaper coverage - There's no reason users should have to pay 5%+ per year to insure against chain failure or failure of major proven protocols like Aave/Uniswap.</p></li></ul></li><li><p>Better hack prevention:</p><ul><li><p>Services which can automatically detect possible hacks in progress and front-run them, or trigger circuit breakers to prevent an entire app from being drained.</p></li></ul></li><li><p>Risk Analysis systems:</p><ul><li><p>Having all risk information in one place is a very useful tool. Especially if it's available just in time as you're about to take an action.</p></li></ul></li></ul></li></ul><p>Some articles may cover a specific area, while others may discuss a specific product.</p><p>If you're building in the crypto space and want to help crypto cross the chasm, subscribe below to learn about solutions you can adopt, and what still needs to be built. If you'd like to chat or have an article written about what you're building send me an email at tim@blueyard.com, or ping me on Twitter / Farcaster / Telegram at @timjrobinson and we can discuss it!</p>]]></content:encoded>
            <author>blueyard@newsletter.paragraph.com (Tim Robinson)</author>
            <category>crypto</category>
            <category>ux</category>
            <category>insurance</category>
            <category>abstraction</category>
            <category>intents</category>
            <category>wallets</category>
            <category>apps</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/be2b4fdf63df2fc3611305bee6947408.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[How Ethereum can solve L2 liquidity fragmentation]]></title>
            <link>https://paragraph.com/@blueyard/how-ethereum-can-solve-l2-liquidity-fragmentation</link>
            <guid>e8MtIKeVRe0ioHJebIp9</guid>
            <pubDate>Mon, 05 Feb 2024 18:13:17 GMT</pubDate>
            <description><![CDATA[Exploring every upgrade Chains and Wallets can make so the L2 ecosystem feels like one chain.]]></description>
            <content:encoded><![CDATA[<h2>Why liquidity must flow seamlessly</h2><p>Last weekend all my Farcaster friends were talking about a hot new coin - $DEGEN on&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://base.org/">Base</a>. Feeling FOMO, I checked out my&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://rabby.io/">Rabby</a>&nbsp;wallet to see how much I could invest:</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/77a0eb50e3e621c0a51e8a6126c4efa8.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAICAIAAAAX52r4AAAACXBIWXMAAA7DAAAOwwHHb6hkAAAAEnRFWHRTb2Z0d2FyZQBHcmVlbnNob3ReVQgFAAACcklEQVR4nD2SXUhTcRjGH0FzenY+3JajgrzJUrqIQNEKoiAwL1Lyrguzb7B05dx2zj7OcR5dogYqzFCT0qahQhdGK0ImNJQETcsLsSYVeaGgLZGQIurEe5zBj5eXc/G8f57zA6xNMDUiQ4WpgXa+jrAGINTDKMOiQvDTF7MKUz1S3YATBgm8QgvjRoYC3reDB9x/3GAlApl3YWns6osxp0JIknDsYcrJfqR4cDi458wgOAVZrcjpoBuCcqj4SemVcHbRADLVwrIR5LZjlwhB1qPdiVxCjzaKBJI93X2xxaU/nY8+5pc9Xd/Qdp8OIadjLa4Vlz/H/ub1Da0nFKP3mv3nr77o7vuwuPS7Jfh+PBofj8axL0BZvBecrL9ah/HQTBxI9V24FZmc/pFVNDg8ury8ovma3rZ1Layuaf3Dn5HVXCVFQ8NfgBpqA5XF5aP+lpnW4HxHz8Ls/Bby7wMO8E5wNeBE8HawTnBVYO1gJDAuwKRW2MaVltnpd1uRaNzpn3oZWZuY2lTvzb1+8z27aODc5fDI6FckizgShMUf+/QXeZ2wquGx1Z+/NOxtACOeMF8vEK6Bsx/kb5SaK0rMF8/yl8DYwYiAUamwRb5taHd8kyjsnZja9AZmkNv+7NXKg8dL4OS8kqHy6jEcaK2RJ3E0GGibA+ywqsHeheNlQ0iq1au3sVwlWAcYG9hKMNXgbsJ4G2kukCcpHhT0JiQR/GBlpLupU6MHnJf0YL20sLoqBpESBZkm7AlbGDdBi4S07SlSusFBFdENViYRLfUw+WHWyVAIoY5CyZMdC7eFYSWa/M6fNLqobsaFdCeR5oChdpt/Cx7r9rIO1rUAAAAASUVORK5CYII=" nextheight="48" nextwidth="188" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>"Ok cool, I can put $500 into this coin, just need to sell some other assets. What does my portfolio look like anyway"</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/213459c4bdba2276dbbc66e2667e931f.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAPCAIAAAAK4lpAAAAACXBIWXMAAA7DAAAOwwHHb6hkAAAAEnRFWHRTb2Z0d2FyZQBHcmVlbnNob3ReVQgFAAAEZElEQVR4nJVU208jVRg//4GPZt94cI0xGn3QuOqDl8SHjW8SoijrBjdguUgAkeUiLLtLUYEuhXLdLlAoUCgtrdM6u0PpQKFXykUQwqall53pTOfSOb1SEtHEdErMZkUTky8nX873nd8v53d+3wFhIhIMRUiKZliBYQWa4TkehkmapNj8enDkyycsD2mGz0c4QpNUNEjQx4GwPxCixE2Wh2JPLExEKJrLI4PRKQt4paZvaLakVFJYfEPa3V98XWJCLT3yYRTDDcgvAIDLL740MDL52bXy7zt+am7vGh1X64zo4PCDJzD1EQDvASB7oK6ouVlaXnujor62sd2Cb/QplE7PDkFGAbqyVfT1CIa7dUYzYrZgljWNFtnc2rPi9u3dQ5dnCwDQ2NTq2flNZ0Qxi82C29fsbu/OgRXfCHHwh3c/7nj9g/WtfTNqMZgwnRF9iOH7hz7c5tg/fBwmIoBmmEQiRjM5BVgekhTL8ZDhICfESSoa5bizP/4U81wDx+f2ObEtkz3l+VgknqJTJxwPYSLFCfFkOsOwQpiIkBQbCpM5ieRSPQBX+/tmPv2yvO1O9y2pTK5Q4jbH/Yk5io++WVD5VkFlz+BQdV2LXKEsLa81mLCJ6QWCCALw6iefd/XeUxRfkzS23q2ua0bM2NSs7sgXCIYivmMiGBLfYFq5/EbBN2bTmtZgWlwyr9s37U6v3elFzJYwHZEU9pYX9mKrq4tL5lWbS6NF1uxu8yMrzTCXnn/5nfdLNpwejdaIYlY98mjd7kYx/MgXzEOfE9AMe3b2e5ThMtlTASYEmMprde4lnolnUsl0JpXJCjCVU48VGA76A6GT7Ek2m00kTwSYyPeTVJSiuafRcwS4zfXC21f1yPIX1ysGhibqm27JB5WqWa3Hvds+NgwuX/pxcKxMUl/zXdttqcyMWpCH1h2HuxCAvrLK6pa7be1StUavM6J2pzdM0v5A6FmCvYPH33YpbA6vSr0gimBEMXzN4Tk49CkNuitlJQhmnZnTqzV6E7ry6/6Ra3vvYHuv8bUrerlietGk0SJ2p3dza2979yBM0s+g5wgoKprNZhmOi8WTOZOI+jCsEAxF4sk0hMkowwkwkUpn8h4jyCgdh1z6hI4lBAjjyXR+PEmK/Sd6jkDSNAfAc82dE01tHW13eqTdA3rk0bweEWCqqKhoYXHpZqtUpV4or2owoSsT0wtUlKr7Stk7iHV19za1dVXVNd8fV6s1eqdn5+IbyEYwAD5UabBJtUal1uWvjNscNBPrVwya0eVFA4rbXOPT8w6X12LdCJDkTMcCMrX+M4ap1NqZecOa3S1O5b9IxPGxs7MsJ8CT7GkqnYknkgwrcHzOJ5wQp2gu9/OQNMtD8f9hjwMEDWMRlhFLMVG36N9jdQFBQ0MjAKCzq6eqrqWpvfO2VKYzolqDOW8JfzDsOyb8IfJpe/j9T44DRK4qRiB0PlMXE8hk9wAAY+OTo+Nz4yrNzLxBlMj1H2f+V/wFWrQ8wEkPMPUAAAAASUVORK5CYII=" nextheight="164" nextwidth="343" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/5b5d04ff1b0ea3fd805ab56a8a2fc57a.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABsAAAAgCAIAAABsC5RsAAAACXBIWXMAAA7DAAAOwwHHb6hkAAAAEnRFWHRTb2Z0d2FyZQBHcmVlbnNob3ReVQgFAAAFVElEQVR4nI1WW3ASVxg+05m++NwZ+9Rpp5mxT7085K0ztk6trZ067bTTmXba2kmsWm2a3tRMR8tkIlhjEpMUElwiJKAhojS44uKGQCgXTdgEg8aEoEiSSgoLJGYJZ4EDbAdWEblUv6fds+d8+3/f+f//HGAZMwHwbEeP1nV9qvVEl1KlbuvoFkswCCGXB0LIbneMGE1Go4mmw/mRNPc4UB78M9i48TkAwDMbXqIo6utvdh/5vUXQLOroEhcYIYTqC9rOHumJbnEgsMyvLxBxHBcMhQ4cOtwibP1q564RoxEEAsubNtVMUeM6nJBifXKFsrCARyabcS56tVNWzYQlk82URMfzLi0FgiHav7DEMAzgR1k2yUcOIVssoVhU+XhFAI7LAgBe31xPEPpdexre2rq9RBqEUDFwtvWkGL9sMJst5aQQQrvdce2a0253+Hx+gBB69Y1aatKN4/rObsmcx1seIGUyDWOYy2JB2Wy66Cs/MxKNHhEc3bvvR7EEs9ocD1QjhHy+u54yOh5Bv9/jdP5711dNKULpgsU5xtra2pqamjhkCYLskyvvr62VxDgzOzfpvuG946/2y2LkGEEe9mvOnXW79zX8XOYjq1Zr2ttOGgyka9pdzMgn5srKaouwVdAsEkuw8XEnSKaSruvXEUIEQWo02ooh3LTZDKf7XKOjHMcV+8iDYWKEwagdxs1jf/sXlnIxwvU4XI9nslmEUPkCniXBsgmW5Z4CgE34agB4DYD+i3rh0T/efX+HWIIVz4hDSJBG9QXdsbZOn+9usSEF0HTY4/EGAsu5DL/jvrT9RXCurUl1Hu/tlY2ax27feWxPEUJjBNHfflIzoGKTyRIunl0swbZs/WDXnu+HNNpchmcykOOyVpvDSU1WFOJzT1OkIXDbU00pyhcbhBAhlPOxt12jU5sSKZamw3Oe+ZWVlZLZq2tMZPU+HYkW2sf/+di0vxMAsHHD21i/rKHx4PYPP9Hh+pIqlPTIBM1CQbOw3Ef+mTAYxRKs+8/eXM2YrzgBeMGov3p2SN30m0CpUpf/dmFm5lJvL0WS5dnDM1ptDqVKLcXkTmryQRXyscQhTKZS5YxphNj19VQi8UTJ3MOaeX7Le/U3brrlClVD46+Li0slqk1mywWd3n51YnzcWbEEIIT319YYJvZgZwAAjT80nRnUtAhbpVhfSetHCKn7lV1Hj5mvkP6FpfLOxHGcFOv76NMv6nfvJwjyUe9xUpMEQVYMweOctP+lvXXVUU0pw8Qi0WgwRDNMLMcYia4sLN5DKM0wDE2HSw4mPtfikGWTSYaJPaWPoL7hoFp9/qdfmurqvytJOgihfEB1rK2zYg/nX8esDimm0Gi0MzO3AITsnm/3hmlah+ulmLw8ijRCEyMjw2IxRZKZx3t4gRHH9YJmkaBZZLFYH/lI0+FgKFTRRyYaiQTurdL0EyVzHAf+8cy/DEDj5m3e5eWLukuSHlnJXkPITlAuo9kSiUarsaDiG0DDm+8AAF4BwDIze0oqUw2eC4ZCJYw6re40Jpufna3IxXGcUqVu/PnQ51/WaTRasErTjZu3Bf1+/LJhetpd8RLicTop0nDTaq0WYyQavRdYnvN4aTqc8zGRTudTBDJMjGGYvILcSGEBhGwylcpks0/l46khAwCgrqHJOz9/4NDhHR9/VlKFDBMbHr4oVyg9Hm81Fgih1eaw2hy5c0Y8oAMAHJdpqImJFmGr6Hi7avCcQnlm6OEpBiGL43qR6ERJby8GTYc7usT9ysErI6M51bF4LqWnpqZxXE8Q5IjRpFCeKVRk7k5BuQiCDIaekD18tv4HPd/C4g0iDpcAAAAASUVORK5CYII=" nextheight="448" nextwidth="377" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>"Oh no"</p><p>Almost every token is on a different L2. To acquire $DEGEN I must perform multiple bridges and swaps, one after the other, to get there. Even with low fees it's still a frustrating hour of bridging and swapping.</p><p>We must solve this, and our north star is making the entire Ethereum ecosystem feel like one network. Lets see how unified liquidity, combined with wallet upgrades, can abstract bridging away and make the cross-chain L2 experience feel like using a single chain.</p><h3>Bridging shouldn't need to be done</h3><p>Why does bridging currently suck? There are a number of flaws:</p><ul><li><p>You must visit a separate website, connect wallet, approve, transfer, pray it arrives on the other end…</p></li><li><p>Bridging often takes 5 - 30 minutes to complete, which is far too slow. Less than 10 seconds is achievable and ideal.</p></li><li><p>Most Bridges require locking liquidity on both networks. The more L2's we have the thinner this liquidity gets. Low liquidity makes it hard to move substantial amounts between chains and you'll get a worse price as a result.</p></li><li><p>Only certain tokens with liquidity can be bridged, for most networks this is ETH + Stablecoins.</p></li><li><p>There are wrapped token bridges which don't require locking liquidity up and can support any token. However after bridging you get a non-native version of the token you desire and must swap it for the real token in order to use any apps on the new network, which requires liquidity, and thus we end up in the same trap.</p></li></ul><p>Most of all, if bridging doesn't&nbsp;<em>have</em>&nbsp;to be done, why are we collectively wasting millions of hours doing it?</p><h3>Wallets and Apps should handle bridging automatically</h3><p>When you use a DEX or Lending protocol it should track your tokens on all chains. When you deposit a token from another chain it should automatically bridge it to the correct chain in the background, so the process feels exactly the same as Ethereum Mainnet.</p><p>Apps and Wallets&nbsp;<em>want</em>&nbsp;to make this happen, but the underlying infrastructure isn't good enough. If it takes 10 minutes to do this bridging and you lose 1% of your tokens in the process, most users will hate the experience.</p><p>Lets dig deeper into the infrastructure layer to see how this can be fixed.</p><h2>How liquidity can flow seamlessly</h2><p>There are 3 main ways for liquidity to be unified across L2 networks, and one enhancement to improve their speed. These methods have different trade-offs but complement each other.</p><p>They are:</p><ul><li><p><strong>Shared Ecosystem Bridges</strong>&nbsp;- Enabling seamless aggregated liquidity across an entire ecosystem of chains.</p></li><li><p><strong>Mint/Burn Tokens</strong>&nbsp;- Which can be transferred in unlimited size between any supported chains.</p></li><li><p><strong>Native Bridges Trusting Each Other</strong>&nbsp;- Enabling cross-ecosystem aggregated liquidity.</p></li></ul><h3>Shared Ecosystem Bridges</h3><p>When you bridge from Ethereum Mainnet to any L2 it looks something like this:</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/9d57f043ee648c962374a36b056d2e75.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAATCAIAAAB+9pigAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAGXRFWHRTb2Z0d2FyZQBnbm9tZS1zY3JlZW5zaG907wO/PgAABbFJREFUeJx9k39ME2cYxy/uH0MwGcUFMBSzwUYxkZGIJBKSgX8UFhG3GRaJQ0EmKdtQh9JNBJ0g2i4bWH60KIMjtisTW0boyQZXHPSKQquzHELbA/peK/QHP86io7RL6C3lGGPT7Jtvcs/73nvv554nzwPRa3q+tEQSxJzdzngWWEiC8HlXqGdLjwzj08BmmgKj4xPDj0bxcWLV7/d6fU+fOhbmqdkZp2XaxgQvnv9BvyToT5+Ppunbzc23m5tLjuUWZB2oPHO6p6NDJhYPob/KlHf77mGnzlemZh29JKgbvK9vgtt/6deYjdOf8cqzDpwoLrpYWPB13DtpebklmkHd/wGmTSZpY0PJsdzK08UkQTwcGhpCe2XKu/cG7zfB7Z9/9c1lYf0jwxPp7a6+exhuMP7c2Xvlcn1x0UVRTauoprX55k9on5am6ZU1/QNgHovz813SW8MDv+3ezio+8nGX9FZvp8LnXfF4Vgbv6wFpg15/80LV9xOmqWlgo2na6/WhfVqtRp/Bzf0gs8Dr9elHRhfmqVdkwDBpmmZS6ZLeWpyf23zC6w3sl1yodjjnX/7eODFV/MXZT08WCIUCGIZLS0vT09NLS0thGJZIJE6ncz2DDYBcIp6z2zdfser30zT9bV0z9cz9MsDweKKhrlUiETc13VAqlQiCSNaEYZhcLne73QFAT08PgiAoig49ePDlyYIWSeOARqNW92MYhqJoH4piGFZ0ht+tQgY0GnRtiWGYWt3/++OHQsH1SxXCWfuMXq/H1zVmNpt1Op3ZbA6UiCRJPp9vtdosALhfvIAb6hVS6QJFEcSk0Wi0AGABwOl01t+AH4zoSZK0AGBcEwDkIrUAwx1Xq+sXqQWCmBx/MsG8MoziFgBguA3HcchsNsvl7YZRXCSqq74miI+NTYqPF99s7lAocHxsQKNRKjtRFD1WwCu7VKXRaO4olFarDcfHlMpOk8lYVfldEa90wjh+R6HU6/UzT2esVhsApMs1hyA9Op0OQlFUKpPx+fzQ0NAQFislJSUublckm707/t3LlVWZB7MiInYEB287dOjDHZGRb4SFcbncOwplh0IRFh7O4cRlZLwfHR0TFh4eFbXzfFnZssdjNJktAFAUJZXJUBSFEATpUChqams/Onw4KmpnQkJCWHhEaOj2rUFBjWIxj1e0JzExISEhNTVtd3x8CCuUy+V2q1Ryefu+5ORINnvLlteionaGsFhvRUeLRHUURRmNRoKYpCjqh5YWBEECAKlMRhCTtddFNbW1MNwGralbpTIYDAMaTXX11ZZWOJLNhiBIq9XWNTQCQA6PjEgkkrPnzkEQFBe3SySqq6q6olb3W602o8mM4+N2h7OlFQ4AmBLZHU7GbveS3eF4LzVVKBR6vT6CmHS55rxen1zenp9/YtXvn5mdNYziq34/giDR0TFyeTtN08sej9u9tOzxAEDaHQ67w7nq969ngKJoSytsdzgIYjLQOSYzAKTVaotks68JBKt+P8PQarV8Pt/lmgOApGm6vLw8LDzieF5eSkpKdnZ25sGszINZMTFvV1RUCATCPYmJaWn7YbgtABgYHGiUNNkdTgACLWgBgCAmma4NYbES9+4tLj51JCeHy+VGstmZmZnZ2dmxHE4sh+N2Lx3JyYEgaF9yMgRBW4OCgoO3JSUlMRWGIKjsQjmGYZBOp6u9LnI455nbGYzRZF72eBrF4rS0/dQzd1h4BARBsRxOh0IBw23R0TFerw8AkhmUKYsFx8cMBgNBTDLB8IjO5ZqTy9sDAJIkYbiNyWAjCcY4PlZYWMjjFR3Py8/PP3H06Cc8XhE3PaOmtjbQLWvFfKWtVpvd4VSr+wODRpKkQCB0ueaY3//Puc3zzMRMFzLTxJx5JcPucMp+lAcGbWVlBUGQ3r6+zUaQnr8deLVpub7ZrVJ1q1QbwYaV/1Kn2+3+C4UQ7FqDXpOQAAAAAElFTkSuQmCC" nextheight="692" nextwidth="1161" class="image-node embed"><figcaption htmlattributes="[object Object]" class="">How bridges currently work</figcaption></figure><p>Each of these bridges are a smart contract on Ethereum, we call these "Native bridges". When you bridge to an L2 your assets are locked on L1 and a copy is minted on the L2. These networks have the power to mint unlimited amounts of any asset their native bridge supports.</p><p>Despite having the same name and explicitly not being called a wrapped asset, every asset bridged from Ethereum to any L2 through a chain's native bridge is actually a wrapped asset because the contract address, and sometimes even code, is different. The contract address of USDC on Ethereum begins with&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://etherscan.io/token/0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48">0xa0b8</a>, while on&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://arbitrum.io/">Arbitrum</a>&nbsp;it begins with&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://arbiscan.io/token/0xaf88d065e77c8cc2239327c5edb3a432268e5831">0xaf88</a>, on&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://www.optimism.io/">Optimism</a>&nbsp;it begins with&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://optimistic.etherscan.io/token/0x0b2c639c533813f4aa9d7837caf62653d097ff85">0x0b2c</a>, and on&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://polygon.technology/polygon-zkevm">Polygon zkEVM</a>&nbsp;it's&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://hackmd.io/SxXtDSwGQ0i7mW-U78nLzQ?view">0xa8ce</a>.</p><p>These assets look and feel the same because wallets and apps have a list of official assets with official images to display so users never know the difference.</p><p>What if instead of having one bridge for every L2, they all shared a bridge. Assets could be minted on a shared chain, called an interop layer, which then mints them on the final destination L2.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/4b6bd04b922eb1f3b4baf973a64b7693.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAUCAIAAABj86gYAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAGXRFWHRTb2Z0d2FyZQBnbm9tZS1zY3JlZW5zaG907wO/PgAAA5hJREFUeJytVE9o22YU/3bUYZfk0BFGGe5GdQxjfwSDIQYpoqHEixnRCItT3BA0dKgsPDsGF2M6YpAHNZO2mpgJjA9CpAfLZSRyDokdQ3CDaWNvMsUGI2MvINvtRSo5aSzfEKtx5nXkd/j43uPp/X6/9/gE8jl1K5XdU4uP5Md8Mp0R5Xqtkc+pQTbGxflYhOPiPBfn67VGq9nOiDIX5x9wD7OZbVlSZEmxJwH4794LMFEEvLvkWZvDPXwyvZXK/vTjL0uetbfAO+s+9soUeu3qR7Kk8Mn07s6+d5n+5MMb/rv3yqVKgIlaljWBYCuVlSUlsrEJAPAu0/mcWq81dnf2f80X1n3s2+DqI/lxNrPd6fTKpYosKbHoDwAA6GN3Z3+yA+dWrzUCTBS6Pnt1Ztv27s7+wvyKbduOzOLBUSzC1WsNGML8YDAc8WGd428C2AvGlmUFmChNhfr9gdPOPs+fvTrj4vxWKssn05GNzYX5FZoKPeAe3rnNfPbpzS8+/3IO98Bv+WR63cfSVGhPLb7mwBGezWzfvEE+e/Z7r3vKJ9O2bbea7SAby+dUqLfXPe11TweDYfX4JMjGljxrS561ABNdvOUtlyovhi9hwYvhy1ECx0qr2V685eWT6XxOLR4ccXG+1Ww73i9a7D+H4VxGCSBazbYsKVemUADAHO6RJaXXPb1ojbDvRQBjqzOiHNnY9C7TQTYW2dgMMNE9tZj6OeNdpmkqFGRjNBX6atFHU6Fvvv4WPpSF+ZV1H8vFeVjDxXmaCnU6vfEOMqJ85zbzwXsfTyGu6+9jC/Mr+Zza7w/qtQZ8ca1mu1yq1GuNJ5Wn2m/P67VGuVSpHp/0un9Uj0+eVJ62mu09tWhZ1niC4XDY6fT6/cEU4ioeHPX7g4kP6r+OaAQBJtrp9P69xjTNNyYQRdHv94fD4Wuu698Fgn6///79703TNAxD13V4wlDTtJG8cQ5N0wzDGEMA5ZAkKQgCjuMAAARBCoWC2+3Gz+FyudxuN4IgOI5TFAUAQFEUwzCSJGdnZ1EUJUlydXUVADA9PZ1IJMY7UBSFoihBEAAAGIYJgiCKIpRmGAaU7Fw0TXOEO3nTNGFyPAGssG0bQZDDw8OJg37jHei6XigUqtUqQRCiKCqKAmkugQAqpSgqHA4TBDEzM4NhWCKRwHEcLu1yCNxutyRJKPrXrwJFUU3TCILQdf0SCCAkSQqHw4nX8T+627b9J0xMBnDFscZwAAAAAElFTkSuQmCC" nextheight="804" nextwidth="1289" class="image-node embed"><figcaption htmlattributes="[object Object]" class="">How an aggregated blockchain bridge works</figcaption></figure><p>Polygon calls this new design an&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://polygon.technology/blog/aggregated-blockchains-a-new-thesis">Aggregated Blockchain</a>.</p><p>What's useful about this design? When moving an asset from one chain to another in this ecosystem, say from Polygon zkEVM to OKX X1, it doesn't have to be moved via a traditional bridge or bridged back to Ethereum first. Instead you can burn the asset and have the interop layer mint the exact same amount of the asset on the destination chain!</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/b85a59f1603adfd82bf5458463598888.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAASCAIAAAC1qksFAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAGXRFWHRTb2Z0d2FyZQBnbm9tZS1zY3JlZW5zaG907wO/PgAAAyFJREFUeJyVlU9o01Acx+NlIF6mp1yMevJPj0FGD45MnHsokiESh4cwGOy2TsbIGGRBxyg24KBWs0ApKbWQ0sLiCs4osu1drAuslEDYWAYONqYDM7odXhWUJ2u2WsXW7UMI/MIv7/t7v/f7/R6B63Bdl6ZpkiRZlg0EAjRN8zzvf+E4LhgMchwHAOjo6AiFBkmSBADYto2bQtQbCCEIoaZphmFACG3bdl3Xtm1FUewqlmW57qrrrm5ubiwufrQsCyF0DIGjMD/3IRZNSKIsR5RUMqfrM6lk7tgCTeKKRROFwpL85MWVS9c6r99b/7QhjkYQqhxPoAmlopNK5lLJ3PmztCTKuj5TKCx53ldfAyHkVfnvDhpGVGP80dPd8p6u6+3t7QRBMAzT0tJCkiRBEKAKRVGe5x0IIFSpf3Bjvn/7vlvewxjPvn7/5fN2zZ/jOIqiWJalKEoQhFqe9wVKRSeuplPJ3PNnmhxR4mramDYbCZSKjn/Id7v7YtFENpOPq+kmAe0LxNV0XE3fucWPDE+MDE8Y06YcURrtQ44oW1vbsWiil3/o108T5wOB/Ku3cTUtiXLgMnO3uy+VzDUJ6p25kErmxNHIyRPn/ciOWKY/McbrnzaGh8ab5AdVI3Wc1cGBMV2fqf3oZ7xGzfx3FWUz+Vg0cVh2lb9Wz2bykigjVPnx88dfi9Z5/jYJCCHLsiRJdnV13b/fw7Js580bK8trsWjCcVZrBYYx3i3vjT+ezGbyhjHd399/+vQZhmFomgYABAIBQRAYhgkGgwAAf3BpmrYv4HkehNAfPjUwxjs7ZXXq5WEe8MrymjgamZ/7gDH2PM+yLAihVcWfUbZtG4ah6zqE0HVd//2fTkaoElfTwbbbkigPDoyVis4Re7CehgI7O+Ve/mGw7TZBnCIIoutGz/DQ+JvZ+YWFeUVRwuGwaZq6rhuGoWmaIAimaYbDYUmSFEX54wwaCZSKjjr1Uo4o/IOBC+euSqLsl++lyxeJOlpbW0OhEADANM3JyUkAAM/zRxLwJ3OhsOS3iDFtZjP5leU1/8CqF8P+VeEnukmKfgGh2nDiacnMKAAAAABJRU5ErkJggg==" nextheight="561" nextwidth="989" class="image-node embed"><figcaption htmlattributes="[object Object]" class="">Moving funds on an aggregated blockchain</figcaption></figure><p>Every asset bridged via this interop layer is now exactly the same across every chain in the ecosystem. Assuming the interop layer is free to use and fast (Polygon have said theirs will take &lt; 20s to finalize) you'll be able to bridge assets of unlimited size, between any L2 in the ecosystem, within seconds, for free!</p><p>Both&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://polygon.technology/">Polygon</a>&nbsp;and&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://zksync.io/">zkSync</a>&nbsp;are working on this interop layer design for their ecosystems, from&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://docs.optimism.io/stack/explainer">Optimism's design documents</a>&nbsp;containing a shared bridge it appears they are pursuing it too, though have yet to confirm it.</p><p>The disadvantage is it only works within one ecosystem and requires all chains to use one bridge, which increases risk, however the reward of having liquidity flow seamlessly between all chains in the ecosystem more than makes up for it.</p><p>Because all tokens are interchangeable across ecosystems, there's no need for your wallet to show what chain you're on or separate tokens by chain. Instead your wallet could look like this:</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/76d743701a6b3416523b8dbcbdad70c3.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAcCAIAAACPoCp1AAAACXBIWXMAAA7CAAAOwgEVKEqAAAAE80lEQVR4nJWV/U9bVRjHzx+giT+o0ThN3A9GnGYxzrgfphEzzWZCNBpYYBnDoXWrIu8U6Bi1MAZdGWXcuhX6Ai1ZJ4wVSVsG0hYKHaxc2Ep4G5ZS+kIvvW1JB73YW+g15VbG2q7A58d7n+d8z3m+5zkPCAQCBBF89cWj77+ZNDM3XUxn5ObTbjYKiChmH891yP5SqTWyzi65XLkRStwdQBDEgnUeAPDdlxc0g5pTaRm/5RZxeU3RofpRuKr6akuzpP2OrEnYjON4RAD5RSy5dejwx1nZ+cmp6RiGhQQwDNPphsh/F8uZixbLdvROUJttRNndUsE0TU4Qz8dkWpB1yrVanVzRg+N4SGAbHMcxDIteehv/+jq2uroRCMSJiQBsBoN+v+3owQ+OHjo1or/f2CQSS24xK6snJ6cizrFosWgGtEO64VvSP91uzz4EFK0ZAIA3wOsyhfJ0emYmhfrRJ5/KOru2BTaDQdIDiNt47VoD5XyW1WqLXosM1mp1hw4fKWdWJaemu92eUIkc5qm2P5JXXIZ7vf20YrrL5Yq5F7vHdflui1CtkAz1xtmycd7EYnNknXKIy8Ow9Wc8wDDM4XA8r76bwaB77cmKb23Ft0qeaU8lIgjC5Vx578BJ6pnfp2em29o72to7WGzO+CNDhAdWq63vb43BMKFQdHu93n0IHHgpEWzRda/rVFpGXlHpsc+Ot0pvRwjA8FhOTmFNTW362R/JqxyT8UeGAtpFqbQt7cy5NZ8vJNBQLQEACKCO/iHtT5RfKitrYHg8uhXsHlQ82FN5V8zrC/n/PGB4nMXm9PSpcvNpXu+TZzxwoujk5BSCLGMYthHYiMjE/H4buvyPw2ZxInusT7hEDpMjMSG1hin0rnpheFyl1pAniMDj9pgXzM5lp9Vqi9NogUBg5xUICbwG3tqy4JWJOUNyypncfFr9de7OJTa3EpQ9vYUll240iahZeTH7gATHcb5Q3CgQFZeWh9+i86fLAAB8ukA/AefmFhXQ6O13ZNGZiNms7+sTMRjmmZn4ZbnB49fVQxeo2WGBbZYcDpVKrVKpjfPz0Wn+9XXL7Oz0gwceZJ8eOBEbJSVHAHVsbPqN8yYEWXaiaHToms/nRFHU5d77SxcWSEx4BwDwAjjSpehK+iY5Kzv/h3Pno0NVas2Vq3W0MkYcA0j4QrFQJGmAboafCul16OtjH+r1uvvD+gIavYBGJ9t4a9g9xYMg3c3NAgbDbjQScckrKs0rKsmkUJ96gON+co83eHy5XIkgy9FpqysrhoGBEaUSte1ygp2EBIxWJOHd76sKuWvra+OPDPpRmBwGESyj6GPjvNm+ZJicwjBsHwIAHNzqg7d1eu1XJ7/9/IsTLDYnOlSp7KlgVokELT9Tfo1vQzmzqqjkUgGNHvaAWsgBAFznywYGVFnZ+RWV1RH3ZHOr0R4vWVh3JZduN7VqQ/MgzosNcXl19RDEbYycyYsW68jIKAyPxUzD/H7DgvGhaW7askDsmZAA6vVmnmVAVRLsX5/BMKEfHSNvUQRut8duszvsS/vug5cTU0gPBocHaKWM4yeSYvaBVqur5TSUMy/HbMOd8IXiVuntq+z6/z0orQUASOSqh2NjmRRqk7A5Zpp+FGaxOczKK7sKlJVXQFwexOWFB842M7Ozbe0d+lE4ZprValOr+9Xq/r3PS4Ig/gNbSw2hxLRHVwAAAABJRU5ErkJggg==" nextheight="348" nextwidth="391" class="image-node embed"><figcaption htmlattributes="[object Object]" class="">A unified wallet on a unified chain</figcaption></figure><p>When performing transactions across multiple chains your wallet can simply show you're using the "Polygon" network and perform all bridging automatically in the background.</p><p>If this design is so great why wasn't it done earlier? ZK Proofs only recently become fast and cheap enough to make this possible. The Interop Layer uses ZK Proofs for all mint/burns so it can finalize in seconds without any challenge period needed.</p><h4>Advantages</h4><ul><li><p>Fast, simple, standard way to move tokens between chains</p></li><li><p>Can move any amount of tokens with no slippage</p></li><li><p>Likely to be completely free to use</p></li></ul><h4>Disadvantages</h4><ul><li><p>Only works within a single ecosystem</p></li><li><p>One bridge is a single point of failure / attack for an entire ecosystem</p></li><li><p>Must be designed from the beginning, can't add to an existing ecosystem without major changes</p></li></ul><h3>Mint/Burn Tokens</h3><p>Rather than relying on a shared ecosystem bridge, chains could leave bridging to tokens. A token needs to implement mint/burn functionality and allow users to burn the token at any time to mint it on another chain.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/f9d3c0c2911d9aeec268d0f0e2339f11.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAOCAIAAADBvonlAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAGXRFWHRTb2Z0d2FyZQBnbm9tZS1zY3JlZW5zaG907wO/PgAAAtRJREFUeJyFk0Fr1EAUgPMXKh72LP0TObnH3nrLQSQtCiuCBsEaKeJY6HYrYoPFkl2qS2SpO7WyTbqUOLuHzU4sbphKrQOFSigtNmCLJG5rGfUUaSJLuq3d7zSHee97894bLuzFeDZ7d2REkiRVVQEAg4ODiqJkMhlZlimlPcO5njcopXoEpRRjrKoqIQRCiBDyfb+3wHVdw1gyjCU7wjRNw1hqWJZt2y3HaTnO/8oMgvZcqbIwX7WbTh01KwvLVaMWn+uoaTU+VI3azvYu13Kc12X4slhkjFFK8/lCPl8gZLWTqGFZP4+OTgvemdbUpDoqT+xs7y7MV0fujBVnyzvbu50L+3vf66h5LOi89EcQNCyrsrgIIRQiPq6uthwHIeS6rhfh+77rupR+Fq9cP2gfhmHI2K+tra+j8sSSbgLwKJ7Q0NAwhOXKwjJn23aylS2HQPiGMSaKoizLYRjatq1p2mCELMuCIGQymfHs+LWhG0EQxIIgaD/OPifOJ13XBUHgOC6dvrz5ZbNb0HKc7EQuO5GzbTuhdBhj6XQ6lUql02kuglJaR829b/thGK6vbYw9fDp8VXpwf9JuOskhVY0aRwjBGBNCGpZlmmY+X7h1W5qZmWlYVsOyVt6vYIxZhO/7jDHP8+Kxr69tTE2q8XinnhRSFy/dzNwrzpZLr97OlSpVozZXqqyvbRyvKUsQhqHnebVaHSHkeV7PLWSM1Wr16WfThcKLuBMH7cOD9uGf33/+rWnyNqW02bSiGVKEkCRJiqK4rhuLOxXE+L6PMVYUBULoeV78OEJI1+c4ISCEAADiLqdSKVEUdV3vfK5kahThuq6u6zzP9/f39/Vd4Hl+YGBA07S4mjMEnfh4HZN90DRNEAQ1QpKkpA9jnMvlZFmGEJ7OdkLQ1YTkYAAAPM9zHMfzfC6XU1W1U2ZXyHmCM4ljIIQAAFEUAQCqqmKMz6ksKfgLd3E6xeIbuGEAAAAASUVORK5CYII=" nextheight="558" nextwidth="1287" class="image-node embed"><figcaption htmlattributes="[object Object]" class="">Moving DAI from zkSync to Polygon without using Mainnet</figcaption></figure><p>These mint/burn messages can be sent via middleware such as&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://layerzero.network/">Layer Zero</a>&nbsp;or&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://chain.link/cross-chain">Chainlink CCIP</a>. Layer Zero is working on a project called&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://l2beat.com/bridges/projects/omnichain">Omnichain</a>&nbsp;which will allow tokens to implement this.</p><p>Some tokens have already implemented this system - Circle recently rolled out their&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://www.circle.com/en/cross-chain-transfer-protocol">Cross Chain Transfer Protocol (CCTP)</a>&nbsp;which does exactly this for USDC across 8 different networks.</p><p>As USDC has high liquidity on many networks, and no cap on liquidity available, it could be the perfect go-between to move assets between chains. Wallets could swap the token you want to bridge to USDC, bridge that USDC using CCTP, then swap it back to the token you desire on the destination chain. This could be done with little fees or slippage and handled automatically by your wallet.</p><p>The downside of leaving liquidity unification to tokens, is it is up to the individual tokens to implement it, and wallets and apps must know which tokens they can bridge automatically vs not.</p><p>It also requires tokens to wait for the chain to finalize before the token can be sent, which can take minutes to hours depending on how often the data is written to Ethereum. If the token doesn't wait for finality it could be double spent by being minted on the destination chain and then having the send reverted in a re-org on the sending chain.</p><p>Another risk to consider is the tokens security relies on every chain and relaying system to be secure. If one L2 is compromised it could print new tokens by sending malicious messages (e.g. saying it burnt a token when it really didn't) to other chains. If the tokens relayer or oracle becomes compromised the same scenario could occur. This would cause the token to break on&nbsp;<em>all</em>&nbsp;chains.</p><p>Cross-chain tokens have been implemented before, in the Cosmos ecosystem with&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://github.com/cosmos/ibc/blob/main/spec/app/ics-020-fungible-token-transfer/README.md">ICS-20</a>. It solves the issue of "One chain breaking the token on all chains" by having tokens track the path they took to get to the current chain. If token X is sent via chains A -&gt; B -&gt; C, and some X tokens are sent A -&gt; C, then chain B is compromised, the first set of X tokens will be worthless but the second set of the same X token will still hold value because they didn't cross chain B. This creates additional issues with token fungibility that wallets and apps must solve, but it is a solution.</p><h4>Advantages</h4><ul><li><p>Tokens can move freely across any L2 chain</p></li><li><p>Can move any amount of tokens with no slippage</p></li></ul><h4>Disadvantages</h4><ul><li><p>Chains must be secure, one compromised chain can break the token across all chains.</p></li><li><p>Wallets must know what individual tokens are capable of to simplify UX for them</p></li><li><p>Tokens must wait for finalization before moving, which takes minutes, occasionally hours</p></li></ul><h3>Native Bridges trusting each other</h3><p>L2 chains with ZK bridges could allow fast, free token transfers by trusting the native bridges of other L2 chains. This would work by users burning a token on one chain, then using a proof of burn to mint that token via the native bridge of another chain.</p><p>For example if&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://scroll.io/">Scroll</a>&nbsp;reviews the&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://linea.build/">Linea</a>&nbsp;bridge and believes it is secure (and cannot be made insecure via upgrades), they can setup a service monitoring the L1 state root of the Linea bridge, allow any user on Linea to post a proof they burnt a token on Linea and this burn transaction is included in the L1 state root, and mint the equivalent token on Scroll.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/0163d92270936687de9f3b16d782e49f.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAOCAIAAADBvonlAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAGXRFWHRTb2Z0d2FyZQBnbm9tZS1zY3JlZW5zaG907wO/PgAAAydJREFUeJyFlF1P01AYx3tF9EPAl9AbLuECMFF7RzTRJcY4vSExwdTEQDEkgok4NNH5Eg3KIoXBGC8DOsrIulE3z7GzGx1u1G2AW90LHWrgbAjLDKvUZhD95yRtT57z/J7zPP8UK/9PCCGCIEiSJAiitbXVVJHBYMArQghVokq6pVcJU5/7pRJCBXWpn3oAeyiapgEAQjBI0zTLsk4ncwg4VgdJMA4KozOMxeYYnpgbsE5abA6LzTE6w0w73S7vBw4KQjh67Okt5dsnMBeEC4kvwWXeA5ccId4dFf0R0bfMe1bDICr6o6IfYzw+p/u9moWDQnf/yydvRtbltHYPxuPbVPJHS9uIrbgcb6Oiv1hAQeiiXnV7GCqvyFqj1H0Mhla0XNs7yAsCHAz09PTU1tY2NTWtxWMT9OK8yxWPxSRJSlYkSZIohp8+7s3IayqvWEDAO7U4P3X12jWj8UZ9ff2pU6ebm5vd82OYFwT0gGmXZ9rpzuZyly5fftDXVy6XrROzlnfU3a4ug8FgNBpbWlra2tqGqOGO223fkqtqpVv5TBAuSCu8nEoODAzgOE6SZDL5FS45Dlp0OMyC0/2+//XQs0HrypeERg2InxPrG42NjVhFdXV1J0+cmKXnN7OJdCpeLpcz8hrk6Jkxs5exJiRBM9JusRgRfdjoDOPmgJ8P+fmQOvBng1bG4wOBEAcDHBQ4KKBDab5CqJCRN5Z5T0T0RUQfWJq2We4zU69DvDv0cTEi+qKiXwx406nYH5vqtb2D1uW0nMmpltVLh/lbZjoVXw3DyjxKu8VilXGxKr+bzeYXz59bR0b6HpquXL0+y7h+7e2pvVJ5ekZekYO8F4KlbC6LEFIURQvQMNUAk8lUU1ODYRiO43e7uiDk5UxOCEfzP37qyipl5LV0Kv49n/0IYUNDgzYe9QXHcbPZXA1QpSiKJEksywIAtM39Uslmn7pJ3BkemzQ/vvegtyOVPHCBdoSmaYqiAAAURdntdvUqxwOqOq6l6OzsPHcexzDs7Jmm9lvtdrtda9q/dTzg6B/GNj5OEMTFCxf6+x+RJMmybFW83mN6wG8JAFWrjoUBIwAAAABJRU5ErkJggg==" nextheight="548" nextwidth="1267" class="image-node embed"><figcaption htmlattributes="[object Object]" class="">Moving any token between two L2's without using Mainnet</figcaption></figure><p>The process of chains checking each others state is covered in greater technical detail in&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://vitalik.eth.limo/general/2023/06/20/deeperdive.html">this post from Vitalik</a>.</p><p>This is similar to bridging back to Ethereum then to the other L2, but this method saves the exorbitant L1 gas fees.</p><p>The risk is now those native bridges won't have exactly the same amount of tokens locked in them as has been minted on the L2, a core property that up until now has not been broken. If in the above example a user moves $1M DAI from Linea to Scroll, the Scroll bridge will be $1M DAI short, and if a user wishes to withdraw many tokens out of the native Scroll bridge there won't be enough available. Bridges could reconcile these differences through bulk L1 token transfers with each other, or by always having 2-way trust between them, so the whale could withdraw funds via the Linea bridge even after the Scroll bridge has been emptied.</p><h4>Advantages</h4><ul><li><p>Tokens can move freely between trusted chains</p></li><li><p>Can move any amount of tokens with no slippage</p></li></ul><h4>Disadvantages</h4><ul><li><p>If one bridge is compromised it could compromise all bridges that trust it</p></li><li><p>Bridges will have differing amounts of tokens locked vs minted on their network. This could cause issues with withdrawals.</p></li></ul><h2>An Economically Secure Fast Finality Layer</h2><p>These three methods have great scaling and security properties, but have one flaw that dramatically slows down transfers - waiting for finalization. Finalizing a block requires both the sending network to write it's data to Ethereum, which&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://l2beat.com/scaling/finality">could take up to an hour</a>, and then Ethereum to finalize which could take&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://ethereum.org/fil/roadmap/single-slot-finality">up to a further 15 minutes</a>.</p><p>Through economic incentives we can create "soft finalization" where a transaction is finalized by more economic value than it is worth. This can work via nodes staking on a service like Eigenlayer, where their stake can be slashed, and attesting that a transaction is finalized. If the transaction is somehow reverted the nodes are slashed and that slashing can potentially be used to plug the hole caused by the revert.</p><p>The benefit of this is transactions can be soft finalized in seconds, greatly speeding up all cross-chain token transfers.</p><p>This is something&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://near.org/">Near</a>&nbsp;is working on. Rather than proofs of sending/burn needing to be written to Ethereum L1 and finalized, instead the proof is written to a NEAR fast finality chain, where finalization is secured by Eigenlayer stakers who get slashed if there are rollbacks or reverts.&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://twitter.com/mraltantutar/status/1732153887476322600">This tweet thread</a>&nbsp;goes into further detail on how it can work.</p><p>Lets see how this fast finality layer could improve on all 3 methods of token transfers:</p><ul><li><p><strong>The Interop layer</strong>&nbsp;is already a fast finality layer, managed by the ecosystem team (Polygon, zkSync etc). It allows transfers within the ecosystem to take seconds.</p></li><li><p>When&nbsp;<strong>tokens are mint/burnt across layers</strong>, instead of waiting for the transaction to be finalized on Ethereum which can take up to 20 minutes, the fast finality layer can attest that the transaction is complete and won't be reverted, and the attesting nodes will be slashed if it is. The destination chain can then trust this layer and mint as soon as it has attested to the transaction.</p></li><li><p>Similarly,&nbsp;<strong>when networks trust each others bridges</strong>, they can settle token transfers via this fast finality layer instead of waiting for Ethereum, and use attestors in the same way as token sending.</p></li></ul><h4>Advantages</h4><ul><li><p>Token transfers can finalize and complete in seconds.</p></li></ul><h4>Disadvantages</h4><ul><li><p>Unclear how slashing can be used to repair the hole caused by a revert that causes a double spend.</p></li><li><p>Reliance on a secondary chain that is not Ethereum to be secure.</p></li></ul><h2>A Future Wallet experience</h2><p>After these new unified liquidity improvements are implemented, what steps remain for cross-L2 wallets to feel like you're using one chain? The two biggest remaining issues are cross-chain gas, and integrating apps with this system.</p><h3>Shared gas between chains</h3><p>If a user is constantly moving across many chains, how do they get gas on all these chains to pay for transfers?</p><p>This is being solved with&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://eips.ethereum.org/EIPS/eip-4337">Account Abstraction AKA EIP-4337</a>&nbsp;and&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://eips.ethereum.org/EIPS/eip-4337#paymasters">paymasters</a>. A paymaster is an address you can ask to pay for your transaction fees for you. Some wallets such as&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://avocado.instadapp.io/">Avocado</a>&nbsp;and&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://www.ambire.com/">Ambire</a>&nbsp;allow you to pre-load a gas balance, and then use this gas on any chain, similar to a pre-paid debit card.</p><p>Another simple solution is the&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://www.bungee.exchange/refuel">Bungee Exchange Refuel</a>&nbsp;which takes gas on one chain and gives you a little gas on another. This is worse UX than a paymaster, and will leave users with a little gas on many chains, but it works for EOA Accounts (standard non smart contract accounts).</p><h3>Apps covering gas fees</h3><p>Paymasters also unlock the ability for Apps themselves to run a paymaster and cover all user transaction fees. This would allow anyone to use an app on its own chain without needing to bridge at all. The app could make profits in other ways, such as selling premium goods that do require tokens, or having a demo mode that is free but you must pay for the full experience.</p><h3>Making it easy for apps to utilize unified liquidity</h3><p>Many apps load user token balances via calling&nbsp;<code>balanceOf</code>&nbsp;on every known ERC-20, which is a slow process and doesn't work cross-chain. They know generally nothing about tokens that may be bridged from other networks.</p><p>This problem should be solved at the wallet level, so every app doesn't have to re-invent the wheel to support a multi-chain future.&nbsp;<a target="_blank" rel="noopener" class="dont-break-out" href="https://eips.ethereum.org/EIPS/eip-2256">EIP-2256</a>&nbsp;introduces a standard function wallets can implement which allows loading all token balances at once, though this is only single chain for now.</p><p>If a wallet is multi-chain aware and knows ways of bridging tokens from one chain to another, it could tell the app the user has those bridgeable tokens available immediately, and when the user interacts with the app the wallet bridges it immediately before performing the interaction. This could use any of the above mechanisms for bridging the tokens.</p><h2>Conclusion</h2><p>Hopefully you now have a better understanding of how liquidity will more seamlessly flow between L2's in the future, and how wallets can use these new technologies to abstract away chains completely in order to make using Ethereum as simple as it was in 2020, without the high gas fees!</p><p><em>Thanks to Chad Fowler, Alejo Salles, Mike B, Montana Wong and Centauri.eth for their feedback on drafts of this post</em></p>]]></content:encoded>
            <author>blueyard@newsletter.paragraph.com (Tim Robinson)</author>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/e5243098d5e8fb3b5e4faa8daeb4b081.png" length="0" type="image/png"/>
        </item>
    </channel>
</rss>