Ahhh, I think I see the misunderstanding. I'm going to take a guess that you're native language is not English?
000001 = zeros in front of 1
1000000 = zeros behind 1
Confusing, hmm. 000001 = 1 with 5 leading zeros. 100000 = 1 with 5 trailing zeros. Here, 01, 0 comes before the 1, therefore we say 1 with a 0 behind it. Math is a universal language though, trying to change it's terms will confuse people. Anyways, I have got my own mirror-verse to deal with. Thanks for talking with machine language with humans.😉 |
|
|
|
From
addr: c. 1MRxjnjFDhZfjtjgpxBNczsMGVEtYqfFyS u. 1Jy6aHcRTWjiPN9DpjZztk2F8xY9iNsaj2
020000000000000000000000000000000000000000000000000000000000000001
040000000000000000000000000000000000000000000000000000000000000001483ada7726a3c 4655da4fbfc0e1108a8fd17b448a68554199c47d08ffb10d4b8
```````
```````all hex range of x
```````
```````
to
addr: c. 1LCQXAGayRCWdAGrh7NKWEcyQNfbbxPdtw u. 1F18os1CipgxyUj9wBMY4yK1HEVUaub2Nr
02ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
04ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff483ada7726a3c 4655da4fbfc0e1108a8fd17b448a68554199c47d08ffb10d4b8
there are addresses with public keys where the coordinate y is the same.
More interesting is the fact that, the public key 02ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff is the correspondence for the same addresses 1LCQXAGayRCWdAGrh7NKWEcyQNfbbxPdtw as 0200000000000000000000000000000000000000000000000000000001000003d0 and continuing like this, if we change the value of the y-coordinate of the public key, for each even/odd value it seems the compressed address is the same:
1LCQXAGayRCWdAGrh7NKWEcyQNfbbxPdtw
0400000000000000000000000000000000000000000000000000000001000003d00000000000000 000000000000000000000000000000000000000000000000002
1KmKgQHBMbequmyi9uP1yfa1vsNjdsjyEz
0400000000000000000000000000000000000000000000000000000001000003d00000000000000 000000000000000000000000000000000000000000000000003
1LCQXAGayRCWdAGrh7NKWEcyQNfbbxPdtw
0400000000000000000000000000000000000000000000000000000001000003d00000000000000 000000000000000000000000000000000000000000000000004
1KmKgQHBMbequmyi9uP1yfa1vsNjdsjyEz
0400000000000000000000000000000000000000000000000000000001000003d00000000000000 000000000000000000000000000000000000000000000000005
`````
`````an so on
1LCQXAGayRCWdAGrh7NKWEcyQNfbbxPdtw
0400000000000000000000000000000000000000000000000000000001000003d0fffffffffffff fffffffffffffffffffffffffffffffffffffffffffffffffff
I could conclude from here that any compressed public address exists as many times as there are for each uncompressed address and vice versa, and the mathematical space of the corresponding keys that generate them is much larger and can be treated as a three-dimensional space.
Did you change the keys somehow? It seems most of them are invalid, I don't know where you got them, but you should put each public key inside a code bracket to better identify them. To be exact, the number of compressed and uncompressed keys are exactly 50-50. You don't happen to have any of their private keys do you? For a second I thought you just found hash collisions.🤣 |
|
|
|
|
Yeah, about that, I have bad news for Bob and Alice should remain a test subject model as she was before, 😂.
If Alice encrypts a message with her own p, nobody other than Alice could decrypt the message.
But you could ask Alice to encrypt a message using Bob's public key so that Bob could decrypt it using his private key.
You should first understand how these things work and then try to use such tools, though to understand how they work you need to use the standard tools which already exist, GPG, PGP, are 2 useful tools.
Encrypting messages with bitcoin keys is possible but not a good practice. Let secp256k1 be used to store coins.
|
|
|
|
Anyway to answer your PM I'm 80% certain about the range. I created the wallet years ago manually and was dumb enough to use it!!
That said, I think I prefer searching for it myself. If you would like to help with the setup, where it's best to rent GPUs, what version of Kangaroo to use, etc happy to pay a fee. I hope you understand, it's too much BTC to just give away the public key on a forum!
Thanks!!
Yeah, somehow I doubt it, being a newbie years ago knowing how to manually generate a very low range key and somehow depositing a large amount in it and then after years now you remembered that you have these coins , yet the funny thing is that you have the public key not the private key, having the public key could mean that you have spent from the address, so the address has an exposed p in a low range, one could use all public keys with balance on blockchain and use kangaroo to find your imaginary key, but we all know there is no such a key and nobody would manually generate low range key to deposit and then forgets the key. Lol |
|
|
|
Who told you that? 1 with 77 zeroes behind it is just 1, doesn't matter how many 0 you add behind it, the total number of keys is called N, go search for it, it is also the private key for the end range key -1.
What are you talking about? 100 is greater than 10, and 1000 is greater than 100. Obviously, the number of zeros behind the 1 matters. Bitcoin has approx this many possible private keys: 100000000000000000000000000000000000000000000000000000000000000000000000000000 Whatever that number is called. A private key is a 32 byte array, and that above number is how many possible combinations a 32 byte array has. It's basic math. Well I don't know what byte array stuff are, but the exact number of bitcoin private keys is FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140 or in decimal 115792089237316195423570985008687907852837564279074904382605163141518161494336. What you described earlier, a 1 with zeroes behind it looks like this 000000000000000000000000000000000000000000000000000000000000000000000000000001 maybe "behind" means something different in your world, like front? Tell me, are you from the upside down world? Lol. Number you posted above is this in hex : dd15fe86affad91249ef0eb713f39ebeaa987b6e6fd2a0000000000000000000 and that doesn't look like N to me. Maybe try to be exact next time, maybe you meant this ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff which is 2^256 -1, so if we add 1 to it, we'll have 10000000000000000000000000000000000000000000000000000000000000000 in hexadecimal = 2^256 exactly.
As I said, we are from different worlds, but please try to provide correct information. |
|
|
|
How many keys can you check per second for just 1 address? That's the important part, never mind the comparing part, tell us how many per second for 1.
The number of possible private keys is a 1 with 77 zeros behind it, whatever that number is called. Here's what ChatGPT says:
Who told you that? 1 with 77 zeroes behind it is just 1, doesn't matter how many 0 you add behind it, the total number of keys is called N, go search for it, it is also the private key for the end range key -1. |
|
|
|
|
Do you need them for multiverse people or what? Since there is no actual use for 10M address a day, your request is sus.😉 I could however generate 30M addresses per second with my laptop! High end GPUs could give you several billion addresses per second.
Welcome to the hunt for the hidden treasures of Satoshi.😅
|
|
|
|
./keysubtracter -p 02ceb6cbbcdbdf5ef7150682150f4ce2c6f4807b349827dcdbdd1f2efa88 5a2630-n 100 -b 120 Note the bolded part above, no space therefore it starts to produce invalid keys. 03f1d41da8acf0506f3bf7140b5629dd33a5cf546133479530cd8065e335a97666 # - 13292279957849158729038070602803446
02000000000000000000000000000000000000000000000000000000000000000 # + 13292279957849158729038070602803446
02b70ae2dcb442548570313f652b91ca093a3acac3a2441cb64614e8195505b6b8 # - 26584559915698317458076141205606892
0367dabeef20a6a8b7b5555b162cc8c8489e3134dcec624fe028573c34dbbf20f6 # + 26584559915698317458076141205606892
02a1d21298779f888cd8169f9ed59e4383219cdadbdb342ba886034ef9013b89be # - 39876839873547476187114211808410338
02ae015703cbaee9570dc648d7bce78ac7cb438630e09d69eef4f1208655e1027d # + 39876839873547476187114211808410338 Note one of the public keys above is the 0 public key aka k(0) public key, it shows up if you subtract your k from your p, basically point at infinity. Now our actual target's k is 13292279957849158729038070602803446 because we subtracted it from our target. Showing examples for newbies to understand, not that a few posts above I wasn't a total noob, now I act as if I know things, go figure.😅 |
|
|
|
Posting in off topics to look for co-founder not a right move, you could move it to project development board found by clicking on this link : https://bitcointalk.org/index.php?board=12.0And btw, if you ever needed someone to shill, sockpuppet and deceive the unsuspected and unaware, let me know because those things are my expertise, Ok here are some examples of my past works which were killing *literary. Here we go : "Wow, cool pro" So you might ask why is it incomplete? Can you imagine how hard it is to shill for hundreds of garbage projects a day? One can get tired and forget to finish the sentence, though I guarantee that half sentence would also work greatly. Here is another one : NTFs are very pro Or : Looking forward to this, Interesting, I'm watching this! etc.
Don't take offence, I have been constantly saturated with ICOs for years, and now with NTFs which are the same as ICOs with a different looks and theme, so no matter how much such projects seem to be legit, I just treat them all the same. *= lol. |
|
|
|
|
So, I have had several discoveries while I was messing around the things I really don't understand "yet", and I would like to share them with you all, knowledge should be shared.
First, finding the k inverse, easy as subtracting your k from N, and distance between your k and your -k is 200% +1 or - 1, lol.
Subtracting your x from itself will actually double your k.
Adding to your -x is actually subtracting from your x.
Subtracting too much, a value greater than your k from your p will actually add the difference to your k, example: subtracting in decimal, 60 from p(k50) will add 10 to your k which in this case you will see p(k60), though this one is an exception, if you add 10 to your k and then subtract your k from this new k, you will see p(k10), which is totally useless and disappointing. Lol.
*And snag! Sharing more than this is actually unwise as it will help breaking elliptic curve cryptography.
*= trying to sound knowledgeable while I understand 0.🤣
|
|
|
|
My man, * you 100 percent understand lol.
Lol^256, my man, I got how to use this thing the first time you explained, what I had encountered was due to no space between target and -o output.txt in the command line page, so it displayed the 0 point public key and all the offsets were invalid coordinates, lol. However when your target is one of the exact points you are subtracting, in the out put file it will show for example: 020000000000000000000000000000000000000000000 # + 1 and your target k is actually 1, so when the tool subtracts 1 from your target, it shows the 0 point public key. This is actually very interesting, because you just need to get "lucky" and subtract the exact k as the k of your target from your target to see the 0 point p. Maybe you didn't know about this, so my man it is you who doesn't 100 percent knows the tool which you developed. Lol^N-1. *= not the original quote, modified by me.😅 |
|
|
|
|
So we need to understand that something still exist even if we don't see it? I believe we pretty much understand that already, it doesn't need any special skills.😉
However quantum physics suggest that there exist states of quantum particles where they can not exist until someone looks at them, it's a nonsense theory suggesting if you are not observing an object directly, the object doesn't exist, this could be the result of double slit experiment, because when you start observing particles, they change their behaviour.
But that has not been proven yet and it could be the result of misunderstanding the infrastructures underlying the quantum world.
|
|
|
|
|
Is anyone around these woods? So I understand if we hit a target while adding and subtracting it will show the public key zero aka 02000 with a lot of other zeros, but what does it mean when I have done the subtraction and it shows 0200000 # target. What to do now?
|
|
|
|
|
So I was thinking about a new method, I call it GPS tracking, it simply uses triangulation tactic to pinpoint the location of the key. The question though, how do I derive the key given not 3 but 9 interconnected values? I have the mutual distances between several keys, I have tried at least 50 combinations and all lead to dead end, but I know there is a way to estimate the closest location coordinates of the key I'm looking for.
For example, if I know the distances between 3 objects, I should be able to determine the nearest point to at least one of them, right?
|
|
|
|
chatGPT suggest this.. It won't work because the math to do it (correctly) is not known import os
import sys
from hashlib import sha256
from binascii import hexlify, unhexlify
from ecdsa import SECP256k1, SigningKey, VerifyingKey
from ecdsa.ecdsa import generator_secp256k1
def find_generator_point(P):
count = 0
G = generator_secp256k1
while P != G:
P = P.__rmul__(2)
count += 1
with open("divisions.txt", "w") as f:
f.write(str(count))
return P
if __name__ == '__main__':
# Generate a random private key
sk = SigningKey.generate(curve=SECP256k1)
# Derive the public key from the private key
vk = sk.get_verifying_key()
# Convert the public key to an EC point
P = vk.pubkey.point
# Find the generator point by dividing P repeatedly
G = find_generator_point(P)
print("Generator Point: ({}, {})".format(hexlify(G.x().to_bytes(32, 'big')).decode(), hexlify(G.y().to_bytes(32, 'big')).decode()))
It won't work because that AI is an idiot, lol there is no SHA256 involved in finding k from p, and there is no "dividing" repeatedly until finding G, what AI can suggest is the worst way possible to brute force because it's an imbecile computer.😅 |
|
|
|
There are not mathematically is just Random. I try many theory mathematics and found some rule of puzzle. There are never complete.
If you like lottery of bitcoin. Try your luck.
Of course they are mathematical, even the keys with no exposed public keys require mathematical shortcuts to speed up the brute force, and the ones with known public keys, it is as simple as + and - , but the order of parameters and the equations makes it a bit hard. Don't forget, everything works according to a sets of mathematical algorithms, universe functions based on equations and complicated algos. Imagine when there is a possibility of 2 distanced sub particles interacting simultaneously with one another, a tiny elliptic curve is just a cake comparing. Moreover, since everything is based on math, we could use the math of other fields such as astronomy, orbital trajectory, and orbital slingshot calculations are applicable here, if you knew how satellites/ spaceships use gravity to boost their speed without using any energy, you'd know that slingshot equation is the best if you tweak it a bit in order to solve the known keys.😉 |
|
|
|
I knew the puzzles, but didn't catch the upgrade. For who also missed it: this transaction sent about $25 million to these addresses. That makes it worth it to allocate much more processing power to cracking the puzzles. Crazy  Well, It's not about more power, of course anyone could use hundreds of high end GPUs to solve for example #125, the point is to find a way to solve it with the help of mind not silicon. Now that you said it, $25M is too much yet very little to spend for safety analyzing. I wish I knew how to automate and sort data processing like you, lol I have millions of public keys I just look for collisions with my eyes.🤣 |
|
|
|
Since you are wanderer your self, you could understand others when they wonder, so I was wondering what happened to your newly improved version of kangaroo/bsgs tool? A good dev always shares the best of his work with the world😉, we'll keep on waiting! |
|
|
|
On April 16, someone sent 0.09BTC to an address with publicly known private key. It disappeared instantly with a $12 fee. Someone earned stole $2700 from this. Yeah, a lot of other things happened that day, for example the same certain someone (Satoshi) sent around 900 bitcoins to puzzle addresses to increase the prize of solving them, and you know how he is, he likes to tip people with Gs, $. 😉 |
|
|
|
|
Show Posts
