Skip to content

Conversation

@mfw78
Copy link
Member

@mfw78 mfw78 commented Dec 8, 2025

Summary

  • Define Swarm-based storage architecture for Nexum
  • Indexed feeds for versioned storage with time-travel capability
  • Batch owner key derivation options (BIP-44 on-card vs EIP-1581 exportable)
  • Feed structure with domain-separated topics for each storage unit
  • Encryption layer using deterministic keys from seed
  • FeedUpdate protobuf structure (without content_hash - Swarm BMT verifies integrity)

Context

NXP-4 specifies how Nexum stores identity metadata on Swarm. Key innovations:

  • Indexed feeds: Every storage ref uses indexed feeds, enabling historical state lookup (time-travel/versioning)
  • Batch owner options: Supports both on-card signing (BIP-44) for security or EIP-1581 exportable keys for higher throughput
  • Storage unit topics: Each metadata type (identity, accounts, preferences, contacts, audit logs) has its own feed

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

Test plan

  • Verify Zola builds successfully
  • Review Swarm feed structure for correctness
  • Confirm indexed feed usage enables proper versioning
  • Verify encryption key derivation examples

Define Swarm-based storage architecture for Nexum:
- Indexed feeds for versioned storage with time-travel capability
- Batch owner key derivation options (BIP-44 vs EIP-1581)
- Feed structure with domain-separated topics
- Encryption layer using deterministic keys
- Storage unit topics for each metadata type
- FeedUpdate protobuf without content_hash (Swarm BMT verifies)

Closes nxm-rs/nexum#87
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.

docs: design storage architecture

2 participants