---

[fuckthesystem]

One thing I haven't mentioned yet is that the passphrase text field supports multi-line text.  This provides a small amount of additional entropy to your passphrase.

So, this passphrase:

Code:

hello world

results in a different bitcoin address than this:

Code:

hello
world

This could also help make it easier to memorize a 12 word mnemonic, by splitting it into 4 lines, for example:

Code:

children park tight
especially blade odd
goal spider everything
slightly unless collapse

Doesn't this introduce incompatibility problems due to the different Windows and UNIX/OSX end of line character(s) standards?
It looks like users are going to want an option to set the EOL standard used.

[1715463771]

1715463771

[1715463771]

1715463771

[Dabs]

I want a version that spits out compressed keys. The private keys that begin with the letter K or L instead of the number 5.

[Financisto]

^^ That's a good request. +1

[Dabs]

^^ That's a good request. +1

I made the same request from the WarpWallet guys in 2014 but they said they were too busy. Maybe someone else can follow them up. Compressed keys. (They don't have a thread here on bitcointalk.)

[Financisto]

Dabs, you're such a lucky guy! 

When I last contacted those guys last year, they were supposed to be so busy that they didn't even bother replying my msg... 

[Dabs]

Oh, I emailed them twice. About a month apart. They replied to my second email. (I may have sent the first email to a wrong address or encrypted to wrong GPG.)

[TheButterZone]

I want a version that spits out compressed keys. The private keys that begin with the letter K or L instead of the number 5.

This would be easy to implement, and I understand why this is a desired function.  However, I prefer not to add more options that add to the complexity.  It may seem minimal to seasoned bitcoiners, but I worry that newcomers may be scared away by any additional options that they have to choose from.  The truth is, I should have used compressed keys to begin with, and now it's too late to change.

Now, if you just want to be able to do it for yourself, you can easily make it spit out compressed keys by modifying line 1246 of the html file:

var gen_compressed = false;

Just change "false" to "true".

Forked with that 1 change: https://github.com/TheButterZone/brainwallet.io

[Dabs]

Since someone bumped this thread, I just thought to mention, that if I can memorize 1 million characters, I might as well memorize the raw private key. Really, anything over a hundred characters is overkill. I'ma just randomly generate 40+ alpha numeric characters and memorize that. 60+ chars if case insensitive (or all one case).

Just don't use the first 60 digits of pi because everyone already has that memorized. I only memorize the first 17 digits because that's all any NASA scientist ever needs. (They use 15~16 for GPS calculations and everything within this solar system.)

[Dabs]

I would not recommend memorizing 40 alphanumeric characters.  Not only do I think it's overkill, but it's also dangerous because you could easily forget it.

You would be better off memorizing 12 random words, which is plenty secure and easier to remember.

Good idea.

Government Agent: "Please tell me your brain wallet password!!!"
Me: "I'm sorry, I forgot! It was 64 characters."

Actually, my use case for stuff like this is to have the characters printed out on paper. It's not a "brain" wallet anymore though.

[Financisto]

What happened to the OP and thread's subject?

[Dabs]

Seems he killed it around last month.... Actually, it seems he deleted all his posts, like he "banned" himself or something. And his email changed recently.

[Financisto]

Seems he killed it around last month.... Actually, it seems he deleted all his posts, like he "banned" himself or something.

A very strange fact.

In fact his projects rock and they're still online.