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

[bzyzny]

i edited my earlier post about the Blakecoin wallet I compiled for linux, please re-download if are using it. next, i will compile a 64bit binary with the same updates, and then i plan to figure out how to make them into .deb and .rpm files. installing the wallet should be simple on linux

https://bitcointalk.org/index.php?topic=306894.msg9243282#msg9243282

[1715550623]

1715550623

[1715550623]

1715550623

[1715550623]

1715550623

[1715550623]

1715550623

[1715550623]

1715550623

[bzyzny]

Announcing a beta (work in progress) wiki site for the Blake Ecosystem! 
read about and discuss it here:
http://blakecrypto.com/forums/topic/blake-wiki-beta-blcwiki-org/

or go directly there:
http://blcwiki.org

[cinnamon_carter]

thanks for the updates , would it be possible for you to fork blake coin on github and upload your changes to source
if you have time ??

Felt like it was time to recompile Blakecoin wallet for linux. This is a 32bit binary. I made a few slight changes from the github code:

- updated openssl to 1.0.1j - this patches POODLE vulnerability
- updated copyright date to 2014
- enabled QR code support, and changed it from generating "bitcoin:(addr)" to "blakecoin:(addr)", adjusted window dimension so "blakecoin:(addr)" fits on one line
- changed the splash screen
- compiled with most recent leveldb
- compiled with gcc executable hardening settings
- changed the about page
- incremented to 0.8.9.1 (small number for builds)

Download archive here (includes binary and source):
http://www.mediafire.com/download/6pewsybe4wsz9ur/Blakecoin-QT-Linux-i386-0.8.9.1-beta.tar.gz

if you are on 64bit linux, you can run this 32bit wallet by installing i386 versions of the dependency libraries. i will probably end up building it for x64 binary as well, since that would be much easier.

update: i compiled a new one since i missed a few details - link is updated

[Sravas]

Does merged mining working or not?
Particularly on NY2 pool?

[BlueDragon747]

Does merged mining working or not?
Particularly on NY2 pool?

it does but been getting quite a few issues with eu3/ny2 past week  

from mmp log on ny2:
2014-10-22T13:15:01.334915,solve,=,1,0,1,1,1,1,ae0f14578486515db370c80868cd12bc1cdc5cbdc585263fce7e060000000000
2014-10-22T13:15:02.377039,solve,=,0,0,0,0,0,0,8351d2a382e5318c136ffa3d7eb0fe13c39496a883512c3f54010f0000000000
2014-10-22T13:15:04.457952,solve,=,0,0,0,0,0,0,2ce0c327105b9ea7b3edb8248fdbc2c0d26af6b32f2a77a36f4b160000000000
2014-10-22T13:15:18.456138,solve,=,0,1,0,0,0,0,e301a9178ad47bb3a07ba2912e4c2d54e195d65bce262910c4e4030000000000
2014-10-22T13:15:34.257466,solve,=,0,0,0,0,0,0,6100fc53bae032b42899929d55f9618ec9a16f461732c27f45bbc80000000000

[BlueDragon747]

thanks for the updates , would it be possible for you to fork blake coin on github and upload your changes to source
if you have time ??

Felt like it was time to recompile Blakecoin wallet for linux. This is a 32bit binary. I made a few slight changes from the github code:

- updated openssl to 1.0.1j - this patches POODLE vulnerability
- updated copyright date to 2014
- enabled QR code support, and changed it from generating "bitcoin:(addr)" to "blakecoin:(addr)", adjusted window dimension so "blakecoin:(addr)" fits on one line
- changed the splash screen
- compiled with most recent leveldb
- compiled with gcc executable hardening settings
- changed the about page
- incremented to 0.8.9.1 (small number for builds)

Download archive here (includes binary and source):
http://www.mediafire.com/download/6pewsybe4wsz9ur/Blakecoin-QT-Linux-i386-0.8.9.1-beta.tar.gz

if you are on 64bit linux, you can run this 32bit wallet by installing i386 versions of the dependency libraries. i will probably end up building it for x64 binary as well, since that would be much easier.

update: i compiled a new one since i missed a few details - link is updated

yes that would be good can merge changes no problem or you can also email them too me if that is easier  

[bzyzny]

im not really familiar with using github beyond downloading code from it, but i can learn how to fork it if that would make things easier here. most of it was just compilation options and only a few changes to the source. The altered source is in the archive i uploaded.  First, I replaced the leveldb folder with the current version from https://github.com/google/leveldb and also updated the qrencode folder with the current version from http://fukuchi.org/works/qrencode/. I made only a few minor changes to the Blakecoin source files, I suppose you could diff them to find the changes.

[photon_coin]

The advantage for you of forking the repo and posting (even the minor) changes you made to the source code is if Bluedragon747 uses them you get 'official credit' as someone who contributed something important to the project. Your 'commit' when 'merged' will rightfully acknowledge 'you' as the person who suggested those changes. You will be forever acknowledged to the world as a contributor to Blake Coin.
Even if the changes are small as an open source project you deserve to get credit for your contributions.

If you like & have time do a gitpull with the changes to src/qt to show Photon instead of Bitcoin to the Photon source code. Once tested I will also merge your work.

If Bluedragon & I author these changes it looks to the world like we wrote them.
I always prefer to give credit when possible.

For dependencies did you use qrencode 3.4.3 ?
I would be curious to see the changes you made to the .pro file.

If you are busy and don't have time it's cool too / Thanks for helping out !!

im not really familiar with using github beyond downloading code from it, but i can learn how to fork it if that would make things easier here. most of it was just compilation options and only a few changes to the source. The altered source is in the archive i uploaded.  First, I replaced the leveldb folder with the current version from https://github.com/google/leveldb and also updated the qrencode folder with the current version from http://fukuchi.org/works/qrencode/. I made only a few minor changes to the Blakecoin source files, I suppose you could diff them to find the changes.

[bzyzny]

ok, ill try out forking it on github when i get a chance, but mainly just for the sake of learning - i dont care about taking credit for this. you can look at the .pro file its in the archive; if i recall right all i did was remove the lines that where specific for windows where it specifies the lib dirs and libboost suffix. i used qrencode 3.4.4 which is the current release

[BlueDragon747]

ok, ill try out forking it on github when i get a chance, but mainly just for the sake of learning - i dont care about taking credit for this. you can look at the .pro file its in the archive; if i recall right all i did was remove the lines that where specific for windows where it specifies the lib dirs and libboost suffix. i used qrencode 3.4.4 which is the current release

I am merging some of the changes but did find a bug with the new leveldb sub version 18 it does not compile on windows so have just used sub version 17 like bitcoin core for now as it does not have same issue  

I am also working on porting to 9.3 code base but need to setup a new dev environment to compile it  

Edit:
Updated Github with most of the merged changes and a couple of bug fixes

[bzyzny]

Thanks BD, i look forward to the updated wallet. will have to look at some change logs to see whats new in v. 9.3. one question, i was unclear about when poking thru the source. in the makefile.unix there is this line
HARDENING=-fno-stack-protector
The comment for this says it is a work around for a bug, but when i looked up the bug it appears it has been fixed years ago. so would it be better to comment out the above line?

edit: BD, I also just noticed in your current blakecoin github, you have my edit that changes the text color of the splash screen to white, but have the original splash.png which is itself white (so the text will be invisible). I changed it to white since the custom splash.png i had used is a darker blue.  you can change the text color on line 38 of splashscreen.cpp

[BlueDragon747]

Thanks BD, i look forward to the updated wallet. will have to look at some change logs to see whats new in v. 9.3. one question, i was unclear about when poking thru the source. in the makefile.unix there is this line
HARDENING=-fno-stack-protector
The comment for this says it is a work around for a bug, but when i looked up the bug it appears it has been fixed years ago. so would it be better to comment out the above line?

