Skip to content

Conversation

@mfw78
Copy link
Member

@mfw78 mfw78 commented Dec 8, 2025

Summary

  • Define pluggable account provider architecture for Nexum
  • AccountProvider trait interface for diverse account types
  • Support for native, delegated, multisig, threshold, smart contract, and shielded accounts
  • Provider determines address; delegation keys derived from address using NXP-2 methods
  • Provider-specific configuration schemas for each account type
  • Migration workflows for various account types
  • WASM module support for future extensibility

Context

NXP-5 introduces the "Account Provider" abstraction, recognizing that accounts can come from many sources beyond the native HD wallet:

Provider Type Description
native Standard BIP-44 derived accounts
delegated EIP-7702 delegated EOAs
multisig Multi-signature wallets (Safe, etc.)
threshold Threshold signature schemes
smart_contract ERC-4337 or custom contract accounts
shielded Privacy-preserving accounts

The provider determines the 20-byte address; any required delegation keys are then derived from that address.

Related to nxm-rs/pm#3 (EPIC 0.0)

Test plan

  • Verify Zola builds successfully
  • Review AccountProvider trait interface
  • Confirm provider configuration schemas are complete
  • Verify migration workflow examples

Define pluggable account provider architecture for Nexum:
- AccountProvider trait interface for diverse account types
- Support for native, delegated, multisig, threshold, smart contract, and shielded accounts
- Provider determines address; delegation keys derived from address
- Provider-specific configuration schemas
- Migration workflows for various account types
- WASM module support for extensibility

Related to nxm-rs/pm#3 (EPIC 0.0)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants