Bitcoin Forum
October 06, 2024, 07:42:01 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Project Development / Re: Keyhunt - development requests - bug reports on: September 28, 2024, 10:26:47 AM
tests/135 solved
2  Bitcoin / Project Development / Re: Keyhunt - development requests - bug reports on: September 21, 2024, 07:18:41 PM

66  | 000000000000000000000000000000000000000000000002832ED74F2B5E35EE | 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so | 73786976294838206463                             | 024ee2be2d4e9f92d2f5a4a03058617dc45befe22938feed5b7a6b7282dd74cbdd | 2024-09-12



Puzzle 66 was found - 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so
3  Bitcoin / Project Development / Re: Keyhunt - development requests - bug reports on: July 23, 2024, 07:13:19 PM
AlbertoBSD

In BSGS Mode what is the difference between "Random" and "Dance"? Are both good for long ranges?

Thanks for any clarification!  Grin

Sequential Mode: This mode searches for the private key in a sequential manner, from a starting point and incrementing step by step. It is straightforward but can be slow if the target key is far from the starting point.

Backward Mode: In this mode, the search starts from a specified point and moves backward. This can be useful if you have reason to believe the key might be located before a certain point.

Both Mode: This mode combines both forward and backward searching. The algorithm searches in both directions simultaneously, which can increase the chances of finding the key faster compared to only moving in one direction.

Random Mode: Instead of following a linear path, the search jumps to random positions. This mode can help in scenarios where the key is not expected to be near the starting point and can be located anywhere in the search space.

Dance Mode: This is a more advanced and less predictable search pattern, potentially combining aspects of the other modes in a dynamic way. The exact implementation details can vary, but the goal is to maximize the coverage of the search space and increase the likelihood of finding the key efficiently.
4  Bitcoin / Project Development / Re: Keyhunt - development requests - bug reports on: June 28, 2024, 04:41:36 PM
Alberto.

I recommend https://electriccoin.co/zashi/ or any other supporting shielded and unshielded addresses.


Also how close are you to developing GPU support?

5  Bitcoin / Project Development / Re: Keyhunt - development requests - bug reports on: June 28, 2024, 12:24:55 PM
Hello Alberto,

Can you please add the in GitHub ZEC donation address?

Addicted to the program, also I think you should accept private donations not everybody wants to reveal their wallets to the world.

THX
6  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][BTCZ] BitcoinZ - No-premine, No-ICO, No-Dev Tax - 100% Community on: December 14, 2017, 09:47:33 PM
Hello Gents.


I'm thinking that BTCZ but be use on Exchange to Exchange transfers because extremely low costs and i think that must be write on whitepaper and coin properties on website.

Also its very very fast transactions..

This two property must be announced on website and coin whitepaper.


Best Regards.


https://www.youtube.com/watch?v=xLteQIYr7vU
7  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][BTCZ] BitcoinZ - No-premine, No-ICO, No-Dev Tax - 100% Community on: December 07, 2017, 03:52:27 PM
https://c-cex.com
is a biggest scam exchange
my money lose in Damn site and no answer tickets, no money back, always maintenance, maintenance, 
Damn site
Damn site
scam site Angry Angry Angry



You just don't know what you do , i have no problem on C-CEX.com and on Tradesatoshi
8  Economy / Exchanges / Re: C-CEX.com Trusted, Secure & Friendly Exchange Since 2013. 200+ Alts,USD,Low Fees on: November 01, 2017, 01:55:37 PM
@c-cex

When BTCZ is listed? There is tons of people waiting for it.

https://twitter.com/BTCZCommunity/status/924290602686173185

Did BTCZ communiy got scammed by C-CEX? :/...

Im sorry if i dont have all the facts right but AFAIK:

- BTCZ asked for listing and C-CEX agreed to list it for 4 BTC(?)
- Payment was done a week ago and C-CEX said it will be listed "in a hour / in a day" or  something like that.
- It has been a week and still no BTCZ on C-CEX...

Quote

   Active Dev/Support team
We have very responsive support team - You can contact us via skype or "Support" section.

Waiting for BTCZ to be listed!!!! What is going ON C-CEX.com
9  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][BTCZ] BitcoinZ on: October 06, 2017, 05:18:32 PM
 Wink
10  Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.5 (Windows/Linux) ANY CLUE on: June 14, 2017, 03:25:32 PM
WHAY MY RIG IS GOING DOWN PLEASE LOOK AT THIS IS !@#$%%^ FOR ME:

