NUT-17: Websockets #203
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#203
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?
https://github.com/cashubtc/nuts/pull/98#discussion_r1655550190
@thesimplekid can I work on this? I'm rewriting this in my nostr relayer, and I successfully did it in my tiny ledger database (which has a long polling HTTP interface), so I'm quite familiar with how to solve it.
Let me know if you already started so I can find another thing to work on.
Cheers,
Hey @crodas,
Sure go for it thank you
@crodas Have you started on this? How is it coming?
@thesimplekid I'm a few days away (perhaps a week) from having a working prototype. Is the timeline ok?
Yes thats fine. Feel free to publish a draft pr if you want me to take a look at anything even before its working.
@crodas I'm going to take this back.
@thesimplekid did you have time to take a look at my WIP PR? I'm extending it and add more tests to both the nut17 implementation, the subscription mod and I'll add it the WebSocket handler.
PR https://github.com/cashubtc/cdk/pull/394 has been merged
Should this issue be closed or is there still something left to be done?
#394 Is mint only so we do still need wallets support, @crodas said he would work on that so lets close this and ill open another tracking issue for that.
Thanks tracking this.