Intersting! Did not occur to me to use a kv solution for this.
I see! Is a document based DB the way to go? In memory?
I'd be curious to see how this runs on a bare metal VPS - I would expect way way higher throughput.
Another thing to try would be to batch writes - instead of writing every time something happens you collect writes in a queue and write every 50ms in one big transaction. This should help a lot with write throughput.
Reading can be done in the same way.
If you want to avoid parameter limits you can use JSON1.
Last but not least, analyze the queries using `EXPLAIN QUERY PLAN` to make sure your indices are correctly used.
A proper SQLite database shouldn't have issues with this amount of traffic. D1 isn't just SQLite though, it's SQLite + an API.
I would try using SQLite-in-DO instead of using D1. There's a good blog post about it here: https://blog.cloudflare.com/sqlite-in-durable-objects/
Secondly I would look at splitting up the database into multiple databases.
What's the reason the rates are so high compared to the rates set by the central banks? Is it a risk thing?
Like, ECB rate is 2% but the credit rates are at 10-13%? Seeing this across the different products that are on the market so not calling you out or anything, just curious how you end up at this rate 😃
Is there work going on to standardize the way signing events with extensions is done from a UI perspective? 🙏
This looks like absolute 💩. How do we expect users to understand this?
Are there examples of this flow that is user-friendly somewhere?
Already in my feed! Need more - would prefer even more technical 😃
Are there Bitcoin podcasts out there where the host is actually a bit technical and interviews developers instead of these rotating 20 influencers that go on every damn podcast out there? It's soooo fucking boring to listen to.
Also having trouble getting in touch with them - I tried their loan thingie and never received the funds, so now I’m stuck having to pay to get my BTC back. Feels like a scam
Hey nostr:npub1ex7mdykw786qxvmtuls208uyxmn0hse95rfwsarvfde5yg6wy7jq6qvyt9 nostr:npub1cn4t4cd78nm900qc2hhqte5aa8c9njm6qkfzw95tszufwcwtcnsq7g3vle - I reached out on X a couple of days ago to get help with my account that for some reason has been locked due to breaking "Terms of Service". I haven't used the account since I registered in April when you launched in the EU. It makes no sense. You sent me a DM asking for my account name, I replied and then you ghosted me?
Support only replies with something along the line of "This decision is final and we have nothing more to say".
And you can check out the stage environment here: https://v2.sveltesociety.dev/
Svelte 5!
Repo here: https://github.com/svelte-society/sveltesociety.dev/tree/v2
Probably a couple of months, they're re-building the Svelte website (merging Svelte, SvelteKit and Learn domains into one) so I suspect once that's done it'll just be some documentation and bits and bobs to finish up :)
Unfortunately not 😭 but I could probably do some kind of Svelte Society Feed for all the content and fire off events whenever they're posted, we'll see!
Started working on the new Svelte Society website. We're going social. Very exciting!
Yes I know what Fedimint is, it was a but if a rethorical question.
I don't see why you would use Fedimint when you can use Mercurylayer+LSP and have it be actually non-custodial? You'll get the exact same experience from a users point of view.
Fedimint is also custodial, no?
There is a fourth option: Mercurylayer + running an LSP for payments to the outside. Non-custodial and no risk of rugging.
Is the only thing we need to scale bitcoin Mercurylayer and Lightning? I think we might get very close.
Mercurylayer gives us non-custodial off-chain transfers within the statechain. Lightning gives us a way to do payments outside of the statechain via one or several "internal" LSPs.
This is basically Wallet of Satoshi but non-custodial.
This is basically Fedimint without having to trust a federation.
Someone, please build this. NOW!