08:03:02:473   1e18   GPU0 t=58C fan=73%, GPU1 t=63C fan=83%, GPU2 t=69C fan=96%, GPU3 t=64C fan=85%, GPU4 t=68C fan=91%
08:03:02:489   1e18   em hbt: 0, fm hbt: 62,
08:03:02:489   1e18   watchdog - thread 0 (gpu0), hb time 31
08:03:02:489   1e18   watchdog - thread 1 (gpu0), hb time 203
08:03:02:489   1e18   watchdog - thread 2 (gpu1), hb time 296
08:03:02:505   1e18   watchdog - thread 3 (gpu1), hb time 141
08:03:02:505   1e18   watchdog - thread 4 (gpu2), hb time 141
08:03:02:505   1e18   watchdog - thread 5 (gpu2), hb time 312
08:03:02:505   1e18   watchdog - thread 6 (gpu3), hb time 312
08:03:02:523   1e18   watchdog - thread 7 (gpu3), hb time 157
08:03:02:527   1e18   watchdog - thread 8 (gpu4), hb time 78
08:03:02:527   1e18   watchdog - thread 9 (gpu4), hb time 250
08:03:03:872   1f64   got 248 bytes
08:03:03:872   1f64   buf: {"id":0,"jsonrpc":"2.0","result":["0x03200243d25df57cd0f2ec5c5919481242a38dfaca86cc45ccf0e448b4b10ad7","0x3868abc5dcee23341dee7f75f1be7f90ca9904961fef9e0f102cedba1171408d","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x3b152b"]}

08:03:03:888   1f64   parse packet: 247
08:03:03:904   1f64   ETH: job changed
08:03:03:920   1f64   new buf size: 0
08:03:03:925   1f64   ETH: 06/14/17-08:03:03 - New job from us1.ethermine.org:14444
08:03:03:926   1f64   target: 0x0000000112e0be82 (diff: 4000MH), epoch #129
08:03:03:926   1f64   ETH - Total Speed: 142.815 Mh/s, Total Shares: 89, Rejected: 0, Time: 00:37
08:03:03:926   1f64   ETH: GPU0 28.600 Mh/s, GPU1 28.564 Mh/s, GPU2 28.426 Mh/s, GPU3 28.592 Mh/s, GPU4 28.634 Mh/s
08:03:05:919   1f64   ETH: checking pool connection...
08:03:05:925   1f64   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

08:03:06:004   1f64   got 248 bytes
08:03:06:004   1f64   buf: {"id":3,"jsonrpc":"2.0","result":["0x03200243d25df57cd0f2ec5c5919481242a38dfaca86cc45ccf0e448b4b10ad7","0x3868abc5dcee23341dee7f75f1be7f90ca9904961fef9e0f102cedba1171408d","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x3b152b"]}

08:03:06:027   1f64   parse packet: 247
08:03:06:027   1f64   ETH: job is the same
08:03:06:042   1f64   new buf size: 0
08:03:07:157   1c60   recv: 51
08:03:07:157   1c60   srv pck: 50
08:03:07:258   1c60   srv bs: 0
08:03:07:258   1c60   sent: 206
08:03:12:157   17bc   recv: 51
08:03:12:157   17bc   srv pck: 50
08:03:12:242   17bc   srv bs: 0
08:03:12:242   17bc   sent: 206
08:03:15:940   1f64   ETH: checking pool connection...
08:03:15:940   1f64   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

08:03:16:041   1f64   got 248 bytes
08:03:16:041   1f64   buf: {"id":3,"jsonrpc":"2.0","result":["0x03200243d25df57cd0f2ec5c5919481242a38dfaca86cc45ccf0e448b4b10ad7","0x3868abc5dcee23341dee7f75f1be7f90ca9904961fef9e0f102cedba1171408d","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x3b152b"]}

08:03:16:041   1f64   parse packet: 247
08:03:16:041   1f64   ETH: job is the same
08:03:16:057   1f64   new buf size: 0
08:03:17:187   11a4   recv: 51
08:03:17:187   11a4   srv pck: 50
08:03:17:272   11a4   srv bs: 0
08:03:17:272   11a4   sent: 206
08:03:21:086   1f64   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x8866c0a", "0x000000000000000000000000000000000000000000000000000000008f29a7d8"]}

08:03:21:170   1f64   got 39 bytes
08:03:21:170   1f64   buf: {"id":6,"jsonrpc":"2.0","result":true}

08:03:21:170   1f64   parse packet: 38
08:03:21:186   1f64   new buf size: 0
08:03:22:222   10c4   recv: 51
08:03:22:222   10c4   srv pck: 50
08:03:22:323   10c4   srv bs: 0
08:03:22:323   10c4   sent: 206
08:03:25:969   1f64   ETH: checking pool connection...
08:03:25:981   1f64   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

08:03:26:056   1f64   got 248 bytes
08:03:26:062   1f64   buf: {"id":3,"jsonrpc":"2.0","result":["0x03200243d25df57cd0f2ec5c5919481242a38dfaca86cc45ccf0e448b4b10ad7","0x3868abc5dcee23341dee7f75f1be7f90ca9904961fef9e0f102cedba1171408d","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x3b152b"]}

08:03:26:066   1f64   parse packet: 247
08:03:26:070   1f64   ETH: job is the same
08:03:26:075   1f64   new buf size: 0
08:03:35:995   1f64   ETH: checking pool connection...
08:03:36:011   1f64   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

08:03:41:561   1f64   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x000000000000000000000000000000000000000000000000000000008f29a7d8"]}

08:03:46:549   1f64   ETH: checking pool connection...
08:03:49:390   1f64   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

08:03:55:436   1f64   Socket was closed remotely (by pool)
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!