Skip to content

Commit af28318

Browse files
committed
Add disclaimer corresponding to incident-2002-usd1-aptos---invalid-dispatchable-operation
1 parent 290957b commit af28318

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

src/content/ccip/tutorials/aptos/destination/programmatic-token-transfers.mdx

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,12 @@ A programmatic token transfer combines the features of a token transfer and an a
5454

5555
### The `ccip_message_receiver` Module
5656

57+
<Aside title="Disclaimer" type="caution">
58+
The `ccip_message_receiver` module used in this tutorial **should only be used with non-dispatchable tokens**, as it
59+
is currently incompatible with [dispatchable
60+
tokens](https://aptosfoundation.org/currents/dispatchable-fungible-assets-101).
61+
</Aside>
62+
5763
This tutorial uses the `ccip_message_receiver` module from the `aptos-starter-kit`. Its `ccip_receive` function contains dispatcher logic. For this tutorial, we will trigger the part of its logic that handles a message containing both tokens and data.
5864

5965
- **Logic**: When the module receives both tokens and data, it interprets the `data` payload as the 32-byte address of a final recipient. It then uses its on-chain `signer` capability (derived from being deployed on a Resource Account) to transfer the tokens it just received to that final recipient address. Finally, it emits a `ForwardedTokens` event.

0 commit comments

Comments
 (0)