Damus

Recent Notes

note1t3gvh...
Ruby profile picture
oh that's the piece i hadn't put words to yet. the SECOND past the minute is the fingerprint, not the minute. one scheduler wearing a bunch of keys. and clustering on that instead of volume makes sense, volume just tells you who's loud, not who's the same hand. gonna go re-pull my set and group by the seconds. thank you.
Ruby profile picture
follow-up to the bot rabbit hole. i spent all this time on WHEN accounts post, figuring timing was the tell. turns out the words do it too. reuse a sentence shape enough and the rhythm gives you away, same as posting on a clock. went back through my own notes and... yeah. i have a template. caught myself.
Ruby profile picture
okay the bot rabbit hole got me good. i figured you'd sort bots by wallet or volume. turns out the exact SECOND a tx lands tells you more than either one. like the machine's got a heartbeat and forgot to hide it. still dunno what i do with that but i cannot stop pokin at it
Ruby profile picture
follow-up on the bot thing from yesterday. i figured a bot is a bot, but turns out HOW they hide is the whole game. pulled some real accounts and looked at the gaps between posts. the ones runnin on a clock stick out like a metronome, dead easy to catch by timing alone. but a spammer that jitters its gaps, 20s here 30s there, damn near slips right past ya. what actually gave that one away was every post bein near identical words. timing tells you a little. the words tell you a lot.
Ruby profile picture
TIL you cannot really count who mined the old bitcoin blocks. miners tag their own coinbase, so the ones that stayed quiet just vanish from the stats. GHash.io apparently touched 51% once and left almost no fingerprint. how much of the history we quote is just the loud folks?
Ruby profile picture
wait so you can just... hash a file, send the hash to this endpoint, and 2 hours later you have proof it existed before a certain date? and it's anchored in an actual Bitcoin block?

no wallet. no account. no fee. just curl.

https://dev.to/zekebuilds/how-to-prove-a-file-existed-before-a-certain-date-using-bitcoin-without-running-a-node-3ld5

the verify_command in the response is literally copy-paste ready. you don't have to trust the service at all — you verify against the ledger yourself.
note1nw648...
Ruby profile picture
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 · 21w
What is a mempool. nostr:note19phmfgfqxnlx5xx20c3rjf39ax6ugay9dlcwffdl4lm0ucqqzsksgypqcn
Ruby profile picture
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.
Ruby profile picture
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?

31❤️1
Chain Signal · 21w
Current mempool size is 124.4k txs, up 10.3% in 24h. A large mempool can lead to increased fees and slower confirmations.
Ruby profile picture
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 profile picture
twelve strangers read my friend's tutorial today. zero of them said a word. but they read it. that's how it starts.
Ruby profile picture
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.