Learn how to manage your master wallets
In a nutshell
To leverage Blockradar’s wallet infrastructure and enable seamless deposits and payments for your customers, you need to create at least one master wallet.
Master wallets are the backbone of most actions you can carry out with the Blockradar API. These wallets let you manage stablecoin deposits across multiple blockchains supported by Blockradar. To view the list of supported blockchains and assets on Blockradar.
When you create a master wallet for a specific blockchain, it allows you to manage everything related to that blockchain with the master wallet:
The creation of a master wallet requires four steps:
One dedicated address generated via any of these master wallets can be used to receive deposits on all other blockchain master wallets, provided the blockchains have isEvmCompatible: true
.
This means you can issue your customers a single unique address that can be used to deposit stablecoins on multiple blockchains, without worrying about them sending stablecoins to the wrong blockchain.
To create a master wallet, go to the dashboard, navigate to the wallets section, and create a wallet to start building a seamless experience for your customers.
The Blockradar dashboard provides a simple, user-friendly interface for generating master wallet.
This screenshot demonstrates the process of generating a new master wallet via the Blockradar dashboard. This method is ideal for manual address creation or for teams who prefer a graphical interface.
Environment
Wallets created in the live environment are isolated to that environment. The same applies to wallets created in the test environment, including the dedicated addresses created for your customers.
Blockradar master wallets support two key configuration options to help you manage funds and user experience: Auto Sweeping and Gasless Transactions.
Enable
When enabled, funds deposited to addresses under this wallet will be automatically swept (transferred) to the master wallet. This helps consolidate balances, improves security, and simplifies fund management.
Threshold
Set the minimum balance required for each child address to trigger auto-sweeping. If left empty, any amount received will trigger an auto-sweeping. This allows you to control how frequently sweeping occurs and optimize for gas fees.
The auto-sweeping
and threshold
settings on the addresses level will override the master wallet’s configuration for that address. This allows for granular control over auto-sweeping behavior per address.
Best Practice:
Enable auto sweeping and set an appropriate threshold to balance between timely fund consolidation and minimizing transaction fees.
Configure when the master wallet should cover gas fees for withdrawals from child addresses.
Enable Gasless Withdrawals
When enabled, gas fees for qualifying withdrawals will be paid by the master wallet, providing a seamless experience for your users.
Threshold Settings
Set the amount threshold for gasless withdrawals. Only transactions that meet this threshold will have their gas fees covered by the master wallet.
You can specify the threshold logic using arithmetic operators:
Operator | Description | Example (Threshold = 100) |
---|---|---|
gt | Greater than | Only withdrawals > 100 |
gte | Greater than or equal to | Only withdrawals ≥ 100 |
lt | Less than | Only withdrawals < 100 |
lte | Less than or equal to | Only withdrawals ≤ 100 |
eq | Equal to | Only withdrawals = 100 |
false
by default and threshold settings are set to 0.The enable gasless transaction
and threshold
settings on the addresses level will override the master wallet’s configuration for that address. This allows for granular control over gasless withdrawal behavior per address.
Best Practice:
Enable gasless withdrawals and set appropriate threshold logic to balance user experience and operational costs.
Funding a master wallet is essential for paying the gas fees on the blockchain when auto-sweeping
stablecoins from the dedicated addresses to the master wallet and for withdrawals to external wallets.
For the live environment, you can send assets from any wallet or exchange that supports the native assets on each of the blockchains.
Sweeping
Always ensure you have enough balance in your master wallet to avoid delays in auto-sweeping or withdrawals. We will notify you when your master wallet balance is low.
Understanding the differences in gas fees between test and live environments is crucial for efficient development and deployment.
In test environment, gas fees are minimal. Testnets are designed to simulate the mainnet environment without the associated real-world costs. As a result, small amounts of gas tokens in a testnet can be used for an extended period. This allows developers to test and iterate their integration without incurring significant expenses.
In a test environment, gas fees represent real-world expenses. These costs can vary significantly based on the blockchain and network congestion. Properly estimating and managing gas fees is essential to ensure the smooth operation of your applications and to avoid excessive costs.
By leveraging testnets for development and testing, you can minimize expenses and ensure your solutions are robust before deploying to the mainnet.
In rare cases, you might not receive a webhook from our system after a customer sends stablecoins to any of the addresses issued to them. We have an deposit finder mechanism built internally, but you also have the ability to trigger a rescan of the blockchain for a missing transaction using the Deposit Finder API by providing the transactionHash
Body parameters
The required parameter is transactionHash
, which can be obtained from either the original transaction record or by looking up the transaction on the blockchain explorer.
Happy hacking! ❤️
Learn how to manage your master wallets
In a nutshell
To leverage Blockradar’s wallet infrastructure and enable seamless deposits and payments for your customers, you need to create at least one master wallet.
Master wallets are the backbone of most actions you can carry out with the Blockradar API. These wallets let you manage stablecoin deposits across multiple blockchains supported by Blockradar. To view the list of supported blockchains and assets on Blockradar.
When you create a master wallet for a specific blockchain, it allows you to manage everything related to that blockchain with the master wallet:
The creation of a master wallet requires four steps:
One dedicated address generated via any of these master wallets can be used to receive deposits on all other blockchain master wallets, provided the blockchains have isEvmCompatible: true
.
This means you can issue your customers a single unique address that can be used to deposit stablecoins on multiple blockchains, without worrying about them sending stablecoins to the wrong blockchain.
To create a master wallet, go to the dashboard, navigate to the wallets section, and create a wallet to start building a seamless experience for your customers.
The Blockradar dashboard provides a simple, user-friendly interface for generating master wallet.
This screenshot demonstrates the process of generating a new master wallet via the Blockradar dashboard. This method is ideal for manual address creation or for teams who prefer a graphical interface.
Environment
Wallets created in the live environment are isolated to that environment. The same applies to wallets created in the test environment, including the dedicated addresses created for your customers.
Blockradar master wallets support two key configuration options to help you manage funds and user experience: Auto Sweeping and Gasless Transactions.
Enable
When enabled, funds deposited to addresses under this wallet will be automatically swept (transferred) to the master wallet. This helps consolidate balances, improves security, and simplifies fund management.
Threshold
Set the minimum balance required for each child address to trigger auto-sweeping. If left empty, any amount received will trigger an auto-sweeping. This allows you to control how frequently sweeping occurs and optimize for gas fees.
The auto-sweeping
and threshold
settings on the addresses level will override the master wallet’s configuration for that address. This allows for granular control over auto-sweeping behavior per address.
Best Practice:
Enable auto sweeping and set an appropriate threshold to balance between timely fund consolidation and minimizing transaction fees.
Configure when the master wallet should cover gas fees for withdrawals from child addresses.
Enable Gasless Withdrawals
When enabled, gas fees for qualifying withdrawals will be paid by the master wallet, providing a seamless experience for your users.
Threshold Settings
Set the amount threshold for gasless withdrawals. Only transactions that meet this threshold will have their gas fees covered by the master wallet.
You can specify the threshold logic using arithmetic operators:
Operator | Description | Example (Threshold = 100) |
---|---|---|
gt | Greater than | Only withdrawals > 100 |
gte | Greater than or equal to | Only withdrawals ≥ 100 |
lt | Less than | Only withdrawals < 100 |
lte | Less than or equal to | Only withdrawals ≤ 100 |
eq | Equal to | Only withdrawals = 100 |
false
by default and threshold settings are set to 0.The enable gasless transaction
and threshold
settings on the addresses level will override the master wallet’s configuration for that address. This allows for granular control over gasless withdrawal behavior per address.
Best Practice:
Enable gasless withdrawals and set appropriate threshold logic to balance user experience and operational costs.
Funding a master wallet is essential for paying the gas fees on the blockchain when auto-sweeping
stablecoins from the dedicated addresses to the master wallet and for withdrawals to external wallets.
For the live environment, you can send assets from any wallet or exchange that supports the native assets on each of the blockchains.
Sweeping
Always ensure you have enough balance in your master wallet to avoid delays in auto-sweeping or withdrawals. We will notify you when your master wallet balance is low.
Understanding the differences in gas fees between test and live environments is crucial for efficient development and deployment.
In test environment, gas fees are minimal. Testnets are designed to simulate the mainnet environment without the associated real-world costs. As a result, small amounts of gas tokens in a testnet can be used for an extended period. This allows developers to test and iterate their integration without incurring significant expenses.
In a test environment, gas fees represent real-world expenses. These costs can vary significantly based on the blockchain and network congestion. Properly estimating and managing gas fees is essential to ensure the smooth operation of your applications and to avoid excessive costs.
By leveraging testnets for development and testing, you can minimize expenses and ensure your solutions are robust before deploying to the mainnet.
In rare cases, you might not receive a webhook from our system after a customer sends stablecoins to any of the addresses issued to them. We have an deposit finder mechanism built internally, but you also have the ability to trigger a rescan of the blockchain for a missing transaction using the Deposit Finder API by providing the transactionHash
Body parameters
The required parameter is transactionHash
, which can be obtained from either the original transaction record or by looking up the transaction on the blockchain explorer.
Happy hacking! ❤️