<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Nomic Foundation - Medium]]></title>
        <description><![CDATA[A non-profit dedicated to Ethereum developers - Medium]]></description>
        <link>https://medium.com/nomic-foundation-blog?source=rss----2db11fd1fd8e---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Nomic Foundation - Medium</title>
            <link>https://medium.com/nomic-foundation-blog?source=rss----2db11fd1fd8e---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:24:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/nomic-foundation-blog" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to write your own Solidity linter using Slang]]></title>
            <link>https://medium.com/nomic-foundation-blog/how-to-write-your-own-solidity-linter-using-slang-356e7565ad1b?source=rss----2db11fd1fd8e---4</link>
            <guid isPermaLink="false">https://medium.com/p/356e7565ad1b</guid>
            <category><![CDATA[solidity]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Igor Matuszewski]]></dc:creator>
            <pubDate>Fri, 14 Jun 2024 14:05:35 GMT</pubDate>
            <atom:updated>2024-06-14T14:05:35.502Z</atom:updated>
            <content:encoded><![CDATA[<h4>… in 25 lines of code!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r_xADsTI36EWd5et3ERbbg.png" /></figure><p><a href="https://github.com/nomicfoundation/slang">Slang</a> is Nomic Foundation’s modular set of compiler APIs empowering the next generation of Solidity code analysis and developer tooling. It’s written in Rust and distributed in multiple languages. It’s currently in alpha stage and in active development, but already useful for many things! Check out the <a href="https://blog.nomic.foundation/slang-alpha-release-6d322cf986a3">initial alpha release announcement</a> to learn more.</p><p>In this guide we will show how you can use Slang to write a simple linter for Solidity in just 25 lines of code. To pick a simple, yet real-life example, we will write our own version of the <a href="https://protofire.github.io/solhint/">solhint</a> <a href="https://solhint-community.github.io/solhint-community/docs/rules/security/avoid-tx-origin.html">avoid-tx-origin</a> rule, which warns whenever tx.origin is used in the code.</p><h3>Let’s get started!</h3><p>The <a href="https://docs.soliditylang.org/en/latest/security-considerations.html#tx-origin">official Solidity documentation includes an example</a> that illustrates why using tx.origin for authorization is a bad idea:</p><pre>// SPDX-License-Identifier: GPL-3.0<br>pragma solidity &gt;=0.7.0 &lt;0.9.0;<br>// THIS CONTRACT CONTAINS A BUG - DO NOT USE<br>contract TxUserWallet {<br>    address owner;<br><br>    constructor() {<br>        owner = msg.sender;<br>    }<br><br>    function transferTo(address payable dest, uint amount) public {<br>        // THE BUG IS RIGHT HERE, you must use msg.sender instead of tx.origin<br>        require(tx.origin == owner);<br>        dest.transfer(amount);<br>    }<br>}</pre><p>We want our linter to be able to briefly report where the offending code is:</p><pre>example.sol:13:17: warning: avoid using `tx.origin`</pre><p>Rather than manually walk the syntax tree to find patterns of source code, like most linters do, we can use Slang’s tree query language, instead. It allows us to concisely specify the pattern we are looking for and the query engine will perform all the heavy-lifting for us!</p><p>To give you a sense of where we’re going, here’s a preview:</p><pre>// Query that we’ll use to find the `tx.origin` expression<br>const query = Query.parse(<br>  `@txorigin [MemberAccessExpression<br>     ... [Expression  ... [&quot;tx&quot;] ...]<br>     ... [MemberAccess ... [&quot;origin&quot;] ...]<br>     ...<br>   ]`,<br>);<br><br>// Parse the source code:<br>const language = new Language(&quot;0.8.22&quot;);<br>const output = language.parse(NonterminalKind.SourceUnit, contents);<br><br>// Query the parsed code...<br>const cursor = output.createTreeCursor();<br>const matches = cursor.query([query]);<br><br>// ...and print the results:<br>let match = null;<br>while ((match = matches.next())) {<br>    const txorigin = match.captures.txorigin[0];<br>    const { line, column } = txorigin.textOffset;<br>    console.warn(`${filePath}:${line + 1}:${column + 1}: warning: avoid using \\`tx.origin\\``);<br>}</pre><p>This prints exactly what we want! Let’s dive in and learn how to implement this step-by-step.</p><h3>Installation</h3><p>First, we need to install Slang. The compiler is written in Rust and distributed both as a Rust package and an NPM package with TypeScript definitions. In this guide, we will use the latter.</p><p>Let’s open a terminal and create a new project:</p><pre>mkdir my-awesome-linter/<br>cd my-awesome-linter<br>npm init<br>npm install @nomicfoundation/slang</pre><h3>Setting up TypeScript</h3><p>We will use TypeScript to write our linter. Let’s install it and create a tsconfig.json file:</p><pre>npm install --save-dev typescript @types/node<br>npx tsc --init</pre><h3>Parsing the Solidity code</h3><p>To analyze the code, we need to parse it into a concrete syntax tree (CST). A CST can represent incomplete or invalid code, and is a good starting point for writing a linter.</p><p>Let’s start by writing a simple index.ts that reads the contents of a file, specified as the first command line argument:</p><pre>// index.ts<br>import fs from &#39;node:fs&#39;;<br>const filePath = process.argv[2];<br>const contents = fs.readFileSync(filePath, &#39;utf8&#39;);</pre><h3>Supporting multiple versions of Solidity</h3><p>The Solidity language has changed quite a lot over time, however Slang is able to parse all versions of Solidity that are in use today, which we consider to be 0.4.11 and later.</p><p>Let’s say that we want to be source-compatible with code that’s expected to work with Solidity 0.8.22. First, we construct an instance of the Language class, which is the main entry point for parsing Solidity code:</p><pre>import { Language } from &quot;@nomicfoundation/slang/language&quot;;<br>const language = new Language(&quot;0.8.22&quot;);</pre><h3>Parsing different language constructs</h3><p>To parse the file using Slang, we’ll use the language.parse() method, which takes a NonterminalKind as its first argument, allowing us to specify which language construct to parse. Since we want to parse the entire file, we&#39;ll use NonterminalKind.SourceUnit.</p><pre>import { NonterminalKind } from &quot;@nomicfoundation/slang/kinds&quot;;<br>const output = language.parse(NonterminalKind.SourceUnit, contents);</pre><h3>Inspecting the parse output</h3><p>The parse function returns a ParseOutput object, which contains the root of the CST (tree()) and a list of parse errors (errors()), if there are any.</p><p>To inspect the CST, we could print it to the console to see what it looks like:</p><pre>const tree = results.tree();<br>console.log(tree.toJSON());<br>// Should print something like:<br>// {&quot;kind&quot;:&quot;SourceUnit&quot;,&quot;text_len&quot;:{...},&quot;children&quot;:[...]}</pre><h3>Matching specific patterns of code</h3><p>We have just parsed the Solidity code into a structured representation that we can now analyze.</p><p>To analyze the CST we will use Slang’s tree query language, which was designed specifically for tasks like ours, and is a great alternative to analyzing the tree manually, due to its brevity and declarative nature.</p><p>The tree queries are instances of the Query class, which are created by parsing a query string, that match specific CST patterns and optionally binds variables to them. The syntax is described in the <a href="https://nomicfoundation.github.io/slang/user-guide/tree-query-language/">Tree Query Language</a> reference.</p><p>Without going too much into the details of this query, we want to match the tx.origin expression, which is a MemberAccessExpression with tx identifier as the left-hand side and origin identifier as the right-hand side:</p><pre>import { Query } from &quot;@nomicfoundation/slang/query&quot;;<br>let query = Query.parse(<br>  `@txorigin [MemberAccessExpression<br>          ...        [Expression  ... @start [&quot;tx&quot;] ...]<br>          ...        [MemberAccess ... [&quot;origin&quot;] ...]<br>          ...<br>    ]`,);</pre><p>That’s a lot to unpack here! Let’s break it down:</p><ul><li>tree nodes are enclosed in square brackets [].</li><li>the first name in the square brackets match the given node’s NonterminalKind.</li><li>after it, there is a list of children nodes we expect to match.</li><li>... is a wildcard that matches any number of children.</li><li>@-prefixed names before nodes are <em>captures</em>, which are used to refer to specific nodes of the matched pattern.</li></ul><h3>Running the queries</h3><p>The queries are executed using the Cursor class, which is another way to traverse the syntax tree, so we need to instantiate one that starts at the root of the tree:</p><pre>const cursor = results.createTreeCursor();<br>// This is a shorthand for:<br>// results.tree().createCursor({ utf8: 0, utf16: 0, line: 0, column: 0 })</pre><p>While it’s possible to run multiple different queries concurrently using the same cursor, we will only run one in our case:</p><pre>const matches = cursor.query([query]);</pre><p>To access the matched QueryResults, we need to call next() repeatedly until it returns null:</p><pre>let match = null;<br>while (match = matches.next()) {<br>    // ... do something with the matched tree fragment<br>}</pre><p>Now, for each query result, we can use the captures we defined in the query to access the nodes we are interested in.</p><p>Each cursor points to a single node but a capture can return multiple cursors, depending on the query. In our case @txorigin will return an array of one Cursor pointing to a MemberAccessExpression node.</p><p>Let’s inspect the JSON representation of the matched node pointed to by a Cursor:</p><pre>const txorigin = match.captures.txorigin[0];<br>console.log(txorigin.node().toJSON());<br>// Should print our matched node:<br>// {&quot;kind&quot;:&quot;MemberAccessExpression&quot;,&quot;text_len&quot;:{...},&quot;children&quot;:[...]}</pre><h3>Reporting the findings</h3><p>The only thing left to do is to report our findings to the user.</p><p>Because we get back a Cursor that points to the offending node from our queries, we can use its .textOffset property to map back its position in the source code. This property contains .line and .column properties that are exactly what we need. It’s worth keeping in mind that Slang uses 0-based indexing but the error reporting/editors often use more natural 1-based indexing, so we need to add 1 to these offsets to use it.</p><p>Having that, we can print out the warning message informing the user where the offending code is:</p><pre>const txorigin = match.captures.txorigin[0];<br>const { line, column } = txorigin.textOffset;<br>console.warn(`${filePath}:${line + 1}:${column + 1}: warning: avoid using \\`tx.origin\\``);</pre><p>To access the full span of the node, we could use the textRange property on the cursor, which returns the start and the end offsets of the node in the source code.</p><p>We could get even more creative and plug this information into a custom formatter of our choice, but for now this will suffice.</p><h3>Putting it all together</h3><p>Here’s the complete code for our linter:</p><pre>// file: index.ts<br>import fs from &quot;node:fs&quot;;<br>import { Language } from &quot;@nomicfoundation/slang/language&quot;;<br>import { NonterminalKind } from &quot;@nomicfoundation/slang/kinds&quot;;<br>import { Query } from &quot;@nomicfoundation/slang/query&quot;;<br><br>const filePath = process.argv[2];<br>const contents = fs.readFileSync(filePath, &quot;utf8&quot;);<br><br>const language = new Language(&quot;0.8.22&quot;);<br>const output = language.parse(NonterminalKind.SourceUnit, contents);<br>const query = Query.parse(<br>  `@txorigin [MemberAccessExpression<br>     ...<br>     [Expression  ... [&quot;tx&quot;] ...]<br>     ...<br>     [MemberAccess ... [&quot;origin&quot;] ...]<br>   ]`,<br>);<br><br>const cursor = output.createTreeCursor();<br>const matches = cursor.query([query]);<br><br>let match = null;<br>while ((match = matches.next())) {<br>    const txorigin = match.captures.txorigin[0];<br>    const { line, column } = txorigin.textOffset;<br>    console.warn(`${filePath}:${line + 1}:${column + 1}: warning: avoid using \\`tx.origin\\``);<br>}<br></pre><p>If we don’t count the empty lines, the code is indeed 25 lines long! 🎉</p><h3>Conclusion</h3><p>In this guide, we’ve demonstrated how to create a simple linter for Solidity using Slang, implementing a simple version of the avoid-tx-origin rule from solhint in just 25 lines of code.</p><p>We covered the essentials of parsing Solidity code, identifying specific code patterns, and reporting findings to users in a clear and straightforward manner.</p><p>We hope that this guide has inspired you to write your own linters or any other tools that operate on Solidity code using Slang!</p><p>If you have any questions or feedback, feel free to reach out to us on <a href="https://github.com/NomicFoundation/slang">GitHub</a> and/or check out Slang’s <a href="https://nomicfoundation.github.io/slang/">documentation</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=356e7565ad1b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nomic-foundation-blog/how-to-write-your-own-solidity-linter-using-slang-356e7565ad1b">How to write your own Solidity linter using Slang</a> was originally published in <a href="https://medium.com/nomic-foundation-blog">Nomic Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Secure deployments with Hardhat Ignition and Ledger hardware wallets]]></title>
            <link>https://medium.com/nomic-foundation-blog/secure-deployments-with-hardhat-ignition-and-ledger-hardware-wallets-028080159e77?source=rss----2db11fd1fd8e---4</link>
            <guid isPermaLink="false">https://medium.com/p/028080159e77</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[ledger]]></category>
            <category><![CDATA[solidity]]></category>
            <category><![CDATA[hardhat-ignition]]></category>
            <dc:creator><![CDATA[Zoey]]></dc:creator>
            <pubDate>Tue, 14 May 2024 12:47:59 GMT</pubDate>
            <atom:updated>2024-05-14T12:47:59.317Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JTuDWgPZWc8P9XpfrnYa3A.png" /></figure><p>As you may know, we recently <a href="https://medium.com/nomic-foundation-blog/introducing-hardhat-ignition-a-refreshed-deployments-experience-9580d2946e10">introduced Hardhat Ignition</a>, a declarative system for deploying smart contracts on Ethereum, which aims to pick up the torch fromhardhat-deployand expand Hardhat&#39;s deployment capabilities.</p><p>Among many other features, Hardhat Ignition supports deploying contracts using a Ledger hardware wallet via the hardhat-ledger plugin. This guide will show you how to deploy your contracts using a Ledger device.</p><p>The first step is to install the hardhat-ledger plugin:</p><pre>npm install --save-dev @nomicfoundation/hardhat-ledger</pre><h3>Configuring the Ledger plugin</h3><p>We are going to use the <a href="https://ethereum.org/en/developers/docs/networks/#sepolia">Sepolia testnet</a> to deploy our Hardhat Ignition module, so you need to add this network in your Hardhat config. Here we are using <a href="https://alchemy.com/">Alchemy</a> to connect to the network.</p><p>You’ll also need to add the @nomicfoundation/hardhat-ledger plugin to your Hardhat config file, configure it for Sepolia, and add the accounts on your Ledger that you’ll use to deploy:</p><pre>// ...rest of your imports...<br>import(&quot;@nomicfoundation/hardhat-ledger&quot;);<br><br>// Go to &lt;https://alchemy.com&gt;, sign up, create a new App in<br>// its dashboard, and set the Hardhat configuration variable<br>// ALCHEMY_API_KEY to the key<br>const ALCHEMY_API_KEY = vars.get(&quot;ALCHEMY_API_KEY&quot;);<br>export default {<br>  // ...rest of your config...<br>  networks: {<br>    sepolia: {<br>      url: `https://eth-sepolia.g.alchemy.com/v2/${ALCHEMY_API_KEY}`,<br>      ledgerAccounts: [<br>        // This is an example address<br>        // Be sure to replace it with an address from your own Ledger device<br>        &quot;0xa809931e3b38059adae9bc5455bc567d0509ab92&quot;,<br>      ],<br>    },<br>  },<br>};</pre><p>To deploy on Sepolia you need to send some Sepolia ETH to the address that’s going to be making the deployment. You can get testnet ETH from a faucet, a service that distributes testing-ETH for free. Here is <a href="https://sepoliafaucet.com/">Alchemy’s Sepolia Faucet</a>.</p><p>For more information on how to configure the hardhat-ledger plugin for things like derivation path, or learning how to use it for signatures, check out the <a href="https://hardhat.org/hardhat-runner/plugins/nomicfoundation-hardhat-ledger">plugin’s documentation</a>.</p><h3>Deploying with Ledger</h3><p>After configuring the plugin, you can now deploy your module as you normally would, and Hardhat Ignition will use your Ledger device to sign the transactions. For this example, we’ll be deploying the Apollo module from the Hardhat Ignition <a href="https://hardhat.org/ignition/docs/getting-started#quick-start">quick start guide</a>. Ensure that your Ledger device is plugged in, unlocked, connected to the Ethereum app, and with <a href="https://www.ledger.com/academy/enable-blind-signing-why-when-and-how-to-stay-safe">Blind Signing enabled</a>, then run the deploy command:</p><pre>npx hardhat ignition deploy ignition/modules/Apollo.ts --network sepolia</pre><p>This will deploy as usual, however, you will now be prompted on your Ledger device to confirm each transaction before it’s sent to the network. You should see a message like the following in your terminal:</p><pre>Hardhat Ignition 🚀</pre><pre>Deploying [ Apollo ]</pre><pre>Batch #1<br>  Executing Apollo#Rocket...</pre><pre>  Ledger: Waiting for confirmation on device</pre><p>At this point, you should see a prompt on your Ledger device to confirm the transaction. Once you confirm, the message will update to show that the transaction was sent to the network, and you’ll see the deployment progress in your terminal.</p><p>To learn more, check out the <a href="https://hardhat.org/ignition/docs/getting-started#overview">Hardhat Ignition</a> and the <a href="https://hardhat.org/hardhat-runner/plugins/nomicfoundation-hardhat-ledger">hardhat-ledger plugin</a> documentation.</p><h3>Feedback welcome</h3><p>We would love your feedback if you run into any issues or have any feature requests! Please <a href="https://github.com/NomicFoundation/hardhat-ignition/issues/new">open an issue on Github</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=028080159e77" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nomic-foundation-blog/secure-deployments-with-hardhat-ignition-and-ledger-hardware-wallets-028080159e77">Secure deployments with Hardhat Ignition and Ledger hardware wallets</a> was originally published in <a href="https://medium.com/nomic-foundation-blog">Nomic Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet the Nomic Team — Antony Blakey, Applied Researcher]]></title>
            <link>https://medium.com/nomic-foundation-blog/meet-the-nomic-team-antony-blakey-applied-researcher-553aa0b76fbd?source=rss----2db11fd1fd8e---4</link>
            <guid isPermaLink="false">https://medium.com/p/553aa0b76fbd</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[nomic-foundation]]></category>
            <category><![CDATA[team-culture]]></category>
            <dc:creator><![CDATA[Dasha Nikolov]]></dc:creator>
            <pubDate>Mon, 29 Apr 2024 16:58:06 GMT</pubDate>
            <atom:updated>2024-04-29T16:58:38.789Z</atom:updated>
            <content:encoded><![CDATA[<h3>Meet the Nomic Team — Antony Blakey, Applied Researcher</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*I_IrA0u2LbWbLnvrLkdB1A.png" /></figure><p>We’re excited to shine the spotlight on Antony — a former co-lead on Slang, our Solidity compiler project, who is now focused on doing Applied Research across all of our projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lAaYxkIMlJ2IeY5lvjbAcA.jpeg" /></figure><h3>Where are you located? Is that where you are from originally?</h3><p>I currently work from Melbourne, Australia. Prior to joining Nomic I spent 6 years working in Amsterdam. I am originally from Adelaide, Australia.</p><h3>Who are you outside of work? What do you like to do in your spare time?</h3><p>Outside of work I am a goatherd in Afghanistan, or sometimes a dairy cow in rural England.</p><p>But seriously … I have many interests. I studied philosophy and music, and both are still a huge part of my life. I love Kant, Nietzsche and Singer. I am a musical theorist and a sometime composer. I have an abiding love of both language e.g. Shakespeare, and linguistics, particularly computational morphotactics, language evolution, and typology. I got into 3D FDM printing at it’s hobbyist-level inception, and I’ve since got into building and using CNC machines for both wood and metal. I owned a small farm with the goal of becoming a permaculturist — but it turns out I’m a thinker more than a real dirt farmer. I do hydroponics, both manual and automated. I have some agricultural robotics projects on the go involving visual servoing and low accuracy mechanical construction, which is a more accurate model of how humans operate. I am into generative art, both visual and aural, particularly in relation to the reification of generative artefacts using e.g. CNC and robotics.</p><p>Basically, creating/designing/building/growing stuff.</p><h3>What were you doing professionally before joining Nomic?</h3><p>My father was an independent software consultant, so I was able to start professionally in 1977, at age 11, doing maintenance on COBOL systems that would be today called ERP. That was my main source of income for 10 years, although I also did some commercial Prolog, and C, and spent my spare time doing APL, reading SIGPLAN, and building, amongst other things, a compiler in COBOL. If I could go back in time I would tell myself to instead build a Scheme interpreter in COBOL and then use Scheme for everything else.</p><p>I was very lucky.</p><p>From then until 2001 I built software startups, and did the whole VC dance, which was going gangbusters until the September 11 attacks dried up the VC market in Australia.</p><p>I slowed down to recover, and spent some years on a retainer for a company that was using the technology I had developed, whilst also working on a foreign aid project in Mindanao in the Southern Philippines.</p><p>I completely stopped work for a few years, and built a CNC workshop to build musical instruments such as violins (my wife is a concert violinist).</p><p>I rejoined the software engineering community doing various interesting gigs, including 9 years working with Smalltalk, first as part of the team maintaining and improving VisualWorks Smalltalk, then at a Dutch company working on the energy market day-ahead trading system. I also did some machine learning and designed and built electronic sensors for a large air-quality monitoring project. This all culminated in building a new Smalltalk runtime/compiler in Rust targeting WASM for delivery in the browser. And thus, Nomic.</p><h3>Why did you decide to join the team?</h3><p>“Come build a greenfield modular compiler, in Rust, for use in developer tools”. Are you kidding?</p><p>In Smalltalk the compiler, IDE, and runtime are all the same thing, so this was right up my alley.</p><p>On top of that, working for a non-profit, on technology designed to liberate the powerless from the control of organised capital, was a deal-clincher. We discussed quite a bit of philosophy in the interviews — it was fantastic! The founders, Franco and Pato, completely won me over. They are better founders than I ever was.</p><h3>What’s your story behind getting into crypto/blockchain/decentralized tech?</h3><p>At the risk of sounding like a heretic, I am not into crypto at all. And barely into blockchain. However once the role of these technologies in liberating the disempowered and attacking corruption were explained, I was completely onboard.</p><p>From a purely technical perspective however, I have a longstanding interest in decentralised systems, and how to make them robust and sustainable. So Ethereum in particular is very attractive.</p><h3>What are the things that you enjoy and appreciate about working at Nomic?</h3><p>The people, the culture, the mission, and the challenging work.</p><p>Steve Jobs said “great artists ship”, and this is the first organisation I’ve worked for that truly understands both sides of that equation. I think we strike a good balance between doing it right, creating a beautiful architecture, and delivering something valuable.</p><h3>Which one of our <a href="https://nomic.foundation/jobs">core values</a> resonates with you the most and why? How do you see it being “used” at Nomic?</h3><p>I am closely aligned, philosophically and politically, with most of Nomic’s core values, so I can’t pick just one. I would however highlight <strong>kindness</strong>, because it is a very rare value for an organisation to have and even rarer to make explicit. It permeates our entire operation.</p><h3>What are you excited about when you think about your future at Nomic?</h3><p>I rarely think about my career in the sense most do, and so I don’t have an answer for this exact question. However I am excited about our roadmap, both short- and long-term, and the work we are doing. I would be very content to stay in the Nomic family forever.</p><h3>What is your best tip for staying productive and happy when working remotely?</h3><p>Have a nice place to work, preferably with a view of something appealing. Look after your body — I can recommend the Herman Miller “Embody” chair.</p><p>The traditional advice is to get dressed, and ‘go to work’, even when you work from home.</p><p><strong>Nomic Foundation is growing</strong>, and we’re looking to hire senior engineers and engineering managers that want to work on developer tooling in Ethereum. If this sounds like you, we welcome you to check out our open roles <a href="https://nomic.foundation/jobs">here.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=553aa0b76fbd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nomic-foundation-blog/meet-the-nomic-team-antony-blakey-applied-researcher-553aa0b76fbd">Meet the Nomic Team — Antony Blakey, Applied Researcher</a> was originally published in <a href="https://medium.com/nomic-foundation-blog">Nomic Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to verify your deployment on Etherscan with Hardhat Ignition]]></title>
            <link>https://medium.com/nomic-foundation-blog/how-to-verify-your-deployment-on-etherscan-with-hardhat-ignition-5cbb7ee6c7be?source=rss----2db11fd1fd8e---4</link>
            <guid isPermaLink="false">https://medium.com/p/5cbb7ee6c7be</guid>
            <category><![CDATA[etherscan]]></category>
            <category><![CDATA[hardhat-ignition]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[solidity]]></category>
            <dc:creator><![CDATA[Zoey]]></dc:creator>
            <pubDate>Thu, 25 Apr 2024 18:17:10 GMT</pubDate>
            <atom:updated>2024-05-06T17:51:29.910Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JTuDWgPZWc8P9XpfrnYa3A.png" /></figure><p>Now that Hardhat Ignition is celebrating both a feature set that is reaching maturity as well as its inclusion inside <a href="https://hardhat.org/hardhat-runner/plugins/nomicfoundation-hardhat-toolbox">Hardhat Toolbox</a>, we’ve added several powerful new features we’re excited to show off including <a href="https://hardhat.org/ignition/docs/guides/create2">native create2 support</a>, <a href="https://hardhat.org/ignition/docs/advanced/reconciliation">resumable deployments</a>, and <a href="https://hardhat.org/ignition/docs/guides/viem">full contract type inference with Viem</a>. The one we’ll be taking a look at today is source verification of your Hardhat Ignition deployments.</p><p>In this guide you will deploy your Hardhat Ignition module to a live network and verify the source code of each of its contracts.</p><p>Verifying a contract means making its source code public, along with the compiler settings you used, which allows anyone to verify what the contract is doing, and even compile it and run it locally. Doing this is extremely important in an open platform like Ethereum.</p><p>In this guide we’ll explain how to do this with the <a href="https://etherscan.io/">Etherscan</a> explorer.</p><h3>Getting an API key from Etherscan</h3><p>The first thing you need is an API key from Etherscan. To get one, go to <a href="https://etherscan.io/login">their site</a>, sign in (or create an account if you don’t have one) and open the “API Keys” tab. Then click the “Add” button and give a name to the API key you are creating (e.g. “Hardhat”). After that you’ll see the newly created key in the list.</p><p>Open your Hardhat config and add the API key you just created:</p><pre>// hardhat.config.ts<br><br>export default {<br>  // …rest of the config…<br>  etherscan: {<br>    apiKey: &quot;ABCDE12345ABCDE12345ABCDE123456789&quot;,<br>  },<br>};</pre><h3>Deploying and verifying on the Sepolia testnet</h3><p>We are going to use the <a href="https://ethereum.org/en/developers/docs/networks/#sepolia">Sepolia testnet</a> to deploy and verify our Ignition module, so you need to add this network in your Hardhat config. Here we are using <a href="https://alchemy.com/">Alchemy</a> to connect to the network.</p><p>This example uses a new Hardhat feature called configuration variables. Read more about `vars` and configuration variables on our <a href="https://blog.nomic.foundation/hardhat-v2-19-0-introducing-configuration-variables-b528c0c9a7c0">announcement blog post</a>.</p><pre>// hardhat.config.ts<br><br>// Go to https://alchemy.com, sign up, create a new App in<br>// its dashboard, and set the Hardhat configuration variable<br>// ALCHEMY_API_KEY to the key<br>const ALCHEMY_API_KEY = vars.get(&quot;ALCHEMY_API_KEY&quot;);<br><br>// Replace this private key with your Sepolia test account private key<br>// To export your private key from Coinbase Wallet, go to<br>// Settings &gt; Developer Settings &gt; Show private key<br>// To export your private key from Metamask, open Metamask and<br>// go to Account Details &gt; Export Private Key<br>// Beware: NEVER send mainnet ETH into testing accounts<br>const SEPOLIA_PRIVATE_KEY = vars.get(&quot;SEPOLIA_PRIVATE_KEY&quot;);<br><br>export default {<br>  // ...rest of your config...<br>  networks: {<br>    sepolia: {<br>      url: `https://eth-sepolia.g.alchemy.com/v2/${ALCHEMY_API_KEY}`,<br>      accounts: [SEPOLIA_PRIVATE_KEY],<br>    },<br>  },<br>};</pre><p>To deploy on Sepolia you need to send some Sepolia ETH to the address that’s going to be making the deployment. You can get testnet ETH from a faucet, a service that distributes testing-ETH for free. Here is <a href="https://sepoliafaucet.com/">Alchemy’s Sepolia Faucet</a>.</p><p>This guide assumes you are using the contracts and HardhatIgnition module from the <a href="https://hardhat.org/ignition/docs/getting-started#quick-start">quick start guide</a>, but the steps are the same for any deployment.</p><p>Now you are ready to deploy your module to the testnet, but first we are going to make the source code of our contract unique. The reason we need to do this is that the sample code from the quick start guide is already verified in Sepolia, so if you try to verify it you’ll get a warning. If you are using your own contracts, you can likely skip this step.</p><p>Open your contract and add a comment with something unique, like your GitHub’s username. Keep in mind that whatever you include here will be, like the rest of the code, publicly available on Etherscan:</p><pre>// Author: @janedoe<br>contract Rocket {</pre><p>You can now run the deployment using the newly added Sepolia network:</p><pre>npx hardhat ignition deploy ignition/modules/Apollo.ts --network sepolia --verify</pre><p>The ` — verify` flag is optional, but it tells Hardhat Ignition to verify the contracts after a successful deployment.</p><p>If you have an existing deployment and want to verify it, you can also run the `verify` task directly by passing the deployment ID:</p><pre>npx hardhat ignition verify chain-11155111</pre><p>If you get an error saying that the address does not have bytecode, it probably means that Etherscan has not indexed your contract yet. In that case, wait for a minute and then try again.</p><p>After the task has successfully executed, for each deployed contract you’ll see a link to its publicly verified code.</p><p>To learn more about verifying, read the <a href="https://hardhat.org/hardhat-runner/plugins/nomicfoundation-hardhat-verify">hardhat-verify</a> documentation.</p><h3>Feedback welcome</h3><p>We would love your feedback if you run into any issues or have any feature requests! Please <a href="https://github.com/NomicFoundation/hardhat-ignition/issues/new">open an issue on Github</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cbb7ee6c7be" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nomic-foundation-blog/how-to-verify-your-deployment-on-etherscan-with-hardhat-ignition-5cbb7ee6c7be">How to verify your deployment on Etherscan with Hardhat Ignition</a> was originally published in <a href="https://medium.com/nomic-foundation-blog">Nomic Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Migrating to Hardhat Ignition from hardhat-deploy]]></title>
            <link>https://medium.com/nomic-foundation-blog/migrating-to-hardhat-ignition-from-hardhat-deploy-c17311bb658f?source=rss----2db11fd1fd8e---4</link>
            <guid isPermaLink="false">https://medium.com/p/c17311bb658f</guid>
            <category><![CDATA[hardhat-ignition]]></category>
            <category><![CDATA[solidity]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[John Kane]]></dc:creator>
            <pubDate>Mon, 01 Apr 2024 17:20:14 GMT</pubDate>
            <atom:updated>2024-04-01T17:22:34.902Z</atom:updated>
            <content:encoded><![CDATA[<h3>Migrating from hardhat-deploy to Hardhat Ignition</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TNFkLI2xqVYEAqrTxL7dYA.png" /></figure><p>For several years, the hardhat-deploy community plugin has been a go-to solution for deploying smart contracts within the Hardhat community. Recently, we <a href="https://medium.com/nomic-foundation-blog/introducing-hardhat-ignition-a-refreshed-deployments-experience-9580d2946e10">introduced Hardhat Ignition</a>, a declarative system for deploying smart contracts on Ethereum, which aims to pick up the torch fromhardhat-deployand expand Hardhat&#39;s deployment features.</p><p>This guide will walk you through migrating your Hardhat project from hardhat-deploy to Hardhat Ignition.</p><h3>Installing Hardhat Ignition</h3><p>To get started, we’ll uninstall the hardhat-deploy plugin and install the Hardhat Ignition one by executing the following steps:</p><ol><li>Remove the hardhat-deploy packages from your project:</li></ol><pre>npm uninstall hardhat-deploy hardhat-deploy-ethers</pre><p>2. Install the Hardhat Ignition package and hardhat-network-helpers to provide additional testing support as a replacement for hardhat-deploy functionality like EVM snapshots:</p><pre>npm install --save-dev @nomicfoundation/hardhat-ignition-ethers @nomicfoundation/hardhat-network-helpers</pre><p>3. Update the project’s hardhat.config file to remove hardhat-deploy and hardhat-deploy-ethers and instead import Hardhat Ignition:</p><pre>- import &quot;hardhat-deploy&quot;;<br>- import &quot;hardhat-deploy-ethers&quot;;<br>+ import &quot;@nomicfoundation/hardhat-ignition-ethers&quot;;</pre><h3>Convert deployment scripts to Ignition Modules</h3><p>hardhat-deploy represents contract deployments as JavaScript or TypeScript files under the ./deploy/ folder. Hardhat Ignition follows a similar pattern with deployments encapsulated as modules; these are JS/TS files stored under the ./ignition/modules directory. Each hardhat-deploy deploy file will be converted or merged into a Hardhat Ignition module.</p><p>Let’s first create the required folder structure under the root of your project:</p><pre>mkdir ignition<br>mkdir ignition/modules</pre><p>Now, let’s work through converting a simple hardhat-deploy script for this example Token contract:</p><pre>// SPDX-License-Identifier: MIT<br>pragma solidity ^0.8.19;<br><br>contract Token {<br>    uint256 public totalSupply = 1000000;<br>    address public owner;<br>    mapping(address =&gt; uint256) balances;<br>    constructor(address _owner) {<br>        balances[_owner] = totalSupply;<br>        owner = _owner;<br>    }<br>    function balanceOf(address account) external view returns (uint256) {<br>        return balances[account];<br>    }<br>    function transfer(address to, uint256 amount) external {<br>        require(balances[msg.sender] &gt;= amount, &quot;Not enough tokens&quot;);<br>        balances[msg.sender] -= amount;<br>        balances[to] += amount;<br>    }<br>}</pre><p>A hardhat-deploy deploy function for the Token contract might look like this:</p><pre>// ./deploy/001_deploy_token.ts<br>import { HardhatRuntimeEnvironment } from &quot;hardhat/types&quot;;<br>import { DeployFunction } from &quot;hardhat-deploy/types&quot;;<br><br>const func: DeployFunction = async function (hre: HardhatRuntimeEnvironment) {<br>  const { deployments, getNamedAccounts } = hre;<br>  const { deploy } = deployments;<br> /*<br>  The deploy function uses the hardhat-deploy named accounts feature<br>  to set the deployment&#39;s `from` and `args` parameters.<br> */<br>  const { deployer, tokenOwner } = await getNamedAccounts();<br>  await deploy(&quot;Token&quot;, {<br>    from: deployer,<br>    args: [tokenOwner],<br>    log: true,<br>  });<br>};<br>export default func;</pre><p>Using an Ignition Module, the equivalent account access code would look like this:</p><pre>// ./ignition/modules/Token.ts<br>import { buildModule } from &quot;@nomicfoundation/hardhat-ignition/modules&quot;;<br><br>/*<br> The callback passed to `buildModule()` provides a module builder object `m`<br> as a parameter. Through this builder object, you access the Module API.<br> For instance, you can deploy contracts via `m.contract()`.<br>*/<br>export default buildModule(&quot;TokenModule&quot;, (m) =&gt; {<br> /* <br>  Instead of named accounts, you get access to the configured accounts<br>  through the `getAccount()` method.<br> */<br>  const deployer = m.getAccount(0);<br>  const tokenOwner = m.getAccount(1);<br><br> /*<br>  Deploy `Token` by calling `contract()` with the constructor arguments<br>  as the second argument. The account to use for the deployment transaction<br>  is set through `from` in the third argument, which is an options object.<br> */<br>  const token = m.contract(&quot;Token&quot;, [tokenOwner], {<br>    from: deployer,<br>  });<br><br> /*<br>  The call to `m.contract()` returns a future that can be used in other `m.contract()`<br>  calls (e.g. as a constructor argument, where the future will resolve to the<br>  deployed address), but it can also be returned from the module. Contract<br>  futures that are returned from the module can be leveraged in Hardhat tests<br>  and scripts, as will be shown later.<br> */<br>  return { token };<br>});</pre><p>The conversion to an Ignition module can be tested by running the module against Hardhat Network:</p><pre>npx hardhat ignition deploy ./ignition/modules/Token.ts</pre><p>Which, if working correctly, will output the contract’s deployed address:</p><pre>You are running Hardhat Ignition against an in-process instance of Hardhat Network.<br>This will execute the deployment, but the results will be lost.<br>You can use --network &lt;network-name&gt; to deploy to a different network.<br><br>Hardhat Ignition 🚀<br><br>Deploying [ TokenModule ]<br><br>Batch #1<br>  Executed Token#Token<br><br>[ Token ] successfully deployed 🚀<br><br>Deployed Addresses<br>Token#Token - 0x5FbDB2315678afecb367f032d93F642f64180aa3</pre><p>To learn more, check out the detailed <a href="https://hardhat.org/ignition/docs/guides/creating-modules">guide on writing Hardhat Ignition modules</a>, which showcases all available features.</p><h3>Migrating tests that rely on hardhat-deploy fixtures</h3><p>Let’s go over the process of rewriting Hardhat tests that rely on hardhat-deploy fixture functionality. Using hardhat-deploy, calls to fixture() deploy everything under the ./deploy and create a snapshot in the in-memory Hardhat node at the end of the first run. Subsequent calls to fixture() revert to the saved snapshot, avoiding rerunning the deployment transactions and thus saving time.</p><p>To do this, hardhat-deploy-ethers enhances the Hardhat ethers object with a getContract method that will return contract instances from the fixture snapshot.</p><pre>import { expect } from &quot;chai&quot;;<br>import { Contract } from &quot;ethers&quot;;<br>import { ethers, deployments, getNamedAccounts } from &quot;hardhat&quot;;<br><br>describe(&quot;Token contract&quot;, function () {<br>  it(&quot;should assign the total supply of tokens to the owner&quot;, async function () {<br>  <br>  // Create fixture snapshot<br>    await deployments.fixture();<br><br>  // This will get an instance from the snapshot<br>    const token: Contract = await ethers.getContract(&quot;Token&quot;);<br><br>    const { tokenOwner } = await getNamedAccounts();<br>    expect(await token.balanceOf(tokenOwner)).to.equal(<br>      await token.totalSupply()<br>    );<br>  });<br>});</pre><p>Hardhat Ignition, in conjunction with the hardhat-network-helpers plugin, also allows you to use fixtures:</p><pre>import { loadFixture } from &quot;@nomicfoundation/hardhat-toolbox/network-helpers&quot;;<br>import { expect } from &quot;chai&quot;;<br>import { ethers, ignition } from &quot;hardhat&quot;;<br>import TokenModule from &quot;../ignition/modules/Token&quot;;<br><br>describe(&quot;Token contract&quot;, function () {<br>  async function deployTokenFixture() {<br>    /*<br>     Hardhat Ignition adds an `ignition` object to the Hardhat Runtime Environment<br>     that exposes a `deploy()` method. The `deploy()` method takes an Ignition<br>     module and returns the results of the Ignition module, where each<br>     returned future has been converted into an *ethers* contract instance.<br>    */<br>    const { token } = await ignition.deploy(TokenModule);<br><br>    return { token }<br>  }<br><br>  it(&quot;should assign the total supply of tokens to the owner&quot;, async function () {<br>    /*<br>     The snapshot feature of `hardhat-deploy` fixtures is replicated<br>     by the call to the `hardhat-network-helpers` function `loadFixture()`.<br>     For a given fixture function, `loadFixture()` will snapshot the in-memory<br>     Hardhat node, and will revert to the snapshot if called with the same<br>     function again.<br>    */    <br>    const { token } = await loadFixture(deployTokenFixture);<br><br>    const [, tokenOwner] = await ethers.getSigners();<br>    expect(await token.balanceOf(tokenOwner)).to.equal(await token.totalSupply());<br>  });<br>});</pre><p>Once converted, tests can be checked in the standard way:</p><pre>npx hardhat test</pre><h3>Feedback welcome</h3><p>We would love your feedback if you run into any issues or have any feature requests! Please <a href="https://github.com/NomicFoundation/hardhat-ignition/issues/new">open an issue on Github</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c17311bb658f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nomic-foundation-blog/migrating-to-hardhat-ignition-from-hardhat-deploy-c17311bb658f">Migrating to Hardhat Ignition from hardhat-deploy</a> was originally published in <a href="https://medium.com/nomic-foundation-blog">Nomic Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet the Nomic Team — Christopher Dedominici, Software Engineer on Hardhat]]></title>
            <link>https://medium.com/nomic-foundation-blog/meet-the-nomic-team-christopher-dedominici-software-engineer-on-hardhat-2be44290b03b?source=rss----2db11fd1fd8e---4</link>
            <guid isPermaLink="false">https://medium.com/p/2be44290b03b</guid>
            <category><![CDATA[team]]></category>
            <category><![CDATA[hard-hat]]></category>
            <category><![CDATA[etehreum]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Dasha Nikolov]]></dc:creator>
            <pubDate>Thu, 08 Feb 2024 18:20:23 GMT</pubDate>
            <atom:updated>2024-02-08T18:20:23.268Z</atom:updated>
            <content:encoded><![CDATA[<h3>Meet the Nomic Team — Christopher Dedominici, Software Engineer on Hardhat</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*keI3eYK5NvWUmRF1E2BTwQ.png" /></figure><p>Meet Chris — a Software Engineer on the Hardhat team and an avid ice bather!</p><h3>Where are you located? Is that where you are from originally?</h3><p>I currently live in Zurich, Switzerland, but originally, I’m Italian, from a small city near Turin. Before moving to Switzerland, I spent 4 years in Copenhagen. After 4 years in such a flat country, I decided to completely change the landscape and move to a very mountainous one.</p><h3>Who are you outside of work? What do you like to do in your spare time?</h3><p>Like many software engineers, I love coding and working on personal projects in my free time. I’m also a huge sports enthusiast: I exercise at the gym, swim, ski, and whenever possible, I try to go sailing. My passion for sailing was so strong that several years ago, I decided to get a sailing license. I still have the secret dream of sailing around the world for 6–12 months. Also, during my time in Denmark, I was introduced to ice bathing by a colleague of mine. At first, I thought he was completely crazy. But after giving it a try, I changed my mind! He was a genius! It’s one of the best feelings ever, even though it was a bit painful the first time, as you can see from the photo below (Nordic Sea on a January morning, water around 1 degree Celsius) 🙂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/756/1*jERCRCfC1LmxlWzRVDgYGA.png" /></figure><h3>What were you doing professionally before joining Nomic?</h3><p>Before joining Nomic, I worked at a large tech company. Then, I decided to make a switch to the blockchain world and the startup scene by joining a crypto bank. Moving from a big company to smaller ones was a very interesting experience. I transitioned from a very “vertical” and organized structure to a more flexible and dynamic one.</p><h3>Why did you decide to join the team?</h3><p>I’ve always used Hardhat for my personal projects in my free time, and I also used it in my previous job. So, when I got the opportunity to join a team that is so passionate about the blockchain world and maintains such high standards in the products they develop, how could I have said no?</p><h3>What’s your story behind getting into crypto/blockchain/decentralized tech?</h3><p>I’ve always been fascinated by the blockchain and crypto world, starting to delve into the field about 4–5 years ago. After a while, it became clear to me that the world was gradually shifting towards decentralization, prompting me to pursue a career in the field to deepen my experience and actively contribute to this change. Working on personal projects was no longer enough for me; I wanted to be more deeply involved.</p><h3>What did you learn about Nomic during your first weeks?</h3><p>It’s not exactly something I learned, but I have a fun story from my first days at Nomic. Several years back, while I was exploring the blockchain world, I came across <a href="https://www.youtube.com/@PatrickAlphaC">free online materials by Patrick Collins</a> (which, by the way, are amazing and highly recommended). He was using Hardhat in his videos!</p><p>I remember that shortly after joining Nomic, I was tasked with addressing a few bugs, and one of them had been reported by none other than Patrick himself! It was an amazing surprise to be fixing a bug reported by the very person who taught me how to use Hardhat!</p><h3>Which of our <a href="https://www.notion.so/Core-values-26b0474e33ef4c47b6de82d24f7937f1?pvs=21">core values</a> resonate with you the most and why? How do you see them being “used” at Nomic?</h3><p>My top three favorites, not in any particular order, are definitely these:</p><ul><li><strong>High Standards: </strong>I love the attention to detail that we put into our everyday work. I realized how high the standards were from day one.</li><li><strong>Developer Experience:</strong> I really appreciate that we care deeply about improving the developer experience as much as possible. We attentively check and read all the comments and issues opened on GitHub by people.</li><li><strong>Autonomy: </strong>I love how flexible my working hours are. I can manage my time however I want. This feeling of freedom is incredible! Especially for software engineers. Because, let’s be honest, who doesn’t love, sometimes, to code at 3 AM when everything in the city is asleep, and you have your favorite music in your headphones? That’s when great code is made!</li></ul><h3>What are you excited about when you think about your future at Nomic?</h3><p>We have a lot of exciting new products and features set to be released this year and in the years to come, which are going to have a huge impact on the ecosystem. Being part of the team that develops tools used by so many people in the blockchain world is an incredible feeling! It truly makes you feel valuable. Plus, the best part is that everything is open-sourced!</p><h3>What is your best tip for staying productive and happy when working remotely?</h3><p>This is a tricky question because I believe it varies from person to person.</p><p>To be honest, at the beginning, I was a bit apprehensive about starting a job that was 100% remote, with no physical office at all. Being Italian, I’m naturally very social and I always enjoyed going to the office to work and spend time with my colleagues. However, the sense of freedom and control over my time that comes with a 100% remote job is truly incredible!</p><p>But, as Spider-Man says, “With great power comes great responsibility” 🙂 The absence of fixed office hours could become a challenge if you’re not adept at managing your time. To mitigate this, I try to set specific working hours dedicated solely to focusing on work, without distractions.</p><p>To maintain a good social interaction level, sometimes I work a few hours in bars or cafes, though not too often since I need my two big screens. I haven’t started yet, but I’m also planning to go to a co-working space 2–3 times a week.</p><p>Do you want to join our team and help grow the ecosystem? <a href="https://jobs.ashbyhq.com/nomic.foundation">We’re hiring</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2be44290b03b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nomic-foundation-blog/meet-the-nomic-team-christopher-dedominici-software-engineer-on-hardhat-2be44290b03b">Meet the Nomic Team — Christopher Dedominici, Software Engineer on Hardhat</a> was originally published in <a href="https://medium.com/nomic-foundation-blog">Nomic Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet the Nomic Team — Luis Schaab, Software Engineer on Hardhat]]></title>
            <link>https://medium.com/nomic-foundation-blog/meet-the-nomic-team-luis-schaab-software-engineer-on-hardhat-4575ce5490e1?source=rss----2db11fd1fd8e---4</link>
            <guid isPermaLink="false">https://medium.com/p/4575ce5490e1</guid>
            <category><![CDATA[remote-work]]></category>
            <category><![CDATA[team-culture]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Dasha Nikolov]]></dc:creator>
            <pubDate>Wed, 13 Dec 2023 17:43:15 GMT</pubDate>
            <atom:updated>2024-01-30T13:51:24.465Z</atom:updated>
            <content:encoded><![CDATA[<h3>Meet the Nomic Team — Luis Schaab, Software Engineer on Hardhat</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gD9W16HeXwoAJHJipFZQYg.png" /></figure><p>Today, we’re introducing Luis — a member of the Hardhat team who played an instrumental role in the development of our latest plugin <a href="https://medium.com/nomic-foundation-blog/hardhat-viem-808a536dcfe6">Hardhat+Viem</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*F9wziDxLC6QBtOPevomk2Q.png" /></figure><h3>What is your name, and what do you do at Nomic?</h3><p>Hey there! I’m Luis and I’m part of the Hardhat team. Since joining, I’ve contributed to the hardhat-verify and hardhat-viem plugins, and more recently, I&#39;ve been involved in integrating ESM into TypeScript projects.</p><h3>Where are you located? Is that where you are from originally?</h3><p>I’m from Argentina and currently live in a small town in the Santa Fe province.</p><h3>Who are you outside of work? What do you like to do in your spare time?</h3><p>Outside of work, I’m a huge gamer — I probably spend more time playing games than I should! 😅 Apart from gaming, I really enjoy spending time outdoors and going on trips with my wife and our dog. We love planning new adventures and discovering different places together.</p><h3>What were you doing professionally before joining Nomic? Why did you decide to join the team?</h3><p>Before joining Nomic, I took a sabbatical leave. I needed a break from the usual corporate software scene and was looking for something new and exciting to dive into.</p><p>The answer to my search turned out to be Nomic. In Hardhat, I have the opportunity to work on something meaningful for the community and, at the same time, something entertaining and challenging for myself.</p><h3>What’s your story behind getting into crypto/blockchain/decentralized tech?</h3><p>I’m a bit ashamed now, but when I first heard about crypto I was pretty skeptical. That changed a couple years later, when I started receiving a part of my salary in cryptocurrency. As I began exploring and playing with crypto, I discovered the huge ecosystem around Ethereum. I was instantly hooked. The more I read, the more fascinated I became. Now, I firmly believe that blockchain and crypto will play a significant role in shaping the future of technology and, hopefully, the world.</p><h3>What are the things that you enjoy and appreciate about working at Nomic?</h3><p>Flexibility. Being able to work at any time, as long as I coordinate with my team, is super nice. Working alongside such a group of crazy smart people is really inspiring. It constantly reminds me that there’s so much to learn, and I love it.</p><h3>Which one of our <a href="https://www.notion.so/Core-values-26b0474e33ef4c47b6de82d24f7937f1?pvs=21">core values</a> resonates with you the most and why? How do you see it being “used” at Nomic?</h3><p>The core value that really speaks to me at Nomic is Kindness. I believe in treating each other with respect and truly valuing different opinions and personalities. Here, I see that every day. Our team is not just talented; they’re genuinely warm and supportive. It’s great to work in such a welcoming environment.</p><h3>What are you excited about when you think about your future at Nomic?</h3><p>There are a lot of cool things coming for Hardhat, and I love being part of it.</p><h3>What is your best tip for staying productive and happy when working remotely?</h3><p>For me, it’s about working in a peaceful environment. That, and lots of coffee and mate 🧉.</p><h3>Empowering developers to decentralize the world</h3><p>If you value a culture of high standards, autonomy, and kindness and are interested in working on impactful projects, we invite you to check out opportunities to <a href="https://jobs.ashbyhq.com/nomic.foundation">join our team</a>. Together, we can ensure that Ethereum continues to deliver a top-quality, reliable developer experience as part of its software development platform, both today and in the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4575ce5490e1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nomic-foundation-blog/meet-the-nomic-team-luis-schaab-software-engineer-on-hardhat-4575ce5490e1">Meet the Nomic Team — Luis Schaab, Software Engineer on Hardhat</a> was originally published in <a href="https://medium.com/nomic-foundation-blog">Nomic Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hardhat v2.19.0: Introducing Configuration Variables]]></title>
            <link>https://medium.com/nomic-foundation-blog/hardhat-v2-19-0-introducing-configuration-variables-b528c0c9a7c0?source=rss----2db11fd1fd8e---4</link>
            <guid isPermaLink="false">https://medium.com/p/b528c0c9a7c0</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[solidity]]></category>
            <dc:creator><![CDATA[Franco Victorio]]></dc:creator>
            <pubDate>Mon, 06 Nov 2023 17:24:04 GMT</pubDate>
            <atom:updated>2023-11-06T17:24:04.739Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6xUFx7q6MA1q12abpVi9Ow.png" /></figure><p>Handling configuration settings is a common situation in Ethereum development, and it often involves sensitive information that could cause issues if leaked. A common example are Infura API keys. Different developers may also have varying settings, which adds to the complexity of managing these configurations.</p><p>Configuration variables are a new Hardhat feature that lets you use values in a configuration file without making them part of your codebase. They work as a replacement for environment variables and <a href="https://www.npmjs.com/package/dotenv">dotenv</a>, but are more secure, flexible, and powerful.</p><p>This is how most projects handle configuration values today:</p><pre>module.exports = {<br>  networks: {<br>    sepolia: {<br>      url: `https://sepolia.infura.io/v3/${process.env.INFURA_API_KEY}`,<br>    },<br>  },<br>};</pre><p>These variables are then put in an .env file and loaded using the <a href="https://www.npmjs.com/package/dotenv">dotenv</a> package. This approach works, but it has a couple of problems:</p><ul><li>A user might accidentally push the .env file to a public repository, making all the data within it accessible to other users or to bots.</li><li>It’s not clear which of these variables need to be set before running the project and which ones are optional.</li><li>If you have multiple projects and want to share some value between them, you have to copy their .env files and keep them in sync.</li></ul><h4>Using configuration variables</h4><p>Hardhat v2.19.0 introduces a new set of tasks under the vars <a href="https://hardhat.org/hardhat-runner/docs/advanced/create-task#scoped-tasks">scope</a> to manage your configuration variables:</p><pre>$ npx hardhat vars set INFURA_API_KEY<br>✔ Enter value: ********************************</pre><p>After setting a configuration variable, you can retrieve it from any Hardhat configuration using vars.get:</p><pre>const INFURA_API_KEY = vars.get(&quot;INFURA_API_KEY&quot;);<br><br>module.exports = {<br>  networks: {<br>    sepolia: {<br>      url: `https://sepolia.infura.io/v3/${INFURA_API_KEY}`,<br>    },<br>  },<br>};</pre><p>For variables that may not exist, you can specify a default value as the second parameter:</p><pre>const salt = vars.get(&quot;DEPLOY_SALT&quot;, &quot;12345&quot;);</pre><p>You can also use vars.has to check if a variable exists:</p><pre>const accounts = vars.has(&quot;TEST_PK&quot;) ? [vars.get(&quot;TEST_PK&quot;)] : [];</pre><h4>Migrating from dotenv</h4><p>If you are using <a href="https://www.npmjs.com/package/dotenv">dotenv</a>, we recommend migrating to our built-in configuration variables manager. This will make it easier to share values across various Hardhat projects, and will minimize the risk of exposing sensitive data by accidentally uploading a .env file to a public repository.</p><p>To migrate from dotenv, follow these steps:</p><ol><li>Replace process.env.KEY references in your configuration with vars.get(&quot;KEY&quot;). Replace conditions like process.env.KEY !== undefined with vars.has(&quot;KEY&quot;)</li><li>Run <a href="https://hardhat.org/hardhat-runner/docs/guides/configuration-variables#setting-up-variables-for-a-project">npx hardhat vars setup</a> to identify all the variables that are used by your project.</li><li>Use npx hardhat vars set for each variable as indicated by the setup task.</li><li>After substituting all instances of process.env, you may uninstall the dotenv package and remove its import from your configuration.</li></ol><h4>Under the hood</h4><p>Configuration variables are stored in plain text on your disk. Avoid using this feature for data you wouldn’t normally save in an unencrypted file. You can run npx hardhat vars path to get the path to the storage file.</p><h4>Give it a try</h4><p>Upgrade to Hardhat v2.19.0 and check our <a href="https://hardhat.org/hardhat-runner/docs/guides/configuration-variables">Configuration variables guide</a> to learn more. And don’t forget to <a href="https://github.com/NomicFoundation/hardhat">star Hardhat on GitHub</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b528c0c9a7c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nomic-foundation-blog/hardhat-v2-19-0-introducing-configuration-variables-b528c0c9a7c0">Hardhat v2.19.0: Introducing Configuration Variables</a> was originally published in <a href="https://medium.com/nomic-foundation-blog">Nomic Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to automate a headache-free deployment with Hardhat Ignition]]></title>
            <link>https://medium.com/nomic-foundation-blog/how-to-automate-a-headache-free-deployment-with-hardhat-ignition-fb2936ae2cfb?source=rss----2db11fd1fd8e---4</link>
            <guid isPermaLink="false">https://medium.com/p/fb2936ae2cfb</guid>
            <category><![CDATA[solidity]]></category>
            <category><![CDATA[hard-hat]]></category>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[John Kane]]></dc:creator>
            <pubDate>Thu, 02 Nov 2023 13:48:42 GMT</pubDate>
            <atom:updated>2023-11-02T13:48:41.988Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*67HqY5gLXbY9eETqWa-uKw.png" /></figure><p><a href="https://hardhat.org/ignition/docs/getting-started#overview">Hardhat Ignition</a> is a declarative system for deploying smart contracts on Ethereum. It enables you to define smart contract instances you want to deploy, and any operation you want to run on them. By taking over the deployment and execution, Hardhat Ignition lets you focus on your project instead of getting caught up in the deployment execution details. It’s a better end-to-end deployment experience. To learn more, check out our <a href="https://medium.com/nomic-foundation-blog/introducing-hardhat-ignition-a-refreshed-deployments-experience-9580d2946e10">announcement post</a>.</p><p>Let’s get started and look into how you can automate a simple deployment using Hardhat Ignition.</p><h3>Installation</h3><p>We’re going to quickly install Hardhat, set up a new project, and install Hardhat Ignition. Skip to the next section if you know how to do this already!</p><p>Open a terminal and execute the following commands to set up an NPM project with Hardhat:</p><pre>mkdir hardhat-ignition-tutorial/<br>cd hardhat-ignition-tutorial<br>npm init<br>npm install --save-dev hardhat</pre><p>Then run npx hardhat init, select “Create a TypeScript project” and “yes” in the following steps. Our Hardhat project is now ready, and we’re going to install Hardhat Ignition next. Run:</p><pre>npm install --save-dev @nomicfoundation/hardhat-ignition</pre><p>Finally, open the hardhat.config.ts file and add this line at the top to enable the plugin:</p><pre>import &quot;@nomicfoundation/hardhat-ignition&quot;;</pre><h3>Creating your contract</h3><p>Paste the following code into contracts/Rocket.sol:</p><pre>// SPDX-License-Identifier: UNLICENSED<br>pragma solidity ^0.8.0;<br><br>contract Rocket {<br>    string public name;<br>    string public status;<br><br>    constructor(string memory _name) {<br>        name = _name;<br>        status = &quot;ignition&quot;;<br>    }<br><br>    function launch() public {<br>        status = &quot;lift-off&quot;;<br>    }<br>}</pre><p>It contains a simple smart contract called Rocket, featuring a launch function that we&#39;ll call after deployment.</p><h3>Creating your first module</h3><p>In Hardhat Ignition, deployments are expressed through Ignition Modules. These modules are defined in JavaScript/Typescript and let you outline and describe the system that you want to deploy.</p><p>Modules are declared in JavaScript or Typescript files inside of ignition/modules. Let&#39;s create that folder structure:</p><pre>mkdir ignition<br>mkdir ignition/modules</pre><p>And paste the following code into a ignition/modules/Apollo.ts. We&#39;ll explain it in a moment.</p><pre>import { buildModule } from &quot;@nomicfoundation/hardhat-ignition/modules&quot;;<br><br>export default buildModule(&quot;Apollo&quot;, (m) =&gt; {<br>  const apollo = m.contract(&quot;Rocket&quot;, [&quot;Saturn V&quot;]);<br><br>  m.call(apollo, &quot;launch&quot;, []);<br><br>  return { apollo };<br>});</pre><p>The first aspect to note is that modules are created by calling the buildModule function, which requires a module ID and a callback function. Our module will be identified as &quot;Apollo&quot;.</p><p>The callback function is where the module definition actually happens. The m parameter being passed into the callback is an instance of a ModuleBuilder, which is an object with methods to define and configure your smart contract instances.</p><p>When we call these ModuleBuilder methods, they create a Future object, which represents the result of an execution step that Hardhat Ignition needs to run to deploy a contract instance or interact with an existing one.</p><p>This doesn&#39;t execute anything against the network, it simply represents it internally. After the Future is created, it gets registered within the module, and the method returns it.</p><p>In our module, we created two Future objects by calling the contract and call methods. The initial one instructs Hardhat Ignition to deploy a Rocket contract instance, specifying &quot;Saturn V&quot; as the only constructor parameter. The second one indicates that we intend to execute the launch function of the deployed Rocket instance, with no arguments provided.</p><p>Finally, we return the Future object representing the Rocket contract instance, to make it accessible to other modules and tests as well.</p><h3>Deploying it</h3><p>Now that our module definition is ready, let&#39;s deploy it to a local Hardhat node. Let&#39;s start by spinning up a local node:</p><pre>npx hardhat node</pre><p>Next, in a separate terminal in the root of your Hardhat project, run:</p><pre>npx hardhat ignition deploy ignition/modules/Apollo.ts --network localhost</pre><p>Hardhat Ignition will execute every Future that we defined in the right order, and display the results:</p><pre>Hardhat Ignition 🚀<br><br>Deploying [ Apollo ]<br><br>Batch #1<br>  Executed Apollo#Rocket<br><br>Batch #2<br>  Executed Apollo#Rocket.launch<br><br>[ Apollo ] successfully deployed 🚀<br><br>Deployed Addresses<br><br>Apollo#Rocket - 0x5fbdb2315678afecb367f032d93f642f64180aa3</pre><p>An ignition/deployments/chain-31337 folder will have been created. It contains all the details about your deployment. Hardhat Ignition uses this data to recover from errors, resume a modified deployment, and more.</p><p>That&#39;s all it takes to define and execute a deployment using Hardhat Ignition!</p><h3>Check it out</h3><p>For an in-depth guide on everything you can express with modules, see <a href="https://hardhat.org/ignition/docs/guides/creating-modules">Creating Ignition Modules</a> on our documentation site. We designed this tool for sophisticated users, which means there’s a lot more that is possible.</p><p>We’d love to hear your feedback, so give it a try! Here are some useful links:</p><ul><li><a href="https://hardhat.org/ignition">Documentation site</a></li><li><a href="https://hardhat.org/ignition/docs/getting-started#overview">Conceptual overview</a></li><li><a href="https://github.com/nomicfoundation/hardhat-ignition">Github repo</a></li><li><a href="https://github.com/NomicFoundation/hardhat-ignition/tree/development/examples">Module examples</a></li></ul><p>If you like Hardhat Ignition, please star the repo on Github, and <a href="https://twitter.com/intent/tweet?text=Trying+out+%40HardhatHQ+Ignition%2C+%40NomicFoundation%27s+new+deployment+tool%21+%F0%9F%9A%80%0A%0Ahardhat.org%2Fignition">let us know</a> what you think!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb2936ae2cfb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nomic-foundation-blog/how-to-automate-a-headache-free-deployment-with-hardhat-ignition-fb2936ae2cfb">How to automate a headache-free deployment with Hardhat Ignition</a> was originally published in <a href="https://medium.com/nomic-foundation-blog">Nomic Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet the Nomic Team — Zoey Morgan, Software Engineer on Ignition]]></title>
            <link>https://medium.com/nomic-foundation-blog/meet-the-nomic-team-zoey-morgan-software-engineer-on-ignition-4586b61b6a90?source=rss----2db11fd1fd8e---4</link>
            <guid isPermaLink="false">https://medium.com/p/4586b61b6a90</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Dasha Nikolov]]></dc:creator>
            <pubDate>Wed, 01 Nov 2023 12:03:54 GMT</pubDate>
            <atom:updated>2023-11-01T12:04:23.591Z</atom:updated>
            <content:encoded><![CDATA[<h3>Meet the Nomic Team — Zoey Morgan, Software Engineer on Hardhat Ignition</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1C_Y5kOWZ-H7iwvJHcDHFQ.png" /></figure><p>In light of <a href="https://medium.com/nomic-foundation-blog/introducing-hardhat-ignition-a-refreshed-deployments-experience-9580d2946e10">Hardhat Ignition’s recent launch</a>, we’d like to introduce you to Zoey, one of the engineers instrumental in bringing this project to life!</p><h4>What is your name, and what do you do at Nomic?</h4><p>Hi! My name is Zoey, and I’m a software engineer at Nomic working on our Hardhat Ignition project!</p><h4>Where are you located? Is that where you are from originally?</h4><p>I was born in the US, but currently I live in Ontario, Canada.</p><h4>Who are you outside of work? What do you like to do in your spare time?</h4><p>Outside of work I’m kind of a huge nerd (well, inside of work too I suppose 😅). I’m really into some videogame speedrunning communities, and I also love watching anime and reading manga!</p><h4>What were you doing professionally before joining Nomic?</h4><p>Before Nomic, I was working for a big corporation doing mostly backend web dev stuff, but I quickly realized that I vastly preferred working for smaller, startup-sized teams. At some point I left the corp job and decided to spend my time hunting for someplace I was really going to enjoy working for again. (hint: it was Nomic!)</p><h4>Why did you decide to join the team?</h4><p>Having worked at a crypto startup before, I knew that’s what I wanted to look for when I started my job search; normal web dev just wasn’t as interesting anymore 😜. Working with Ethereum and smart contracts was super fun, but I just wasn’t finding a project that was clicking for me. Eventually, I got lucky enough to stumble across Nomic, and I knew immediately that this was the only place I wanted to work.</p><p>Rather than working on a single product, their vision was about empowering devs and supporting the Ethereum ecosystem as a whole. The team was (and is) very close-knit and eager to grow together, which is all exactly what I was looking for.</p><h4>What’s your story behind getting into crypto/blockchain/decentralized tech?</h4><p>While I was learning web development, one of my friends introduced me to Ethereum and tried explaining the concept of smart contracts to me. I didn’t understand it at all 😂 but it was exciting and interesting! I went down the rabbit hole and learned everything I could about it; I was totally fascinated. Eventually I landed a job as a smart contract engineer at a growing startup, and the rest is history!</p><h4>What are the things that you enjoy and appreciate about working at Nomic?</h4><p>There’s so many!! My favorite would be that the team is as welcoming as it is diverse, so whether it’s technical or cultural, I feel like I’m learning new things constantly which is really amazing.</p><h4>Which one of our <a href="https://www.notion.so/Core-values-26b0474e33ef4c47b6de82d24f7937f1?pvs=21">core values</a> resonates with you the most and why? How do you see it being “used” at Nomic?</h4><p>For me, I think Kindness resonates the most. The tech industry in general doesn’t have the best reputation when it comes to its treatment of women in the industry, but in the (nearly) two years I’ve worked at Nomic, that has never been an issue. I mentioned earlier how diverse and inclusive the team is, and that truly shows here. I feel safe and supported by my colleagues, and for me, there’s no greater source of motivation.</p><h4>What are you excited about when you think about your future at Nomic?</h4><p>IGNITION!!! 🚀</p><p>Okay, yes, I’m biased, but watching this project launch after all the work we’ve put into it is extremely exciting. I can’t wait to see how it grows in the years to come!</p><p>Aside from that, I’m just excited for Nomic to grow as a whole! The size of the team has nearly tripled since I joined, and it’s been such a joy getting to know every new face.</p><h4>What is your best tip for staying productive and happy when working remotely?</h4><p>Oh gosh, I think the best tip I could give is just to find what works for you, and don’t be afraid to change something up if it’s not working. Whether it’s working from a cafe, setting up a dedicated “office” space in your home, or trying a different work schedule (as much as possible), the best part of working remotely is the flexibility, so work with it! Try different things and find/create the environment that enables you to succeed and feel good while doing it!</p><h4><strong>Empowering developers to decentralize the world</strong></h4><p>If you value a culture of high standards, autonomy, and kindness and are interested in working on impactful projects, we invite you to check out opportunities to <a href="https://jobs.ashbyhq.com/nomic.foundation">join our team</a>. Together, we can ensure that Ethereum continues to deliver a top-quality, reliable developer experience as part of its software development platform, both today and in the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4586b61b6a90" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nomic-foundation-blog/meet-the-nomic-team-zoey-morgan-software-engineer-on-ignition-4586b61b6a90">Meet the Nomic Team — Zoey Morgan, Software Engineer on Ignition</a> was originally published in <a href="https://medium.com/nomic-foundation-blog">Nomic Foundation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>