You’re correct. If you create an API key, it should be used elsewhere. But you should be able to get a refund for your API key easily. Refund and everything works great for me as well. Mullvad shouldn’t be an issue at all.
We should give you Nostr cloud configuration options. Maybe we should just read your relay list on Nostr use those to store your data along with our default ones.
I’m sorry about the losses. If you still have those API keys you couldn’t get refunded, it’d really help if you could share them with me over DMs. (keychat? Or Signal?)
I haven’t tried it with pyRoutstr. Will check it out.
Also, i didn’t get a notification here. Idk why. I’m following you now, maybe that’s why?
Hey nostr:npub130mznv74rxs032peqym6g3wqavh472623mt3z5w73xq9r6qqdufs7ql29s I keep trying to test your chat. Big believer in what you are building.
I paid multiple nip60 lightning invoices from multiple wallets that confirm payment but the funds never appear in the routstr wallet. Routstr says payment failed after multiple checks.
History tab shows nothing.
The non nip60 wallet accepted payment and shows in history but doesn't show as available for API keys. The migration to nip60 then worked and the sats are available for an API key.
The API key was made. The API key error 401 when put into pyRoutstr client and network errors when attempting to refund.
Hey! Sorry about that. I think this is a problem with the relays.
Just to confirm, were you behind Tor the whole time? I tried using it via the Tor browser and it didn’t work as expected either. We’ll fix that asap.
Maybe you made the lightning payment but we couldn’t store them into the nip60 wallet as the events could’ve been rejected. In such a case we can give you a Cashu token refund.
Thanks a lot for reporting this! If you remember any specific error messages or if you know exactly how to reproduce this, pls let me know :).
We were having issues with the default provider. We want to make it more robust with many more providers if some go offline.
api.routstr.com was offline. I brought my own provider online at ai.redsh1ft.com and have it as default on chat.routstr.com rn.
Soon I’ll configure it in a way the chat app automatically switches to the available provider.
We will also have Nostr based monitoring for provider health as well. Centralised reliance is a no go!
You didn’t lose sats when the provider went down, the frontend stores a Cashu token locally if the request is unsuccessful. You should be able to see this in history.
Anyone here setup yet as a nostr:npub130mznv74rxs032peqym6g3wqavh472623mt3z5w73xq9r6qqdufs7ql29s AI provider?
Seems like a fun and interesting way to generate passive #satsflow.
I need to learn how to do this!
Simple.
1. Clone the repo: https://github.com/Routstr/proxy
2. Configure the .env file using .env.example. Set your upstream URL to localhost as you’re running a model locally. be sure to setup your nsec to store sats in a nip60 wallet.
3. Configure models.json similar to models.example.json (this is where you set your price)
4. Run docker-compose.
5. Finally, send a note tagging nostr:npub130mznv74rxs032peqym6g3wqavh472623mt3z5w73xq9r6qqdufs7ql29s with your URL endpoint to start stacking sats!
Hit us up if you’re facing any issues. Will write a more detailed guide soon.
nostr:npub1kvaln6tm0re4d99q9e4ma788wpvnw0jzkz595cljtfgwhldd75xsj9tkzv
Is Minitbits down for anyone else?