Sync workspace: config, docs, scripts, CI, operator rules, and submodule pointers.

- Update dbis_core, cross-chain-pmm-lps, explorer-monorepo, metamask-integration, pr-workspace/chains
- Omit embedded publish git dirs and empty placeholders from index

Made-with: Cursor

x402-api/README.md

@@ -1,6 +1,6 @@
 # x402 API (Chain 138–ready)
 
-Minimal Express API that accepts [x402](https://portal.thirdweb.com/x402) payments using thirdweb’s `settlePayment` and facilitator. Configured with a custom **Chain 138** definition; by default uses **Arbitrum Sepolia** and USDC so you can test without a Chain 138 token that supports permit.
+Minimal Express API that accepts [x402](https://portal.thirdweb.com/x402) payments using thirdweb’s `settlePayment` and facilitator. **Production target:** Chain **138** with **cUSDT V2 / cUSDC V2** (ERC-2612 / ERC-3009). **Default demo:** Arbitrum Sepolia + USDC so you can run the server without a permit-capable Chain 138 token in `.env`.
 
 ## Prerequisites
 
@@ -36,7 +36,7 @@ x402 requires the payment token to support **ERC-2612 permit** or **ERC-3009** w
 
 - **Default:** The API uses **Arbitrum Sepolia** and default USDC so you can test without custom chains.
 - **Alltra (651940) + USDC:** Set `X402_USE_ALLTRA=true` and `SERVER_WALLET_ADDRESS` in `.env`. Optional: `CHAIN_651940_RPC_URL`. Local verification is used; `THIRDWEB_SECRET_KEY` is not required for the Alltra path.
-- **Chain 138:** Set `X402_USE_CHAIN_138=true` and optionally `RPC_URL_138` once a Chain 138 token has permit/ERC-3009 (see [CHAIN138_X402_TOKEN_SUPPORT.md](../docs/04-configuration/CHAIN138_X402_TOKEN_SUPPORT.md)).
+- **Chain 138:** Set `X402_USE_CHAIN_138=true` and optionally `RPC_URL_138`. Use **V2** compliant USD token addresses from [CHAIN138_X402_TOKEN_SUPPORT.md](../docs/04-configuration/CHAIN138_X402_TOKEN_SUPPORT.md) in the API’s price config (V1 cUSDT/cUSDC are not x402-capable).
 
 Verification script for token support: