search

johguse / profanity

Vanity address generator for Ethereum
834 stars 324 forks source link

Matching String Generation Outputting Incorrect Results #62

Closed Hurve closed 2 years ago

Hurve commented 2 years ago

When I do profanity --matching deadc0ffee, I expect for the program to continue to run this until it gets to an address starting with deadc0ffee. However, when I do it, I get a result where instantly at the beginning I get the address 0xdead1fff924c5c01c3ca6661c9b0f5acef2d785f for example with a score of 3, which doesn't make sense because it has 7 characters matching. I also instantly get an address similar to 0xdeadc0b9ee10326cc21bc3fc835d6ca778b96da4, where two characters in a row are incorrect and it has a score of 4. No matter how long I run it after this, I never get another address or an address with more characters matching. What is happening where two characters are not being generated?

Hurve commented 2 years ago

Update: I managed to get it to generate it after about 3000 seconds but I feel it is still notable because it could generate a string with all but 2 characters in 2 seconds. This would leave 225 more combinations and so should take 450 seconds, but it takes much longer, but I'll leave it at that.