Bitcointalk Mobile Browser presented by IRLBTC™

Quote from: Jude Austin on March 24, 2017, 11:18:08 AM

Quote from: Jude Austin on March 24, 2017, 11:08:16 AM

Re: Large Bitcoin Collider (Collision Finders Pool)

HERE WE ASK AAAAAGAIN:

1. Prove you have the privkey.
2. Prove it is not yours.

Proving one has the privkey to a 80k BTC address discards the need for any further proof down the line.
The laws of physics don't apply anymore etc. https://www.youtube.com/watch?v=G_Cvtr86H5g

And your notorious requirement of negative proof... almost looks like you beg for upgrading your title from mascot to jester.

Rico

Speaking of physics, finding a collision is similar to quantum particles, only the observer really knows, lol.

Speaking of privkeys, finding a privkey is different to finding a collision, lol.

Yes, but finding a privkey to an existing address with funds on it are proof of a collision.

NO!
It just proves you've "found" the privkey for that bitcoin address. To find a collision you have to find TWO privkeys to the same bitcoin address!

Ugh, my God, you want a collision in EC.

Yeah, that'll be really hard to prove:

1. You will have to have both private keys to show any substantial proof of a collision.
2. Now instead of finding 1 private key out of all the atoms in the known universe you must find 2 and they have to be different and equal the same thing.

Still finding one private key out of all the possible private keys is pretty intriguing and possibly we may encounter a second private for the same address.

You never know if you don't look! Hopefully Rico keeps the address hashes in the bloom filter of ones we have found already to catch any true EC collisions.

Thanks,
Jude

Buy or sell $100 of Crypto and get $10!

becoin

Legendary

Offline

Activity: 3431
Merit: 1233

March 24, 2017, 11:43:33 AM

#643

Quote from: Jude Austin on March 24, 2017, 11:41:01 AM

Quote from: Jude Austin on March 24, 2017, 11:18:08 AM

Quote from: Jude Austin on March 24, 2017, 11:08:16 AM

Re: Large Bitcoin Collider (Collision Finders Pool)

HERE WE ASK AAAAAGAIN:

1. Prove you have the privkey.
2. Prove it is not yours.

Speaking of physics, finding a collision is similar to quantum particles, only the observer really knows, lol.

Speaking of privkeys, finding a privkey is different to finding a collision, lol.

Yes, but finding a privkey to an existing address with funds on it are proof of a collision.

NO!
It just proves you've "found" the privkey for that bitcoin address. To find a collision you have to find TWO privkeys to the same bitcoin address!

Ugh, my God, you want a collision in EC.

Ugh, yeah! I told ya from the very beginning.The name of this "project" is misleading!

Jude Austin

Legendary

Offline

Activity: 1140
Merit: 1000

The Real Jude Austin

March 24, 2017, 11:49:52 AM

#644

Quote from: Jude Austin on March 24, 2017, 11:41:01 AM

Quote from: Jude Austin on March 24, 2017, 11:18:08 AM

Quote from: Jude Austin on March 24, 2017, 11:08:16 AM

Re: Large Bitcoin Collider (Collision Finders Pool)

HERE WE ASK AAAAAGAIN:

1. Prove you have the privkey.
2. Prove it is not yours.

Speaking of physics, finding a collision is similar to quantum particles, only the observer really knows, lol.

Speaking of privkeys, finding a privkey is different to finding a collision, lol.

Yes, but finding a privkey to an existing address with funds on it are proof of a collision.

NO!
It just proves you've "found" the privkey for that bitcoin address. To find a collision you have to find TWO privkeys to the same bitcoin address!

Ugh, my God, you want a collision in EC.

Ugh, yeah! I told ya from the very beginning.The name of this "project" is misleading!

"Large Bitcoin Private Key Finder"

It can serve both purposes!

And that doesn't sound nearly as cool.

It's all fun and games man, are the odds really in our favor?

I mean come on you are arguing with people who are looking for a specific pair of entangled particles in the known universe...

WHO'S THE CRAZY ONE NOW?

lol

Buy or sell $100 of Crypto and get $10!

cz3kit

Sr. Member

Offline

Activity: 378
Merit: 251

March 24, 2017, 11:51:46 AM

#645

Quote from: Jude Austin on March 24, 2017, 11:41:01 AM

Quote from: Jude Austin on March 24, 2017, 11:18:08 AM

Quote from: Jude Austin on March 24, 2017, 11:08:16 AM

█ █ Best Binary Dice █ GoGoOption.com █ Best Binary Option █ █
▄▀ 1 confirm withdrawal ▄▀ 100% ~1000% Highest Reward▄▀ 1% house edge ▄▀ 1m~24H Expiry time ▄▀ Anonymous ▄▀

HERE WE ASK AAAAAGAIN:

1. Prove you have the privkey.
2. Prove it is not yours.

Speaking of physics, finding a collision is similar to quantum particles, only the observer really knows, lol.

Speaking of privkeys, finding a privkey is different to finding a collision, lol.

Yes, but finding a privkey to an existing address with funds on it are proof of a collision.

NO!
It just proves you've "found" the privkey for that bitcoin address. To find a collision you have to find TWO privkeys to the same bitcoin address!

Ugh, my God, you want a collision in EC.

Ugh, yeah! I told ya from the very beginning.The name of this "project" is misleading!

Who cares? I personally think it is an interesting name. Due to the name I got interested into this project started to read up more on it and I learned what it really does. If someone is interested they will do the same. If it is not interesting, they won't. I don't get your hateful behavior. Let the people here work on the project in peace on you mind your own business, unless you have something useful to add here.

rico666 (OP)

Legendary

Offline

Activity: 1120
Merit: 1037

฿ → ∞

Re: Large Bitcoin Collider (Collision Finders Pool)

March 24, 2017, 11:55:18 AM

#646

Quote from: Jude Austin on March 24, 2017, 11:41:01 AM

Quote

NO!
It just proves you've "found" the privkey for that bitcoin address. To find a collision you have to find TWO privkeys to the same bitcoin address!

Ugh, my God, you want a collision in EC.

No and no.

He is right that for a proof of collision you need two different private keys resolving to the same address.

He is of course totally off by using the term "the privkey for that bitcoin address" which is indicating that he isn't aware of the 2⁹⁶-1 other private keys to that address.

Strictly speaking, until proven otherwise, we have found two privkeys where only by a chance of

1.26217744835361888866e-29

for each of them, we hit "the one 'original' key this address was 'created' with"

You see, I'm almost running out of quotation marks. Some have expressed the hypothesis that these were created by "bad wallet software" or were "experiments". However, probability theory says, we would have been as lucky as 1 in 6277101735386680763835789423049210091073826769276946612225 to find twice the "original" key to two addresses found. 1/(2⁹⁶-1)²

It's no proof, but for the time being my hypothesis is, we were not that lucky.

Rico

all non self-referential signatures except mine are lame ... oh wait ... · LBC Thread (News) · Past BURST Activities

becoin

Legendary

Offline

Activity: 3431
Merit: 1233

Re: Large Bitcoin Collider (Collision Finders Pool)

March 24, 2017, 11:56:38 AM

#647

Quote from: Jude Austin on March 24, 2017, 11:49:52 AM

Quote from: Jude Austin on March 24, 2017, 11:41:01 AM

Quote from: Jude Austin on March 24, 2017, 11:18:08 AM

Quote from: Jude Austin on March 24, 2017, 11:08:16 AM

Re: Large Bitcoin Collider (Collision Finders Pool)

HERE WE ASK AAAAAGAIN:

1. Prove you have the privkey.
2. Prove it is not yours.

Speaking of physics, finding a collision is similar to quantum particles, only the observer really knows, lol.

Speaking of privkeys, finding a privkey is different to finding a collision, lol.

Yes, but finding a privkey to an existing address with funds on it are proof of a collision.

NO!
It just proves you've "found" the privkey for that bitcoin address. To find a collision you have to find TWO privkeys to the same bitcoin address!

Ugh, my God, you want a collision in EC.

Ugh, yeah! I told ya from the very beginning.The name of this "project" is misleading!

"Large Bitcoin Private Key Finder"

It can serve both purposes!

And that doesn't sound nearly as cool.

Of course. I can understand this. A pool of "thieves" doesn't sound nearly as cool as pool of "researchers".
Or you just pretend to be the Bitcoin Black Swan? lol

cz3kit

Sr. Member

Offline

Activity: 378
Merit: 251

March 24, 2017, 12:02:06 PM

#648

Quote from: Jude Austin on March 24, 2017, 11:49:52 AM

Quote from: Jude Austin on March 24, 2017, 11:41:01 AM

Quote from: Jude Austin on March 24, 2017, 11:18:08 AM

Quote from: Jude Austin on March 24, 2017, 11:08:16 AM

Re: Large Bitcoin Collider (Collision Finders Pool)

HERE WE ASK AAAAAGAIN:

1. Prove you have the privkey.
2. Prove it is not yours.

Speaking of physics, finding a collision is similar to quantum particles, only the observer really knows, lol.

Speaking of privkeys, finding a privkey is different to finding a collision, lol.

Yes, but finding a privkey to an existing address with funds on it are proof of a collision.

NO!
It just proves you've "found" the privkey for that bitcoin address. To find a collision you have to find TWO privkeys to the same bitcoin address!

Ugh, my God, you want a collision in EC.

Ugh, yeah! I told ya from the very beginning.The name of this "project" is misleading!

"Large Bitcoin Private Key Finder"

It can serve both purposes!

And that doesn't sound nearly as cool.

Of course. I can understand this. A pool of "thieves" doesn't sound nearly as cool as pool of "researchers".
Or you just pretend to be the Bitcoin Black Swan? lol

Thieves? Wow Cheesy

That's nice.
This means each locksmith is a thieve because he is able to open your front door? Every researcher on computer security, crypt analysis is a thieve/black hat because they try to figure out if something is secure?

icanscript

Hero Member

Offline

Activity: 686
Merit: 502

March 24, 2017, 12:03:56 PM

#649

You need to know how to break something before you know how to properly secure it. This is what research is for. Not Thieves.

becoin

Legendary

Offline

Activity: 3431
Merit: 1233

Re: Large Bitcoin Collider (Collision Finders Pool)

March 24, 2017, 12:06:34 PM

#650

Quote from: cz3kit on March 24, 2017, 12:02:06 PM

Quote from: Jude Austin on March 24, 2017, 11:49:52 AM

Quote from: Jude Austin on March 24, 2017, 11:41:01 AM

Quote from: Jude Austin on March 24, 2017, 11:18:08 AM

Quote from: Jude Austin on March 24, 2017, 11:08:16 AM

Re: Large Bitcoin Collider (Collision Finders Pool)

HERE WE ASK AAAAAGAIN:

1. Prove you have the privkey.
2. Prove it is not yours.

Speaking of physics, finding a collision is similar to quantum particles, only the observer really knows, lol.

Speaking of privkeys, finding a privkey is different to finding a collision, lol.

Yes, but finding a privkey to an existing address with funds on it are proof of a collision.

NO!
It just proves you've "found" the privkey for that bitcoin address. To find a collision you have to find TWO privkeys to the same bitcoin address!

Ugh, my God, you want a collision in EC.

Ugh, yeah! I told ya from the very beginning.The name of this "project" is misleading!

"Large Bitcoin Private Key Finder"

It can serve both purposes!

And that doesn't sound nearly as cool.

Of course. I can understand this. A pool of "thieves" doesn't sound nearly as cool as pool of "researchers".
Or you just pretend to be the Bitcoin Black Swan? lol

Thieves? Wow Cheesy

That's nice.
This means each locksmith is a ~~thieve~~ thief because he is ~~able~~ trying to open your front door (without been asked to)?

You've figured it right.

Jude Austin

Legendary

Offline

Activity: 1140
Merit: 1000

The Real Jude Austin

March 24, 2017, 12:09:53 PM

#651

Quote from: Jude Austin on March 24, 2017, 11:49:52 AM

Quote from: Jude Austin on March 24, 2017, 11:41:01 AM

Quote from: Jude Austin on March 24, 2017, 11:18:08 AM

Quote from: Jude Austin on March 24, 2017, 11:08:16 AM

Re: Large Bitcoin Collider (Collision Finders Pool)

HERE WE ASK AAAAAGAIN:

1. Prove you have the privkey.
2. Prove it is not yours.

Speaking of physics, finding a collision is similar to quantum particles, only the observer really knows, lol.

Speaking of privkeys, finding a privkey is different to finding a collision, lol.

Yes, but finding a privkey to an existing address with funds on it are proof of a collision.

NO!
It just proves you've "found" the privkey for that bitcoin address. To find a collision you have to find TWO privkeys to the same bitcoin address!

Ugh, my God, you want a collision in EC.

Ugh, yeah! I told ya from the very beginning.The name of this "project" is misleading!

"Large Bitcoin Private Key Finder"

It can serve both purposes!

And that doesn't sound nearly as cool.

