Token terminology update (#1414)

Author: dwightjl

public/samples/CCIP/Messenger.sol

@@ -191,7 +191,7 @@ contract Messenger is CCIPReceiver, OwnerIsCreator {
 
     /// @notice Sends data to receiver on the destination chain.
     /// @notice Pay for fees in native gas.
-    /// @dev Assumes your contract has sufficient native gas coins.
+    /// @dev Assumes your contract has sufficient native gas tokens.
     /// @param _destinationChainSelector The identifier (aka selector) for the destination blockchain.
     /// @param _receiver The address of the recipient on the destination blockchain.
     /// @param _text The text to be sent.

scripts/reference/chains.json

@@ -89,7 +89,7 @@
       "wss://bsc-ws-node.nariox.org"
     ],
     "faucets": ["https://free-online-app.com/faucet-for-eth-evm-chains/"],
-    "nativeCurrency": { "name": "Binance Chain Native Gas Coin", "symbol": "BNB", "decimals": 18 },
+    "nativeCurrency": { "name": "Binance Chain Native Gas Token", "symbol": "BNB", "decimals": 18 },
     "infoURL": "https://www.binance.org",
     "shortName": "bnb",
     "chainId": 56,
@@ -110,7 +110,7 @@
       "https://bsc-testnet.publicnode.com"
     ],
     "faucets": ["https://testnet.binance.org/faucet-smart"],
-    "nativeCurrency": { "name": "Binance Chain Native Gas Coin", "symbol": "tBNB", "decimals": 18 },
+    "nativeCurrency": { "name": "Binance Chain Native Gas Token", "symbol": "tBNB", "decimals": 18 },
     "infoURL": "https://testnet.binance.org/",
     "shortName": "bnbt",
     "chainId": 97,

src/pages/ccip/api-reference/Client.mdx

