Pages:
Author

Topic: 0.1 BTC for python help! (Read 971 times)

copper member
Activity: 1330
Merit: 899
🖤😏
April 17, 2023, 10:21:02 PM
#58
I was looking for because BTC was placed on a strategic location. Enjoy your puzzle solving!
Strategic location was lost till yesterday! I mean you are a terrible strategist , lol.

Enjoy your puzzle solving!
We will because that's the idea!


To everyone here, when someone offers imaginary money, just control your drooling and demand evidence of funds, specially for strangers.
newbie
Activity: 19
Merit: 1
April 15, 2023, 11:38:06 PM
#57
Great NEWS!!!!!
I found my rouge BTC. A simple list of collisions made things quite manageable, which was exactly I was looking for because BTC was placed on a strategic location. I thank all of you guys for your suggestions as well as criticism. All I say here is that, things won't always be the same! Elliptic Curve encryption system will soon be redundant! Enjoy your puzzle solving!

Congrats! but come on tell me the truth, you found it with the help of the forum and you regretted giving rewards, Lol.
sr. member
Activity: 1190
Merit: 469
April 15, 2023, 11:26:44 PM
#56
OP is full of shit. Wasting our time asking for help for his stupid elliptic curve fail and then proclaiming the end of elliptic curve.

he'll probably be posting about his new quantum computer soon. watch out  Shocked problem is, his quantum computer will probably not have any error correction so the results will be wildly off.
legendary
Activity: 3472
Merit: 10611
April 15, 2023, 10:05:34 PM
#55
1 billion public key is a 130 GB text document, you just need a lot of RAM to load it all or split it into several txt documents
It depends on how you store it and how you use it.

For example it could be stored as binary (instead of hex in a text file) and in its compressed form. That is 33 byte per pubkey and a billion of them makes it a 33 GB file (65 GB for uncompressed).

As for usage of this data, you don't need to load it all in memory. You could use a database and/or sort the list in a way that would make it faster to search using methods such as binary search, etc.
jr. member
Activity: 47
Merit: 12
gmaxwell creator of 1000 BTC puzzl + Pinapple fund
April 15, 2023, 09:05:12 PM
#54
OP is full of shit. Wasting our time asking for help for his stupid elliptic curve fail and then proclaiming the end of elliptic curve.
sr. member
Activity: 1190
Merit: 469
April 15, 2023, 06:33:57 PM
#53
Great NEWS!!!!!
you decided to start backing up your funded bitcoin addresses?

Quote
Elliptic Curve encryption system will soon be redundant! 
how did you figure that?  Shocked
newbie
Activity: 18
Merit: 1
April 15, 2023, 03:47:56 AM
#52
Great NEWS!!!!!
I found my rouge BTC. A simple list of collisions made things quite manageable, which was exactly I was looking for because BTC was placed on a strategic location. I thank all of you guys for your suggestions as well as criticism. All I say here is that, things won't always be the same! Elliptic Curve encryption system will soon be redundant! Enjoy your puzzle solving!
sr. member
Activity: 1190
Merit: 469
April 14, 2023, 06:27:25 PM
#51
Quote from:  Unplugged Taste
I am still working on this thing by putting another BTC and moving forward with my research.
what exactly is the purpose of the research? to figure out ways to generate a private key that is complicated? A private key is just a number. Whether you get it by doing a single operation or a million trillion operations doesn't make that number any more secure. Lips sealed

Quote
I am simply a victim of untoward incident like a flood, a tornado, or lightening or house on fire or robbery etc we have little to no control over it.

That's not how I see it but whatever.  If you have a funded address then that particular private key needs to be backed up.

member
Activity: 182
Merit: 35
STRAIGHT FORWARD
April 14, 2023, 02:06:12 PM
#50
years ago I believe that I saw NotATether helped someone to maintain something like this. I think that the best thing to do would be handling your files to someone here that is trusted and let him work on the recovery.

Other option you can try; https://www.walletrecoveryservices.com/

I don't know him, didn't try him but was mentioned through trusted member here that I don't remember who
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
April 14, 2023, 02:00:18 PM
#49
Those who think I was dumb making 1 billion keys are also wrong. 1 billion is what is left in USB Drive, however originally they were 1trillion.
That's 66 TB. Must be a nice USB disk Roll Eyes

Quote
I am still working on this thing by putting another BTC and moving forward with my research.
Lol. That's literally the best way to describe what you're doing.

Quote
I am simply a victim of untoward incident like a flood, a tornado, or lightening or house on fire or robbery etc we have little to no control over it.
It's more like you threw your money in the fire place yourself. All of this could have been prevented if you didn't try to invent your own private key creation, but it looks like you haven't learned from it. I suggest this title for your next topic: "I lost 1 BTC again".
newbie
Activity: 18
Merit: 1
April 14, 2023, 01:02:40 PM
#48
If someone has any doubt or suspicions about what I am saying, they can simply leave, no big deal. I am not here to somehow skim or exploit anyone's programming capabilities, don't judge me. I will explicitly appreciate anyone's genuine help & reward accordingly. Those who think I was dumb making 1 billion keys are also wrong. 1 billion is what is left in USB Drive, however originally they were 1trillion. The reason I am not exposing my scheme is that I am still working on this thing by putting another BTC and moving forward with my research. I don't have any GPU neither want one & I am also not interested in 125 BTC puzzle rest assured. I am simply a victim of untoward incident like a flood, a tornado, or lightening or house on fire or robbery etc we have little to no control over it. you can call it dumb or whatever you like.
legendary
Activity: 3472
Merit: 10611
April 14, 2023, 06:22:08 AM
#47
Read it again Wink
Oh. I always automatically assume that the coins someone has is received from a third party (no access to that address). Tongue

Quote
I usually take rewards from Newbies with a grain of salt. Sometimes it's real, sometimes it isn't.
Yeah, They receive the same level of help regardless of the "offer".
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
April 14, 2023, 05:43:16 AM
#46
if OP shares the address and signs a message from the address that funded it, there's no longer a reason to doubt his story.
If OP could sign message from that address he wouldn't have been here since signing a message requires having the private key Tongue
Read it again Wink

Quote
Although if you want to not-doubt his story OP could share the public key + address. Considering that hashes inside addresses are not reversible to get the public key, the chances of it being a fake story diminishes significantly.
That will work too, but I guess OP doesn't want to share the public key. Sharing the address reveals less.

Quote
Although if you want the "reward" none of the above would help, you'd need to use an escrow Wink
I usually take rewards from Newbies with a grain of salt. Sometimes it's real, sometimes it isn't.
legendary
Activity: 3472
Merit: 10611
April 14, 2023, 05:33:12 AM
#45
And is it only me finding this suspicious? I wonder where is the address containing 1 btc? Because it has no out going tx, we can't find it's public key and steal the coin if that's what OP is afraid of. So where is the address in question?
The address is irrelevant, although if OP shares the address and signs a message from the address that funded it, there's no longer a reason to doubt his story.
If OP could sign message from that address he wouldn't have been here since signing a message requires having the private key Tongue
Although if you want to not-doubt his story OP could share the public key + address. Considering that hashes inside addresses are not reversible to get the public key, the chances of it being a fake story diminishes significantly.
Although if you want the "reward" none of the above would help, you'd need to use an escrow Wink
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
April 14, 2023, 04:37:59 AM
#44
And is it only me finding this suspicious? I wonder where is the address containing 1 btc? Because it has no out going tx, we can't find it's public key and steal the coin if that's what OP is afraid of. So where is the address in question?
The address is irrelevant, although if OP shares the address and signs a message from the address that funded it, there's no longer a reason to doubt his story.

maybe not suspicious but i find it strange why someone would need to generate 1 billion private keys if they are only going to use one of them. doesn't make any sense.
If it's true, OP made a very dumb mistake (but I'm sure he knows that already). Don't try to reinvent how to create private keys, it will increase the risk of losing your funds.

@Unplugged Taste: I get that you don't want to share the range, but can you at least share how large the range is? That should give a decent idea whether or not it's doable to reproduce one of the addresses.
sr. member
Activity: 1190
Merit: 469
April 13, 2023, 10:21:29 PM
#43
And is it only me finding this suspicious?
maybe not suspicious but i find it strange why someone would need to generate 1 billion private keys if they are only going to use one of them. doesn't make any sense.

Quote
I wonder where is the address containing 1 btc? Because it has no out going tx, we can't find it's public key and steal the coin if that's what OP is afraid of. So where is the address in question?
good question.
member
Activity: 119
Merit: 36
April 13, 2023, 08:28:29 PM
#42
By "it worked" I meant that the script worked. It says I have to wait 1.7 million year before it actually finds the key.

