-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cashurpc #6
base: main
Are you sure you want to change the base?
cashurpc #6
Conversation
Added new protobuf definitions to the cashu RPC handling framework for managing states and state proofs. These message types will facilitate state checking and updating. Protobuf definitions include `PostCheckStateRequest`, `PostCheckStateResponse`, and `States` among others.
# Conflicts: # cmd/nutw/nutw.go # wallet/client.go # wallet/storage/bolt.go # wallet/storage/storage.go # wallet/wallet.go
# Conflicts: # cashu/cashu.go # cashu/nuts/nut01/nut01.go # cashu/nuts/nut02/nut02.go # cashu/nuts/nut03/nut03.go # cashu/nuts/nut04/nut04.go # cashu/nuts/nut05/nut05.go # cashu/nuts/nut06/nut06.go # cmd/nutw/nutw.go # go.mod # go.sum # mint/config.go # mint/db.go # mint/lightning/lnd.go # mint/mint.go # mint/server.go # wallet/storage/bolt.go # wallet/wallet.go
resolved changes from @callebtc
|
to what does it need to change? |
Tthe contact infos currently defined as an array of arrays with at most 2 elements. The first element represents the key, while the second element is the value. This should probably be update to an array of objects. current state:
desired state (already implemented in this PR)
I am going to open a new pull request in the nuts repository and propose the change to the protocol there. |
No description provided.