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

Disaster recovery, transaction processing, and accelerated development tooling can help your DeFi project achieve scalability

Digital assets have reached their mainstream moment. In 2021, the estimated increase in cryptocurrency adoption globally was 880%. The total value of the NFT market was $40 billion in 2021. The total ETH deposited in the Eth2 Beacon Chain, part of Ethereum’s forthcoming upgrade from Proof-of-Work to Proof-of-Stake known as “the Merge,” was $10 million as of March 22.


This growth is astounding to anyone, but it’s especially meaningful if you’ve launched a DeFi protocol or work for one. This growth means affirmation of your venture or the continued success of your business. It also means it’s time to scale and that requires leveling up your infrastructure to withstand the new challenges growth brings.


Scalability is the problem we are all trying to solve in order for innovations to reach their full potential. At Infura, we’re constantly evolving our platform to ensure our platform gives customers infrastructure architected to scale limitlessly. Web3 connectivity is essential for scalable ease of development and enterprise standards. The Infura API suite provides instant HTTPS and WebSocket access to Ethereum, the world’s largest public blockchain, decentralized storage layer, IPFS, and Layer 2 chains such as Polygon, Abritrum, and Optimism:


Over 400,000 developers use Infura today for diverse use cases. When it comes to DeFi, Infura offers seamless integration with wallets like MetaMask that use Infura Transactions (ITX), NFT marketplaces like the Palm Studio to deploy full nodes and scalable endpoints, and staking-as-a-service businesses like Codefi access Eth2’s Beacon Chain.


Here are three core Infura features you can leverage to help your DeFi protocol scale.

Transaction processing and gas management with Infura Transactions

Building DeFi protocols often comes with the challenges of stuck transactions, high gas fees, and hidden costs. At Infura we want to ensure you’re focused on building the next DeFi innovation and not the complexities of handling ETH. Infura Transactions (ITX) was designed to do just this.


The Infura Transactions feature provides developers the ability to send transactions with the best gas prices and no need for complex transaction management. DeFi companies can pay with FIAT currencies like the US dollar and execute ETH-based transactions without owning ETH on their balance sheets.


For crypto wallet providers, you can plug and play with this feature to meet the needs of your infrastructure and create a seamless experience for your end user transaction. DeFi dapps can have the same seamless experience with fast managed transactions that help users lower their fees by sending ETH to the ITX feature and using Infura’s relay service. This feature also allows for optimal gas prices for L2s and is now available on Polygon. A critical step for L2 rollups is writing their transactions back to mainnet. The ITX feature has a fee adjustment strategy to ensure the rollup block is mined at the best price. All these benefits combined mean you can scale your products and services.

Disaster recovery and backup support for exchanges and funds

For large crypto enterprises like exchanges and funds, whose businesses rely on priority Service Level Agreements with their institutional clients, it is crucial that data is never lost or that their services go offline by having backup infrastructure in place. This is the benefit of Infura’s backup support and disaster recovery feature.

Disaster recovery shows operational maturity and DeFi companies who have this in place have the peace of mind their services can run despite interruptions and that data is being archived. In addition to being a backup service, customers can also use this feature to run full nodes they diversify with Infura access points.



Accelerated development with the ConsenSys tech stack

Accelerated development is a feature Infura offers by giving customers the opportunity to leverage our partner’s tools and services. Infura is part of ConsenSys, a blockchain development company founded by Ethereum’s co-founder, Joseph Lubin. Being part of ConsenSys means Infura’s customers have access to additional tooling, support, and even collaborations to accelerate their business development from other ConsenSys companies like MetaMask, Codefi, ConsenSys NFT, Quorum, and more.

In the case of DeFi, Codefi leverages Infura’s Teku Client endpoints to provide institutions with reliable 99.5% uptime to minimize slashing for staking ETH in four key areas:

An example of accelerated development for an NFT project is the Palm Network powered by Infura and Quorum. ConsenSys NFT worked with Palm NFT studio to launch a low-cost and sustainable Quorum network dedicated to NFT launches run on Infura infrastructure. You can learn more about the partnership here.


Key Takeaways


Web3 and digital assets are here to stay. As the growth of the DeFi industry continues to surpass even the most bullish predictions, businesses must be able to scale at light-speed, and these core features of Infura will help get them there.


In addition to Ethereum and IPFS, Infura supports Ethereum Layer 2s platforms  like Polygon, Arbitrum, and Optimism with a roadmap set to continue on a multi-blockchain and protocol expansion. Keep an eye out for more news about this expansion.


Start building with Infura today for free here!

Scaling Your DeFi Project - 3 Core Infura Features You Can Leverage

What’s the great thing about building an app with a public blockchain as a backend? The availability of the data. It’s always there, it’s always running, and all you have to do is query it. What’s the bad thing about it? ...There’s a lot of data to be queried.

So much, in fact, that you might find your dapp’s performance bottlenecked, or at least impacted, by what you’re getting back from the JSON-RPC interface. Luckily for you, there are solutions, and they live on Infura.


What are filters?

Filters are JSON RPC methods that allow you specify the information you’re interested in coming from the network. The filter requests this information, and all information resulting from that filter since the time of the filter’s last request is returned. Filters are available over HTTPS.

You can create filters with the following API methods:

 * eth_newFilter
 * eth_newBlockFilter

Poll for changes to the filters using the eth_getFilterChanges API method which returns an array of changes that occurred since the last poll.

Using filters offer several advantages: first of all, you control when they fire. This gives you the ability to customize when that call goes out within the flow of your dapp. And even if it’s been a while since your last filter request, you’ll get updated with everything that’s happened since your previous call. The downside to that feature is that the filter is maintaining state in the node, based on a filter ID. However, that ID is subject to garbage collection, and thus requires its own maintenance.

At the end of the day, a filter can be a very stable option for network data querying: after all, it’s a series of discrete requests, as opposed to a long-lived connection that may break or be interrupted.


What are subscriptions?

The other option, of course, is using the JSON-RPC pub/sub service. As opposed to filters, in which your dapp is actively requesting the information from the network, in a pub/sub scenario, your dapp is passively receiving the information as it is published. The data is essentially pushed from the node into your connection, once established. The pub/sub service is only available via WebSockets.

One thing to keep in mind about setting up your data querying through subscriptions is stability. If a websocket connection closes, the subscription is automatically closed and removed. Additionally, data received through subscriptions are stored in an internal buffer. If this buffer runs out of space, this will also cause the connection to be closed.

Another aspect to subscriptions is that they report current events. With filters, you got updated with “everything since the last time you called,” so to speak. That’s not the case with subscriptions, but this is a perfect example of choosing the method that best fits your use case.

Are you building a ticker reporting most recent events? Maybe a subscription is what you’re looking for.

Are you building an app that displays transaction histories? This might be the case for a filter.



Integrations with Infura


Whichever option fits your use case best, Infura is ready to help you query the network. If you’re looking for next steps or some examples, jump in with the documentation.



Examples


In the following examples we'll show how to watch for transfer events using both methods. We'll keep it at the HTTP JSON-RPC or WebSocket level without using any Web3 libraries.


This first example is a suboptimal way to process the latest block and get the transfer events from that block. For example, imagine this code in a loop, call eth_blockNumber to detect when we see a new block and do a subsequent eth_getLogs call based on this new block. This is prone to missing blocks depending on network latency, how accurately timed the loop is, and processing / P2P block catch ups the node may be doing internally.


const axios = require('axios');
const infuraUrl = "https://mainnet.infura.io/v3/<ProjectID>";
const payloadProto = {
jsonrpc: "2.0",
method: "",
params: [],
id: 1
};
(async () => {
// Let's get the latest block number
const blockPayload = Object.assign({}, payloadProto, { method: 'eth_blockNumber' })
const client = axios.create({
url: infuraUrl,
method: 'POST',
headers: { 'Content-Type': 'application/json'}
})
var resp = await axios({
url: infuraUrl,
method: 'POST',
data: blockPayload,
headers: { 'Content-Type': 'application/json' }
});
const blockNumber = resp.data
console.log(blockNumber)
// Get the Transfers events in this block
const logPayload = Object.assign({}, payloadProto, { method: 'eth_getLogs', params: [
{
fromBlock: Number(blockNumber),
toBlock: Number(blockNumber),
topics: ["0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"]
}
]})
resp = await axios({
url: infuraUrl,
method: 'POST',
data: logPayload,
headers: { 'Content-Type': 'application/json' }
})
for (var it of resp.data.result) {
console.log(it)
}
})();



Let's improve the code by using the eth_newBlockFilter and eth_getFilterChanges APIs. The benefit is that we can poll the API for changes, and network conditions don't matter, we could even stop this script and start it minutes later.


As long as we use a consistent filter ID, it will return changes from the last time we polled

the server. Since the filter ID can get garbage collected during high node usage, extra care is required to ensure the filter still exists.  You'll need to recreate the filter if it no longer exists.



const axios = require('axios');
const infuraUrl = "https://mainnet.infura.io/v3/<ProjectID>";
const payloadProto = {
jsonrpc: "2.0",
method: "",
params: [],
id: 1
};
(async () => {
// Start by getting a filter ID
// We are interested in getting new blocks, so we create a newBlockFilter
const newFilterPayload = Object.assign({}, payloadProto, { method: 'eth_newBlockFilter' })
const filterIdResponse = await axios({
url: infuraUrl,
method: 'POST',
data: newFilterPayload,
headers: {'Content-Type': 'application/json'}
})
const filterId = filterIdResponse.data.result
console.log(`Using filterId: ${filterId}`)
const newBlockPayload = Object.assign({}, payloadProto, { method: "eth_getFilterChanges", params: [filterId]})
const hash = "";
while (true) {
var newBlockResponse = await axios({
url: infuraUrl,
method: 'POST',
data: newBlockPayload,
headers: {'Content-Type': 'application/json'}
})
var hashes = newBlockResponse.data.result
if (hashes.length === 0) { continue }
// Since we get blockHashes back with this, the getLogs call changes slightly
hashes.map(async (hash) => {
const logByHashPayload = Object.assign({}, payloadProto, {method: 'eth_getLogs', params: [{
blockHash: hash,
topics: ["0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"]
}]})
const logResponse = await axios({
url: infuraUrl,
method: 'POST',
data: logByHashPayload,
headers: {'Content-Type': 'application/json'}
})
if (logResponse.data.result) {
console.log(`Found: ${logResponse.data.result.length} logs for Block: ${hash}`)
} else {
console.log(logResponse.data)
}
})
}
})();



We could further improve this by skipping the new blocks retrieval and simply create a new filter specifically on logs. This simplifies the polling:



const axios = require('axios');
const infuraUrl = "https://mainnet.infura.io/v3/<ProjectID>";
const payloadProto = {
jsonrpc: "2.0",
method: "",
params: [],
id: 1
};
(async () => {
// Like all filters start with getting a new Filter ID
// In this case we can just pass a the log params into the filter to specify the match.
// The node in this case will return the events associated with the `latest` block
const filterIdPayload = Object.assign({}, payloadProto, { method: 'eth_newFilter', params: [{
topics: ["0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"]
}]})
const filterResponse = await axios({
url: infuraUrl,
method: 'POST',
data: filterIdPayload,
headers: {'Content-Type': 'application/json'}
})
const filterId = filterResponse.data.result;
const filterChangePayload = Object.assign({}, payloadProto, { method: 'eth_getFilterChanges', params:[ filterId ]})
while(true) {
const filterLogResponse = await axios({
url: infuraUrl,
method: 'POST',
data: filterChangePayload,
headers: {'Content-Type': 'application/json'}
})
console.log(filterLogResponse.data)
}
})();



Now let’s try to get the same data by subscribing for logs using a WebSocket connection. This method returns logs that are included in newly imported blocks.


Please note that the WebSocket connection will get closed by the server after one hour of being idle (for example, no data coming over). Ensure you add a reconnect routine and also unsubscribe when the subscription is no longer needed. When subscribing to relatively silent contracts, you could also subscribe to newHeads which prevents your WebSocket connection going into idle.



const WebSocket = require('ws')
const ws = new WebSocket('wss://mainnet.infura.io/ws/v3/projectID);
ws.on('open', function open() {
//ws.send('{"jsonrpc":"2.0", "id": 1, "method": "eth_subscribe", "params": ["newHeads"]}');
ws.send('{"jsonrpc":"2.0", "id": 1, "method": "eth_subscribe", "params": ["logs", {"topics": ["0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"]}]}');
});
ws.on('message', function message(data) {
console.log('received: %s', data);
});

HTTPS Filters and WSS Subscriptions through Infura: Weighing the Advantages

You can now access a dedicated gateway to decentralized storage for your projects through the Infura IPFS API. A gateway allows applications, such as browsers, that do not natively support IPFS to access IPFS content. This is a new feature our team has released today in anticipation of our gradual deprecation of our public gateways in October.

Now you are able to create your own unique gateways, dedicated to only your projects. With this initial release, you can also create your own subdomain and restrict your view to show only content you have pinned. These features were previously not available when you accessed IPFS through the public gateway.

Our continued commitment to this technology is proof that we believe in it. A dedicated team is constantly working hard behind the scenes, continually improving the robustness, resilience and latency of our IPFS API, and shipping new features like this one to improve the usability of IPFS for all your decentralized storage needs.

Please see the bottom of this post for details of the Deprecation of the public gateway October 5th 2022


How to enable dedicated gateway:


Step 1: Go to your IPFS project’s general settings, where you will see a new section for Dedicated Gateway:

Step 2: Click the enable/disable toggle and you will see a box appear, where you can choose a unique name for your dedicated gateway:


Step 3: Type your chosen gateway name into the box and click “SAVE SUBDOMAIN”. Once you do, our system runs an automatic check, to ensure that this chosen name is unique.


If this name is unique, you will see a green box in the top right-hand corner, telling you that your project settings have been updated:


Step 4: Optional: Check the “Only pinned content” box, to restrict your gateway’s usage, such that the gateway only responds with content you have pinned to your project:


You are now ready to use this endpoint in your project!


 * If you wish to change the name of your project, you may do so by typing directly into the unique subdomain box.
 * Make sure that you remember to click the Save Project button. You will see the green success box, only with the updated name of your unique subdomain, in the Project Summary section, with all the project details.
 * You can rename your unique subdomain by typing directly into the box.
 * The dedicated gateway URL form is:
 *  https://$custom-subdomain.ipfs.infura-ipfs.io/ipfs/$CID/path/to/something
   
 * You have a maximum of 20 unique subdomains across all IPFS projects
 * You can return to a previously used subdomain
 * You can only have 1 active subdomain per project


Billing and future iterations


The dedicated gateway traffic will be billed at the same price as accessing IPFS via the Infura API:

 * 5GB of storage free
 * 5GB data transfer up free
 * 5GB data transfer down free

Anything above that limit will be charged at:

 * Unlimited storage at $0.08/GB
 * Unlimited data transfer at $0.12/GB

Currently, for this release the billing will not be split out into API and gateway traffic, on your Stats Dashboard nor your invoices. We will work on getting that split out very soon.

For more information, please refer to the Documentation, or contact support.


Deprecation of the public API and gateway


At Infura, we are constantly upgrading our systems to facilitate your building of Web3. As such, we have made vast improvements to the robustness and stability of our internal systems, and the next stage of this includes deprecating the public API and gateway. This will take place six months from now, on October 5th 2022.

Please ensure that, by the above date, you will have migrated your endpoints over to the authenticated API endpoints within your project settings, enabled the dedicated gateway, and changed your gateway endpoints at any place where you access the gateway within your IPFS dApps/code.


Remember, you can migrate your pins to the new IPFS service in three easy steps. Happy pinning!

Introducing your dedicated gateway to IPFS Web3 storage

ETHDenver 2022 truly revived the #BUIDL spirit for the Ethereum community. Here are insights into the challenges of scaling APIs from a panel with our Co-Founder and Chief Infrastructure Engineer, EG Galano.


If you attended #ETHDenver this year, you already know it was such a vibe, #thisisthegwei. This vibe was sorely missed during two years without IRL Ethereum events. As the largest and longest-standing Ethereum gathering, our expectations for the event this year were high, but more importantly, they were exceeded. ETHDenver 2022 truly revived the #BUIDL spirit within the community and has reminded us, when we build on Ethereum, we build for the greater good.


The Infura team was there in full force to reconnect with our community and welcome newcomers to Web3. Here is a complete list of all our events, one of which was a panel entitled, The challenges of scaling blockchain APIs. If you missed it, no worries.


Here is a summary of our learnings from Infura’s Co-Founder and Chief Infrastructure Engineer, EG Galano and fellow API builders Nader Dabit (Developer Relations Engineer, The Graph) and Temoc Weber (Co-Founder and CEO, Gateway.fm).


The challenges of scaling blockchain APIs


Building APIs is hard. Scaling them is even harder. We kicked off the panel with EG, asking him the most common barriers to scalability he’s seen as the first to provide an API solution for Ethereum after founding Infura in 2016.


“You can’t project growth. You can’t project traffic. Typically, when you’re building a project, [it’s] like a game. You know you’re going to launch in May and you can start to prepare. When you’re an infrastructure provider, you don’t have the ability to prepare. You have to make sure you’re architecting systems that can scale almost limitlessly,” said EG.


Choosing an API provider for asset perpetuity


Next, we discussed EG’s advice for running node infrastructure and API services. With so many options in the market, it was important to break down what developers should consider when choosing a service like Infura.


“Take a close look at the technologies you’re using and make sure there’s something like an API continuity plan. Is this API something that is going to continue servicing your users for many years in its current form? Is it going to change under your current application?” he explained.


EG went on to explain that he’s seen NFTs disappear, not because they weren’t on chain anymore, but because the API provider pivoted. Suddenly, NFT owners have to go through significantly more technical steps to regain access to their assets and migrate them to a space they can live in perpetuity. He went on to encourage developers to build responsibly to avoid this.


“As you're designing, keep in mind that our customers and the people consuming this content are going into it without understanding everything that’s holding it up. So, let’s build responsibly.”


Why Web3?


As we continued to delve into the challenges of scaling APIs for different use cases, I asked what drew each panelist to Web3 in the first place. EG’s response told the story of how Infura began.


“I’ve always worked in developer tools and [am] very close to developer-focused applications. It was in 2015 when a friend of mine introduced me to Ethereum,” he said.


EG later went on to meet Joe Lubin, Ethereum co-founder and ConsenSys CEO. He then joined ConsenSys whose mission was (and still is) to further the growth of Ethereum.


“I joined ConsenSys with no specific idea in mind except wanting to understand the problem space. Nothing really clicked until I met one of my co-founders who said, everyone in this space is super talented and extremely smart and they’re all having issues running their infrastructure. Coming from an infrastructure background, I felt like that was a place I could immediately contribute. There was latent demand for something like Infura. So we built it.”


Hybrid infrastructure as a new best practice


As the panel continued, the next important question was to try and understand how an API service could scale across multiple protocols. So many new layer one chains have launched in recent years: Solana, Avalanche, NEAR, and Cosmos to name a few. Perhaps the most interesting part of the panel came when each panelist started to discuss how their services could interoperate and create what EG defined as hybrid infrastructure; a best practice we established during the panel. Hybrid infrastructure is a method of building that involves multiple API solutions working together that increases network resilience and security, while encouraging decentralization.


“It doesn’t need to be a choice of just using Infura or just using Gateway. You have the opportunity, because we support an open standard for API, to use both,” said EG. “And have a structure in place that is more resilient than using just one provider.”


We went on to contextualize hybrid infrastructure within Moxie Marlinspike’s “My first impressions of Web3” piece, where the creator and co-founder of Signal Messaging calls out a reliance on the Infura API. EG quickly refuted this.


“A lot of applications use Infura. But none of them are solely dependent on Infura. And that’s a big difference.”


Final thoughts
You can watch the complete panel here to keep learning. We are grateful for the chance ETHDenver 2022 gave us to reconnect with our community and look forward to attending more events this year! Follow us on Twitter for updates on where we’ll be next.

News

The Challenges of Scaling Blockchain APIs

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.

Recent Posts (page 12)

Scaling Your DeFi Project - 3 Core Infura Features You Can Leverage

HTTPS Filters and WSS Subscriptions through Infura: Weighing the Advantages

Introducing your dedicated gateway to IPFS Web3 storage

The Challenges of Scaling Blockchain APIs

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