Skip to main content
Quotes were off, as noted by Vincenzo; added 4 characters in body
Source Link
Antoine Poinsot
  • 9.1k
  • 2
  • 18
  • 36

Using C-lightning RPC interface you can avoid specifying optional parameters, just by not specifying them. Using the console in Spark wallet shouldn't be different.

You can refer to a specific optional argument by its name while omitting the others by using the -k command line option of lightning-cli. So for the example your gave:

lightning-cli -k getroute id=024...a67 msatoshi=1000000sat riskfactor=10 exclude='[“564334x877x1/0”,“564195x1292x0/1”]'
lightning-cli -k getroute id=024...a67 msatoshi=1000000sat riskfactor=10 exclude='["564334x877x1/0","564195x1292x0/1"]'

I don't know if Spark provides a way to refer to options by their name. You can always just specify the default of the options as documented.

Using C-lightning RPC interface you can avoid specifying optional parameters, just by not specifying them. Using the console in Spark wallet shouldn't be different.

You can refer to a specific optional argument by its name while omitting the others by using the -k command line option of lightning-cli. So for the example your gave:

lightning-cli -k getroute id=024...a67 msatoshi=1000000sat riskfactor=10 exclude='[“564334x877x1/0”,“564195x1292x0/1”]'

I don't know if Spark provides a way to refer to options by their name. You can always just specify the default of the options as documented.

Using C-lightning RPC interface you can avoid specifying optional parameters, just by not specifying them. Using the console in Spark wallet shouldn't be different.

You can refer to a specific optional argument by its name while omitting the others by using the -k command line option of lightning-cli. So for the example your gave:

lightning-cli -k getroute id=024...a67 msatoshi=1000000sat riskfactor=10 exclude='["564334x877x1/0","564195x1292x0/1"]'

I don't know if Spark provides a way to refer to options by their name. You can always just specify the default of the options as documented.

added 356 characters in body
Source Link
Antoine Poinsot
  • 9.1k
  • 2
  • 18
  • 36

Not sure about how Spark Wallet handles this. Using C-lightning RPC interface you can avoid specifying optional parameters, just by not specifying them. Using the console in Spark wallet shouldn't be different.

For your usage question, pleaseYou can refer to a specific optional argument by its name while omitting the others by using the the manual-k command line option of lightning-cli. It specifies that exclude must be a JSON array and even gives you anSo for the example your gave:

[“564334x877x1lightning-cli -k getroute id=024...a67 msatoshi=1000000sat riskfactor=10 exclude='[“564334x877x1/0”,“564195x1292x0/1”]1”]'

I don't know if Spark provides a way to refer to options by their name. You can always just specify the default of the options as documented.

Not sure about how Spark Wallet handles this. Using C-lightning RPC interface you can avoid specifying optional parameters, just by not specifying them.

For your usage question, please refer to the manual. It specifies that exclude must be a JSON array and even gives you an example:

[“564334x877x1/0”,“564195x1292x0/1”]

Using C-lightning RPC interface you can avoid specifying optional parameters, just by not specifying them. Using the console in Spark wallet shouldn't be different.

You can refer to a specific optional argument by its name while omitting the others by using the -k command line option of lightning-cli. So for the example your gave:

lightning-cli -k getroute id=024...a67 msatoshi=1000000sat riskfactor=10 exclude='[“564334x877x1/0”,“564195x1292x0/1”]'

I don't know if Spark provides a way to refer to options by their name. You can always just specify the default of the options as documented.

Source Link
Antoine Poinsot
  • 9.1k
  • 2
  • 18
  • 36

Not sure about how Spark Wallet handles this. Using C-lightning RPC interface you can avoid specifying optional parameters, just by not specifying them.

For your usage question, please refer to the manual. It specifies that exclude must be a JSON array and even gives you an example:

[“564334x877x1/0”,“564195x1292x0/1”]