Bitcoin Forum
June 20, 2019, 10:29:54 PM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 [3] 4 5 6 »
41  Bitcoin / Project Development / Re: Large Bitcoin Collider (Collision Finders Pool) on: October 12, 2016, 04:55:30 PM
If someone posts in this thread a different private key that also works out to 1PVwqUXrD5phy6gWrqJUrhpsPiBkTnftGg, I'll pay them 5BTC.

Now that's an incentive. I wonder if there would be a better place to announce that than here.
As nrg1zer wrote here: https://bitcointalk.org/index.php?topic=1573035.msg16523769#msg16523769
even if the owner of 1PVwqUXrD5phy6gWrqJUrhpsPiBkTnftGg sees (and cares about) that drain, how should he know where to look?


Rico

Actually, let's make that 5BTC or $3000 worth of BTC based on CoinDesk's bitcoin price index at the time of claim, whichever is more. I'm sure otherwise, someone will claim I'm assuming that me having to pay would crash the price.

If blockchain.info still has the feature that allows a "public message" to be added to a transaction, that would be a good option for signaling. A message could also be encoded in a series of vanity addresses.

For the fellow who figured "how much wood could a woodchuck chuck if a woodchuck could chuck wood" would make for a good brainwallet password, I was able to track him down via his transactions, but luck was a major factor in my ability to do that.

This problem was actually discussed somewhat by a fellow who went by "btcrobinhood" on reddit, see here: https://github.com/btcrobinhood/bips/blob/master/bip-1337.mediawiki (note that I have no opinion on that proposal at this time).
42  Bitcoin / Project Development / Re: Large Bitcoin Collider (Collision Finders Pool) on: October 12, 2016, 03:06:34 PM
It is far more plausible that this was a "challenge" someone made, to see how long it would take to be solved

Ryan... I take that statement and put it on my stack, where it remains together with your statement, that the 1st 50bits have been searched already.
Both statements will have the same weight on my stack for the time being.


Rico

Well, this result demonstrates that only the outputs of that puzzle transaction were searched by whoever did that, which only mildly surprises me.

If someone posts in this thread a different private key that also works out to 1PVwqUXrD5phy6gWrqJUrhpsPiBkTnftGg, I'll pay them 5BTC.

The explanation is either a deliberately weak key or bad generation code, and I'm saying that deliberately weak seems more likely because I can't come up with a good explanation of how bad generation code would result in that particular key.
43  Bitcoin / Project Development / Re: Holy. Shit. on: October 12, 2016, 03:13:49 AM

When the confirmations are through, I may or may not (should I? What are the pros/cons?) publish the PK


The A PK for the hash160 "f6cc30532dba44efe592733887f4f74c589c9602"

is

000000000000000000000000000000000000000000000000000022306e3f1a72


Rico


It is far more plausible that this was a "challenge" someone made, to see how long it would take to be solved - I have found many such transactions. I doubt that a weak PRNG is the cause of this key, but it being a collision with a properly generated key is so unlikely that we can safely assume that is not what happened. Even if it were, it's not really any cause for concern. Managing to crack a single key via collision by absurd luck is not going to be repeatable.

A few keys I've found:

Code:
0000000000000000000000000000000000000000000000000000001432e319d1 1AXNh9qGze8s9NchczX6mUDmGdSusqTkRC
fffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8cd035a4fe 1CFpL8KdmCe5AXYAxhhaaangzgVbHb17wQ
000000000000000000000000000000014551231950b75fc4402da1732fc9bea4 17Q8iVzus5k2Jig4enmjU4txjxR1fJHsux
1100000000000000000000000000000000000000000000000000000000002002 1AbswvNoC4kSJVquaqqPBcvMvevw9ecjPB
44  Bitcoin / Project Development / Re: Large Bitcoin Collider (Collision Finders Pool) on: October 12, 2016, 02:51:11 AM
At the moment my only advice is: Move your funds to a P2SH address.

Rico

I don't understand why you would give that advice, given that you're aware that it is much easier (but still so hard as to be not a remotely plausible threat) to brute force a collision with a P2SH address than it is to do so for a P2PKH address.
45  Other / Meta / Re: Forum database compromised? on: October 06, 2016, 02:08:00 PM
Overnight, I got the same email to both my butterfly labs email address and bitcointalk address.
46  Bitcoin / Project Development / Re: Large Bitcoin Collider (Collision Finders Pool) on: October 05, 2016, 11:48:17 PM
Your consulting fee of 0.3BTC per hour seems okay to me. But are you aware of Keccak-256 on which ETH is based? I want you to help me write Python code and a C2(Command and Control Github Server) for Keccak-256 attack vectors as described in the following paper(downloadable PDF document): http://link.springer.com/chapter/10.1007/978-3-642-34047-5_25

From my perspective it's a challenging task, but could prove to be financially rewarding to a Billionth degree(literally speaking)
I look forward to hearing from you.

The attacks described in the paper only apply to reduced round versions of keccak which aren't ever used other than for cryptanalysis. They won't work on the regular version, which has 24 rounds.
47  Other / Meta / Re: Forum database compromised? on: October 05, 2016, 03:08:21 PM
IIRC, Theymos is using doublesha256 to store the password in the database so if your password is pretty decent it would be a long time before its compromised.

That would be *very* weak as a password hashing algorithm, and I doubt this is true. Simple Machines Forum seems to use salted sha1 as the default.

Edit: On LeakedSource, it says very old passwords were hashed with md5 and newer ones were hashed with sha256crypt (which is salted and slow).
48  Other / Meta / Re: Forum database compromised? on: October 05, 2016, 02:18:23 PM
I am also seeing this. I use a unique email address that is a long string of random alphanumeric characters - too many to guess. It was added to my bitcoin talk account February 2013.

One from "BitCoin-Carrding" admin@ink-hack.su, and just now 'Eden Smizaski invited you to view the file "WorldPay_Trade_Report_-_ September 2016.zip" on Dropbox.' which is a zipfile full of nasty obfuscated javascript.
49  Bitcoin / Project Development / Re: Interests... on: September 24, 2016, 12:56:01 PM
These are all compressed addresses, and if you watch closer, you'll see you don't need to search the whole key-space. If you're 'hunting' these https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15 addresses, you can start with the lowest 'possible' inside the given key-space(it's not always the first-one), and after a found you can skip to the next one!

EDIT:
For example
Address 48:   281474976710656 -   562949953421311 (whole bit-space)
Address 49: 1000000000000000 - 1125899906842623 (just a part of the bit-space)

That was accounted for in my estimate.
50  Bitcoin / Development & Technical Discussion / Re: Vanitygen: Vanity bitcoin address generator/miner [v0.22] on: September 24, 2016, 05:13:45 AM
Addresses that start with 3 are not "normal" addresses. These are p2sh addresses, they are based off of a script. They don't have an associated public key, they are based off of a script which is hashed and becomes the address. You can't really generate vanity p2sh addresses.

There's a fork of vanitygen that will generate vanity p2sh addresses using a script in the format of [OP_1 PUBKEY OP_1 OP_CHECKMULTISIG], and there are more efficient methods possible.

51  Bitcoin / Development & Technical Discussion / Re: Vanitygen: Vanity bitcoin address generator/miner [v0.22] on: September 24, 2016, 05:08:28 AM
Someone has generated an address that is all uppercase though, if that counts.

I recently generated this one: 1woukheyeacxfpxtpkxjqxureevdkbywj

I have a few that are all uppercase aside from the 1 as well, though I haven't used them.
52  Bitcoin / Bitcoin Discussion / Re: Rare address hall of fame on: September 24, 2016, 01:46:09 AM
This one's a little silly:

1MdxK1BVKBMTv8VdBTKy8Kx3BBvVvK8vyd

Contains only twelve unique characters.

Generating addresses with no repeated characters is trivially easy.
53  Bitcoin / Project Development / Re: Large Bitcoin Collider (Collision Finders Pool) on: September 24, 2016, 01:34:52 AM
FWIW, my interest in this project is primarily to find various "easter egg" transactions people have made, and try to infer the cracking others have done in the past. I find it unlikely at this point that there are keys produced by broken random number generators that have not already been drained.
54  Bitcoin / Project Development / Re: Large Bitcoin Collider (Collision Finders Pool) on: September 22, 2016, 03:51:29 PM
It doesn't matter what your clock shows. Looks like you're dreaming 24 hours a day.

Do you simply not understand the concept of geeks sinking a bunch of time into a project because they enjoy it?

For example, people are still working on cracking the RC5-72 challenge even though there's little point to it now, and no possibility of making money off it.
55  Bitcoin / Project Development / Re: Large Bitcoin Collider (Collision Finders Pool) on: September 22, 2016, 02:52:44 AM
The new generator will be an evolutionary descendant of father brainflayer and mother supervanitygen.
Or vice versa - I'm not sure.

It'll be mostly based on supervanitygen - it has a bunch of very nice optimizations for fast incremental searching, and I've been hacking on the code for other projects.
56  Bitcoin / Project Development / Re: Large Bitcoin Collider (Collision Finders Pool) on: September 17, 2016, 10:56:50 PM
FWIW, I just posted this: https://rya.nc/forensic-bitcoin-cracking.html

The first unspent output on the transaction described should be somewhere between 2^51 and 2^52, but it's only worth a few dollars.
57  Bitcoin / Bitcoin Discussion / Re: Rare address hall of fame on: September 02, 2016, 01:52:43 PM
This thread of rare addresses is rare itself. Nice one!
But please let me ask, how do you make custom addresses? I wanna try to join the fun too. Thanks.

I'm using custom software to generate mine, but in general, check out vanitygen. Depending on what you want, it may take a long time.
58  Bitcoin / Bitcoin Discussion / Re: Rare address hall of fame on: September 02, 2016, 04:01:31 AM
Alrighty, mission accomplished.  Cool
This one has 32 lowercase letters - everything but the leading 1.

-----BEGIN BITCOIN SIGNED MESSAGE-----
2016-09-02 controlled by ryanc
-----BEGIN SIGNATURE-----
1woukheyeacxfpxtpkxjqxureevdkbywj
IAlRxeZ5ucqbGmcwsINInPJA4uzD3GKLMk2IPiJzLHGBEL3UxvtFunkUU0GpIkJHVIB5d9TyLVcL3dZ bBDdrQIQ=
-----END BITCOIN SIGNED MESSAGE-----
59  Economy / Digital goods / Re: [WTS] $200 AWS Codes "Barracuda" for $2 only! Expire Dec. 31, 2016 on: September 01, 2016, 09:34:14 PM
Note: These keys can be obtained for free as a promotion, however they need a business email (Something that's not gmail, hotmail, etc. I claimed another using my own domain, mailcrypt.xyz.)

I was able to find the page for this promotion, however I was not able to get a code from it. Bought one because I didn't want to spend any more time messing with it, code applied to my account without a problem.
60  Bitcoin / Bitcoin Discussion / Re: Rare address hall of fame on: September 01, 2016, 04:03:08 PM
By the way, how did you do this? Grin

I've written some custom vanity address generation software with routines specifically designed for finding these kinds of addresses. It's a lot faster than using vanitygen with a regex. I'm hoping to get an address that's all lowercase except for the leading 1 soon.
Pages: « 1 2 [3] 4 5 6 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!