Bitcoin Forum
July 08, 2024, 07:55:12 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 [4] 5 6 »
61  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: July 03, 2018, 04:54:18 AM
Also, there are no known collisions for both SHA-256 and RIPEMD-160 hash functions. Not a single one.

Nobody bothered.

No, you will not find 50.000 BTC wallet by searching for the solution of this puzzle, I guarantee you that.

You are not authorized to guarantee that  Grin unless you're our dear Allah.
62  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: July 02, 2018, 10:02:38 AM
That's what anonymous author of the puzzle is telling us, and he backed his claim with all these BTC. If he is wrong, someone would pick the money from this puzzle.

Sooo wrong  Grin There is no direct relation between 32BTC puzzle and "real wallets". While searching for modest .5BTC puzzle you can discover 50.000BTC wallet due to collision.

That's what attracts so many mommies's-crypto-kiddies to LBC

One problem is the probability of such discovery....  Grin
63  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: June 23, 2018, 01:45:11 PM
The selection of key is totally random within the range with all values equally likely.

1. There is no true randomness in computers.
2. Can you count? 30 keys from 55 were in second half.

But OK, I've counted myself just now and was expecting a bit more than 30/55 chances
64  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: June 22, 2018, 04:30:23 PM
The person who created the puzzle has already posted exactly how he did it.

Not exactly. He just mentioned that values are random. But randomness can be very different.
If you look at the table with keys 1-55 you'll see that keys tend to sit in second part of range.

65  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: June 22, 2018, 04:26:50 PM
I've read most of this thread and am absolutely mesmerized by everyone's knowledge of the inner workings of things. I would love to be up to par with everyone on this. so who wants to tutor me and/or provide a link to something that explains more in-depth?

Theory is explained here (in short):
https://lbc.cryptoguru.org/about

and here (a lot of reading):
https://bitcointalk.org/index.php?topic=1877935.260

Software is available in at least two options:

LBC
or
https://bitcointalk.org/index.php?topic=3102823.0
66  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: June 22, 2018, 08:39:51 AM
I gave him an approximate search space.

Approx search space for puzzle56 is 36028797018963968-72057594037927936  Grin
67  Bitcoin / Project Development / Re: Faster and Autonomous Large Bitcoin Collider fork on: June 22, 2018, 08:13:07 AM
>run some modified versions of Vanitygen but not luck with this

Maybe it's a bit confusing, but NDV didn't do any mods to vanitygen. Only oclvanitygen.

Only weakminded do LBC on CPU, as even with good GPU with 50-100MKeys one needs several years to check puzzle56 range. And gazillion years to find any real wallet.
68  Bitcoin / Project Development / Re: Faster and Autonomous Large Bitcoin Collider fork on: June 20, 2018, 08:31:54 AM
VPS ?  Grin
69  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: June 20, 2018, 08:28:09 AM
Quote from: Andzhig
Arulbero looking for 56 between 00000000000000000000000000000000000000000000000000B2BE1F9B67E100 00000000000000000000000000000000000000000000000000D2BE1F9B67E100

You talk some crap as usual, there are no spends on p56, so public address is unknown.
70  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: June 19, 2018, 04:21:23 AM
When do you calculate a private address for a 56bit puzzle?

This "trick" is explained here and in LBC thread.
If someone spends PART of puzzle56, then Arulbero (or anyone who is capable of) can spend the rest.

I guess, this doesn't prove regular BTC wallets to be vulnerable, as their location in 2^159 address space is unknown.

Anyway huge respect to arulbero. He definitely didn't sleep at math classes.
71  Bitcoin / Project Development / Re: Faster and Autonomous Large Bitcoin Collider fork on: June 10, 2018, 05:36:15 PM
I do not understand what exactly you complain about.
VG from NDV goes DOWN - in opposite direction to LBC.

If you want to check it, pick for example 17E6C640 hex and it should
find first 29 bounties in several seconds (on GPU like 1070).
72  Bitcoin / Project Development / Re: Faster and Autonomous Large Bitcoin Collider fork on: June 08, 2018, 03:00:50 AM
Quote from: Sokolik4
standard vanitygen

This thread is not about standard vanitygen

Quote from: Sokolik4
(2*56-2*55)/200000000/60/60/24=2084 days?

Yes, around 6 years at 200MegaKeys. But vanitygen from ndv is slower. And another parties are also doing the same work, so
a. puzzle56 will be found earlier
b. you'll need luck
73  Bitcoin / Project Development / Re: Faster and Autonomous Large Bitcoin Collider fork on: June 07, 2018, 04:37:01 PM
> I'll get the results of the test, if anyone will help start the program

I personally do not need tests any more.

I've bought 1050, 1060 and 1070. The speed is strictly proportional to price. With 1070 I have around 45MegaKeys. So 1080ti will be 55-70MK.

Oh, and finally some math:

2^55/45000000/86400/365=25.4

with one gtx1070 it will take 25.4 years to find puzzle56.

puzzle57 - 50 years

p.s. If you search for say 70k beefiest wallets, that is
815437248150114052278668908511886675023028061025637774925757633858543166/45000000/86400/365=574607678103412010456246764552600678605775453115760312676 years to find first

good luck Grin


74  Bitcoin / Project Development / Re: Faster and Autonomous Large Bitcoin Collider fork on: June 07, 2018, 01:49:04 PM
Соколик, а повторяющаяся фраза "отказано в доступе" не смущает? Smiley

To the question of windows10 - Windows users are born to suffer Cheesy
Try admin privileges, if all required apps are installed, path variable. And it makes sense to compile proggie by yourself.


You can specify starting key in HEX, not WIF key.
In linux there's a nice util bc.

As puzzle55 is already found, going for p56.

echo 'ibase=10; obase=16; 2^56 ' | bc
100000000000000
[go@russian /]# echo 'ibase=10; obase=16; 2^55 ' | bc
80000000000000

puzzle 56 is between
80000000000000 and 100000000000000 (that's HEX!)

vanitygen searches DOWN. So you can start from 100000000000000, but actually I've checked several days from the very end.
It is better to pick some random number, like 65. We'll go to 65% of p56 range. That is

echo 'ibase=10; (2^55) + (2^55*65/100) ' | bc
59447515081290547 (in decimal)

and

echo 'ibase=10; obase=16; (2^55) + (2^55*65/100) ' | bc
D3333333333333 (in HEX)


75  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: June 01, 2018, 02:31:26 AM
Nobody admitted the find, so private key is unknown.

rico claims that he knows the key, but doesn't tell, not updates his cewl site. Once again showing his shitty attitude towards all LBC crowd.
76  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: May 31, 2018, 02:22:45 AM
Yeah, and judging by LBC discord, that's NOT LBC Smiley
77  Bitcoin / Bitcoin Discussion / Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it on: May 27, 2018, 04:12:08 PM
LBC is down ??

LBC is deprecated Grin

>Because the gift is very large 32 bitcoin it is a very big gift

Even if there is no scam or trolling and bounty55 is in 2^55 range, bounty56 is in 2^56 range and so on you have no chances to find something above bounty 60. So, it is about 2-3BTC at stake, not 32.

And huge amount of work is required.
78  Bitcoin / Project Development / Re: Faster and Autonomous Large Bitcoin Collider fork on: May 02, 2018, 02:49:13 PM
Are you sure that those are dormant addresses?
Some are just in cold storage or paper wallets locked in a vault since 2010.

This is what the previous replies have told you: nobody would help you knowing that this can potentially hack their own private keys.

I guess you haven't heard of 32BTC bounty.

Also you are mad if you really think that 100% of Bitcoins from 2009-2012 are paper wallets  Grin I guess 90% are LOST. Don't take the rest, I will not. Actually it's very easy to find rightful owner of wallet (if he still possesses the key).

"nobody would help you"

Don't say on behalf of nobody. Actually I myself have some BTC. So what?
79  Bitcoin / Project Development / Re: Faster and Autonomous Large Bitcoin Collider fork on: May 01, 2018, 02:22:33 PM
There's a limited proposal to rewrite a ECC part for only $250 because there's another guy who wants the same for Ethereum.
Normally he wanted about $500.
Predicts boost of 25-30%.

I'll take a pass this time.
80  Bitcoin / Project Development / Re: Faster and Autonomous Large Bitcoin Collider fork on: April 29, 2018, 05:53:21 AM
I extracted a list of dormant addresses with 5++BTC and it is only 71.500 entries in it.
Dunno why LBC search for the dust (15mln wallets) Smiley

As for vanitygen - size affects search speed greatly. With 160 addresses of 32BTC puzzle it does 26MK per second, with 71k addresses 23MK.
If you switch to compressed addresses only - you will have almost twice more.
So, to beat LBC one needs around 30 pcs of 1060  Grin
OOPS! That was some anomaly with gtx1050ti when disabling uncompressed addresses gave 2X boost.
On my current gtx1070 it almost doesn't matter 47 vs 48 megakeys.

With 71k addresses gtx1070 gets 40 megakeys.

Test 1080ti please!
Pages: « 1 2 3 [4] 5 6 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!