Not sure the best way to fix it if it's an lnbits mint, this info endpoint should return a public key for the mint.

https://obsessedjerky7.lnbits.com/cashu/api/v1/L4bNfiBtTyhEpZWdt6QTb4/v1/info

We still add the mint, but just point it out to try to get you to follow the spec.

Reply to this note

Please Login to reply.

Discussion

Yes makes sense, I chose to test on VPS for better clearnet reliability & uptime, so this issue makes sense. My node is the funding source for this LNBits instance, but maybe cashu can't identify that somehow (since instance is not hosted on same hardware as pubkey)

I made a super quick sites page about the mint & contact information here: https://TinyUrl.com/thesupermint

Thank you very much for making a mint review & search nostr client. Very much needed indeed!

I think it's just not built into lnbits to return the pubkey... none of the lnbits mints I've seen do. It's the mint's pubkey not lightning node's pubkey

Makes more sense. Thanks for clarifying

You might want to consider to not allow adding LNbits demo mints at all to the list. It's unclear whether these will be there permanently.

Looks like just self-hosted lnbits so far, but good point