You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Would like an easier way to bake a super macaroon.
Describe the solution you'd like
Add a config option to litd that will allow a super macaroon to be baked automatically on startup if it does not already exist.
Describe alternatives you've considered
Use the gRPC or CLI (https://lightning.engineering/api-docs/api/lit/proxy/bake-super-macaroon/) to do it manually after first creating the node. This is annoying because the user needs to coordinate a one time task to determine whether the macaroon exists or not and deal with yet another macaroon to control litd to then create the super macaroon.
Additional context
When using taproot assets, you often need to use both lnd and tapd RPC's and having to manage multiple connections to the same litd instance with multiple macaroons is a nuisance.
When creating docker containers for litd, normally the one time tasks of doing container setup are done in the Dockerfile, but litd does not normally start and create the node data until after the docker container is started and appropriate volumes are mounted. With this paradigm in mind, all other macaroons are automatically created on startup if they do not exist, and the super macaroon is an exception that I don't think we should have to deal with.
The text was updated successfully, but these errors were encountered:
Related: I noticed that litcli ln now seems to bake it's own super macaroon in some way. Is this right? Does it create a new super macaroon every time the CLI is used? With litcli ln calls I seem to be able to use them without passing the tapd macaroon. I also saw some error in the log file if I pass the wrong macaroon, it says it can't bake a super macaroon. However, I don't see where it is writing a super macaroon to disk anywhere, so maybe it just discards it at the end of the call. Any idea what litcli ln is doing?
Yes, we use connectSuperMacClient to create a super macaroon on the fly just for the connection to tapd (it's not stored anywhere). We can do that if we have access to the lit.macaroon which has that capability.
Though with some of the latest changes, you should also be able to create a super macaroon using the admin.macaroon from lnd.
Is your feature request related to a problem? Please describe.
Would like an easier way to bake a super macaroon.
Describe the solution you'd like
Add a config option to litd that will allow a super macaroon to be baked automatically on startup if it does not already exist.
Describe alternatives you've considered
Use the gRPC or CLI (https://lightning.engineering/api-docs/api/lit/proxy/bake-super-macaroon/) to do it manually after first creating the node. This is annoying because the user needs to coordinate a one time task to determine whether the macaroon exists or not and deal with yet another macaroon to control litd to then create the super macaroon.
Additional context
When using taproot assets, you often need to use both lnd and tapd RPC's and having to manage multiple connections to the same litd instance with multiple macaroons is a nuisance.
When creating docker containers for litd, normally the one time tasks of doing container setup are done in the Dockerfile, but litd does not normally start and create the node data until after the docker container is started and appropriate volumes are mounted. With this paradigm in mind, all other macaroons are automatically created on startup if they do not exist, and the super macaroon is an exception that I don't think we should have to deal with.
The text was updated successfully, but these errors were encountered: