Be my guest


The tool itself is here: https://mega.co.nz/#!xZdhRAwJ!a6e7ORQYVdEapDXwiVr5ZVxzrkxki5RWMC3kdY6dfts

I thought about this "darkNXT mining" recently. The problem is that to be successful, a somewhat large number of "miners" needed, and they need to be committed, i.e. no to abandon mining after a week or so without payouts.

Let's do some math. Complexity to "break" an account without a public key is 2^64, or 2^63 on average. According to earlier replies in this thread, there are about 1'000 accounts without public key, or about 2^10. Thus, on 2^53 work on average until at least one account is "broken".

The speed limiting factor is generating of public key from a (random) private key, the reasonable (yet optimistic) estimate is about 8'000-10'000 per second per CPU core, or 2^13.2 per second per CPU core. For 2^53 work this translates to 2^39.8 CPUcore-seconds, or about 110 million CPUcore-days / 300'000 CPU-core-years.

If we are very optimistic and assume that all miners are quad-core and that it is possible to 8x accelerate code by using e.g. AVX, then we'll be looking at "only" about a 3'500'000 Quad-core CPU day / 9'400 Quad-core CPU-years. GPUs won't reduce that figure more than tenfold (and that is *very* optimistic assumption).

So I am not convinced we have enough computing power to reliably mine darkNXT at this moment... To unlock one account per month (with current software) we'll need about 1 million "miners". For highly-optimized (and yet-to-be-seen) software that number drops to about 120'000, which is still pretty high number.

Parallel of course. System is designed in a way that all 'darkNXT' accounts can be recovered with a single 2^64 'pass', there's no need to target accounts individually.

So with darkNXT out there has anyone thought already about mining it?

I have some thoughts on how to do this from the technical standpoint but don't really know if it's profitable. Can someone perhaps provide rough estimates on number of darkNXT accounts and their total amount?

The point of my registration on this board was to share the tool (thus low message count). It is indeed very unfortunate that there's been some hacking lately. I haven't released source code along with the binary because I was concerned it could've been repurposed into a password cracker.

Anyways, I've updated the tool with ability to search for an account number with given prefix and/or suffix and now releasing source code along with binaries.

Usage:
nxtvanitygen p s t

All parameters are optional. If no thread count is specified, tool will use all available CPU resources.

Examples:
1. Search for accounts starting with "100" and ending with "001" using 7 threads
nxtvanitygen p100 s001 t7
[INFO] Starting search with 7 threads
[INFO] Searching for account with prefix "100"
[INFO] Searching for account with suffix "001"
[20] 10097471757607329001 : EtYAigzyvucocenbrl4TgrQnZQd
[20] 10003885613434887001 : Hap4Z3hiSUXmwcb71oaX4SA6lne

2. Search for accounts starting with "1337":
nxtvanitygen p1337
[INFO] Starting search with 8 threads
[INFO] Searching for account with prefix "1337"
[20] 13370655427675222059 : wyE3TKF1biEp8MQ9gF1yJEzvhr
[19]  1337321701037332552 : wyE3TKF1biEp8MQ9gF1yJEzvcu
[19]  1337265426018415968 : wyE3TKF1biEp8MQ9gF1yJEzvu6a

3. Search for accounts ending with "1337":
nxtvanitygen s1337
[INFO] Starting search with 8 threads
[INFO] Searching for account with suffix "1337"
[20] 17555624245168541337 : MLrIa0inNTbg1xEsX1Y6Q5d00o
[19]  4357874968632581337 : d7cf3etnKoQyZj5jClnb0rCaBL
[19]  2400089921591981337 : YfXTBQL1BZzCGUVjb0Z0dauGsla
[19]  1973134486410101337 : MLrIa0inNTbg1xEsX1Y6Q5d0bya

4. Just search for shortest possible account number:
nxtvanitygen
[INFO] Starting search with 8 threads
[20] 10338085328686616285 : OmMGRjBOMpShlfYMGFlBuPgja
[19]  4937369289318610888 : OmMGRjBOMpShlfYMGFlBuPgjd
[18]   629863575730409614 : OmMGRjBOMpShlfYMGFlBuPgjj
[18]   468107626643704710 : rctCFsNJU5WlLcdzoDXdhOd4b
[18]   220355335410294776 : OmMGRjBOMpShlfYMGFlBuPgjL
[17]    37716758511259142 : rctCFsNJU5WlLcdzoDXdhOd4P
[17]    31036511679475309 : OmMGRjBOMpShlfYMGFlBuPgjUb
[17]    30528851690106364 : OmMGRjBOMpShlfYMGFlBuPgjld
[17]    23063671801022467 : OLvwAaS8r244yFUCCjVkPzppXd
[17]    16132847436026631 : Kuj2No73oIIyqQ1sSZwXkmAmge
[17]    15844488120866410 : aycQzKqv8VwDly9bAnvJIrwcNf
[17]    14905054651945515 : rctCFsNJU5WlLcdzoDXdhOd4Nj
[17]    12782313021349671 : aycQzKqv8VwDly9bAnvJIrwcvl
[16]     8408041613508761 : aycQzKqv8VwDly9bAnvJIrwcJn
[16]     4055260369096446 : aycQzKqv8VwDly9bAnvJIrwcWt
[16]     2291473488286971 : OmMGRjBOMpShlfYMGFlBuPgjZz
[16]     1547187421785168 : aycQzKqv8VwDly9bAnvJIrwcyz
[15]      550469753637579 : rctCFsNJU5WlLcdzoDXdhOd4xR
[15]      412692226299035 : OLvwAaS8r244yFUCCjVkPzppXQb
[15]      190944096726430 : SedqAaKiWOme016JBddYCObdkNd
[13]        2511821714948 : 9MLNId7oWfs2aYcysRVibYKy99e

Few words on security: tool generates random passwords. They are constructed by combining 24-char random (per-thread) prefix and sequential suffix. Tool uses OpenSSL's RNG to generate that random prefix.

Also, it should go without saying but: PLEASE DON'T USE ANY OF THE PASSWORDS ABOVE AS IT'S NOT SAFE BECAUSE THEY ARE PUBLIC.

You can grab latest binaries (Windows only) here: https://mega.co.nz/#!sZ8j3CTL!O20atwe7U058_BJORo-3jzKn1LpsWmaVAs_xgmj4tBI (use 64-bit version if you're on 64-bit OS)
Source code (and VS 2013 project; you'll have to take care of OpenSSL headers and libs yourself): https://mega.co.nz/#!5E1wnCDI!Z062LkiZK9xJjpMKevNRjnvgfThr4d_eXbBS1gtQwnk

If you find the tool useful and/or fun please consider sending few tokens of appreciation to account number 86533079761. Thanks

Why would you think so? Every time you run the tool OpenSSL RNG is properly seeded and 16-character random prefix is generated, which becomes part of the account password. I personally do not see any issue with this.

I'm also planning to add some minor features and release the source code so anyone can audit.

This one (https://bitcointalk.org/index.php?topic=345619.msg3735874#msg3735874)?

No offence, but why run Java when there is much faster native implementation (https://bitcointalk.org/index.php?topic=345619.msg3735874#msg3735874)?

Hello folks. I am new here and don't have NXTs yet, but instead of just asking to send me some I figured I'd give something in return

I've noticed in the other thread there's been some discussion on generating short addresses. I've made a tool that could help with this; it is also much faster than the Java one posted before. It's free and you can grab it here (Windows binaries): https://mega.co.nz/#!9MkAWQ4Z!bz3BFCsVRSK_4Euhn8c-aj-umjstTsCe7-VYEcCYTEY

To use open command-line window and run it:

(Please use 64-bit binary whenever possible; it's like 3x faster than 32-bit one)

By default it'll use all available cores; if you'd rather limit it's appetite just specify number of threads to use on the command line:

That's it. When running, it will print out gradually decreasing account numbers and their passwords, e.g.:

As a bonus you can be sure that password is secure - it is composed of per-thread 16-character random prefix and random suffix of length 1 to 8.

Now, back to the opening point. If you find the tool useful and/or fun please consider sending few tokens of appreciation to account number 86533079761. Thanks

Mt.Gox introduced verification not so long ago (in May 2013, IIRC). That was supposedly done to increase safety of withdrawals, although at a cost of reduced privacy. I am certainly not comfortable with sending Mt. Gox my ID and/or utility bills, although others may have other opinion on that.

Mt.Gox isn't the only exchange, there are others with less privacy-invading practices.