Skip to content

[bug]: remove irrelevant options from litcli ln addinvoice #1121

@ZZiigguurraatt

Description

@ZZiigguurraatt
431de8e23386:/$ litcli ln addinvoice -h
NAME:
   litcli ln addinvoice - Add a new invoice to receive Taproot Assets.

USAGE:
   litcli ln addinvoice [command options] [--asset_id=X | --group_key=X] --asset_amount=Y [--rfq_peer_pubkey=Z] 

CATEGORY:
   Invoices

DESCRIPTION:
   
  Add a new invoice, expressing intent for a future payment, received in
  Taproot Assets.
  

OPTIONS:
   --memo value                                a description of the payment to attach along with the invoice (default="")
   --preimage value                            the hex-encoded preimage (32 byte) which will allow settling an incoming HTLC payable to this preimage. If not set, a random preimage will be created.
   --amt value                                 the amt of satoshis in this invoice (default: 0)
   --amt_msat value                            the amt of millisatoshis in this invoice (default: 0)
   --description_hash value                    SHA-256 hash of the description of the payment. Used if the purpose of payment cannot naturally fit within the memo. If provided this will be used instead of the description(memo) field in the encoded invoice.
   --fallback_addr value                       fallback on-chain address that can be used in case the lightning payment fails
   --expiry value                              the invoice's expiry time in seconds. If not specified, an expiry of 86400 seconds (24 hours) is implied. (default: 0)
   --cltv_expiry_delta value                   The minimum CLTV delta to use for the final hop. If this is set to 0, the default value is used. The default value for cltv_expiry_delta is configured by the 'bitcoin.timelockdelta' option. (default: 0)
   --private                                   encode routing hints in the invoice with private channels in order to assist the payer in reaching you. If amt and amt_msat are zero, a large number of hints with these channels can be included, which might not be desirable.
   --amp                                       creates an AMP invoice. If true, preimage should not be set.
   --blind                                     creates an invoice that contains blinded paths. Note that invoices with blinded paths will be signed using a random ephemeral key so as not to reveal the real node ID of this node.
   --min_real_blinded_hops --blind             The minimum number of real hops to use in a blinded path. This option will only be used if --blind has also been set. (default: 0)
   --num_blinded_hops --blind                  The number of hops to use for each blinded path included in the invoice. This option will only be used if --blind has also been set. Dummy hops will be used to pad paths shorter than this. (default: 0)
   --max_blinded_paths --blind                 The maximum number of blinded paths to add to an invoice. This option will only be used if --blind has also been set. (default: 0)
   --blinded_path_omit_node value              The pub key (in hex) of a node not to use on a blinded path. The flag may be specified multiple times.
   --blinded_path_incoming_channel_list value  The chained channels specified via channel id (separated by commas), starting from a channel which points to the self node.
   --asset_id value                            the asset ID of the asset to receive; cannot be used at the same time as --group_key
   --group_key value                           the group key of the asset to receive; cannot be used at the same time as --asset_id
   --asset_amount value                        the amount of assets to receive (default: 0)
   --rfq_peer_pubkey value                     (optional) the public key of the peer to ask for a quote when converting from assets to sats for the invoice; must be set if there are multiple channels with the same asset ID present
   
431de8e23386:/$

shows a lot of options that are not relevant to taproot assets invoices. For example

  1. --private seems irrelevant because the hop hints always exist in taproot asset invoices and are done as part of the RFQ process.
  2. --fallback_addr I don't think works with taproot assets
  3. --amp I don't think works with taproot assets
  4. --blind and all related options I don't think work with taproot assets.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingp3

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions