welcome to bitcoin culture lol

Oh, I wasn't aware that was an option. Let me know how you like it!

i started my own meetup to discuss only the tech

get yourself a framework

i have undertaken the task of writing and implementing the spec, as requested by the team

> the specs will sort themselves out if they’re needed

they are needed and i am the guy to make it happen

i'm overthinking it, just write the damn code and push out the PR

it's a serious question! i have never written a (successfully merged) spec before.

seems like the key goal is to disambiguate any possible misunderstanding of the important implementation details while leaving the rest of the decisions up to the implementor. does this require two different individuals to implement it? if an llm is implementing it, are two different prompts sufficient?

is it an antipattern to write a spec and implement it twice yourself to get the spec merged?

when someone shows you who they are, believe them the first time

😬 better update that firmware!

@nevent1qqs...

@nevent1qqs...

I vibed up a rust library to do this. Nobody uses it afaik. I need a network of sovereign mining pools for my purposes, so it's a ways off from being useful.

What do you intend to use it for?

published crate
https://crates.io/crates/bitcoin-nostr-relay

source
https://github.com/vnprc/bitcoin-nostr-relay

test env
https://github.com/vnprc/tx-relay-playground

contributions welcome, i heard ZMQ was faster than RPC 👀
https://github.com/vnprc/bitcoin-nostr-relay/issues/5

another day another ledger customer list leak

don't buy ledger. if you must, don't give them your private info