I understand people will always be on the fence, as we have all seen scammers in crypto.
I've not seen the code, but i have been in contanct with @ttdclient via mail for the past weeks, and i must say, my impression is that he is a stand up guy, that wants to help the community with the poolclient he made - simple as that.
If he were to be a scammer im sure he would have used an e-mail address not associated with his own domain which is run by his company.
I don't really see any red signals here.
Topic: [ARCHIVE] Bitcoin challenge discusion - page 6. (Read 29427 times)
Scam. the pool will never find a solution. And do not share it. The author does not want to show the source code.
Is everyone who doesn't want to show the code a cheater? I have seen the source code and I can confirm that it is clean.
Scam. the pool will never find a solution. And do not share it. The author does not want to show the source code.
By appearing under the nickname "testtest" I allow myself to connect to the pool activity from time to time.
The contact in time related to his pool has allowed me to gain confidence in the matter of intentions, and the fact of my temporary absence in topic # 64 is related to the fact that I use the power I currently have for other purposes. I intend to make the progress available in # 64 available for this pool (22 quadrillions of already checked keys) and after resuming full participation in this challenge with all my strength - I intend to do it through this pool.
-
I wrote this post to:
- explanations of the increases that take place
- warn other participants that my 320,000 checked ranges will be added to the "testtest" account
- encourage others to join, as I, as a person who poses a threat to the success of the pool (de facto a slightly 50% chance that I would find the key first) - I move to it myself.
Greetings!
The contact in time related to his pool has allowed me to gain confidence in the matter of intentions, and the fact of my temporary absence in topic # 64 is related to the fact that I use the power I currently have for other purposes. I intend to make the progress available in # 64 available for this pool (22 quadrillions of already checked keys) and after resuming full participation in this challenge with all my strength - I intend to do it through this pool.
-
I wrote this post to:
- explanations of the increases that take place
- warn other participants that my 320,000 checked ranges will be added to the "testtest" account
- encourage others to join, as I, as a person who poses a threat to the success of the pool (de facto a slightly 50% chance that I would find the key first) - I move to it myself.
Greetings!
seems like the tddclient pool is getting more and more attention, the last hour we have been running at 9 BillionKeys/s in total 
great work getting this pool up and running @ttdclient
great work getting this pool up and running @ttdclient
Hello, i tried it and its work. But i don't understand why the program include some other wallet and found them !!?
and also how can I add range that I scanned ? because if i just let program run ,he will rescan some range that I scanned in my own !!
TTDClient 1.0 http://www.ttdsales.com/64bit/
cuBitCrack -b 52 -t 256 -p 1200 --keyspace F2D5B10000000000:+FFFFFFFFF -o F2D5B10000000000.txt 16ARje2KC7bVhHbBjjF9Bdwgi4dfM2wXKM 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
[2019-11-17.10:14:24] [Info] Compression: compressed
[2019-11-17.10:14:24] [Info] Starting at: 000000000000000000000000000000000000000000000000F2D5B10000000000
[2019-11-17.10:14:24] [Info] Ending at: 000000000000000000000000000000000000000000000000F2D5B10FFFFFFFFF
[2019-11-17.10:14:24] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-11-17.10:14:24] [Info] Initializing Tesla P100-PCIE-16GB
[2019-11-17.10:14:24] [Info] Generating 15,974,400 starting points (609.4MB)
[2019-11-17.10:14:28] [Info] 10.0%
[2019-11-17.10:14:29] [Info] 100.0%
[2019-11-17.10:14:29] [Info] Done
Tesla P100-PCIE- 1729 / 16280MB | 2 targets 462.14 MKey/s (14,376,960,000 total) [00:00:29][2019-11-17.10:15:02] [Info] Found key for address '16ARje2KC7bVhHbBjjF9Bdwgi4dfM2wXKM'. Written to 'F2D5B10000000000.txt'
Tesla P100-PCIE- 1729 / 16280MB | 1 target 464.17 MKey/s (68,546,150,400 total) [00:02:26][2019-11-17.10:16:57] [Info] Reached end of keyspace
cuBitCrack -b 52 -t 256 -p 1200 --keyspace BF5100A000000000:+FFFFFFFFF -o BF5100A000000000.txt 1C6md6xDXeskzof2e8FJWJJq4v8VJCEyZj 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
[2019-11-17.10:16:58] [Info] Compression: compressed
[2019-11-17.10:16:58] [Info] Starting at: 000000000000000000000000000000000000000000000000BF5100A000000000
[2019-11-17.10:16:58] [Info] Ending at: 000000000000000000000000000000000000000000000000BF5100AFFFFFFFFF
[2019-11-17.10:16:58] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-11-17.10:16:58] [Info] Initializing Tesla P100-PCIE-16GB
[2019-11-17.10:16:58] [Info] Generating 15,974,400 starting points (609.4MB)
[2019-11-17.10:17:02] [Info] 10.0%
[2019-11-17.10:17:03] [Info] 100.0%
[2019-11-17.10:17:03] [Info] Done
Tesla P100-PCIE- 1729 / 16280MB | 2 targets 461.89 MKey/s (19,472,793,600 total) [00:00:40][2019-11-17.10:17:46] [Info] Found key for address '1C6md6xDXeskzof2e8FJWJJq4v8VJCEyZj'. Written to 'BF5100A000000000.txt'
Tesla P100-PCIE- 1729 / 16280MB | 1 target 464.42 MKey/s (49,105,305,600 total)
The second target is used for proof of work. The private key that is found when scanning the range is used to find the range marker in the DB to mark it checked.
They are located at random locations throughout the individual ranges.
They are located at random locations throughout the individual ranges.
I had a large amounts of .txt files generated with bitcrack as i used the --continue parameter before scanning with ttdclient, these files contains information about your scanned range, i handed those over to @ttdclient and he imported the ranges in the database as scanned...
bounty0z - bulleteyedk is correct. The linux and the windows version are intended to operate the same. You put your settings into settings.ini and just run ./ttdclient.
If you could create an account on the pool and send me an email so we can get a dialog started I would very much like to work with you to get the ubuntu version working solid.
If you could create an account on the pool and send me an email so we can get a dialog started I would very much like to work with you to get the ubuntu version working solid.
Hello, i tried it and its work. But i don't understand why the program include some other wallet and found them !!?
and also how can I add range that I scanned ? because if i just let program run ,he will rescan some range that I scanned in my own !!
TTDClient 1.0 http://www.ttdsales.com/64bit/
cuBitCrack -b 52 -t 256 -p 1200 --keyspace F2D5B10000000000:+FFFFFFFFF -o F2D5B10000000000.txt 16ARje2KC7bVhHbBjjF9Bdwgi4dfM2wXKM 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
[2019-11-17.10:14:24] [Info] Compression: compressed
[2019-11-17.10:14:24] [Info] Starting at: 000000000000000000000000000000000000000000000000F2D5B10000000000
[2019-11-17.10:14:24] [Info] Ending at: 000000000000000000000000000000000000000000000000F2D5B10FFFFFFFFF
[2019-11-17.10:14:24] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-11-17.10:14:24] [Info] Initializing Tesla P100-PCIE-16GB
[2019-11-17.10:14:24] [Info] Generating 15,974,400 starting points (609.4MB)
[2019-11-17.10:14:28] [Info] 10.0%
[2019-11-17.10:14:29] [Info] 100.0%
[2019-11-17.10:14:29] [Info] Done
Tesla P100-PCIE- 1729 / 16280MB | 2 targets 462.14 MKey/s (14,376,960,000 total) [00:00:29][2019-11-17.10:15:02] [Info] Found key for address '16ARje2KC7bVhHbBjjF9Bdwgi4dfM2wXKM'. Written to 'F2D5B10000000000.txt'
Tesla P100-PCIE- 1729 / 16280MB | 1 target 464.17 MKey/s (68,546,150,400 total) [00:02:26][2019-11-17.10:16:57] [Info] Reached end of keyspace
cuBitCrack -b 52 -t 256 -p 1200 --keyspace BF5100A000000000:+FFFFFFFFF -o BF5100A000000000.txt 1C6md6xDXeskzof2e8FJWJJq4v8VJCEyZj 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN
[2019-11-17.10:16:58] [Info] Compression: compressed
[2019-11-17.10:16:58] [Info] Starting at: 000000000000000000000000000000000000000000000000BF5100A000000000
[2019-11-17.10:16:58] [Info] Ending at: 000000000000000000000000000000000000000000000000BF5100AFFFFFFFFF
[2019-11-17.10:16:58] [Info] Counting by: 0000000000000000000000000000000000000000000000000000000000000001
[2019-11-17.10:16:58] [Info] Initializing Tesla P100-PCIE-16GB
[2019-11-17.10:16:58] [Info] Generating 15,974,400 starting points (609.4MB)
[2019-11-17.10:17:02] [Info] 10.0%
[2019-11-17.10:17:03] [Info] 100.0%
[2019-11-17.10:17:03] [Info] Done
Tesla P100-PCIE- 1729 / 16280MB | 2 targets 461.89 MKey/s (19,472,793,600 total) [00:00:40][2019-11-17.10:17:46] [Info] Found key for address '1C6md6xDXeskzof2e8FJWJJq4v8VJCEyZj'. Written to 'BF5100A000000000.txt'
Tesla P100-PCIE- 1729 / 16280MB | 1 target 464.42 MKey/s (49,105,305,600 total)
bounty0z - bulleteyedk is correct. The linux and the windows version are intended to operate the same. You put your settings into settings.ini and just run ./ttdclient.
If you could create an account on the pool and send me an email so we can get a dialog started I would very much like to work with you to get the ubuntu version working solid.
If you could create an account on the pool and send me an email so we can get a dialog started I would very much like to work with you to get the ubuntu version working solid.
i tried this command
Code:
./ttdclient --keyspace 800A900100100100:FFFF500100100100 -c 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN -b 52 -t 256 -p 1200
Code:
TTDClient 1.0 http://www.ttdsales.com/64bit/
cuBitCrack -b 48 --keyspace :+FFFFFFFFF -o .txt
[2019-11-16.10:08:47] [Error] Missing arguments
BitCrack OPTIONS [TARGETS]
Where TARGETS is one or more addresses
--help Display this message
cuBitCrack -b 48 --keyspace :+FFFFFFFFF -o .txt
[2019-11-16.10:08:47] [Error] Missing arguments
BitCrack OPTIONS [TARGETS]
Where TARGETS is one or more addresses
--help Display this message
I don't know if there is any difference between the windows/linux version, but you only need to run ttdclient, the parameters have to be in the settings.ini file:
Quote
The first three lines of this file are used to configure ttdclient.exe settings
The first line is your username.
The second line is to configure which version of BitCrack you are using. cu for Nvidia and cl for AMD GPUs.
The third line is to tweak bitcrack for better performance with you particular GPU and or to select which GPU to run the program on. These are the same settings you would feed BitCrack.
The first line is your username.
The second line is to configure which version of BitCrack you are using. cu for Nvidia and cl for AMD GPUs.
The third line is to tweak bitcrack for better performance with you particular GPU and or to select which GPU to run the program on. These are the same settings you would feed BitCrack.
I have released version 1.1 of the windows client. It now displays the real keys per second between ranges.
It will also exit smoothly if the prize key is found with a message instead of trying to continue to request ranges.
It can be downloaded from the pool stats page.
http://www.ttdsales.com/64bit/
If someone out there could tell me if the ubuntu version is working well I will implement the changes to that version as well.
I only have linux in vmware so can not test with a GPU.
i tried this commandIt will also exit smoothly if the prize key is found with a message instead of trying to continue to request ranges.
It can be downloaded from the pool stats page.
http://www.ttdsales.com/64bit/
If someone out there could tell me if the ubuntu version is working well I will implement the changes to that version as well.
I only have linux in vmware so can not test with a GPU.
Code:
./ttdclient --keyspace 800A900100100100:FFFF500100100100 -c 16jY7qLJnxb7CHZyqBP8qca9d51gAjyXQN -b 52 -t 256 -p 1200
Code:
TTDClient 1.0 http://www.ttdsales.com/64bit/
cuBitCrack -b 48 --keyspace :+FFFFFFFFF -o .txt
[2019-11-16.10:08:47] [Error] Missing arguments
BitCrack OPTIONS [TARGETS]
Where TARGETS is one or more addresses
--help Display this message
cuBitCrack -b 48 --keyspace :+FFFFFFFFF -o .txt
[2019-11-16.10:08:47] [Error] Missing arguments
BitCrack OPTIONS [TARGETS]
Where TARGETS is one or more addresses
--help Display this message
I have released version 1.1 of the windows client. It now displays the real keys per second between ranges.
It will also exit smoothly if the prize key is found with a message instead of trying to continue to request ranges.
It can be downloaded from the pool stats page.
http://www.ttdsales.com/64bit/
If someone out there could tell me if the ubuntu version is working well I will implement the changes to that version as well.
I only have linux in vmware so can not test with a GPU.
It will also exit smoothly if the prize key is found with a message instead of trying to continue to request ranges.
It can be downloaded from the pool stats page.
http://www.ttdsales.com/64bit/
If someone out there could tell me if the ubuntu version is working well I will implement the changes to that version as well.
I only have linux in vmware so can not test with a GPU.
hi there mrxtraf,
great things you are making sir,
is this available to try out, would again two days off, to do some program learning etc.
instead of just doing nothing,
thanks for the updates.
I really don't understand why on-topic messages are being deleted by mods in this thread.
It's not like we're breaking Bitcoin itself. An open discussion regarding this challenge will actually encourage improvements in security.
It's not like we're breaking Bitcoin itself. An open discussion regarding this challenge will actually encourage improvements in security.
After re-reading the deleted message, I've realised it was probably removed because it contained a link posted by brainless.
So I'll repost the second part of the text, which is not specifically related to brainless' weird/possibly scammish challenge.
====
====
====
I believe that with ECDSA it's possible to do some magic with multiple related public and private keys, like pubkey(privkey1+privkey2+privkey3+...) == pubkey1+pubkey2+pubkey3+...
Imagine a challenge where the private key holding funds could only be determined once multiple pubkeys had been cracked. Add together all of the cracked privkeys, and you have the final value for the privkey that holds the funds.
Would everyone go it alone, or co-operate to achieve the outcome more efficiently?
almightyruler sent you PM, check and reply
In an effort to reduce system load I do not see why making system stats available to non users would be beneficial.
It could encourage more to sign up. The URL you keep linking doesn't really provide any information or motivation to join.
Create the page once every 10 minutes (or whatever) then serve the cached copy.
I like that reason. I compromised and added a user free version of the last 60 minutes chart to the login page.
I have been meaning to add some explanation of how the pool works to that page too at some point.
In an effort to reduce system load I do not see why making system stats available to non users would be beneficial.
It could encourage more to sign up. The URL you keep linking doesn't really provide any information or motivation to join.
Create the page once every 10 minutes (or whatever) then serve the cached copy.
In an effort to reduce system load I do not see why making system stats available to non users would be beneficial.
What is the reason you had in mind?
On a side note I just updated the stats page to include active user indication on the top 10 and current speed of the active users.
Also made some additional interface tweaks.
http://www.ttdsales.com/64bit/
We are about to cross 1/1000 of the entire range.
What is the reason you had in mind?
On a side note I just updated the stats page to include active user indication on the top 10 and current speed of the active users.
Also made some additional interface tweaks.
http://www.ttdsales.com/64bit/
We are about to cross 1/1000 of the entire range.
However in fact, this list of 10 million addresses is only "wild kangaroos" received from the public key of "rich BTC address". Only the creator of the list knows "the step" from every address to the rich one.
This is like "hidden scam". The creator's goal is to find the key to the rich address, and he provides the list of 10 million addresses derived from that one. All the followers will actually spend the electricity, use their CPU/GPU powers to help the pseudo researcher to find the rich key (thinking that they are actually helping in some crypto research)
This is like "hidden scam". The creator's goal is to find the key to the rich address, and he provides the list of 10 million addresses derived from that one. All the followers will actually spend the electricity, use their CPU/GPU powers to help the pseudo researcher to find the rich key (thinking that they are actually helping in some crypto research)
So I guess it would be similar to a third party generating a vanity address?
1. Requester generates a random privkey, discloses requesterpubkey and desired targetaddress to cracker
2. Cracker generates random privkeys to find a match: address(pubkey(crackerprivkey)+requesterpubkey)==targetaddress
3. When found, cracker provides requester with the solution (which is crackerprivkey)
4. Requester recovers privkey of targetaddress by adding together requesterprivkey+crackerprivkey
5. Cracker never knows they've actually cracked a funded address.
On second thoughts, it can't be that simple, since the cracker would still need to bruteforce the 2^160 space, which is impossible. How does it work? The scammer is precomputing kangaroo steps and splitting them out into discrete problems which can be recombined to form the final solution?
The thing is no scammer ever had success with this.They have this delusional idea and try it against all odds.
@Tddclient, can you please make the stats accessible for non-registered users (anonymized sensible data)?
-snip-
On second thoughts, it can't be that simple, since the cracker would still need to bruteforce the 2^160 space, which is impossible. How does it work? The scammer is precomputing kangaroo steps and splitting them out into discrete problems which can be recombined to form the final solution?
On second thoughts, it can't be that simple, since the cracker would still need to bruteforce the 2^160 space, which is impossible. How does it work? The scammer is precomputing kangaroo steps and splitting them out into discrete problems which can be recombined to form the final solution?
It is my hypothesis about "hidden scam". But you are right - it is not simpe. However, "scammer" has no any investments and presents a positive self-image: like he is not cracker, but researcher, or crypto analytic and so on. Followers will actually crack the key thinking that they are helping in crypto research.
Also the creators of million-list addresses do not disclose how they actually received these addresses, just ask to find any one private key to any address within the list. I beleive that if you face with such situation it is scam and do not recommend to participate in pseudo crypto research. As there are no dependencies disclosure from the addresses creators, I guess it is hidden scam.
However in fact, this list of 10 million addresses is only "wild kangaroos" received from the public key of "rich BTC address". Only the creator of the list knows "the step" from every address to the rich one.
This is like "hidden scam". The creator's goal is to find the key to the rich address, and he provides the list of 10 million addresses derived from that one. All the followers will actually spend the electricity, use their CPU/GPU powers to help the pseudo researcher to find the rich key (thinking that they are actually helping in some crypto research)
This is like "hidden scam". The creator's goal is to find the key to the rich address, and he provides the list of 10 million addresses derived from that one. All the followers will actually spend the electricity, use their CPU/GPU powers to help the pseudo researcher to find the rich key (thinking that they are actually helping in some crypto research)
So I guess it would be similar to a third party generating a vanity address?
1. Requester generates a random privkey, discloses requesterpubkey and desired targetaddress to cracker
2. Cracker generates random privkeys to find a match: address(pubkey(crackerprivkey)+requesterpubkey)==targetaddress
3. When found, cracker provides requester with the solution (which is crackerprivkey)
4. Requester recovers privkey of targetaddress by adding together requesterprivkey+crackerprivkey
5. Cracker never knows they've actually cracked a funded address.
On second thoughts, it can't be that simple, since the cracker would still need to bruteforce the 2^160 space, which is impossible. How does it work? The scammer is precomputing kangaroo steps and splitting them out into discrete problems which can be recombined to form the final solution?
Jump to: