Mint RPC Server #476
Assignees
Labels
Comments
2 tasks
crodas
added a commit
to crodas/cdk
that referenced
this issue
Dec 20, 2024
The SignatoryManager manager provides an API to interact with keysets, private keys, and all key-related operations, offering segregation between the mint and the most sensible part of the mind: the private keys. Although the default signatory runs in memory, it is completely isolated from the rest of the system and can only be communicated through the interface offered by the signatory manager. Only messages can be sent from the mintd to the Signatory trait through the Signatory Manager. This pull request sets the foundation for eventually being able to run the Signatory and all the key-related operations in a separate service, possibly in a foreign service, to offload risks, as described in cashubtc#476. The Signatory manager is concurrent and deferred any mechanism needed to handle concurrency to the Signatory trait.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We would like to add an RPC server to the mint so that a mint operator has both better control of mint settings with the ability to change these settings without restarting and changing the config file as currently required. This should also include methods that give the mint operator better visibility into their mint operator in order to better mange their mint and lightning liquidity,
Below is list of methods that I think should be supported.
MInt
Lightning
cc: @davidcaseria @crodas
The text was updated successfully, but these errors were encountered: