[ANN][BLC] Blakecoin Blake-256 for GPU/FPGA With Merged Mined Pools Stable Net

[Ignatius]

And as a little present to the BlakeCoin community (it's a crude hack, see the README).
https://github.com/kramble/FPGA-Blakecoin-Miner/tree/master/vanitygen

Thank you for this. I actually took a brief look at the source before and failed to get a blake version going. If you have extra time and find the desire, please create a blc brainwallet program.

Code:

$ ./vanitygen -F compressed -X 26 BT
Difficulty: 109
Pattern: BT
Address: BTruFNfT29KuMraSmgGBP7hbeJRRXmpCqs
Privkey: L12wp3ze5HZwRh8j1sAZUxHGGPszZbecPhPWK13x5XJnq2qPkpkN

$ ./vanitygen -F compressed -X 26 BTBLC
Prefix 'BTBLC' not possible
Hint: valid bitcoin addresses begin with "1"

$ ./vanitygen -F compressed -i -X 26 Bs
Difficulty: 185
Pattern: Bs
Address: Bs19E1xnhrb3yUp2D6fveWf1VXoHiDmoux
Privkey: KysJgiYgJj6L7yj11vmx79TfbqepyCCz7Z569u73eSWRzfYp71gP

$ ./vanitygen -F compressed -X 26 Bsa
Prefix 'Bsa' not possible
Hint: valid bitcoin addresses begin with "1"

$ ./vanitygen -F compressed -X 26 Bsb
Prefix 'Bsb' not possible
Hint: valid bitcoin addresses begin with "1"

$ ./vanitygen -F compressed -i -X 26 Bsc
Prefix 'Bsc' not possible
Hint: valid bitcoin addresses begin with "1"

$ ./vanitygen -F compressed -i -X 26 Bsd
Prefix 'Bsd' not possible
Hint: valid bitcoin addresses begin with "1"

I can't seem to generate addresses, likely due to my lack of understanding of required blc prefixes.

Edit: Yes this works, thanks & sorry.

Ah, maybe my comment in the README was a bit confusing. I said the valid range was BT to Bs (I worked this out by trial and error), but only part of BT and part of Bs are usable. You can generate any address from BU, BV, BW, BX, BY, BZ and Ba, Bb, Bc to Bq, Br (excluding Bl since lowercase l is not part of the base58 character set). For example I've been running:
./vanitygen -F compressed -X 26 -ik -o outkram.txt bkram

[bzyzny]

With merged mining being a primary goal here, I was wondering if anyone capable of doing so would be willing to implement this idea. It Would be helpful to have a multicoin wallet for the merged mineable coins. Perhaps using electrum as a base since that would also remove the need to download the block chains for every coin. Any thoughts on this suggestion?

[kramble]

I can't seem to generate addresses, likely due to my lack of understanding of required blc prefixes.

Ah, maybe my comment in the README was a bit confusing. I said the valid range was BT to Bs (I worked this out by trial and error), but only part of BT and part of Bs are usable. You can generate any address from BU, BV, BW, BX, BY, BZ and Ba, Bb, Bc to Bq, Br (excluding Bl since lowercase l is not part of the base58 character set). For example I've been running:
./vanitygen -F compressed -X 26 -ik -o outkram.txt bkram

Brainwallet is easy. I have a python script that I can trivially modify to do that. I'll sort something out tomorrow (its getting late here). Doing it in C will be a bit more difficult (and a web version is quite beyond my ability, sorry). Not that I'd recommend brainwallets, they are really very dangerous unless you know exactly what you are doing.

[BlueDragon747]

And as a little present to the BlakeCoin community (it's a crude hack, see the README).
https://github.com/kramble/FPGA-Blakecoin-Miner/tree/master/vanitygen

Awesome looks cool  

[kramble]

Awesome looks cool  

Thanks. I was just curious as to why the original vanitygen did not work for blake with the -X 26 version byte. It was just a matter of using blake hash instead of sha256d for the base58 checksum, plus a change to the privkey version byte. Also using compressed rather than uncompressed addresses, hence the fork from WyseNynja rather then samr7's original.

Anyway I've just updated the github (it's slightly less of a horrible hack now, the previous version completely broke vanitygen for anything other than -X26 blakecoin). I've also put up my blake brainwallet python script for Ignatius. It's based on JackJack's pywallet and is very helpful for understanding the address generation process (which is why I wrote it way back for bitcoin).

[Ignatius]

I've also put up my blake brainwallet python script for Ignatius. It's based on JackJack's pywallet and is very helpful for understanding the address generation process (which is why I wrote it way back for bitcoin).

It works great, thank you!

Any links to information that explains your stance on brainwallets being very dangerous? I wonder if there is something I need to be aware of besides the need for an extremely strong passphrase.

Donation sent to your BLC address. Thank you for all of your effort.

[kramble]

It works great, thank you!
Donation sent to your BLC address. Thank you for all of your effort.

Many thanks

Any links to information that explains your stance on brainwallets being very dangerous? I wonder if there is something I need to be aware of besides the need for an extremely strong passphrase.

Just some threads I recall reading some months back. The problem is more acute with bitcoin but it's worth bearing in mind for blakecoin too. Some crooks have built enormous rainbow tables of brainwallet addresses and are monitoring the blockchain just waiting for these addresses to appear, then instantly sweep the coin into their own accounts. So using any simple combination of words, or a well known phrase (say from a book, or song lyrics), risks losing your coin. It's a big risk for novices, less so if you know what you are doing and select a good passphrase (though there is the matter of "entropy", which basically says you need a long passphrase to match the security of the 160 bit address hash).

Googling "brainwallet security" (without the quotes) brings up some good links. This is a good discussion.

[Ignatius]

Just some threads I recall reading some months back. The problem is more acute with bitcoin but it's worth bearing in mind for blakecoin too. Some crooks have built enormous rainbow tables of brainwallet addresses and are monitoring the blockchain just waiting for these addresses to appear, then instantly sweep the coin into their own accounts. So using any simple combination of words, or a well known phrase (say from a book, or song lyrics), risks losing your coin. It's a big risk for novices, less so if you know what you are doing and select a good passphrase (though there is the matter of "entropy", which basically says you need a long passphrase to match the security of the 160 bit address hash).

Googling "brainwallet security" (without the quotes) brings up some good links. This is a good discussion.

Ok I will definitely keep that in mind. This was also an interesting read:

Just lost 4 BTC out of a hacked brain wallet. The pass phrase was a line from an obscure poem in Afrikaans. Somebody out there has a really comprehensive dictionary attack program running.
http://www.reddit.com/r/Bitcoin/comments/1ptuf3/brain_wallet_disaster/

[kramble]

I have a couple DE0-Nano boards that aren't doing anything at the moment. Would you upload the code to github?

I've just updated the github and uploaded a bitstream, see the README.

The verilog is fine (in fact the bistream is the same as the one I compiled back in October). The problem was due to the TCL script not coping with the getwork pool sending 129 bytes rather than the 128 bytes expected, there being an additional byte of data after the nonce field. Interestingly this extra byte (6B) together with the nonce (35303152) spell K105r (the author of the pool software).

Another interesting bug is that the pool sends a block header version byte 2, compare 114 (0x70) for solo mined blocks (this can be easily verified with the blockexplorer, most of the recent blocks being version 2, while the early ones are version 114). Not that it affects the miner, but it does make the blockchain a bit untidy.

Anyway, the DE0-Nano is not going to be of much use as a miner (just 5 MHash/sec or so), but the code may be of use for porting to other Altera devices, though it would be better to use the LX150 code as a base for the larger ones.

[backdogs]

looks great,both CPU and GPU?

[mogrith]

looks great,both CPU and GPU?

Yes and many FPGAs also

[c-cex]

https://c-cex.com exchange moved to much faster servers.
We can now handle 10x times more online users! Welcome!

[Calhil]

It seems there are very good news for non-scrypt based coins today:
https://www.kncminer.com/products/titan - 100MH/s scrypt miner for 10k$
Guess whats going to happen when they start shipping 

[kramble]

Since I've been looking at addresses, I've had a go at modifying JackJack's pywallet for blakecoin

https://github.com/kramble/FPGA-Blakecoin-Miner/tree/master/blake_pywallet

You need to run it with --otherversion=26 --datadir /home/user/.blakecoin (on linux)

It seems to work ok for dumping an unencrypted wallet on the command line, but running via the web interface it displays the addresses incorrectly (it looks like it's using the bitcoin version byte instead) oops, my bad, the version needs to be entered onto the web form as well as the command line.

[bzyzny]

hey kramble, i was trying out your blc vanitygen. im a bit unclear about which characters and prefixes are possible. also the program gives an error that valid bitcoin address must start with 1, unless i run the command with -r. any suggestions? also is there a way to have vanitygen give me an estimated time or # tries until completion? thx

[Ignatius]

hey kramble, i was trying out your blc vanitygen. im a bit unclear about which characters and prefixes are possible. also the program gives an error that valid bitcoin address must start with 1, unless i run the command with -r. any suggestions? also is there a way to have vanitygen give me an estimated time or # tries until completion? thx

Ah, maybe my comment in the README was a bit confusing. I said the valid range was BT to Bs (I worked this out by trial and error), but only part of BT and part of Bs are usable. You can generate any address from BU, BV, BW, BX, BY, BZ and Ba, Bb, Bc to Bq, Br (excluding Bl since lowercase l is not part of the base58 character set). For example I've been running:
./vanitygen -F compressed -X 26 -ik -o outkram.txt bkram

[kramble]

hey kramble, i was trying out your blc vanitygen. im a bit unclear about which characters and prefixes are possible. also the program gives an error that valid bitcoin address must start with 1, unless i run the command with -r. any suggestions?

Thanks for the bug report. I've updated the hint so it now gives the correct range for blakecoin when run with -X26. The valid range is discussed in the README, so it's always a good idea to read this in case of difficulty (RTFM as they say )

Also is there a way to have vanitygen give me an estimated time or # tries until completion? thx

Others have commented on the lack of usefulness of the vanitygen progress messages, unfortunately this sort of change is rather beyond my level of expertise, so perhaps you can take it up with the original author?
https://bitcointalk.org/index.php?topic=25804.0
https://github.com/samr7/vanitygen

This is probably as far as I'm going to go with the blake version of vanitygen, but if someone wants to create a windows executable, or even better an OCL version, then that would be quite helpful.

EDIT: Reading through the recent posts on the vanitygen thread, it seems that Red Emerald has taken over support for vanitygen (my blake version is forked from his/her github repo, so should be up-to-date).

[bzyzny]

Thanks Kramble, I got the vanitygen to work, luckily my username here is a valid prefix, check my sig below

[lin0sspice]

I just got the Cairnsmore1 from a friend.
Please help me to run it on Blake-256 ?

https://en.bitcoin.it/wiki/CM1Quickstart

Which controller bitstream did your friend have loaded?

Blake bitstreams are located here: https://github.com/kramble/FPGA-Blakecoin-Miner/tree/master/experimental/CM1

I have no idea.
I try to got hashvoodoo_controller , but i dont know how.
I try to use Virtual Box program.
I also just got Xlinix cable program.
Any help to pre-program it please.

[lin0sspice]

Found it Finally.
(same folder )
c:/Controller/SPIProg.exe hashvoodoo_dynamic_09_23_2012.bit