<?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>Dan Finlay</title>
        <link>https://paragraph.com/@dan-finlay</link>
        <description>MetaMask Founder, building for a more consentful web.</description>
        <lastBuildDate>Wed, 18 Nov 2026 21:32:02 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>Dan Finlay</title>
            <url>https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/1132c3be700babdb3b30c75c98b09064ce7561093929343f763fb6baa00f9943.jpg</url>
            <link>https://paragraph.com/@dan-finlay</link>
        </image>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[Introducing Delegatable Ethereum]]></title>
            <link>https://paragraph.com/@dan-finlay/introducing-delegatable-ethereum</link>
            <guid>RkhFHJbfAxhScW6Ksmnj</guid>
            <pubDate>Wed, 01 Jun 2022 15:38:21 GMT</pubDate>
            <description><![CDATA[Today I’m happy to start publicly sharing some early but working Ethereum tools that enable general purpose delegation in Ethereum. This is the culmination of years of thinking about what is missing from the computing blockchain ecosystem, and I’m eager to see what the community does with it. A few things it helps address:Onboarding without needing gasMinimizing the need to onboard to a “wallet”Help users make smaller, more deliberate connections to applications.Maximize the interconnectivity...]]></description>
            <content:encoded><![CDATA[<p>Today I’m happy to start publicly sharing some early but working Ethereum tools that enable general purpose delegation in Ethereum. This is the culmination of years of thinking about what is missing from the computing blockchain ecosystem, and I’m eager to see what the community does with it.</p><p>A few things it helps address:</p><ul><li><p>Onboarding without needing gas</p></li><li><p>Minimizing the need to onboard to a “wallet”</p></li><li><p>Help users make smaller, more deliberate connections to applications.</p></li><li><p>Maximize the interconnectivity of smart contracts</p></li><li><p>Allow smart contract developers to write less security sensitive code</p></li><li><p>Enable transaction batching</p></li><li><p>Create social systems that are maximally responsive &amp; dynamic.</p></li><li><p>Enable applications to benefit from trust that may exist in their communities.</p></li><li><p>Enable deploying devices with the minimum set of permissions without needing to transfer funds or perform transactions.</p></li><li><p>Allow transactions to not be blocked by each other (nonce queue issues).</p></li><li><p>Provide tools to reduce key reuse across devices.</p></li><li><p>Provide a framework for dynamic, accountable, and highly liquid allocation of scarce resources.</p></li></ul><h2 id="h-background-and-theory" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Background &amp; Theory</h2><p>You don’t need to know any of this background to recognize the value and start using it today, so feel free to skip this section if you want to get to the practical bits.</p><p>In 2016 I first started becoming very certain that there was some kind of design that could allow highly dynamic and responsive social organizations. I recognized that Moloch DAO was addressing the same general issue but with a very different approach, which introduced latency. I had enough problems in mind that required highly responsive organizations that I wanted to find the best possible solution to social scalability that does not depend on time locks.</p><p>This problem was feeling very challenging in part because defining “trust” can seem damn near impossible. For simplicity’s sake, I took a detour and tried reducing the problem to lending: Representing what is risked as “just” money.</p><p>I spent a year reading any proposal I could for decentralized credit systems, but mostly found myself tearing them apart. <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://medium.com/@danfinlay/phi-decentralized-lending-and-stable-currency-might-not-actually-be-stable-36f472948591">My review of Dfinity’s Phi</a> was pretty entertaining, I think.</p><p>I eventually <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/danfinlay/status/934308978225319936?s=20&amp;t=_hqKGQ7mRtXbp80-0hzMkw">articulated a concept well enough</a> that my twitter community was able to direct me to some prior art, and that led me to two concepts that would end up guiding a lot of my work for the next couple of years: social collateral and object capabilities.</p><p>Social collateral in short is the idea that you can trust someone with anything as long as they value your relationship more than that thing. Your social relationship is a form of collateral. People don’t want to get cut out. There’s some great economics literature about <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://academic.oup.com/qje/article-abstract/124/3/1307/1905159?redirectedFrom=fulltext">how scalable and secure this tool can be</a>, how it actually underpins the banking system already, and how it <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.ucpress.edu/book/9780520287051/social-collateral">de-facto underpins most casual lending relationships</a>.</p><p>My research on social collateral led me to seek patterns that could allow people to issue transitive allowances to each other (I grant you an allowance, and you can grant it to someone else), and that led to me meeting folks who have been working on systems like that such as <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://trustlines.network/">Trustlines</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://joincircles.net/">Circles UBI</a>, as well as approaches that focus on scalability like <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://medium.com/fairlayer/xln-extended-lightning-network-80fa7acf80f3">XLN (Extended Lightning Network)</a>.</p><p>I wrote a rough description of a specification in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://gist.github.com/danfinlay/73b6ffd11aea5a85767fe20c6ad868c5">this gist on github</a>, and was quickly directed to the <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://web.archive.org/web/20220309192621/https://w3c-ccg.github.io/zcap-ld/">zcap-ld specification at w3c</a> by Mark Miller and Christine Lemmer-Webber, Agoric, and the extensive prior literature on what they call object capability security. What their work showed me was that the secure scalability properties of social collateral were not exclusive to the economic and financial, but could be considered a general framework for managing access around any sensitive resource.</p><p>This made a lot of sense, because a recurring challenge of defining a system of trust is trying to define trust, and reducing it to the form of a financial allowance was always obviously reductive. In the object-capability framework, you aren’t always granting a financial allowance delimited in dollars, you can provide access to any function, delimited with whatever computable caveats you can dream of. Here I felt like I had found home, where we were uniting the maximally secure with the maximally expressible.</p><p>In 2019 <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://ethereum-magicians.org/t/ethereum-object-capabilities/3035">I wrote a public appeal for someone in the Ethereum ecosystem to take up this cause and implement it</a>, but nobody did. I’ve been pretty busy making MetaMask, so I kept feeling pulled away from this, but during a break in early 2022, I finally took the steps to sit down and begin it.</p><p>The Delegatable framework does not achieve what I would call pure object capabilities, because it still involves developers needing to manage signature and delegation code, although I’ve started <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/danfinlay/delegatable-eth/tree/main/packages/js-eth-delegatable-utils">a library that hopefully makes it somewhat ergonomic</a>. The <em>object</em> in <em>object capabilities</em> comes from object oriented programming, and is meant to mean that the syntax of the programming language itself represents the distributed delegation system as mere reference passing. Therefore, I might call this a capability security framework for Ethereum, but have chosen the name Delegatable Eth for the sake of trying to more simply convey the core benefit to the most possible readers.</p><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://agoric.com/">The Agoric Blockchain</a> is one where the syntax of the smart contract language itself does achieve object-capability security by using a secure subset of JavaScript, but on the Agoric blockchain every delegation (by default) is an on-chain action. A novel benefit of the Delegatable Eth framework is that all delegations can be performed off-chain, and for some applications this can enable highly off-chain side-networks of “counterfactual” transactions that <em>could be submitted</em>. I think it remains to be seen how significant a scaling benefit this offers, but I think the MobyMask proof of concept has a pretty promising example of getting a large amount of functionality out of a very small number of on-chain transactions. A similar framework could be built on top of Agoric’s blockchain, but it would lose the ergonomics of keeping the capability management within the language’s syntax.</p><p>The design of Delegatable Eth is extremely similar to and obviously inspired by zcap-ld, but with the unique feature of being validated by any Ethereum Virtual Machine, bringing its benefits to any Solidity contract that inherits from it, instead of simply bringing these benefits to a centralized server. By running a private blockchain as a validator, a consumer of Delegatable Eth could use it in a similar way to zcap-ld if they wanted to.</p><h2 id="h-developer-experience" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Developer Experience</h2><p>By inheriting from this solidity class, any contract gets a host of features:</p><ul><li><p>Support for MetaTransactions</p></li><li><p>Support for batched operations: Many actions in one transaction, and potentially lower gas costs.</p></li><li><p>Support for signing multiple actions that aren&apos;t blocked by each other, so an urgent transaction isn&apos;t blocked by the low nonce of a low-stakes low-gas bid transaction.</p></li><li><p>Support for signing commitments that can be lazily submitted to the blockchain later.</p></li><li><p>Allow users to sign off chain messages that delegate authority to perform any action they can perform</p></li><li><p>Every delegation includes support for an open-ended system for adding restrictions to that delegation, including revocation.</p></li><li><p>Allow the holder of any delegation to issue a delegation from it (transitive invitations), also with an off-chain signature and no transaction fee.</p></li><li><p>Allows creating invite links to users who don&apos;t have accounts set up yet, by signing delegations to a key you send along with them.</p></li></ul><p>Integrating <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/danfinlay/delegatable-eth#delegatable">the Delegatable library</a> is as simple as inheriting from a solidity class, and overriding `_msgSender()` (and using that method instead of `msg.sender` directly).</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/dd6b90d3b4acb832f81465d2fb7a21de274802449cafc9419ef0383a589d2b0d.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>Once inherited, the resulting contract allows any user to sign delegation methods that allow them to share anything they can do on that contract with anyone else. You can see some <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/danfinlay/delegatable-eth/blob/main/packages/hardhat/test/myTest.js">sample delegation signatures in these tests</a>. These delegation messages are off chain, and include any number of “caveats”, which can include special restrictions like revocability, allowances, call limits, time limits, or eventually with some changes, even multi-sigs and additional forms of cryptography.</p><p>Some example caveats that a delegation message include:</p><ul><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/danfinlay/delegatable-eth/blob/main/packages/hardhat/contracts/caveat-enforcers/RevocationEnforcer.sol">Revocation</a></p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/danfinlay/delegatable-eth/blob/main/packages/hardhat/contracts/caveat-enforcers/AllowedMethods.sol">Allowed methods</a></p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/danfinlay/delegatable-eth/blob/main/packages/hardhat/contracts/caveat-enforcers/LimitedCalls.sol">Limited call count</a></p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/danfinlay/delegatable-eth/blob/main/packages/hardhat/contracts/caveat-enforcers/ExpirationEnforcer.sol">Time limit</a></p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/danfinlay/delegatable-eth/blob/main/packages/hardhat/contracts/caveat-enforcers/ERC20Allowance.sol#L13:L13">Token Allowance</a></p></li><li><p>NFT allowance</p></li><li><p>Parameter ranges</p></li><li><p>Approved recipients</p></li></ul><p>You can look at how it works by looking at <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/danfinlay/delegatable-eth/blob/main/packages/hardhat/contracts/Delegatable.sol#L15">the implementation of the invoke method here</a>. It can also help to read <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/danfinlay/delegatable-eth/blob/main/packages/hardhat/scripts/types.js">the type file that is used to generate much of the signature validation code</a>. You can see what it looks like to sign delegations in JS with this library <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.npmjs.com/package/eth-delegatable-utils">eth-delegatable-utils</a>.</p><p>To help guide initial development, I chose to start with the anti-phishing registry use case as <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://mirror.xyz/0x55e2780588aa5000F464f700D2676fD0a22Ee160/8whNch3m5KMzeo6g5eblcXMMplPf8UpW228cSh3nmzg">MobyMask</a> because it a very simple contract, is a pressing and dire issue, has relatively low stakes if it turns out to be flawed, and it demonstrates a non-financial use case for a blockchain, which I think could be a useful cultural bridge for expanding the discourse of what blockchains are good for. I believe it’s valuable to think about how applications that minimize reliance on a blockchain can still leverage one for key security critical operations, like managing a sensitive access policy.</p><p>I think distributing negative reputation in the form of a phishing list is ultimately an incomplete solution, and is only needed on sites where public replies by default and paid ads are the norm, and this issue could be more completely eliminated by changing those norms, but via this tool I hope to demonstrate how these web3 tools can help solve web2 problems.</p><p>Long term, there are a wide range of possible uses for making a smart contract Delegatable, but I think it could benefit just about any smart contract. Some ideas:</p><ul><li><p>Finer grained allowances, without needing on-chain transactions.</p></li><li><p>Site logins that imbue any number of on-chain permissions</p></li><li><p>Issuing transitive allowances, enabling a form of micro-credit.</p></li><li><p>Providing a kind of <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://medium.com/capabul/the-simplest-trustworthy-oracle-fad057c5b271">peer to peer insurance</a> without reliance on a global oracle.</p></li><li><p>Creating <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/danfinlay/status/1127686312033579008">a referral economy that incentivizes honest reviews and rewards influencers</a>.</p></li><li><p>Off chain restricted order books can allow any number of deal-finders to get a commission, while also reducing the possible buyers, which could help combat miner extractible value.</p></li></ul><p>Part of why I’m a fan of <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://eips.ethereum.org/EIPS/eip-3074">EIP-3074</a> or <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/ethereum/EIPs/pull/5003">EIP-5003: AUTH_USURP</a> is that they would allow any ETH account to benefit from all of the features I’m showing off in the delegatable framework for free, for all contracts they interact with, with no transactions needed until an on-chain action is performed.</p><p>If you’d like to try contributing to MobyMask, you can <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/danfinlay/MobyMask">find it on github here</a>.</p><p>If you’d like to try out the Delegatable framework, you can <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/danfinlay/delegatable-eth">find it on github here</a>.</p><p>If you want to hear me talk more on this topic and how it relates to my broader work at MetaMask, I discuss it a bit on the Epicenter podcast here.</p><p>If you’d like to join me and help build a more dynamic, secure, and cheap decentralized future, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://grnh.se/43dbcbde1us">we’re hiring</a>.</p><p>Thanks for reading ❤️</p><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://etherscan.io/address/0xD7640b32F4b91BbF498B4cC686B6B7C2e82B84cB">edition://0xD7640b32F4b91BbF498B4cC686B6B7C2e82B84cB?editionId=0</a></p>]]></content:encoded>
            <author>dan-finlay@newsletter.paragraph.com (Dan Finlay)</author>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/2f157582da6bd141806ee20b8bb5c3e39b07e0b4fe1e4668570bc0ad593b37df.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[   MobyMask: An Initiative to Eliminate Phishers  ]]></title>
            <link>https://paragraph.com/@dan-finlay/mobymask-an-initiative-to-eliminate-phishers</link>
            <guid>kqBUgdMwCaSgMjH5CDOu</guid>
            <pubDate>Wed, 01 Jun 2022 15:07:56 GMT</pubDate>
            <description><![CDATA[MobyMask is the first demonstration of a new crypto primitive and the kinds of interactions it makes possible: Delegatable, which allows any contract to easily enjoy webs of off-chain invitations and invocations, with on-chain redemption and revocation for enforcement. You can watch a video presentation of MobyMask here.“All men live enveloped in whale-lines. All are born with halters round their necks; but it is only when caught in the swift, sudden turn of death, that mortals realize the si...]]></description>
            <content:encoded><![CDATA[<p>MobyMask is the first demonstration of a new crypto primitive and the kinds of interactions it makes possible: <strong>Delegatable</strong>, which allows any contract to easily enjoy webs of off-chain invitations and invocations, with on-chain redemption and revocation for enforcement.</p><p>You can watch <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://youtu.be/OA1RR4cbWzY">a video presentation of MobyMask here</a>.</p><blockquote><p><em>“All men live enveloped in whale-lines. All are born with halters round their necks; but it is only when caught in the swift, sudden turn of death, that mortals realize the silent, subtle, ever-present perils of life.”  — Herman Meliville, Moby Dick</em></p></blockquote><p>The internet today is not unlike the oceans of 1800s Nantucket, where those that “reside alone and riot on the sea” slaughtered masses of whales for great fortune. Now the sea is our social media feeds. Simply send a Tweet with the word “MetaMask” and you are met with a different type of phisher, likely a bot sporting a familiar-looking username like @metamask095 or @RealOfficialSupp0rt.</p><p>Phishing has gotten so bad that now 80% of all tickets MetaMask receives through its support are <em>users reporting phishers.</em> MetaMask maintains our own phishing list and warns users when visiting reported domains, but we struggle to keep up with the influx of reports, and the social platforms where phishers roam free are failing to solve this issue.</p><p>What if we could harness the power of the community that is already reporting scammers around the web every day? Better yet, what if we could label these fake accounts so that the next person doesn’t get fooled into thinking they are interacting with an official support handle?</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/dcd14c3fcf25ec20d2f7fe28657483691b93d70e256b290c08aef9ce72623f76.png" alt="The white whale logo I drew. Isn&apos;t it pretty?" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">The white whale logo I drew. Isn&apos;t it pretty?</figcaption></figure><p>For this year’s ConsenSys Cypherpunk Hackathon, I decided to take on the phishers with a project I’ve called MobyMask. Unlike the singular Moby-Dick, MobyMask becomes more powerful as more people join to form a web of trust using a new solidity library I made called <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/danfinlay/delegatable-eth#delegatable">Delegatable</a>. Delgatable lets you sign off-chain messages that grant powers to other people. These powers are non-transferrable (dare I say <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://vitalik.ca/general/2022/01/26/soulbound.html">soulbound</a>?). New members are able to invite other members to report, and all reports are transparent enabling accountability via a single revocation that can disable all invitations by a suspect member.</p><p>It doesn’t look like much, but it does a few things that no other web3 dapp is doing today.</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/d56f1f027f54d71e5e74e446e884731725dad342e60fddaba06023349fb7c176.png" alt="The current landing page for members." blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">The current landing page for members.</figcaption></figure><p>With <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://mobymask.com/#/">MobyMask</a>, users can report phishers by entering the accused Twitter handle (more types are easy to add). You can also declare others to be definitely not phishers, and you can also grow the network of phishing reporters by inviting people you trust, by generating an invitation link. All reporters can invite additional reporters, and all invitations can be revoked, which will cancel all memberships that were previously invited by the recipient, and invalidate any of their outstanding report messages.</p><p>The idea is that we can spread the right to report as widely as we reliably can, keep the system transparently accountable, and allow countless phisher detection strategies to aggregate together into a shared database. I believe this could lay the foundation for the most responsive phishing detection system in the world, because it can incorporate any number of strategies, allows instant reporting, while also retaining perfect auditability and accountability.</p><p>These phishing reports are easily validated off-chain, and so while the system is controlled by  an on-chain registry, we can maintain an arbitrarily large off-chain phishing list with no transaction fees, and caching their values, and cross checking them against the chain for revocations periodically.</p><p>That’s right: Users could store these phishing reports so we could have a p2p anti-phishing network with virtually no transaction fees. The blockchain only becomes necessary when a user wants to revoke one of their invitations but is concerned about having that revocation censored by someone in the network. This is very similar to patterns known as verifiable claims or Decentralized Identifiers (DIDs), but with an anchor of trust on-chain.</p><p>Not only are all the phishing reports useful off-chain, but the reports are also batchable, it’s easy in the UI to queue up any number of phishing reports in a single transaction, which makes it cheaper to prove your reports, since they are all validated with just one signature.</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/130733a18400a55c5af3a9b4070f219f29707a351ea18ef13e0be54adb1f5c22.png" alt="Supports batches of reports in a single transaction." blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">Supports batches of reports in a single transaction.</figcaption></figure><p>Since all of these reports can be off-chain and batched by users who are invited with a simple invitation link, I was finding the wallet connection to be too large a burden to put up front on a newly invited phishing reporter. Since the whole point of this project is to rapidly distribute a responsive phishing detection network, any hurdle was one to eliminate.</p><p>To postpone wallet onboarding until a wallet is actually required, I made an onboarding library I’m calling <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.npmjs.com/package/lazyconnect">LazyConnect</a>. It wraps the couple of buttons that actually require the blockchain, so that users are able to do as much as possible before they get a wallet, backup, or any ether for transaction fees.</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/1fda9ddcb27ab5810a8db6130ba8a996a7e032f8553e7c1b8a37556ca8675ec5.png" alt="LazyConnect in action" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">LazyConnect in action</figcaption></figure><p>It’s not too pretty yet, but it has CSS classes for easy customization, and it can allow many users to never need a wallet, or postpone getting one until they have a better reason to. I felt like this was even more important to make possible with the Delegatable framework, since it makes it so easy to create invite links and MetaTransactions, enabling far more user experiences without needing a wallet in the traditional sense.</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/55695d50fea4844103705630124ee11ad34f8dc0f13bcb9cad44278f9d0c4fe9.png" alt="An example of LazyConnect in action" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">An example of LazyConnect in action</figcaption></figure><p>In today’s proof of concept, a wallet is needed to revoke invitations and also to submit reports, but by creating “phishing clients”, we could eliminate the need to submit every report on-chain, and then a wallet would only be needed to revoke invitations, and even then there would still be a possibility for someone to subsidize those reports since all actions in MobyMask are MetaTransactions (and can be submitted by someone else paying the gas).</p><p>The project isn’t quite ready to be useful for stopping phishers just yet. We’re also going to need:</p><ul><li><p>Systems that draw from the database to help warn users faster.</p></li><li><p>Systems that make it easier for users to report in the context where they encounter phishers.</p></li><li><p>Systems for auditing outstanding phishing reports, facilitating conflict resolution (Someone you invited is in a disagreement! Review and revoke if needed, or your membership could be revoked!)</p></li><li><p>Ideally we would integrate reporting &amp; new member invitations all over the web.</p></li></ul><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/f989bedfb358f1c60fc9889c7d767b8ae02b87dab33c72331aa88b40fed9ba5c.png" alt="Ideally we would integrate reporting &amp; new member invitations all over the web." blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">Ideally we would integrate reporting &amp; new member invitations all over the web.</figcaption></figure><p>In the case of a dispute in this system, I suggest we help users see when someone they’ve invited has made a report that is in conflict with someone else’s report, and make it easy to review that conflict and revoke their invitation if they disagree. The incentive is to act quickly, because if someone who invited you reviews the same conflict and finds your invitee in the wrong, it could be <em>your</em> invitation that’s revoked!</p><p>We also have multiple opportunities for optimizing the underlying tech.</p><p>Here’s a diagram of the libraries and tech involved in the current MobyMask proof of concept:</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/9b6b58bb1d22ea6a445a719bfdd36702d5fe3f6f307bab415b75d9a959c09620.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>With a bit more work, we could make self-hostable MobyMask clients that aggregate these off-chain phishing reports and gossip them, allowing the phishing report network to grow without needing most reports to go on-chain. The blockchain becomes an anti-censorship insurance policy: The only things that definitely benefit from it in this system would be publishing revocations that are otherwise being censored from the network. Besides that, it’s not unlike a verified claims system:</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/0b81b8024fb105d9b3292bce9ac09803856c7ba60409512af2bfa949fce05fd1.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>Longer term, here’s what it might look like to have a version that might be lightweight enough to be fully peer to peer, using local counterfactual forks of local <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.laconic.com/">Laconic Network</a> light clients for caching just the relevant data from the blockchain:</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/7b5dcada4bbdb762918129d5df6048b934bd8fa74691e8e3858b227d03d78127.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>Beyond that, we should also allow users to subscribe to any number of “roots of trust” for phishing reports, and other kinds of metadata, too. Phishing reporting is a huge deal, but is also just a first use case for building out the infrastructure to enable the Delegatable pattern.</p><p>If you’re interested in <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/danfinlay/delegatable-eth">Delegatable framework</a> that I used to build this system, I’ve published <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://mirror.xyz/0x55e2780588aa5000F464f700D2676fD0a22Ee160/pTIrlopsSUvWAbnq1qJDNKU1pGNLP8VEn1H8DSVcvXM">a blog post about it more specifically here</a>.</p><p>If you’d like to join me and help build this out, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://grnh.se/43dbcbde1us">we’re hiring</a>.</p><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://etherscan.io/address/0xD7640b32F4b91BbF498B4cC686B6B7C2e82B84cB">edition://0xD7640b32F4b91BbF498B4cC686B6B7C2e82B84cB?editionId=0</a></p>]]></content:encoded>
            <author>dan-finlay@newsletter.paragraph.com (Dan Finlay)</author>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/1e1a8e2f1975b3b96d46f40f2e361a0189d21f67dcc778533253ead9de417e14.jpg" length="0" type="image/jpg"/>
        </item>
    </channel>
</rss>