Then your range must have been quite large or you have input it incorrectly.

This is one occasion where I would suggest you DO NOT publish your public keys. Instead, for those who keep asking "where is the btc" use this

https://iancoleman.io/bitcoin-key-compression/
(note there are malicious versions of this site so make sure you use the legit one)

Input the public key. it will produce two addresses compressed and uncompressed.
These you can safely publish and if there is any btc in them people can look up with this
https://www.blockchain.com/explorer

or similar.
copper member
Activity: 1330
Merit: 899
🖤😏
April 13, 2023, 05:52:37 PM
#41
And is it only me finding this suspicious? I wonder where is the address containing 1 btc? Because it has no out going tx, we can't find it's public key and steal the coin if that's what OP is afraid of. So where is the address in question?
member
Activity: 873
Merit: 22
$$P2P BTC BRUTE.JOIN NOW ! https://uclck.me/SQPJk
April 13, 2023, 04:20:19 PM
#40
still dont know what the author wants..

@Unplugged Taste
tell us, do you know the public key of the address containing 1 BTC or not ??

from your posts i believe you dont know which public key is the correct one....

i posted on the first page a script that converts all the public keys you have into addresses and compares them to the address containing your money.
it will return only the address and it's public key

IF you already know the public key of the address why would you need to check all the public keys at once??
I will write an example, we will take 125 original public key puzzles and generate 1 billion keys from them, then just crack one single public key out of billion public keys, you will get a private key in the form of numbers and according to it you can calculate the private key for 125


there is vinner of your 0.1 BTC ?
newbie
Activity: 19
Merit: 1
April 13, 2023, 04:20:05 PM
#39
Let's see if I understand


possibility #1


you generated 1000m of keys with intervals of 1m between each 1
1000095 to 1000000095

1000095
1000000095


in
hex

00000000000000000000000000000000000000000000000000000000000f429f
000000000000000000000000000000000000000000000000000000003b9aca5f



you put 1btc in any of them

you lost the private key

You know the address, the public key, and the range so finding it will only take minutes.



if the range is in hex
use

download repo
https://github.com/WanderingPhilosopher/KeyHuntCudaClient

open x64 folder

open console in folder

paste

with GPU

KeyHunt-Cuda.exe -t 0 -g --gpui 0 --gpux 256,256 -m xpoint --coin BTC --range "your range here. start:end" "your public here whitout first 2 ch"

example

KeyHunt-Cuda.exe -t 0 -g --gpui 0 --gpux 256,256 -m xpoint --coin BTC --range 8000000000:ffffffffff a2efa402fd5268400c77c20e574ba86409ededee7c4020e4b9f0edbee53de0d4

with CPU

KeyHunt-Cuda.exe -t "HERE CPU CORES TO USE"  --gpui 0 --gpux 256,256 -m xpoint --coin BTC --range "your range heree. start:end" "your public here whitout first 2"

example

KeyHunt-Cuda.exe -t 4  --gpui 0 --gpux 256,256 -m xpoint --coin BTC --range 8000000000:ffffffffff a2efa402fd5268400c77c20e574ba86409ededee7c4020e4b9f0edbee53de0d4

testet with my 4 cpu cores

1mkey/s = 1000mKeys in 1000 sec or 17 minutes.

If range is Decimal

example

1000000 to 20000000

in python

decimal to hex

Code:
start =1000000000
h = hex(start)[2: ]
print('hex :', h)

end =2000000000
h = hex(end)[2: ]
print('hex :', h)

use hex in keyhuntcuda

to generate the ranges of 1000000 in decimals you only add 1m x times

if you want to save all pubkey and privkey in ranges of every 1m

python modules

random
bitcoin

pip install bitcoin

for compressed addr

Code:
import bitcoin as bit
import random




#edit range_start


range_start= int(10000095)
N=int(1000000)
for N in range(1000000000):
    add= str(N) +'000000'
    result= int(add)
    sum= int(result + range_start)
    b = hex(sum)[2:]
    c = str.format(b)
    pk= c.zfill(64)
    public_key = bit.privkey_to_pubkey(pk)
    public_key_compressed = bit.compress(public_key)
    data = open("found.txt","a")
    data.write(str(public_key_compressed)+"\n"+ str(pk)+"\n")
    data.close()
           


for uncompressed addr
  
Code:
import bitcoin as bit
import random




#edit range_start

range_start= int(10000095)
N=int(1000000)
for N in range(1000000000):
    add= str(N) +'000000'
    result= int(add)
    sum= int(result + range_start)
    b = hex(sum)[2:]
    c = str.format(b)
    pk= c.zfill(64)
    public_key = bit.privkey_to_pubkey(pk)
    data = open("found.txt","a")
    data.write(str(public_key)+"\n"+ str(pk)+"\n")
    data.close()

if you know the public key and you want to save it

for compressed addr

Code:
import bitcoin as bit
import random


#edit range_start


range_start= int(10000095)
N=int(1000000)
for N in range(1000000000):
    add= str(N) +'000000'
    result= int(add)
    sum= int(result + range_start)
    b = hex(sum)[2:]
    c = str.format(b)
    pk= c.zfill(64)
    public_key = bit.privkey_to_pubkey(pk)
    public_key_compressed = bit.compress(public_key)
    target = "here your public key"
    if public_key_compressed in target:
        print("address found")
        data = open("found.txt","a")
        data.write(str(pk)+"\n"+ str(public_key_compressed)+"\n")
        data.close()

for uncompressed addr

Code:
import bitcoin as bit
import random




#edit range_start


range_start= int(10000095)
N=int(1000000)
for N in range(1000000000):
    add= str(N) +'000000'
    result= int(add)
    sum= int(result + range_start)
    b = hex(sum)[2:]
    c = str.format(b)
    pk= c.zfill(64)
    public_key = bit.privkey_to_pubkey(pk)
    target = "here your public key"
    if public_key in target:
        print("address found")
        data = open("found.txt","a")
        data.write(str(pk)+"\n"+ str(public_key)+"\n")
        data.close()


possibility #2

you take Hex(only numbers)

example

1000000 in decimal is 1000000

1000000 in hex is f4240


range 1000000- 1000000000 in hex is

0000000000000000000000000000000000000000000000000000000001000000
0000000000000000000000000000000000000000000000000000001000000000

this increase your search range


use python

if you want to save all public keys and private keys in ranges of every 1m

for compressed addr

Code:
import bitcoin as bit
import random




#edit range_start

range_start= int(10000095)
N=int(1000000)
for N in range(1000000000):
    add= str(N) +'000000'
    result= int(add)
    sum= str(result + range_start)
    pk= sum.zfill(64)
    public_key = bit.privkey_to_pubkey(pk)
    public_key_compressed = bit.compress(public_key)
    data = open("found.txt","a")
    data.write(str(public_key_compressed)+"\n"+ str(pk)+"\n")
    data.close()
           

for uncompressed addr

Code:
import bitcoin as bit
import random




#edit range_start

range_start= int(10000095)
N=int(1000000)
for N in range(1000000000):
    add= str(N) +'000000'
    result= int(add)
    sum= str(result + range_start)
    pk= sum.zfill(64)
    public_key = bit.privkey_to_pubkey(pk)
    data = open("found.txt","a")
    data.write(str(public_key)+"\n"+ str(pk)+"\n")
    data.close()




if you know the public key, and you want to save it

for compressed addr

Code:
import bitcoin as bit
import random




#edit range_start

range_start= int(10000095)
N=int(1000000)
for N in range(1000000000):
    add= str(N) +'000000'
    result= int(add)
    sum= str(result + range_start)
    pk= sum.zfill(64)
    public_key = bit.privkey_to_pubkey(pk)
    public_key_compressed = bit.compress(public_key)
    target = "here your public key"
    if public_key_compressed in target:
        print("address found")
        data = open("found.txt","a")
        data.write(str(pk)+"\n"+ str(public_key_compressed)+"\n")
        data.close()



for uncompressed addr

Code:
import bitcoin as bit
import random




#edit range_start

range_start= int(10000095)
N=int(1000000)
for N in range(1000000000):
    add= str(N) +'000000'
    result= int(add)
    sum= str(result + range_start)
    pk= sum.zfill(64)
    public_key = bit.privkey_to_pubkey(pk))
    target = "here your public key"
    if public_key in target:
        print("address found")
        data = open("found.txt","a")
        data.write(str(pk)+"\n"+ str(public_key)+"\n")
        data.close()

in case you are an honest person.

bc1qtfhwwgf5pmq99f5x8hwvvklepzxumdxgrmya8k

Pages:
Jump to: