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

[BlueDragon747]

I'm back, the pool went offline because blakecoind crashed. I'm fixing it now and I will place an script to avoid this in the future. All the funds are safe and will be arriving to you very soon.
As this project is taking off, I will dedicate way more of my time than before to the pool so I should not be as offline as before.

Excellent   

[1713543281]

1713543281

[1713543281]

1713543281

[1713543281]

1713543281

[1713543281]

1713543281

[BlueDragon747]

ok I should have merged all the accounts and workers from eu1 into ny1 

[bzyzny]

I have started a thread here:
https://bitcointalk.org/index.php?topic=440990.0

It is for sharing and discussing promotional content for Blakecoin, such as icons, logos, fonts, charts, graphs, writings, etc. Anyone with graphic design experience, your help would be appreciated, since my skill with the Gimp/Photoshop is pretty limited.

Also, BlueDragon, I was hoping you would share with us any guidelines you had in mind. For example, do you have a specific font you wish to have associated with Blakecoin? Or can you provide a a hexadecimal # for the shades of blue and orange you wish to have associated with Blakecoin? Thanks

[BlueDragon747]

I have started a thread here:
https://bitcointalk.org/index.php?topic=440990.0

It is for sharing and discussing promotional content for Blakecoin, such as icons, logos, fonts, charts, graphs, writings, etc. Anyone with graphic design experience, your help would be appreciated, since my skill with the Gimp/Photoshop is pretty limited.

Also, BlueDragon, I was hoping you would share with us any guidelines you had in mind. For example, do you have a specific font you wish to have associated with Blakecoin? Or can you provide a a hexadecimal # for the shades of blue and orange you wish to have associated with Blakecoin? Thanks

cool 

not worried about the colours but I am using a custom font(free) called videopac which you may find useful www.dafont.com/videopac.font

I have all the PSD's for logo's etc I can upload them if you wanted?

[bzyzny]

not worried about the colours but I am using a custom font(free) called videopac which you may find useful www.dafont.com/videopac.font

I have all the PSD's for logo's etc I can upload them if you wanted?

thanks for the font, yes the PSD and other source files would be exactly the type of thing to post on the thread i started

[BlueDragon747]

not worried about the colours but I am using a custom font(free) called videopac which you may find useful www.dafont.com/videopac.font

I have all the PSD's for logo's etc I can upload them if you wanted?

thanks for the font, yes the PSD and other source files would be exactly the type of thing to post on the thread i started

if I find any other useful bits will upload and post 

[kr105]

What are the exchanges where this coin is currently listed on?

[Prelude63]

Happy lunar new year to those who are celebrating !! 

[BlueDragon747]

Happy lunar new year to those who are celebrating !!  

Happy Lunar New Year, I wish everyone good health and lasting prosperity  

[BlueDragon747]

What are the exchanges where this coin is currently listed on?

Atomic-Trade allows trading of Blakecoin
www.atomic-trade.com

OpenEx is in Maintenance for 2-3 weeks according to r3wt
https://bitcointalk.org/index.php?topic=437532

[Prelude63]

Happy lunar new year to those who are celebrating !! 

Happy Lunar New Year, I wish you good health and lasting prosperity 

Let's wish everyone here good health and lasting prosperity from Blakecoins!!! May Blakecoin blast to the moon as exchange trollbox always say ;-p

[BlueDragon747]

Good news everybody  

Blakecoin has just been listed on Crypto-Currency Exchange https://c-cex.com  
https://bitcointalk.org/index.php?topic=418700


Edit
BLC-USD
https://c-cex.com/index.html?p=blc-usd
BLC-BTC
https://c-cex.com/index.html?p=blc-btc

[Prelude63]

Good news everybody  

Blakecoin has just been listed on Crypto-Currency Exchange https://c-cex.com  
https://bitcointalk.org/index.php?topic=418700


Edit
BLC-USD
https://c-cex.com/index.html?p=blc-usd
BLC-BTC
https://c-cex.com/index.html?p=blc-btc

Congrats! A great start for the lunar new year!

[BlueDragon747]

My service provider is having some issues in one of the datacenters

Edit:
ok should be back to normal but will keep a close eye on it

[dreamwatcher]

I wanted to extend the olive branch and apologize to BlueDragon747 for the friction over merged mining and Blakecoin.

As I look back with a somewhat clearer head(as clear as it can be now     ), I realize that it would have never been possible using an unaltered MM proxy because of conflicting goals.

When I set out to relaunch Federation Credits, one of the main goals was an automatic redistribution of the coins on the original chain. I wanted coin holders to be able to simply place their old wallet files in the new UFC directory, salvage the wallet, and have their coins and addresses back on the new chain. This is also the reason for the 8 Million coin super block, it was redistributed in block 121 to all the same addresses and amounts the coins were on in the original chain.

Part of Blakecoin design was a change in the way keys are encoded. While in itself this is perfectly fine and adds more “Blakeness” to the coin, I could not use that system and have an easy coin redistribution .I had to change the key encoding back to sha256. Note: key encoding and block encoding are not the same thing, every coin I have seen up until now, uses sha256 key encoding regardless of the block encryption scheme.

When I first talked to Bluedragon747, I was not aware that the key encode had been changed or the repercussions it would have on the redistribution.

The second issues with versions. Just my policy. After repairing  coin clients and seeing it happen to others, I do everything I can to prevent crosstalk between different chains and incompatible client versions. In theory, all one needs to do is change the network identifier (prefix) and P2P port, but I have seen many strange things happen when nodes that should not be talking to each other start to. I use version numbers to further block out old clients/other chains, which was especially necessary in this case to make sure UFC 1.5.5 and lower were completely blocked from this chain. I was also using wallet version to facilitate an auto-detection and wallet salvage routine that did not turn out as planned.

I just want to end by stating the friction that occurred in previous posts was my fault. The amount of pressure I was under to fix a third coin of which I was not the original developer , but now am the developer, was taking its toll. The blockchain was completely POS locked and the new client had to be made and the new blockchain in place with redemption very quickly to avoid the coin dying out.

If we can see past this, I would be happy to work with Bluedragon747 on a merged mine solution, if he still wants to. If not, it is perfectly understandable.

[Jude Austin]

FPGA = awesome.

Will it work with the X6500s?

I have 3 of them laying around.

[BlueDragon747]

FPGA = awesome.

Will it work with the X6500s?

I have 3 of them laying around.

miner:
https://github.com/kramble/x6500-miner

the different fpga bitstreams/source for the supported boards:
https://github.com/kramble/FPGA-Blakecoin-Miner/tree/master/experimental

Thanks to kramble for his awesome work 

[Jude Austin]

FPGA = awesome.

Will it work with the X6500s?

I have 3 of them laying around.

https://github.com/kramble/x6500-miner

Ahh, thank you!

Off to mine some Blakecoin!

[BlueDragon747]

I wanted to extend the olive branch and apologize to BlueDragon747 for the friction over merged mining and Blakecoin.

As I look back with a somewhat clearer head(as clear as it can be now    ), I realize that it would have never been possible using an unaltered MM proxy because of conflicting goals.

When I set out to relaunch Federation Credits, one of the main goals was an automatic redistribution of the coins on the original chain. I wanted coin holders to be able to simply place their old wallet files in the new UFC directory, salvage the wallet, and have their coins and addresses back on the new chain. This is also the reason for the 8 Million coin super block, it was redistributed in block 121 to all the same addresses and amounts the coins were on in the original chain.

Part of Blakecoin design was a change in the way keys are encoded. While in itself this is perfectly fine and adds more “Blakeness” to the coin, I could not use that system and have an easy coin redistribution .I had to change the key encoding back to sha256. Note: key encoding and block encoding are not the same thing, every coin I have seen up until now, uses sha256 key encoding regardless of the block encryption scheme.

When I first talked to Bluedragon747, I was not aware that the key encode had been changed or the repercussions it would have on the redistribution.

The second issues with versions. Just my policy. After repairing  coin clients and seeing it happen to others, I do everything I can to prevent crosstalk between different chains and incompatible client versions. In theory, all one needs to do is change the network identifier (prefix) and P2P port, but I have seen many strange things happen when nodes that should not be talking to each other start to. I use version numbers to further block out old clients/other chains, which was especially necessary in this case to make sure UFC 1.5.5 and lower were completely blocked from this chain. I was also using wallet version to facilitate an auto-detection and wallet salvage routine that did not turn out as planned.

I just want to end by stating the friction that occurred in previous posts was my fault. The amount of pressure I was under to fix a third coin of which I was not the original developer , but now am the developer, was taking its toll. The blockchain was completely POS locked and the new client had to be made and the new blockchain in place with redemption very quickly to avoid the coin dying out.

If we can see past this, I would be happy to work with Bluedragon747 on a merged mine solution, if he still wants to. If not, it is perfectly understandable.

I can see past this issue as I do value the fans/miners of our coins and it is not worth splitting the hashing power over this misunderstanding  

Some more work will be needed and we will have less examples to work from but its far from impossible, the most important bit is that the mining is not changed so the work share from the miner is valid on both chains but the pool side has more issues and we will need a new MM proxy that acts as the submitter to the other chains and logs shares in the DB

possibly the best way would be to use the python miner from kramble's fpga miner based on work by teknohog and pass the nonce and do something like this for each chain? https://github.com/kramble/FPGA-Blakecoin-Miner/blob/master/MiningSoftware/blakeminer.py#L168

I can think of a few ways to do this, another example is to have a second eloipool with different name space and submit the share to second pool but this will only scale so far and could get messy resource wise?

maybe you have some ideas too?

we will also need to mod MPOS for multi Blake-256 based coins as it is currently not designed that way

Happy to work together, merge mining Blake-256 coins is a winning combo for everyone    


 

[boymok]

Or he can better join Blakecoin!