Files

Deploy to Phoenix / deploy (push) Has been cancelled

Details

docs: Ledger Live integration, contract deploy learnings, NEXT_STEPS updates

- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands
- CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround
- CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check
- NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere
- MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates
- LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-02-12 15:46:57 -08:00

2.9 KiB

Raw Blame History

explorer.d-bis.org

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

Integration of the dual-chain provider, token list, and Wallet page with the live explorer at https://explorer.d-bis.org.

What is integrated

Component	Integration
Provider	`TOKEN_LIST_URL` = `https://explorer.d-bis.org/api/config/token-list`; chain `blockExplorerUrls` = `https://explorer.d-bis.org`.
Explorer frontend	Wallet page at `/wallet`; Add to MetaMask (Chain 138, Mainnet, ALL Mainnet); token list URL shown uses `NEXT_PUBLIC_API_URL` or same origin (production: `https://explorer.d-bis.org`).
Explorer backend	Must serve `GET /api/config/networks` and `GET /api/config/token-list` (embedded JSON). See `explorer-monorepo/backend/api/rest/config.go` and `routes.go`.

Production URLs

Explorer (UI): https://explorer.d-bis.org/
Wallet page: https://explorer.d-bis.org/wallet
Token list (MetaMask): https://explorer.d-bis.org/api/config/token-list
Networks config (API): https://explorer.d-bis.org/api/config/networks

Backend requirement

For the token list and networks config to work on the live site, the explorer backend (Go API) must be deployed and reachable at the same origin (or CORS-enabled) with these routes:

GET /api/config/networks — returns DUAL_CHAIN_NETWORKS.json (Chain 138, 1, 651940).
GET /api/config/token-list — returns DUAL_CHAIN_TOKEN_LIST.tokenlist.json (Uniswap token list format).

If the current deployment at explorer.d-bis.org uses a different stack (e.g. Blockscout-only) and does not run the Go API with these handlers, either:

Deploy the Go API (explorer-monorepo/backend/api/rest) and reverse-proxy /api/config/* to it, or
Proxy /api/config/networks and /api/config/token-list to a server that serves the embedded JSON.

Current live check: GET https://explorer.d-bis.org/api/config/networks may return 400 if the deployed stack does not yet serve our Go API routes. Once the backend (or proxy) serves the config routes, run:

EXPLORER_API_URL=https://explorer.d-bis.org ./scripts/integration-test-all.sh

and expect GET /api/config/networks OK and GET /api/config/token-list OK.

Frontend env (production)

For production at https://explorer.d-bis.org, set (or leave empty for same-origin):

NEXT_PUBLIC_API_URL=https://explorer.d-bis.org

So the Wallet page shows token list URL: https://explorer.d-bis.org/api/config/token-list.

Test all (without live API)

If the live API is not yet deployed, run tests without EXPLORER_API_URL:

cd metamask-integration
pnpm run run-all

Provider test and config JSON validation pass; Explorer API and token-aggregation API checks are skipped unless URLs are set.

Last updated: 2026-01-30

2.9 KiB Raw Blame History