ExploreTrendingAnalytics
Nostr Archives
ExploreTrendingAnalytics
Ross121d ago
If anyone wants to try out a GPU (CUDA) based npub miner I put one together and pushed to GitHub. https://github.com/rossbates/rummage
💬 9 replies

Replies (9)

Ross121d ago
Took about 10 days on a 3070 to find this 9 char prefix.
0000 sats
Ross121d ago
FWIW… there is also a branch with a Metal build which is functional, but it’s only doing 8mm keys/sec vs about 42mm on the 3070.
0000 sats
Ross121d ago
Not totally sure about RHEL but I bet we can get it figured out. When you run nvcc —version does it fail? RHEL packages appear to be publicly available without any sort of restrictions https://developer.download.nvidia.com/compute/cuda/repos/… https://developer.download.nvidia.com/compute/cuda/repos/…
0000 sats
Ross121d ago
Found this which sounds like it might match your setup https://developer.download.nvidia.com/compute/cuda/12.4.1…
0000 sats
Ross120d ago
You bet, not a problem. If you get them installed all you would need to do is update the makefile to CCAP=60 and set NOSTR_BLOCKS_PER_GRID = 1120 in GPURummage.h
0000 sats
Ross120d ago
Yeah good point, no reason not to display both formats in either mode for convenience. Just updated that. Also heads up that I moved the block/thread config to the makefile as compiler flags so people don’t have to edit 2 files.
0000 sats
Ross119d ago
😬 well that’s embarrassing. Spent too much time on performance and not enough on testing. The math was correct, it was just backwards. Just pushed a fix.
0000 sats
Ross119d ago
Validated on both prefix types in a nostr client.
0000 sats
Ross119d ago
Also for the record, while some might blame Claude, AI slop, etc etc… I see this as my fault. Once I cloned the Damus repo and gave Claude the right instructions for testing everything was sorted out quickly. Had I done that up front, which is the proper approach, this would have been avoided.
0000 sats