Files
proxmox/docs/04-configuration/metamask/ALL_NEXT_STEPS.md
defiQUG bea1903ac9
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
Sync all local changes: docs, config, scripts, submodule refs, verification evidence
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-21 15:46:06 -08:00

4.5 KiB

All Next Steps (Chain 138 / MetaMask Integration)

Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation


Consolidated list of next steps for dual-chain provider, explorer, token-aggregation, Snap, and optional business/listing work.

Completion status (2026-01-30): Items 1-11 completed (provider test, integration script, builds, live deployment to VMID 5000). See PHASES_1-4_COMPLETE.md and DEPLOYMENT_COMPLETE_VMID5000.md.


Testing and integration (runnable now)

# Step Action
1 Provider integration test cd metamask-integration/provider && node test-integration.mjs (or npm run test:integration)
2 Full integration script cd metamask-integration && ./scripts/integration-test-all.sh
3 Optional: Explorer API Set EXPLORER_API_URL (e.g. http://localhost:8080) and re-run script; ensure explorer backend + DB are running
4 Optional: Token-aggregation API Set TOKEN_AGGREGATION_URL (e.g. http://localhost:3000) and re-run script when service + DB are running
5 Provider E2E (manual) Serve metamask-integration/examples/ (e.g. npx serve metamask-integration) and open provider-e2e.html with MetaMask

Fixes and builds

# Step Action
6 Token-aggregation build Fix TypeScript errors in smom-dbis-138/services/token-aggregation/src/config/canonical-tokens.ts so npm run build passes
7 Chain 138 Snap build In metamask-integration/chain138-snap/: run yarn install then yarn build; fix any peer/version issues if needed
8 Snap in MetaMask Flask Run yarn start in chain138-snap/, install Snap via the provided site (e.g. localhost:8000), test get_chain138_config and get_chain138_market_chains with token-aggregation apiBaseUrl

Explorer and token-aggregation (run with DB)

# Step Action
9 Explorer backend Configure DB, run explorer API, verify GET /api/config/networks and GET /api/config/token-list
10 Explorer Wallet page Run explorer frontend, open Wallet page, test “Add to MetaMask” for Chain 138, Mainnet, ALL Mainnet
11 Token-aggregation service After build fix: configure DB and env, run service, verify GET /api/v1/chains, GET /api/v1/tokens?chainId=138

Optional: Custom MetaMask Snap (roadmap)

# Step Action
12 Market data / pricing in Snap Have Snap call token-aggregation REST API for prices and token list; show in Snap UI
13 Swap flow Add or integrate a quote API for Chain 138; Snap requests quote → user approves → Snap returns tx to sign
14 Bridge flow Expose bridge API (CCIP + custom routes); Snap shows routes and builds tx for user to sign
15 Snap testing and distribution Test in MetaMask Flask; optionally submit to MetaMask Snap directory

See: SNAP_IMPLEMENTATION_ROADMAP.md


Optional: Native MetaMask USD and Consensys

# Step Action
16 CoinGecko submission Submit Chain 138 and tokens per docs/04-configuration/coingecko/COINGECKO_SUBMISSION_GUIDE.md to improve native USD in MetaMask
17 Consensys outreach Use metamask-integration/docs/CONSENSYS_OUTREACH_PACKAGE.md to request native Swaps/Bridge support for Chain 138

Optional: Smart Accounts / other

# Step Action
18 Paymaster (optional) Deploy Paymaster contract for gas abstraction if using Smart Accounts Kit
19 Market data for dApps Use token-aggregation REST API as single source for prices, volume, OHLCV in dApps and Snap; see REST_API_REFERENCE.md

Quick reference

Last updated: 2026-01-30