Wormhole NTT Rate Limits: Returns, Events and Queues
When a Wormhole NTT transfer hits the rate limit, outbound calls revert or queue; inbound overflow queues by digest on the destination for later completion.
Uruguay Can Editorial

When a Wormhole Native Token Transfer (NTT) exceeds capacity, the EVM NttManager either reverts with NotEnoughCapacity or queues the outbound transfer, while inbound overflow queues on the destination; NTT enforces capacity on both sides.
The transfer call takes an amount, destination chain, recipient, refund address, shouldQueue flag and instructions. The NttManager checks the amount against current outbound capacity, which refills over the rate limit duration (24 hours by default). A Monad bridge route is a concrete example: its outbound queue sequence gives the integration a handle to show and manage a transfer waiting for capacity.
Outbound capacity determines whether the call reverts or queues
When the amount exceeds remaining outbound capacity, shouldQueue selects the result. With shouldQueue set to false, the call reverts with NotEnoughCapacity, carrying current capacity and the requested amount. With shouldQueue set to true, the call returns a queue sequence, emits OutboundTransferRateLimited with the sender, sequence, amount and current capacity, and emits OutboundTransferQueued.
Take a transfer for more than the available capacity. If you opt out of queueing, show the failure and let the user retry later. If you opt in, the sender’s tokens have already been taken and are held for that queued transfer. Store the sequence and surface it in the product: the sender can use it to track the transfer or call cancelOutboundQueuedTransfer to recover the tokens. Only that sender can cancel.
After the rate limit duration, the queued transfer can be sent with completeOutboundQueuedTransfer(sequence). Calling it too early reverts with a StillQueued error carrying the queue timestamp. The call returns a message sequence when completion succeeds.
When an incoming transfer exceeds the destination’s inbound capacity, the destination NttManager queues it by digest and emits InboundTransferQueued. The sender cannot opt out. Complete it on the destination with completeInboundQueuedTransfer(digest) after the wait. For a Monad bridge integration, handle this as a destination-side pending state, distinct from a source-side outbound queue.
- Branch on NotEnoughCapacity when queueing is off.
- When an outbound transfer queues, save and display its sequence.
- When the destination queues an inbound transfer, track its digest and completion state.
Questions integrators ask next
How do I read current outbound capacity before calling transfer?
Read getCurrentOutboundCapacity() on the source NttManager. Capacity can change before your transaction executes, so still handle NotEnoughCapacity.
Who can change NTT rate limits after deployment?
The NttManager owner can change outbound and inbound limits. Check the deployed manager’s owner and governance setup.
Do queued transfers need a fresh delivery fee on completion?
Outbound completion is payable and sends the transfer, so provide the required fee for that transaction. Inbound completion performs the destination-side release and is not payable.
How should the UI show a transfer queued on the destination side?
Show it as pending on the destination and retain its digest. The user cannot cancel it from the source; completion happens on the destination after the queue delay.