Infura product tips and Web3 tutorials for developers building decentralized applications.

Infura Developer Tutorials

Tutorials

Getting Started With Infura

Comparing NFT Standards - ERC-721 vs ERC-721a vs ERC-1155

Wanna be in the same league as Damien Hirst, DC, and Niftys? Then build your NFT on the Palm network!

Infura and Palm NFT Studio are excited to announce that the Palm network is now available to all users of Infura. Nearly 430,000 developers now have access to create NFTs on the Palm network.

The Palm NFT Studio

The Palm network is an Ethereum sidechain dedicated to selling, purchasing, and trading NFTs that are associated with real-world and digital assets. Palm provides low gas costs and fast transaction finality. The network is over 99% more energy efficient than Proof of Work-based blockchain networks, providing artists with a more sustainable solution today, while Ethereum upgrades to Proof of Stake in the Merge, tentatively scheduled for release in July 2022.

The Palm NFT Studio has collaborated with Damien Hirst, DC, Niftys and Warner Brothers and other artists in minting NFTs on the Palm network.

How to mint an NFT on Palm

For users looking to mint NFT projects, the Palm network provides an effective solution to create NFTs that are able to be bridged back to Ethereum.

To access the Palm mainnet or testnet endpoints, here’s how to get started:

1. Login to your Infura account and select an existing Ethereum project (or create a new Ethereum project if you have not yet).

2. Click on the settings of the project to view the Palm API endpoints.

Using Palm mainet and testnet is free as part of all Infura plans, and requests sent to the API count as part of your existing plan. No action is required to activate Palm, and the availability of Palm testnet allows you to have an environment to begin developing and testing your NFT project before going live.

See our documentation on Palm for more information, as well as links to helpful tutorials.

Get in touch and start building

Interested in creating your own NFTs, but do not know where to start?

Learn more from Infura’s Director of Engineering, Kris Shinn, on minting NFTs using Infura and Replit, based on his EthDenver 2022 presentation.

Let us know how you are using NFTs in our Discord and feel free to ask questions in our community.

Just getting started with Infura? Our docs will get you building.

Ethereum Network Updates, Upgrades, Hard Forks

Infura - Ethereum Network Updates

Network

The Palm network is now available for all NFT creators on Infura

Last July, we published Ethereum JavaScript Libraries: web3.js vs. ethers.js (Part I) to provide “a comparison of web3.js and ethers.js, focusing on their similarities and differences, so that you can better understand the nuances of the libraries.”

To recap, we dove into the documentation of both libraries. We then used a modified version of a software evaluation framework Andres Canal established in his article “Using Quill,js to Build a WYSIWYG Editor for your Website” to guide the reader toward making the best decision in choosing which library to use.

The article was “written with the intent of educating developers to understand the tradeoffs between the two libraries to be able to make a decision of which library to use for their particular use case.”

How have the conclusions from that article changed over the course of the past year?

Table 1: Comparison of Conclusions about Web3.js and Ethers.js




July 2020
October 2021




Web3.js has a community of users and maintainers associated with the Ethereum Foundation. Web3.js has a good API reference and has been around since 2015. Many projects are using it and the library has been the go-to in many "Build Your First dApp" tutorials.
Web3.js is best for those who prefer the most-used Ethereum javascript library that is also maintained by a blockchain-focused firm. Web3.js's strengths are its tests and community. Documentation is currently modest in design and scope and can definitely be improved.


Ethers.js is excellent because it is a small, compact library with a large number of test cases. It has good “Getting Started” documentation, making it accessible to new users. Developers find ethers.js simple and intuitive and the library has gained in popularity over the past two years, seeing increased downloads and usage by projects.
Ethers.js is best for those who prefer lightweight, user-friendly libraries with robust testing and documentation. Ethers.js’s strengths are its documentation, tests and community. It could have more maintainers in order to create some redundancy in the development team - currently a single individual.







Let’s dive into the updated data and explain why these conclusions have changed.


1) How important is the popularity of the library?

To use Andres Canal’s definition,

“A popular project on Github means exactly what you expect it to. Namely, that there are lots of people questioning, contributing, and supporting it. This activity tends to result in more reliable software. You can check the popularity of any project by looking at how many stars it has, how many issues are opened, how many pull requests are pending, and how many contributors worked on the project.”

Web3.js has about 11,600 stars and ethers.js 3,100 as of Oct. 14, 2021. Web3.js is used by 112,849 repositories, compared with 65,519 for ethers.js.

Looking back to July 2020, Web3.js had nearly 8,800 stars while ethers.js had nearly 1,500. Web3.js was used by 51,300 repositories on GitHub, compared with 18,500 for ethers.js.

Web3.js remains the more popular library, but impressively for both libraries, their dependencies have at least doubled over this time period. Web3.js remains more popular, but the overall pie of dependent projects has grown from about 69,800 to 178,368. We will dive more into the dependencies in question 3.


2) How important is the maintenance of the library?

To quote ourselves from the last article,

“We want to use libraries that are updated frequently, so that bugs are squashed and new features are added. Though it is not perfect, looking at a month (or two) of commits, closed issues, active issues, and the number of maintainers over that time period can give a sense of the strengths and weaknesses of an open source project. This also reveals patterns of maintenance, giving some insight to the user of a library when updates and bug fixes are generally addressed, which can be used as a proxy metric for maintenance of the library.”

Using the same metrics from our last article, we see the following for both libraries.

Table 2: GitHub Monthly Pulse for Sept. 14, 2021 to Oct. 14, 2021




Library
Commits to Main Branch
Closed Issues
Active Issues
Maintainers




web3.js
20
60
107
10


ethers.js
2
17
39
1






GitHub Pulse now reveals some additional useful information about the libraries, which gives us even more context of why we are seeing what we are seeing.

For web3.js, we can see that a single individual is responsible for the majority of the commits, though there are three individuals that have 10 or more commits. This is something I see as a plus. This means there is redundancy built into the development team, in case someone were to stop contributing to the project. Web3.js has 121 commits to branches other than the main branch, as web3.js is transitioning off of the 1.x version as outlined in this blogpost the roadmap for web3.js (which we will reference again in the next section). This indicates a lot of work is going into the future releases.

For ethers.js, Richard Moore continues to be the sole maintainer of the library, but there are many more people contributing to the project by opening and closing issues on the GitHub repository, indicating that there is a community of individuals committed to the health of the library. By virtue of a single maintainer, it is not surprising to see fewer overall commits.


3) Who is responsible for the development of the library and how many projects use it?

ChainSafe is the lead maintainer of the web3.js library, having received a grant from the Ethereum Foundation to “continue the maintenance and further development” of web3.js in September 2020. ChainSafe’s outline of the future plans for web3.js reveals major changes coming, such as the deprecation of web3-bzz and web3-shh packages in version 3.x and an eventual move to Typescript in version 4.x. These are exciting additions, but the tradeoff is that ChainSafe will need time to realize these while maintaining the existing library.

Ethers is the lead maintainer of the ethers.js library, which is Richard Moore’s project, so we can think of Richard Moore = Ethers. Ethers has been the lead maintainer of the project since the inception of it. This can be a risk for some projects, but in this case, it has made ethers.js very quick in adding features and capabilities. For example, ethers.js is fully TypeScript-ready with “definition files and full TypeScript source” according to the documentation.


Table 3: Dependent Repository and Package Counts, October 15, 2021




Library
Dependent Repositories
Dependent Packages




web3.js
113,018
4,685


ethers.js
66,950
3,505







Web3.js, likely due to the longer existence of the project, has more repositories and packages that are dependent upon it. When compared with metrics from our last article, ethers.js is closing the gap with web3.js when it comes to dependent packages.


4) How important is it that the library has tests?

Answer: Very important to any dApp developer worth their salt. Luckily for us, both libraries have gotten even better since our last article.

Ethers.js has a test suite API documented for the current v5 release on their GitHub repository. The documentation of the testing is very impressive. Check it out.

Web3.js has added test documentation since our last article. This documentation, based on my personal inspection, appears robust and clearly written.

I believe ethers.js has the lead, but web3.js has done a great job catching up in terms of its tests and their documentation, and I feel both have great coverage when it comes to tests. Tests are a strength for both libraries now.


5) How important is the number of downloads of the library?

As of Oct. 15, 2021, web3.js has 30,767,910 downloads and ethers.js has 24,284,490 downloads. Compare that with May 20, 2020, when we first looked at this statistic, when web3.js had 14,703,432 downloads and ethers.js had 8,500,336 downloads. The overall pie has grown, but the difference in downloads is surprisingly close: a difference in total downloads of 6,484,420 on Oct. 15, 2021 compared with a difference of 6,203,096 in late May of 2020.

When we look at weekly downloads, the two libraries are practically even: web3.js at 330,102 and ethers.js at 339,318. Weekly downloads of both libraries have nearly doubled since we last checked this statistic (May 20, 2020, for those following along): web3.js at 175,661 and ethers.js at 184,798.


6) How important is web performance?

Web performance is indirectly measured by comparing the size of the libraries, as we are assuming smaller libraries take less time to load in the browser.

Both libraries are small. Web3.js has decreased the size of the library to 7.28 MB unpacked (unpacked refers to the size of the library when published) from 10.6 MB when we last checked. Ethers.js touts its very small size, which has increased to 322 kb uncompressed from 284 kb uncompressed over the same time period. It’s unclear what occupies 322 kb within ethers.js. NPM shows ethers.js 10.2 MB unpacked, and I confirmed this when I downloaded to my personal machine and calculated the size of the ethers.js package using the Finder application on Macs. So we have to take ethers.js's word that it is small in size, which is a big plus, though I do need to do further research to confirm this claim is valid.


7) How important is the quality of the documentation?

Ethers.js is the clear winner when it comes to the quality of the documentation of the library and it stands out for three key reasons.

 1. Ethers.js has an extensive “Getting Started Guide,” which helps a user orient themselves to both the library and the vocabulary of Ethereum.
 2. Ethers.js has useful call outs and additional information provided as part of the documentation, giving the end user visual cues, convenient links, and other helpful user experience features that make reading and using the documentation an enjoyable experience.
 3. Ethers.js documentation has an extremely useful feature - a toggle to single page view, in which all documentation is provided on a single page. This makes using “Ctrl + f” in the documentation a breeze, and helps with finding the method you are looking for quickly.

Web3.js has not had many visible changes to the documentation since our last article and could use an update to make the user experience more pleasant.

An indirect additional comment on the documentation - ethers.org provides a very helpful “playground,” where you can try out the library in browser: https://playground.ethers.org/. This useful feature lets a user get started playing around with the library quickly and easily. While it could be argued that remix.ethereum.org provides a similar playground experience for web3.js, this is not the goal of remix, and remix support ethers.js as well.


8) How important is the overall usage of the library?

The last time we looked at the numbers, web3.js was the clear winner in overall usage, with ethers.js gaining users at a rate that appeared that it would only be time before ethers.js caught up to web3.js. The results today show that both have healthy ecosystems and a large number of users. My personal belief is that the overall growth of the ecosystem shows that both libraries have been adopted by a significant number of projects and users. So, while web3.js has more downloads, stars, and overall metrics, ethers.js is competitive to web3.js in its usage. It’s fair to say both have been widely adopted.


9) How important is the license?

This is one area that has not changed since we last reported. Web3.js still has the LGPLv3 license and ethers.js the MIT license. I am not a lawyer, and so this is the hardest area for me to pick a winner. It is worth reviewing Slava Todavchich’s article “Understanding open-source and free software licensing,” which we suggested in our July 2020 blogpost.

But wait... there is a new category!


10) How important is the community and community experience?

Yes, I am adding a new way to evaluate the two libraries, based on my experience in Developer Relations and Software Community. I am personally looking for robust channels where developers using the software can interact with one another, find information about updates and hotfixes, share their use cases and help each other debug their code. The best software projects provide this for their users and it is a differentiating factor.

Web3.js and ethers.js have both embraced Discord as a means to communicate directly with their community of developers. Web3.js lives within the ChainSafe Discord Server, in the channel #web3js-general. Web3.js has used this channel not just to interact with developers, but  as of September 2021, to promote a web3.js developer survey to help drive the direction of changes for version 4.x of web3.js. Ethers.js utilizes the EF JavaScript Team Discord Server, in the #ethers channel. Both are active channels with communication on a daily basis.

Both also use Twitter to communicate changes to their audiences, though both have relatively light follower counts. @web3_js (1,250 followers) and @ethersproject (1,279 followers) only tweet to announce updates and changes to the libraries, serving as another way for notifications about updates to get through to developers.

ChainSafe also uses their Medium account to post some updates about web3.js, though not a regular cadence.  

GitHub continues to be a source of discussion for communities of both libraries, though the shift to Discord by both reflects a growing trend in the Ethereum community, as well as in software communities in general, to commit to this tool for a mix of synchronous and asynchronous communication.

The verdict is that both take development and interaction with their communities seriously.

What’s the next step?

You should go ahead and test out the libraries themselves with Infura, and we created a tutorial for just this purpose: Ethereum JavaScript Libraries: web3.js vs ethers.js (Part II). The best way to see if my evaluation is valid is to kick the tires on both libraries.

In conclusion, instead of declaring a winner, it seems that Ethereum itself is benefitting from having two leading JavaScript front-end libraries. More libraries being built that can utilize the features of web3.js and ethers.js will push them to be even better (like web3-react, for example). In updating this article, I have been struck by the growth of downloads and dependencies of both libraries, making me of the opinion that you can choose either and feel comfortable with the decision. I hope this illuminated some ways you can evaluate both to choose what works best for you.

Get started building on Infura for free today.

Ethereum JavaScript Libraries: Web3.js vs Ethers.js: An Update

As the clock ticks down to the Merge, the Teku and Infura teams have continued refining their collaboration. In case you missed it, these two teams have created an eye-poppingly fast Ethereum 2.0 client sync experience. Since then, they have continued refining their integration and made some important discoveries and improvements.


Attestations with Teku

