Ninjastic
Search content
Sort by
Showing 3 of 3 results by TKDomino
Post
Topic
Board Bitcoin Discussion
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
by
TKDomino
on 23/02/2025, 15:24:04 UTC
Quote from: madogss on Today at 12:57:42 AM
Quote from: TKDomino on February 22, 2025, 09:53:01 PM

So, if I'm understanding it the last 3 places are cut off or will they continue to be cut off as the number grows. The reason why I'm asking is to keep track of my place. What would the correct syntax to output it to a file and would the file have it cut off or would it be correct in the file?

No the last 3 places are not cut off and the number continues to grow without hiding any numbers.

It is hard to keep track of your place because keyhunt-cuda works by dividing the global range by your grid so each thread is assigned a small chunk and each is incremented.

example if your grid is 512,512 and your global range is 3FFFFFFFF (34 bit) then that means you have 512 * 512 = 262,144 threads
so with 3FFFFFFFF(17179869183) / 262,144 = 65,535.999996185302734375 then we round to 65,536
this means each thread searches a small range of 65,536 keys.

The math is still not mathin in my head. If it was truly 661.92Mk/s it would only take a second because it's smaller than my search range 17.1 million. But if your saying it's billion then it would be even faster. So am I double checking keys at that point? So what would i need to set grid size to not double check keys? From what I see is its correctly counting because it's under my seach range 17 million. Found at 15 million.
Post
Topic
Board Bitcoin Discussion
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
by
TKDomino
on 23/02/2025, 00:00:57 UTC
Quote from: madogss on February 22, 2025, 11:25:10 PM
Quote from: TKDomino on February 22, 2025, 09:53:01 PM
Question for someone smarter than me. I don't understand, I'm running KeyHunt-Cuda but the output shows 661.92 Mk/s but for the T: 15,032,385,536. only 15 million. can someone explain it because the original key hunt was display correctly. maybe its just me not understanding what the T stands for. I though it was threads processed which would be a single key processed. correct me if I'm wrong please.

PS C:\KeyHunt-Cuda-main> .\KeyHunt-Cuda.exe -t 0 -g --gpui 0 --gpux 512,512 -m address --coin BTC --range 730fc235c00000000:730fc235fffffffff 1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9

KeyHunt-Cuda v1.07

COMP MODE    : COMPRESSED
COIN TYPE    : BITCOIN
SEARCH MODE  : Single Address
DEVICE       : GPU
CPU THREAD   : 0
GPU IDS      : 0
GPU GRIDSIZE : 512x512
SSE          : YES
RKEY         : 0 Mkeys
MAX FOUND    : 65536
BTC ADDRESS  : 1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9
OUTPUT FILE  : Found.txt

Start Time   : Sat Feb 22 13:25:47 2025
Global start : 730FC235C00000000 (67 bit)
Global end   : 730FC235FFFFFFFFF (67 bit)
Global range : 3FFFFFFFF (34 bit)

GPU          : GPU #0 Tesla T4 (40x64 cores) Grid(512x512)

[00:00:20] [CPU+GPU: 661.98 Mk/s] [GPU: 661.98 Mk/s] [C: 78.125000 %] [R: 0] [T: 13,421,772,800 (34 bit)] [F: 0]
=================================================================================
PubAddress: 1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qbP2K5cm35XKMND1X1KW
Priv (HEX): 730FC235C1942C1AE
PubK (HEX): 0212209F5EC514A1580A2937BD833979D933199FC230E204C6CDC58872B7D46F75
=================================================================================
[00:00:22] [CPU+GPU: 661.92 Mk/s] [GPU: 661.92 Mk/s] [C: 87.500000 %] [R: 0] [T: 15,032,385,536 (34 bit)] [F: 1]

That's displaying correctly, that is 15 billon not million multiply your Mk/s by the time so 661920000 * 22 = 14.56 billion this number is not exact because the speed fluctuates.

The T is for total keys checked.

So, if I'm understanding it the last 3 places are cut off or will they continue to be cut off as the number grows. The reason why I'm asking is to keep track of my place. What would the correct syntax to output it to a file and would the file have it cut off or would it be correct in the file?
Post
Topic
Board Bitcoin Discussion
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
by
TKDomino
on 22/02/2025, 21:53:01 UTC
Question for someone smarter than me. I don't understand, I'm running KeyHunt-Cuda but the output shows 661.92 Mk/s but for the T: 15,032,385,536. only 15 million. can someone explain it because the original key hunt was display correctly. maybe its just me not understanding what the T stands for. I though it was threads processed which would be a single key processed. correct me if I'm wrong please.

PS C:\KeyHunt-Cuda-main> .\KeyHunt-Cuda.exe -t 0 -g --gpui 0 --gpux 512,512 -m address --coin BTC --range 730fc235c00000000:730fc235fffffffff 1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9

KeyHunt-Cuda v1.07

COMP MODE    : COMPRESSED
COIN TYPE    : BITCOIN
SEARCH MODE  : Single Address
DEVICE       : GPU
CPU THREAD   : 0
GPU IDS      : 0
GPU GRIDSIZE : 512x512
SSE          : YES
RKEY         : 0 Mkeys
MAX FOUND    : 65536
BTC ADDRESS  : 1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9
OUTPUT FILE  : Found.txt

Start Time   : Sat Feb 22 13:25:47 2025
Global start : 730FC235C00000000 (67 bit)
Global end   : 730FC235FFFFFFFFF (67 bit)
Global range : 3FFFFFFFF (34 bit)

GPU          : GPU #0 Tesla T4 (40x64 cores) Grid(512x512)

[00:00:20] [CPU+GPU: 661.98 Mk/s] [GPU: 661.98 Mk/s] [C: 78.125000 %] [R: 0] [T: 13,421,772,800 (34 bit)] [F: 0]
=================================================================================
PubAddress: 1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9
Priv (WIF): p2pkh:KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qbP2K5cm35XKMND1X1KW
Priv (HEX): 730FC235C1942C1AE
PubK (HEX): 0212209F5EC514A1580A2937BD833979D933199FC230E204C6CDC58872B7D46F75
=================================================================================
[00:00:22] [CPU+GPU: 661.92 Mk/s] [GPU: 661.92 Mk/s] [C: 87.500000 %] [R: 0] [T: 15,032,385,536 (34 bit)] [F: 1]