feat: nut-20 signature on mint witness #446
No reviewers
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!446
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "sign_mint"
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?
https://github.com/cashubtc/nuts/pull/188
@ -376,6 +376,105 @@ async fn test_fake_melt_change_in_quote() -> Result<()> {Ok(())}Would it be good to generate
secretinsidewallet.mint_quoteand also put it into the database there, so when you callwallet.mint()a few lines further, you don't need to providesecret.public_key()but could fetch it from the db again insidewallet.mint()?@ -376,6 +376,105 @@ async fn test_fake_melt_change_in_quote() -> Result<()> {Ok(())}Yeah I was thinking about this I initially did it this way to avoid storing the secret in the database but I don't think there is much benefit to that. Storing it in the cdk database makes it much easier for the implementer as they do not have to store or manage secrets so I will go this route as you suggest.
@ -376,6 +376,105 @@ async fn test_fake_melt_change_in_quote() -> Result<()> {Ok(())}addressed by 4051e493482bb385708bd3fbe42536f659d3c936