feat: manage Cashu infrastructure and durable wallet operations #39
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
asmo/cashu-operator!39
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/cashu-infrastructure-wallets"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This extends Cashu Operator from mint deployment to independently managed Bitcoin, Lightning, payment processor, Ark and persistent wallet resources. Existing CashuMint manifests continue to select CDK when implementation is omitted; existing external and inline backends are preserved.
The commits separate API/schema contracts, managed mint integration, infrastructure controllers, native wallet execution, operator/admission wiring, and samples/documentation/verification receipts.
Bark incoming BOLT11 qualification exposed an upstream gross/net accounting error: a 10,000 sat payment credited 9,880 sat after fees. The pinned native patch now uses verified immutable net credit for both status and events; four actual-SDK tests pass, and readback of the same original paid request returns 9,880 sat with its original storage/identity retained. The failed original receipt is preserved.
Validation and exact receipts are in docs/implementation/status.md and compatibility/lock.json: generated schemas/RBAC and seven-CRD installer, Go unit/envtest/vet/build, zero-issue lint and strict MkDocs build; eight inspected local ARM64 native images with embedded source/dependency/patch records; native node/processor authentication and identity-retention tests; 12 complete native wallet/mint/backend financial combinations (eight CDK/Nutshell plus four Coco); four real-Lightning accepted/delayed lost-response Melt cases; native identity/restart and bounded original-operation recovery evidence. Final-image Pod replacements for all three wallet implementations also preserved original journals, private results, native database digests and independent settlement evidence without new financial operations.
New profiles are explicitly experimental and restricted to regtest. No image is published and no profile is production-qualified. Native AMD64, production recovery/upgrade qualification, funded BDK issuance/redemption, Ark rounds and the remaining experimental payment-method gates are listed individually. LDK's original outgoing BOLT12 attempt expired and is recorded as failed acceptance, without retry; the verified BOLT11 and incoming BOLT12 cases are recorded separately.
No production cluster or production financial state was changed. Capacity interruptions in the isolated k3d environment retained financial databases, identity Secrets, PVCs and original request IDs; native chain recovery procedures and their precise limits are documented in the receipts.
5a39cb7e25db53faaafeView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.