We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Im on mutinynet using the ln address provided by their faucet and it's not working.
Im doing the following logic:
const payRequest: LnPayRequest = { paymentInfo: "lnurl1dp68gurn8ghj7enpw43k2apwd46hg6tw09hx2apwvdhk6tmpwp5j7mrww4excac7utxd6", amountMsat: 5 * 1000, finishInBackground: true }; return await fedimint.ln.pay(payRequest);
and it's returning: LOG [Error: POST request failed. Status: 500, Body: Something went wrong: Unexpected response from lnurl: LnUrlWithdrawResponse(WithdrawalResponse { default_description: "Mutinynet Faucet", callback: "https://faucet.mutinynet.com/api/lnurlw/callback", k1: "k1", max_withdrawable: 10000000000, min_withdrawable: None, tag: WithdrawRequest })]
LOG [Error: POST request failed. Status: 500, Body: Something went wrong: Unexpected response from lnurl: LnUrlWithdrawResponse(WithdrawalResponse { default_description: "Mutinynet Faucet", callback: "https://faucet.mutinynet.com/api/lnurlw/callback", k1: "k1", max_withdrawable: 10000000000, min_withdrawable: None, tag: WithdrawRequest })]
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Im on mutinynet using the ln address provided by their faucet and it's not working.
Im doing the following logic:
and it's returning:
LOG [Error: POST request failed. Status: 500, Body: Something went wrong: Unexpected response from lnurl: LnUrlWithdrawResponse(WithdrawalResponse { default_description: "Mutinynet Faucet", callback: "https://faucet.mutinynet.com/api/lnurlw/callback", k1: "k1", max_withdrawable: 10000000000, min_withdrawable: None, tag: WithdrawRequest })]
The text was updated successfully, but these errors were encountered: