At Infura, we believe testnet ETH should be free and easily accessible.

As an Ethereum developer, you know how important it is to test your dapps before deploying them to the mainnet. However, testing can be challenging when you need to acquire Sepolia testnet ETH to fund your smart contracts and there’s nowhere to turn.

Aligned with Infura’s mission of making building in web3 easy and accessible to everyone, we're releasing Infura’s new Ethereum testnet faucet that drips 0.5 ETH daily requests.


Why we created the Infura testnet faucet


At Infura, we believe testnet ETH should be free and easily accessible. Recent shortages of testnet ETH have caused significant problems for developers, who have had to purchase GoETH on the open market.

The monetization of GoETH led to speculators driving the price to $1.61 per token, and one user even purchased a Cryptopunk using funds from GoETH transactions.

Because testnet ETH should be free and easily accessible, the Ethereum Foundation is shutting down Goerli testnet and requesting that developers migrate to the Sepolia Testnet.

Infura's new testnet faucet is here to help the ecosystem by providing a reliable, high-volume drip of Sepolia ETH. Facilitating web3 development QA procedures on a test network is critical to the future of blockchain implementation at the protocol level. Access to a stable, high-volume faucet will make web3 development easier for developers.

With this faucet, you can request free testnet ether with just a few clicks. Want to see for yourself?

Here’s how.


How to use the Infura testnet faucet


To use the Infura testnet faucet, follow these simple steps:

First, to go: https://www.infura.io/faucet/sepolia.  

Then enter your Ethereum address into the open field. (More detailed steps to do this are here: How to get your Sepolia Wallet address on MetaMask)

Next, click the login button to access your Infura account.

Click "Receive ETH" and wait for the transaction to be processed. You can follow the Etherscan link for transaction verification.

Check your MetaMask wallet to confirm you’ve received your testnet ETH. You can do this on the Sepolia network. (Reminder: Secure your MetaMask wallet)



It's that easy! You can request testnet ETH as often as you need to, but please be aware of the 0.5 ETH daily limit.


Keep learning with Infura


Congratulations! Now you have the ETH you need to test your dapp, publishing a few smart contracts, and even mint some NFTs. Below are a few helpful resources to keep learning with Infura:

 * Getting Started with Infura
 * The Developer’s Guide to the Web3 Stack
 * Get started with using Infura’s NFT API + SDK
 * Read our Infura NFT API Documentation for more ideas
 * Deploy a Smart Contract on Sepolia Testnet and test it out!


Frequently Asked Questions


Q: Can I receive more testnet ETH?

A: The current limit is 0.5 testnet ETH per day, but this could change later.

We may increase testnet ETH rewards for engaging with Infura in the future. Open emails and follow us on Twitter to get the latest updates on test ETH withdrawal limits!

Q: Will you support upcoming testnets like Holesky?

A: We're working closely with the Ethereum Foundation on launching and providing services to additional testing and development in the Ethereum ecosystem. The upcoming Shanghai / Capella upgrade is in scope with upcoming iterations of the feature.

Q: What other features can we expect in the future?

A:  With the recent acquisition of Hal by ConsenSys, we plan to implement an example monitoring service to notify users when transactions are  fully processed. We already use Hal for internal monitoring of transaction processing for manual retries.

Additional FAQs are answered directly on the faucet site.

We hope the new Infura testnet faucet makes your developer experience easier and more pleasant so you can keep shipping your innovations and building the future of web3.

Infura product updates and feature announcements.

Infura Product & Features

Product & Features

Introducing Infura’s ETH testnet faucet: Get 0.5 ETH daily to test your dapps!

The Developer’s Guide to the Web3 Stack

Infura’s NFT API + SDK are packed with all the tooling you need to mint your innovations with ease.

Have you ever wanted to create something beautiful with a few lines of code? What if with just three lines of code you could build an NFT marketplace? Or mint digital art? With the announcement of Infura's NFT API + SDK general release today, you can! It’s never been easier to mint any-NFT-thing you want.  

Over the past several months, the Infura team has been hard at work to create the best NFT tooling possible. It was only June of last year when we started the private beta with a handful of developers, using a handful of endpoints that connected to Ethereum and Polygon.

“ConsenSys products have powered the NFT experience since the very beginning, with a significant volume of NFT transactions in the ecosystem passing through the MetaMask wallet backed by web3’s strongest infrastructure from Infura. Since the limited beta release of our NFT API and SDKs in June 2022, our team has made significant strides in making the NFT toolkit the best tooling builders need to bring their NFT innovation to the world,” said Rob Dawson, Chief Technology Officer, ConsenSys Software.

Today, the Infura NFT API comes with 14 endpoints so developers have access to all the metadata they need for building. The NFT API also includes read and write capabilities from eight blockchain networks, in four languages, with integrated IPFS access.

“With the general availability of the Infura NFT API, we are focused on helping even more developers capture the huge demand of the NFT market and accelerate their building journey with instant access to cross-chain data, pre-built templates, and the ability to mint NFT collections to 8 networks in one integrated product,” Rob added.

Today we want to thank you the 500 participants who took part in our beta programs and gave us such valuable feedback that has allowed us to build the NFT API + SDK we believe will empower creators.

Let’s learn more.


The Infura NFT API + SDK offers superior security with ConsenSys Diligence


While other RPC-providers might have similar endpoint offerings, Infura’s NFT API + SDK is a clear choice for creators and developers who value the safety of their smart contracts.

The Infura NFT SDK comes with three ERC-721 and ERC-1155  templates that cover more than 85% of all NFT use cases. Each template has been pre-audited by leading blockchain security platform, ConsenSys Diligence. This means these templates are not only easily customized with metadata to create and mint NFTs in minutes, but also provide top security.

Being pre-audited means Infura’s NFT templates have been run through Diligence’s smart contract security software, Diligence Fuzzing.

The fuzzing tool battle tests contracts by attacking them with millions of scenarios over and over again until the contract is deemed error-free. The blockchain is immutable and immutable means forever. Why risk your IP using anything else?


The Infura NFT API + SDK offers multi-chain options and compatibility


Infura is an industry leader when it comes to multi-chain compatibility with RPC endpoints to 14 networks. When it comes to the NFT API, 14 endpoints with read/write capability are supported across 8 networks.

This includes early access to the new zkEVM launched by ConsenSys that’s scheduled to be available to the general public in April. Its zero knowledge-rollup technology will reduce blocktimes, latency, and gas fees–significant for NFT dapps.


The Infura NFT API + SDK offers accelerated development with the ConsenSys product suite


Developers using the Infura NFT API can take advantage of accelerated development for their NFT innovations with easy integration to the ConsenSys product suite. Add Infura, Diligence, ConsenSys zkEVM, and MetaMask to your tooling to take your NFT project to the next level.

Developers and creators can use the Truffle Suite to build an NFT dapp, spin up a dev environment to test for free, then check the Truffle dashboard for results and predict gas fees.

Next, download the MetaMask Unity SDK to use the wallet as a login authenticator and automatically connect users and their wallets to your NFT dapp or blockchain game.


Hear what devs using the Infura NFT API + SDK are saying


"Infura’s NFT API removed all the legwork to provide NFT capabilities for our web3 gaming platform. We no longer have to analyze every smart contract on-chain to determine whether they are NFTs or store NFT data and metadata. Using the Infura NFT API means we don't need to worry about scaling our database to account for increased traffic of our wallet application. Infura does it all for us." - Jay Chung, Global Business Development at Intella X / Neowiz

“Infura’s NFT API and SDK helped us very quickly build a dashboard and advanced filtering system for our users by leveraging the high-level API. We did not need to parse a long list of blockchain transactions ourselves to display meaningful information. And compared to some concurrent providers, we’ve never had any issues with the API stability and the rate limiting. Plus, the first tier of pricing helped us grow in our first months without being too expensive.” - Louis Pinsard, Co-Founder & CTO at Dialog


The Infura NFT API + SDK is only getting better


While we believe the Infura NFT API + SDK are built to empower NFT creators today we’re certainly not finished making it the best tooling on the market. Here’s what to expect from the product roadmap:  

 * Six more Diligence-secured NFT smart contracts
   
 * Expansion of the read function, making it even easier for developers to extract, manipulate, and report on metadata.
   
 * Low code and no code offerings for those non-technical creators to ensure every kind of builder can participate in the NFT creator economy.


Get started today


Check out the below demo for step-by-step instructions to get started using the Infura NFT API + SDK today.



The Infura NFT API + SDK is now available for all Infura users. Don’t have any Infura account to use the NFT tooling?

No problem. You can create an account in just three steps for free on infura.io/register.

Happy minting!

Empowering creators with the Infura NFT API + SDK

Ethereum Network Updates, Upgrades, Hard Forks

Infura - Ethereum Network Updates

Network

How To Choose The Right Blockchain For Your Next Dapp

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

Infura Developer Tutorials

Tutorials

Getting Started With Infura

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?

Infura now supports additional networks including Arbitrum, Optimism and Polygon.

All three projects are essentially new blockchain networks. They offer low transaction fees and faster confirmation times compared to Ethereum. Crucially, they extend the utility of Ethereum as users can transact using their assets that fundamentally reside on Ethereum.

This scaling approach is called off-chain protocols and we have put together a short post to help explain how they help to scale (and extend the utility) of Ethereum.


Why not just transact on Ethereum? What is the scalability bottleneck?

Ethereum supports around 15 transactions per second and as seen in Figure 1 the network fees tend to skyrocket when users exceed the network’s throughput ceiling. In some ways, the throughput limitation is self-imposed by the community in the pursuit of decentralization.

The goal for decentralization is to maximise the percentage of the world’s population who can verify the blockchain’s integrity (and transactions) in real-time. This goal is essential to minimise the trust in block producers as the community can self-enforce the set of consensus rules that govern the validity of blocks. Depending on the target percentage of the world’s population, there is a limit to the computational, storage and bandwidth available to the network for processing transactions.

Our challenge as a community is to figure out how to increase the network’s throughput while adhering to the imposed resource constraints.


Why should we care about off-chain protocols like sidechains or rollups?

Most approaches to scale the network focus on:

 * Distributing verification. The verification task is distributed amongst nodes on the network as opposed to requiring all nodes to replicate the same work (Ethereum today).
 * Better utilize the network's available resources. The network's resources should be continuously utilised and not allowed to sit idle. For example, short block intervals to better utilize bandwidth.  

Scaling solutions still remain a few years away from adoption as they require major changes to the underlying Ethereum protocol.

An alternative and popular scaling approach, off-chain protocols, is a solution that is immediately available. It scales the network in a following way:

Off-chain protocols: Transaction processing is moved away from Ethereum to another network while still transacting with the same assets that reside on Ethereum.

We consider this a scaling solution as other blockchain networks are not limited by the same resource constraints as Ethereum. They can experiment with various scaling protocols (or simply test the limits of go-ethereum) while extending the utility of Ethereum.


Where are my assets held when transferred to another network?

A bridge contract is responsible for holding the user’s assets on one blockchain (Ethereum) and notifying the other network to mint an equal quantity of coins for the user. Once minted, the user can transact on the other network and eventually withdraw their funds back to the original blockchain (Ethereum) via the bridge contract.

Not all bridge contracts are equal. We must consider the bridge contract's process for deciding when to release funds back to the user. Ideally, the funds should only be released if the bridge contract is convinced the other network is not compromised. This is called the underlying trust assumption that ultimately protects the user’s funds. It can often cause controversy when discussing whether an off-chain protocol is truly scaling Ethereum.

On one hand, some users only consider a new blockchain network a scalability solution if the other network can retain the same (or very close to) security of Ethereum.  Protocols that can achieve this level of security are often called rollups. Whereas, other users will be satisfied with stronger trust assumptions as long as the funds locked into the other network are secure enough (sidechains).

Rollups, that retain the same security as the main-chain, will require more resources from Ethereum. For example, every transaction on the rollup network generates a state update that is published to the bridge contract. Whereas a side-chain does not necessarily require significant resources from Ethereum as validation of transactions is performed by a set of external parties. This trade-off on security/resources will be felt financially by the users and as a result there is no free-lunch.

Regardless, we believe that different bridge contracts will emerge and implement different degrees of trust. In the end, all blockchain networks which support transacting assets that reside on Ethereum will increase the utility of Ethereum. It is just important that users are aware of the trust assumptions and risks before deciding to lock funds into a bridge contract.


What is a sidechain?

The term sidechain originates from a paper by Blockstream. It was an interoperability solution to enable two blockchains to verify information about each other’s progress via light-weight proofs. The intention was to allow bitcoins to be locked in Bitcoin and to be released in the other network (and vice versa) without trusting any intermediary with the funds.

Over the years, the term sidechain has taken on a life of its own. It is often used to imply that an independent blockchain network has a relationship with another blockchain network. In practice, this is implemented with a bridge contract that allows assets to be moved from the main-chain (Ethereum) to another blockchain network.

There are three type of bridge contracts that are used for side-chains:

 * Single organisational. A single party has custody of the funds locked in the bridge contract.
 * Multi organisational. A fixed set of independent parties (K of N) has custody of funds that are locked.
 * Crypto-economic. A dynamic set of parties, determined by their weight in assets, have custody of the funds.

For example, WBTC is a single organisational bridge as the BTC is held by BitGo. The Liquid Network and RSK blockchain implement a multi-organisational bridge as an appointed set of parties will authorise assets to be moved across from one blockchain to another (i.e., implemented as a multi-sig). Polygon is a crypto-economic bridge as it relies on (⅔)+1 of stake to appoint validators who post periodic checkpoints about the network’s state to the bridge contract (and this checkpoint can be used to automate user withdrawals).

Crucially, the bridge contract for a sidechain does not verify the integrity of the other network and instead it relies on a set of parties to attest to its validity. It is assumed that at least a threshold of parties should have a financial incentive to remain honest and protect the user’s funds.

While the cost of a sidechain transaction consumes no additional Ethereum resources, the trade off is that the network will not retain the security of Ethereum and ultimately, trustlessness.


What is a rollup?

The term rollup originates from barry whitehat’s zkrollup and it emerged from the research on Plasma.

A rollup is still an independent blockchain network, but the transacted assets that reside on Ethereum are protected by the bridge contract. It must be continuously convinced the rollup network is not compromised and the funds are not at risk. In the worst-case, the bridge will bypass the other network and allow users to unwind and eventually withdraw their funds.

A rollup can retain the same (or very close to) the security of Ethereum and this is accomplished by solving the following problems:

 * Data availability. The bridge contract must be convinced that all data is publicly available. This allows anyone to independently compute the rollup’s stateful database.
 * State transition integrity. The bridge contract must be convinced that all state transitions (transactions) are valid.
 * Censorship-resistance. The bridge contract will self-enforce transaction inclusion to ensure a user can eventually withdraw their funds if the network is compromised (or no longer making progress).

As a quick summary on potential solutions. The data availability problem is solved by just posting all data to the Ethereum network and this is where the name rollup originates (to roll up the data). The state transition integrity problem is solved using a fraud proof (Optimistic rollup) or a validity proof (zero knowledge rollups) system. The censorship-resistance problem is a little trickier, and often not discussed, but it requires the bridge contract to self-force the inclusion and eventual execution of user-generated transactions.

There is an on-going financial cost for rollup. The network must continuously provide evidence to the bridge contract that all finalised transactions are valid and the network is not compromised. This consumes resources from Ethereum and impacts the scalability that is attainable by rollups. However in the immediate term, it can significantly reduce the cost of a transaction. For example, in Arbitrum, a swap costs 1,600 gas compared to 120,000 gas on Ethereum.


What is the difference between a sidechain and a rollup?

Sidechains, such as Polygon and rollups, such as Optimism and Arbitrum are just independent blockchain networks. They have their own set of block producers and smart contract environments. The core difference between a sidechain and a rollup is found in the bridge contract that locks funds from Ethereum onto the other network. Precisely, it is the trust assumption that protects the funds held by the bridge contract.

 * Sidechain. The bridge contract may receive information about the other network, but it does not validate its correctness. A set of parties who govern the bridge are responsible for checking the other network is not compromised and attesting this fact to the bridge contract.
 * Rollup. A set of parties (sequencers) are responsible for providing evidence about the state of the other network to the bridge contract. It is up to the bridge contract to validate the evidence’s correctness and to independently verify the other network is not compromised.

It is a subtle difference, but it boils down to whether the bridge contract can self-enforce the validity of transactions on the other network or if it must rely upon a trusted set of parties to attest that it is valid.

Of course, there is no free lunch. Rollup networks can retain the security of Ethereum, but it also consumes more resources of Ethereum. This increases the financial cost to transact on a rollup network compared to a side-chain.  As a user or developer, you will need to consider the security offered by the other network and the potential financial cost that it entails.

Choose a solution that best suits your use case.


How can I get started with rollups and sidechains?

You can check out our blog announcements for the networks we support which includes Arbitrum, Optimism and Polygon.

All networks adhere to the same JSON RPC standard as the Ethereum network and they support EMV-compatible smart contracts. You can activate the networks in your Infura account, update the provider URL and start interacting with the networks immediately.

Arbitrum and Optimism are still in beta and in the progress of preparing for their mainnet launch. You may need to contact the teams if you want to deploy a smart contract to their mainnet. Polygon is already launched and you can start deploying contracts immediately.

We hope you found this article about rollups and side-chains informative. At Infura, we have supported Ethereum for over 5 years and we are excited to now support new projects that extend the utility (and scalability) of Ethereum.

Off-chain protocols: Sidechains and Rollups

The developer demand for scaling solutions that work directly with Ethereum is here and growing, so today we are very excited to launch API support for the Polygon PoS network on Infura. Polygon PoS is a thriving solution that we are thrilled to be supporting as it adds a ton of value to the community of developers building with our tools.

Polygon PoS  is a hybrid Plasma Proof-of-Stake sidechain to the Ethereum mainnet which consists of a Tendermint consensus validator layer and a Plasma sidechain for block production. This configuration allows for higher transaction throughput, lower gas fees, and through Polygon's established bridges, easy connection back to the Ethereum mainnet. Check out Polygon's full getting started docs for more information.

The Infura Polygon network API largely utilizes the same JSON RPC specification as Ethereum and Infura will support all the necessary API methods for building a fully functional application on the Polygon network. To get started all you have to do is add the new Polygon Network Add-on to your account. To do this, login to your Infura account, go to your Ethereum workspace/project list and click to upgrade your plan,

From here you will see the new Network Add-ons section, select the Polygon network add-on,

You will be taken to a quick checkout page where you can finalize your account changes and you will be all set up and ready to go!

You can find all of the documentation for the new APIs here. If you have any questions, feedback, or just want to chat reach out to us at our community page.

Our colleagues at Truffle are also adding a great new tool to help developers start building right away on the Polygon network. The new Truffle CLI integration will simplify the process by which a developer can instantiate, compile, and deploy an application vis-a-vis Polygon PoS, using a boilerplate Polygon Truffle project (a “Truffle Box”). In addition to enabling development for Polygon PoS, The Polygon Truffle Box includes detailed instructions for configuring and using a Truffle project to interact with the Polygon PoS chain. Both Infura and Truffle will support the Polygon PoS mainnet and Mumbai testnet. You can access all of the new Truffle Polygon tools here.

We are very excited to be adding Polygon PoS to our development suite and we can't wait to see all of the amazing applications built with these tools. Stay tuned as we continue to add more networks, features, and products that accelerate and simplify development on this exciting new technology.

Want instant, scalable, and reliable API access to the Ethereum, Eth2, IPFS, and Filecoin, and Polygon networks? Sign up for our Core service to start building for free today. Need more request volume and direct support? Check out our premium plans and pick the right plan for your project.

Twitter | Newsletter | Community | Docs | Contact | We're Hiring!



Infura and Truffle Now Support Polygon

Add 1 million daily requests to your Ethereum API subscription for only $200 USD per month!

Ethereum Request Packs are here! Now Infura customers (on any subscription tier) can add increments of 1,000,000 daily requests to their account for $200 per month!

Say you’re subscribed to the Team tier and are currently allotted 1,000,000 requests per day. You can now add an additional 1,000,000 requests per day, bringing you to a total of 2,000,000 total daily requests for $425 per month. You can add multiple Request Packs directly in your Dashboard until you reach a limit of 100MM total daily requests. If you need more than 100MM/day, please reach out to us and we will set you up with a custom account.


How to Get Started

To add Ethereum Request Packs to your account, click Change Plan in your Dashboard, select Request Packs, and designate the number of packs you’d like to purchase.

Once you've successfully checked out, your Billing page will be updated to reflect your new daily request limit.

That's it! If you need help at any time, join the Infura Community to connect with the team or drop us an email at support@infura.io.


Other Updates from Infura:


Why You Should Use ITX Instead of Building Your Own In-House Relayer

We know how frustrating stuck transactions can be so that’s why we’re rigorously working to solve transaction management friction for the industry. Check out this post where we outline three critical problems that currently prevent developers and DeFi users from getting more efficient transactions on Ethereum, and how you can use Infura Transactions to eliminate this friction to create a better end user experience.


ICYMI, MetaMask Launched a Custom Networks API to Improve Layer 2 Support

The API now enables developers to recommend Layer 2 networks, like Polygon (formerly Matic), Arbitrum, and Optimism; sidechains like SKALE and xDAI. Once connected and configured, these networks are added to the user’s network menu, enabling the user to switch between networks. If you’re operating a dApp that integrates with MetaMask, and want to start onboarding more users to Layer 2 networks, check out MetaMask’s latest post.


Notice: Eth2 Public Beta Deprecation of Project IDs

ICYMI: Our Eth2 API is publicly available! Please note that on April 1, project IDs used in our Eth2 private beta will no longer be accepted in the public beta. More details and what to do.


We’re Ready for the Berlin Fork

Ethereum mainnet is currently targeting the Berlin fork for April 14, 2021 at block height 12,244,000. Using Infura? No changes required! Running your own node? How to get fork-ready.


New Developer Tutorials!

 * Want to jump into Filecoin and start building something? This tutorial will get you up and running quickly by creating a simple Node.js script using Infura and the Filecoin network.
 * How to Access the Eth2 API Pyrmont testnet

Want instant, scalable, and reliable API access to the Ethereum, Eth2, IPFS, and Filecoin networks? Sign up for our Core service to start building for free today. Need more request volume and direct support? Check out Infura+ to pick the right plan for your project.

Twitter | Newsletter | Community | Docs | Contact | We're Hiring!

Introducing Ethereum Request Packs!

This blog post captures the highlights from Patrick McCorry's talk at EthDenver 2021. Patrick is Master of Relays at Infura and is passionately working to solve transaction management friction for the industry. We outline three critical problems that currently prevent developers and DeFi users from getting more efficient transactions on Ethereum, and how Infura Transactions seeks to eliminate this friction to create a better end user experience.


What is the problem behind stuck transactions?

The Ethereum network is like a funnel. Transactions waiting inside the funnel can be considered pending, and they are only mined after they have passed through the funnel. A block is generated every 14 seconds, and every block contains around 12MM gas. When there are too many pending transactions in the funnel, and it exceeds the block capacity, it’s physically impossible for every pending transaction to get into the next block. Generally, this is the source of stuck transactions.

Ethereum as a global permissionless fee market. It is up to YOU to entice the miner.

