feat: EIP-712 signature requests (WALLET-1251)

[ost-ptk]

WALLET-1251 — EIP-712 signature requests

Jira: https://make-software.atlassian.net/browse/WALLET-1251 (epic WALLET-1250, release CW 2.5.0)

Adds the EIP-712 typed-data signing flow: a dapp calls provider.signTypedData(params, publicKey), the user sees a window with Domain/Message blocks and signs with a software key, and the dapp receives the signature. All domain logic lives in casper-wallet-core (eip712Repository); the wallet renders the prepared domainRows/messageRows and signs.

How it works

dapp.signTypedData(params, pubKey)
  → content sdk.ts → signTypedDataRequest
  → background: dispatch typedData into redux (vault slice) + openWindow(SignatureRequestEip712)
  → SignEip712Page: reads typedData from redux → useFetchDataForEip712Request → eip712Repository.prepareSignatureRequest
  → renders Domain/Message rows; handleSign → eip712Repository.signTypedData → signTypedDataResponse
  → content/index.ts proxies the response to the page → dapp receives SignTypedDataResult

Changes

Dependencies / compilation

• casper-js-sdk 5.0.10 → 5.0.12 (deduplicates with the core copy), date-fns 2.30 → ^4 (fixes the enUS import in core)
• Deep type imports casper-js-sdk/dist/... moved to the package root (5.0.12 no longer ships .js at those paths)

SDK / protocol (src/content/)

• sdk.ts: signTypedData(params, signingPublicKeyHex) method
• sdk-method.ts: signTypedDataRequest/Response/Error actions
• sdk-types.ts: SignTypedDataParams, SignTypedDataResult, EIP712HashArtifacts (contract aligned with the playground)
• index.ts: whitelist response/error in the content proxy (otherwise the call hangs)

Background / redux

• vault slice: eip712ById field + eip712PayloadReceived + selectEip712JsonById (follows the deploy jsonById pattern)
• WindowApp.SignatureRequestEip712 + RouterPath.SignEip712
• signTypedDataRequest handler in background/index.ts

UI (src/apps/signature-request/pages/sign-eip712/)

• useFetchDataForEip712Request hook
• Eip712DisplayRow — presentation → component mapper (AccountInfoRow / ContractInfoRow / Hash / text), all rows lay out label↔value via SpaceBetweenFlexRow
• Eip712NetworkRow — Network with icon (reuses NetworkIconColor + the resolver from sign-transaction)
• SignEip712Content — Domain + Message blocks
• SignEip712Page — fetch + sign + cancel, route wired up

Ledger guard

• Ledger accounts are rejected on the EIP-712 signing page (mirrors the existing decrypt-message pattern): an early signingAccount.hardware === HardwareWalletType.Ledger check sends signTypedDataError back to the dapp and throws, so the user sees the ErrorBoundary screen. New ErrorMessages.signTypedData.LEDGER_NOT_SUPPORTED constant.

Testing

• npm run ci-check — green (format + lint + tsc + test)
• npm run build:chrome — successful
• Manual e2e via the Casper Wallet playground: sign/cancel, Domain/Message rendering, ContractInfoRow for a real package hash, and the Ledger-account rejection path

Notes

• Ledger: EIP-712 typed-data signing is intentionally not supported on Ledger hardware wallets (confirmed with the feature owner). Software-key signing only; Ledger accounts are rejected before reaching the signing step.
• Package hash when the package is unresolved: when core cannot resolve a contract package, the row arrives as presentation: 'string' and the hash is shown in full. Recommendation for core — force presentation: 'hash' for contract_package_hash. With a real package hash the row renders as ContractInfoRow correctly.

🤖 Generated with Claude Code

[Comp0te]

👍