lol, you can only see new events on your feed every 10 mins , after a block is mined
stakworks does something very similar, would be cool to see nostr + stakworks
or even modular. seems like a good design is to separate storage from relay so operators can choose their own backend
blixtr , cause it’s blisteringly fast 😂
great way to chunk up the work. i think there will also be a use case for blazing fast proxy relays which help sync across slower, beefier relays with more storage
very cool, i might take a look. been wanting to dust off my elixir hat 😁
fuck yeah, low-latency high volume relays seems like the perfect elixir usecase. i’ve seen a few people mentioning relays which broadcast to other relays.. seems like this would be perfect for that?
haha the worst part of having tattoos
right, but i think that’s still stratumV2 haha. basically you need 1 or more miners behind a bitcoin core node, and the core node creates block templates. the benefit i see here is you can choose for yourself in stratumv2 how cooperative vs decentralised you want to be.
not saying fedipool is a bad idea, or stratumv2 is better. just trying to understand if fedipool adds anything new, and it doesn’t seem like it does. but maybe fedipool gets more traction?
there is an open grant to have someone work on it from spiral or square crypto, can’t remember which one. tell all your rust frens about it
interesting, although i’m not seeing the benefit of having guardians construct blocks vs having individual miners construct blocks (which is what stratumV2 is proposing)
been having the same thought recently. there’s actually quite a few guides on running an AS! personally, been focusing on self hosting first and then eventually plan to go full retard and try to set up an AS
seems this is proposing guardians construct blocks, whereas i think stratumV2 has each miner constructing a block, iirc
what benefits does this have over stratumv2? briefly glanced and they more or less seem to be tackling the same problem, the biggest of which is the pool operator constructing the block
merry crimus ya filthy animals
excellent point. your client is the one making the call. even better, your client can choose to ignore this information!
yeah, nostr.rocks is a lil slow. either way, very cool feature!
which client are you using? i see a checkmark when using nostr.rocks

