Forum Replies Created
-
Posts
-
no spam please
http://blakecrypto.com/project-funding/
donate amount in box add to cart and go to checkout it will give you an address and automatically check payment status
released a minor update for 0.8.9.4 electron wallet
https://github.com/Electron-Coin2014/Electron-ELT/releases/tag/0.8.9.4b
I released a new version 0.8.9.4 with minor updates and using openssl 1.0.2a
https://github.com/BlakeBitcoin/BlakeBitcoin/releases
not had spare time for any new coin releases so they are on hold atm, also been doing some bits on moving to 10.x code base but again need to get some game stuff released before I have spare time to finish testing and bug hunting
I released a new version 0.8.9.4 with minor updates and using openssl 1.0.2a
hehe 🙂
trying to get some balance ingame with some female zombies 😉
It could use any web technology I guess
here is the bountysource repo
https://github.com/bountysourceBCS is holding 24k BLC for this project bounty Now
I released a new version 0.8.9.3 with CoinControl
https://github.com/lithiumcoin/lithium/releases/tag/0.8.9.3this is useful for people that either send large transactions or have a lot of small inputs which has been known to create sending issues “Transaction To Large”, with coincontrol you can consolidate these inputs, set a custom change address, or lock inputs on an address if for some reason you dont want them to move from that address and I also added mininput again so you can define a set minimum input that gets used for creating transactions
I released a new version 0.8.9.3 with CoinControl
https://github.com/Electron-Coin2014/Electron-ELT/releases/tag/0.8.9.3this is useful for people that either send large transactions or have a lot of small inputs which has been known to create sending issues “Transaction To Large”, with coincontrol you can consolidate these inputs, set a custom change address, or lock inputs on an address if for some reason you dont want them to move from that address and I also added mininput again so you can define a set minimum input that gets used for creating transactions
I released a new version 0.8.9.3 with CoinControl
https://github.com/BlakeBitcoin/BlakeBitcoin/releases/tag/0.8.9.3this is useful for people that either send large transactions or have a lot of small inputs which has been known to create sending issues “Transaction To Large”, with coincontrol you can consolidate these inputs, set a custom change address, or lock inputs on an address if for some reason you dont want them to move from that address and I also added mininput again so you can define a set minimum input that gets used for creating transactions
often coincontrol is seen with PoS coins so you might see one of those joining the merge mine pools soon 😉
I released a new version 0.8.9.3 with CoinControl
https://github.com/BlueDragon747/Blakecoin/releases/tag/0.8.9.3this is useful for people that either send large transactions or have a lot of small inputs which has been known to create sending issues “Transaction To Large”, with coincontrol you can consolidate these inputs, set a custom change address, or lock inputs on an address if for some reason you dont want them to move from that address and I also added mininput again so you can define a set minimum input that gets used for creating transactions
often coincontrol is seen with PoS coins so you might see one of those joining the merge mine pools soon 😉
qt is not including the dll when building the wallet so it either needs more rules added to build or the qt needs building with some extra flags so that it is included
easy option is to just include the extra dll but both me and cinnamon have been trying to get it fully static build without any extra dll on win7/win8
only thing I did not like about the final candidate was that the security margin seem far too conservative and wasteful as really they seemed to be trying to gain the judges favor by making some changes based on the criticism that Blake was too fast
when working with FPGA the previous 10 round submission was far more practical to implement with the design tools, for Blakecoin I used a 8 round Blake-256 variant and at the time of working on it estimated a best attack of about 2^192
I was very happy to see this paper that shows a best attack against 8 rounds of 2^200 which is better than I had originally thought and more than adequate for how we are using it in the wallet and mining http://eprint.iacr.org/2013/852.pdf
a 40% improvement in efficiency, latency or area has turned out to be a good trade off and its still 2^256 for bruteforce and if you look at the whole round function due to its parallel nature 8 rounds is actually 64 G function calls which which could be compared with SHA-256 which normally uses 64 rounds in a linear fashion so 8 round Blake was another very cool way to do things 😛
for the asic paper they only compare against a single SHA-256 but Bitcoin uses a length-extension defense “SHA-256d” design by Ferguson and Schneier. SHA256d(x) = SHA256(SHA256(x)) therefore in silicon SHA-256d has either twice the latency or twice the area depending on the design vs a single SHA-256
Excellent keep up the good work it is appreciated 😀
