It doesn't use invalid characters. But I'm not fluent in bech32m encoding, so maybe some character sequences just don't happen and therefore I can't find them?

It's 5 prefix + 3 suffix. I did a 4 + 4 a while back and that took about 3 days, but maybe I was extremely lucky then.

Reply to this note

Please Login to reply.

Discussion

Extremely lucky! 8 chars in 3 day is a no way with a consumer hardware. 6 chars requires 2-5 hours, 7 many days, I suppose 8 is about weeks.

Said that, the last 6 chars are a checksum, so inuitivelely it is possible that if you personalize them this can heavily (exponentially?) increase the matching complexity.

Don't remember if nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg did some experiments on this, maybe he can help.

The 4+4 was with 6 cores on a Xeon E-2286G, so no consumer thing. Lowered it to 3 cores now, as the machine is also busy with other stuff. I've set my mind on this address, so I have no choice to be patient 😄

I got mine (7 characters) in ~4 hours with ~100 CPUs on Google Cloud