Files

defiQUG bee1d29d55 Add full Chain 138 integration: 8 steps, chain spec, app-ethereum config, docs

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

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

README.md

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

serializer.ethereum-chain138.ts

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

types.ethereum-chain138.ts

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

validation.ethereum-chain138.ts

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

walletApiAdapter.chain138.ts

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

Step 7 — Wallet API

wallet-api repo — If Ethereum family already supports multiple chainIds, add 138 to validation and routing. Otherwise use:
- validation.ethereum-chain138.ts — Zod schema allowing chainId 138.
- types.ethereum-chain138.ts — Transaction types.
- serializer.ethereum-chain138.ts — Serialize/deserialize for JSON-RPC.
- In packages/core/src/families/common.ts ensure FAMILIES includes the family; in validation.ts and serializer.ts add the new type to the union.
ledger-live repo — Bump @ledgerhq/wallet-api-core, -server, -client. Add or extend walletApiAdapter.chain138.ts in libs/ledger-live-common/src/families/ethereum/walletApiAdapter.ts so WalletAPI transactions with chainId 138 map to LL transactions. Do not edit the generated generated/walletApiAdapter.ts by hand; add the source adapter and run the sync-families-dispatch script.
Changelog — pnpm changelog, create changeset for @ledgerhq/wallet-api-core (minor), open PR.