From cfa807d9dc94235160752361e0fe106b8cea12e8 Mon Sep 17 00:00:00 2001 From: ben-weinberg Date: Tue, 10 Sep 2024 10:30:00 -0400 Subject: [PATCH] feat: update description of msg.sender for token manager (#1147) Co-authored-by: Stephen Fluin Co-authored-by: Marty <149421156+ffe9f8@users.noreply.github.com> --- .../dev/send-tokens/interchain-tokens/token-manager.mdx | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/pages/dev/send-tokens/interchain-tokens/token-manager.mdx b/src/pages/dev/send-tokens/interchain-tokens/token-manager.mdx index c97449b40..a105d46ae 100644 --- a/src/pages/dev/send-tokens/interchain-tokens/token-manager.mdx +++ b/src/pages/dev/send-tokens/interchain-tokens/token-manager.mdx @@ -1,6 +1,6 @@ # Token Managers -[Token Managers](https://github.com/axelarnetwork/interchain-token-service/blob/main/contracts/token-manager/TokenManager.sol#L22) are contracts that facilitate the connection between your interchain token to the Interchain Token Service (ITS). The manager is the `msg.sender` of the transactions being executed on the token while it is being bridged. +[Token Managers](https://github.com/axelarnetwork/interchain-token-service/blob/main/contracts/token-manager/TokenManager.sol#L22) are contracts that facilitate the connection between your interchain token to the Interchain Token Service (ITS). For certain manager types, such as `mint/burn` Token Manager, the manager is the `msg.sender` of the transaction being executed on the destination chain for the token when it is bridged in. ## Token Manager Types There are different [types](https://github.com/axelarnetwork/interchain-token-service/blob/main/contracts/interfaces/ITokenManagerType.sol#L10) of token managers available for developers to offer different types of integrations to ITS. These are; `nativeInterchain`, `mintBurnFrom`, `lockUnlock`, `lockUnlockFee`, `mintBurn`, and `gateway`. @@ -51,4 +51,5 @@ Token Managers handle the flow limits for a token's ITS integration. A `flowLimi For each cross-chain transaction that goes through ITS the `flowIn` & `flowAmount` amount are increased to track the [inflow](https://github.com/axelarnetwork/interchain-token-service/blob/main/contracts/TokenHandler.sol#L51) and [outflow](https://github.com/axelarnetwork/interchain-token-service/blob/main/contracts/TokenHandler.sol#L120) of tokens. To [set](https://github.com/axelarnetwork/interchain-token-service/blob/main/contracts/token-manager/TokenManager.sol#L167) the `flowLimit` of a given token the caller must be a registered [flowLimiter](https://github.com/axelarnetwork/interchain-token-service/blob/main/contracts/utils/RolesConstants.sol#L13). -More info on `flowLimits` can be found [here](/dev/send-tokens/interchain-tokens/rate-limit/) \ No newline at end of file +For more information on `flowLimit`s, see [Flow Limit in Interchain Token Service +](/dev/send-tokens/interchain-tokens/flow-limit/)