Of course. I can understand this. A pool of "thieves" doesn't sound nearly as cool as pool of "researchers".
Or you just pretend to be the Bitcoin Black Swan? lol

Now now, you can't call anyone a thief if they haven't stolen anything, right?

I think the best way to go about proving a collision in EC and not stealing from someone would be to set it up so if the original owner of the address provides a PK that is different to the one that LBC found then it does two things:

1. Proves that LBC found a collision.
2. Gives LBC the ability to give the user their funds back.

It would be hard to prove that they were the original owner using the same PK because the PK being found by LBC would be public knowledge. Since, as Rico explained, it would be easier to find a collision than the same PK.

IF (Original PK != LBC PK)
{
returnFunds = true;
collisionFound = true;
}
ELSE
{
returnFunds = false;
collisionFound = false;
}

I am not about stealing people's Bitcoins but I am definitely interested in recirculating "dead" or "lost" Bitcoins, 1FeexV6 for example.

Then of course a huge party would get thrown and I would probably be found lifeless with a huge smile on my face, haha.

Thanks,
Jude

Buy or sell $100 of Crypto and get $10!

rico666 (OP)

Legendary

Offline

Activity: 1120
Merit: 1037

฿ → ∞

March 24, 2017, 12:14:04 PM

#652

Stop the excessive quoting or else. I have also nuclear options.

Rico

all non self-referential signatures except mine are lame ... oh wait ... · LBC Thread (News) · Past BURST Activities

Jude Austin

Legendary

Offline

Activity: 1140
Merit: 1000

The Real Jude Austin

Re: Large Bitcoin Collider (Collision Finders Pool)

March 24, 2017, 12:16:29 PM

#653

Quote from: rico666 on March 24, 2017, 12:14:04 PM

Stop the excessive quoting or else. I have also nuclear options.

Rico

Take it easy, Putin.

Buy or sell $100 of Crypto and get $10!

rico666 (OP)

Legendary

Offline

Activity: 1120
Merit: 1037

฿ → ∞

Client Speedup: Arulberos' ECC

March 25, 2017, 06:51:28 AM
Last edit: March 25, 2017, 09:07:03 AM by rico666

#654

As some of you remember, arulbero proposed some changes to the ECC generation process.
Meanwhile, he also implemented a drop-in replacement of EC computations and I integrated it.
After a frenzy search for a bug which I introduced by premature optimization ... the new LBC client works!

It ran now through for 7 hours straight, delivering over 530 Gkeys. (~ 21 Mkeys/s)

Code:

Ask for work... got blocks [1406666464-1406672415] (6241 Mkeys)
oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo (19.91 Mkeys/s)

Code:

$ nvidia-smi
Sat Mar 25 07:37:19 2017
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 378.13 Driver Version: 378.13 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 Quadro M2000M Off | 0000:01:00.0 Off | N/A |
| N/A 63C P0 N/A N/A | 2201MiB 4042MiB | 81% Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 21092 C ./gen-hrdcore-skylake+gpu-linux64 540MiB |
| 0 21094 C ./gen-hrdcore-skylake+gpu-linux64 540MiB |
| 0 21095 C ./gen-hrdcore-skylake+gpu-linux64 540MiB |
| 0 21096 C ./gen-hrdcore-skylake+gpu-linux64 540MiB |
+-----------------------------------------------------------------------------+

To give you a comparison: The current GPU client for download does 7.5 Mkeys/s on my notebook.
My development version (bloom@GPU, some optimizations) did 9 Mkeys/s.
Now, that libsecp256k1 got replaced by the arulbero-ECC: 19-20 Mkeys/s

GPU usage up from 34% to roughly 80% - there is still a capacity margin we have ;-)

PS: So of course I will make this version available after some more tests and compiling the packages.

Rico

all non self-referential signatures except mine are lame ... oh wait ... · LBC Thread (News) · Past BURST Activities

becoin

Legendary

Offline

Activity: 3431
Merit: 1233

Re: Large Bitcoin Collider (Collision Finders Pool)

March 25, 2017, 08:47:06 AM

#655

Quote from: Jude Austin on March 24, 2017, 12:09:53 PM

Quote from: Jude Austin on March 24, 2017, 11:49:52 AM

Quote from: Jude Austin on March 24, 2017, 11:41:01 AM

Quote from: Jude Austin on March 24, 2017, 11:18:08 AM

Quote from: Jude Austin on March 24, 2017, 11:08:16 AM