yes you can comment it if you want as like you said its been patched in most newer distro's anyway

[BlueDragon747]

Blakecoin 0.8.9.2 for Windows

Built with static dependencies and QR code support

Built with:
Boost 1.55
OpenSSL 1.0.1j
Qrencode 3.4.4
Libpng 1.6.12

https://github.com/BlueDragon747/Blakecoin/releases/tag/v0.8.9.2

[bzyzny]

A note for anyone trying to compile the wallet on Ubuntu (and probably any derivatives) with openssl 1.0.1j - ubuntu repositories currently only have 1.0.1f so you will have to get the 1.0.1j deb files from the debian sid repository and install them manually. Hopefully the ubuntu repositories will update to libssl 1.0.1j  soon. I only mention this because the 1.0.1j update is important since it fixes a severe security bug.

[BlueDragon747]

A note for anyone trying to compile the wallet on Ubuntu (and probably any derivatives) with openssl 1.0.1j - ubuntu repositories currently only have 1.0.1f so you will have to get the 1.0.1j deb files from the debian sid repository and install them manually. Hopefully the ubuntu repositories will update to libssl 1.0.1j  soon. I only mention this because the 1.0.1j update is important since it fixes a severe security bug.

easy to fix

Code:

wget https://www.openssl.org/source/openssl-1.0.1j.tar.gz
tar -xvzf openssl-1.0.1j.tar.gz
cd openssl-1.0.1j
./config --prefix=/usr/lib/ssl --openssldir=/usr/lib/ssl
make
make install

Code:

sudo ln -sf /usr/lib/ssl/bin/openssl `which openssl`

make sure its in your path

Code:

nano /root/.bashrc
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/lib/ssl:/usr/lib/ssl/bin

check version

Code:

openssl version -a

should get a result like this:

Code:

OpenSSL 1.0.1j 15 Oct 2014
built on: Wed Oct 22 17:58:50 UTC 2014
platform: linux-x86_64
options:  bn(64,64) rc4(16x,int) des(idx,cisc,16,int) idea(int) blowfish(idx)
compiler: gcc -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -DTERMIO -O3 -Wall -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM
OPENSSLDIR: "/usr/lib/ssl"

[BlueDragon747]

LA1 is down atm in contact with service provider hope to have it back online soon  

Edit:
got a reply having LA1 moved to a different server with more resources should be back to normal when thats done  

Edit2:
LA1 is back online 

[laitec]

No Asik. This will kill the algorithm.

[BlueDragon747]

No Asik. This will kill the algorithm.

Proof?

it costs so much to make an Asic it makes no sense with the current market capitalization of even all the merge coins combined to produce a custom 8 round Blake-256 Asic yet

the only Asic that has been made was for the 14 round version for the SHA-3 competition which is not used in Blakecoin or the merged coins  

as proven by both SHA-256D and Scrypt if an algorithm becomes popular and the market value exceeds the cost to produce then an Asic is most likely going to be produced no matter what you do!

atm only GPU/FPGA are practical for mining the 8 round Blake-256 used by Blakecoin and the merged coins but if one day it made sense to make Asic's then it would be smaller in silicon and cheaper to produce in volume which should make the mining devices cheap to buy and use less watt/hash than SHA-256D if built on same nano-meter process

Asic = Application-specific integrated circuit

most technology gets an Asic if widely used like: the chip and pin system for bank cards, a network card for your pc, a home router used for internet connection or most of the chips inside your mobile phone!  

[bzyzny]

an 8 round blake256 asic would produce very fast hash rate with very little electricity. this would be a good thing, more network security and less energy consumption. personally i cant wait for blake asics

[bzyzny]

as promised, here is the current Blakecoin Wallet compiled for 64bit Linux (tested on ubuntu). You will need to install dependencies if you havent already. next I will make an ubuntu PPA so that you can install the blake family wallets thru apt-get/synaptic and have the dependencies installed automatically.

https://www.mediafire.com/?pox6154n66a8w66