1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57

[btcdvl]

Opinion discussion : The topic is the total number of wallets that can be created with HEX64.  Given the difficulty of Bitcoin and the mining system, I think that all wallets can be created with a P2P netwrok. In the future there may be asic computers for this.

Legal approach:   Since bitcoin is a reward block finding system, it is legal to generate coins and use the hashing power for a reward, but I think the secp256k1 algorithm used in bitcoin is inadequate and this is a design flaw.

Maybe this has been discussed a long time ago. I was able to build such a structure using my software knowledge. My target is only lost wallets.

If the topic is elsewhere, you can skip this thread.

I would like to discuss that this system is scientific and buildable.

I have created the software structure to realize this.

[mochi86_]

Uhhhhh... Perhaps state your point instead of beating around the bush. You 'built a software structure' targeting, what, lost wallets?

What are you suggesting with what you are trying to do? Take funds from lost wallets? If so, I'd advise you to get lost before the rest of the forum goes cut-throat on you. Best you just delete this post, too. You're just wasting everyone's time with a topic that will be disregarded by everyone.

Spend your time trying to invest in bitcoin or obtaining it legally instead of wasting time on dumb luck to find "lost wallets".

[stwenhao]

1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57

We are safe.

1. This number is wrong, because you copy-pasted only half of it correctly.
2. You work with decimal numbers, so your code is probably written in Python, in interpreted mode, which is one of the slowest possible approaches.
3. You are probably trying to target n-value of the secp256k1, so you are going to generate 2^256 keys, instead of 2^128, so you are not a serious attacker.
4. You are trying to target all possible keys, instead of focusing only on those, which are really used. It is like trying to land on the moon by exploring the whole universe, inch by inch, including visiting every single place, filled entirely with void.
5. You don't attack any non-standard keys with timelocks, keyless outputs, and many other address types, so you won't get all coins anyway (and we may switch into Pay to Quantum Resistant Hashes long before you will find a single key).

I would like to discuss that this system is scientific and buildable.

It is. But not in a brute force way. First, try to solve the 67-bit address, or the 135-bit public key. Starting point: https://mempool.space/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15

[pooya87]

Maybe this has been discussed a long time ago. I was able to build such a structure using my software knowledge. My target is only lost wallets.

There is no such thing as a lost wallet. If you have a gold bar stored somewhere around your house that you have not touched for 10 years, does that mean it is "lost" and I can come to your home and steal it?

Apart from "software knowledge" you also need basic understanding of math. 2²⁵⁶ is big enough that makes searching it to "getting lucky" impossible.

[satscraper]

Apart from "software knowledge" you also need basic understanding of math. 2²⁵⁶ is big enough that makes searching it to "getting lucky" impossible.

And apart from "software knowledge",  basic understanding of math and the incredible quantity of powerful computing systems   OP would need the reachless amount of energy ^{(ball park can be found here)} to  "getting lucky". Even quantum computers wouldn't help him as  to make the math they need to dissipate the relevant heat by the means of their cooling  which in turn requires comparable energy.

[btcdvl]

1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57

We are safe.

1. This number is wrong, because you copy-pasted only half of it correctly.
2. You work with decimal numbers, so your code is probably written in Python, in interpreted mode, which is one of the slowest possible approaches.
3. You are probably trying to target n-value of the secp256k1, so you are going to generate 2^256 keys, instead of 2^128, so you are not a serious attacker.
4. You are trying to target all possible keys, instead of focusing only on those, which are really used. It is like trying to land on the moon by exploring the whole universe, inch by inch, including visiting every single place, filled entirely with void.
5. You don't attack any non-standard keys with timelocks, keyless outputs, and many other address types, so you won't get all coins anyway (and we may switch into Pay to Quantum Resistant Hashes long before you will find a single key).

I would like to discuss that this system is scientific and buildable.

It is. But not in a brute force way. First, try to solve the 67-bit address, or the 135-bit public key. Starting point: https://mempool.space/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15

1. Answer : This is the right number 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,575,177,306,100,000,000,000,000

2 - 3. Answer : For example, in hexadecimal:

b798b220579fadfb9ad9371b1540fee36355b7f05372446de84b8d3727c72138
is a HEX64 value, expressed in binary as follows:


10110111 10011000 10110010 00100000 01010111 10011111 10101101 11111011
10011010 11011001 00110111 00011011 00010101 01000000 11111110 11100011
01100011 01010101 10110111 11110000 01010011 01110010 01000100 01101101
11101000 01001011 10001101 00110111 00100111 11000111 00100001 00111000
This format is 256-bit long.

Is there some other length that I don't know about. HEX64 = 256bit

4. Answer I'm not focusing on that. What I'm focusing on is that every P2P client will generate 1 billion block hashes and it will be random
For example;
0000000000000000000000000000000000000000000000041d546d02404c4eff
0000000000000000000000000000000000000000000000041d546d027be718ff

There are 1 billion wallets between these two blocks. This block will be scanned by only 1 user. No wallet and key will be stored with the generated Hash, there is no system to store all addresses.
Change your perspective: After 2013, I created a db repository for the lost wallets in the P2P network. The hash generating client will match the compressed and uncompressed wallets it generates in this area with the lost wallets I store in the P2P network. So the generator will be instantly audited.

5. Answer I don't understand what you are saying about this. Secp256k1 does not have a stamped encryption.
The issue is simple. Whoever has the privatekey owns the wallet.

stwenhao thank you for your response. to continue the discussion, your questions will contribute to the development.

Uhhhhh... Perhaps state your point instead of beating around the bush. You 'built a software structure' targeting, what, lost wallets?

What are you suggesting with what you are trying to do? Take funds from lost wallets? If so, I'd advise you to get lost before the rest of the forum goes cut-throat on you. Best you just delete this post, too. You're just wasting everyone's time with a topic that will be disregarded by everyone.

Spend your time trying to invest in bitcoin or obtaining it legally instead of wasting time on dumb luck to find "lost wallets".

I'm not talking about luck, I'm talking about technology.
Bitcoin is a system where the structure of the currency is designed as a reward;
But what if the rules of this system are flawed?
Also these search methods are already available on many sites but they are using the wrong method.
Instead of people on the forum attacking me. They should learn about the encryption system and more secure address methods.

Bitcoin 256 bit wallet system <> π

As a software developer, he can find at least one lost wallet password with an investment of 2 million dollars.
Or if 1-2 million users generate hashes at the same time. 2-3 years to find 1 lost wallet.
I explain this with linear algebra and probability.

There are 73,000 BTC that have been idle since 2013.  
An estimated 155,000 BTC are missing.

[hexan123]

it probably won't work because there aren't enough hard drives in the world to store all those numbers in order
the only method is to calculate the key and not guess or check all the combinations
ps. how do you check that the wallet is lost?

[btcdvl]

it probably won't work because there aren't enough hard drives in the world to store all those numbers in order
the only method is to calculate the key and not guess or check all the combinations
ps. how do you check that the wallet is lost?

no keys will be stored. there is no need for storage. Inside the P2P structure there is a list of lost wallets to be matched.
to see if they're matched. I made the first version of my software.

I have given some information about the system above. Please read it.

[hexan123]

let's say we have a list of lost addresses/keys in some distributed database and what next? how do you want to find the key: people in the p2p network are supposed to generate keys and match? how do you want to search for keys? generating all combinations and comparing with an old, long unused public key? write something more, nobody will steal your method, I'm just curious what you came up with?



edit: https://lbc.cryptoguru.org/about   ?

[btcdvl]

let's say we have a list of lost addresses/keys in some distributed database and what next? how do you want to find the key: people in the p2p network are supposed to generate keys and match? how do you want to search for keys? generating all combinations and comparing with an old, long unused public key? write something more, nobody will steal your method, I'm just curious what you came up with?



