Just a lazy solution: import java.math.BigInteger;
public class K { public static void main(String[] args) { BigInteger start = new BigInteger("0552e025571c01bcd9eda59365a2fb3ae0bd7547dfeeeb13d971d848bcbf0467", 16); BigInteger stride = BigInteger.valueOf(58L).pow(32);//depends on the position of most-right unknown character BigInteger range = BigInteger.valueOf(58L).pow(5);//5=number of unknown characters BigInteger end = start.add(range); System.out.println("START: "+start.toString(16)); System.out.println("END: "+end.toString(16)); System.out.println("STRIDE: "+stride.toString(16)); } } Going back to this version of Kangaroo: I think there is still something wrong with calculations with checksum - for longer ranges (>6 unknown characters) it does not return result, while when there is case without checksum (just a stride) it works good. how do i run this java. i have a question, does this work with missing chars at the end of the wif, really want to know, stuck on reading here past 2 days.
|
|
|
thanks for the fast response, and yes that was a bit with the "puzzle" thing in mind, like the range 8000000-fffffff or like with the numbers 1-160? great thanks noticing all the changes you applying to you'r newer versions. i noticed that with some lets say 17 characters amount of total keys to check as with 16 characters missing, stayed the same.
but anyway a 110% release. and good luck so far.
|
|
|
thanks a lot for another greater release. i have a question, could you make it search in a specific bit range=x thanks a lot.
|
|
|
may I try your modified VanitySearch with keyspace search?
I would honestly not recommend using non-stable software. If I get it to work properly and understand the part going wrong, I'm happy to share. But at this moment, it needs front-running code to restart it. I would be feeling guilty and spending time helping people out, instead of fixing the real problem. I was hoping to trigger someone on the code part going wrong, rather then making people run unstable heb tijd and uit amsterdam, pm maar door, would be able to do some testing in spare time,
|
|
|
Hoi, because this is about btc, i have a wallet.dat, thought this private key came out of this mywallet.pfx from op, strangly bc_key works with the wallet.dat ** Usage: ./bc_key BITCOIN_ADDRESS /path/to/wallet.dat ./bc_key ALL /path/to/wallet.dat ./bc_key EVERYTHING /path/to/wallet.dat and op got his things out the pfx. as you said to have used it on an address from a wallet? But when I ran bc_key with an address in some wallet file, I got this output: -----BEGIN EC PARAMETERS----- short ASCII string for me here was btc address, but the thing is bc_key does work only with one wallet.dat i have unencrypted, that gives me the pem encrypted key back. -----END EC PARAMETERS----- -----BEGIN EC PRIVATE KEY----- really long string of ASCII text that looks like one in OP same here the encrypted key -----END EC PRIVATE KEY----- this make me think that this is a way around the loading the wallet inside the btc core client and then doing dumpwallet one by one, as op did one. this above does all that in a jiffy with all addresses from bc_key back to pem and from there back to your keys. so every wallet is its own pem file. the only pitty is that i dont know about is how to have a pem file with all the pem encrypted keys to get trough bc_key at one go. seems it does not accept all those line at once without editing the result of bc_key, first of all the address is in the way, then one pem key it works and stops.
|
|
|
Hi thanks for the help HCP, this wallet was is not encrypted that is why i asked, i know how to import it, so that was not an issue, the OP posted a pfx. wallet format. how to get a hold of that with btc.
|
|
|
From the old topic it's a PUBLIC key not a PRIVATE key. Why did you change it?
I don't want to post my private Key online so anyone can take my BTC. You are able to use a sample private key created from bitaddress.org if all you want to do is convert it from PEM and back again. https://www.bitaddress.org/bitaddress.org-v3.3.0-SHA256-dec17c07685e1870960903d8f58090475b25af946fe95a734f88408cef4aa194.html
PEM is an RSA private key file format. So you are trying to convert an RSA private key bytes to bitcoin private key bytes but this doesn't make sense at first because bitcoin private keys use elliptic curve cryptography, not RSA. But when I ran bc_key with an address in some wallet file, I got this output: -----BEGIN EC PARAMETERS----- short ASCII string -----END EC PARAMETERS----- -----BEGIN EC PRIVATE KEY----- really long string of ASCII text that looks like one in OP -----END EC PRIVATE KEY----- So what you did is convert the output of bc_key, an ECC private key, into an RSA public key. We should probably figure out how to get the private key bytes out of this ECC key first as it's most likely a valid bitcoin private key. i get this error with bc_key, you might know why, read EC key unable to load Key 140245723776704:error:0906D06C:PEM routines:PEM_read_bio:no start line:pem_lib.c:707:Expecting: ANY PRIVATE KEY and this with ssl openssl pkcs12 -in mywallet.dat -nocerts -out privatekey.pem -nodes 140391597541056:error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag:tasn_dec.c:1200: 140391597541056:error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error:tasn_dec.c:374:Type=PKCS12
|
|
|
From the old topic it's a PUBLIC key not a PRIVATE key. Why did you change it?
I don't want to post my private Key online so anyone can take my BTC. You are able to use a sample private key created from bitaddress.org if all you want to do is convert it from PEM and back again. https://www.bitaddress.org/bitaddress.org-v3.3.0-SHA256-dec17c07685e1870960903d8f58090475b25af946fe95a734f88408cef4aa194.html
PEM is an RSA private key file format. So you are trying to convert an RSA private key bytes to bitcoin private key bytes but this doesn't make sense at first because bitcoin private keys use elliptic curve cryptography, not RSA. But when I ran bc_key with an address in some wallet file, I got this output: -----BEGIN EC PARAMETERS----- short ASCII string -----END EC PARAMETERS----- -----BEGIN EC PRIVATE KEY----- really long string of ASCII text that looks like one in OP -----END EC PRIVATE KEY----- So what you did is convert the output of bc_key, an ECC private key, into an RSA public key. We should probably figure out how to get the private key bytes out of this ECC key first as it's most likely a valid bitcoin private key. hi there arkadas, do you know if you can get to enter the password with bc_key for the wallet.dat file. thanks
|
|
|
From the old topic it's a PUBLIC key not a PRIVATE key. Why did you change it?
I don't want to post my private Key online so anyone can take my BTC. Thx for this code with Python HCP. This was what I need. This gives an cool formated output to see everthing bedder: openssl asn1parse -in privatekey.pem Hex-dump is the Private Key I found a Code from https://gist.github.com/Jun-Wang-2018/3105e29e0d61ecf88530c092199371a7#file-bitcoin_from_private_key_to_wif-py to convert HEX to WIF: # From private key(hex) to Wallet Import Format(WIF) # Reference: https://medium.freecodecamp.org/how-to-create-a-bitcoin-wallet-address-from-a-private-key-eca3ddd9c05f # https://docs.python.org/2/library/hashlib.html import codecs #If not installed: "pip3 install codecs" import hashlib # PK0 is a demo private key. PK0 = "3cd0560f5b27591916c643a0b7aa69d03839380a738d2e912990dcc573715d2c" PK1 = '80'+ PK0 PK2 = hashlib.sha256(codecs.decode(PK1, 'hex')) PK3 = hashlib.sha256(PK2.digest()) checksum = codecs.encode(PK3.digest(), 'hex')[0:8] PK4 = PK1 + str(checksum)[2:10] #I know it looks wierd
# Define base58 def base58(address_hex): alphabet = '123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz' b58_string = '' # Get the number of leading zeros leading_zeros = len(address_hex) - len(address_hex.lstrip('0')) # Convert hex to decimal address_int = int(address_hex, 16) # Append digits to the start of string while address_int > 0: digit = address_int % 58 digit_char = alphabet[digit] b58_string = digit_char + b58_string address_int //= 58 # Add ‘1’ for each 2 leading zeros ones = leading_zeros // 2 for one in range(ones): b58_string = '1' + b58_string return b58_string
WIF = base58(PK4) print(WIF)
quoted all dang, here's the link: https://github.com/matja/bitcoin-toolto say that matja btc tool does the same true one command and batch format like several keys at once. gl.
|
|
|
clbitcrack has always had issues, still does, and did you change the compute_cap in your makefile, otherwise compiling the cubitcrack won't succeed. even if succeeded won't work with your hardware. change it accordingly to your hardware.
I didn't change the compute_cap value and was still able to compile cubitcrack on windows simply by updating the references to CUDA 10.1 to 11.2 and making sure project resources were in the correct locations. I'm not able to actually run it because of the "misaligned address" error, so I am using clbitcrack instead until someone is able to fix cubitcrack and allow it to run again with CUDA 11.2+. In the meantime, what issues should I expect clbitcrack to have running on Windows? I'm not working with any P2SH addresses. What other issues would cause clbitcrack to not find a private key, as @yoyodapro mentioned? https://github.com/brichard19/BitCrack/issues/81this was the main reason i said that, besides you can test it out easily if it works o.o.t.b.
|
|
|
with passworded files, it will Segmentation fault (core dumped), with non password files, just do nothing at all, you have to pipe it out. only addresses in there, no keys as said, btc wallet version before hall brought this thing out, will give keys. this one only lines like this.
pool 00000065 2020/03/12 1GWeaBZYsZ5XvovhuagCKCFHaPoDKkrWix
any one got that version lying around as .exe thanks ahead.
thanks a lot for that ssl issue fix thing was already on it few hours before you posted. thanks
|
|
|
clbitcrack has always had issues, still does, and did you change the compute_cap in your makefile, otherwise compiling the cubitcrack won't succeed. even if succeeded won't work with your hardware. change it accordingly to your hardware.
|
|
|
yes that is an edited vanitsearch used there, used with wildcards. * stronger cards and more means more chances, or to say lesser wildcards. good luck there,
Noname, COMPUTE_CAP=35 this in the makefile instead of COMPUTE_CAP=30 makes it work for me same with your files as with yoyodapro's files, thanks for the help there mate ,
|
|
|
Thanks for the help a ton, and only changed the c_c to 35 in my case. made the solution file work as a charm, otherwise no issues yet. is there a verbose mode on this bitcrack as of no others have that, like show where it is now instead of continue file. changed to 1024 now. thanks guys
|
|
|
i am using a 1070, 128 1000 256
|
|
|
cubitcrack does - the provided PTX was compiled with an unsupported toolchain
clbitcrack works fine,
|
|
|
is this a possible new exchange to list xcn 2? https://bitcointalk.org/index.php?topic=5121953.0;all[EXCHANGE] ShorelineCrypto - ZERO Withdraw fee, Listing Fee 0.005-0.01 BTC We also offer 50% discount for new coin listing under ShorelineCrypto Coin listing Service Discount Program if the payment is made on Nengcoin (NENG)
|
|
|
hi there i had some to there in 1 or so in full. big vernon v get out ya hole help out biash
|
|
|
DP: 626,941,151 TP: 14,389,459,189,655,514
how much percentage of 120th puzzle should these dp and tp have reached, anyone? thanks
|
|
|
Hello! Dextronomous. Thanks for the answer. BSGS has multiple bat files. Run each one sequentially.? Or parallel to the core?
yes identical if you have 4 you can use 3 bat files if you are not on that pc working, or 15 if you have 16cores. if you think it is in one of the other ranges the bat files wich start with different starting points you want you choose. good luck
|
|
|
|