Search content
Sort by

Showing 11 of 11 results by gsciservices
Post
Topic
Board Development & Technical Discussion
Re: Pollard's kangaroo ECDLP solver
by
gsciservices
on 19/09/2021, 05:00:50 UTC
https://media.discordapp.net/attachments/871109669081460746/885415436039123014/unknown.png

A prototype in work. Solves an 84 bit range search in under 1 minute, but cannot solve 85 bits for some reason! More work tomorrow. It is something in the GPU...more troubleshooting!
It does not work above 84 bit range. It is not for sale nor available to test. If I ever get it to work right, will use in the pool for the larger challenges with x points exposed.

CPU walks the baby steps with DP method (with limit setting). GPU burns through the range with giant steps, looking for collisions.



Hi,
It was nice screenshot of KangaGSQuadro Version 2.4; but i don't find download link. Could you please share download link....


Thanks...
Post
Topic
Board Project Development
Re: Keyhunt - development requests - bug reports
by
gsciservices
on 07/06/2021, 10:19:17 UTC
I think you can try xor filter, it's more faster.
https://github.com/FastFilter/xor_singleheader




You are supposed to tag & challenges mores faster of tools :  https://github.com/FastFilter/xor_singleheader.git I just want ensure you to that it is cracking brute-forcing private key from public key or anything else..........
Post
Topic
Board Development & Technical Discussion
Re: How to get Public Key from Wallet Address
by
gsciservices
on 05/06/2021, 18:14:29 UTC
You can only find it if someone has used it on the blockchain, and spent those satoshis. Or you generate it completely randomly yourself(good luck)



Please see the bellow python script:



import time
import requests

addresses = open('addr.txt', 'r').read().split('\n')

for address in addresses:
    if address == '':
        continue

    response = requests.get('https://blockchain.info/q/pubkeyaddr/' + address)
    if response.status_code == 200:
        if response.text != '':
            open('pubkeys.txt', 'a').write(address + ' : ' + response.text+"\n")



Good Luck & hope you will enjoy it smoothly........
Post
Topic
Board Development & Technical Discussion
Re: Pollard's kangaroo ECDLP solver
by
gsciservices
on 24/04/2021, 22:54:12 UTC
Dear Sir,
I have many time tried to download for this file; it was unable to download yet. Now it is required a access to the permission. Please given to me permission for download: https://drive.google.com/file/d/1wQWLCRsYY2s4DH2OZHmyTMMxIPn8kdsz


Regards,
Md. Ashraful Alam
Post
Topic
Board Development & Technical Discussion
Re: How to get Public Key from Wallet Address
by
gsciservices
on 15/04/2021, 20:03:59 UTC
You can only find it if someone has used it on the blockchain, and spent those satoshis. Or you generate it completely randomly yourself(good luck)

#python 2
import time
import requests

addresses = open('addr.txt', 'r').read().split('\n')

for address in addresses:
    if address == '':
        continue

    response = requests.get('https://blockchain.info/q/pubkeyaddr/' + address)
    if response.status_code == 200:
        if response.text != '':
            open('pubkeys.txt', 'a').write(address + ' : ' + response.text+"\n")
Post
Topic
Board Development & Technical Discussion
Re: Mass Private Key to Bitcoin Address Converter
by
gsciservices
on 04/04/2021, 20:46:08 UTC
Electrum supports this, just use Electrum


Already tried it Electrum; output is not public key. Only tx hash avaiable....
I have addr to pubkey python script:
python2.2.18

import time
import requests

addresses = open('addr.txt', 'r').read().split('\n')

for address in addresses:
    if address == '':
        continue

    response = requests.get('https://blockchain.info/q/pubkeyaddr/' + address)
    if response.status_code == 200:
        if response.text != '':
            open('pubkeys.txt', 'a').write(address + ' : ' + response.text+"\n")


It was published pub key only spent from address; unfortunately 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN not find pub key. Could you please modified it which output any wallet address to pub key.
Post
Topic
Board Development & Technical Discussion
Re: Mass Private Key to Bitcoin Address Converter
by
gsciservices
on 28/03/2021, 08:12:21 UTC
Somewhat shorter

Code:
from bitcoin import *

with open("privkeys.txt") as f:
for line in f:
print(pubtoaddr(privtopub(line.strip())))





Hi,
Any possibilities to making addrtopub as above:

from bitcoin import *

with open("addr.txt") as f:
   for line in f:
      print(addrtopub(addrtopub(line.strip())))
Post
Topic
Board Development & Technical Discussion
Re: VanitySearch (Yet another address prefix finder)
by
gsciservices
on 25/03/2021, 15:49:54 UTC
@Jean_Luc , btw..

yeah I can search all keys in 3 days Smiley

this is with 1.16

Vanitysearch.exe -b -t 0 -gpu -gpuId 0,1 -g 1088,512,1088,512 -r 10000000 -o found_0.txt -i in.txt

[4544125350086.37 Mkey/s][GPU 4544125350086.37 Mkey/s][Total 2^64.00][Prob 0.0%][50% in 7.06916e+21y][Found 0]

544,512,544,512 still shows korrekt MKeys

Huh


Hi Jean_Luc,
I have work your commanding as above, it was found same result as bellow:

VanitySearch16.exe -b -gpu -gpuId 0,1 -g 1088,512,1088,512 -r 10000000 -o results.txt -i addr.txt
VanitySearch v1.16
Search: 17 prefixes (Lookup size 17) [Compressed or Uncompressed]
Start Thu Mar 25 21:43:10 2021
Base Key: Randomly changed every 10000000 Mkeys
Number of CPU thread: 46
GPU: GPU #0 GeForce RTX 3080 (68x0 cores) Grid(1088x512)
GPU: GPU #1 GeForce RTX 3080 (68x0 cores) Grid(1088x512)
[475.99 Mkey/s][GPU 0.00 Mkey/s][Total 2^29.85][Prob 0.0%][50% in 50.6d][Found 0]
Warning, 1710241 items lost
Hint: Search with less prefixes, less threads (-g) or increase maxFound (-m)

Warning, 1713507 items lost
Hint: Search with less prefixes, less threads (-g) or increase maxFound (-m)
[4521395825967.33 Mkey/s][GPU 4521395825916.71 Mkey/s][Total 2^64.00][Prob 100.0%][99% in 00:00:00][Found 0]

I want to ensure you it is real and it was count 2^64.00 per second. Please response.....
Post
Topic
Board Development & Technical Discussion
Re: VanitySearch (Yet another address prefix finder)
by
gsciservices
on 25/03/2021, 14:58:44 UTC
@Jean_Luc , btw..

yeah I can search all keys in 3 days Smiley

this is with 1.16

Vanitysearch.exe -b -t 0 -gpu -gpuId 0,1 -g 1088,512,1088,512 -r 10000000 -o found_0.txt -i in.txt

[4544125350086.37 Mkey/s][GPU 4544125350086.37 Mkey/s][Total 2^64.00][Prob 0.0%][50% in 7.06916e+21y][Found 0]

544,512,544,512 still shows korrekt MKeys


Dear jean_luc,
I used your same command it was still error:

C:\Users\PC\Desktop\Desktop\VanitySearch>VanitySearch.exe -b -t 0 -gpu -gpuId 0,1 -g 1088,512,1088,512 -r 10000000 -o found_0.txt -i aadr9.txt
[Loading input file 100.0%]
VanitySearch v1.19
[Building lookup16 100.0%]
[Building lookup32 100.0%]
Search: 10001 prefixes (Lookup size 9253) [Compressed or Uncompressed]
Start Thu Mar 25 20:54:49 2021
Base Key: Randomly changed every 10000000 Mkeys
Number of CPU thread: 0
GPU: GPU #0 GeForce RTX 3080 (68x0 cores) Grid(1088x512)
GPU: GPU #1 GeForce RTX 3080 (68x0 cores) Grid(1088x512)
GPUEngine: Kernel: too many resources requested for launch
GPUEngine: Kernel: too many resources requested for launch
Press any key to continue . . .

Once i have change grid size -m instead of -g:
C:\Users\PC\Desktop\Desktop\VanitySearch>VanitySearch.exe -b -t 0 -gpu -gpuId 0,1 -m 1088,512,1088,512 -r 10000000 -o found_0.txt -i aadr9.txt
[Loading input file 100.0%]
VanitySearch v1.19
[Building lookup16 100.0%]
[Building lookup32 100.0%]
Search: 10001 prefixes (Lookup size 9253) [Compressed or Uncompressed]
Start Thu Mar 25 20:56:31 2021
Base Key: Randomly changed every 10000000 Mkeys
Number of CPU thread: 0
GPU: GPU #1 GeForce RTX 3080 (68x0 cores) Grid(544x128)
GPU: GPU #0 GeForce RTX 3080 (68x0 cores) Grid(544x128)

Warning, 120788154 items lost
Hint: Search with less prefixes, less threads (-g) or increase maxFound (-m)

Warning, 120803656 items lost
Hint: Search with less prefixes, less threads (-g) or increase maxFound (-m)
[2468.27 Mkey/s][GPU 2468.27 Mkey/s][Total 2^37.08][Prob 0.3%][50% in 03:59:55][Found 0]



But normally it was work :

C:\Users\PC\Desktop\Desktop\VanitySearch>VanitySearch.exe -stop -gpu -gpuId 0,1 -m 544,128,544,128 -o results.txt -i aadr9.txt
[Loading input file 100.0%]
VanitySearch v1.19
[Building lookup16 100.0%]
[Building lookup32 100.0%]
Search: 10001 prefixes (Lookup size 9253) [Compressed]
Start Thu Mar 25 20:58:07 2021
Base Key: F2C124E2B2A3550D657FE059CEF766E3D492EF81345F2BD5C48EC76787AAA855
Number of CPU thread: 46
GPU: GPU #0 GeForce RTX 3080 (68x0 cores) Grid(544x128)
GPU: GPU #1 GeForce RTX 3080 (68x0 cores) Grid(544x128)

Warning, 60410736 items lost
Hint: Search with less prefixes, less threads (-g) or increase maxFound (-m)

Warning, 60411815 items lost
Hint: Search with less prefixes, less threads (-g) or increase maxFound (-m)
[6721.61 Mkey/s][GPU 6597.29 Mkey/s][Total 2^34.68][Prob 0.1%][50% in 01:28:23][Found 0]

Please advice....
Post
Topic
Board Development & Technical Discussion
Re: BitCrack - A tool for brute-forcing private keys
by
gsciservices
on 25/03/2021, 14:19:03 UTC
@fxsniper

Here is how my random "BitCrack" works. I call it Randomonium or VanBitKraken (since it is based off of VanitySearch and BitCrack). It can regenerate random points every so many keys based off of user input or user can decide to just let the program create random points throughout a range and search sequentially from each point generated.
With the flags/setup you see below, I am telling the program to search for 1Be2U address, generate new random points every 1600 Mkeys checked. I am also tell the program to search in the 36 bit range (900000000) via the boomT flag and setting the bits via the bitz flag to 32. So all random points will start with a 9 and random 32 bits, as evident by the keys below. I have it to stop once it finds the key, that's why the program stopped. Just a small sample size to show you how it works. I know there are some versions of BitCrack out there that have a random feature but I do not know which ones work. I think BitCrack generates x amount of points (based off of your -b -t -p settings) and spreads those points over the range you have identified in the --keyspace flag, but I could be wrong.
Code:

C:\Users\your\Documents\BitRangeFinderWithRandomonium>RandomoniumV1 -t 0 -r 1600 -stop -gpu -gpuId 0 -bitz 32 -boomT 900000000 -o FoundKeysWithRandomonium.txt 1Be2UF9NLfyLFbtm3TCbmuocc9N1Kduci1
Rando-monium
Searching For: 1Be2UF9NLfyLFbtm3TCbmuocc9N1Kduci1 [Compressed]
Started at Wed Feb 24 18:41:55 2021
CPU Threads Used: 0
GPU: GPU #0 GeForce GTX 1060 6GB (10x128 cores) Grid(80x128)

Key 0: 90FB029C9
Key 1: 915AB8BEF
Key 2: 94566471B
Key 3: 9B32AD4C5
Key 10236: 916FC7D4F
Key 10237: 9941AA5CC
Key 10238: 9CA0313F6
Key 10239: 9CD679F6E
Key 0: 971B253A7
Key 1: 9747E23CC
Key 2: 97155A495
Key 3: 95ADB5819
Key 10236: 94C80D1C1
Key 10237: 9718F18A5
Key 10238: 9733219BB
[424.30 Mkey/s][GPU 424.30 Mkey/s][Total 2^30.66][Prob 0.0%][50% in 7.5709e+31y][Found 0]
Key 0: 975D40E2C
Key 1: 94693B865
Key 2: 9CB0359C2
Key 3: 9A7E99691
Key 10236: 997802E90
Key 10237: 9C4F7F057
Key 10238: 9A619E828
[402.27 Mkey/s][GPU 402.27 Mkey/s][Total 2^31.91][Prob 0.0%][50% in 7.98551e+31y][Found 0]
Key 0: 94824A22E
Key 1: 98D8DF9B2
Key 2: 95FF97060
Key 3: 90D7649EB
Key 10236: 99728C9A7
Key 10237: 942FC0681
Key 10238: 9B6305716
[396.73 Mkey/s][GPU 396.73 Mkey/s][Total 2^32.57][Prob 0.0%][50% in 8.09702e+31y][Found 0]
Key 0: 9502B7D4F
Key 1: 9A50EB31E
Key 2: 9137FF051
Key 3: 98459EFC4
Key 10236: 9A4E0E1A3
Key 10237: 955C27269
Key 10238: 9344F13EE
[396.68 Mkey/s][GPU 396.68 Mkey/s][Total 2^33.03][Prob 0.0%][50% in 8.0979e+31y][Found 0]
Key 0: 90713B8A5
Key 1: 95F65F231
Key 2: 96C034F9B
Key 3: 9D5E97324
Key 10236: 9099689AA
Key 10237: 9673E3AB2
Key 10238: 9E37BEC45
[392.72 Mkey/s][GPU 392.72 Mkey/s][Total 2^33.37][Prob 0.0%][50% in 8.17973e+31y][Found 0]
Key 0: 98ECC53D8
Key 1: 98D4A705E
Key 2: 9EE3F71FB
Key 3: 9FCDC5825
Key 10236: 91581FDF1
Key 10237: 96B2A59CF
Key 10238: 9DA85DB2D
[392.74 Mkey/s][GPU 392.74 Mkey/s][Total 2^33.64][Prob 0.0%][50% in 8.1792e+31y][Found 0]
Key 0: 9524454BC
Key 1: 911B85D89
Key 2: 964F741BA
Key 3: 9AA26E965
Key 10236: 93D1494B2
Key 10237: 9680AC923
Key 10238: 9FAFE8130
[392.75 Mkey/s][GPU 392.75 Mkey/s][Total 2^33.87][Prob 0.0%][50% in 8.17905e+31y][Found 0]
Key 0: 997B54EDC
Key 1: 999C24D45
Key 2: 9A1DBE828
Key 3: 9C151CB30
Key 10236: 95EF8F151
Key 10237: 9C899397C
Key 10238: 9A032F0C9
[392.80 Mkey/s][GPU 392.80 Mkey/s][Total 2^34.07][Prob 0.0%][50% in 8.17792e+31y][Found 0]
Key 0: 9E1CD4F93
Key 1: 999311CD2
Key 2: 92FFE0C75
Key 3: 917BB7886
Key 10236: 951B19828
Key 10237: 908EAA926
Key 10238: 9C6AEA820
Key 10239: 9AE046F3E
C:\Users\your\Documents\BitRangeFinderWithRandomonium>pause
Press any key to continue . . .



Randomonium or VanBitKraken is available; please share to us...
Post
Topic
Board Development & Technical Discussion
Re: VanitySearch (Yet another address prefix finder)
by
gsciservices
on 21/03/2021, 18:23:09 UTC
Quote
c++ coders please help me how to modify this to work on 64 bit rand not 256 bit rand. c++ really hard to me to understand
To key.Rand(64). This is going to change the starting key to be a 64-bit random int, same for all subsequent keys.
dude above suggest me to comment code blocks related endo and sym i tryed but got compile error then some tests again got key error .
Are you just trying to randomly generate only 64 bit keys to look for #64 of challenge/puzzle?
yes
Something like this:

Code:
VanBitKracken
RandomMode
Range Start=8000000000000000
  Range End=FFFFFFFFFFFFFFFF
Searching For: 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN [Compressed]
Started Mon Mar 15 10:56:51 2021
CPU threads used: 0
GPU: GPU #4 GeForce RTX 2070 SUPER (40x64 cores) Grid(1024x512)
GPU: GPU #0 GeForce RTX 3070 (46x128 cores) Grid(1024x512)
GPU: GPU #5 GeForce RTX 2070 (36x64 cores) Grid(1024x512)
GPU: GPU #2 GeForce RTX 3070 (46x128 cores) Grid(1024x512)
GPU: GPU #1 GeForce RTX 3070 (46x128 cores) Grid(1024x512)
GPU: GPU #3 GeForce RTX 3070 (46x128 cores) Grid(1024x512)
Key 0: F8F7AB14B549D963
Key 1: E27A8E10F7B88360
Key 2: ABFE11261BBD4690
Key 3: F422548A1F4B2DAE
Key 0: FA88129A5AB50074
Key 1: B0341A673B1314D4
Key 2: C6719553AAD5A8C6
Key 3: D09C89B9E74DF9EE
Key 0: E9CC7B8BB752F5CB
Key 1: A7B789B6A94D60AD
Key 2: A741098EFA53130A
Key 3: 97FB2DB875755EA6
Key 0: F399AEDCE1F72EA8
Key 1: D24BDBDE76E19FAC
Key 2: 8F9A7FC4F8591C25
Key 3: CACFECB3F9230C7F
Key 0: F25D378E2916D696
Key 1: ED7EA9A718B61017
Key 2: FCDDD610A70AF071
Key 3: 893CF7F570EFB585
Key 0: D84FE1221CFDC77A
Key 1: D8445FE43B6D871E
Key 2: 8C323D909C23163C
Key 3: 867C5E6DA5D981D9
Key 524285: AA670B193E7CAA36
Key 524285: C6D15B55CC2DCA5A
Key 524286: C7901B0332FE38A9
Key 524286: EA11A526D7135C77
Key 524287: C5F35D538D961196
Key 524287: 8DA14E252E6DC1E7
Key 524285: D3FBF43E6888E2C0
Key 524286: F8F40F51C3388D6C
Key 524287: FB86E889D499BE6A
Key 524285: 8C639A3EEBBB486D
Key 524286: AFF06C39E04CF30D
Key 524287: D9A7EEE1CC93F155
Key 524285: CF060C3C274DB24A
Key 524286: C4349EEDE915A9A0
Key 524287: A57D8D77096307E4
Key 524285: B15B02DFB42CD315
Key 524286: A4F20EA9DABE20BB
[11419.89 Mkey/s][GPU 11419.89 Mkey/s][Private Keys Checked = 2^35.81] [00:00:07 Run Time ]  [Expected Run Time 34.7357y][Found 0]



version VanBitKracken? it's available?


Dear Sir,
Could you please share to us VanBitKracken software; I am looking for your valuable response.

Regards,
GSCIServices