Search content
Sort by
Showing 20 of 23 results by btcdvl
It offers pictures produced with artificial intelligence. I believe it will be a success.
https://x.com/DogeKamala
Max Supply : 100.000.000
Pre- Sales : 2.000.000
AirDrop : 10 Seasons Total 5 .000.000
http://t.me/dogemilf
https://tools.smithii.io/launch/DogeMilf
Lots of weird mumblings of your "magic formula/algorithm/whatever/P2P". Just don't waste our time any further, please, it's fine when you waste yours alone.
You repeatedly violate rule #32 of forum rules, too bad this won't get you banned. But that would be a too easy solution. Go ahead, embarrass yourself further, until most will simply ignore you, because: don't feed the trolls, old rule, still valid.
Anything substantial to fill your empty words? No need to repeat your already posted blank ideas.
I can watch "your success" easily, I've a watch-only wallet of the Patoshi blocks, roundabout 1.1 million Bitcoins, presumably mined by the forum's founder. I'm not worried, those approx. 21954 mined blocks were and still are safe, so are a lot of other old and newer blocks and their UTXOs. Surprise me, even when I don't approve any nefarious actions to move those coins, because they're not yours, period!
You repeatedly violate rule #32 of forum rules, too bad this won't get you banned. But that would be a too easy solution. Go ahead, embarrass yourself further, until most will simply ignore you, because: don't feed the trolls, old rule, still valid.
Anything substantial to fill your empty words? No need to repeat your already posted blank ideas.
I can watch "your success" easily, I've a watch-only wallet of the Patoshi blocks, roundabout 1.1 million Bitcoins, presumably mined by the forum's founder. I'm not worried, those approx. 21954 mined blocks were and still are safe, so are a lot of other old and newer blocks and their UTXOs. Surprise me, even when I don't approve any nefarious actions to move those coins, because they're not yours, period!
Patoshi blokları bunu bilmiyordum ve bu bilgi benim için değerli. Bu tartışmayı bilmediğim şeyleri öğrenmek ve tavsiyeleri dinlemek için yapıyorum. her dakika yeni bir proje çıkıyor. Kimse teknolojinin güvenliği ve faydası ile ilgilenmiyor. Bu arada araştırdığım bir şeyi daha paylaşayım. Bitcoin geliştirmeyi destekleyen şirketlerin ve yazılımcıların çoğu bu tür teknikleri deniyor. Github'da linkler buldukça burada paylaşacağım.
Translated with DeepL.com (free version)
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
....
You are arguing with someone who does not even understand basic concepts of math and encryption and how miners work.
Mark Twain:
Quote
Never argue with an idiot. They will only bring you down to their level and beat you with experience,
As I posted a couple of hours ago people like him keep coming here every once in a while thinking they know better then everyone else. You point out the things that are wrong with their logic and math as you and others have done and then walk away and let them waste their time and effort and money.
-Dave
SH256 is impossible to recycle. But it is not an impossible algorithm to catalog. If a number has an end and a beginning, the only obstacle is the technological power at the time.
The first computer I used ran on 16MB of RAM.
That's the maximum we would have seen if the development had been faithful to your ideas.
The fact that you have no other idea than to manipulate people is a psychological branch and I am not very knowledgeable about it.
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
....
You are arguing with someone who does not even understand basic concepts of math and encryption and how miners work.
Mark Twain:
Quote
Never argue with an idiot. They will only bring you down to their level and beat you with experience,
As I posted a couple of hours ago people like him keep coming here every once in a while thinking they know better then everyone else. You point out the things that are wrong with their logic and math as you and others have done and then walk away and let them waste their time and effort and money.
-Dave
Lots of insults do not make you right. This form was created to give a different explanation than anyone else. This question and discussion thread was opened to reason, not to satisfy your ego.
You are like the Europeans of the 15th century who considered anything that goes outside your rules and the teroi you know as bad.
As you say, we just need to shut up and you can go to other threads and insult. I am ignorant anyway.
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
Your numbers do not add up for HEX64.
This thread was only opened to investigate the technical possibility of this.
There is no technical possibility to count up to 2**256, let alone match stuff at each iteration.
It does not matter if you use a single computer, 10.000 computers, 1 trillion CUDA devices, 1 quadrillion ASIC devices each running whatever amount of TH/s, or even all the atoms in the Universe, each as a computing node in your distributed P2P. Again, there is no physical possibility to build even a simple counter that does: 1, 2, 3, 4.... 2**256 without ending up in the situation of witnessing the last proton in the universe decay itself.
You would need multiple parallel multiverses in order to be able to have the required energy to flip over bits from 0 to 1 which is needed, if you want to traverse all those 2**256 variations of all possible SHA256 values you intend to break.
And even if you do succeed, you would then have to break the corresponding secp256k1 of the public key for which you have found a collision to an address, which is itself a 2**128 operations problem.
The answer to your question is NO, but you should have known that already before even needing to open such a topic.
I am thankful that Isaac Newton did not think like you.
Screening from a different perspective
https://privatekeys.pw/scanner
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
Your numbers do not add up for HEX64.
This thread was only opened to investigate the technical possibility of this.
There is no technical possibility to count up to 2**256, let alone match stuff at each iteration.
It does not matter if you use a single computer, 10.000 computers, 1 trillion CUDA devices, 1 quadrillion ASIC devices each running whatever amount of TH/s, or even all the atoms in the Universe, each as a computing node in your distributed P2P. Again, there is no physical possibility to build even a simple counter that does: 1, 2, 3, 4.... 2**256 without ending up in the situation of witnessing the last proton in the universe decay itself.
You would need multiple parallel multiverses in order to be able to have the required energy to flip over bits from 0 to 1 which is needed, if you want to traverse all those 2**256 variations of all possible SHA256 values you intend to break.
And even if you do succeed, you would then have to break the corresponding secp256k1 of the public key for which you have found a collision to an address, which is itself a 2**128 operations problem.
The answer to your question is NO, but you should have known that already before even needing to open such a topic.
I don't need your made-up information, I am aware of the difficulty. 1 TH power may be a power you will despise. But I'm sure it will be a serious force on P2P.
3DES is a 168-bit security algorithm. And it has now been removed from firewall protocols.
https://en.wikipedia.org/wiki/Triple_DES
Mainly because of the markup. So if you can write something numerically, that means you can mark it as a mode. I've written to you many times about the algorithm that will not be marked, Timstamp Hash Bcrypt.
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
Code:
def calculate_time_to_explore_keyspace(attempts_per_second):
total_keys = 2**256 # Approximately 1.15 x 10^77
seconds_per_year = 60 * 60 * 24 * 365
keys_per_year = attempts_per_second * seconds_per_year
total_years = total_keys / keys_per_year
total_seconds = total_years * seconds_per_year
total_minutes = total_seconds / 60
total_hours = total_minutes / 60
total_days = total_hours / 24
return total_years, total_seconds, total_minutes, total_hours, total_days
def print_detailed_time(total_years, total_seconds, total_minutes, total_hours, total_days):
print(f"Total time to explore the entire keyspace: {total_years:.2e} years")
print(f"Total time in seconds: {total_seconds:.2e} seconds")
print(f"Total time in minutes: {total_minutes:.2e} minutes")
print(f"Total time in hours: {total_hours:.2e} hours")
print(f"Total time in days: {total_days:.2e} days\n")
def present_keyspace_analysis():
print("Keyspace Analysis for Bitcoin Private Keys")
print("=" * 40)
high_attempt_rate = 10**9 # assuming 1 billion attempts per second (very optimistic)
total_years, total_seconds, total_minutes, total_hours, total_days = calculate_time_to_explore_keyspace(high_attempt_rate)
print(f"Assuming {high_attempt_rate:,} keys can be tested per second:")
print(f"Total keys in Bitcoin (2^256): {2**256:.2e} keys")
print_detailed_time(total_years, total_seconds, total_minutes, total_hours, total_days)
hex64_attempts = 10**18 # 1 quintillion HEX64 combinations (also very optimistic)
total_years_hex64, total_seconds_hex64, total_minutes_hex64, total_hours_hex64, total_days_hex64 = calculate_time_to_explore_keyspace(hex64_attempts)
print(f"Assuming {hex64_attempts:,} HEX64 combinations can be tested per second:")
print_detailed_time(total_years_hex64, total_seconds_hex64, total_minutes_hex64, total_hours_hex64, total_days_hex64)
print("Comparison of Bitcoin keyspace sizes:")
print(f"- 256-bit keyspace: 2^256 ≈ {2**256:.2e} keys")
print(f"- 135-bit public key space: 2^135 ≈ {2**135:.2e} keys")
print(f"- 67-bit address space: 2^67 ≈ {2**67:.2e} keys")
print("\nProbability of randomly guessing a Bitcoin private key:")
probability = 1 / (2**256)
print(f"The probability of successfully guessing a valid Bitcoin private key: {probability:.2e}")
print("\nConclusion:")
print("Even with highly optimistic assumptions about the number of keys tested per second,")
print("the time required to brute-force the entire Bitcoin private key space is")
print("astronomically high and completely impractical, making the claims about")
print("recovering lost wallets through this method unfounded.")
if __name__ == "__main__":
present_keyspace_analysis()
total_keys = 2**256 # Approximately 1.15 x 10^77
seconds_per_year = 60 * 60 * 24 * 365
keys_per_year = attempts_per_second * seconds_per_year
total_years = total_keys / keys_per_year
total_seconds = total_years * seconds_per_year
total_minutes = total_seconds / 60
total_hours = total_minutes / 60
total_days = total_hours / 24
return total_years, total_seconds, total_minutes, total_hours, total_days
def print_detailed_time(total_years, total_seconds, total_minutes, total_hours, total_days):
print(f"Total time to explore the entire keyspace: {total_years:.2e} years")
print(f"Total time in seconds: {total_seconds:.2e} seconds")
print(f"Total time in minutes: {total_minutes:.2e} minutes")
print(f"Total time in hours: {total_hours:.2e} hours")
print(f"Total time in days: {total_days:.2e} days\n")
def present_keyspace_analysis():
print("Keyspace Analysis for Bitcoin Private Keys")
print("=" * 40)
high_attempt_rate = 10**9 # assuming 1 billion attempts per second (very optimistic)
total_years, total_seconds, total_minutes, total_hours, total_days = calculate_time_to_explore_keyspace(high_attempt_rate)
print(f"Assuming {high_attempt_rate:,} keys can be tested per second:")
print(f"Total keys in Bitcoin (2^256): {2**256:.2e} keys")
print_detailed_time(total_years, total_seconds, total_minutes, total_hours, total_days)
hex64_attempts = 10**18 # 1 quintillion HEX64 combinations (also very optimistic)
total_years_hex64, total_seconds_hex64, total_minutes_hex64, total_hours_hex64, total_days_hex64 = calculate_time_to_explore_keyspace(hex64_attempts)
print(f"Assuming {hex64_attempts:,} HEX64 combinations can be tested per second:")
print_detailed_time(total_years_hex64, total_seconds_hex64, total_minutes_hex64, total_hours_hex64, total_days_hex64)
print("Comparison of Bitcoin keyspace sizes:")
print(f"- 256-bit keyspace: 2^256 ≈ {2**256:.2e} keys")
print(f"- 135-bit public key space: 2^135 ≈ {2**135:.2e} keys")
print(f"- 67-bit address space: 2^67 ≈ {2**67:.2e} keys")
print("\nProbability of randomly guessing a Bitcoin private key:")
probability = 1 / (2**256)
print(f"The probability of successfully guessing a valid Bitcoin private key: {probability:.2e}")
print("\nConclusion:")
print("Even with highly optimistic assumptions about the number of keys tested per second,")
print("the time required to brute-force the entire Bitcoin private key space is")
print("astronomically high and completely impractical, making the claims about")
print("recovering lost wallets through this method unfounded.")
if __name__ == "__main__":
present_keyspace_analysis()
Your numbers do not add up for HEX64.
I apologize for writing so late. I will formulate the structure with a different argument without going into detail, because the theory you wrote is just linear search, the method I use is point-to-point, think of it like this, there are trillions of spheres in a circle, there is a dotted communication network between these spheres. I send a different hash generator to the circle furthest away from the collision, like searching at different points.
This search is not something I made up. Think of it as the math equivalent of a mode.
The number of wallet addresses that I think are completely missing from these is 743.
I realize it is incredibly difficult even with these factors, but ASICs are running at TH power (10,000,000,000,000,000) for this block generation. Secp256k1 can be variable. Cuda nvida allows 1/3 of that in Python. If 10,000 users are included in the average network, it still reaches 100 quadrillion throughput.
Even the model approximation can create another formula based on probability and 743 wallet hits given Python Functions. I will spend time to make a few formulas of this, there is an important technical fair. After a few days I will present you the approximate probability with the structure I have.
Also, if there is an ASIC pool, machines like Antminer S9 are running 13.5 TH.
This thread was only opened to investigate the technical possibility of this.
But the P2P model beta test is available.
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
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...
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...
The rules of this game are set by satoshi. I don't do anything outside the rules of this game.
If you had enough information, you would know the criteria for lost wallet assets.
It's not a wallet theft. It's not a theft. It's a lack of satashonin rules.
And there will be a lot of developers and designers who will try this after me.
What have you done for development? Crypto Dom needs a stronger mechanism and more security to prevent its destruction.
1 BTC $70,000
1 BTC = Hash
1. a lot more than you have ever done that is for sure..
2. and stealing coins just because "You think you can" is not a excuse to do so..
3. There is no "criteria" for a lost wallet your just trying to justify stealing.. If a bank keeps a gold bar for 30 years in a valut don't mean you can break in and steal it because it has dust on it and has not moved for time..
Legit your rat theif and not welcome here.. -1 trust for being a scumbag and trying to convince people YOU know there coins are lost.
How fooliish.
Nowhere does it say I will take the funds, nowhere does it say I will steal them. I am trying to raise awareness in the Bitcoin global network of ignorance. I am sure this topic will be very valuable in the future. Because it's a science
First you talk about my inexperience, then you can't provide a scientific argument. If that doesn't work, you are so worried that you insult me.
I will not stoop to your level.
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
You are a difficult character for innovations.
Stealing others' money is hardly innovation.
Plus, you really want everybody around here explain that you fail to gasp how big some numbers are... or help you steal.
And there will be a lot of developers and designers who will try this after me.
I can bet that many have tried also before you, in a way or another.
Go ahead, give it a try. Let us know after a while if you have found anything (heh) or you understood your chances.
To be aware of this, you first need to know that it is not theft. Promoting Blockchain security awareness is not the same as abusing Blockchain security.
Is it written anywhere that I will withdraw the funds and use them or distribute them?
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
Current computing can't break bitcoin's encryption. Even with all the world's electricity and 4nm dedicated ASICs.
Maybe quantum computing will achieve better results. Till then we have time to upgrade the network to a better more quantum resistant standard.
I'm not worried. Everyone's BTC will be safe. No reason to fear monger if you don't understand cryptography. I'd just recommend doing some reading for now instead of writing such posts.
To put it bluntly, if a number is so large you can't even put it in your title, do you really think it'll be that easy to break this strength of cryptography?
Maybe quantum computing will achieve better results. Till then we have time to upgrade the network to a better more quantum resistant standard.
I'm not worried. Everyone's BTC will be safe. No reason to fear monger if you don't understand cryptography. I'd just recommend doing some reading for now instead of writing such posts.
To put it bluntly, if a number is so large you can't even put it in your title, do you really think it'll be that easy to break this strength of cryptography?
I'm not talking about a computer, I'm talking about P2P. For that, you need to read what is written first.
Give me a mathematical probability that it won't happen.
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
PS go find a blackhat forum this is not blackhat stealing world...
I wouldn't worry, judging by the awareness level of OP on how things work, he'd probably be the one who gets hacked if he ever posts his brilliant ideas to the BH community.
There are too many things OP claimed that are complete bogus to anyone even bothering to refute them. Latest one is using a SHA output as a private key, which actually works the other way around. But hey, I'm waiting for that ASIC that can break two different hashing algorithms just to end up with a 256-bits (128-bit secure) public key! I guess it doesn't matter there's not enough juice in the universe to even count all the attempts required to do that.
Hey, by the way, you can't escape that easily. What do you think SHA256 looks like? Can you write me a SHA256 bit key?
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
Other than that, write me something I don't know and haven't heard. I'm waiting. Is Chuck Norris changing this code in the background
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
PS go find a blackhat forum this is not blackhat stealing world...
I wouldn't worry, judging by the awareness level of OP on how things work, he'd probably be the one who gets hacked if he ever posts his brilliant ideas to the BH community.
There are too many things OP claimed that are complete bogus to anyone even bothering to refute them. Latest one is using a SHA output as a private key, which actually works the other way around. But hey, I'm waiting for that ASIC that can break two different hashing algorithms just to end up with a 256-bits (128-bit secure) public key! I guess it doesn't matter there's not enough juice in the universe to even count all the attempts required to do that.
There is no information to say that the content I have presented on this is wrong. In short, you have no argument.
I want to write to you with mathlab output, which is a linear algorithm that calculates probability.
V = { v ∈ F₂²⁵⁶ | v = (v₁, v₂, …, v₂₅₆), vᵢ ∈ {0, 1} }
I feel your excitement when you first heard about Bitcoin. In those years I was struggling with 5 different languages and math formulas.
You are a difficult character for innovations.
As for the hack, your arguments that deify bitcoin as the perfect deity have no proof. Satoshi forgot something.
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
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...
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...
The rules of this game are set by satoshi. I don't do anything outside the rules of this game.
If you had enough information, you would know the criteria for lost wallet assets.
It's not a wallet theft. It's not a theft. It's a lack of satashonin rules.
And there will be a lot of developers and designers who will try this after me.
What have you done for development? Krypton needs a stronger mechanism and more security to prevent its destruction. 1 BTC $70,000
1 BTC = Hash
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
Quote
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.
SECP256K1
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
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
SHA-256 in ECDA space
0000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000 0000000000000000001
= 0000000000000000000000000000000000000000000000000000000000000001 HEX64 variant
Wallet address = 1BgGZ9tcN4rm9KBzDn7KprQz87SZ26SAMH
https://btckeygen.com/
you can access it here.
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
Quote
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.
Quote
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.
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
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.
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
Quote
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.
Quote
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.
Quote
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.
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
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.
I want the lost wallets to be distributed equally among all clients. The software does it automatically.
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.
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
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 ?
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 3 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.
Re: 1,157,920,892,373,161,954,235,709,850,086,879,078,532,699,846,656,405,640,394,57
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?
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.