edit: https://lbc.cryptoguru.org/about   ?

The system works in a messy way, but I should explain it in simple terms.

The structure consists of 4 phases
1- Lost Wallet database
2- HEX64 worker database
3- Unifying field
4- Reward center

For example, each user generates 1 billion blocks.
0000000000000000000000000000000000000000000000000000000000000000- 000000000000000000000000000000000000000000000000000000003b9aca00
While the system is generating this field of 1 billion blocks, another user detects that this field has been generated and does not generate this field, which the “HEX64 worker database” will provide. It randomly generates a different field. If two consecutive blocks run out, they are merged in the “Unifying field”, which is P2P connected to the users so that they do not take up more space in the database.
because creating a database that can store even 1 billion production blocks one after the other

For example

block_308002 0000000000000000000000000000000000000000000000041d546d02404c4eff 0000000000000000000000000000000000000000000000041d546d027be718ff 2024-10-25 09:05:48

this is 2 Petabytes to write all blocks one after the other.

instead the generated blocks will be concatenated by the “Unifying field” and a single line will be written.

each producer will instantly register their wallet in the “Lost wallet database” at the same time. If the lost wallet is found, it will be encrypted in the “Reward Center”.

The reward center stores and updates the total list of running users and the total number of blocks generated by users.

[hexan123]

well, this is probably a better version of this: https://lbc.cryptoguru.org/about they apparently found something there but not much, thanks for the explanation and good luck

[btcdvl]

well, this is probably a better version of this: https://lbc.cryptoguru.org/about they apparently found something there but not much, thanks for the explanation and good luck

I have studied this similar approach.  
Only this one is missing how the system works and the reward system.
Presumably they take the lost wallets themselves.


Also, when I examine the pages on bitcointalk, I see that the structure is a sequential system, not a block system, and the hash generation areas of the users will probably overlap.

[ABCbits]

but I think the secp256k1 algorithm used in bitcoin is inadequate and this is a design flaw.

How exactly it's flawed or inadequate? It's still deemed secure until now and at that time, Satoshi couldn't use Schnorr Signature due to patent.

My target is only lost wallets.

And what exactly do you mean by lost wallets?

Also, when I examine the pages on bitcointalk, I see that the structure is a sequential system, not a block system, and the hash generation areas of the users will probably overlap.

Personally i find it's hard to believe SHA-256 collusion happen that easily.

Edit: I sent merit to OP by mistake.

[btcdvl]

How exactly it's flawed or inadequate? It's still deemed secure until now and at that time, Satoshi couldn't use Schnorr Signature due to patent.

in the old days it would have been impossible. But now any password without a timestamp can be brute forced. Algorithms like Bcrypt are stronger. You can examine the range of timestamped ciphers with public hash used in cryptography.

And what exactly do you mean by lost wallets?

Before 2013, there was no movement. or wallets that were stolen and not moved, I have a 6-month research for these.
73,000 BTC lost wallet and 155,000 BTC Lost and Stolen wallet total.

Personally i find it's hard to believe SHA-256 collusion happen that easily.

there are many privatkey sites. But none of the methods, none of them are the same as the structure I created.

well, this is probably a better version of this: https://lbc.cryptoguru.org/about they apparently found something there but not much, thanks for the explanation and good luck

Thank you for your contribution.

[ABCbits]

How exactly it's flawed or inadequate? It's still deemed secure until now and at that time, Satoshi couldn't use Schnorr Signature due to patent.

in the old days it would have been impossible. But now any password without a timestamp can be brute forced. Algorithms like Bcrypt are stronger. You can examine the range of timestamped ciphers with public hash used in cryptography.

What are you talking about? secp256k1 (as part of ECDSA) is used to generate public key and sign transaction/message, not handling password.

And what exactly do you mean by lost wallets?

Before 2013, there was no movement. or wallets that were stolen and not moved, I have a 6-month research for these.
73,000 BTC lost wallet and 155,000 BTC Lost and Stolen wallet total.

IMO it's flawed way, when i've seen people claim they attempt to recover their Bitcoin they obtained a decade ago or longer. Besides, how do you determine whether certain Bitcoin were stolen? Rely on people's report?

[btcdvl]

What are you talking about? secp256k1 (as part of ECDSA) is used to generate public key and sign transaction/message, not handling password.

Just so you understand the subject, there are much superior methods other than SHA-256 Eliptic Curve that you can generate both public and private keys. I know what Public Key and Private Key are. Satoshi designed it as a system that is impossible to recycle but can be signed with a public key. A private key gives you full access.   But today's cryptography is way beyond that. That's why it's not bruteforce-proof.

IMO it's flawed way, when i've seen people claim they attempt to recover their Bitcoin they obtained a decade ago or longer. Besides, how do you determine whether certain Bitcoin were stolen? Rely on people's report?

I'm looking at how people use technology and what their security is. 

Actually, your point of view is right, opening the door of a house with thousands of keys is a similar level of theft.
We agree that this is unethical.

My point of view is to accelerate this process and evolve cryptocurrencies into higher-level structures.

The principle of Bitcoin was built entirely on being trustworthy against other valuable currencies.

The Chinese, who are not asleep, with a good ASIC and good Logic, will design this and take over BTC funds.

[stwenhao]

This is the right number 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,575,177,306,100,000,000,000,000

It is not. And your AI tool is terrible at math, so we are safe. Maybe one day, you will get at least the number of possible private keys correctly.

And you don't need AI for that. You can read it here: https://neuromancer.sk/std/secg/secp256k1

[kTimesG]

So he wants to merge HEX64 hashed blocks into the Unifying field using technology, in order to break SHA Elliptic Curve passwords of lost wallets, by adapting the field modulus to something better: a 272 bits AI generated non-prime number, as the base of the reward system.

That sounds completely legit. Someone should hurry building up the circuitry for this stuff, while we scrape our heads how to move our addresses off this soon-to-be-obsolete private key system.

[btcdvl]

This is the right number 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,575,177,306,100,000,000,000,000

It is not. And your AI tool is terrible at math, so we are safe. Maybe one day, you will get at least the number of possible private keys correctly.

And you don't need AI for that. You can read it here: https://neuromancer.sk/std/secg/secp256k1

I'm sorry I couldn't get back to you right away.

10110111 10011000 10110010 00100000 01010111 10011111 10101101 11111011
10011010 11011001 00110111 00011011 00010101 01000000 11111110 11100011
01100011 01010101 10110111 11110000 01010011 01110010 01000100 01101101
11101000 01001011 10001101 00110111 00100111 11000111 00100001 00111000

Its content is encrypted in all variations of 256-bit.
It is not a structure added to it or outside of it.
Your secp256k1 is just a technique to create a public and private key.
To summarize


SHA-256 in ECDA space
0000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000001

= 0000000000000000000000000000000000000000000000000000000000000001 HEX64 variant

Wallet address = 1BgGZ9tcN4rm9KBzDn7KprQz87SZ26SAMH

https://btckeygen.com/

you can access it here.

[DaCryptoRaccoon]

Why do all these OPs assume the coins are lost and just not being held by the users.

Just because something don't move don't make it fair game...

At this point the forum should really stop allowing these types of cracking hacking stealing topics.

YOU have no proof the coins that have not moved are lost.  ZERO proof...

The mainstream are semi-floating the idea becase they would love nothing more than to do something to try "recover" the "LOST" (or sleeping) coins.

These topics are nothing more than brute force attempts on other people property.

Build something usefull....Not destructive.

PS go find a blackhat forum this is not blackhat stealing world...