Feature: Add Custodial Wallet Persistence and KMS References

[3m1n3nc3]

Description

Add wallet and managed-key-reference models without storing plaintext Stellar secrets.

File Location

learnault-api/prisma/schema.prisma, wallet migration/types, KMS interface, and tests

Design Reference

API Roadmap Phase 1: Add Custodial Wallet Persistence and KMS References.

Dependencies

• Status: Blocked
• Blocked by: Feature: Replace Floating-Point Monetary Storage #64; Feature: Introduce Typed Status Enums and Transition Guards #65; Feature: Add Auditable Data Lifecycle and Archive Policy #66
• Blocks: Feature: Implement Idempotent Stellar Wallet Provisioning #90; Feature: Add Wallet Status Balance and History API #92

Tasks

• Add wallet user, network, custody, public key, status, and timestamps
• Add opaque managed-key/envelope metadata only
• Enforce intended wallet and public-key uniqueness
• Define provisioning, active, failed, export, migrated, and disabled transitions
• Add KMS interface and fake
• Test migration, uniqueness, transitions, redaction, and lifecycle

Acceptance Criteria

• Schema/DTO cannot store plaintext secret
• Uniqueness and transitions are enforced
• KMS references never enter ordinary responses
• Tests pass

Verification Evidence

• Attach schema threat review, migration, and secret-redaction tests

Difficulty

Advanced

[OluRemiFour]

Hi Maintainer,
Interested in working on this issue. I'll implement the requested changes and ensure everything is properly tested before submission.

[heymide]

I can take this on. I've gone through the details and will provide a well-tested solution aligned with the project standards.

[grantfox-oss]

🦊 GrantFox — @heymide has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #89)
2. Your PR will be reviewed by the learnault maintainers

Good luck! Track your progress on GrantFox.