0 sats \ 0 replies \ @antic 18 Mar \ on: Jack of all trades; Digging deep, not wide. Which one do you prefer? art

If I were to give advice to myself 20 years ago, I'd say to start wide but choose a deep path, then zoom out again. I spent decades staying wide and rarely going deep, which is fun but randomizing and less productive. In the few places where I've really gone deep, it's been amazing, but finding the discipline to not get distracted by the wide array of other options is always a challenge.

I think we are still very early and territories are a subtle knife in the side of reddit. Ultimately, why would anyone use Reddit? For karma? Why would you spend time on stock traded platforms that are selling your data to Google (Reddit ipo is days away) if you had an option of building the same communities powered by sats instead of karma points. Sure, it’s a long road and Reddit has a huge user activity base, but I’d move it all here if it were up to me.

I think as people realize that platforms are making huge amounts of money from their usage and time, they will seek honest communities built upon an honest ledger. Same goes for Steem/Hive. All of those communities would be better here.

Jokes on everyone, Elon Musk has been mining bitcoin since 2010 and he moved it to an exchange so he could ape it into Dogecoin to drive it to $1 before dumping Doge back for 7,000 bitcoin.

Carnage.

Totally, which is why this particular batch is so interesting. Why stop at moving precisely 1,000 of mined bitcoin unless it’s just a round chunk of a bigger set of holdings.

This person probably has many thousands of bitcoin offline anyway still. Selling this batch of 1,000 might have just been a way to get $68M for spending money for the rest of their lives/retirement.

It looks like it went to an exchange. The multisig payout address then shot it all out (9 minutes later) to a collection of segwit addresses as 11.23080108 BTC each and to some multisigs... and the segwit addresses shot them out to more places that appear to be distribution gatway addresses (like https://mempool.space/address/bc1qpn5jcmqjfx3j00j6ktzgrn2gdlf534cjcgtwdq) maybe this is a big odd washing system...

hah, my brain is still wired in GPG/PGP thinking. Correct, I have a tendency to blurt "large primes! It's all primes!" in my sleep. And yes, that's some unoptimized quick hackery from chatgpt in python. Not usable but readable enough to make the point.

absolutely. And, like I said in the linked article, wouldn't it have been so much fun and profitable to sign a bunch of messages using those keys pretending to be Satoshi and sending markets into chaos? The owner of those 2010 block rewards had huge power to pretend to be Satoshi... could have made up a lot of interesting stories. Glad they didn't, but it was in their power.

ECDSA using Secp256k1 can still be brute forced (albeit inefficiently) using a discrete log solving method like rho:

`from sympy import isprime, nextprime def pollards_rho(G, Q, curve_order): x = G y = G factor = 1 while factor == 1: x = curve_add(x, G, curve_order) y = curve_add(y, G, curve_order) y = curve_add(y, G, curve_order) factor = gcd(abs(x[0]-y[0]), curve_order) return factor def curve_add(p1, p2, curve_order): # Simplified elliptic curve addition return (p1[0] + p2[0], p1[1] + p2[1]) % curve_order def gcd(a, b): while b: a, b = b, a % b return a # Example parameters (not for secp256k1) G = (3, 7) # Generator point Q = (13, 17) # Public key curve_order = 19 # Elliptic curve order d = pollards_rho(G, Q, curve_order) print(f"Private key (d): {d}")`

This would take a gazillion lifetimes of the universe to compute.
It could be ported to Shor's on a quantum cluster if the cluster gets stupid large and actually corrects for errors.

Schnorr signatures are also reliant on the difficulty of solving the discrete log problem.

The thing that gets exposed when you spend from a P2PKH (pay to public key hash) is the unhashed PK (public key). Factoring large primes requires knowing one of the two large numbers. The private key is one number, the public key is the other number. By using P2PK, the original block rewards were paid out directly to the public key number itself without any secret being made of it. Hashing the public key prevents anyone from deriving the actual number that is the public key, which prevents using a number factoring attack (as long as you keep both the private key and the public key secret).

You could reduce this to make visualization easier by imagining a keyspace of only 10 numbers. By using P2PK, they were saying to the world, "my secret key maps to the public key for the number 6" and then someone can simply find the private key that matches the number 6. Hashing the public key prevents anyone from knowing which of the 10 numbers your private key pairs with, so they would have to brute force and test each one, which is very doable for a keyspace of 10, but relatively impossible for a keyspace of 2^128

It's cool to see the evolution of your art over time.
I'm partial to BITCOIN RADIANCE! -- the fiat melting into the ocean under the skull, the colors, raw and brutal but somehow also hopeful. Dig it.