Skip to content

docs: define derivation path standards #86

@mfw78

Description

@mfw78

Context

Nexum must define standard derivation paths for multiple key types: smart account keys, storage keys (for Swarm), and deterministic discovery mechanisms. These standards enable secure, reproducible key generation across different use cases.

Considerations

This specification should address the following considerations:

  • BIP-32/BIP-44 compliance and extensions
  • Derivation paths for EOA wallets
  • Derivation paths for smart account control keys (delegation keys)
  • Derivation paths for system keys (registry framework)
  • Derivation paths for identity-specific keys (profile isolation)
  • Deterministic discovery of derived accounts
  • Account gap limits and scanning
  • Hardened vs non-hardened derivation choices
  • Compatibility with existing wallet standards
  • Integration with Keycard derivation capabilities

Solution

Documented in NXP-1: Derivation Path Standards.

Key features:

  • Index Space Partitioning: SYSTEM_OFFSET (2³⁰) separates user accounts from system keys
  • Delegation Keys: Zero-metadata discovery for multisig/EIP-7702 delegation
  • System Key Registry: Framework for NXP specifications to allocate reserved indices
  • BIP-32 Compliance: Deterministic retry algorithm for edge cases

Dependencies

Depends on (Phase 2):

Blocks:

Out of Scope

  • Implementation of cryptographic primitives
  • Keycard-specific implementation details
  • Account recovery mechanisms
  • Specific system key allocations (defined by separate NXPs, e.g., NXP-2 for storage)

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    docsDocumentation is wrong or missing.featureNew capability that doesn't exist yet.p1-brokenActually broken. Fix this week.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions