sei-protocol · alexander-sei · Jul 21, 2026 · Jul 21, 2026
diff --git a/STYLE_GUIDE.md b/STYLE_GUIDE.md
@@ -1,4 +1,4 @@
 # Sei Docs Style Guide

 This style guide contains general rules and principles to ensure the documentation is cohesive, useful, and organized.

@@ -6,7 +6,7 @@

 This documentation strives to be:

 ### Beginner Friendly

 The Sei community welcomes members from all walks of life. As such, the documentation should be understandable by anyone, including those who are new to Web3 or non-technical.

@@ -22,8 +22,8 @@

 - To be clear and inclusive, avoid using jargon and obscure words where possible.
 - Limit the number of clauses in a sentence and make sure that your points are structured.
 - Avoid qualifying language, which is ~~quite~~ often ~~completely~~ unnecessary.
 - Information should be simply organized and easy to find.

 ### Self-explanatory

@@ -64,13 +64,13 @@
 - **Reference**: Transactions, RPC reference, tokens, changelog, ecosystem contracts
 - **Hardware Wallets**: Ledger integration with Ethers
 
 ### Cosmos-SDK (Deprecated)
 
-> ⚠️ **Deprecation Notice**: Cosmos SDK and CosmWasm functionality is being deprecated in favor of EVM-only. For more details, see [SIP-3](https://github.com/sei-protocol/sips/blob/main/sips/sip-3.md) and [Proposal 99](https://www.mintscan.io/sei/proposals/99).
+> ⚠️ **Deprecation Notice**: Cosmos SDK and CosmWasm functionality is being deprecated in favor of EVM-only. For more details, see [SIP-3](https://github.com/sei-protocol/sips/blob/main/sips/sip-3.md) and [Proposal 99](https://seistream.app/proposals/99).
 
 This section contains legacy documentation for Cosmos SDK functionality. New development should focus on the EVM.
 
 ### Operate (Node)

 The Operate section covers topics related to running Sei infrastructure. This is relevant for node operators, validators, and those looking to contribute to chain infrastructure.

@@ -79,15 +79,15 @@
 - **Node Operations**: Overview, Seictl setup, statesync, snapshot sync, node types, troubleshooting, API configuration, validators, oracle price feeder
 - **Advanced Operations**: Configuration & monitoring, RocksDB backend, technical reference

 ## Style Guidelines

 ### Acronyms and Abbreviations

 To maximize clarity, we should avoid acronyms and abbreviations where possible, especially for shorter, more ambiguous acronyms:

 - Just use 'CosmWasm' instead of 'CW'

 However, there are occasions where acronyms might be more easily understandable (e.g., NFT instead of Non-Fungible Token, RPC instead of Remote Procedure Call), or referred to very frequently.

 In these cases, we should first use the spelled-out term followed by the shortened form in parentheses:

@@ -252,7 +252,7 @@
 </Frame>
 ```

 ### Callouts and Admonitions

 Use callouts to highlight important information. Mintlify supports the following callout types:


diff --git a/cosmos-sdk/index.mdx b/cosmos-sdk/index.mdx
@@ -10,10 +10,10 @@ canonicalUrl: "https://docs.sei.io/evm"
 
 **Deprecation Notice**
 
-Cosmos SDK and CosmWasm functionality is being deprecated in favor of EVM-only. For more details, see [SIP-3](https://github.com/sei-protocol/sips/blob/main/sips/sip-3.md) and [Proposal 99](https://www.mintscan.io/sei/proposals/99).
+Cosmos SDK and CosmWasm functionality is being deprecated in favor of EVM-only. For more details, see [SIP-3](https://github.com/sei-protocol/sips/blob/main/sips/sip-3.md) and [Proposal 99](https://seistream.app/proposals/99).
 
-In addition, [Proposal 115](https://www.mintscan.io/sei/proposals/115) disables CosmWasm code uploads (`MsgStoreCode`) and contract instantiations (`MsgInstantiateContract`) chain-wide. No new CosmWasm contracts can be deployed; only `execute` and `query` against pre-existing contracts remain available via the [CosmWasm precompile](/evm/precompiles/cosmwasm-precompiles/cosmwasm).
+In addition, [Proposal 115](https://seistream.app/proposals/115) disables CosmWasm code uploads (`MsgStoreCode`) and contract instantiations (`MsgInstantiateContract`) chain-wide. No new CosmWasm contracts can be deployed; only `execute` and `query` against pre-existing contracts remain available via the [CosmWasm precompile](/evm/precompiles/cosmwasm-precompiles/cosmwasm).
 
-[Proposal 116](https://www.mintscan.io/sei/proposals/116) additionally disables inbound IBC transfers. After this passes and is activated, IBC assets bridged from Cosmos chains can no longer arrive on Sei. [Proposal 120](https://www.mintscan.io/sei/proposals/120) re-disables inbound IBC (setting the `ibc` module's `InboundEnabled` parameter to `false`) while leaving outbound IBC unchanged. See the [SIP-03 Migration Guide](/learn/sip-03-migration) for affected assets and migration routes.
+[Proposal 116](https://seistream.app/proposals/116) additionally disables inbound IBC transfers. After this passes and is activated, IBC assets bridged from Cosmos chains can no longer arrive on Sei. [Proposal 120](https://seistream.app/proposals/120) re-disables inbound IBC (setting the `ibc` module's `InboundEnabled` parameter to `false`) while leaving outbound IBC unchanged. See the [SIP-03 Migration Guide](/learn/sip-03-migration) for affected assets and migration routes.
 
 </Danger>
diff --git a/docs.json b/docs.json
@@ -461,8 +461,8 @@
             "href": "https://seiscan.io"
           },
           {
-            "label": "Mintscan",
-            "href": "https://www.mintscan.io/sei"
+            "label": "Seistream",
+            "href": "https://seistream.app"
           }
         ]
       },

diff --git a/evm/differences-with-ethereum.mdx b/evm/differences-with-ethereum.mdx
@@ -35,11 +35,11 @@
 
 **Deprecation Notice**
 
-Cosmos SDK and CosmWasm functionality is being deprecated in favor of EVM-only. For more details, see [SIP-3](https://github.com/sei-protocol/sips/blob/main/sips/sip-3.md) and [Proposal 99](https://www.mintscan.io/sei/proposals/99).
+Cosmos SDK and CosmWasm functionality is being deprecated in favor of EVM-only. For more details, see [SIP-3](https://github.com/sei-protocol/sips/blob/main/sips/sip-3.md) and [Proposal 99](https://seistream.app/proposals/99).
 
-[Proposal 115](https://www.mintscan.io/sei/proposals/115) further disables CosmWasm code uploads and contract instantiations chain-wide — no new CosmWasm contracts can be deployed. Only `execute` and `query` against pre-existing CosmWasm contracts remain available.
+[Proposal 115](https://seistream.app/proposals/115) further disables CosmWasm code uploads and contract instantiations chain-wide — no new CosmWasm contracts can be deployed. Only `execute` and `query` against pre-existing CosmWasm contracts remain available.
 
-[Proposal 116](https://www.mintscan.io/sei/proposals/116) additionally disables inbound IBC transfers — IBC assets bridged from Cosmos chains can no longer arrive on Sei after this passes and is activated. [Proposal 120](https://www.mintscan.io/sei/proposals/120) re-disables inbound IBC (setting the `ibc` module's `InboundEnabled` parameter to `false`) while leaving outbound IBC unchanged. See the [SIP-03 Migration Guide](/learn/sip-03-migration) for affected assets and migration routes.
+[Proposal 116](https://seistream.app/proposals/116) additionally disables inbound IBC transfers — IBC assets bridged from Cosmos chains can no longer arrive on Sei after this passes and is activated. [Proposal 120](https://seistream.app/proposals/120) re-disables inbound IBC (setting the `ibc` module's `InboundEnabled` parameter to `false`) while leaving outbound IBC unchanged. See the [SIP-03 Migration Guide](/learn/sip-03-migration) for affected assets and migration routes.
 
 </Danger>
 
@@ -50,7 +50,7 @@
  - 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](/evm/precompiles/example-usage) and [pointer contracts](/learn/pointers)

 ## Sei EVM Release

 Sei EVM was originally deployed at the following block heights and versions:

@@ -66,7 +66,7 @@
 - **Height:** `79123881`
 - **Changelog:** https://github.com/sei-protocol/sei-chain/blob/main/CHANGELOG.md#v552

 ## Opcode Differences

 | Opcode | Sei EVM | Ethereum | Notes |
 | --- | --- | --- | --- |
@@ -80,7 +80,7 @@
 | Blob‑related opcodes | Not supported (Pectra without blobs) | Supported post‑Cancun (EIP‑4844) | Blob transactions are not enabled on Sei. |


 ### PREVRANDAO

 Since Sei doesn't rely on the same pseudo‑randomness way of determining the next
 validator like Proof of Stake (PoS) Ethereum does, it doesn't have the
@@ -94,19 +94,19 @@
 Coinbase address on Sei is always set to (the EVM address of) the global fee
 collector.

 ## State Root

 Since Sei uses AVL-tree instead of Merkle Patricia Trie (MPT) for data storage,
 Sei doesn't have per-account state root. The global state root is the AVL-tree
 root which is also not equivalent to Ethereum's overall state root (which is a
 MPT root)

 ## Block Hash

 The block hash on Sei is computed based on the block header in Tendermint data
 format, and is different from Ethereum's block Hash as a result.

 ## Base Fee & Tips

 Sei supports all non‑blob transaction types, including the Pectra `SetCode` transaction (EIP‑7702). However for a legacy (non EIP‑1559) type
 transaction, you must specify a gas price at or above Sei's governance-set minimum gas price (currently `50 gwei` on mainnet). Query the live value with `eth_gasPrice` rather than hard-coding it. In addition to this, excess
@@ -131,7 +131,7 @@
 value: '"0.007500000000000000"'
 ```

 ## Non-EVM Transactions

 On Sei there exists non-EVM transactions which may update states accessible by
 EVM transactions. The simplest example would be bank balances, which may be
@@ -145,7 +145,7 @@
 committed (~400 ms) — meaning that commitment levels of "safe", "latest",
 "justified", and "finalized" on Ethereum are all the same thing on Sei.

 ## Pending State

 On Ethereum the block proposer would execute its proposed block first (and
 update its local state) before broadcasting the proposal to others (the updated
@@ -156,7 +156,7 @@
 the same time), so Sei does not have a window when "pending state"
 exists.

 ## Gas Model & Fees

 Sei does not implement base‑fee burning. There is no base‑fee burn; all transaction fees accrue to validators. Fees are calculated as:

@@ -178,11 +178,11 @@

 </Info>

 ## SSTORE Gas Cost
 
 On Sei, the `SSTORE` opcode gas cost is configurable as an on-chain parameter, meaning it can be adjusted via governance proposal without requiring a chain upgrade. This provides flexibility to tune storage costs based on EVM state size and network conditions.
 
-Currently, the `SSTORE` gas cost is set to the non-standard value of **72,000 gas**. This value is the same on both mainnet (`pacific-1`) and testnet (`atlantic-2`). It was set by governance [Proposal #109](https://www.mintscan.io/sei/proposals/109) ("Update EVM SSTORE set gas to 72000"), which changed the `evm` module parameter `KeySeiSstoreSetGasEIP2200` to `72000`.
+Currently, the `SSTORE` gas cost is set to the non-standard value of **72,000 gas**. This value is the same on both mainnet (`pacific-1`) and testnet (`atlantic-2`). It was set by governance [Proposal #109](https://seistream.app/proposals/109) ("Update EVM SSTORE set gas to 72000"), which changed the `evm` module parameter `KeySeiSstoreSetGasEIP2200` to `72000`.
 
 The values below are read **live** from the Sei EVM: 
 
@@ -192,7 +192,7 @@

 <Info>Since `SSTORE` is a governance-controlled parameter, this value may change in the future through a governance proposal.</Info>

 ## ERC Token Standards Compatibility

 Sei’s EVM fully supports the common token standards:

@@ -202,7 +202,7 @@

 Existing OpenZeppelin contracts and tools work unchanged.

 ## Testing & Migration Checklist

 - ✅ Re‑deploy your Solidity code to Sei testnet; most contracts need no changes.
 - ✅ If you used SELFDESTRUCT, refactor to a soft‑close pattern.

diff --git a/evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx b/evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx
@@ -9,9 +9,9 @@
 <Danger>
   **Deprecation Notice — Prop 115 & Prop 116**
 
-  Per [governance Proposal 115](https://www.mintscan.io/sei/proposals/115), CosmWasm code uploads (`MsgStoreCode`) and contract instantiations (`MsgInstantiateContract`) are disabled chain-wide. The `instantiate()` function on this precompile **will revert** for all callers. Only `execute()`, `execute_batch()`, and `query()` against pre-existing CosmWasm contracts remain functional, and all CosmWasm functionality is deprecated in favor of EVM-only per [SIP-3](https://github.com/sei-protocol/sips/blob/main/sips/sip-3.md).
+  Per [governance Proposal 115](https://seistream.app/proposals/115), CosmWasm code uploads (`MsgStoreCode`) and contract instantiations (`MsgInstantiateContract`) are disabled chain-wide. The `instantiate()` function on this precompile **will revert** for all callers. Only `execute()`, `execute_batch()`, and `query()` against pre-existing CosmWasm contracts remain functional, and all CosmWasm functionality is deprecated in favor of EVM-only per [SIP-3](https://github.com/sei-protocol/sips/blob/main/sips/sip-3.md).
 
-  In addition, [Proposal 116](https://www.mintscan.io/sei/proposals/116) disables inbound IBC transfers — IBC assets bridged from Cosmos chains can no longer arrive on Sei after this passes and is activated. See the [SIP-03 Migration Guide](/learn/sip-03-migration) for affected assets and migration routes.
+  In addition, [Proposal 116](https://seistream.app/proposals/116) disables inbound IBC transfers — IBC assets bridged from Cosmos chains can no longer arrive on Sei after this passes and is activated. See the [SIP-03 Migration Guide](/learn/sip-03-migration) for affected assets and migration routes.
 
   For new smart contract development, use the EVM directly. See [Deploy a Smart Contract](/evm/evm-general).
 </Danger>
@@ -20,7 +20,7 @@

 <Info> **What is a precompile?** A precompile is a special smart contract deployed at a fixed address by the Sei protocol itself, that exposes custom native chain logic to EVM-based applications. It acts like a regular contract from the EVM's perspective, but executes privileged, low-level logic efficiently. </Info>

 ## How Does the CosmWasm Precompile Work?

 The CosmWasm precompile at address `0x0000000000000000000000000000000000001002` exposes functions like `execute()`, `execute_batch()`, and `query()`.

@@ -28,7 +28,7 @@
 - **Native Execution:** Operations are executed at the Cosmos SDK level for maximum efficiency and security.
 - **Seamless Bridge:** No need for separate wallet integrations or complex cross-chain interactions.

 ## What You'll Learn in This Guide

 By the end of this guide, you'll be able to:

@@ -41,9 +41,9 @@

 The CosmWasm precompile exposes the following functions:
 
 ### Transaction Functions
 
-<Warning>The `instantiate()` function has been disabled by [Prop 115](https://www.mintscan.io/sei/proposals/115) and will revert. It is omitted from this reference. The ABI in `@sei-js/precompiles` may still expose it for backwards compatibility, but calling it on-chain will fail.</Warning>
+<Warning>The `instantiate()` function has been disabled by [Prop 115](https://seistream.app/proposals/115) and will revert. It is omitted from this reference. The ABI in `@sei-js/precompiles` may still expose it for backwards compatibility, but calling it on-chain will fail.</Warning>
 
 ```solidity
 /// Executes some message on a CosmWasm contract.
@@ -71,7 +71,7 @@
 ) payable external returns (bytes[] memory responses);
 ```

 ### Query Functions

 ```solidity
 /// Queries a CosmWasm contract.
@@ -84,7 +84,7 @@
 ) external view returns (bytes memory response);
 ```

 ## Using the Precompile

 ### Setup

@@ -97,7 +97,7 @@
 - **EVM-compatible wallet**
 - **SEI tokens** for gas and contract operations

 #### Install Dependencies

 Install the required packages for interacting with Sei precompiles:

@@ -109,7 +109,7 @@
 npm install @sei-js/precompiles@2.1.2
 ```

 #### Import Precompile Components

 ```typescript
 // Import CosmWasm precompile address and ABI
@@ -134,11 +134,11 @@
 const cosmwasm = new ethers.Contract(WASM_PRECOMPILE_ADDRESS, WASM_PRECOMPILE_ABI, signer);
 ```

 ## Critical: Understanding Message Formats

 One of the most important concepts to understand when working with the Sei CosmWasm precompile:

 ### CosmWasm Message Structure

 The CosmWasm precompile requires **JSON-encoded messages** that conform to each contract's specific schema:

@@ -148,7 +148,7 @@
 | `query()` | req parameter (input) | JSON bytes | `ethers.toUtf8Bytes(jsonString)` |
 | **All functions** | response (output) | JSON bytes | `JSON.parse(ethers.toUtf8String(response))` |

 ### How Message Encoding Works

 **All CosmWasm functions require JSON-encoded byte arrays:**

@@ -160,7 +160,7 @@
 - Use `msg.value` for SEI amounts
 - Use `coins` parameter for other denominations (encoded as JSON bytes)

 ### Best Practice: Message Encoding Helpers

 When working with CosmWasm messages, use proper JSON encoding:

@@ -203,7 +203,7 @@
 });
 ```

 ## Message Format Helpers

 Use these helper functions to handle CosmWasm message formatting:

@@ -251,9 +251,9 @@
 const coins = CosmWasmHelper.createCoins([{ denom: 'uusdc', amount: '1000000' }]);
 ```

 ## Step-by-Step Guide: Using the CosmWasm Precompile

 ### Execute a CosmWasm Contract

 <Tabs>
 <Tab title="JavaScript">
@@ -311,7 +311,7 @@
 </Tab>
 </Tabs>

 ### Execute Batch Operations

 <Tabs>
 <Tab title="JavaScript">
@@ -382,7 +382,7 @@
 </Tab>
 </Tabs>

 ### Query a CosmWasm Contract

 <Tabs>
 <Tab title="JavaScript">
@@ -451,9 +451,9 @@

 <Warning> **Query Limitations:** CosmWasm queries are read-only operations and don't consume gas, but parsing JSON responses in Solidity is complex. Consider handling response parsing off-chain. </Warning>

 ## Advanced Usage Examples

 ### Cross-Runtime DeFi Integration

 ```typescript
 async function crossRuntimeDeFiOperation(cosmwasmDexContract: string, evmTokenContract: string, amount: string) {
@@ -492,7 +492,7 @@
 }
 ```

 ### Complete Integration Example

 <Tabs>
 <Tab title="JavaScript">
@@ -730,9 +730,9 @@

 ## Troubleshooting

 ### Common Issues and Solutions

 #### Message Encoding Issues

 ```typescript
 // Ensure proper JSON encoding for messages
@@ -750,7 +750,7 @@
 const incorrectMsg = ethers.toUtf8Bytes('invalid json');
 ```

 ### Error Code Reference

 | Error | Cause | Solution |
 | --- | --- | --- |
@@ -761,23 +761,23 @@
 | `unauthorized` | Insufficient permissions | Check admin/owner permissions |
 | `query parsing failed` | Invalid query message format | Match contract's query schema |

 ## Important Notes

 <Info> Remember the key rule: All CosmWasm messages must be properly JSON-encoded as bytes, and contract schemas vary by implementation! </Info>

 ### Message Format Requirements

 - **JSON Encoding:** All messages must be valid JSON encoded as UTF-8 bytes, invalid JSON will cause transaction failures
 - **Schema Compliance:** Messages must match the contract's expected format
 - **Type Safety:** Use proper data types as expected by the contract

 ### Contract Address Format

 - Use valid Sei contract addresses with `sei1...` prefix
 - These are Cosmos-format addresses, not EVM addresses
 - **Contract Existence:** Verify contracts exist before calling

 ### Cross-Runtime Considerations

 - **State Isolation:** CosmWasm and EVM contracts have separate state
 - **Gas Estimation:** CosmWasm operations may require different gas calculations
@@ -785,7 +785,7 @@
 - **Native Token Handling:** Use `msg.value` for SEI, `coins` for other denominations
 - **Batch Limitations:** Large batches may hit gas limits

 ### Best Practices

 - Always validate JSON messages before sending
 - Handle response parsing carefully, especially for complex data structures

diff --git a/evm/precompiles/cosmwasm-precompiles/example-usage.mdx b/evm/precompiles/cosmwasm-precompiles/example-usage.mdx
@@ -6,7 +6,7 @@
 
 
 <Info>
-Per [Proposal 115](https://www.mintscan.io/sei/proposals/115), no new CosmWasm contracts can be deployed on Sei. The examples below apply to **pre-existing CosmWasm contracts** only — `instantiate()` will revert. Separately, [Proposal 116](https://www.mintscan.io/sei/proposals/116) disables inbound IBC transfers as part of the [SIP-03](/learn/sip-03-migration) migration.
+Per [Proposal 115](https://seistream.app/proposals/115), no new CosmWasm contracts can be deployed on Sei. The examples below apply to **pre-existing CosmWasm contracts** only — `instantiate()` will revert. Separately, [Proposal 116](https://seistream.app/proposals/116) disables inbound IBC transfers as part of the [SIP-03](/learn/sip-03-migration) migration.
 </Info>
 
 The Sei precompiles can be used like any standard smart contract on the EVM. For
@@ -47,7 +47,7 @@
 const contract = new ethers.Contract(WASM_PRECOMPILE_ADDRESS, WASM_PRECOMPILE_ABI, signer);
 ```

 #### Querying & Executing a CosmWasm Contract

 Once you have the contract, you can query and execute messages to any CosmWasm
 smart contract. In the below example we assume there is a counter contract with a `get_count` function

diff --git a/learn/dev-interoperability.mdx b/learn/dev-interoperability.mdx
@@ -6,10 +6,10 @@
 ---
 
 <Info>
-  **CosmWasm deployments are frozen, and inbound IBC is being disabled.** Per [Proposal 115](https://www.mintscan.io/sei/proposals/115), no new CosmWasm contracts can be uploaded or instantiated on Sei. [Proposal 116](https://www.mintscan.io/sei/proposals/116) additionally disables inbound IBC transfers, so IBC assets bridged from Cosmos chains can no longer arrive on Sei. The interoperability features described on this page apply to **already-deployed** CosmWasm contracts, native Bank Module assets, and Cosmos-SDK modules accessed via precompiles. For new smart contract development, build directly on the EVM. See [SIP-3](https://github.com/sei-protocol/sips/blob/main/sips/sip-3.md) for the full migration context.
+  **CosmWasm deployments are frozen, and inbound IBC is being disabled.** Per [Proposal 115](https://seistream.app/proposals/115), no new CosmWasm contracts can be uploaded or instantiated on Sei. [Proposal 116](https://seistream.app/proposals/116) additionally disables inbound IBC transfers, so IBC assets bridged from Cosmos chains can no longer arrive on Sei. The interoperability features described on this page apply to **already-deployed** CosmWasm contracts, native Bank Module assets, and Cosmos-SDK modules accessed via precompiles. For new smart contract development, build directly on the EVM. See [SIP-3](https://github.com/sei-protocol/sips/blob/main/sips/sip-3.md) for the full migration context.
 </Info>
 
 ## Dual Address Support

 Sei utilizes two distinct address types:

@@ -23,7 +23,7 @@
 For more details on interoperability, explore our article
 [here](https://blog.sei.io/sei-v2-interoperability/).

 ## Virtual Machine Interoperability

 EVM and existing CosmWasm-based smart contracts co-exist on Sei, but live in
 different execution environments. This creates a challenge for users, who use
@@ -35,7 +35,7 @@
 already-deployed CosmWasm contracts to the EVM via precompiled contracts. New
 smart contracts on Sei should be deployed on the EVM directly.

 ## Precompile Contracts

 Sei precompiles are smart contracts embedded directly within the Sei EVM
 environment. They provide a gateway for users and developers to access Cosmos-SDK functions through the EVM RPC interface.
@@ -43,7 +43,7 @@
 For instructions on utilizing EVM precompiles, refer to the
 [Example Usage](/evm/precompiles/example-usage) section.

 ## Example Diagram

 ![Interoperability](/assets/interoperability.png)
 *Enabling seamless access to all tokens and contracts on Sei*
diff --git a/learn/dev-token-standards.mdx b/learn/dev-token-standards.mdx
@@ -5,7 +5,7 @@
 ---
 
 <Info>
-  **Use ERC20 / ERC721 / ERC1155 for new tokens.** Per [Proposal 115](https://www.mintscan.io/sei/proposals/115), CosmWasm code uploads and contract instantiations are disabled on Sei, so no new CW20 / CW721 / CW1155 tokens can be deployed. The CW standards described below are documented for users and developers interacting with already-deployed legacy contracts.
+  **Use ERC20 / ERC721 / ERC1155 for new tokens.** Per [Proposal 115](https://seistream.app/proposals/115), CosmWasm code uploads and contract instantiations are disabled on Sei, so no new CW20 / CW721 / CW1155 tokens can be deployed. The CW standards described below are documented for users and developers interacting with already-deployed legacy contracts.
 </Info>
 
 In this section, we delve into the various token standards supported on Sei.
@@ -17,7 +17,7 @@
 - [Sei Token](#sei-token)
 - [Smart Contract Tokens](#smart-contract-tokens)

 ## Sei Token

 The Sei token is the native token of the Sei blockchain, serving multiple roles
 within the ecosystem.
@@ -42,19 +42,19 @@

    `1 gwei = 1 nsei`

 ## 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.

 ### Smart Contract Tokens

 - **ERC20** (recommended): The ERC20 standard defines a common set of rules for
  fungible tokens on EVM-based blockchains. These tokens can be transferred,
   approved, and queried using standard functions. **Use ERC20 for any new
   fungible token on Sei.**
 - **CW20** (legacy only): The Cosmos-side fungible token standard. Per
-  [Prop 115](https://www.mintscan.io/sei/proposals/115), no new CW20 contracts
+  [Prop 115](https://seistream.app/proposals/115), no new CW20 contracts
   can be deployed. Existing CW20 tokens continue to function and can still have
   pointer contracts created for them.
 - **Interoperability and Pointer Contracts**:
@@ -78,7 +78,7 @@
   semi-fungible tokens. **Use these for any new NFT collection on Sei.**
 - **ERC2981**: Defines a royalty mechanism for NFTs, ensuring creators receive
   a percentage of sales.
-- **CW721 / CW1155** (legacy only): Per [Prop 115](https://www.mintscan.io/sei/proposals/115),
+- **CW721 / CW1155** (legacy only): Per [Prop 115](https://seistream.app/proposals/115),
   no new CW721 / CW1155 contracts can be deployed. Existing collections continue
   to function and can be surfaced on the EVM via pointer contracts.
 - **Interoperability**: Similar to fungible tokens, legacy CW NFT collections

diff --git a/learn/explorers.mdx b/learn/explorers.mdx
@@ -1,10 +1,10 @@
 ---
 title: 'Sei Blockchain Explorers Guide'
 sidebarTitle: 'Block Explorers'
 description: 'A comprehensive overview of block explorers for the Sei Network across different environments. Access tools for tracking transactions, analyzing addresses, and monitoring network activity.'
 keywords: ['sei blockchain explorer', 'transaction tracking', 'block analysis', 'blockchain monitoring', 'network statistics']
 ---
 ## What Is a Block Explorer?

 Rather than downloading the entire blockchain ledger, using a block explorer is
 the most common method to look up all kinds of useful on-chain information.
@@ -36,12 +36,11 @@
  Note: In rare cases, some information may be misinterpreted. Off-chain data should be used as a guide only.
 </Info>

 ## Sei Explorers

 <Tabs>
   <Tab title="mainnet (pacific-1)">
     - [Seiscan](https://seiscan.io) — A user-friendly block explorer for the Sei Pacific-1 mainnet.
-    - [Mintscan](https://www.mintscan.io/sei) — Comprehensive blockchain explorer and analytics platform for Sei mainnet.
     - [Seistream](https://seistream.app/) — Real-time transaction streaming and monitoring tool for Sei mainnet.
     - [NG Explorer](https://sei.explorers.guru) — Comprehensive blockchain explorer provided by Nodes Guru for Sei mainnet.
   </Tab>

diff --git a/learn/pointers.mdx b/learn/pointers.mdx
@@ -1,4 +1,4 @@
 ---
 title: 'Sei Pointer Contracts: Bridging EVM and Cosmos Environments'
 sidebarTitle: 'Pointer Contracts'
 description: "Understand how Sei's pointer contract system enables seamless asset movement between EVM and Cosmos environments, with implementation patterns for various token types."
@@ -6,7 +6,7 @@
 ---
 
 <Info>
-  **Pointer contracts are now primarily a legacy / migration tool.** Per [Proposal 115](https://www.mintscan.io/sei/proposals/115), no new CosmWasm contracts can be uploaded or instantiated on Sei, so the CW20 / CW721 / CW1155 → ERC20 / ERC721 / ERC1155 pointer flow only applies to already-deployed CosmWasm contracts. Native (Bank Module) pointers continue to work normally. For new tokens or NFTs, deploy ERC20 / ERC721 / ERC1155 contracts directly on the EVM.
+  **Pointer contracts are now primarily a legacy / migration tool.** Per [Proposal 115](https://seistream.app/proposals/115), no new CosmWasm contracts can be uploaded or instantiated on Sei, so the CW20 / CW721 / CW1155 → ERC20 / ERC721 / ERC1155 pointer flow only applies to already-deployed CosmWasm contracts. Native (Bank Module) pointers continue to work normally. For new tokens or NFTs, deploy ERC20 / ERC721 / ERC1155 contracts directly on the EVM.
 </Info>
 
 Pointer Contracts enable tokens to be used interoperably in both EVM and
@@ -14,7 +14,7 @@
 serves as an interpreter between the two "languages" used in either
 execution environment.

 ## Why Pointer Contracts

 ![Without Pointer Contracts](/assets/pointer-contracts-without.png)
 *A world without pointer contracts*
@@ -31,7 +31,7 @@
 ![With Pointer Contracts](/assets/pointer-contracts-simplified.png)
 *With pointer contracts, all tokens can be accessed by wallets of either environment*

 ## How Pointer Contracts Work

 ![How Pointer Contracts Work](/assets/pointer-contracts-how-it-works.png)
 *Pointer contracts enable seamless interoperability*