docs: clarify ERC20 compatibility requirements and registry metadata roles

Author: restorenode

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

@@ -9,12 +9,15 @@ 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.
 
-<Info>
-  Registry listing and token contract compatibility solve different problems. A
-  token may appear in some balance displays (for example, on scan) but still
-  fail in Wallet or Bridge actions. For full end-user support across Initia
-  apps, you need both complete registry metadata and compatible token behavior.
-</Info>
+<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
 

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

@@ -8,31 +8,33 @@ For developers looking to create standard ERC20 tokens on EVM rollups, we
 recommend using the
 [ERC20Factory](/resources/developer/contract-references/evm/erc20-factory)
 contract. For most teams, this is the lowest-risk path because it deploys a
-token implementation that already includes Initia ERC20 compatibility
-extensions.
+token implementation that already includes the required Initia chain integration
+hooks (including `sudoTransfer`).
 
 ## Production Readiness Checklist
 
-Before treating a token as ready for broad ecosystem support:
+Before treating a 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)
-   (or implement equivalent Initia extensions in a custom token contract using
-   [Creating Custom ERC20s](/developers/developer-guides/vm-specific-tutorials/evm/creating-erc20s/creating-custom-erc20s)
-   and
-   [`InitiaCustomERC20`](/resources/developer/contract-references/evm/initia-custom-erc20)).
+   or, for custom ERC20 deployments, inherit
+   [`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)).
 2. Add token metadata to the relevant `assetlist.json` in
    [Initia Registry](/developers/developer-guides/integrating-initia-apps/registry/introduction).
-3. Confirm your token supports the Cosmos transfer path (`sudoTransfer`) used in
-   escrow-style bridge transfer handling by following the compatibility guidance
-   in
+3. Confirm your token exposes the chain-called `sudoTransfer` hook used by
+   Initia module logic during bridge-related transfer execution 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).
 
 <Note>
-  Registry listing is required for app-level discovery and metadata display
-  across Initia products.
+  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,9 +17,10 @@ Fee Token as an ERC20 token.
 Use validator (admin) account to update the chain parameter.
 
 <Warning>
-  The fee token ERC20 must include Initia ERC20 compatibility extensions.
-  Factory-deployed tokens satisfy this automatically. For custom deployments,
-  inherit `InitiaCustomERC20` (recommended for direct deployment).
+  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

@@ -230,8 +230,10 @@ 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 Cosmos-side transfer handling in Initia ERC20 flows, `sudoTransfer` is the
-  key transfer hook used by chain-level logic.
+  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