Yeah, no problem. I have a bunch of older paper wallet generators, some don't exist anymore due to the website disappearing (or removing the files). In the end I'm fairly convinced that using Electrum or one of those Electrum compatible seed generators using your own entropy (if you like to flip coins or roll dice) is more convenient.

I plan to release an update adding support for this "passphrase plus xor" brainwallet variant, so don't go using it.

Someone forked Warp Wallet to spit out a 12 word seed (as well as the extended private key), but still haven't found one that directly goes to segwit addresses. You could do a multi-step procedure to use a randomly generated password to spit out yprivs and zprivs if you like to have a segwit brainwallet.

I found these:
https://github.com/Logicwax/PortalWallet <= used older Warp Wallet code, and doesn't have segwit.
https://www.nowallet.org/

The only use-case for a pure brainwallet, as others have mentioned, is when escaping a country or government or warzone with only the clothes on your back. Even in this case, you can probably sew on embroidered password under your clothes or otherwise write it down somewhere on your person.

Unfortunately, I don't have an easy answer to this.

In this case, might be the most relevant though only to count trust based on Escrow service feedback.

I'd like to point out that 5/6th of your positive DT feedback is based on Trust selfscratching. Without this, your 10.9 Score would drop to 7.6, which mean you'd share Rank 11 and 12 instead of 5.

It doesn't seem right to use the Trust rating you've inflated by yourself to increase your Grade from A to AA.

@Financisto: I've only looked at one account because I noticed Dabs' post. It would be really nice if you can adjust all grades for the effect of "Trust selfscratching".

I have noticed the compile error for the "SSE2 instruction set" for some computers.
This seems to be related to the physical machine that is used.
Argon2 is optimized for the x86 architecture, and this is the cause of the compile error.

I have three Ubuntu 14.04 machines, and the two 64-bit machines compile the source without errors, one Intel and one AMD machine.

But the older 32 bit machine with an Intel Atom processor get the compile error.
I will fix this.


Yes, Bitgen is currently using Argon2d (and not Argon2i), but the choice was not an easy one.

The choice of the "d" version instead of "i" was motivated  since a dedicated machine without any internet connection should not have any side-channels for timing attacks(?)
For example, on a shared Linux-machine were several persons are logged in at the same time there will be possible to use side-channels when someone is changing a password.

I also interpret "being faster" as positive regarding ASIC-resistance.
If it is faster on a normal PC, it will perform better compared to a dedicated ASIC hardware.

The parameters for the "hardness" of the Argon2 function have been choose so it will take about 10 seconds to  perform the key derivation.

Here are the choosen parameters:

   const unsigned t_cost = 5;
   const unsigned m_cost = 100000;
   const unsigned thr = 8;


However, it is not too late to change if there is enough reason to do so.


I have to update the documentation, will be done in the next release.

Argon2 is a key derivation function that was selected as the winner of the Password Hashing Competition in July 2015. It was designed by Alex Biryukov, Daniel Dinu, and Dmitry Khovratovich from the University of Luxembourg. The reference implementation of Argon2 is released under a Creative Commons CC0 license (i.e. public domain) or the Apache License 2.0, and provides three related versions:

a) Argon2d maximizes resistance to GPU cracking attacks. It accesses the memory array in a password dependent order, which reduces the possibility of time–memory trade-off (TMTO) attacks, but introduces possible side-channel attacks.

b) Argon2i is optimized to resist side-channel attacks. It accesses the memory array in a password independent order.

c) Argon2id is a hybrid version. It follows the Argon2i approach for the first pass over memory and the Argon2d approach for subsequent passes. The Internet draft recommends using Argon2id except when there are reasons to prefer one of the other two modes.

Quoted and verified.

However, this gives me pause:

Could you also sign a message using one of your old addresses, like this one: 1ERHkyaSFUrmTr4pxK4a8GXrb9htADD876? 
It'll go a long way to prove your account hasn't been compromised or sold.



[Archive]
[Archive]

Does anybody know what happened with this project and its creator pointbiz?
Last time he was active only on July 2, 2018 (more than a year ago).