d-bis/smom-dbis-138
4
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

chore: sync submodule state (parent ref update)

Browse Source 
Made-with: Cursor
This commit is contained in:
defiQUG
2026-03-02 12:14:09 -08:00
parent 50ab378da9
commit 5efe36b1e0
1100 changed files with 155024 additions and 8674 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
docs/operations/integrations/METAMASK_BRIDGE_SWAP.md
View File

@@ -8,6 +8,27 @@ ChainID 138 is **not** currently supported in MetaMask's native Swaps and Bridge
## Swaps (In-Wallet Aggregator)
### Known error: "No XChain Swaps native asset found for chainId: eip155:138"
If you see this error in MetaMask while connected to Chain 138, it can appear when clicking **Send** or **Swap** (depending on MetaMask version; the Send flow sometimes uses the same LavaPack/XChain code):
```
Error: No XChain Swaps native asset found for chainId: eip155:138
at LavaPack.loadBundle.s.getNativeAssetForChainId (...)
```
**Cause:** MetaMask’s LavaPack/XChain logic only supports a fixed list of chains. Chain 138 is not in that list. In some versions, the **Send** UI triggers this path (e.g. for gas or asset lookup), so the error appears on Send as well as Swap. This is not about using eth_sendTransaction vs eth_sendRawTransaction (the error happens in the UI before any RPC), and it is not caused by the Chain 138 Snap or its allowlisting—the extension uses its own LavaPack list and does not ask Snaps for native asset.
**If it happens on Send:**
- **Recommended — Chain 138 Send page:** Use the **Chain 138 Snap companion site Send page** (e.g. `/send` on the deployed Snap site). This page uses `eth_sendTransaction` from the dApp context, bypassing MetaMask's broken Send UI—connect MetaMask, open the Send page, ensure Chain 138, enter recipient and amount, then click Send.
- **Alternative — Different entry point:** Try sending from the account/balance view (e.g. click the balance or “Send” from the asset list) instead of the home “Send” button, in case your MetaMask version uses a different code path.
- **Alternative — Another wallet:** Use a wallet that supports custom EVM networks (e.g. add Chain 138 via Chainlist) and does not rely on this backend for Send.
**If it happens on Swap:** Do **not** use the in-wallet Swaps button for Chain 138. Use a DEX that supports Chain 138 (see [Workaround: Use DEX UI](#workaround-use-dex-ui) below).
Receiving and using dApps on Chain 138 work normally; the failure is in MetaMask’s own Send/Swap UI for unsupported chains.
### Current Limitation
MetaMask Swaps supports a fixed set of networks:
@@ -79,9 +100,16 @@ For bridges to work with ChainID 138:
## Buy/Sell (Fiat On/Off-Ramp)
### Priority flows (mainnet liquidity + ramps)
**Recommended user flows** (operator must fund mainnet liquidity first):
- **On-ramp:** Buy on Ethereum Mainnet via ramp → bridge to Chain 138. See [MAINNET_RAMP_USER_FLOWS.md](../../../../docs/04-configuration/MAINNET_RAMP_USER_FLOWS.md).
- **Off-ramp:** Bridge Chain 138 → Mainnet → sell on mainnet via ramp. See [MAINNET_LIQUIDITY_AND_RAMPS_PRIORITY.md](../../../../docs/00-meta/MAINNET_LIQUIDITY_AND_RAMPS_PRIORITY.md) and [MAINNET_RAMP_USER_FLOWS.md](../../../../docs/04-configuration/MAINNET_RAMP_USER_FLOWS.md).
### Current Limitation
MetaMask's on-/off-ramp partners only support certain chains/tokens. ChainID 138 assets are not currently supported.
MetaMask's on-/off-ramp partners only support certain chains/tokens. ChainID 138 assets are not currently supported natively.
### Workaround: Bridge from Supported Chains