TLDR:
Blast is an EVM-compatible L2 protocol with a major modification—ETH and stablecoins bridged over to the Blast network yield natively.
As an example of what this means—if you have your ETH on your address on the Blast network and do nothing, your ETH balance will grow (rebase positively, to be more technical) over time.
Check out the Blast documentation to understand where the yield is coming from.
For the purposes of this tutorial, we focus purely on the technical part.
There are a few precompiled contracts on Blast that make the network tick. For the full list, see Blastdocs: Contracts.
The ones that provide native yield generation are:
Inspecting these contracts will reveal that each of them has the same yieldMode
setting:
You can write this setting with the configure(YieldMode yieldMode
function:
This means that every USDB or WETH token on the Blast network has a yield mode assigned to it:
AUTOMATIC
— default mode; your USDB or WETH token rebases positively.
VOID
— your USDB or WETH token does not rebase or accrue claimable yield.
CLAIMABLE
— your USDB or WETH token does not rebase but accrues claimable yield separately.
ETH or stablecoins bridged to the Blast network get assigned the default AUTOMATIC
yield mode.
Users can manually set any other (VOID
or CLAIMABLE
) mode to their assets by calling the configure(YieldMode yieldMode
on each of the contracts.
This is all we need to know. This seems like checking the live addresses as they interact on the Blast network for the yield mode setting might raise a flag if it’s non-default and could be useful. And this is what we are going to do in this simple tutorial.
We will do a Python script that:
from
.All of the code is in the GitHub repository.
Log in to your Chainstack account and get a node endpoint.
Since the both the USDB and the WETH contracts are almost the same, we are going to use the same common ABI for both of them.
Let’s first do a script that identifies and prints all active accounts in each new block that have one of the three settings: AUTOMATIC
, VOID
, CLAIMABLE
.
We’ll do this to make sure the script works as expected.
where
rps=25
— an RPS setting to make sure you stay within the limits.Running the script will reveal that an overwhelming majority of accounts interact with on the network with the default automatic yield setting.
Let’s modify the script to only print the VOID
and CLAIMABLE
accounts, which would be a decent enough flag for non-ordinary accounts.
This tutorial guided you through creating a simple Python project that tracks and flags accounts as they come live that have a very uncommon yield mode setting.
TLDR:
Blast is an EVM-compatible L2 protocol with a major modification—ETH and stablecoins bridged over to the Blast network yield natively.
As an example of what this means—if you have your ETH on your address on the Blast network and do nothing, your ETH balance will grow (rebase positively, to be more technical) over time.
Check out the Blast documentation to understand where the yield is coming from.
For the purposes of this tutorial, we focus purely on the technical part.
There are a few precompiled contracts on Blast that make the network tick. For the full list, see Blastdocs: Contracts.
The ones that provide native yield generation are:
Inspecting these contracts will reveal that each of them has the same yieldMode
setting:
You can write this setting with the configure(YieldMode yieldMode
function:
This means that every USDB or WETH token on the Blast network has a yield mode assigned to it:
AUTOMATIC
— default mode; your USDB or WETH token rebases positively.
VOID
— your USDB or WETH token does not rebase or accrue claimable yield.
CLAIMABLE
— your USDB or WETH token does not rebase but accrues claimable yield separately.
ETH or stablecoins bridged to the Blast network get assigned the default AUTOMATIC
yield mode.
Users can manually set any other (VOID
or CLAIMABLE
) mode to their assets by calling the configure(YieldMode yieldMode
on each of the contracts.
This is all we need to know. This seems like checking the live addresses as they interact on the Blast network for the yield mode setting might raise a flag if it’s non-default and could be useful. And this is what we are going to do in this simple tutorial.
We will do a Python script that:
from
.All of the code is in the GitHub repository.
Log in to your Chainstack account and get a node endpoint.
Since the both the USDB and the WETH contracts are almost the same, we are going to use the same common ABI for both of them.
Let’s first do a script that identifies and prints all active accounts in each new block that have one of the three settings: AUTOMATIC
, VOID
, CLAIMABLE
.
We’ll do this to make sure the script works as expected.
where
rps=25
— an RPS setting to make sure you stay within the limits.Running the script will reveal that an overwhelming majority of accounts interact with on the network with the default automatic yield setting.
Let’s modify the script to only print the VOID
and CLAIMABLE
accounts, which would be a decent enough flag for non-ordinary accounts.
This tutorial guided you through creating a simple Python project that tracks and flags accounts as they come live that have a very uncommon yield mode setting.