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

Blockchain development can be complex. And no wonder—when working within a decentralized system operating on a set of complex protocols there are many factors you need to consider. Even for even the simplest of activities, you need to access blockchain nodes, check gas prices, pay for gas, sign transactions, and more.

Infura is a powerful suite of APIs and developer tools that abstracts away these complexities on the most popular blockchains, including Ethereum, Linea, Arbitrum, StarkNet, IPFS, and more. By using Infura, you can spend more time building your dapp, and less time worrying about details such as scalability and uptime.

This guide provides all the steps necessary to set up and get started using Infura. You’ll be able to set up an Infura API key, access the Ethereum (Sepolia) blockchain, and use Infura to build your dapp. By the end of this guide, you’ll see why leading dapps and tools such as MetaMask, Uniswap, and MakerDAO rely on the reliability, ease of use, and scale of Infura to power their ventures.


Prerequisites

To get started, you’ll need a one-time setup of some tools and software essential to creating and deploying your dapp.


Set up MetaMask

First, in order to conduct transactions on a blockchain (for example, deploying a contract or minting an NFT), you’ll need a crypto wallet.

Several options for wallets are available in the market, but we’ll use the most popular and easy to use, MetaMask. MetaMask is a self-custodial wallet that gives users full control over their crypto and transaction authorizations. MetaMask is available for free as a browser extension.

Once you install the extension, MetaMask will ask you to complete a series of simple steps to set up a wallet for you. In the process, you’ll receive a secret phrase for accessing and managing your wallet. Make sure you store this secret phase safely (ideally both in a digital and physical space), and never share this publicly. If someone learns your secret phrase, they can then steal the assets in your wallet. We recommend creating a separate wallet address for development purposes, where your valuable assets wont be stored.


Switch to the Sepolia test network

Once your wallet is set up, navigate to the top-right of the wallet window and click on Show/Hide Test Networks. After showing test networks, you’ll see the drop-down option for Sepolia. Switch your network from Ethereum mainnet to Sepolia test network.

If this is your first time using a wallet, you should see a balance of 0 SepoliaETH. We’ll fund this wallet in a later step.


Node.js and npm

We’ll use Truffle to create the foundation of your project. Truffle is an industry-leading Ethereum development environment that allows you to create, test, and deploy smart contracts to EVM-based blockchains.

To use Truffle, you need to first install Node.js and npm. You can install both on your local machine by following these instructions.

You can verify their successful installations using the command line. (Your version numbers might be different from what’s shown below.)

$ node -v

v16.13.0

$ npm -v

9.1.1


Step #1: Obtain an Infura API key

As mentioned earlier, Infura is a tool that gives you easy, fast, and reliable access to most major public blockchains and L2s, including Ethereum. Infura does this by giving you access to RPC endpoints. Think of RPC endpoints as API endpoints to which you can send requests. In order to access these endpoints, you’ll need an Infura API key.


Create an account

To get an API key, you’ll first need to sign up for an Infura account that is free. Once you’ve signed up, you’ll be taken to the dashboard. This dashboard allows you to complete a variety of tasks, such as:

 * Create new API Keys
 * View analytics
 * Access support and other helpful resources
 * Setup project security
 * Upgrade your plan and activate add-on networks
 * Get network endpoints for mainnet and testnets
 * And more


Create API key

From the dashboard, click Create New API Key. This will open a pop-up form. For network, choose Web3 API. You can name the project anything you want.



Once you click Create, Infura will create a new API key for you and redirect you to the key’s dashboard page. Navigate to the Endpoints page for your key. project.

On this page, you’ll see all the RPC endpoints that you can access. Under Ethereum endpoints, select the endpoint for Sepolia. The endpoint should be of the format https://sepolia.infura.io/v3/[YOUR API KEY].


After this step, we recommend that you add your own RPC endpoint to MetaMask by adding a new customer network. This will allow you to track your MetaMask requests directly from the Infura dashboard and understand what is happening in the backend when you send transactions from your MetaMask wallet.


Step #2: Set up your development environment

With a MetaMask wallet and an Infura RPC endpoint in hand, you can begin setting up your development environment using Truffle.


Initialize a Node.js project

First, let’s set up a Node project and install all necessary packages. Create an empty Node repository by running the following commands:

$ mkdir infura-project && cd infura-project

$ npm init -y

Next, install Truffle:

$ npm -g install truffle

Remember that we installed MetaMask so that we could pay for transactions conducted on the blockchain. You’ll need to give Truffle access to your wallet so it can perform that action on your behalf. For this, you’ll need another package: hdwallet-provider.

$ npm install @truffle/hdwallet-provider

You’ll be sharing your wallet secret phrase with your Truffle project. Under no circumstance do we want these secrets to ever be made public. You should never hard-code your secret phrase or credentials into your project. Instead, provide them through environment variables.

We’ll use dotenv  and gitignore to do this. This prevents you from being committed to version control systems and reduces the risk of accidental exposure when sharing code repositories like GitHub.

$ npm install dotenv

Touch .env 

Add your project keys here, and wallet address.

touch .gitignore

Next, add “.env” to make sure GitHub doesn’t include the file containing your keys publicly.


Create a Truffle project

Now, we can create a barebones Truffle project. Run the following command from within your Node.js project root folder:

$ npx truffle init

To ensure that everything works correctly, run the following command:

$ npx truffle test


Compiling your contracts...

===========================

> Everything is up to date, there is nothing to compile.

✓ Downloading compiler. Attempt #1.


  0 passing (1ms)

If you don’t receive any errors, you can proceed with your project. If you have any issues, check out the Truffle support and help page.

In your project, you should now see a contracts subfolder. Within this folder, let’s create an extremely simple smart contract in a file called Donations.sol. This contract does the following:

 1. Allow anyone to make a donation.
 2. Allow the owner of the contract to withdraw all the donations made.

The code Donations.sol should look like this:

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;

contract Donations {
  address public owner;

  constructor() {
    owner = msg.sender;
  }

  // Function to donate
  function donate() public payable {
    require(msg.value > 0, "Donation needs to be a positive value");
  }

  // Withdraw ether
  function withdraw() public payable {
    require(msg.sender == owner, "Only the owner can withdraw!");

    uint balance = address(this).balance;
    require(balance > 0, "No ether left to withdraw");

    (bool success, ) = (msg.sender).call{value: balance}("");
    require(success, "Transfer failed.");
  }
}

Compile the contract with the following command:

$ npx truffle compile


Compiling your contracts...

===========================

> Compiling ./contracts/Donations.sol

> Artifacts written to /home/user/infura-project/build/contracts

> Compiled successfully using:

   - solc: 0.8.20+commit.a1b79de6.Emscripten.clang


Configure Truffle and environment variables

Next, we’ll need a file to store our environment variables. This is where we’ll put your project secrets—namely, your MetaMask wallet secret phrase and the Sepolia RPC endpoint which contains your Infura API key.

In your project root folder, create a file called .env with the following information:

INFURA_ENDPOINT = "https://sepolia.infura.io/v3/<Your-API-Key>"

MNEMONIC = "<Your-MetaMask-Secret-Recovery-Phrase>"

Next, let’s inject this information and configure your Truffle project. Replace the contents of truffle.config.js with the following:

require('dotenv').config();

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

const { INFURA_ENDPOINT, MNEMONIC } = process.env;


module.exports = {

  networks: {

    development: {

      host: "127.0.0.1",

      port: 8545,

      network_id: "*"

    },

    sepolia: {

      provider: () => new HDWalletProvider(MNEMONIC, INFURA_ENDPOINT),

      network_id: '11155111',

    },

  },

  compilers: {

    solc: {

      version: "0.8.19",

    }

  }

};


Step #3: Deploy your smart contract to Sepolia

Now that we’ve configured our Truffle project and written the smart contract, we can deploy it to the Sepolia blockchain.


Use the Infura faucet to get some test SepoliaETH

Although we’ve set up your MetaMask wallet and configured it to use the Sepolia network, your wallet balance is still 0 SepoliaETH. In order to conduct any transactions—such as deploying your contract, making donations, and even retrieving donations—you’ll be required to pay gas. So, you’ll need some SepoliaETH in your wallet.

Since we’re deploying our contract to a test network (Sepolia), you can obtain these tokens for free through the Infura Sepolia faucet.

Once you’ve filled up your wallet, you should see a small SepoliaETH balance.



Deploy smart contract to Sepolia

In order to deploy your contract to Sepolia, we’ll write a script called 1_deploy_contract.js. Create the file in the migrations folder and paste in the following code:

const Donations = artifacts.require("Donations");


module.exports = async function (deployer) {

    try {

        // Deploy the Donations contract

        await deployer.deploy(Donations);


        // Get the deployed instance

        const donationsInstance = await Donations.deployed();


        console.log("Donations contract deployed at:", donationsInstance.address);

    } catch (error) {

        console.error("Error deploying the contract:", error);

    }

};

Then, deploy the smart contract:

$ npx truffle migrate --network sepolia

If all goes well, you should see output that looks something like this:

Compiling your contracts...

===========================

> Everything is up to date, there is nothing to compile.



Migrations dry-run (simulation)

===============================

> Network name:    'sepolia-fork'

> Network id:      11155111

> Block gas limit: 30000000 (0x1c9c380)


…


Starting migrations...

======================

> Network name:    'sepolia'

> Network id:      11155111

> Block gas limit: 30000000 (0x1c9c380)



1_deploy_contract.js

====================


   Deploying 'Donations'

   ---------------------

   > transaction hash:    0xab4650f9fb25379fcb7d95e18c42f3235069566da2cb75d5f654e7b9a5100f3b

   > Blocks: 0            Seconds: 20

   > contract address:    0xb658FB9c330381a059e8A14363F71fb7D4648f2A

   > block number:        3558024

   > block timestamp:     1685040444

   > account:             0x147A4cb54D7181222B7E10a91A492d5b4892b4aC

   > balance:             0.499121902496838849

   > gas used:            351239 (0x55c07)

   > gas price:           2.500000009 gwei

   > value sent:          0 ETH

   > total cost:          0.000878097503161151 ETH


Donations contract deployed at: 0xb658FB9c330381a059e8A14363F71fb7D4648f2A

   > Saving artifacts

   -------------------------------------

   > Total cost:     0.000878097503161151 ETH


Summary

=======

> Total deployments:   1

> Final cost:          0.000878097503161151 ETH


Congratulations! Your contract is now live! You can double-check this by searching for your contract address on Sepolia Etherscan.

You can also verify your contract on Etherscan by uploading the source code, which Etherscan will match and compare against the code on the blockchain. On the Etherscan page, click the Contract tab and then click Verify and Publish.

After this verification is complete, you’ll see the green check mark over the Contract tab.


Step #4: Send a transaction using MetaMask

Now let’s donate a small amount (0.001 ETH) to this contract. Navigate to the Contract tab and then to the Write Contract tab. Click on Connect to Web3.

This will open a modal to prompt you to connect to a wallet. Select your MetaMask wallet.

Once your wallet is connected, you can click donate. Enter an amount to donate (0.001), and then click Write.

Your MetaMask wallet will pop up, and you’ll be asked to confirm this transaction. Click Confirm.



After you’ve confirmed the transaction, you can view the transaction details. The list of transactions for the smart contract also shows the recent transaction.


And that’s it! With just a few clicks, you were able to make a donation through MetaMask on your smart contract. Every single step in the process was powered by Infura.


Step #5: Track smart contract activity on the Infura dashboard

To see the work done by Infura under the hood, you can check out the analytics associated with our Infura project. Navigate to the main Infura dashboard, find your project, and click View Stats.

If this is a project that you’ve just created, change the timeline to Last 1 Hour.

You will be able to see the number of requests made during that window.

You should also be able to see the specific requests made to the Sepolia Ethereum blockchain. On the surface, you’ve only made a few clicks, but hundreds of requests have been propagated to make what we wanted to do possible.

To also see your MetaMask transactions, you will need to update your MetaMask RPC endpoint by switching from the default MetaMask RPC to your Infura one.


Step #6: Start building

Infura simplifies your job as a blockchain developer by allowing you to connect to different blockchain networks without having to run your own nodes. This takes care of the scalability, uptime, and the reliability of your dapp so you can focus on the core logic of your business or product.

Now that you’re set up, let’s start building with the following resources:

 * How to Choose the Right Blockchain for your Application
 * The Developer’s Guide to the Web3 Stack
 * Full Stack Frontend using IPFS
 * Infura NFT API + SDK
 * Infura Help Center
 * Infura Discord

Stay up to update on all Infura product releases and news by following us on Twitter.

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

Today, we’re excited to announce that ConsenSys has acquired any.sender to join the Infura team! Any.sender is a team of two very talented engineers, Patrick McCorry and Chris Buckland, who built an Ethereum transaction relaying service that not only makes the transaction sending process much easier for developers and end-users, but also prevents them from overspending on network fees by actively managing the gas involved in sending their transactions.

We’re thrilled to welcome Pat and Chris into the Infura family and incorporate any.sender’s powerful relaying features into the Infura development suite. Infura has been actively working on improving the transaction experience for developers and the work the any.sender team has done will form the foundation of many Infura features that target solving this problem for developers.

Pat and Chris are thought leaders in the space, exceptional engineers, and generally great people. Adding them to the team instantly accelerates our efforts to provide the tools developers need to build on Ethereum and adds handsomely to our already industry leading development team.


Introducing Infura Transactions (ITX)

Infura Transactions (ITX) is a simplified way to send Ethereum transactions. Using ITX removes the need for developers to deal with the complexities around gas fee management.

Before ITX, developers had to:

 * Monitor the gas price market and pick a competitive fee, based on all transactions in the network’s pending pool
 * Keep track of account nonces
 * Manage their own transaction queue and make sure an earlier low-fee transaction doesn’t prevent later high-priority transactions from being mined
 * Make sure to re-publish low-fee transactions with a higher fee when network conditions change (failing to do so might get their transactions stuck indefinitely in a pending state, or dropped from the network pool).

Many developers today choose to overpay their gas fees in an attempt to minimize the likelihood of running into these issues, although the recent upsurge in Ethereum gas prices has made this approach increasingly inefficient. The real solution is using a specialized, reliable transaction infrastructure that authorizes, publishes and verifies that a transaction was indeed accepted into the blockchain.

With ITX, such an infrastructure is now available. Developers will be able to:

 * Send transactions without having to worry about setting the right gas price
 * Benefit from the ITX monitoring infrastructure that ensures transactions are re-published with competitive gas prices rather than getting stuck or dropped from the network pool
 * Submit transactions to Ethereum only once and pay the minimum gas possible required by the current network conditions to ensure transactions are successfully mined.
 * Pay for the gas of a transaction on behalf of their users.

The result of this service enables users to both have more reliable transactions and not overspend on the gas prices they typically use for making sure their transactions are mined.


How does it work?

ITX introduces three new RPC methods:

 * relay_sendTransaction: specifies a transaction to be created, signed and relayed by Infura.
 * relay_getTransactionStatus: returns the status of a relay transaction specified by its id
 * relay_getBalance: returns the balance of the user's ITX relaying account

These new methods allow users to send transactions to be relayed by ITX and monitor key functions of the system, including the status of the transaction, and the balance of their account (required to relay transactions).

There are three steps developers need to take when using ITX:

 1. On-chain deposit
    Relayed transactions via ITX can be paid for by depositing ETH with Infura’s on-chain deposit contract. This action credits the user’s gas tank with the corresponding amount of ETH. The ITX relay system is responsible for managing the user's gas tank.
 2. Send relay request
    When ITX receives a new transaction relay request from a respective user, it first checks if the user has a sufficient balance before locking a portion of their funds and then relaying the transaction on their behalf to the Ethereum network.
 3. Transaction mined & balance deducted
    As soon as the transaction is mined and becomes part of the blockchain, the cost of the transaction which includes the network fee (gas price * gas used) + the ITX fee, will be subtracted from the user's gas tank balance.

The Infura Transactions alpha release is available for testing on the Rinkeby network and will roll out to a small group of beta testers before the official public rollout in Q1, 2021.

If you’d like to be considered for early access to the feature, submit your request here. Once given access, the feature is easy to use - we’ve included a short walkthrough in our documentation portal.

Infura offers developers fast, reliable access to Ethereum and IPFS networks. Our Core service is free and provides everything developers need to build decentralized applications.

Twitter | Newsletter | Community | Docs | Contact

News

Announcing our acquisition of any.sender and the alpha release of Infura Transactions!

Deciding whether to run your own Ethereum node (or nodes), outsource your infrastructure to a Web3 provider like Infura, or deploy a hybrid node solution really depends on your API workload. To help developers evaluate their options, we’ve built Versus: an open source API benchmarking tool. Versus compares your API workload across different node implementations and Web3 providers so you can make data-based decisions.

Tests run using the Versus tool are 99% reproducible. In this post we step through a sample test to demonstrate how the tool works, and share the test parameters and results so others can follow the same method and reproduce them.


Getting Started

This project lives here. Simply grab the latest release binary for your platform, extract it, put it in your $PATH and you’re ready to roll.


How it Works

Versus is a command-line tool that reads lines of JSON-RPC requests from STDIN and concurrently sends them to multiple endpoints. It validates that the same results are returned, and compares the time to retrieve them, across each endpoint.

For example: let’s say we have a file queries.json with lines of the types of queries that our application performs:

$ cat queries.json

{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber"}

{"jsonrpc":"2.0","id":1,"method":"eth_getBalance","params" ["0x49318b3970C8a82275B440900bE45f27bf682108","latest"]}

{"jsonrpc":"2.0","id":1,"method":"eth_getCode","params":["0x2a0c0dbecc7e4d658f48e01e3fa353f44050c208","latest"]}




We can send those queries to our local node: `cat queries.json | versus "http://127.0.0.1:8545"


The results would be returned super fast. That's because these are fairly simple queries – and there are only three of them. If we want to run a few thousand queries, it’s going to take a bit more time. We can bump up the concurrency of versus with the --concurrency=20 flag. Add --verbose once or twice to get more output as the process is going.

We can also run the same queries against multiple endpoints at the same time:

$ export INFURA_API_KEY=”... grab this from your https://infura.io/dashboard”
$ cat many-queries.json | versus -vv --concurrency=50 \
"http://geth-node:8545" \
	"http://parity-node:8545" \
	"https://mainnet.infura.io/v3/${INFURA_API_KEY}"



Some responses may be mismatched, but that’s to be expected. Geth and Parity don’t always agree on the exact output that certain types of queries should generate. Note that Websocket support is not implemented yet - pull requests are welcome!


Generating Realistic Queries

Not many of us have a juicy many-queries.json sitting around on our hard drive - and even if we do, these queries get stale really fast. The performance of a node on queries that touch recently-mutated state will vary from state that is super old.

To generate realistic queries, we can use Ethspam - another handy open source tool. Ethspam generates an infinite stream of realistic queries, based on the typical pattern of RPC methods that Infura receives. It’s not perfect, but it’s very useful in combination with Versus. After grabbing a binary release, we can pipe it directly:

$ ethspam | versus -vv --concurrency=50 --stop-after=10000 \
"http://geth-node:8545" \
	"http://parity-node:8545" \
	"https://mainnet.infura.io/v3/${INFURA_API_KEY}"




Output

Below is an example of the output you can expect, once you’ve piped your query into Versus:

In this example, we’ve used Infura (Core Tier) as the Web3 provider, and a local “anonymous” node on an i3.xlarge EC2 instance, and ran a test to compare the two.


Results

In this test, the local node was quite limited. Despite many optimizations (high-IO storage, high memory with increased cache size, etc), requests were bottlenecked. By comparison, Infura’s concurrency proved to be unbounded (i.e., there was no limit to how many requests Infura could respond to, per second).
Some requests were very fast to serve from the local node, which resulted in a lower minimum latency time -- however, the average and maximum latency was significantly and consistently lower for requests through Infura (0.1291s standard deviation for Infura vs 3.2035s for the local node).


Key Learnings

 1. The mismatched responses presented above were predominantly due to the local node disagreeing with Infura about what the latest block number was. If Versus is run with the --verbose flag, it will print mismatched results. Ethspam included some queries that required an archival node to retrieve. Neither the local node nor the Infura Core plan had access to archive-tier data, so these particular results matched up;
 2. Ethspam input is random, which means that if you’re using Versus to compare separate runs, your results won’t be consistent. When comparing nodes, make a single Versus run against multiple endpoints. A single run will confirm that the results match. Only make multiple Versus runs against each single endpoint if you’re using the exact same input;
 3. When running Versus against a single node, make sure that node is fully synced and functional. Nodes like geth will happily respond with an empty non-error response, even when it’s not synchronized, without doing any actual work. Running simultaneously against a known functioning node helps ensure that results are not mismatched.
 4. When running with high concurrency, make sure there are enough samples to reach consistent performance. At minimum, we suggest at least x100 requests per unit of concurrency. Higher is better!


Get Testing!

Though Versus was built by Infura, it’s intended to be an impartial and open source project. We encourage ideas and pull requests from the Ethereum community that seek to make Versus a better, more objective tool that anyone can run.

You can start playing around with Versus now to compare different node implementations and Web3 providers. Compare a light node to a full node, compare different kinds of nodes against each other, or compare Infura against other Web3 providers in high load/concurrency situations.

Our hope is that developers will find Versus a useful tool to help them evaluate what’s out there and ultimately find the best solution to power their DApp.

Want more Web3 tools? Check out this post for open source tools that help you interact more seamlessly with IPFS. Ready to test out Infura? Sign up to start building for free!

Engineering

Compare Ethereum API Performance with Versus

JSON RPC, methods, calls, requests - what does it all mean?! When you start building a dapp on the Ethereum blockchain, you’re introduced to a host of new concepts, request methods and naming conventions to employ - it can be overwhelming. The Infura team are experts in web3 infrastructure. We build open source tools and materials to help more developers interact with Ethereum and IPFS. In this tutorial, we leverage the collective experience of our team to bring you an in-depth guide to reading and writing requests to the Ethereum blockchain, using Infura.


Key Terms and Concepts

Before jumping into the meat of this tutorial, let’s clarify some key terminology. Below is a list of important terms and their corresponding definitions that you need to get familiar with.


Request

A developer interacts with Infura by sending a request through JSON RPC either over HTTP or WebSocket; as a single request or as a batched array. Requests follow this format:

{"id":1234, "method": "eth_foo", "params":[...] }

Because you should be posting this to an endpoint that has your v3 key in it, we can always associate these requests with a key or a project.


Method

The method is essentially what function we are asking an Ethereum node to execute. This will either request data from the node, execute an EVM function and return a response, or transmit data to the Ethereum network (send a transaction). Currently there are 65 methods which are supported by the popular Ethereum clients (Geth, Parity, Besu, Nethermind):

The most commonly used methods are highlighted in bold and comprise the vast majority of Infura’s traffic:

These methods can be grouped into the following categories:

i) Block Data Related

 * eth_getBlockByHash: retrieves a block's details by its hash (a string representing the 32-byte hash of a block);
 * eth_getBlockByNumber: retrieves a block's details by its number (an integer block number, or the string "latest", "earliest" or "pending");
 * eth_blockNumber: retrieves the current block number.

These methods retrieve static data about a particular block in the blockchain. This data is contained in the blockchain headers and could include information like block number or transactions mined, for example.

ii) Per User (address) Data

 * eth_getTransactionCount: retrieves the nonce of an address (i.e: how many transactions have already been mined, per user, for that address). This is needed because when you go to send a new transaction, there’s a field called ‘the nonce’ which is intended to prevent you from accidentally rebroadcasting transactions and sending them out in an order that you didn’t intend.

This method retrieves the simple state data for addresses. It doesn’t matter whether that address is a user or a smart contract. Any address can have an ETH balance.

iii) Reading Existing Smart Contract Data

The concept of smart contracts, and interacting with them, is what makes Ethereum different from other blockchains. A smart contract is two things:

 1. It’s a bit of code, usually written in Solidity, that compiles down into byte code - which is understood by the Ethereum Virtual Machine (EVM);
 2. It’s a means of storage. Think of it as halfway between ‘disc storage’ and ‘ram.’

Below are the most common methods for interacting with smart contracts:

 * eth_call: retrieves a constant EVM method on a Smart Contract and is the primary way to retrieve already mined data from the blockchain about a particular smart contract;
 * eth_getLogs: retrieves events published by smart contract transactions. Smart contracts can emit logs that are really user defined, so when you’re creating this smart contract you can decide the format of these log events. These dapps can then see when your smart contract has emitted these events, and respond accordingly;
 * eth_getStorageAt: retrieves raw state storage for a smart contract;
 * eth_getCode: retrieves the compiled EVM code for a smart contract. There is no copy of a smart contract’s source code on the blockchain itself. So, for example, when you search an address on Etherscan and the verified code of that smart contract is returned, that all happens off chain.


Using eth_call

ERC20 is one standard for how developers can create a token. Almost all wallet software understands this standard, so if you want to create a token and make it easier for people to interact with it, ERC20 is a good place to start.
Eth_call is the most commonly used method for interacting with smart contracts, particularly ERC20 contracts. A typical eth_call request looks like this:

At first glance, it’s not clear what any of this information represents. Let’s break it down:

The "id":1 field is an identifier string which is set by the requester, and helps make sure the client and server are communicating in the same context.

The "jsonrpc":"2.0" field specifies the version of the protocol and must be exactly “2.0”, which the protocol expects.

The from field is the data requester, which could be any wallet address or smart contract. This field is optional.

The to field is always a smart contract. There are two ways to find out what that smart contract is:

 1. You can make a request on the blockchain using eth _getCode, but that would give you the compiled code. Unless you have tools to reverse-engineer the EVM byteCode, you’re not going to immediately know what that means.
 2. You can type the smart contract address into Etherscan.
    Searching Etherscan is the most common way to find out what type of smart contract you’re dealing with. Let’s take the smart contract address 0x6B175474E89094C44Da98b954EedeAC495271d0F and type it in to see what happens:

Etherscan tells us that this smart contract is for the ‘Dai Stablecoin (DAI)’. At this point, we also have the opportunity to inspect the original Solidity code for this contract and confirm that it’s verified:

Great! Now we know that this address represents an ERC20 contract.


Deep-Dive into ERC20

Created in 2015, ERC20 is a relatively simple token standard and the most common contract type on Ethereum. Within this standard, an ERC20 token has to implement the following functions:

 * function totalSupply() public constant returns (uint);
 * function balanceOf(address tokenOwner) public constant returns (uint balance);
 * function allowance(address tokenOwner, address spender) public constant returns (uint remaining);
 * function transfer(address to, uint tokens) public returns (bool success);
 * function approve(address spender, uint tokens) public returns (bool success);
 * function transferFrom(address from, address to, token uint) public returns (bool success).

At certain times, an ERC20 token also has to emit the following events:

 * event Transfer(address indexed from, address indexed to, uint tokens);
 * event Approval(address indexed tokenOwner, addressed indexed spender, uint tokens).

You can view the standard on GitHub for more detail about how these functions work and when to emit these events. For now, let’s try to request the balance for some of the DAI tokens.

We know that our address is 0xDfBaf3E4c7496DAd574a1B842bC85B402BDC298D.

We also know that the DAI contract address is 0x6B175474E89094C44Da98b954EedeAC495271d0F.

To query our balance using eth_call, we use the balanceOf function of the token contract. The JSON-RPC format expects eth_call to have a specific data field format that requires normalizing the contract function balanceOf to a short Function Selector. To do this, we take out the names and the type of inputs it takes, and take that as a string. We then run it through Ethereum’s sha3 keccak hash:

web3_sha3(“balanceOf(address)”)[0..4]-> 0x70a08231

The first four bytes of this hash comprise it’s 4-byte signature. We then take this 4-byte signature, pad it with zeros, add our address as an input and send the eth_call:

This is a hexadecimal number, padded to a 32-byte length with zeroes. If we want to, we can convert this output to a decimal number by using a hex-to-decimal converter. This would return the result 3.890227426645114e+24, which is scientific notation for 3.890227426645114 * 10^24. This is the contract’s balance of Dai in wei, a standard unit of 10^18.

So finally, divide 3.890227426645114 * 10^24 by 10^18, and ta-da! Now we know the balance of the wallet address 0xDfBaf3E4c7496DAd574a1B842bC85B402BDC298D in this contract is 3,890,227.426645114 Dai.


Sending Transactions

Eth_calls are commonly used to read data from a smart contract. But what if you want to write data to a smart contract?

Let’s say we wanted to call the transfer function. Again, we would need to normalize the function first. We take the string transfer(address to, uint tokens) and hash it to get the 4-byte signature. Again, we take that 4-byte signature, pad it with zeros, insert the address and the amount of tokens, and package this information into a data string. We then sign the transaction and send it using eth_sendRawTransaction.

At this point, nodes start broadcasting our transaction out to the rest of the network. Eventually a miner will get a copy of it, go through all their proof-of-work stuff, get lucky and find a hash that matches the proof-of-work and broadcast a block that contains our transaction. Every node that receives this block reads the transactions within it, re-executes them, and holds our ERC20 token transaction in the EVM to update.  

Gas is sent along with any other values, and is spent running the EVM code. The miner gets the block reward, plus all the gas spent in transactions. If you’d like to learn more about how Ethereum mining works, these EthHub docs are a great start.


Mined Transactions

When a transaction is mined, two important things happen: the on-chain Ethereum state is changed via contract interactions, and Event Logs are published for public viewing. Once the Event Logs are published, we can execute JSON-RPC requests for eth_getLogs to investigate what changed, relative to the events that we care about, and react to them.

For example: an event ticketing service that wants to issue off-chain tickets based on crypto payments, could use eth_getLogs to find payments to their address, and react to these events by processing some logic in their backend servers to issue tickets to users.


Using eth_getLogs

In the above sample request, we use the parameters "from block" and "to block" to specify the hexadecimal block number that we are interested in retrieving logs from. Note that if this information is omitted, the method will return information from "block 0" to "block latest" by default (the entire chain history) and that’s not ideal. Infura has a cap on requests of 10,000 events per query. Best practice is to request a single block, as we’ve done in this example, and do that for each mined block.

What this request is saying to the blockchain is “hey, I want event logs relating to address 0x6B175474E89094C44Da98b954EedeAC495271d0F emitted in block 0x91F37C (hexadecimal for block 9565052) that matches topics 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef, 0x000000000000000000000000ee25e1ba53c225d250861c8e5a9a3e0fe19c790e and  0x000000000000000000000000dfbaf3e4c7496dad574a1b842bc85b402bdc298d.

The response returned for this request is an array of events. In the example we’re using, only one event for one address matched the specified topics.

Topics

Topics are events emitted by smart contracts. If we take a look at the original DAI ERC20 Solidity contract again 0x6B175474E89094C44Da98b954EedeAC495271d0F, we can see two event signatures that could be associated with it:

 * 94    event Transfer(address indexed from, address indexed to, uint tokens);
 * 95    event Approval(address indexed tokenOwner, address indexed spender, uint tokens).

How do we find out which topic (event) it actually was? You guessed it: we have to create the Function Selector of the Event and take the hash of it. Let’s try the event on line 94:

web3.sha3('Approval(address,address,uint256)')

The resulting hash is 0x8c5be1e5ebec7d5bd14f71427d1e84f3dd0314c0f7b2291e5b200ac8c7c3b925. This doesn’t match the hash provided in the initial request response. Now let’s try the event on line 95 of the contract:

web3.sha3('Transfer(address,address,uint256)')

Bingo! The resulting hash is 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef, which matches the hash provided in the initial request response. Now we know that 0xddf25 is the Transfer event.


More Event logs

You might be wondering what the data provided in the request response means:

In this context, data refers to all the ‘non-indexed stuff’ that’s captured in the events. In our example, for the Transfer topic, data represents the number of tokens that were transferred. That is, that 0x41f900d25d6693623a6 or 19471.6949921 Dai tokens were transferred from ee25e1ba53c225d250861c8e5a9a3e0fe19c790e to dfbaf3e4c7496dad574a1b842bc85b402bdc298d.

This completes our investigation 🎉

View our developer documentation to explore different ways to interact with Infura to read and write Ethereum data. New to Infura? Sign up and get started for free!

Ethereum RPCs, Methods and Calls

Gitcoin is a place for freelance developers to work on Open Source projects in return for blockchain-based digital currencies. The platform regularly hosts virtual hackathons to bring developers from around the world together to work on themed blockchain ‘hacks’ and engage with some of the biggest companies in the industry.

In January, Gitcoin ran a two-week virtual hackathon dubbed Take Back the Web. The aim was to inspire developers to identify problems with the internet as we know it, and solve them by building blockchain-based solutions. At the end of the hackathon, every contributor had made something cool and the winners were awarded a bounty!

Hackers had 23 bounties to choose from across 9 Web3 companies. 448 hackers from around the world participated and worked in teams to submit 162 projects over the two weeks. Infura put up two bounties totalling $1000 in Eth. These bounties were created for developers with varying levels of experience - so it didn’t matter if you were new to blockchain development or were a seasoned Web3 pro, every developer had a shot at winning an Infura bounty.


The Infura IPFS Development Prize

The InterPlanetary File System (IPFS) is a protocol and peer-to-peer network for storing and sharing data in a distributed file system. IPFS uses content-addressing to uniquely identify each file in a global namespace connecting all computing devices. If this sounds foreign to you, don’t worry! The purpose of these projects is to make it easier for more developers to understand and build on decentralized protocols, so you should definitely read on and check out the projects below.

Infura offers an API that emulates working with a local IPFS node. To win this bounty, hackers had to use our API to create a dapp with a frontend that could be hosted on IPFS. The project had to be executed well, demonstrate high code quality and make the most novel use of our IPFS API.

And The Winner is…

@jmsofarelli! 🎉When you store (‘pin’) content on IPFS, that content becomes publicly viewable by anyone who knows the hash of that content. But some applications may need to regulate access to certain types of IPFS content in order to function. @jmsofarelli was awarded the IPFS Development Prize by enabling creators to pin their content to IPFS, sign and verify using uPort ID and register each item’s hash on the Ethereum network. By using Ethereum contracts to register these hashes and regulate access to them, this project helps solve the viewability problem.

Special Mentions

While there can only be one winner, we wanted to give a shout out to two great submissions that were also superb uses of the Infura IPFS API:  

 * 📣IPFS-FRBR by @cervoneluca is a  package to handle versioning on IPFS by means of FRBR categorization and Ethereum ERC721 contracts. It offers a solution for the always troublesome problem of software versioning, and combines IPFS storage with Ethereum ERC-721 NFT identifiers.
 * 📣WalletConnect is an interoperability standard for interaction with Ethereum wallets. @Abhimanyu121 created a WalletConnect integration for event management by combining smart contracts for event management with IPFS as the storage destination for a wallet’s tickets. This solution enables developers to store static assets in IPFS, which can always be accessed by a hash, removing the risk of having to rely on a central server.


Infura Ethereum API Optimization Prize

Each Ethereum network call costs money and can be vulnerable to network clogging. This prize challenged advanced developers to create tools for optimizing Ethereum API calls: either by reducing the number of eth_calls that a dapp makes, or by reducing the cost. Projects had to showcase improvements in dapp efficiency and hackers were encouraged to be as creative as possible.

And The Winner is…

@Destiner! 🎉The Ethereum network can become congested with transactions, making the network slower and more expensive to use. Applications can help alleviate congestion and increase their own performance by optimizing the way they request data from the network. One way to do this is through better smart contract design and adopting Solidity best practices. Another way is to batch static read calls together. We awarded this prize to @Destiner for their ethcall Javascript library. This library can be imported to allow batching transactions, thereby helping more developers optimize their API usage and improve the efficiency of their dapps.

Thank you to everyone who participated! Please check out the linked Github repositories and give ‘em a star. You can register for more Infura bounties at https://gitcoin.co/infura or subscribe to our newsletter to stay-up-to date.


Ready to Build?

If you and your fellow developers are eager to start building and want quick, reliable access to Ethereum and IPFS, check out this guide and get started for free with Infura: https://blog.infura.io/getting-started-with-infura-28e41844cc89/. You can also access excellent resources to help you learn dapp development by checking out Kauri’s recently released guide, or through the ConsenSys developer portal.

See you at the next hackathon! Infura will have folks attending EthDenver, EthLondon and EthCC so be sure to swing by the ConsenSys booth to meet the team and drop your feature requests.

Infura Blog | Community News and Announcements

Infura Community News and Announcements

Community

Taking Back the Web With Infura

Monerium Case Study

Many developers look to programmable decentralized platforms like Ethereum to build new financial products and services that remove friction for the end customer, decrease the cost of trade and increase access to credit. To deliver on these customer promises, FinTech applications like Monerium utilize smart contracts on the Ethereum network to store all the critical information necessary to manage a complex digital currency. These applications must be able to interact with those contracts by accessing and changing the information stored inside and are live 24/7. This means they require an ‘always on’ connection to networks like Ethereum.

We caught up with Gisli Kristjansson, co-founder and CTO of Monerium to learn more about the Monerium-Tradeshift collaboration to enable instant invoice settlement on the blockchain with regulated e-money - and why they chose Infura for their infrastructure needs.

Can you introduce Monerium, for those who aren’t familiar with the company?

Kristjansson: At Monerium, we believe that money should be accessible, secure and simple to transact. That is why we are bringing regulated fiat currency to the blockchain, where everything of value will be stored and transacted. Our customers are European businesses (specifically SMEs) but we'll be expanding into other jurisdictions and opening up our product to consumers over the next few years.

You partnered with Tradeshift to enable their customers to settle invoices on the blockchain using Monerium-issued e-money. Can you tell us more about that project?

Kristjansson: The goal of the project was to demonstrate the viability of using blockchains for real-world use cases. We wanted to demonstrate that it was possible to issue digital invoices for products and services, and settle them online without going through traditional payment intermediaries. Supply chain innovation partners like Tradeshift have the ability to create products and services where the entire flow of money becomes an if-then-else statement in their program logic. By partnering with Tradeshift, we could enable their customers to issue invoices on the blockchain, and settle them instantly using e-money issued by Monerium.

What drew you to Infura as the infrastructure solution for this project?


Kristjansson: Monerium has developed a cloud hosted issuance managing platform for e-money, essentially bridging traditional payment flows and blockchains. For this project, we needed a reliable connection to Ethereum to enable us to scale the supply of digital currency to reflect our customer holdings. Building reliable, production-grade infrastructure in-house would have required specialized knowledge and resources that we just didn’t have. Infura provided us with a standardized interface to Ethereum. That meant that we didn’t have to worry about the operation of blockchain nodes. Instead, we could focus all our attention and resources on building our product.

To see what other developers are building on Infura, head to our customers page and check out more stories from killer applications like MakerDAO, Lucidity, OpenZeppelin and Aragon.


Want your project featured? Drop us a message to share your story.


Case studies highlighting customer and partner success with Infura products and solutions.

Customer case studies highlighting customer and partner success with Infura products and solutions.

Posts by Talia Knowles-Rivas

Announcing our acquisition of any.sender and the alpha release of Infura Transactions!

Compare Ethereum API Performance with Versus

Ethereum RPCs, Methods and Calls

Taking Back the Web With Infura

Powering Invoice Settlement on the Blockchain With Regulated Digital Currency