<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mike Godsey on Medium]]></title>
        <description><![CDATA[Stories by Mike Godsey on Medium]]></description>
        <link>https://medium.com/@godsey?source=rss-49eacd289ec1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*92FdR9dLxSj-aPpJG7b41Q.png</url>
            <title>Stories by Mike Godsey on Medium</title>
            <link>https://medium.com/@godsey?source=rss-49eacd289ec1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 09:03:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@godsey/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Today we are launching Infura Plus]]></title>
            <link>https://medium.com/@godsey/today-we-are-launching-infura-plus-c19114c1849d?source=rss-49eacd289ec1------2</link>
            <guid isPermaLink="false">https://medium.com/p/c19114c1849d</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[launch]]></category>
            <category><![CDATA[infura]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Mike Godsey]]></dc:creator>
            <pubDate>Wed, 17 Jul 2019 21:39:35 GMT</pubDate>
            <atom:updated>2019-07-17T21:41:04.417Z</atom:updated>
            <content:encoded><![CDATA[<h3>Today we are launching Infura+</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tALUh9UyeuZgGxNj0qHbuA.png" /></figure><p>In the first few years of Ethereum and IPFS, Infura has earned the trust of the Web3 community with our easy-to-use, dependable infrastructure service. Now, in order to provide even better stability and enhanced features, we are creating some more diverse product offerings to improve the developer experience. We’re excited to announce the release of our premium Ethereum API subscription service, Infura+.</p><p>Infura+ includes 3 new subscription tiers supporting blockchain developers building applications of all sizes on the Ethereum network. Developers can choose the infrastructure services that fit their needs with custom plans available from day one. Here are the 3 Infura+ tiers:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1VvlmHRpYQ4Z5jym5ZuwLg.png" /></figure><h3>About Infura+ Ethereum API Subscription Options</h3><p>All Infura tiers provide access to Ethereum mainnet and the Rinkeby, Ropsten, Kovan, and Goerli test-nets. Infura+ tiers provide increased daily request volume and support features tailored for larger, production-ready applications. All users will be able to configure their accounts with custom add-ons. At launch, developers will be able to select the Ethereum Archive Data add-on for their account.</p><p>Everyone can now sign up to Infura+ directly in the <a href="https://infura.io/login">Infura Dashboard</a> and start taking advantage of the benefits of our premium service. We are also excited to announce that for accounts created before today’s launch, <strong>we are offering a 3 month free trial for all subscription configurations</strong>. For a limited time, new users will also receive 3 months of free service!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3jLK6Ye_q0qde0_pXZuIMg.png" /></figure><p>Here are some of the basics of Infura+ so you can learn about the new service and which subscription level works best for your app.</p><h4>Q: Will I still be able to access Infura for free?</h4><p>A: Yes, the free tier, now known as the <strong>Core</strong> tier, is specifically for on-ramping developers to Ethereum. We are committed to providing the easiest way to start building Ethereum applications. Now, Infura+ can help growing applications scale by letting them upgrade their account when their application needs it.</p><h4>Q: How do I sign up for my 3 months free of Infura+?</h4><p>A: It’s easy to upgrade your account and take advantage of your free trial. Start by logging into the Infura Dashboard at <a href="https://infura.io/login">https://infura.io/login</a>. Then you will see a link to upgrade your account.</p><h4>Q: Why do I have to enter my payment information for the 3 month free trial?</h4><p>A: Since Infura+ is a subscription, we do not want to interrupt your service to complete the account activation process after your trial period ends. Configuring payment now means that your account will be ready to go when the fourth month starts. (You can opt out at any time during your trial.)</p><p>We are adding more payment options in our next release. If there is one you’d really like to see, <a href="/service/mailto:hello@infura.io">let us know</a>.</p><h4>Q: Do I have to use Dashboard-generated Project IDs to use Infura+?</h4><p>A: Dashboard-generated Project IDs are required to use the features of Infura+. As a reminder, Project IDs lets you keep track of and control access to your account. We recommend upgrading all projects using Infura to the latest API authentication, if you haven’t already. Unauthenticated requests and requests using old versions of authentication are unsupported.</p><h4>Q: What happens if I don’t upgrade to Infura+?</h4><p>A: Infura+ is not mandatory for any developers on Infura! We are maintaining the free access you know and love on the <strong>Core</strong> tier. Infura+ is for applications that require increased request volume, features such as Ethereum Archive Data, and advanced support directly from the Infura team.</p><p>The Archive Data add-on is required for access to Ethereum archive data. Infura+ users will also have an increased rate limit over free users. For more information on rate limits, visit <a href="https://infura.io/docs/ethereum/json-rpc/ratelimits">https://infura.io/docs/ethereum/json-rpc/ratelimits</a>.</p><h4>Q: Do you support custom plans with SLAs or other features?</h4><p>A: Yes, if you are interested in a customized plan for your business or use case, we support configurable plans with options for increased request volume, SLAs, higher levels of support, and more. <a href="/service/mailto:inquiry@infura.io">Reach out to us</a> and a member of our team will work with you to create a custom solution.</p><p>Thank you again to all the Infura users who helped test our service and provided feedback. With your help — and the billions of requests we’ve served and learned from — we have built Infura to be the most reliable, scalable, and easy-to-use Ethereum infrastructure available. Infura+ is the next step in the evolution of a better distributed web.</p><p>If you have more questions or want more specifics on the new options Infura+ is offering, please feel free to ask questions in our <a href="https://community.infura.io/">community</a> or reach out to our <a href="/service/mailto:hello@infura.io">team directly</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c19114c1849d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Infura June 2019 Update]]></title>
            <link>https://medium.com/@godsey/infura-june-2019-update-9528c388a3b4?source=rss-49eacd289ec1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9528c388a3b4</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[ipfs]]></category>
            <category><![CDATA[infura]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Mike Godsey]]></dc:creator>
            <pubDate>Wed, 26 Jun 2019 22:19:29 GMT</pubDate>
            <atom:updated>2019-06-27T00:40:34.499Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oq6q98Gs-lhwn5TQsU_YBg.png" /></figure><p>Thanks for joining for a quick update on our our development progress at Infura. Here are some of the latest releases and improvements that are now available for our Ethereum and IPFS APIs.</p><h3>Websocket API improvements for logs subscriptions</h3><p>In March, we announced an update to the Websocket newHeads subscription here, <a href="https://blog.infura.io/websocket-api-upgrade-now-live-e3406cc70d14">https://blog.infura.io/websocket-api-upgrade-now-live-e3406cc70d14</a>. This month, we have released the same improvements to the ‘logs’ subscription type.</p><p>Developers using the Websocket logs subscription will now have 100% consistent data responses, no timeout issues, and full support for reorged blocks. If you haven’t started using our Websocket subscriptions, check out the docs here, <a href="https://infura.io/docs/ethereum/wss/eth_subscribe">https://infura.io/docs/ethereum/wss/eth_subscribe</a>.</p><p>In addition, improvements in our implementation have brought new efficiencies in handling logs overall, so we’re happy to announce we’ve raised the limit on eth_getLogs results to 10,000 logs and events per request.</p><h3>Open source project, go-ethlibs, is live!</h3><p>We are building out our internal open source culture and are excited to release the go-ethlibs project, available here, <a href="https://github.com/infura/go-ethlibs">https://github.com/infura/go-ethlibs</a>. Go-ethlibs is a sandbox repository of various in-progress helpers that we use within our infrastructure and will continue to work on in the open. The following are available today in the repo:</p><ul><li>eth: Helpers for serializing/deserializing Ethereum JSONRPC types</li><li>jsonrpc: JSONRPC request and response parsing</li><li>node: A proto-ethclient in the node namespace</li><li>rlp: Independent implementation of RLP parsing</li></ul><p>Some of this work is “clean-room” rewrites of pieces inside of go-ethereum utilizing a more permissive license (MIT) which will hopefully help other companies and developers to not have to duplicate this effort. We are looking forward to seeing creative applications of these libraries.</p><h3>Other updates</h3><p>We are continuing to make major updates and improvements to our IPFS endpoint. We have solved issues some users were reporting with regards to 502 and 504 errors. We are also working actively with the Protocol Labs team to improve the go-ipfs client and overall IPFS functionality, which will allow us to provide a better service and increase the usability of the client for all operators. More updates coming soon.</p><p>The feedback and questions posted to our community site at <a href="https://community.infura.io/">https://community.infura.io/</a> have been incredibly valuable in helping us find areas for improvement, thank you to everyone reporting issues and asking questions. We are working every day to help grow that community and make it a go-to place for Web3 developers to find helpful information. Stop by anytime to ask questions, help other developers, or just to check out the activity.</p><p>Thanks for reading and stay tuned, we have a big release coming and will be announcing that shortly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9528c388a3b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Websocket API Upgrade Now Live]]></title>
            <link>https://medium.com/@godsey/websocket-api-upgrade-now-live-e3406cc70d14?source=rss-49eacd289ec1------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3406cc70d14</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[updates]]></category>
            <category><![CDATA[infura]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[websocket]]></category>
            <dc:creator><![CDATA[Mike Godsey]]></dc:creator>
            <pubDate>Mon, 25 Mar 2019 17:52:45 GMT</pubDate>
            <atom:updated>2019-04-12T12:56:18.451Z</atom:updated>
            <content:encoded><![CDATA[<p>In an ongoing effort to improve our Websocket API, we released a new upgrade to the ‘new-heads’ subscription type. We often receive questions from our users about Websocket subscription functionality, such as issues around keeping connections open, and consistency of responses. This update is specifically targeted at answering these questions and establishing the Infura Ethereum Websocket API as the most reliable way to utilize this interface for accessing Ethereum data.</p><p>Here are more specifics on the improvements to new-heads subscriptions,</p><ul><li>Fixes the 1 hour idle timeout that some users have reported with the Websocket endpoint.</li><li>New-heads subscriptions will now provide data on reorged blocks which is not supported by Ethereum clients. This means that in the case of a chain reorganization, users will receive the new block headers for the updated chain.</li><li>100% consistent responses, no matter how many requests or the time of day, your response will always be consistent with previous or future responses.</li></ul><p>The Websockets feature is still in Beta within the Ethereum clients. Infura is committed to supporting it for all our developers who need or use it. We will continue to release more improvements to Websockets and the Infura APIs, so stay tuned. Your feedback about Websockets has been incredibly valuable in enhancing the Infura service, please keep it coming!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*XqXyqiV2sE4HzKXzPtFROA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3406cc70d14" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[API Security section now available in the Infura Dashboard]]></title>
            <link>https://medium.com/@godsey/api-security-section-now-available-in-the-infura-dashboard-9f8cfae64044?source=rss-49eacd289ec1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f8cfae64044</guid>
            <category><![CDATA[infura]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[dashboard]]></category>
            <dc:creator><![CDATA[Mike Godsey]]></dc:creator>
            <pubDate>Tue, 19 Mar 2019 17:53:34 GMT</pubDate>
            <atom:updated>2019-03-19T18:23:39.307Z</atom:updated>
            <content:encoded><![CDATA[<h3>API Security Section Now Available in the Infura Dashboard</h3><p>This week we released a major update to the Infura Dashboard that gives developers the ability to specify additional information about their API requests in order to further secure the usage of their Infura APIs.</p><p>We will soon be enabling premium services and they will all require properly authenticated requests to utilize. With these premium services we will be introducing per user limitations to request traffic. This will allow us to continue to provide our service at the high reliability and availability that our users demand. To ensure that your project’s API traffic is accurately associated with your account, we are releasing these new features to help you secure your Project ID and Project Secret.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vxseLHxA6nZdbUqnUp7Png.png" /></figure><p>For each project ID in a developer’s dashboard, they can now control the following options:</p><ul><li><strong>Private Secret Required</strong>: Enabling this option will set this project to only serve requests where both the Project ID and Project Secret are included in the request. We have updated our <a href="https://infura.io/docs/gettingStarted/authentication">documentation</a> to outline how to properly send your requests with a Project Secret. We will be releasing more information shortly about the importance of Project Secrets and how they should be used with requests.</li><li><strong>Whitelist Addresses</strong>: You can add specific Ethereum addresses that your application uses, either smart contracts or wallets. For methods that explicitly refer to address parameters, this will restrict requests using those methods to only allow requests referencing addresses identified in your whitelist.</li><li><strong>Whitelist User Agents</strong>: User Agent is commonly utilized in the request header by browsers and mobile apps to identify the software or app making the requests. Configuring entries here will only allow requests to the whitelisted user agents. We do case sensitive partial matching to check these entries.</li><li><strong>Whitelist Origins</strong>: Modern browsers sending HTTP requests will generate the Origin header on all POST requests as the URL of the page that created the request with path information removed. Setting the origin on your project ID will only allow requests to the whitelisted entries. We support wildcards as part of the prefix when checking these entries, e.g. <em>*.infura.io</em></li></ul><p>Here are some high level functionality notes important to keep in mind when configuring these whitelists:</p><ul><li>If no entries are added to any of the whitelists, all requests will be served using that project ID. Otherwise, if entries are added to any of the whitelists, <strong>only </strong>requests containing the whitelisted entries will be served.</li><li>If you apply multiple whitelist entries to a single project ID, entries of the same type are boolean ORed together and each whitelist type is then boolean ANDed with the others.</li></ul><p>For example, if you have the following whitelist entries applied to your project ID;</p><ul><li>Addresses:0x1234, 0xBEEF</li><li>User Agents:my-awesome-app.com/123</li></ul><p>Then the effective filter logic would be,</p><ul><li>IF( Address=(&quot;0x1234&quot; OR &quot;0xBEEF&quot;) AND UserAgent.contains(&quot;my-awesome-app.com/123&quot;) THEN ALLOW</li></ul><p>Please see the docs for even more information on how to use these new options, <a href="https://infura.io/docs/gettingStarted/authentication">Infura Documentation</a>.</p><p>As part of our transition to dashboard generated project IDs for sending API requests we wanted to include industry best practices for managing API requests. You can start taking advantage of these new security features now.</p><p>For the latest timing on the transition, please see the following post, <a href="https://blog.infura.io/infura-dashboard-transition-update-c670945a922a">Dashboard Transition Update</a></p><p>As always, we are here to help with any new features and your transition to dashboard generated project IDs. If you have any questions please reach out to us at our <a href="https://community.infura.io/">Community</a> page or by email at <a href="/service/mailto:support@infura.io">support@infura.io</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f8cfae64044" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>