cmdruid / cmdruid/regtest-workbench

is grpc-port=<port> supported?

Open
#20 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
16
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Hi,

Still very noob so please ignore any mistake i make here. But it seems the way the GRPC API is now enabled is with either supplying --grpc-port= to lightningd, or adding grpc-port= to the config file.

This has been tried by modifying the config file, or hacking 03-lightning-setup.sh however things seem to break (no certs, and cl-rest seems to break).

Can this be supported? Also happy to flesh out some example projects [#10]. I've got the REST api to work with workbench, and the GRPC API to work on what is soon to be my main node. But not vice-versa.

Contributor guide

No contributing guide indexed for this repository

Research direction

Read 03-lightning-setup.sh and the configuration path it modifies, then reproduce enabling grpc-port=. Investigate the reported missing certificates and cl-rest failure while comparing the working REST and GRPC setups described in the issue. Done means GRPC support works without breaking certificates or cl-rest.

Written by the indexing model from the issue text.

Assessment

Tech stack
grpc, shell
Domain
api, devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.