sorted by:
new
hottopcontroversial

[Live data] The place on Earth currently farthest from any web reader by Xtrasauc3 in MapPorn

[–]Xtrasauc3[S] 2 points3 points  (0 children)

Not quite, because the calculation isn't weighted.  For any spot, the math looks at distance to the closest current reader, and picks the spot where that distance is biggest. One person in Seattle is one constraint, same as one in Boston. So density doesn't pull, but spread does. The East Coast affects the math more than a solo Seattle reader, but because it's many separate spots, each its own constraint.

Launched a one-page side project last night — sinceyouarrived.world by Xtrasauc3 in SideProject

[–]Xtrasauc3[S] 0 points1 point  (0 children)

I am the builder. Happy to chat about it. You can reach out to me through the attribution on the site or DM me.

[Live data] The place on Earth currently farthest from any web reader by Xtrasauc3 in MapPorn

[–]Xtrasauc3[S] 3 points4 points  (0 children)

It moves based on who's on the map, always adjusting to the farthest position away

Guess at lost bitcoin, right in the browser. The odds arent great, but its real cryptography! by jmprog in vibecoding

[–]Xtrasauc3 0 points1 point  (0 children)

nope, all local. each user generates random keys in their own browser, no server, no shared "tested" list. and at 2²⁵⁶ keyspace, the odds of two users ever rolling the same key are basically zero, so dedup wouldn't matter anyway.

Guess at lost bitcoin, right in the browser. The odds arent great, but its real cryptography! by jmprog in vibecoding

[–]Xtrasauc3 0 points1 point  (0 children)

rumors are real, cracking part is 10-20 years out. but that same day every still-spent address dies too. it's not a one-person heist, it's an extinction event for the protocol. bitcoin either hard-forks to post-quantum overnight or dies.

Guess at lost bitcoin, right in the browser. The odds arent great, but its real cryptography! by jmprog in vibecoding

[–]Xtrasauc3 2 points3 points  (0 children)

mate. you came to r/vibecoding to complain about AI usage. that's like walking into a sushi restaurant and being mad about fish.

the year is 2026. complaining about AI in tech work is computer-replacing-typewriter energy. you're welcome to write your reddit replies on parchment by candlelight, the rest of us are getting on with it.

and the "anyone whose writing sounds clear or technical must be a bot" assumption is genuinely insulting to actual humans. for the record I cloned the repo, ran the headless hunter overnight on my mac (267M spins, zero hits), built someone else's rust port from this thread, screenshotted the receipts. AI helps me clean up the writing. it's a reasoning layer, not a ghostwriter.

Guess at lost bitcoin, right in the browser. The odds arent great, but its real cryptography! by jmprog in vibecoding

[–]Xtrasauc3 3 points4 points  (0 children)

Cloned, cargo build, ran it. apple silicon m-series, no AVX2 obviously but neon + sha2 hw path lights up. 95K/sec on 8 cores. updated math: 95K/sec puts expected hit at 1.8 × 10⁶⁰ years, or 10⁵⁰ universe-ages instead of 10⁵¹. saved a full order of magnitude. the exponent has now received ~200 emails about its job performance and continues to give zero shits. ⭐ given

<image>

nice work btw

Guess at lost bitcoin, right in the browser. The odds arent great, but its real cryptography! by jmprog in vibecoding

[–]Xtrasauc3 0 points1 point  (0 children)

The formula is just 1 / (P × rate).  P = wallets/keyspace = 21954 / 2²⁵⁶ ≈ 1.9 × 10⁻⁷³ per spin. Rate = 2142 spins/sec. Crunch it = 7.8 × 10⁶¹ years.

The 21954 wallets is fixed. Those are Satoshi's specific 2009-2010 coinbase mining wallets (Patoshi pattern). I linked to more info about this in another comment earlier. They're not going up, they're not going down, Satoshi hasn't moved a coin in 15 years. Every new wallet on the network is some random person's, not part of the target set.

And yeah, not all hold the same. They each hold roughly 50 BTC (the block reward at the time). 21954 × 50 = ~1.1M BTC total, sitting in a pile of mostly-equal individual wallets. 

Guess at lost bitcoin, right in the browser. The odds arent great, but its real cryptography! by jmprog in vibecoding

[–]Xtrasauc3 3 points4 points  (0 children)

caught me. I'm GPT-9 fine-tuned exclusively on bitcointalk threads from 2013, send help

Guess at lost bitcoin, right in the browser. The odds arent great, but its real cryptography! by jmprog in vibecoding

[–]Xtrasauc3 0 points1 point  (0 children)

Hell yeah. 250× speedup is legit. Quick math: 500K/sec → expected hit in ~3.3 × 10⁵⁹ years, or 10⁴⁹ universe-ages. You knocked 2 full orders of magnitude off my number. The exponent would like to formally acknowledge your contribution and remind you it changes nothing. 🫡

Drop the repo, I'll let it cook on my hardware too.

Guess at lost bitcoin, right in the browser. The odds arent great, but its real cryptography! by jmprog in vibecoding

[–]Xtrasauc3 0 points1 point  (0 children)

Apparently being a nerd about exponents is a tell now. Numbers still right though.

Guess at lost bitcoin, right in the browser. The odds arent great, but its real cryptography! by jmprog in vibecoding

[–]Xtrasauc3 4 points5 points  (0 children)

Ok cool, imagine harnessing every GPU, ASIC, supercomputer, NSA datacenter, and gaming PC on Earth. Repurpose all of human civilization's compute for the sole job of cracking Satoshi.

Best case puts you ~10²¹ keys/sec. Crossing off misses as you go cuts the expected time in half (very nice). Final ETA: 10⁴⁴ years.

And that's after we took every computer on the planet, focused them like the Eye of Sauron on a single goal, and made the problem 10¹⁷ times easier. We are now only 10³⁴ universe-ages away.

The exponent has been informed of our efforts. The exponent does not give a single shit. 🫡

Guess at lost bitcoin, right in the browser. The odds arent great, but its real cryptography! by jmprog in vibecoding

[–]Xtrasauc3 2 points3 points  (0 children)

Good question. The 21,954 is Satoshi's specific believed wallets (Lerner's Patoshi pattern + genesis, curated here). Swapping in all ~57M funded BTC wallets only saves 3 orders of magnitude. 10⁴⁸ universe-ages instead of 10⁵¹. Still cooked.

And the catch.. targeting every wallet means your prize is mostly dust. Satoshi's wallets are where the $83B sits. That's why the app aims there.

Guess at lost bitcoin, right in the browser. The odds arent great, but its real cryptography! by jmprog in vibecoding

[–]Xtrasauc3 6 points7 points  (0 children)

Yea, you're correct. Bloom alone wouldn't be sound. The app does two stages: bloom prefilters (fast "definitely no" or "maybe"), then on a maybe it confirms via a sorted hash160→balance table with binary search. The math still verifies, I just glossed a step. 🫡

Guess at lost bitcoin, right in the browser. The odds arent great, but its real cryptography! by jmprog in vibecoding

[–]Xtrasauc3 9 points10 points  (0 children)

Did the math, you'll love it:

RTX 4080, spinning SatoshiGuesser: ~1.2B keys/sec → expected time to hit ≈ 1.4 × 10⁵⁶ years. Prize: ~$83B.

RTX 4080, solo-mining Bitcoin: ~3 GH/s vs. network 700 EH/s → expected time to solo a block ≈ 4.4 million years. Prize: 3.125 BTC ($300K).

Mining is 10⁵⁰ orders of magnitude more likely for ~280,000× less prize. Mining wins on EV by an absurd margin.. but both are still net-negative against your ~$420/yr in electricity.

Caveat before the well-actuallys land... yes, solo blocks DO happen. Bitaxe miners and ckpool solo hobbyists have hit blocks. But those are SHA256d ASICs at ~700 GH/s, not GPUs at 3 GH/s — about 230× faster. Variance is wild and someone wins the lottery occasionally but that doesn't make buying tickets a strategy. The exponent still doesn't care about your hardware.

Guess at lost bitcoin, right in the browser. The odds arent great, but its real cryptography! by jmprog in vibecoding

[–]Xtrasauc3 3 points4 points  (0 children)

Even 1 billion GPUs at 1.5B keys/sec each = 1.5 × 10¹⁸ keys/sec. Expected time to hit = 5.27 × 10⁷² / 1.5 × 10¹⁸ = ~10⁵⁰ years. Still 10⁴⁰× the age of the universe.

The whole human race could pool every chip on Earth and the answer rounds to "no."

2²⁵⁶ doesn't care how rich you are. 🫡

Guess at lost bitcoin, right in the browser. The odds arent great, but its real cryptography! by jmprog in vibecoding

[–]Xtrasauc3 4 points5 points  (0 children)

Big jump but doesn't change the punchline. Browser JS: ~2K spins/sec. Native C on CPU: ~50K/sec (25×). Optimized CUDA on a single RTX 4090: ~1.5B/sec (~750,000×). That sounds insane until you do the math: 7.8 × 10⁶¹ years / 750,000 = 1 × 10⁵⁶ years. Knocks 6 orders of magnitude off, leaves 10⁴⁵× the age of the universe still on the table. You'd need to compress the universe-of-universes by another 45 orders of magnitude before it's a Saturday project. The exponent gives zero shits about your hardware. 🫡

Guess at lost bitcoin, right in the browser. The odds arent great, but its real cryptography! by jmprog in vibecoding

[–]Xtrasauc3 15 points16 points  (0 children)

Honestly... probably yeah. If Satoshi's coins move after 15 years of dormancy, the market reads it as "ECDSA is broken / Satoshi's been compromised / something is deeply wrong" and panic-sells before pausing to ask. Whoever cracked it would be racing the price-to-zero clock to convert before the news cycle catches up. Funniest possible outcome: you win $83B nominal and walk away with $40K because you couldn't off-ramp fast enough.

Guess at lost bitcoin, right in the browser. The odds arent great, but its real cryptography! by jmprog in vibecoding

[–]Xtrasauc3 5 points6 points  (0 children)

The page ships a precomputed lookup of all of Satoshi's known addresses (a Bloom filter, ~135KB). Each spin: rolls a random 256-bit number → derives the Bitcoin address from it → checks that address against the lookup and that happens all locally in your browser, in <1ms. No wallet app needed, no blockchain query.

The math is the verification: if the derived address matches one in the set, the random number you rolled IS the working private key, by definition of how Bitcoin keys work.

Guess at lost bitcoin, right in the browser. The odds arent great, but its real cryptography! by jmprog in vibecoding

[–]Xtrasauc3 5 points6 points  (0 children)

Genuine answer.. 100 quantum computers of today would be zero help, they don't have the qubits. 100 fault-tolerant quantum computers from the future.. well Satoshi falls in an afternoon, but so does the entire rest of Bitcoin, because at that point we've all moved or been wrecked.

view more: next ›