@@ -81,7 +81,7 @@ struct EVM2AnyMessage {
 | receiver     | bytes                   | Receiver address. Use `abi.encode(sender)` to encode the address to _bytes_.                                                         |
 | data         | bytes                   | Payload sent within the CCIP message.                                                                                                |
 | tokenAmounts | Client.EVMTokenAmount[] | Tokens and their amounts in the source chain representation.                                                                         |
-| feeToken     | address                 | Address of feeToken. Set `address(0)` to pay in native gas coins such as ETH on Ethereum or MATIC on Polygon.                        |
+| feeToken     | address                 | Address of feeToken. Set `address(0)` to pay in native gas tokens such as ETH on Ethereum or MATIC on Polygon.                       |
 | extraArgs    | bytes                   | Users fill in the [EVMExtraArgsV1 struct](#evmextraargsv1) then encode it to bytes using the [\_argsToBytes function](#_argstobytes) |
 
 ### EVM_EXTRA_ARGS_V1_TAG

src/pages/ccip/architecture.mdx

@@ -87,7 +87,7 @@ One OffRamp contract per [lane](/ccip/concepts#lane) exists. This contract perfo
 
 Each token has its own token pool, an abstraction layer over ERC-20 tokens that facilitates OnRamp and OffRamp token-related operations. Token pools are configurable to `lock` or `burn` at the source blockchain and `unlock` or `mint` at the destination blockchain. The mechanism for handling tokens depends on the characteristics of the token in question. Here are a few examples:
 
-- Blockchain-native gas coins, such as ETH, MATIC, and AVAX, can only be minted on their native chains. These tokens cannot be burned on the source and minted at the destination to transfer these tokens between chains. Instead, the linked token pool uses a "Lock and Mint" approach that locks the token at its source and then mints a wrapped or synthetic asset on the destination blockchain. This synthetic asset represents the locked asset and is essential for redeeming the locked asset.
+- Blockchain-native gas tokens, such as ETH, MATIC, and AVAX, can only be minted on their native chains. These tokens cannot be burned on the source and minted at the destination to transfer these tokens between chains. Instead, the linked token pool uses a "Lock and Mint" approach that locks the token at its source and then mints a wrapped or synthetic asset on the destination blockchain. This synthetic asset represents the locked asset and is essential for redeeming the locked asset.
 - A token like LINK is minted on a single chain (Ethereum mainnet) with a fixed total supply. CCIP cannot natively mint it on another chain. In this case, the "Lock and Mint" approach is required.
 - Some tokens can be minted on multiple chains. Examples of such tokens include stablecoins like USDC, TUSD, USDT, and FRAX. The linked token pools use a "Burn and Mint" method to burn the token at its source and then mint it natively on the destination blockchain. Wrapped assets such as WBTC or WETH are other examples that use the "Burn and Mint" approach.
 - A token with a Proof Of Reserve (PoR) feed on a specific chain poses a challenge for the "Burn and Mint" method when applied to other chains because it conflicts with the PoR feed. For these tokens, "Lock and Mint" is the preferred approach.
@@ -134,7 +134,7 @@ Read the [ARM concepts](/ccip/concepts#active-risk-management-arm-network) page
 
 The CCIP billing model uses the `feeToken` specified in the message to pay a single fee on the source chain. CCIP uses a gas-locked fee payment mechanism, referred to as _Smart Execution_, to help ensure the reliable execution of cross-chain transactions regardless of destination chain gas spikes. For developers, this means you can simply pay on the source chain and CCIP will take care of execution on the destination chain.
 
-On each source chain, CCIP maintains a cache of destination gas prices, denominated in each `feeToken`. To prevent staleness, these prices are routinely updated by either piggybacking user messages or timeouts. CCIP supports fee payments in LINK and in alternative assets, which currently includes native blockchain gas coins and their ERC20 wrapped versions. The payment model for CCIP is designed to significantly reduce friction for users and quickly scale CCIP to more blockchains by supporting fee payments that originate across a multitude of chains over time.
+On each source chain, CCIP maintains a cache of destination gas prices, denominated in each `feeToken`. To prevent staleness, these prices are routinely updated by either piggybacking user messages or timeouts. CCIP supports fee payments in LINK and in alternative assets, which currently includes blockchain-native gas tokens and their ERC20 wrapped versions. The payment model for CCIP is designed to significantly reduce friction for users and quickly scale CCIP to more blockchains by supporting fee payments that originate across a multitude of chains over time.
 
 ### Overheads and fees
 

src/pages/ccip/getting-started.mdx

@@ -17,7 +17,7 @@ import { CodeSample, ClickToZoom, CopyText, Aside } from "@components"
 
 A simple use case for Chainlink CCIP is sending data between smart contracts on different blockchains. This guide shows you how to deploy a CCIP sender contract and a CCIP receiver contract to two different blockchains and send data from the sender contract to the receiver contract. You pay the CCIP fees using LINK.
 
-Fees can also be paid in alternative assets, which currently include the native gas coins of the source blockchain and their ERC20 wrapped version. For example, you can pay ETH or WETH when you send transactions to the CCIP router on Ethereum and MATIC or WMATIC when you send transactions to the CCIP router on Polygon.
+Fees can also be paid in alternative assets, which currently include the native gas tokens of the source blockchain and their ERC20 wrapped version. For example, you can pay ETH or WETH when you send transactions to the CCIP router on Ethereum and MATIC or WMATIC when you send transactions to the CCIP router on Polygon.
 
 ## Before you begin
 

src/pages/ccip/supported-networks.mdx

@@ -28,7 +28,7 @@ Each available network has two rate limits:
 
 Both limits have a _Refill rate_, which is the speed at which the maximum capacity is restored. For example, if 100 LINK is transferred using the Ethereum Sepolia => Optimism Goerli Lane, the total capacity for that lane is used up. After that, the maximum capacity restores at a rate of 1 LINK per second.
 
-Read the [LINK Token Contracts](/resources/link-token-contracts?parent=ccip) page to learn where to get testnet LINK and native gas coins. You can pay fees for each network in native gas coins, wrapped native gas coins, or LINK tokens.
+Read the [LINK Token Contracts](/resources/link-token-contracts?parent=ccip) page to learn where to get testnet LINK and native gas tokens. You can pay fees for each network in native gas tokens, wrapped native gas tokens, or LINK tokens.
 
 ## Service Limits
 

src/pages/ccip/tutorials/cross-chain-tokens-from-eoa.mdx

@@ -96,7 +96,7 @@ To transfer tokens and pay in LINK, use the following command:
 node src/transfer-tokens.js sourceChain destinationChain destinationAccount tokenAddress amount feeTokenAddress
 ```
 
-The `feeTokenAddress` parameter specifies the token address for paying CCIP fees. The supported tokens for paying fees include LINK, the native gas coin of the source blockchain (ETH for Ethereum), and the wrapped native gas coin (WETH for Ethereum).
+The `feeTokenAddress` parameter specifies the token address for paying CCIP fees. The supported tokens for paying fees include LINK, the native gas token of the source blockchain (ETH for Ethereum), and the wrapped native gas token (WETH for Ethereum).
 
 Complete the following steps in your terminal:
 
@@ -269,9 +269,9 @@ The script calls the router to estimate the fees for transferring tokens.
 
 This section handles the actual transferring of tokens. It covers three cases:
 
-    - **Fees paid using the native gas coin:** The contract makes one approval for the transfer amount. The fees are included in the `value` transaction field.
-    - **Fees paid using an asset different from the native gas coin and the token being transferred:** The contracts makes two approvals. The first approval is for the transfer amount and the second approval is for the fees.
-    - **Fees paid using the same asset that is being transferred, but not the native gas coin:** The contract makes a single approval for the sum of the transfer amount and fees.
+    - **Fees paid using the native gas token:** The contract makes one approval for the transfer amount. The fees are included in the `value` transaction field.
+    - **Fees paid using an asset different from the native gas token and the token being transferred:** The contracts makes two approvals. The first approval is for the transfer amount and the second approval is for the fees.
+    - **Fees paid using the same asset that is being transferred, but not the native gas token:** The contract makes a single approval for the sum of the transfer amount and fees.
 
 The script waits for the transaction to be validated and stores the transaction receipt.
 

src/pages/ccip/tutorials/cross-chain-tokens.mdx

@@ -15,7 +15,7 @@ whatsnext:
 import { CodeSample, ClickToZoom, CopyText, Aside } from "@components"
 import CcipCommon from "@features/ccip/CcipCommon.astro"
 
-In this tutorial, you will use Chainlink CCIP to transfer tokens from a smart contract to an account on a different blockchain. First, you will pay for the CCIP fees on the source blockchain using LINK. Then, you will use the same contract to pay CCIP fees in native gas coins. For example, you would use ETH on Ethereum or MATIC on Polygon.
+In this tutorial, you will use Chainlink CCIP to transfer tokens from a smart contract to an account on a different blockchain. First, you will pay for the CCIP fees on the source blockchain using LINK. Then, you will use the same contract to pay CCIP fees in native gas tokens. For example, you would use ETH on Ethereum or MATIC on Polygon.
 
 <Aside type="note" title="Node Operator Rewards">
   CCIP rewards the oracle node and ARM node operators in LINK.
@@ -127,7 +127,7 @@ You will transfer _0.001 CCIP-BnM_. The CCIP fees for using CCIP will be paid in
 
 You will transfer _0.001 CCIP-BnM_. The CCIP fees for using CCIP will be paid in Sepolia's native ETH. Read this [explanation](#transferring-tokens-and-pay-in-native) for a detailed description of the code example.
 
-1.  Open MetaMask and connect to _Ethereum Sepolia_. Fund your contract with native gas coins. You can transfer <CopyText text="0.01" code/> _ETH_ to your contract. **Note**: The native gas coins are used to pay for CCIP fees.
+1.  Open MetaMask and connect to _Ethereum Sepolia_. Fund your contract with native gas tokens. You can transfer <CopyText text="0.01" code/> _ETH_ to your contract. **Note**: The native gas tokens are used to pay for CCIP fees.
 
 1.  Transfer CCIP-BnM from _Ethereum Sepolia_:
 
@@ -159,7 +159,7 @@ You will transfer _0.001 CCIP-BnM_. The CCIP fees for using CCIP will be paid in
             alt="Chainlink CCIP Explorer transaction details"
           />
 
-1.  The CCIP transaction is completed once the status is marked as "Success". The data field is empty because you only transfer tokens. Note that CCIP fees are denominated in LINK. Even if CCIP fees are paid using native gas coins, node operators will be paid in LINK.
+1.  The CCIP transaction is completed once the status is marked as "Success". The data field is empty because you only transfer tokens. Note that CCIP fees are denominated in LINK. Even if CCIP fees are paid using native gas tokens, node operators will be paid in LINK.
 
                 <br />
 
@@ -226,7 +226,7 @@ The `transferTokensPayNative` function undertakes five primary operations:
    - The `tokenAmounts` is an array, with each element comprising an `EVMTokenAmount` [struct](/ccip/api-reference/Client#evmtokenamount) containing the token address and amount. The array contains one element where the `_token` (token address) and `_amount` (token amount) are passed by the user when calling the `transferTokensPayNative` function.
    - The `extraArgs` specifies the `gasLimit` for relaying the message to the recipient contract on the destination blockchain, along with a `strict` parameter. In this example, the `gasLimit` is set to `0` because the contract only transfers tokens and does not expect function calls on the destination blockchain. The `strict` parameter is set to `false`.
      **Note**: If `strict` is true and `ccipReceive` reverts on the destination blockchain, subsequent messages from the same sender will be blocked by CCIP until the reverted message can be executed.
-   - The `_feeTokenAddress` designates the token address used for CCIP fees. Here, `address(0)` signifies payment in native gas coins (ETH).
+   - The `_feeTokenAddress` designates the token address used for CCIP fees. Here, `address(0)` signifies payment in native gas tokens (ETH).
 
      {" "}
 

src/pages/ccip/tutorials/programmable-token-transfers.mdx

@@ -15,7 +15,7 @@ whatsnext:
 import { CodeSample, ClickToZoom, CopyText, Aside } from "@components"
 import CcipCommon from "@features/ccip/CcipCommon.astro"
 
-In this tutorial, you will use Chainlink CCIP to transfer tokens and arbitrary data between smart contracts on different blockchains. First, you will pay for the CCIP fees on the source blockchain using LINK. Then, you will use the same contract to pay CCIP fees in native gas coins. For example, you would use ETH on Ethereum or MATIC on Polygon.
+In this tutorial, you will use Chainlink CCIP to transfer tokens and arbitrary data between smart contracts on different blockchains. First, you will pay for the CCIP fees on the source blockchain using LINK. Then, you will use the same contract to pay CCIP fees in native gas tokens. For example, you would use ETH on Ethereum or MATIC on Polygon.
 
 <Aside type="note" title="Node Operator Rewards">
   CCIP rewards the oracle node and ARM node operators in LINK.
@@ -146,7 +146,7 @@ You will transfer _0.001 CCIP-BnM_ and a text. The CCIP fees for using CCIP will
 
 You will transfer _0.001 CCIP-BnM_ and a text. The CCIP fees for using CCIP will be paid in Sepolia's native ETH. Read this [explanation](#transferring-tokens-and-data-and-pay-in-native) for a detailed description of the code example.
 
-1.  Open MetaMask and connect to _Ethereum Sepolia_. Fund your contract with ETH tokens. You can transfer <CopyText text="0.01" code/> _ETH_ to your contract. The native gas coins are used to pay the CCIP fees.
+1.  Open MetaMask and connect to _Ethereum Sepolia_. Fund your contract with ETH tokens. You can transfer <CopyText text="0.01" code/> _ETH_ to your contract. The native gas tokens are used to pay the CCIP fees.
 
 1.  Send a string data with tokens from _Ethereum Sepolia_:
 
@@ -178,7 +178,7 @@ You will transfer _0.001 CCIP-BnM_ and a text. The CCIP fees for using CCIP will
             alt="Chainlink CCIP Explorer transaction details"
           />
 
-1.  The CCIP transaction is completed once the status is marked as "Success". In this example, the CCIP message ID is _0x3a2cde0d0dd07f2b2e7841b550221101d57792eb581a75ed11419022f13fd865_. Note that CCIP fees are denominated in LINK. Even if CCIP fees are paid using native gas coins, node operators will be paid in LINK.
+1.  The CCIP transaction is completed once the status is marked as "Success". In this example, the CCIP message ID is _0x3a2cde0d0dd07f2b2e7841b550221101d57792eb581a75ed11419022f13fd865_. Note that CCIP fees are denominated in LINK. Even if CCIP fees are paid using native gas tokens, node operators will be paid in LINK.
 
                 <br />
 
@@ -255,7 +255,7 @@ The `sendMessagePayNative` function undertakes five primary operations:
    - The `data` is encoded from a `string` to `bytes` using [abi.encode](https://docs.soliditylang.org/en/develop/abi-spec.html).
    - The `tokenAmounts` is an array, with each element comprising an `EVMTokenAmount` [struct](/ccip/api-reference/Client#evmtokenamount) containing the token address and amount. The array contains one element where the `_token` (token address) and `_amount` (token amount) are passed by the user when calling the `transferTokensPayNative` function.
    - The `extraArgs` specifies the `gasLimit` for relaying the message to the recipient contract on the destination blockchain, along with a `strict` parameter. In this example, the `gasLimit` is set to `200000` and `strict` is set to `false`. **Note**: If `strict` is true and `ccipReceive` reverts on the destination blockchain, subsequent messages from the same sender will be blocked by CCIP until the reverted message can be executed.
-   - The `_feeTokenAddress` designates the token address used for CCIP fees. Here, `address(0)` signifies payment in native gas coins (ETH).
+   - The `_feeTokenAddress` designates the token address used for CCIP fees. Here, `address(0)` signifies payment in native gas tokens (ETH).
 
      {" "}