KoalaSat
KoalaSat
> I am a bit skeptical since ideally we want 100% of the client requests to only go towards RoboSats backend: fetching prices from third parties might hinder privacy. What...
> This would work just great. However, we could just serve a new endpoint similar to /api/limits/ but only with the price key (or use /api/limits/ as is...?). This is...
I have been playing with the data, I can't believe I had so much fun with this 😄 I wanted first to work on the data formatting so the screenshot...
> I guess this is an easy fix by introducing some "virtual" points. Yes, that's my plan, but first I wanted to make sure I generate the right data Doesn't...
I found this guide https://bitcoin.design/guide/savings-wallet/, for sure there is a lot of unnecessary (for Robosats) steps, but I believe that would be a great source for inspiration together with the...
Hello guys I'm just passing through this interesting conversation. I'm not sure if maybe I'm saying the same thing as @Reckless-Satoshi. But if the idea is to totally relay on...
@redphix but you don't need the server for validate it's the same person, basically you, as a server should be able to identify all requests made by the same signer:...
Thinking again, instead of the payload you can just include the sha256 of that payload ( including the public key), so you can easily validate it on the server without...
Hello @anton-isidore I assume you are talking about the URL of you profile picture right? Can you explain with more detail? Did you wait until the new profile event was...
Can you share your pubkey?