feat: add signing component registry and firmware-gated reqs

[yilmazbahadir]

📝 Summary

This PR introduces a plugin-owned signing-component registry for chain plugins and removes broad SDK helper coupling when adding/migrating chains.

It includes:

• plugin-owned definitions/requirements with explicit minFirmware gating
• transactional registration behavior in SDK runtime
• signer migration for evm, solana, cosmos, xrp
• compatibility fixes for existing DeviceContext integrations
• terminology/API refactor from primitive to signing component
• lint/wiring cleanup commits needed to stabilize and pass checks

🔧 Context / Implementation

• Added chain-core signing component model:
  • SigningComponentKind, SigningComponentDefinition, SigningComponentRequirement
  • ChainSigningSuite
  • signingSuite?: ChainSigningSuite on ChainPlugin
• Replaced primitive registry with signing component registry in chain-core:
  • createSigningComponentRegistry, preflight, atomic register, resolve, resolveOrThrow, reverseResolve, has, list, reset
  • collision semantics retained for name/code conflicts
• Replaced SDK primitive lifecycle with signing component lifecycle:
  • lazy/idempotent seeding from EXTERNAL.SIGNING.{HASHES,CURVES,ENCODINGS}
  • plugin preflight/register helpers
  • fail-closed requirement shape validation (minFirmware required)
• Made registration transactional and safe:
  • seed -> preflight -> register plugin -> commit definitions
  • rollback on failure
  • discovery path uses same registration flow
• Added plugin-owned definition cleanup on unregister:
  • tracks plugin-owned signing component definitions
  • unregisterChain() removes owned definitions and prevents stale conflicts on re-register
• Added firmware requirement enforcement in useChain() before signer creation.
• Setup now seeds signing components early (idempotent).
• Migrated lattice signers to context.resolveSigningComponent(...):
  • evm, solana, cosmos, xrp
• Preserved compatibility for older contexts:
  • signers now fallback to constants.EXTERNAL.SIGNING when resolver is absent
• Kept explicit request-time EIP-7702 firmware gate in EVM signer (>= 0.18.0).
• Tightened firmware typing (packages/types/src/firmware.ts) by removing permissive index signatures from signing maps.
• GET_ADDR_FLAGS and getFwVersionConst() behavior remain unchanged in this PR.

Concrete developer experience — what a new chain plugin author writes:

export const latticePlugin: ChainPlugin<LatticeNewChainContext> = {
  chainId: 'newchain',
  device: 'lattice',
  module: newchain,
  createSigner: (context) => createLatticeNewChainSigner(context),
  signingSuite: {
    definitions: [
      { kind: 'encoding', name: 'NEWCHAIN', code: 9 },
      { kind: 'hash', name: 'BLAKE2B', code: 4 },
    ],
    requirements: [
      { kind: 'curve', name: 'ED25519', minFirmware: [0, 14, 0] },
      { kind: 'encoding', name: 'NEWCHAIN', minFirmware: [0, 20, 0] },
      { kind: 'hash', name: 'BLAKE2B', minFirmware: [0, 20, 0] },
    ],
  },
};

// Inside signer:
const curveCode = context.resolveSigningComponent('curve', 'ED25519');
const encodingCode = context.resolveSigningComponent('encoding', 'NEWCHAIN');
const hashCode = context.resolveSigningComponent('hash', 'BLAKE2B');

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/gridplus-sdk@728

commit: 4909666

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d308cf86e2

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".