trim IBC, tokenfactory and unused api

Author: alexander-sei

README.md

@@ -55,7 +55,3 @@ To propose changes directly, you can open a Pull Request against this repository
 Alternatively, if you have more general suggestions on how we can improve or correct these docs, you can [open an issue](https://github.com/sei-protocol/sei-docs/issues).
 
 ### Local Development
-
-#### Generating Cosmos API Reference Docs
-
-Run the script in the data directory to generate the Cosmos API reference docs. If you need to get an updated openapi json file, that can be generated from the `sei-chain` repo using IgniteCLI.

content/evm/differences-with-ethereum.mdx

@@ -105,7 +105,7 @@ Cosmos SDK and CosmWasm functionality will be deprecated in favor of EVM-only. F
 - **Sei is a dual-execution environment (EVM and Cosmos-SDK).** This means:
   - Non-EVM transactions can update EVM-accessible state.
     - For example, an account's SEI balance can be affected by both Cosmos (bank send, wasm execute) transactions as well as EVM send transactions
-  - Sei assets can not only exist as EVM (i.e., ERC20/721/1155), but also as CW (i.e., CW20, CW721) or as "native" (Sei, IBC, Tokenfactory).
+  - Sei assets can not only exist as EVM (i.e., ERC20/721/1155), but also as CW (i.e., CW20, CW721) or as "native" (Sei).
   - User accounts on Sei have [two addresses](/learn/accounts) derived from the same public key (Cosmos Bech32 and EVM-compatible 0x…)
   - Interoperability between EVM and Cosmos-SDK modules is governed and navigated via [precompiles](./precompiles/example-usage) and [pointer contracts](/learn/pointers)
 

content/evm/precompiles/cosmwasm-precompiles/pointer.mdx

@@ -211,7 +211,7 @@ Each pointer type requires specific parameters:
       <tr>
         <td className="px-4 py-3 text-sm text-neutral-900 dark:text-neutral-100 whitespace-nowrap font-medium">**Native**</td>
         <td className="px-4 py-3 text-sm text-neutral-600 dark:text-neutral-400">Token denomination</td>
-        <td className="px-4 py-3 text-sm text-neutral-600 dark:text-neutral-400 font-mono">tokenfactory/...</td>
+        <td className="px-4 py-3 text-sm text-neutral-600 dark:text-neutral-400 font-mono">uatom</td>
         <td className="px-4 py-3 text-sm text-neutral-600 dark:text-neutral-400">ERC20 compatible contract</td>
       </tr>
       <tr>
@@ -271,7 +271,7 @@ Each pointer type requires specific parameters:
 ```typescript copy
 // Create a pointer for native SEI tokens
 async function createNativePointer() {
-  const tokenDenom = 'tokenfactory/....'; // Native SEI denomination
+  const tokenDenom = 'uatom'; // Native token denomination
 
   try {
     console.log('Creating native pointer for:', tokenDenom);
@@ -551,7 +551,7 @@ contract CW721PointerManager {
 Once you create a native token pointer, you can interact with it like any erc20 token:
 
 ```typescript copy
-// After creating a native pointer for 'tokenfactory/....'
+// After creating a native pointer for a native token
 const ERC20_ABI = ['function balanceOf(address) view returns (uint256)', 'function transfer(address, uint256) returns (bool)', 'function approve(address, uint256) returns (bool)'];
 
 const seiPointer = new ethers.Contract(pointerAddress, ERC20_ABI, signer);

content/evm/tokens.mdx

@@ -1,6 +1,6 @@
 ---
 title: 'Viewing Tokens in MetaMask'
-description: 'Learn how to view and manage different token types in MetaMask with Sei network, including ERC20 tokens, ERC721 NFTs, TokenFactory assets, and CW20/CW721 tokens with pointer contracts.'
+description: 'Learn how to view and manage different token types in MetaMask with Sei network, including ERC20 tokens, ERC721 NFTs.'
 keywords: ['metamask tokens', 'erc20', 'erc721', 'nft display', 'cw20 tokens', 'pointer contracts']
 ---
 
@@ -21,17 +21,4 @@ Viewing NFTs in MetaMask requires manual addition. Follow the steps provided
 [here](https://support.metamask.io/manage-crypto/nfts/nft-tokens-in-your-metamask-wallet/)
 to add and view your NFTs in the wallet.
 
-#### TokenFactory & CW20 Tokens
-
-TokenFactory and CW20 tokens can only be visible in MetaMask if there's a
-pointer contract created for it. A pointer contract enables a native Sei token
-to be linked across Cosmos and EVM through an ERC20 interface. Once created
-for a native token, you can import it as an ERC20 token using the steps above.
-
-#### CW721 NFTs
-
-Similarly, CW721 NFTs can only be visible in MetaMask if a pointer contract
-created for it. Once created, you can import it into your wallet like a standard
-ERC721 NFT.
-
 <Callout type="info">Visit our [Pointer Contract page](/learn/pointers) to learn more.</Callout>

content/learn/dev-interoperability.mdx

@@ -1,7 +1,7 @@
 ---
-title: "Sei Network Interoperability Framework"
-description: "Understand how Sei enables seamless interaction between EVM and Cosmos ecosystems through its dual address system, precompiles, and pointer contracts."
-keywords: ["blockchain interoperability", "EVM Cosmos bridge", "dual address system", "precompile contracts", "pointer contracts"]
+title: 'Sei Network Interoperability Framework'
+description: 'Understand how Sei enables seamless interaction between EVM and Cosmos ecosystems through its dual address system, precompiles, and pointer contracts.'
+keywords: ['blockchain interoperability', 'EVM Cosmos bridge', 'dual address system', 'precompile contracts', 'pointer contracts']
 ---
 
 import { ImageWithCaption } from '../../src/components/ImageWithCaption';
@@ -50,8 +50,8 @@ For instructions on utilizing EVM precompiles, refer to the
 Pointer Contracts are a unique feature introduced on Sei, designed to enhance
 interoperability between EVM and Cosmos environments. These contracts serve as a proxy, or interface for either token standard, making them compatible with both EVM and Cosmos-SDK clients.
 
-Pointer contracts can be deployed for any Token Factory, Smart Contract (ERC20,
-ERC721, etc.), and any IBC denom.
+Pointer contracts can be deployed for any Smart Contract (ERC20,
+ERC721, etc.).
 
 ## Example Diagram
 

content/learn/dev-token-standards.mdx

@@ -1,7 +1,7 @@
 ---
 title: 'Token Standards'
-description: 'Explore the different token types on Sei including native SEI, TokenFactory tokens, smart contract tokens (ERC20/CW20), NFTs, and IBC tokens, with implementation guidance for each standard.'
-keywords: ['token standards', 'erc20', 'cw20', 'nfts', 'tokenfactory', 'ibc tokens']
+description: 'Explore the different token types on Sei including native SEI, smart contract tokens (ERC20/CW20), and NFTs, with implementation guidance for each standard.'
+keywords: ['token standards', 'erc20', 'cw20', 'nfts']
 ---
 
 import { Callout } from 'nextra/components';
@@ -12,12 +12,10 @@ In this section, we delve into the various token standards supported on Sei.
 Understanding these standards is crucial for developers as they form the
 foundation of many decentralized applications.
 
-Sei offers support for four main token types:
+Sei offers support for the following token types:
 
 - [Sei Token](#sei-token)
-- [Token Factory Tokens](#tokenfactory)
 - [Smart Contract Tokens](#smart-contract-tokens)
-- [IBC Tokens](#ibc-tokens)
 
 ## Sei Token
 
@@ -47,9 +45,7 @@ within the ecosystem.
 ## Fungible Tokens
 
 Fungible tokens are digital assets that are interchangeable with one another and
-are not unique. Sei supports both ERC20 and CW20 fungible token standards, so
-developers have the option to create tokens using the TokenFactory module, or via
-smart contract standards.
+are not unique. Sei supports both ERC20 and CW20 fungible token standards.
 
 ### Smart Contract Tokens
 
@@ -70,7 +66,7 @@ smart contract standards.
   interactions for use with existing dApps and maximum compatibility.
 
 <Callout type="info">
-**Interoperability:** Regardless of the choice, both TokenFactory and CW20/ERC20 tokens can have pointer contracts deployed, facilitating seamless cross-vm interoperability.
+**Interoperability:** CW20/ERC20 tokens can have pointer contracts deployed, facilitating seamless cross-vm interoperability.
 
 For more detailed guidance, refer to the
 [Pointer Contracts Documentation](/learn/pointers).
@@ -92,16 +88,6 @@ ERC721 and CW721 standards as well as their counterparts with royalties (2981).
 - **Pointer Contract Registry**: A registry for tracking pointer contracts
   specific to NFTs.
 
-## IBC Tokens
-
-Inter-Blockchain Communication (IBC) is a trust-less and permission-less interchain
-messaging protocol that enables communication between many different chains. IBC
-tokens are tokens bridged from one chain to another using the IBC protocol.
-Channels are set up to establish communication between the chains. Each channel
-has a unique identifier and specific configurations. View the
-[IBC Channel](https://github.com/sei-protocol/chain-registry/blob/main/ibc_info.json)
-section of the Sei chain registry for channel information.
-
-### Wrapped Sei (wSei)
+## Wrapped Sei (wSei)
 
 Some dApps may require Sei tokens to be wrapped in order to interact with them (similar to Wrapped ETH on Ethereum). The Wrapped Sei Token WSEI is deployed under the contract address [`0xE30feDd158A2e3b13e9badaeABaFc5516e95e8C7`](https://seitrace.com/token/0xE30feDd158A2e3b13e9badaeABaFc5516e95e8C7?chain=pacific-1).

content/learn/ledger-setup.mdx

@@ -12,11 +12,9 @@ import { Callout } from 'nextra/components';
 
 The Sei network supports various crypto assets, including:
 
-- Native tokens ($SEI, tokenfactory, IBC)
+- Native tokens ($SEI)
 - ERC20 tokens
 - ERC721 NFTs
-- CW20 tokens
-- CW721 NFTs
 
 Using a Ledger hardware wallet ensures secure key management for users interacting
 with the Sei network.