web: Fix bitcoin address.

Authored by marcus on May 31 2017, 6:48 PM.

Description

web: Fix bitcoin address.

Details

Committed
marcusMay 31 2017, 6:48 PM
Parents
rD6a8191df0adc: web: Fix checkout-se de and fr layout.
Branches
Unknown
Tags
Unknown
aa raised a concern with this commit.May 31 2017, 8:46 PM
aa added a subscriber: aa.

Hi Fellows,
Suggestion.
is it possible to use a vanity adress for donations ?
for instance.

Difficulty: 259627881
Pattern: 1GnuPG
Address: 1GnuPGAKtzA7fDE4UkKsM8Gjs1Y3FHGJG1
Privkey: 5J3SYaUa4Y74diSo2cPo9zKjLb6HiqM5WJv5aKpYubMYkyW7heU

So 1GnuPG would be the 'General address' for donations and we also could use 1GnuP{projectname} in case people want to donate for a specific sub-project of GnuPG ecosystem.

PS->If the project name is too long it is possible to "mining" a name in a pool.
More info on https://bitcointalk.org/index.php?topic=25804.0

Kind Regards,
--aa

This commit now has outstanding concerns.May 31 2017, 8:46 PM
werner added a subscriber: werner.Jun 1 2017, 9:59 AM

FWIW, due to organizational matters we won't be able to handle donation dedicated to a certain task.
What we will do is to consider suggestions on which subproject to prioritize.

marcus requested verification of this commit.Jun 2 2017, 2:05 PM

Thanks, good idea, but too late for this round. The devops to keep the wallet secure is annoying enough even without another program to generate a private key and importing it into bitcoin-qt (which can be done in the debug console).

This commit now requires verification by auditors.Jun 2 2017, 2:05 PM
marcus added an auditor: kai.Jun 2 2017, 2:06 PM
kai accepted this commit.Jun 2 2017, 2:07 PM
aa added a comment.Jun 2 2017, 8:11 PM

FWIW, due to organizational matters we won't be able to handle donation dedicated to a certain task.
What we will do is to consider suggestions on which subproject to prioritize.

Fair enough. I also agree that a certain level of centralization on Accountancy & Finance department is desirable.

aa added a comment.Jun 2 2017, 8:55 PM

Thanks, good idea, but too late for this round. The devops to keep the wallet secure is annoying enough even without another program to generate a private key and importing it into bitcoin-qt (which can be done in the debug console).

Yes I agree. Actually the topic was already beat to death in 2011 Keep your CPU Busy

May I ask two last questions (answer is opcional, just curiosity)
1 - How that key pair was seeded ? For Instance.

Vanitygen uses the OpenSSL random number generator. This is the same RNG used by bitcoin and a good number of HTTPS servers. It is regarded as well-scrutinized. On Linux, the RNG will be seeded from /dev/urandom. Guessing the private key of an address found by vanitygen will be no easier than guessing a private key created by bitcoin itself. Nonetheless, if you feel the default RNG is unable to provide numbers that are sufficiently difficult to guess, vanitygen can be directed to seed the RNG from an external file using the -s option.

2 - Why the last two digits diff ? did you type it manually ?

1 - How that key pair was seeded ? For Instance.

AFAIK, Marcus used the standard bitcoin-qt.

2 - Why the last two digits diff ? did you type it manually ?

I do not want to invest more time into bitcoin. Actually our bank has locked our Euro account due to the exchange of bitcoins. See the mailing list of the verein for details.

This commit no longer requires audit.Oct 27 2017, 9:34 AM