One of those discoveries was that validators linked to a remote beacon node could have significant performance issues: specifically, a lot of missed attestations. Obviously, this is a pretty crucial issue. It turned out to be not just a problem with a remote beacon node, but specifically a remote beacon node behind load balancers, including Infura’s load balancers.

If you’re interested in the blow-by-blow, check out the Github issue here.

The solution the team came to was to implement an option to disable early attestation publishing when the block is received:

--validators-early-attestations-enabled[=<FALSE>]

Find the full Teku documentation on this issue here.

This option allowed validators connecting to Infura beacon nodes to have performance equivalent to validators connected to a local beacon node, which in and of itself is impressive. It would appear that this is a fix not just for nodes connecting through Infura, but for any context where Teku validators are using load-balanced beacon nodes.

The second innovation the team has made surrounding attestations is batch attestations. This consists of sending all attestations produced for a given slot to the beacon node in a single batch. In the context of Infura, this allows running a lot more validators without hitting rate limits.


The future of history

Another feature that the team has been working on, which isn’t quite ready yet for a full release, is an innovative way to store historical state without having a hard drive the size of the Library of Alexandria.

With increasing adoption of decentralized technology, there is more and more demand, and even novel use cases, for historical chain data. The most top-of-mind for many in the space is tax compliance. Institutions and even individuals are increasingly in need of solutions for being able to query, quickly and cheaply, historical chain data.

Like most great things in this space, the solution being developed uses Merkle tries. Without getting too deep into the woods (pun intended), as it’s not finished yet, the technique essentially takes the difference between slots and stores the branch updates. The applicability for this is tremendous, so watch this space for more updates.


Safety through Diversity

As we approach the reality of Ethereum 2.0, more and more voices are calling out a topic of vital importance: client diversity. The Ethereum Proof of Work consensus mechanism is, at this point, venerable and battle-tested, at least in blockchain terms, and is resistant to 51% of attacks. As the network transitions to Proof of Stake, the threat remains that a single Ethereum client will be running on a majority of validator nodes. This opens the door not only for a malicious attack, but also for single points of failure bringing down the entire network.

For more explanation, check out this very readable primer that should bring a lot of issues into focus. There are so many reasons to make the move to a Proof-of-Stake consensus model, and the network is on track to do so. It would be a stunning failure of vision and quite simply, wildly unsafe to move Ethereum to a PoS network that has a majority of any Ethereum client.

Even if we were to assume that all clients were going to act in the best interests of the network as a whole, which in and of itself is a leap most aren’t willing to take, the Ethereum network is a sprawling global entity with external dependencies. No client should be able to be a single point of failure for the entire network.

As we build the Beacon Chain and validators up and out, client diversity must be included as an essential consideration.

Learn more about Infura’s Eth2 API here and sign up for a free account.

Teku + Infura to 2.0: How to Handle Attestations

SoK: Validating Bridges as a Scaling Solution for Blockchains

So, why would you need a hybrid infrastructure model alongside Infura?

Let’s think about how your database is set up. You probably have your own database, which is great. What happens if that database goes down? Would your app continue to run seamlessly, delivering the experience you want your customers to get? Or, would your database shutdown cause outages and crashes in your app?

If the dataset you’re hosting is a public dataset, you have a new paradigm for making your infrastructure much more resilient and reliable by integrating Infura into your overall strategy. Infura implements a reverse proxy pattern internally and can be a highly reliable and performant node in your infrastructure stack, allowing you the ability to have a portion (or all) of your traffic routed to Infura.

You can choose to keep your database as your primary database with Infura as a backup, or vice versa. In this way, Infura will act as an always-on backup for your database, providing a level of flexibility previously not available with a single database running.

You also have the opportunity to use Infura as a stats comparison tool to make sure your performance is up to par. Alternatively, you may need to handle more load (request traffic) than your infrastructure can currently handle. You can route the overflow to an Infura project ID to handle spikes in traffic so your service stays up and running.

There are many opportunities for you to use Infura alongside your own in-house node infrastructure to improve your user experience. Let’s dive a little deeper on how we accomplish this.


What does it mean when Infura implements a reverse proxy pattern?

Let’s review what a normal proxy is first, and then we’ll flip it and reverse it, a la Missy Elliott, to talk about the reverse proxy. A proxy server (or web proxy or forward proxy) is a server located in front of a group of client machines (computers). When those computers make requests, the proxy server intercepts those requests and communicates with the target web servers on behalf of those clients. Basically, a proxy is a fancy word for a request/response middleman.

If you’re a visual learner, here’s a diagram from Cloudflare that shows just where that forward proxy sits:


What is a reverse proxy?

A reverse proxy is a server that typically sits on the edge of your infrastructure. It is responsible for receiving requests from web clients and subsequently routing them to one or more backend web servers.

Here’s another great diagram from Cloudflare to show how the reverse proxy fits in to the whole flow:




One of the main reasons to use a reverse proxy server is load balancing, ensuring the flow of traffic between clients and servers remains smooth. This is one of the main advantages of using both your own node and Infura. In addition, it allows you to cache content and provides web acceleration for improved performance. Lastly, reverse proxies allow for more efficient, secure SSL encryption and protection from DDoS attacks and related security issues.

As we previously mentioned, Infura can be used as a reverse proxy to assist with ensuring the flow of traffic for your clients and servers stays as smooth as possible, making for a more enjoyable user experience.


Some examples of a reverse proxy in action

Let’s first look at how we can set up a very simple reverse proxy using Caddy.

We will use our localhost and a backend HTTP service running on 127.0.0.1:9000 to make sure we’re getting our reverse proxy working correctly.

First, download Caddy. Once that’s downloaded, check out their Getting Started guide here. Or, follow along to learn how to set up a simple reverse proxy!


At this point, you may be running your own node, but since it takes too long to sync one for this article, we can substitute with a simple NodeJS stub to check that our reverse proxy is working correctly. I simply named mine main.js.


const http = require('http');

const hostname = '127.0.0.1';
const port = 9000;

const server = http.createServer((req, res) => {
   res.statusCode = 200;
   res.setHeader('Content-Type', 'text/plain');
   res.end('Reverse proxy success!\n');
});

server.listen(port, hostname, () => {
   console.log(`Server running at http://${hostname}:${port}/`);
});



This sets up a backend HTTP service running on 127.0.0.1:9000 mentioned earlier and will display a “Reverse proxy success!” message if our proxy is working correctly. To start this, run `node main.js` in a different terminal window and leave that connection open!

Next, we will want to create a Caddyfile (literally create a new text file in whatever directory you’re working in and name it Caddyfile). Once you have that set up, we will set up our simple reverse proxy itself inside the Caddyfile with just two lines:

localhost 

reverse_proxy 127.0.0.1:9000



In this instance, reverse_proxy is where we want to get our information from (the original site), and localhost is where we are redirecting to using our reverse proxy.

Now, from the same directory as your Caddyfile in a new terminal window from your `node main.js`, run:  

caddy run



This will start the caddy server and will allow your reverse proxy to work! Now, you’ll notice when you run this that you don’t see the “Reverse proxy success!” message popping up.

That’s because this just started the server. You now need to make a request to “https://localhost” and you’ll see the message. To do this, open another terminal window (that makes three now, for those of us keeping track), and simply run:

curl https://localhost



Running this command will give you the “Reverse proxy success!” message we were looking for, and now you know you’ve successfully set up a simple reverse proxy.


Enter Infura!

Now that we’ve gotten a basic reverse proxy up and running, let’s try one using an Infura endpoint. We will keep our overall setup of using a Caddyfile the same, but we won’t need the backend HTTP service running in the background, as that will be switched to an Infura endpoint.

We’re going to change up how our Caddyfile looks:

localhost 

reverse_proxy https://rinkeby.infura.io {
   header_up Host {/v3/<YOUR_PROJECT_ID>}
}



You will notice that we’ve added in a “header_up Host” inside the reverse_proxy section. This allows us to include our Project ID to both the Rinkeby endpoint and the localhost endpoint we are proxying to.

To test this out, we will need to send a request, so I used web3_clientVersion as an example:

curl https://localhost/v3/<YOUR_PROJECT_ID> \
-X POST \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"web3_clientVersion","params": [],"id":1}'



When we run this, we get the following output:

{"jsonrpc":"2.0","id":1,"result":"Geth/v1.10.8-omnibus-aef5bfb3/linux-amd64/go1.16.7"}



Cool! But how do I know my reverse proxy is working? Well, if you switch out `localhost` in our curl command to `rinkeby.infura.io`, you get the same output, which shows that our reverse proxy is running properly.


How do you use Infura as a backup for your own node?

We’re going to set things up initially the same as we did in the previous example but with two upstreams, one to our localhost and the other to the Infura node.

Next, we’re going to set up load balancing. Now, what’s load balancing? Load balancing acts like a traffic cop sitting in front of your application servers, routing client requests across all the servers that can fulfill those requests quickly and efficiently.

So how do we set that up?

Since we’re using Caddy, we can refer to their docs for the basics of how to use more than one upstream. When we look at lb_policy, there are many ways to determine which upstream Caddy will use first. Caddy will default to using the first listed upstream and will move down the list if the servers stop responding. In our example, we want to have localhost:9000 from our main.js file be the first upstream, meaning we want our reverse proxy to send the data through our localhost first, so we will identify that by putting it first in our list of upstreams (we will leave our Infura Rinkeby endpoint in as the second upstream):

localhost

reverse_proxy localhost:9000 https://rinkeby.infura.io {
   header_up Host {/v3/66172ed429624788ac264604755ba42c}
}



Since we are using the localhost:9000 port, we want to get that server back up and running. In another terminal window, start the Node server with node main.js.

To make sure everything is set up correctly, let’s run our request through by running the same request from earlier but with the :9000 port included, expecting to get the “Reverse proxy success!” message:

curl http://localhost:3000/v3/<YOUR_PROJECT_ID> \
-X POST \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"web3_clientVersion","params": [],"id":1}'



and we get the following output:

Reverse proxy success!



Excellent! Now, how do we incorporate the Infura endpoint to be a fallback?

You’ll notice we left the Infura endpoint in our Caddyfile where it originally stood and we asked our proxy to load balance using the first upstream (our localhost), which was how we got that “Reverse proxy success!” message.

Now that we confirmed that we set everything up correctly on our end, we’re going to kill the localhost server, mimicking what would happen if your private node went down. Once we do that, our requests should automatically start routing to the Infura node and we should get something similar to the below output:

{"jsonrpc":"2.0","id":1,"result":"Geth/v1.10.8-omnibus-aef5bfb3/linux-amd64/go1.16.7"}* Closing connection 0



But wait! We don’t get that! Instead, we get an error message.

This is because Caddy only allows us to use either two HTTP or two HTTPS endpoints - in our case, localhost is HTTP and our Infura endpoint is HTTPS.

Luckily, there is a tool we can use to make this work with localhost that will create a TLS certificate and sign it with a CA trusted locally by your device and browser. That tool is called mkcert, and it’s incredibly easy to install by following these steps.

Keep in mind if you’re doing this with your own private HTTPS node, you likely will not need this additional step.

If you are following our tutorial step-by-step (using localhost), be sure to follow all the steps, including updating your main.js file to the below to include the HTTPS requirement and the options constant.

const https = require('https');
const fs = require('fs')
const options = {
   key: fs.readFileSync('<PATH_TO_CERTIFICATE-KEY_FILE>.pem'),
   cert: fs.readFileSync('<PATH_TO_CERTIFICATE_FILE>.pem')
};

const hostname = '127.0.0.1';
const port = 9000;

const server = https.createServer(options, function(req, res) {
   res.statusCode = 200;
   res.setHeader('Content-Type', 'text/plain');
   setTimeout(() => {res.end('Reverse proxy success!\n');}, 1000)
});

server.listen(port, hostname, () => {
   console.log(`Server running at https://${hostname}:${port}/`);
});



When you run the mkcert localhost command from the tutorial, the certificate key file and certificate file used in the code above will be created.

Now that we have our localhost running with HTTPS, we can continue! Since we are running everything with HTTPS, we need to update our Caddyfile to reflect those changes.

localhost:3000 

reverse_proxy https://localhost:9000 https://rinkeby.infura.io {
   header_up Host {/v3/66172ed429624788ac264604755ba42c}
}



Now that we have all our files in order, let’s make sure our Node.js server is running and send that request again.

curl http://localhost:3000/v3/<YOUR_PROJECT_ID> \
-X POST \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"web3_clientVersion","params": [],"id":1}'



What do we get?

Reverse proxy success!



Perfect! That’s exactly what we want to get, as we have asked our reverse proxy to go to https://localhost:9000 first.

Now, what happens if we kill the Node server and send our request again? Remember last time we did this, we got an error message. This time we should be getting the result from our Infura Rinkeby node:

{"jsonrpc":"2.0","id":1,"result":"Geth/v1.10.8-omnibus-aef5bfb3/linux-amd64/go1.16.7"}



Success!

Our reverse proxy is, in essence, ignoring the localhost node, as it’s not functioning, and is defaulting to the Infura Rinkeby node!

Super easy, right? Now you know how to use Infura as a backup node to keep your services up and running smoothly!


Where can I learn more about reverse proxies?

Take a look at our client story from MakerDAO. They currently use Infura for a multitude of reasons, including using us as a backup node solution to ensure all developers can use the MakerDAO toolkit!

Another great example is the Polygon PoS network. We initially began working with Polygon to share some traffic load for their network, allowing users to access the Polygon networks via Infura endpoints and effectively ensuring their network remains fast and functional, regardless of traffic spikes they may see. We have since increased our partnership so we are now handling 100% of their network traffic.

Check out this blog post highlighting multiple companies across all verticals using a hybrid infrastructure model of their own nodes plus Infura. Get some ideas on how we can help you accomplish your needs, from verifying transactions to providing backup database services!

If you would like to run an Infura node in addition to your own, sign up for a free trial today.

How to Run Your Own Node AND an Infura Node

When enterprise developers build dapps on Ethereum, they often have to consider the entire tech stack and development process. The list of considerations range from application features such as Web2 interfaces to deployment, which is usually on a permissioned network hosted by a preferred cloud provider. Since most full-stack software engineers build off of SDKs and API calls, it’s important to establish the value of the application with consideration of the deployment network.



Get the best of both Web2 and Web3 worlds

Many enterprise blockchain business cases build on the principles of traditional Web2 development. Web2 focuses on operating with a fluid user experience with attention to detail on scalable and responsive code on multiple devices. A valuable decentralized application (dapp) in Web3 redesigns the economics and industry roles while building on complementary existing systems -- instead of fully replacing those systems with analogous Web3 features.

Say you would like to reinvent a syndicated loans issuance platform such as IPREO. This effort would require significant IT resources to spin up a minimum viable product from the ground up if you’re recreating features like tranche issuance calculations or calendar date exceptions. Instead, consider a path to lesser resistance: blockchain modules that connect these digital assets to new liquidity networks. The functionality is a re-issuance of an existing financial instrument to ABC network with a listing on XYZ automatic market maker rather than the full end-to-end dashboard.

To connect to pockets of liquidity, an enterprise developer must deploy with the same smart contract language that is compatible with the Ethereum Virtual Machine (EVM) and look to bridge the assets to networks with the desired investor and issuer markets.


Why build on public Ethereum?

Until now, publishing enterprise dapps on Ethereum requires significant system integration, executive buy-in and high set-up costs. Recently, we have seen more public blockchains working with enterprises to cover non-functional technical needs in order to meet minimum requirements of security audits and performance. However, the relatively tribal nature of the blockchain developer subculture means that mainstream enterprises are still conservative when it comes to building on Ethereum.

If you are an enterprise developer, consider the following advantages of building on public Ethereum vs. permissioned networks:

1. Faster setup and lower total cost of ownership

2. Immutability and longevity of the data stored with thousands of independent nodes

3. Composability and low barrier of entry to decentralized finance (DeFi)




1. Faster set-up and lower total cost of ownership

This is a standard private blockchain journey for a consortium:

After you develop your dapp, a lot of time is focused on node deployment adhering to enterprise software standards. On the business side, you are also trying to build a consortium to agree on the benefits and adoption before the tech is tested.

The consortium model usually chooses a separate tech vendor that does not have single ownership from one consortium member to prevent conflicts of interest. The tech vendor determining deployment and long-term support likely runs the Ethereum nodes on behalf of participants. This will get the product to market faster and focus on the business benefits.

The last step involves time and licenses for adding more nodes and mutualizing infrastructure costs across participants. Compared with private networks that remove tokens from their operation, public networks require ownership of native tokens to fund transactions. This gas cost pays for the infrastructure -- third parties running full nodes and running operations for mining/validating. In my time building enterprise projects, we have never seen this happen.

The public journey is much more straightforward. After you develop your dapp, the deployment is a choice between public networks with updated configurations on your Truffle setup. The added complexity is the gas costs for funding and running your transactions on this network.

To simplify connectivity to EVM-compatible networks, you can use Infura’s Ethereum API to connect your app instantly with a single line of code. Simplify your transaction management with Infura Transactions (ITX) using prepaid accounts without holding ETH on your balance sheets. ITX is a transaction relayer that manages your transactions to prevent dropped or stuck transactions.

You will also likely want to work with a team such as Diligence that can audit your contracts and monitor them when they’re live.

Public Ethereum has an overall lower total cost of ownership when you compare the operational cost of running a system on mainnet rather than focusing on the ownership and maintenance of the network itself.

A consortium may have more control in the private chain and face less security and treasury reviews at first. However, your infrastructure overhead and negotiations on consortium network matters tend to outweigh the convenience and added features of connecting to mainnet.


2. Immutability and Longevity

The Ethereum mainnet is secured by the interaction of thousands of independent nodes run by individuals and miners throughout the world. Private chains typically have a small number of nodes controlled by one or a few organizations. Those nodes can be tightly controlled, but only a few need to be compromised in order to rewrite the chain or commit fraudulent transactions.

At ConsenSys, we’ve recommended public networks to enterprise developers for their resilience of replicated data as you are able to recover more quickly with a larger network of more than 15,000 independent nodes. The more peers you have, the easier it is to find a seed and fully recover your recorded transactions. In consensus decisions, the more blockchain validators there are to verify transactions, the more difficult it is to coordinate a majority decision that may lead to an attack.

In a permissioned network, the security is governed by the node with the least security. Your network is only as secure as the weakest link. Any added nodes to the network may also increase the surface area of attack. Most institutions will recommend a base software security test in order to join as a full node owner. The node owner will have to pass standard penetration testing to prevent any hacking on the node in case it is a bad actor to the entire network.


3. Composability and Low Barrier to Entry on DeFi


The Ethereum network powers a vibrant ecosystem of third party applications and technology including DeFi and NFTs. A highly composable and interoperable system allows you to connect to DeFi to build financial products that enable and combine multiple apps to match specific user needs. The Ethereum mainnet offers enterprise developers the ability to gain access to market liquidity and provide innovative ways for users to participate in the exchange, trading or growth of that liquidity.

When we say composable, it’s much more than just an open banking API. It’s a set of open source live protocol contracts that can be called and extended. We’ve seen pure forks of open source code like with Uniswap to get sushiswap. The market has seen countless copies of DeFi models such as Compound and Aave, and it doesn’t look like things are slowing down anytime soon.

There’s more and more real value happening in DeFi leading us to believe that cryptocurrencies are not a fad. It is here to stay.

Watch Clemens’ presentation “Pitching Public Ethereum to Enterprises” at EdCon 2021.

Interested in building on Ethereum? Contact us to get support on starting your enterprise project.

3 things enterprise developers should consider when deploying on Ethereum

Are you excited by blockchain but don’t have a great deal of experience coding? It can be easy to fall down a rabbit hole of technical tutorials that make assumptions regarding your initial development knowledge. A particularly important topic to grasp is basic security within your code.

As you begin to build out your very own dApp, you will have to include information such as an Infura API key, along with a mnemonic.

If you are new to coding, this is the equivalent of giving a stranger your social security number and keys to your home. Once this information is public, there is no definitive way to ensure it hasn’t been captured by a person or web crawler, which could result in malicious behavior.

So, how can we address this?

Thankfully, we can use dotenv along with git to protect our sensitive information within our project when / if we push to github.

Dotenv is a zero-dependency module that loads environment variables from a .env file into process.env, storing configuration in the environment separate from the code. It is often a convention for environment variables to be stored in a .env file or other mechanisms based on the server you are using.

Note: This article will focus on building out a project using Truffle and Infura.

In our project, we will need to run the following command:

npm i dotenv


Once the process in our terminal has been completed, we will want to make sure we have the dependency successfully installed. Head over to your package.json file and check to ensure that dotenv has been added under dependencies.

Next, at the root of our project, let’s create a .env file:

Here is where you will add all of the sensitive information that should not be shared.

We will make sure we can access our .env information in our truffle.config file. At the top of the truffle.config file, add the following:

require("dotenv").config


This will tell your project to load anything that is in the .env into an environment variable, granting you access to it.

Now, instead of having to put our Infura api key or mnemonic in an exposed file, we can import that information from our .env file.

When it comes to gaining access to our project key we are going to use, sign up to Infura and create a project. In your dashboard, you should see something similar to this:

The following code is an example between the usage of .env and exposed information within truffle.config:

const HDWalletProvider = require('@truffle/hdwallet-provider');

const infuraURL = 'https://rinkeby.infura.io/v3/<project id here>'

const mnemonic = "Your mnemonic here"


rinkeby: {

provider: () => new HDWalletProvider (mnemonic, infuraURL),

network_id: 4,

gas: 5500000,

confirmations: 2,

timeoutBlocks: 200,

skipDryRun: true

},


Imagine if you pushed this up to github. Anyone would have the ability to open your truffle.config file could take advantage of your exposed mnemonic and project id from Infura.

Let’s take a look at that same code and implement better security practices.

Notice how we are calling upon the information without having to directly add to our file.

One important detail, as of now even with an .env file: if you push this project to github, it will show the .env file, which would defeat the purpose!

Take a look for yourself.

This is where .gitignore comes into play. We will need to create a .gitignore file, so we can push this project up to github.

Without getting into git, a quick summary could be git is version control software that keeps track of all of your files and the versions of them. What .gitignore does is it tells git not to keep track of this file along with everything it contains.

If you want to dive deeper into git along with other foundational material, have a look at our Basic Training, a free course that helps ensure you have the fundamental tools when developing.

At our root (similar to the level our .env file lives), we will create a .gitignore. Inside of that file, we will add .env along with any other files you would rather not be pushed to github.

We can now push our project up to github and notice that our .env file is no longer exposed. Our sensitive information is now much more secure.

If you are experimenting with this, make sure you add your .env file to your .gitignore before pushing.

If you are running into issues, remember gitignore ignores only untracked files. If your files were committed in the past, they are now tracked by git. To ignore them, you first need to delete said files, git rm them, commit and then ignore.

Otherwise, you can delete the .env file and run

Git rm .env --cached


Here is a helpful link discussing the removal of sensitive data from a repo if it was previously committed and discusses how to clean the git history. Savvy attackers don't just look at the most recent repository info, they'll look at the history of it as well.

Note: If you come across it in documentation, a question you might have is
“What is env. example”

An env. example file, on the contrary to this tutorial, is actually included in the repository, it is used as an example file for you to know what KEY=VALUE pairs you need for your project. Most often, it is used to copy the .env file and then change the values.

Example of execution:
Enter to the project root directory using your terminal.

Check if .env the file exists or not.

If the file does not exist then create a file named .env.

Now execute the command

cp .env.local .env.


So the .env.sample file has all the ENV declarations defined but without their values. It helps other developers establish/set up the project without having to reverse-engineer the codebase.

So after git clone, you usually execute the command `cp .env.sample .env` and fill in the values with the Infura credentials as we saw in the example above.

Note: When you create a new repo using github, if you scroll down you should see the option to include a .gitignore file so you don’t have to create one yourself in the future.

Hopefully, you found this article on basic security practices helpful as you begin to develop your very own projects. Feel free to join our Discord if you want to continue the conversation, share projects, ideas, and join the community!

Start here with a free Infura account >

How to Use .env to Enhance Basic Security Within Your DApp

Optimistic Ethereum is a rollup scaling solution that allows users to submit transactions on the Ethereum network and get them executed faster for a much lower gas cost. From the perspectives of users and developers, this is a "parallel universe" called Layer 2, or L2, where users typically have the same addresses as they do on the Ethereum blockchain (also called Layer 1 or L1). There are gateways that allow messages and assets to be transferred between the universes.

The Optimism network API largely uses the same JSON-RPC specification as Ethereum and Infura supports all the necessary API methods for building a fully functional application on the Optimistic Ethereum network.


Why are transactions cheaper on Optimism?

On L1 Ethereum, thousands of nodes run your transaction to verify that the proposed block that includes it is valid. This process is expensive and has to be paid for. Unlike on L1 Ethereum, Optimistic roll ups provide faster and cheaper transactions because it allows users to perform most of their tasks off-chain in a "layer 2" protocol. On Optimistic Ethereum, the smart contract has only two tasks: deposits/withdrawals and verifying proofs of transactions on chain. This makes the process more efficient and a lot cheaper.


Why is this safe?

The great thing about decentralization is you can trust that transactions are executed correctly because there are thousands of computers executing them. Honest miners would reject such a transaction. With rollups, you don't have that level of redundancy.

The answer, in the case of optimistic rollups, is incentives. Every node in the network has to put up a stake before it can propose a new block with the execution results of a transaction. Every other node can check up on those results, and if it thinks they are incorrect, dispute them. The dispute is resolved on L1, so it is as trustworthy as anything else in Ethereum. Whichever node lies, either proposer or disputer, loses its stake and most of it goes to the other node involved.

Of course, the whole point is to avoid running transactions in L1. This system achieves that by making it pointless to cheat. Any proposer who attempts to cheat is going to be caught by the other nodes, lose its stake, and not get the invalid transaction result accepted as valid. A disputer can force a single transaction to go into L1 arbitration as a denial of service attack, but the stake is high enough that it wouldn't be worth doing.


How does Infura work with Optimism?

Infura exposes endpoints for Optimistic Ethereum (the production network) and Optimistic Kovan (the test network). You use them the same way you use any other network, by selecting them from the menu and using the specified endpoint.

There are a few small differences between building on Layer 1 Ethereum and Optimism:

1. You must use the JSON-RPC API as we do not support Websockets yet.
2. Search filters are not yet supported


How to Get Started on Optimism...



The main difference between Optimism and regular L1 Ethereum (other than the cost) is the access point URL.

| Network          | RPC URL |


… If you are using the Truffle development environment

Infura users can add the free Truffle Optimism add-on directly on their Infura dashboard. The Truffle Optimism box also contains the configuration definitions required to use Infura. Currently, you will need to manually add the gas costs of transactions when you use Truffle to run deployments or tests on Optimistic Kovan or the main Optimistic Ethereum network.


… If you are using Hardhat

To use Optimistic Ethereum or Kovan, edit hardhat.config.js's modules.export.networks to add these definitions:

"optimistic-kovan": {
    url: 'https://optimism-kovan.infura.io/v3/<Infura Project ID>',
    accounts: { mnemonic: <your account mnemonic goes here> },
    gasPrice: 15000000,
    ovm: true // This sets the network as using the ovm and ensure
                      // contract will be compiled against that.
},
"optimistic-ethereum": {
  url: 'https://optimism-mainnet.infura.io/v3/<Infura Project ID>',
  accounts: { mnemonic: <your account mnemonic goes here> },
  gasPrice: 15000000,
  ovm: true // This sets the network as using the ovm and ensure
                    // contract will be compiled against that.
}



Then you simply run:

npx hardhat --network optimistic-<kovan or ethereum> <command>



… If you are using Remix

When you use the Remix Optimism plugin to develop for Optimism, network connections are created through the wallet. If you use MetaMask, you can select the network Custom RPC and fill in the details:

What is Optimistic Ethereum?

In the second half of 2017, the ICO boom catapulted Ethereum’s popularity. Infura had been in production for over a year and we felt confident about the state of our infrastructure and our ability to scale it. As token sales hammered the Ethereum mainnet, and more Web3 neophytes installed wallets like Metamask to explore and interact with this new ecosystem, Infura’s architecture was truly tested and we encountered new opportunities to improve and optimize our service.

Overnight, our small team organized an on-call, rotating shift system so we could maintain Infura’s availability and service our growing user base, 24 hours a day, 7 days a week. It was an exciting moment in Ethereum’s history and it was exhilarating to be a part of it. As the market continued to mature, we entered a slower period that some have referred to as “Crypto Winter.” This quieter era provided us with the time and space to take a step back, evaluate the state of our infrastructure and pour our collective energy into making engineering improvements to our service. Addressing eth_call traffic was one of the first places to start.


The Importance of eth_call

Ethereum smart contracts are just pieces of code waiting to be executed by the Ethereum Virtual Machine (EVM). To interact with these smart contracts your application will be doing one of two things. It will either be sending an eth_call or sending a transaction to the contract. The state of the Ethereum network changes as each block of transactions gets added to the network.

If you are trading on Uniswap, or interacting with other DeFi applications, you will be reading data from the contract based on the current state of the network before sending a transaction which will modify the resulting state of the network. An analogy would be making sure you know the balance of your bank account before sending someone a check. In technical terms, it means you need to have an Ethereum node with the full chain downloaded and up-to-date before you read the data from the smart contract.

That gives you the required data to prepare the transaction you send to the network which will mint tokens, swap tokens, open a new position, or any of the other mutable methods allowed by a smart contract. Each of those eth_call reads executes by taking the parameters of the request and evaluating it within an execution environment (the Ethereum EVM with the latest network state). What is returned is the calculated output of the EVM.

By crypto winter, we were handling billions of API requests and about 300MM of those were eth_calls. Eth_call is a complex API request and serving all that traffic with zero downtime was a great accomplishment but we knew there were areas where we had to improve. Our alerting systems noticed when spikes in traffic resulted in higher latency times or occasional error rate anomalies. We knew we could do better and that to prepare for traffic spikes in the future, we would need to revamp our systems. Over the next 18 months we had the opportunity to develop those improvements with hindsight and battle scars informing our decisions. We started by revisiting the monitoring and observability of our platform. Did we have enough visibility into any potential bottlenecks?


Scaling eth_call Traffic

The most common way to scale API request traffic is to cache. You would put a server-side cache or CDN in front of your origin servers to protect your infrastructure. The cache would serve these common requests and shield your origin servers from the bulk of the traffic. If I ask for Resource A and a million other people ask for Resource A, the ideal scenario is that the cache loads Resource A from the origin once and the remaining 999,999 requests get served from the cache. The difference with serving blockchain data is that there is less cache commonality between similar requests. A million users interacting with the same smart contract may get a million different results.


Battle-Test: Running eth_calls Locally vs Infura’s Ethereum API

Two billion eth_calls per day averages out to about 23k requests per second, but in the last month we’ve observed spikes of up to 30k requests per second! Ethereum nodes are busy machines. They are doing a lot of things at the same time: validating blocks, storing and reading data from the local disk, keeping track of pending transactions from the peer-to-peer network, and handling RPC API requests from your applications. The good news is that the teams that have written Ethereum clients like Geth, Besu, and Open Ethereum have made them very performant.

Using two of the open-source tools developed by the Infura team, Versus and Ethspam, we ran a load test against a local Ethereum node to establish the number of eth_call requests that can be handled by a local node. The results of this test revealed that the local node was able to handle a simulated eth_call load of up to 5,249 requests per second:


This is no small feat! An eth_call request is more compute heavy than a traditional API request. As a result, performance can vary depending on what else is going on inside the node at that point in time. Take a look at a sample of profiling data of what exactly is going on in a node during a load test like this:

As there’s so much going on, the request throughput a node is able to deliver tends to vary. We loaded the test parameters from the same file to ensure that the same 5000 requests would be sent to the node with each run. The performance of the test varied by as much as 22.2%! Below are the results from two additional test results, performed within seconds of each other:

If you were wondering how many requests an application like Uniswap makes in the course of making a trade for something like ETH to an ERC-20 token, inspecting the network traffic shows that the Metamask Web3 browser makes about 24 requests during the course of presenting a transaction estimate to the user.

By contrast, during the activity peak in 2017 Infura was processing +300MM eth_calls per day. Since that peak, we’ve scaled Infura’s architecture to over two billion eth_calls per day during the recent DeFi activity spike of 2020 - that’s nearly a 7x increase in volume! Our increased ability to handle such high volumes, in large part, comes down to our approach to scaling methods like eth_call. Back in 2017, scaling was high-touch and manual. Today, Infura’s architecture dynamically scales to support our APIs. The process is seamless, fully automated and means that developers can expect reliability and stability from their Infura service, even during unprecedented network or usage spikes.

We feel a deep responsibility to give developers peace of mind so they can focus less on infrastructure and more on building great user experiences. If you’re interested in learning more about our architecture, you might find this post very helpful.

Yours in Infra,

E.G.

Want more insight from the Infura engineering team? Subscribe to the Infura newsletter and never miss a post. As always, if you have questions or feature requests, you can join our community or reach out to us directly.

Engineering

What Does it Take to Handle Two Billion eth_calls Per Day?

We’re happy to share that IPFS 0.5, the largest upgrade to the IPFS protocol and Public Network yet, is now available on the Infura IPFS service. The upgrade offers major performance and reliability updates so that you can distribute content peer-to-peer more efficiently. The improvements to the Distributed Hash Table (DHT) and stability of peering allow us to provide an even more reliable product and continue to get IPFS into the hands of dapp developers.

Upgraded Subdomain Gateway Support

Version 0.5 allows Infura to provide a faster, more secure IPFS gateway, enabled by having the root content identifier (CID) be a subdomain, rather than part of the path portion of the URL. The upgraded subdomain gateway support ensures that every dapp gets its own browser origin and makes it easier to write websites that are compatible with IPFS because absolute paths will now work. This greatly improves the security of our offering while helping us support some great new features.

The previous, path-based Infura IPFS gateway will remain in the short term, but will redirect automatically to the new subdomain-based one. All users should migrate to the subdomain-based gateway, as the path-based gateway will eventually be deprecated. We will provide ample communication and timelines before any services are changed, but if you want handle your migration to the subdomain-based gateway now, here’s how to do so:

Ensure that your code or libraries no longer reference IPFS resources on Infura endpoints via URLs of the form:

https://ipfs.infura.io/ipfs/<cid-v0>/<path>

And instead only utilize URLs of the form:

https://<cid-v1-base32>.ipfs.infura-ipfs.io/<path>


As the subdomains are case insensitive, the CID format also changes to become a CIDv1 with the base32 encoding.

As an example:

https://ipfs.infura.io/ipfs/Qmexhq2sBHnXQbvyP2GfUdbnY7HCagH2Mw5vUNSBn2nxip/static/media/ipfs-logo.e2de4d07.svg

will become

https://bafybeihw65wvlfz2qu53eceycjenfskhd3mhu7mcltslrisjjfigbgw3nu.ipfs.infura-ipfs.io/static/media/ipfs-logo.e2de4d07.svg

And that’s it! 🎉

Looking forward, IPFS v0.6 is coming soon and we’re working hard towards the launch of our premium IPFS product. This product will expand on the current API functionality, provide a full dashboard and the latest auth integration, and offer an overall more reliable and scalable solution for developers with production ready applications. We will have much more on this in the coming months.

Subscribe to our newsletter so you can be the first to know when our new IPFS product has launched. As always, if you have questions or feature requests, you can join our community or reach out to us directly.

News

IPFS 0.5 is here with a new improved gateway!

Another Ethereum hard fork is upon us. You know what that means — time to update your nodes! Ethereum’s program of continuous innovation makes critical improvements to the network. These improvements result in new protocol upgrades, like the upcoming Istanbul Fork. This upgrade brings improvements in layer 2 performance, increased resilience against DDoS attacks, greater interoperability between Ethereum and Zcash, and enables more inventive functions within contracts.

On October 2 Eastern Time, Ethereum will implement Istanbul for the Ropsten Testnet (10.2). This will be followed by Görli in late October, Rinkeby in November and Kovan in December. The mainnet implementation is due to take place in the first months of 2020.

To retain the ability to verify and confirm new blocks on the Ethereum blockchain, all nodes in the network must upgrade to the main consensus before January 2020.


Running Your Own Node? Get Fork-Ready.

Ethereum is a peer-to-peer network. That means that anyone who wants to run Ethereum infrastructure will need to update their software to an Ethereum client version that is “fork-ready”. These software versions are due for release in late September. If you “miss the fork” and fail to upgrade your software in time, you’ll no longer have an accurate view into the source of blockchain data. You’ll need to resynchronize your node with the blockchain, a process that could take hours or days.

If you’re running your own node, you can get “fork-ready” by taking the following steps:

 1. Regularly check client pages for the software update announcement:

 * Geth
 * Parity
 * Besu
 * Trinity
 * Nethermind;

2. Review the fork updates to determine if any changes are needed in your applications, or if any users will be impacted;

3. Update your node prior to the fork block.


Using Infura? No Changes Required.

If you’re an Infura user, don’t worry — we’re ready. There’s no action needed from you. Infura has been running reliable Ethereum infrastructure for over three years and we’re adept at handling large-scale updates during network hard forks. We’ll take care of the upgrade so you can continue building great software.


As always, we’re here to help. If you have any questions about the upgrade, please reach out to the team via our Community page or drop us an email at support@infura.io.

We’re Ready for the Istanbul Fork

Infura is excited to announce full support of the Görli test network. The Görli testnet is a community-driven effort and is the first proof-of-authority cross-client Ethereum testnet. Our mission has always been to provide reliable access to developers building on top of Ethereum and the Görli test network gives our developers another option to facilitate development and testing.

Infura has been a supporter and participant in this community effort from the beginning. Founder, E.G. Galano, presented at GörliCon last month and has been actively involved in demonstrating our support. See his presentation here.

In order to use the Görli test network, login to your Infura Dashboard where you will find the correct Endpoint URL to use to connect to Görli.

Announcing Görli Testnet Support

** Infura will support the Constantinople Postponement and is actively working on updating its infrastructure to adjust to this new release. Read more about the Constantinople delay below or stay updated via twitter at @infura_io. **

UPDATE [Jan 16]: “We’ve been coordinating with others in the community over the last 24 hrs and we have completed updating our infrastructure to support delaying the Constantinople network upgrade.”

The Ethereum Core Developers and the Ethereum Security Community were made aware of the potential Constantinople-related issues identified by ChainSecurity on January 15, 2019. We are investigating any potential vulnerabilities and will follow with updates in this blog post and across social media channels.

Out of an abundance of caution, key stakeholders around the Ethereum community have determined that the best course of action will be to delay the planned Constantinople fork that would have occurred at block 7,080,000 on January 16, 2019.

This will require anyone running a node (node operators, exchanges, miners, wallet services, etc…) to update to a new version of Geth or Parity before block 7,080,000. Block 7,080,000 will occur in approximately 32 hours from the time of this publishing or at approximately January 16, 8:00pm PT / January 16, 11:00pm ET / January 17, 4:00am GMT.


What You Need To Do

If you are a person who simply interacts with Ethereum (you do not run a node), you do not need to do anything.


Miners, Exchanges, Node Operators:

 * Update your Geth and/or Parity instances when they are released.
 * These releases are not released yet. We will update this post when they are available.
 * Links and version numbers and instructions will be provided here when they are available.
 * We expect to have updated releases in 3–4 hours from the time this blog is published.


Geth

 * Upgrade to 1.8.21 , OR
 * Downgrade to Geth 1.8.19, OR
 * Remain on 1.8.20, but use the switch ‘–override.constantinople=9999999’ to postpone the Constantinople fork indefinitely.


Parity

 * Upgrade to Parity Ethereum 2.2.7-stable (recommended)
 * Upgrade to Parity Ethereum 2.3.0-beta
 * Downgrade to Parity Ethereum 2.2.4-beta (not recommended)


Everyone Else:


Ledger, Trezor, Safe-T, Parity Signer, WallEth, Paper Wallets, MyCrypto, MyEtherWallet and other users or token holders that do not participate in the network by syncing and running a node.

 * You do not have to do anything.


Contract owners

 * You do not have to do anything.
 * You may choose to examine the analysis of the potential vulnerability and check your contracts.
 * However, you do not have to do anything as the change that would introduce this potential vulnerability will not be enabled.


How was the decision to postpone the Constantinople fork was made

Security researchers like ChainSecurity and TrailOfBits ran (and are still running) analysis across the entire blockchain. They did not find any cases of this vulnerability in the wild. However, there is still a non-zero risk that some contracts could be affected.

Because the risk is non-zero and the amount of time required to determine the risk with confidence is longer the amount of time available before the planned Constantinople upgrade, a decision was reached to postpone the fork out of an abundance of caution.

This article was put together in a collaborative effort by EvanVanNess, Infura, MyCrypto, Parity, Status, The Ethereum Foundation, and the Ethereum Cat Herders.

For the full text and latest Geth/Parity versions, please read the Ethereum Foundation’s blog post here: https://blog.ethereum.org/2019/01/15/security-alert-ethereum-constantinople-postponement/



Network

Ethereum Network Updates, Upgrades, Hard Forks

What Does it Take to Handle Two Billion eth_calls Per Day?

IPFS 0.5 is here with a new improved gateway!

We’re Ready for the Istanbul Fork

Announcing Görli Testnet Support

Security Alert: Ethereum Constantinople Postponement