In the Wormhole Native Token Transfer (NTT) framework, Rate Limiting is a key feature. It sets a maximum transfer limit within a specific time window (default is 24 hours) to prevent malicious or abnormal large transfers, ensuring the safety of the multi-chain bridge.
When a transfer request exceeds the set rate limit, and the shouldQueue configuration is set to True, NTT will queue these requests and process them once the rate limit period expires. If set to False, the transfer will be immediately rejected. This ensures that even under high-load conditions, the system can process transfer requests in an orderly manner.
Let's go through the steps to configure Rate Limiting.
Updating Rate Limiting
To set or update the rate limits, you need to modify the NTT configuration file: deployment.json.
1.Pull Current Chain Configuration:
Use the ntt pull command to retrieve the current configuration from the blockchain:
2.Modify the Configuration File:
In the deployment.json file, find the configuration for the relevant chain, and add or modify the limits section. For example:
In this example:
●outbound: Sets the maximum amount that can be transferred out within a specified time window.
●inbound: Sets the maximum amount allowed to be transferred from specific chains.
3.Push Configuration Updates:
Use the ntt push command to push the updated configuration to the blockchain:
By following these steps, you can effectively manage Wormhole NTT's rate limits for multi-chain token transfers, ensuring the system's security and stability.
Example
The following is information from the deployment.json file in the project, which records the NTT Manager, Transceiver, Owner, and Token information.