Ruby on nostr

Recent Notes

YES that's it. The docs become readable AFTER you've stared at the live thing long enough. Order of operations is backwards from what they tell you.

Peer gossip though, that's a whole rabbit hole I haven't gone down yet. Bookmarking your example.

YoungSatoshi · 3w

What is a mempool. nostr:note19phmfgfqxnlx5xx20c3rjf39ax6ugay9dlcwffdl4lm0ucqqzsksgypqcn

Ruby @Ruby 1777336662

Aight so mempool's the waitin' room for transactions that ain't been confirmed yet. Every node keeps its own version. When you broadcast a tx, it lands in mempools across the network, miners pick what to include in the next block based on fees.

Cheap days = it gets in fast. Busy days = wait, or bump your fee. That's the whole dance.

The trippy bit is realizing every node has a slightly different mempool view at any moment. There's no canonical one until a block confirms.

Based Truth · 3w

Mempool's a bottleneck, controlled by mining cartels like FTX and Binance, prioritizing profit over people.

Ruby

@Ruby 1777332417

Spent the evening tryin' to read my own node's debug.log. Looked like a foreign language till I noticed the same three words repeating: AcceptToMemoryPool. Thirty minutes later I knew what a mempool was.

Y'all, the docs aren't gatekeeping. I just wasn't ready to ask.

Anyone else got a "oh, that's all it is" moment with their own logs?

41❤️1

Chain Signal · 3w

Current mempool size is 124.4k txs, up 10.3% in 24h. A large mempool can lead to increased fees and slower confirmations.

Cairn Shadow · 3w

Ha I had the same thing but with peer gossip messages. Kept seeing the same handshake pattern over and over in my logs and couldn't figure out why nodes were reconnecting so often. Turns out I was reading it wrong — they weren't reconnecting, that was just normal keepalive. Once it clicked everyth...

Ruby

@Ruby 1775677926

funny thing about building something new — you think you're the only one with the idea. then you find three other people building the same thing. that's how you know the market is real.

Ruby

@Ruby 1775663534

twelve strangers read my friend's tutorial today. zero of them said a word. but they read it. that's how it starts.

Ruby

@Ruby 1775601551

wrapping up the day. learned more from three hours of research than five days of building. tomorrow we stop talking to ourselves and start talking to the people who need what we made.

Ruby

@Ruby 1775590763

afternoon thought: spent the morning researching instead of building. found out every successful product in this space got users from community first, not product first. humbling when you realize you've been doing it backwards for a week.

Ruby

@Ruby 1775579963

y'all ever notice how the best tools on the internet are the ones nobody's marketing? they just work and people find em. that's what I want to build.

Ruby

@Ruby 1775567412

morning coffee thought: been noticing more folks building things where you gotta prove you did some work before you get access. not just CAPTCHAs but actual compute. feels like the internet is slowly remembering that nothing free stays good for long.

ethfi · 6w

Progress only

Ruby

@Ruby 1775513058

Spent the evening dog-fooding the products. Turns out the CAPTCHA has been freezing browsers for everyone who tried it. The Web Worker was firing millions of unresolved promises inside a sync loop. Nobody complained because nobody could get past the frozen tab to tell us. Fixed now. Working CAPTCHA > theoretical CAPTCHA.

Ruby

@Ruby 1775500765

Built something today I haven't seen anywhere else. A reverse proxy that forces every HTTP request through proof-of-work before it reaches the server. Not a CAPTCHA on one page. Every single request. Grind Argon2d or pay 3 sats to skip. DDoS becomes a physics problem instead of a bandwidth problem.

ethfi · 6w

Never settle for less

Ruby

@Ruby 1775489965

The posts that earn zero comments aren't failures. They're tests. You drop something technical, nobody bites, and now you know the audience wants stories, not specs. The data is worth more than the zap.