docs(evm): clarify Initia ERC20 compatibility for wallet/bridge and r…

developers/developer-guides/integrating-initia-apps/registry/introduction.mdx

@@ -9,6 +9,16 @@ registration is done via a GitHub pull request to the registry repository. The
 file and directory that need to be updated in the PR vary depending on the type
 of information being added.
 
+<Tip>
+  Full token support across Initia apps depends on two separate requirements:
+
+1. Registry metadata (`assetlist.json`): Controls how the token appears in
+   product UIs (name, symbol, decimals, logo, and display info in Initia Scan).
+2. Token contract behavior: Controls whether token actions actually work (for
+   example, sending and bridging). For MiniEVM ERC20 tokens, this includes the
+   `sudoTransfer` hook.
+   </Tip>
+
 ## Adding Profiles
 
 For an application's information including logo, name, description, and more to

developers/developer-guides/vm-specific-tutorials/evm/creating-erc20s/creating-standard-erc20s.mdx

@@ -7,7 +7,36 @@ title: Creating Standard ERC20s via ERC20Factory
 For developers looking to create standard ERC20 tokens on EVM rollups, we
 recommend using the
 [ERC20Factory](/resources/developer/contract-references/evm/erc20-factory)
-contract.
+contract. For most teams, this is the lowest-risk path because it deploys a
+token implementation that already includes the required Initia chain integration
+hooks (including `sudoTransfer`).
+
+## Production Readiness Checklist
+
+Before treating a factory-deployed token as ready for support across Initia
+products (for example, Initia Scan, InterwovenKit, Wallet, and Bridge):
+
+1. Deploy via
+   [`ERC20Factory`](/resources/developer/contract-references/evm/erc20-factory).
+2. Add token metadata to the relevant `assetlist.json` in
+   [Initia Registry](/developers/developer-guides/integrating-initia-apps/registry/introduction).
+3. Confirm your token is compatible with the required `sudoTransfer` hook used
+   in sending and bridging flows (included by default for `ERC20Factory`
+   deployments) by following the compatibility guidance in
+   [Creating ERC20s Introduction](/developers/developer-guides/vm-specific-tutorials/evm/creating-erc20s/introduction)
+   and
+   [`InitiaCustomERC20` reference](/resources/developer/contract-references/evm/initia-custom-erc20).
+
+If you need custom token logic, deploy a custom ERC20 that inherits
+[`InitiaCustomERC20`](/resources/developer/contract-references/evm/initia-custom-erc20)
+as the base contract (see
+[Creating Custom ERC20s](/developers/developer-guides/vm-specific-tutorials/evm/creating-erc20s/creating-custom-erc20s)).
+
+<Note>
+  Registry listing is required for tokens to appear correctly in Initia product
+  UIs with metadata (name, symbol, decimals, logo), and to be selectable in
+  flows such as balances, transfers, and bridging.
+</Note>
 
 ## Project Setup
 

developers/developer-guides/vm-specific-tutorials/evm/creating-erc20s/introduction.mdx

@@ -2,18 +2,18 @@
 title: Introduction
 ---
 
-To ensure compatibility with Initia's EVM module and the Cosmos SDK in general,
-ERC20 tokens on rollups includes certain extensions beyond the standard ERC20
-template.
+For an ERC20 token to work across Initia products (for example, Initia Scan,
+InterwovenKit, Wallet, and Bridge), it must include Initia chain integration
+hooks in addition to standard ERC20 behavior.
 
 Developers looking to create and deploy ERC20s on EVM rollups have two options:
 
-1. Deploy Initia ERC20s using the
+1. Deploy using the
    [ERC20Factory](/resources/developer/contract-references/evm/erc20-factory)
-   contract.
-2. Extend and modify Initia's
+   contract (recommended when you only need standard token behavior).
+2. For custom ERC20 logic, inherit from
    [InitiaCustomERC20](/resources/developer/contract-references/evm/initia-custom-erc20)
-   contract.
+   and extend it.
 
 <Note>
   While Initia's `CustomERC20.sol` contains additional logic, it is still fully

developers/developer-guides/vm-specific-tutorials/evm/update-fee-token.mdx

@@ -17,7 +17,10 @@ Fee Token as an ERC20 token.
 Use validator (admin) account to update the chain parameter.
 
 <Warning>
-  The deployed ERC20 token must inherit the `InitiaERC20` contract.
+  The fee token ERC20 must implement Initia-compatible chain hooks, especially
+  `sudoTransfer`, which is used by chain-level transfer handling. Tokens
+  deployed via `ERC20Factory` satisfy this requirement by default. For custom
+  ERC20 deployments, the token contract must inherit `InitiaCustomERC20`.
 </Warning>
 
 ```ts

resources/developer/contract-references/evm/initia-custom-erc20.mdx

@@ -229,6 +229,13 @@ function burn(address from, uint256 amount) external burnable(from) onlyOwner
 Transfers tokens from one address to another, bypassing the usual access control
 checks. This function can only be called by the chain signer.
 
+<Info>
+  For MiniEVM ERC20 tokens, `sudoTransfer` is a required hook in the token
+  contract. If you deploy through `ERC20Factory` or inherit `InitiaCustomERC20`,
+  it is included automatically. Without it, sending and bridging may fail even
+  if the token appears in UIs.
+</Info>
+
 ```solidity
 function sudoTransfer(address sender, address recipient, uint256 amount) external onlyChain
 ```