Feature: allow multiple payment backends #1465
Labels
No labels
DB & Storage
Deployment
Error Handling & Logging
Maintenance
Payment Backend
backport
backport v0.13.x
backport v0.14.x
backport v0.15.x
bindings
blocked
bug
cdk-sql
ci
cli
deps
documentation
duplicate
enhancement
good first issue
help wanted
invalid
keep-open
ldk-node-ui
migrations
mint
mutation-testing
needs rebase
needs review
new nut
nut change
question
ready
rust-version
rustfmt
stacked hold
stale
testing
wallet
weekly-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
cashubtc/cdk#1465
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Currently, cdk-mintd is designed to allow a single lightning backend. Expanding this to allow multiple concurrent backends would enable:
Solution to this could be allowing a arrays of
[ln]backendswe should add this before #1127
This is a limitation of cdk not mintd. cdk mint has the payment processors as a hashmap of the unit/method pair being the key (
github.com/cashubtc/cdk@54a0b54bea/crates/cdk/src/mint/mod.rs (L70)). So If we were to support multiple backends for a unit method pair we would have to change this and likely implement some method of selecting which one to use.This is a limitation of mintd config and already supported by cdk, so we should add support for this and should not be to difficult.
I am not against supporting multiple backends for a single unit/method paid but I think it would be a bigger refactor and we should split them.
Array of ln backends makes sense. But why do we need multiple database blocks?