Given this list of pending transactions, miners get to decide which transactions to include in the next block and which transactions to ignore. This is why we have a fee market. It is up to you to set a high fee that can outcompete all other pending transactions and thus entice miners to include your transaction over others.


Problem #1: Transactions get dropped by the network

Let's consider the first source of stuck transactions. You pick your transaction, set a fee you are happy with, sign it, and broadcast it to the network. Then, for some reason, the transaction gets dropped and it won't be picked up by miners because they are simply unaware of it.

Dropped transactions are typical when the network is under high congestion. Your transaction must be propagated over the devp2p network, and any node between you and the miners can decide to drop your transaction for any reason - especially when the mempool is congested. So, let’s assume an Ethereum node can only hold 4,096 transactions (default node configuration setting) and there are 4,097 transactions in the pending pool, then one transaction has to get dropped. If your transaction is the one with the lowest fee transaction in the pending pool, it will be the one that is most likely to get dropped.

There are also various different (and often awkward) network rules that have an impact on why transactions get stuck. For example: you might have 17 transactions in the pending pool, but it only guarantees to keep around 16, so the 17th gets dropped as seen by the go-ethereum code and config.

A wider problem with dropped transactions is called the nonce gap issue. Let’s say you send 6 transactions in a row. For some reason, transaction 3 gets dropped from the network. As a result, its child transactions (in this case transaction 4, 5, and 6) are going to get stuck, and will never be confirmed by a miner. That’s because there’s a special network rule: for every Ethereum transaction, the nonce must increment strictly by 1. In this case however, transaction 3 got dropped and makes it impossible for any proceeding transaction to get mined. That’s an extremely frustrating situation to be in.

How theoretical is the nonce gap problem? Do we really incur dropped transactions? Let’s look at this research from Blocknative. Their forensic mempool investigation surfaced the events on March 12 and 13 2020, when over 50,000 transactions an hour were being dropped from the pending pool as you can see here:

One company that suffered during Black Thursday (and highlighted in the Blocknative blog post) was MakerDAO.

When the price of ETH collapsed on March 12, 2020, a large number of CDPs on MakerDAO immediately became undercollateralized and eligible for forcible liquidation. When a CDP is forcefully liquidated, it triggers an auction process that lets anyone (keeper bots) place a bid to purchase the remaining collateral. However, on Black Thursday, many Keeper transactions were adversely affected as the network congestion led to miner nodes dropping transactions at an unusually high rate.

This led to the keeper's bot non-dropped transactions becoming stuck. They tried to bump the gas price of the stuck transactions including setting an outrageous fee of 4,500 gwei (10x the normal gas fee) - and even that transaction got stuck! This is because the dropped transactions resulted in a nonce gap that prohibited miners from including any of the child transactions. The solution was not to bump the gas price, but to re-publish the dropped transactions and fix the nonce gap issue.

Of course, some users noticed that keeper bots were struggling to submit bids and they subsequently won the the auctions by submitting 0 DAI bids. Overall, the keeper bots just had a bug in their relay infrastructure.


Problem #2: Transaction queues get stuck

The second problem is how a bot manages the transaction fees for each transaction in their queue of transactions.

It can become problematic if the same fee schedule is not applied across the entire transaction queue. For example, you can see in the above that if there is a low fee transaction in the middle of the queue, then it can be nearly as bad as having a dropped transaction. This is because Ethereum miners don't always look at your dependent transactions, and as a result the queue can get stuck because of that one low fee. (This is slightly different to Bitcoin, as miners do consider dependent transactions. This is called "child pays for parent"  and it helps bump up the transaction fee.)


Problem #3: Paying too much… bad fee management

Finally, the third problem: setting the gas price too high. Commonly, people visit Eth Gas Station, get the trader rate, and then send that to the network. For the most part, that works. You pay a premium fee, and your transaction will get mined in the next few blocks. Of course, the prices are so volatile that even that doesn’t work, because the fees skyrocket by the time you send your transaction. Consequently,  everyone overpays the fee and you still don't have a guarantee that the fee will be sufficient for the transaction to get mined.


Solving these problems is not trivial.

Most teams that build their own in-house relayers would agree that transaction relayer software is really fiddly. In fact, one team we spoke with recently, described their in-house relayer as a complex beast.

Writing robust fee-replacement and transaction monitoring software is complex and time consuming. Transaction monitoring also requires dedicated infrastructure, resources, and effort running 24/7 to work reliably. And even if you build your own relayer, it’s really difficult to get satisfactory guarantees. Unless done properly transactions won’t be mined at a reliable rate, resulting in bad UX. If you get the relayer software wrong, you can end up with a potential loss of funds. Some transactions are time-critical (e.g. a CDP) and fragile transaction infrastructure could lose you money.

Just like the issues faced by the keeper bots competing in the liquidation auction on Black Thursday...most of the problems could have been avoided with better relayer software.


...Enter Infura Transactions

So really, the whole point of Infura Transactions (ITX) is to help you to no longer deal with stuck transactions and to ensure you do not need to re-invent the wheel by building your own in-house relayer.

How does it work? You can simply hook into the Infura Transactions API and send your relay transaction to Infura. We'll guarantee that your transaction gets delivered to Ethereum and that you will no longer deal with stuck transactions.


How does ITX solve the problem?

The ITX relayer is built with the following features:

 * Republish periodically. ITX re-publishes the transaction every few minutes, so even if your transaction gets dropped, we don't need to check if it was dropped or not, we will always just republish it.
 * Highest fee first. Our transaction queue is organized such that the highest fee paying transaction is at the start of the queue and the lowest fee paying transaction is at the end of the queue.
 * Real-time fee adjustments. Our initial gas price estimate for sending the transaction aims to pay the minimum price while targeting a quick confirmation.
 * Escalator algorithm. We have an increasingly sophisticated bidding strategy such that we pay the best price at any time.

Our list of features and ITX is built with reliability in mind and to help avoid users paying unnecessarily excess fees. There are plenty of gotchas at the network level that we have discovered while building ITX and we hope no one else will need to re-implement the wheel to overcome the same issues.


Who may find ITX useful?

You may find ITX useful if you are working on the following products:

 * Crypto wallet providers. There are several wallet providers who send transactions on behalf of their users including Gnosis, Argent, Dharma and Loopring. Our infrastructure is close to plug-and-play for most smart contract wallet providers.
 * Sequencers and rollup providers. A sequencer needs to send very large bocks (~12 million gas for an optimism block) and thus they need to effectively outcompete the rest of the network to get their block confirmed. Our fee bumping strategy ensures that we'll eventually get the rollup block mined at the best price.
 * Server-side scripts & DeFi bots. An example includes the keeper bot's for the liquidation auctions and ensuring the auction bids are reliably processed in time.
 * Dapps. An example is the Ethereum Name service as it requires ~3-4 transactions before the domain name is set up. Ideally, the user can simply send ETH to the ENS service, and then the server-side script finishes the process on behalf of the user.


How do we get started?


We hope that you are now hyped up about using the ITX service for your project.

To get started:

 1. ETH is money. You can deposit directly into our service as a pre-payment to cover your gas fees. This will act as your virtual gas tank and we will use that ETH to pay for gas on the network. ETH is the payment mechanism, ETH is money, use it as money, and deposit into the ITX service.
 2. Ethereum account. We use Ethereum signing keys to handle authentication for new relay requests to the ITX service. You sign it and then simply give us the job.
 3. Coding project. You need a script or a project that will send a transaction to the network.


How  to set up your gas tank:

All deposits are handled by an on-chain smart contract and it has the same address across all networks:

 * Send deposit. You can send the funds using the depositFor function.
 * Wait. Your balance will be updated on the ITX service after 10 blocks.
 * You are ready. Just send us a transaction and watch it get mined.

Just to remind everyone. ETH is money. ETH is how we take the payment. And ETH is used in your gas tank.

Of course, since the deposit is handled by a smart contract. You can simply automate the top-up process in your application and you may even use ITX to perform the continuous top-ups.


How have we implemented ITX:

We have three new JSON RPC commands. If you are using ethers.js, you can simply use provider.send(["jsonRpcName","parameters"]) to send us the command.

Let's briefly cover each command:  

relay_getBalance: Given an Ethereum account, it will return the balance of the user's gas tank in WEI.

relay_sendTransaction: Given a pre-signed relay transaction, it will return a relay transaction has to let you track it's progress.

relay_getTransactionStatus: Given a relay transaction hash, it will return a list of broadcast Ethereum Transactions (and then you can check if one is mined).

Our Status API returns a list of transaction hashes due to how fee bumping works in Ethereum. Every time we bump the network fee on your behalf it will produce a new Ethereum Transaction (and a new hash). We decided to provide all  hashes to let you decide how your users will track the progress of their transaction.  


Find out more:

We hope you have enjoyed this article and hopefully you will decide to give ITX instead of trying to build an in-house relayer (i.e., a complex beast).

If you would like to find out more information about ITX and the API, then please our documentation and submit a request for alpha access. If you want something slightly more hands-on, then our ITX demo project is available for you to try.

Why You Should Use ITX Instead of Building Your Own In-House Relayer


Start using Infura Transactions (ITX) on Mainnet today!

Infura Transactions (ITX) is the easiest way to send Ethereum transactions that mitigates many of the complexities around gas fees and transaction management.


Our on-chain flow lets you pay your ITX fees using ETH, no credit card needed.

To get started as a new user, you can simply deposit ETH into our on-chain smart contract. The ITX relaying system detects the on-chain deposit and then increments your gas tank. When the gas tank is filled, you can send up a transaction request and ITX will guarantee it is mined in the Ethereum blockchain in a timely manner and at the best price. See our docs for specific details on the ITX relay fee structure.


Off-chain ITX Credits coming soon!

Stay tuned as we will soon be adding support for ITX Credits. ITX Credits will enable you to purchase transaction credits directly in your Infura dashboard using a credit card. This means you can send Ethereum transactions with all the features of ITX and the added benefit of not having to manage on-chain ETH.

Only a limited number of developers will be admitted into the alpha, so submit your request to be considered. Subscribe or check our community for future updates.


Help shape Infura Transactions for a chance to win a $500 Amazon gift card

As we continue to build out ITX, we want to make sure you're able to pay for the feature in a way that makes the most sense for you. By filling out this three minute survey, you'll have your say about how you'd like to pay for ITX, and what aspects of the service you're most interested in.

Your time is super valuable, so to thank you for your contribution, all completed surveys will go into the draw to win a $500 Amazon gift card 💳


Tuning into EthDenver?

Make sure you check out our super ambitious Infura bounty! 👇

Bring Uniswap and ITX closer together 🧡🦄🧡

🏆 Prize: $1500 🏆

To win this bounty, we challenge you to build a new website that allows a user to swap tokens on Uniswap via Infura Transaction Service (ITX). The user should not require any ETH upfront or a pre-deposit on ITX to use the service. Instead, the relayer (you!) should pay the network fee up front and then get refunded via the swap’s output. For example, if the user swaps DAI to ETH, then the relayer takes a slice of the ETH to cover the cost (and some profit too).

We are applying for a Unigrant to support the development of this project after the EthDenver hackathon. Assuming the grant is successful and the winning team delivers an exciting MVP, then there should be a larger bounty available to bring the relayer-enabled exchange to production (and/or hopefully integrated into the Uniswap interface). Of course, all code should be open-source and as you will soon see, we have designed ITX to have minimal integration-specific components such that the final router contract will not be aware of ITX at all and it is easy to swap out ITX with another relay service.

So let’s stop stuck transactions (Uniswap swaps) together!

+ ICYMI:

A presentation by Infura's Patrick McCorry at ETHDenver: "Infura Transaction Relays for Better UX"


Access Our Eth2 API Public Beta!

The future of Ethereum is here! If you want to analyze the state of the Eth2 Beacon Chain and increase the reliability of your Eth2 validator setup, you can get beta access to our Eth2 API here.

*Note: project IDs used during the Eth2 private beta will no longer work after 4/1/21. New Eth2 users as well as those who participated in the Eth2 private beta should create a new project ID specific to Eth2.


New Developer Tutorials

 * Ever wonder how developers take advantage of arbitrage opportunities with flash loans and flash swaps? Check out this post where we break down arbitrage trading, contract coding, and optimistic transfers.
 * A walk through on how to structure a program with Infura that can watch for and execute on profitable arbitrage trades!
 * How to deploy your contract to Ropsten using the combined power of Infura and Truffle
 * Building with Filecoin? Here’s how to get started using Infura’s Filecoin API


We’re hiring!

We’re passionate about building a diverse team of humans and as such, if you think you've got what it takes for our dynamic, remote-friendly, start-up environment— apply!

Technical Project Manager | Data Scientist | Senior Product Manager | Senior Backend Engineer

Want instant, scalable, and reliable API access to the Ethereum, Eth2, IPFS, and Filecoin networks? Sign up for our Core service to start building for free today. Need more request volume and direct support? Check out Infura+ to pick the right plan for your project.

Twitter | Newsletter | Community | Docs | Contact

News

ITX Now Live on Mainnet | ETHDenver Bounties

The future of Ethereum is here!


Start accessing the Eth2 Beacon Chain through the Infura Eth2 API.  

You can use Infura’s Eth2 API to analyze the state of the Eth2 chain, as well as simplify and increase the reliability of your Eth2 validator setup. Explore the full functionality and API spec.


Access the Beta


*Notice: Eth2 public beta: deprecation of project IDs*

Other resources

 * Ethereum 2.0 refers to a set of interconnected upgrades that will make Ethereum more scalable, more secure, and more sustainable. Learn more.
 * Ethereum Foundation: Ethereum 2.0 Explained
 * Ethereum 2.0 Knowledge Base
 * How to query validator balances programmatically with Infura’s Eth2 API
 * A Guide to ConsenSys’ Eth2 Products

Product & Features

Infura product updates and feature announcements.

Infura and Truffle Now Support Polygon

Introducing Ethereum Request Packs!

Why You Should Use ITX Instead of Building Your Own In-House Relayer

ITX Now Live on Mainnet | ETHDenver Bounties

Infura’s Eth2 API is Live! How to Access the Public Beta