Bitcoin Forum
April 27, 2017, 07:22:42 AM
 News: Latest stable version of Bitcoin Core: 0.14.1  [Torrent]. (New!)
 Home Help Search Donate Login Register
 Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 [51] 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 ... 163
phelix
Legendary

Offline

Activity: 1680

nmc:id/phelix

 March 24, 2013, 04:43:16 PM

Is it correct that it is virtually impossible to create an address that consists of only upper case letters and numbers?

blockchained.com ■ bitcointalk top posts
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1493277763
Hero Member

Offline

Posts: 1493277763

Ignore
 1493277763

1493277763
 Report to moderator
1493277763
Hero Member

Offline

Posts: 1493277763

Ignore
 1493277763

1493277763
 Report to moderator
1493277763
Hero Member

Offline

Posts: 1493277763

Ignore
 1493277763

1493277763
 Report to moderator
jackjack
Legendary

Offline

Activity: 1008

May Bitcoin be touched by his Noodly Appendage

 March 24, 2013, 04:44:29 PM

Is it correct that it is virtually impossible to create an address that consists of only upper case letters and numbers?
No

When you restrain ONE character to be a precise letter, the odds are (1/62)
When you restrain TWO characters to be a precise letter, the odds are (1/62)^2
etc...
When you restrain ONE character to be an upper case letter or number, the odds are (26upper case+10digits)/(62)=36/62
When you restrain TWO characters to be an upper case letter or number, the odds are [ (26upper case+10digits)/(62) ] ^ 2 = (36/62)^2

Addresses with 6 fixed characters are pretty common (K1773R owns 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y), the odds are ~1/57billions
The odds of having an address with only upper case letters and digits is (36/62)^34 ~ 1/17billions
It's about 4 times quicker to find such an address than an address with 6 fixed characters. Far from impossible.

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
The00Dustin
Hero Member

Offline

Activity: 806

 March 24, 2013, 05:24:29 PM

Addresses with 6 fixed characters are pretty common (K1773R owns 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y), the odds are ~1/57billions
The odds of having an address with only upper case letters and digits is (36/62)^34 ~ 1/17billions
It's about 4 times quicker to find such an address than an address with 6 fixed characters. Far from impossible.
But the last characters are checksum.  Just because you can get all uppercase in what you go for vane doesn't mean you can get an all uppercase checksum as well.  Since a checksum is a hash, I doubt you can even calculate the odds on that...  Given the random nature of a hash, though, I doubt it can be proven impossible either.
phelix
Legendary

Offline

Activity: 1680

nmc:id/phelix

 March 24, 2013, 05:51:10 PM

Is it correct that it is virtually impossible to create an address that consists of only upper case letters and numbers?
No

When you restrain ONE character to be a precise letter, the odds are (1/62)
When you restrain TWO characters to be a precise letter, the odds are (1/62)^2
etc...
When you restrain ONE character to be an upper case letter or number, the odds are (26upper case+10digits)/(62)=36/62
When you restrain TWO characters to be an upper case letter or number, the odds are [ (26upper case+10digits)/(62) ] ^ 2 = (36/62)^2

Addresses with 6 fixed characters are pretty common (K1773R owns 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y), the odds are ~1/57billions
The odds of having an address with only upper case letters and digits is (36/62)^34 ~ 1/17billions
It's about 4 times quicker to find such an address than an address with 6 fixed characters. Far from impossible.
I had got it wrong, thanks.

Addresses with 6 fixed characters are pretty common (K1773R owns 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y), the odds are ~1/57billions
The odds of having an address with only upper case letters and digits is (36/62)^34 ~ 1/17billions
It's about 4 times quicker to find such an address than an address with 6 fixed characters. Far from impossible.
But the last characters are checksum.  Just because you can get all uppercase in what you go for vane doesn't mean you can get an all uppercase checksum as well.  Since a checksum is a hash, I doubt you can even calculate the odds on that...  Given the random nature of a hash, though, I doubt it can be proven impossible either.
Guess I will have to give it a try then

blockchained.com ■ bitcointalk top posts
jackjack
Legendary

Offline

Activity: 1008

May Bitcoin be touched by his Noodly Appendage

 March 24, 2013, 05:54:20 PM

Addresses with 6 fixed characters are pretty common (K1773R owns 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y), the odds are ~1/57billions
The odds of having an address with only upper case letters and digits is (36/62)^34 ~ 1/17billions
It's about 4 times quicker to find such an address than an address with 6 fixed characters. Far from impossible.
But the last characters are checksum.  Just because you can get all uppercase in what you go for vane doesn't mean you can get an all uppercase checksum as well.  Since a checksum is a hash, I doubt you can even calculate the odds on that...  Given the random nature of a hash, though, I doubt it can be proven impossible either.
The random nature is exactly why I think we can apply odds to this

For exemple, let's take characters in "0123456789"
Addresses in that system is 6 random digit + 4 digit from hash
The condition we want is "<3"
So:
- the odds for the 6digits part is (3/10)^6
- about the hash part: the hash is random, so you have 3/10 odds that one character of the hash is <3
- then the hash part has (3/10)^4 odds to be written with 4 "<3" digit

So finally, we get (3/10)^10, just like if we don't take into account the fact that last characters are from a hash
This works because a hash is random, this gives the necessary linear independance

I might be proven wrong though

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
phelix
Legendary

Offline

Activity: 1680

nmc:id/phelix

 March 24, 2013, 06:01:04 PM

1P3H99S84AVNAV7UX4EY8BFUF6H4MQVFZE

edit: nice tool.

In case you are wondering: This allows slightly leaner QR codes.

blockchained.com ■ bitcointalk top posts
K1773R
Legendary

Offline

Activity: 1526

/dev/null

 March 24, 2013, 07:50:48 PM

Addresses with 6 fixed characters are pretty common (K1773R owns 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y), the odds are ~1/57billions
The odds of having an address with only upper case letters and digits is (36/62)^34 ~ 1/17billions
It's about 4 times quicker to find such an address than an address with 6 fixed characters. Far from impossible.
But the last characters are checksum.  Just because you can get all uppercase in what you go for vane doesn't mean you can get an all uppercase checksum as well.  Since a checksum is a hash, I doubt you can even calculate the odds on that...  Given the random nature of a hash, though, I doubt it can be proven impossible either.
as the last poster proofed it is possible, etotheipi has a only uppercase too

[GPG Public Key]  [Devcoin Builds]  [BBQCoin Builds]  [Multichain Blockexplorer]  [Multichain Blockexplorer - PoS Coins]  [Ufasoft Miner Linux Builds]
BTC/DVC/TRC/FRC: 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM AK1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: NK1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: LKi773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: EK1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: bK1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
phelix
Legendary

Offline

Activity: 1680

nmc:id/phelix

 March 24, 2013, 10:04:35 PM

also single (lower) case addresses are much easier to tell over the phone:

vanitygen64.exe -r "^[a-z0-9_]*\$"

-->  141zuyxnimmphjtow3ckrb4y7pswn56rmo

blockchained.com ■ bitcointalk top posts
wtfvanity
Hero Member

Offline

Activity: 504

WTF???

 March 25, 2013, 02:25:35 PM

But you guys have numbers mixed in too.

Make it ALL lower or upper only, with just the leading one

https://bitcointalk.org/index.php?topic=90982.0

There is an all uppercase address, and I have these two

1odfsrirfbxtwjoviseqdnuixwvhsnPbJ       (longest lowercase prefix - owner: wtfvanity)
19279281759997344NJ2KMcdRZNVT5rHhq      (longest digit-only prefix  - owner: wtfvanity)

.      .            .            .        .            .            .          .        .     .               .            .             .            .            .           .            .     .               .         .              .           .            .            .            .     .      .     .    .     .          .            .          .            .            .           .              .     .            .            .           .            .               .         .            .     .            .            .             .            .              .            .            .      .            .            .            .            .            .            .             .          .
Remember remember the 5th of November
Legendary

Offline

Activity: 1526

Reverse engineer from time to time

 March 27, 2013, 12:35:48 PM

With 13.2 beta drivers, it's impossible to run anything that has to do with OCL, I keep getting this error during the compilation of the .CL kernel(LLVM error and so on), which is the exact same error people are having here.

I would sure hope there is some workaround ASIDE from downgrading drivers, I honestly need these new drivers.

BTC:1AiCRMxgf1ptVQwx6hDuKMu4f7F27QmJC2
nagnagnag2
Full Member

Offline

Activity: 142

 March 27, 2013, 11:16:23 PM

1 BTC bounty for a fix for 13.x catalyst + vanitygen patch working, with source and builds for Linux, Windows, etc.

I will add 0.1 BTC to that.
jackjack
Legendary

Offline

Activity: 1008

May Bitcoin be touched by his Noodly Appendage

 March 27, 2013, 11:54:17 PM

Is samr7 still developing Vanitygen?

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
K1773R
Legendary

Offline

Activity: 1526

/dev/null

 March 28, 2013, 09:14:03 AM

hes inactive since a long time

[GPG Public Key]  [Devcoin Builds]  [BBQCoin Builds]  [Multichain Blockexplorer]  [Multichain Blockexplorer - PoS Coins]  [Ufasoft Miner Linux Builds]
BTC/DVC/TRC/FRC: 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM AK1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: NK1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: LKi773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: EK1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: bK1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
wtfvanity
Hero Member

Offline

Activity: 504

WTF???

 March 28, 2013, 01:49:17 PM

hes inactive since a long time

Date Registered:   June 08, 2011, 10:59:48 PM
Last Active:   October 24, 2012, 03:59:55 PM

.      .            .            .        .            .            .          .        .     .               .            .             .            .            .           .            .     .               .         .              .           .            .            .            .     .      .     .    .     .          .            .          .            .            .           .              .     .            .            .           .            .               .         .            .     .            .            .             .            .              .            .            .      .            .            .            .            .            .            .             .          .
malevolent
can into space
Staff
Legendary

Offline

Activity: 1680

 April 02, 2013, 07:21:54 PM

I think he may return; last time he came back with a new version of vanitygen after 11 months of inactivity.
Lethos
Sr. Member

Offline

Activity: 476

Keep it Simple. Every Bit Matters.

 April 06, 2013, 10:29:48 PM

I'm sure some might find this funny, but has anyone tried this on a Raspberry Pi - vanitygen that is.
I got a little project going (My RPi will arrive soon) and it might be nice to have a few of my preferred bitcoin tools on there.

I don't expect fast results, I just wondered if anyone had done it.

Lethos Designs | UK BTC Seller -  Local Bitcoins | BTC OTC Rating | 1EFhXfX9uXsbXBF3LC69GiVfS3SHCsyMR1
K1773R
Legendary

Offline

Activity: 1526

/dev/null

 April 06, 2013, 11:37:56 PM

the CPU is too bad for it

[GPG Public Key]  [Devcoin Builds]  [BBQCoin Builds]  [Multichain Blockexplorer]  [Multichain Blockexplorer - PoS Coins]  [Ufasoft Miner Linux Builds]
BTC/DVC/TRC/FRC: 1K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM AK1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: NK1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: LKi773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: EK1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: bK1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
Remember remember the 5th of November
Legendary

Offline

Activity: 1526

Reverse engineer from time to time

 April 07, 2013, 03:49:12 PM

Pardon my abilities, but I think the error may come from the bignum implementation. At least, after removing the functions that cause it to crash, I started re-adding them, then I started to remove pieces of code from functions and ended up with an OK compile which led me to this theory.

To further support my theory, change this:
Code:
typedef struct {
bn_word d[BN_NWORDS];
} bignum;

to this

Code:
typedef struct {
bn_word d[0];
} bignum;

The program won't work correctly, but the calc_addr.cl kernel will compile.

BTC:1AiCRMxgf1ptVQwx6hDuKMu4f7F27QmJC2
MeatPopsicle
Jr. Member

Offline

Activity: 48

 April 08, 2013, 08:53:14 AM

How'd you figure out the functions that were causing it to crash?
Remember remember the 5th of November
Legendary

Offline

Activity: 1526

Reverse engineer from time to time

 April 08, 2013, 12:25:19 PM

How'd you figure out the functions that were causing it to crash?
I was more than clear in my post.

Anyway, I was still wrong. After talking on the #opencl channel on freenode, an OpenCL C compiler developer said that the issue is caused by incorrect instructions produced by the OpenCL compiler.

BTC:1AiCRMxgf1ptVQwx6hDuKMu4f7F27QmJC2
 Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 [51] 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 ... 163