How to set up an account

To start using the GetBlock node connection services for building a decentralized application (dApp), an account should be registered and customized. It only takes a few clicks!

Step 1. Signing up to GetBlock

Please, select a preferred sign-up option:

• Connect wallet. By choosing this option, you are not required to share your email address and create a new password. If you do not currently have a wallet browser extension, you will be asked to install the extension.
• Sign in with Google. Google will share your name, email address, language preference, and profile picture with getblock.io.
• Sign up with email. You will be asked to provide your name and email address. Should you choose the first option, you’ll be asked to verify the email address you entered.

Note that to start using our service you will be asked to accept our Terms of Service and Privacy Policy.

Step 2. Check your user ID.

Find your user ID located in the ‘Account Settings’ section. Please use it when contacting GetBlock’s team so we can identify your account and help you faster.

Step 3. Choose your way to interact with blockchain

With shared nodes, users can access peer-shared node infrastructure. This option is perfect for early-stage decentralized applications.

• Access to 50+ chains
• Rate limit: 200 requests/sec
• Pay-per-use options available

Dedicated nodes as a private service hosted by GetBlock guarantee simple integration of Web3 development solutions and seamless launching of all kinds of dApps. Endpoints for dedicated nodes are not charged from the account balance.

• No rate limits (1000+ requests/sec depending on a blockchain)
• 99.9% availability
• Custom settings

Select an API interface you want to use to interact with the blockchain in the dropdown next to each endpoint. Several API interfaces (JSON-RPC, REST, WS, etc) are available depending on the protocol.

Step 4. Create shared node or dedicated node endpoints

Sign in to your account. You will see a basic dashboard with your endpoints and general statistics. With your GetBlock account, you can create an unlimited number of endpoints for your shared nodes and dedicated nodes.

1. To create a shared node endpoints, navigate to ‘Dashboard’ and scroll down to ‘My Endpoints’ section. Select a protocol, the network, and a desired API. Add as many access tokens to this protocol as you need. Your balance of requests for shared nodes is distributed on all projects marked with the ticker ‘Shared nodes’.
2. To create a dedicated node endpoint, switch over to the ‘Dedicated Nodes’ tab. Select a protocol and an available network. Click on ‘Get’ to proceed with configuring a dedicated node from the window that pops up. You can add more dedicated nodes following these steps. Add as many access tokens for each dedicated node as you need.

Next to each protocol or dedicated node, you will find an associated configuration file. Expand the endpoint to see all the access tokens generated for the protocol.

Step 5. Get to know Subscriptions for shared nodes

GetBlock connects customers’ apps to 50+ blockchain RPC nodes.

Every time your software (wallet, dApp, crypto exchange, etc.) interacts with blockchains via GetBlock infrastructure, the interaction is called “request”. For instance, you can request the blockchain to demonstrate block details by hash, to display account balance by its address, and so on.

In order to start sending requests to GetBlock’s shared nodes, users can choose between “Start” subscriptions (with a limited number of requests) and “Unlimited” ones. Also, Free plan with 40,000 requests in 24 hours are available.

On paid subscriptions, users can purchase from 5 to 100 mln requests per month. Unused requests can be transferred to the next period once the subscription for this period is activated.

For instance, if Alice pays for a one-month subscription with 50 mln requests on Oct.10, it expires on Nov.10. If she doesn’t use all of the 50 mln requests, the remaining ones become available once she pays for the next period.

Also, if she decides that 50 mln requests are not enough for her goals, she can purchase additional packages in her dashboard.

Users can pay for subscriptions with fiat via Puddle; recurrent payments are set by default to automate the process of payments. Also, customers can top up accounts with crypto via Coinbase; one-time payments are available. If the balance of the card is insufficient, GetBlock attempts to top up the account one more time in three days before freezing the requests.

Here is the calculation that helps to determine the time during which the whole amount of requests from the “Start” subscription will be spent at a maximum capacity set to 200 requests per second (RpS):

• 5,000,000 requests / (200 RpS * 60 sec) = 416 min (or 6 hrs 57 min);
• 10,000,000 requests / (200 RpS * 60 sec) = 833 min (or 13 hrs 53 min);
• 50,000,000 requests / (200 RpS * 60 sec) = 4166 min (or 69 hrs 27 min);
• 100,000,000 requests / (200 RpS * 60 sec) = 8332 min (or 138 hrs 54 min).

The ‘Unlimited’ plan users are given access to an infinite number of requests with unrivaled bandwidth of 300 RpS on all shared nodes for 1, 3, 6, 9 or 12 months.

To interact with shared nodes, select the required protocol and network, click ‘Get’, and receive your endpoint address and API token in a matter of a few seconds.

Note that your balance of requests for shared nodes is distributed on all endpoints added under the ‘Shared nodes’ tab.

Step 6. Configure a dedicated node

You can configure a dedicated node by following an easy step-by-step process, which starts with selecting a protocol you want to deploy:

All you have to do next is choose a plan (an available discount is applied automatically) and set up your privately tailored API endpoint.

Pay for your dedicated nodes via the GetBlock account or select a customer support option if necessary.

Step 7. Study GetBlock documentation

Dive deeper into how GetBlock works, which methods it uses and how the blockchain node provider interacts with the nodes.

Step 8. Creating a request to a node

To get connected to the blockchain node, copy an endpoint that includes an access token from your dashboard or retrieve the config file and import it into your App.

Ensure the secure storage of your access tokens. If compromised, an access token can easily be rolled or deleted. Press the '...' button next to the compromised endpoint and select the desired option.

You have the option to download configuration files for each protocol individually. These files will include all your access tokens for a specific endpoint in both JSON and JS formats. To obtain all the access tokens in one go, simply click the file icon next to 'My Endpoints.'

You can set up multiple access tokens for a selected blockchain or dedicated node if needed.

You can also download the Postman GetBlock’s collection to test our service.

Once the connection is established, the user can check the history of their requests.

Additionally, the user can access their connection with the command line interface (CLI). For instance, here’s how the height of the Binance Smart Chain (BSC) mainnet is verified by GetBlock CLI.

Step 9. Checking the requests statistics

To check the statistics, head to the ‘My Endpoints’ section and switch to the ‘Statistics’ tab. You can customize the data view by parameters or by token using the dropdown menu.

Select the time period, a blockchain name, networks, and APIs to analyze the data.

All the information on the number of requests, response status, method calls, and rate limits rejection will be displayed in the form of infographics.

Stay tuned for more updates and announcements directly from GetBlock’s team.