We should probably generate and track the PaymentHash and PaymentSecret that the wallet user uses in the invoice. This enables the library to help with fee verification described in #61 .
We will need to set min_value_msat, invoice_expiry_delta_secs, and min_final_cltv_expiry_delta when creating the inbound payment for the user. I'm not sure if there are sensible defaults we should use? Could expose all three in the configuration for the wallet user.
We should probably generate and track the PaymentHash and PaymentSecret that the wallet user uses in the invoice. This enables the library to help with fee verification described in #61 .
We will need to set
min_value_msat,invoice_expiry_delta_secs, andmin_final_cltv_expiry_deltawhen creating the inbound payment for the user. I'm not sure if there are sensible defaults we should use? Could expose all three in the configuration for the wallet user.