Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Mint RPC Server #476

Open
thesimplekid opened this issue Nov 27, 2024 · 0 comments
Open

Mint RPC Server #476

thesimplekid opened this issue Nov 27, 2024 · 0 comments
Assignees
@thesimplekid
Labels
enhancement New feature or request mint

Comments

@thesimplekid
Copy link
Collaborator

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

  • Update NUT06 info description etc
  • Rotate keyset
  • View total issued ecash
  • View total spent ecash
  • View total outstanding (difference of the above two)
  • Issued, spent and outstanding per keyset
  • Disable/Enable mint and melt

Lightning

  • Open channel
  • Close channel
  • Balance view

cc: @davidcaseria @crodas
@thesimplekid thesimplekid added enhancement New feature or request mint labels Nov 27, 2024
@crodas crodas mentioned this issue Dec 16, 2024
Merged
2 tasks
crodas added a commit to crodas/cdk that referenced this issue Dec 20, 2024
@crodas
Introduce a SignatoryManager service.
9911511 
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.
@crodas crodas mentioned this issue Dec 20, 2024
Draft
6 tasks
crodas added a commit to crodas/cdk that referenced this issue Jan 14, 2025
@crodas
Introduce a SignatoryManager service.
45d8352 
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.
crodas added a commit to crodas/cdk that referenced this issue Jan 14, 2025
@crodas
Introduce a SignatoryManager service.
a11988b 
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.
crodas added a commit to crodas/cdk that referenced this issue Jan 14, 2025
@crodas
Introduce a SignatoryManager service.
a8c289e 
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.
@thesimplekid thesimplekid assigned thesimplekid and unassigned crodas Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thesimplekid thesimplekid

Labels
enhancement New feature or request mint
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@crodas @thesimplekid