Currently there is no known implementation of kangaroo algorithm which handles multiple pubkeys. JLPs implementation processes each pubkey consecutively.
BSGS is possible to handle each pubkey simultaneously.
Which one is faster? Depends.
Topic: BSGS solver for cuda - page 8. (Read 3827 times)
help me to understand which one is faster when you are searching multiple keys from file
BSGS or Kangaroo?
i heard that if you load list of PB keys in kangaroo it is not checking all simultaneously, is it true?
if over 80 bit kangaroo is more efficient and fast than bsgs please explain why?
BSGS or Kangaroo?
i heard that if you load list of PB keys in kangaroo it is not checking all simultaneously, is it true?
if over 80 bit kangaroo is more efficient and fast than bsgs please explain why?
Is there any script to uncompress multiple pubkeys in a file?
like this script: BTC Adresses > HASH160
https://github.com/sezginyildirim91/btc-address-to-hash160
here i see post related to compress to uncompress and uncompress to compress (codes)like this script: BTC Adresses > HASH160
https://github.com/sezginyildirim91/btc-address-to-hash160
https://bitcointalksearch.org/topic/m.57700007
Use bitcoin-tool.
https://github.com/matja/bitcoin-tool
https://github.com/matja/bitcoin-tool
Is there any script to uncompress multiple pubkeys in a file?
like this script: BTC Adresses > HASH160
https://github.com/sezginyildirim91/btc-address-to-hash160
here i see post related to compress to uncompress and uncompress to compress (codes)like this script: BTC Adresses > HASH160
https://github.com/sezginyildirim91/btc-address-to-hash160
https://bitcointalksearch.org/topic/m.57700007
Total: 4294967296 bytes
Save BIN file:79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798_536870912_b.BI N
Press Enter to exit
new error
Download 1.3.2 version. decreased chunk size to 1GbSave BIN file:79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798_536870912_b.BI N
- chunk:2147483648b
Press Enter to exit
new errorlet me try
Total: 4294967296 bytes
Save BIN file:79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798_536870912_b.BI N
Press Enter to exit
new error
Download 1.3.2 version. decreased chunk size to 1Gb Save BIN file:79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798_536870912_b.BI N
- chunk:2147483648b
Press Enter to exit
new error
Total: 4294967296 bytes
Save BIN file:79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798_536870912_b.BI N
Press Enter to exit
new error
Save BIN file:79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798_536870912_b.BI N
- chunk:2147483648b
Press Enter to exit
new error --snip--
i am beginner so must be doing some wrong but what program you will recommend for above 80-bit range
JLP Kangaroo. https://github.com/JeanLucPons/Kangaroo i am beginner so must be doing some wrong but what program you will recommend for above 80-bit range
Is there any script to uncompress multiple pubkeys in a file?
like this script: BTC Adresses > HASH160
https://github.com/sezginyildirim91/btc-address-to-hash160
like this script: BTC Adresses > HASH160
https://github.com/sezginyildirim91/btc-address-to-hash160
i am sorry bro its still same and still showing 4095 memory and cannot utilize above 3200+
Make sure you run v1.3.1. you can check version in the begining.yes bro this is v1.3.1 nut still same incorrect detection
By the way bsgs fast only in small ranges like 2^64 and less. if you will try use bsgs for #80 puzzle for ex. then you will search pubkeys much longer then JLP kangaroo.
i am beginner so must be doing some wrong but what program you will recommend for above 80-bit range
i am sorry bro its still same and still showing 4095 memory and cannot utilize above 3200+
Make sure you run v1.3.1. you can check version in the begining.yes bro this is v1.3.1 nut still same incorrect detection
By the way bsgs fast only in small ranges like 2^64 and less. if you will try use bsgs for #80 puzzle for ex. then you will search pubkeys much longer then JLP kangaroo.
i am sorry bro its still same and still showing 4095 memory and cannot utilize above 3200+
Make sure you run v1.3.1. you can check version in the begining.yes bro this is v1.3.1 nut still same incorrect detection
i fixed it as i did not delete old files which were computed before by old program , when i deleted all old .bin etc file and now everything is fine thanks man will start testing now
i am sorry bro its still same and still showing 4095 memory and cannot utilize above 3200+
Make sure you run v1.3.1. you can check version in the begining.yes bro this is v1.3.1 nut still same incorrect detection
i am sorry bro its still same and still showing 4095 memory and cannot utilize above 3200+
Make sure you run v1.3.1. you can check version in the begining.Does it search whole 256bit space? Or limited only to few lsb bits?
i am sorry bro its still same and still showing 4095 memory and cannot utilize above 3200+
Make sure you run v1.3.1. you can check version in the begining. Do i have to remove 04 from bigging of uncompressed key or software can recognize with 04 also?
and seems like one more issue is there
if i am using range like this
49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5eba34000000000000
its running fine in range but when i use 120 range it is calculating range fine but running very below and showing false collision
this started like this
GPU#0 Cnt:0000000000000000000000000000000000000000000000000000000000000001
.....
GPU#0 Cnt:0000000000000000000000000000000000000000000000160cc3800000000001
but i set range 0x800000000000000000000000000000 to 0xffffffffffffffffffffffffffffff
is something wrong with software ?
You can run with 04 in front of uncompressed key's x,y points; you just can not use a compressed key in any format.and seems like one more issue is there
if i am using range like this
49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5eba34000000000000
its running fine in range but when i use 120 range it is calculating range fine but running very below and showing false collision
this started like this
GPU#0 Cnt:0000000000000000000000000000000000000000000000000000000000000001
.....
GPU#0 Cnt:0000000000000000000000000000000000000000000000160cc3800000000001
but i set range 0x800000000000000000000000000000 to 0xffffffffffffffffffffffffffffff
is something wrong with software ?
The Cnt's are the giant steps. Program offsets (subtracts start range) pubkey on startup and then after all the baby steps and sorting, the GPU starts the giant steps. Nothing is wrong with the program. If you run a smaller range, you will see the same thing and you will see it will solve for the inputted key. False collisions are normal due to 8 bytes stored in hash table.
awesome man got the point i was worried that something wrong with my setup
Do i have to remove 04 from bigging of uncompressed key or software can recognize with 04 also?
and seems like one more issue is there
if i am using range like this
49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5eba34000000000000
its running fine in range but when i use 120 range it is calculating range fine but running very below and showing false collision
this started like this
GPU#0 Cnt:0000000000000000000000000000000000000000000000000000000000000001
.....
GPU#0 Cnt:0000000000000000000000000000000000000000000000160cc3800000000001
but i set range 0x800000000000000000000000000000 to 0xffffffffffffffffffffffffffffff
is something wrong with software ?
You can run with 04 in front of uncompressed key's x,y points; you just can not use a compressed key in any format.and seems like one more issue is there
if i am using range like this
49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5eba34000000000000
its running fine in range but when i use 120 range it is calculating range fine but running very below and showing false collision
this started like this
GPU#0 Cnt:0000000000000000000000000000000000000000000000000000000000000001
.....
GPU#0 Cnt:0000000000000000000000000000000000000000000000160cc3800000000001
but i set range 0x800000000000000000000000000000 to 0xffffffffffffffffffffffffffffff
is something wrong with software ?
The Cnt's are the giant steps. Program offsets (subtracts start range) pubkey on startup and then after all the baby steps and sorting, the GPU starts the giant steps. Nothing is wrong with the program. If you run a smaller range, you will see the same thing and you will see it will solve for the inputted key. False collisions are normal due to 8 bytes stored in hash table.
Do i have to remove 04 from bigging of uncompressed key or software can recognize with 04 also?
and seems like one more issue is there
if i am using range like this
49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5eba34000000000000
its running fine in range but when i use 120 range it is calculating range fine but running very below and showing false collision
this started like this
GPU#0 Cnt:0000000000000000000000000000000000000000000000000000000000000001
.....
GPU#0 Cnt:0000000000000000000000000000000000000000000000160cc3800000000001
but i set range 0x800000000000000000000000000000 to 0xffffffffffffffffffffffffffffff
is something wrong with software ?
and seems like one more issue is there
if i am using range like this
49dccfd96dc5df56487436f5a1b18c4f5d34f65ddb48cb5eba34000000000000
its running fine in range but when i use 120 range it is calculating range fine but running very below and showing false collision
this started like this
GPU#0 Cnt:0000000000000000000000000000000000000000000000000000000000000001
.....
GPU#0 Cnt:0000000000000000000000000000000000000000000000160cc3800000000001
but i set range 0x800000000000000000000000000000 to 0xffffffffffffffffffffffffffffff
is something wrong with software ?
Seems like i fix app.. 
Replace most commands with unofficial _v2
Also speed is little increased.
Replace most commands with unofficial _v2Code:
GPU #0 launched
GPU #0 TotalBuff: 5168.000Mb
GPU#0 Cnt:0000000000000000000000000000000000000000000000000000000000000001
GPU#0 Cnt:00000000000000000000000000000000000000000000000015ea000000000001 697MKey/s x536870912 2^29.45 x2^30=2^59.45
GPU#0 Cnt:0000000000000000000000000000000000000000000000002bd4000000000001 697MKey/s x536870912 2^29.45 x2^30=2^59.45
GPU#0 Cnt:00000000000000000000000000000000000000000000000041be000000000001 697MKey/s x536870912 2^29.45 x2^30=2^59.45
GPU#0 Cnt:00000000000000000000000000000000000000000000000057a8000000000001 697MKey/s x536870912 2^29.45 x2^30=2^59.45
GPU#0 Cnt:0000000000000000000000000000000000000000000000006d92000000000001 697MKey/s x536870912 2^29.45 x2^30=2^59.45
GPU#0 Cnt:000000000000000000000000000000000000000000000000835a000000000001 696MKey/s x536870912 2^29.44 x2^30=2^59.44
GPU#0 Cnt:0000000000000000000000000000000000000000000000009922000000000001 696MKey/s x536870912 2^29.44 x2^30=2^59.44
***********GPU#0************
Total solutions: 1
KEY!!>000000000000000000000000000000000000000000000001a838b13505b26867
Pub: 30210c23b1a047bc9bdbb13448e67deddc108946de6de639bcc75d47c0216b1be383c4a8ed4fac77c0d2ad737d8499a362f483f8fe39d1e86aaed578a9455dfc
****************************
Found in 17 seconds
Result above with -w 29GPU #0 TotalBuff: 5168.000Mb
GPU#0 Cnt:0000000000000000000000000000000000000000000000000000000000000001
GPU#0 Cnt:00000000000000000000000000000000000000000000000015ea000000000001 697MKey/s x536870912 2^29.45 x2^30=2^59.45
GPU#0 Cnt:0000000000000000000000000000000000000000000000002bd4000000000001 697MKey/s x536870912 2^29.45 x2^30=2^59.45
GPU#0 Cnt:00000000000000000000000000000000000000000000000041be000000000001 697MKey/s x536870912 2^29.45 x2^30=2^59.45
GPU#0 Cnt:00000000000000000000000000000000000000000000000057a8000000000001 697MKey/s x536870912 2^29.45 x2^30=2^59.45
GPU#0 Cnt:0000000000000000000000000000000000000000000000006d92000000000001 697MKey/s x536870912 2^29.45 x2^30=2^59.45
GPU#0 Cnt:000000000000000000000000000000000000000000000000835a000000000001 696MKey/s x536870912 2^29.44 x2^30=2^59.44
GPU#0 Cnt:0000000000000000000000000000000000000000000000009922000000000001 696MKey/s x536870912 2^29.44 x2^30=2^59.44
***********GPU#0************
Total solutions: 1
KEY!!>000000000000000000000000000000000000000000000001a838b13505b26867
Pub: 30210c23b1a047bc9bdbb13448e67deddc108946de6de639bcc75d47c0216b1be383c4a8ed4fac77c0d2ad737d8499a362f483f8fe39d1e86aaed578a9455dfc
****************************
Found in 17 seconds
Also speed is little increased.
i am sorry bro its still same and still showing 4095 memory and cannot utilize above 3200+
Jump to: