TLDR:
This guide focuses on the EVM Trader nodes: Ethereum, BNB Smart Chain, Polygon.
A Warp transaction is an integration of Chainstack and the high-speed bloXroute network. Warp transactions are designed to reduce transaction times and ensure efficient delivery to their destination.
Simply put, when a transaction is sent through a Trader node with Warp transactions endpoint, it is placed on an “expressway” for blockchain transaction propagation. This means that compared to sending transactions through a standard EVM node, a Warp transaction can reach validators much more quickly, significantly reducing transaction finalization time.
This article describes how to implement Warptransactions with Chainstack and popular Web3 libraries.
When a transaction is sent to a normal EVM node, it is propagated to all nodes within the blockchain network. It moves from node to node until a validator validates it or eventually reaches all nodes. Depending on network conditions, this process usually takes a few hundred milliseconds to a few seconds.
Check out how to test transaction propagation by reading Monitoring transaction propagation from node to mempool in EVM networks with Python.
Figure 1. A normal transaction propagation in a nutshell
A bloXroute distribution network (BDN), which can be found in more detail in the BDN Architecture, is a special network with a direct connection to a set of validators. The core of the BDN is a high-capacity, low-latency global network of servers optimized to propagate transactions and blocks quickly. In general, a transaction sent to the BDN will be delivered to a validator in an expedited manner.
Figure 2. Transaction propagation through BDN
According to their website, bloXroute’s BDN provides several benefits, including:
A Trader node with Warp transactions enabled is a hybrid of a normal EVM node and a BDN, combining the best of both worlds. In most circumstances, it behaves just like a normal EVM node. However, when it receives a transaction from the user, it immediately forwards the transaction to the closest bloXroute cloud API, which serves as the gateway to the BDN. The transaction does not follow the normal propagation process.
There are a few benefits of using Trader nodes with Warp transactions:
The Trader node transactions feature is available on the paid plans for the following protocols:
To deploy a Trader node, in the wizard select a Trader node > Warp transactions.
This is the gateway to your application.
A Warp transaction is a type of transaction that is dispatched to your node using the eth_sendRawTransaction RPC method. This method is a standard Ethereum procedure for transmitting transactions.
In this section, we will dive deeper into the process of sending Warp transactions using some of the most widely used Web3 libraries. We will provide examples for web3.js, ethers.js, web3.py, and ethClient.go.
web3.js is a library that allows you to interact with a local or remote Ethereum node using HTTP, IPC, or WebSocket. Here’s how you can send a Warp transaction using web3.js:
ethers.js is a complete Ethereum library and wallet implementation prioritizing compactness and simplicity. Here’s how you can send a Warp transaction using ethers.js:
web3.py is a Python library for interacting with Ethereum. It’s commonly used for scripting, back-end development, and server-side tasks. Here’s how you can send a Warp transaction using web3.py:
ethClient.go is a Go-based Ethereum client that allows you to interact with the Ethereum blockchain. Here’s how you can send a Warp transaction using ethClient.go:
This article has provided an in-depth look at the integration between Chainstack and bloXroute, the mechanics of Warp transactions, and how to execute Warp transactions using the most popular Web3 libraries.
Feel free to ping me on Twitter or Telegram if you have any questions.
TLDR:
This guide focuses on the EVM Trader nodes: Ethereum, BNB Smart Chain, Polygon.
A Warp transaction is an integration of Chainstack and the high-speed bloXroute network. Warp transactions are designed to reduce transaction times and ensure efficient delivery to their destination.
Simply put, when a transaction is sent through a Trader node with Warp transactions endpoint, it is placed on an “expressway” for blockchain transaction propagation. This means that compared to sending transactions through a standard EVM node, a Warp transaction can reach validators much more quickly, significantly reducing transaction finalization time.
This article describes how to implement Warptransactions with Chainstack and popular Web3 libraries.
When a transaction is sent to a normal EVM node, it is propagated to all nodes within the blockchain network. It moves from node to node until a validator validates it or eventually reaches all nodes. Depending on network conditions, this process usually takes a few hundred milliseconds to a few seconds.
Check out how to test transaction propagation by reading Monitoring transaction propagation from node to mempool in EVM networks with Python.
Figure 1. A normal transaction propagation in a nutshell
A bloXroute distribution network (BDN), which can be found in more detail in the BDN Architecture, is a special network with a direct connection to a set of validators. The core of the BDN is a high-capacity, low-latency global network of servers optimized to propagate transactions and blocks quickly. In general, a transaction sent to the BDN will be delivered to a validator in an expedited manner.
Figure 2. Transaction propagation through BDN
According to their website, bloXroute’s BDN provides several benefits, including:
A Trader node with Warp transactions enabled is a hybrid of a normal EVM node and a BDN, combining the best of both worlds. In most circumstances, it behaves just like a normal EVM node. However, when it receives a transaction from the user, it immediately forwards the transaction to the closest bloXroute cloud API, which serves as the gateway to the BDN. The transaction does not follow the normal propagation process.
There are a few benefits of using Trader nodes with Warp transactions:
The Trader node transactions feature is available on the paid plans for the following protocols:
To deploy a Trader node, in the wizard select a Trader node > Warp transactions.
This is the gateway to your application.
A Warp transaction is a type of transaction that is dispatched to your node using the eth_sendRawTransaction RPC method. This method is a standard Ethereum procedure for transmitting transactions.
In this section, we will dive deeper into the process of sending Warp transactions using some of the most widely used Web3 libraries. We will provide examples for web3.js, ethers.js, web3.py, and ethClient.go.
web3.js is a library that allows you to interact with a local or remote Ethereum node using HTTP, IPC, or WebSocket. Here’s how you can send a Warp transaction using web3.js:
ethers.js is a complete Ethereum library and wallet implementation prioritizing compactness and simplicity. Here’s how you can send a Warp transaction using ethers.js:
web3.py is a Python library for interacting with Ethereum. It’s commonly used for scripting, back-end development, and server-side tasks. Here’s how you can send a Warp transaction using web3.py:
ethClient.go is a Go-based Ethereum client that allows you to interact with the Ethereum blockchain. Here’s how you can send a Warp transaction using ethClient.go:
This article has provided an in-depth look at the integration between Chainstack and bloXroute, the mechanics of Warp transactions, and how to execute Warp transactions using the most popular Web3 libraries.
Feel free to ping me on Twitter or Telegram if you have any questions.