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

[BlueDragon747]

"It is unfortunate that it appears we are incompatible working together as developers."

could have something to do with not working with me and doing your own incompatible thing on your own, the only contact you gave me was to tell me your are going to use Blake, I did ask in a friendly and polite way to look into merge mining to avoid this exact issue regarding the merge mining proxy but you never replied  

you just purposely changed stuff like protocol version/address knowing full well this is in the headers and would effect mining

"I certainly was not just going to clone Blakecoin and slap the Federation Credit name on it"

but you did you even left this block height check in which is not needed for a new coin:
https://github.com/scificryptocoin/Federation-Credits/blob/master/src/main.cpp#L1170

you are welcome to re-write the pool software and merge mine proxy to make it compatible its quite a bit of work  

that proxy does work with namecoin et al. so very few changes needed if any, as proof of concept I will write a coin that is both merge able using the proxy and not a exact clone, at the very least this will create a base for people to use, it will also show the range of changes that can be done without touching the protocol versions (headers) and the address (blake-256) in fact most scrypt based coins show the range of different reward structures you can have without changing these things!

I am not upset you are welcome to do your own thing, I am just deeply disappointed in both your actions and attitude

 

[BlueDragon747]

You know what, forget it. I was looking forward to working with you and maybe even making some improvements to the concept of merged mining. However, since you are getting upset about not being able to use some pre-built proxy that I am not even sure would work without modification anyway, I am going to wish you the best of luck. I hope you find somebody who is willing to make an exact clone and change the name only as it appears that is what you are looking for.

No-hard feelings, and I hope Blakecoin will become a big success. It is unfortunate that it appears we are incompatible working together as developers.

Maybe not my place to butt in here, but for the sake of fostering cooperation and a friendly community, i wish to comment. If you feel we must agree to disagree, so be it, but hopefully there is room to discuss things further before jumping to that conclusion. I'm sure BlueDragon did not intend to come across as overly critical about your methods. Please consider discussing more details so we can try to find solutions that work for all of us.
I'm not sure of the technical details involved with merged mining and pool proxies, etc. however my understanding is that merged mining does not equate to cloning. Correct me if im wrong, but would not the ancillary coin have the freedom to differ from the primary coin? If you consider Blakecoin to be the primary blockchain, then the merge mined coin(s) would use the primary blockchains proof of work as input to generate its own blockchain. They are separate coins entirely, only sharing hashing resources to reduce duplicate effort. As for the pool software (or any other coin related tools), i'm sure there may be a current way to ensure compatibility, but theres also always room for improvement. Obviously it would be ideal to have standardization of interfaces to allow for broad interoperability, but the issue is making an api or platform that provides the flexibility to permit differences between the blake-based coins.

Anyways I could be totally wrong about all that but my main point is simply that working together can be difficult since people can have vastly different opinions, but it's worth giving it a shot at seeing if at least some things can be agreed on, and thats something each of us has to participate in.

I am all for working together as a team or helping out a developer or even doing some beta tests but it does require cooperation and communication which has been lacking here with dreamwatcher and this is a good example of the end result.  

It also happened in the Apollo program with the CO2 scrubbers and almost cost the crew of Apollo 13 their lives but the fix was a messy hack with duct tape and plastic bags, something I would like to avoid with the pool software

with the merge mining and eloipool/merge mine proxy, it treats each coin base separately and generates the merkle for each but as I said the proxy reuses many functions in the pool that have been modified for Blakecoin hence the compatibility issues as far as I understand it from working with the pool software

changing the protocol versions and address generation will ensure incompatibility with the pool software without some re-writes, if you want a coin to have a different network you only need to change the magic number to have a different broadcast address for your network/wallet  

I have a new pool up and working in New York so will spend some time this weekend working on merge mining coin and general stability of the pool software  

[BlueDragon747]

BLC on Atomic-Trade Promo

List:
BlueDragon747: 1000 BLC
Donations:         383 BLC
MikuCoin:           350 BLC
mogrith:            217 BLC
kramble:            200 BLC
Donations:         249.99 BLC
bzyzny:             500 BLC
hal7:                 386 BLC
Donations:          200 BLC
Donations:          468.27 BLC
Ignatius:            100 BLC

              Total: 3854.26 BLC

[Ignatius]

BLC on Atomic-Trade Promo

List:
BlueDragon747: 1000 BLC
Donations:         383 BLC
MikuCoin:           350 BLC
mogrith:            217 BLC
kramble:            200 BLC
Donations:         249.99 BLC
bzyzny:             500 BLC
hal7:                 386 BLC
Donations:          200 BLC
Donations:          468.27 BLC

              Total: 3754.26 BLC

100BLC sent, http://blakexplorer.dyndns.org:2750/tx/c469a8a43bc95487d9e94f27891beb838277fc33304fb54baead430b6a1422bf#o0

[ByronP]

BLC has been tested and synced... Will go live shortly :-)

[BlueDragon747]

BLC has been tested and synced... Will go live shortly :-)

Awesome thanks ByronP

I sent the donations to the address you sent me 

[bzyzny]

I am considering launching a wiki for Blakecoin. To start I will find a free wiki host to run it from, and if needed, set up a dedicated server later. Does any one have suggestions for which wiki host service to use, or what wiki platform to run if self-hosted? I was considering wikispaces.com or nginx+PmWiki (PHP). Any input is appreciated, thanks.

[ByronP]

BLC Blakecoin now active

[bzyzny]

BLC Blakecoin now active

Awesome, it's great to see Blakecoin on another exchange, even if it is another new one. It looks a lot more professional than the other one, hopefully it is more secure too (although to their credit, openex seems to have made some improvements). I'm real interested in seeing how you roll out USD support, since it would be the first (to my knowledge) to support depositing/withdrawing USD to buy/sell LTC and other alts in the USA.

[rupy]

Pool eu1.blakecoin.com is down!

Do we have any other working pools?

[bzyzny]

I took a few minutes to make these images for people to use for anything Blakecoin related.

[MikuCoin]

Pool eu1.blakecoin.com is down!

Do we have any other working pools?

You can try to solo mine it.

[rupy]

Pool eu1.blakecoin.com is down!

Do we have any other working pools?

You can try to solo mine it.

Now I am, good thing I don't have to wait two years to see if it works like BTC, should have a block soon with 1.6GH...

[BlueDragon747]

I am working on fixing this share bug issue on the pool and have another in New York but I am testing new code on that and is not suitable to have people mining while I am working on it, kr105 is still away so the eu pool is only public pool atm

[kramble]

Pool eu1.blakecoin.com is down!

Do we have any other working pools?

You can try to solo mine it.

You can configure cgminer to failover to solo mining ...

./cgminer -T --cainsmore-clock 195 --icarus-timing 1.0=20 -S /dev/ttyUSB0 --verbose --url stratum+tcp://eu1.blakecoin.com:3334 --userpass username.worker:password --failover-only --url localhost:8772 --userpass username:password 2>log.txt

[BlueDragon747]

Pool eu1.blakecoin.com is down!

Do we have any other working pools?

You can try to solo mine it.

You can configure cgminer to failover to solo mining ...

./cgminer -T --cainsmore-clock 195 --icarus-timing 1.0=20 -S /dev/ttyUSB0 --verbose --url stratum+tcp://eu1.blakecoin.com:3334 --userpass username.worker:password --failover-only --url localhost:8772 --userpass username:password 2>log.txt

cool that is useful thanks kramble

my cgminer.conf now looks like this:

Code:

{
"pools" : [
	{
	        "url" : "stratum+tcp://eu1.blakecoin.com:3334",
		"user" : "UserName.Worker",
		"pass" : "WorkerPass"
        },
        {
		"url" : "127.0.0.1:8772",
		"user" : Walletuser",
		"pass" : "Walletuserpass"
	}
],

"intensity" : "10",
"auto-gpu" : true,
"expiry" : "120",
"failover-only" : true,
"gpu-threads" : "2",
"log" : "5",
"no-restart" : true,
"queue" : "3",
"scan-time" : "30",
"worksize" : "128",
"temp-hysteresis" : "4",
"blake256" : true,
"vectors" : "1",
"failover-only" : true,
"kernel-path" : "/"
}

if it was pool 1 and pool 2 you can also add:

Code:

"no-submit-stale" : true,

but not recommended for solo or mix pool/solo

still can't get hold of kr105 I assume he is working away from home atm, I will release another server for next weekend

Edit:
updated the EU pool code to match latest I am testing on the New York server

[MikuCoin]

we need more trading volume on AT

[rupy]

Found my first solo mining crypto currency block ever at 5:13 this morning! I like it!

Does anyone know how much bandwidth the wallet consumes?

Will "no-submit-stale" remove all the "Share below target" in the log?

Generally is there another "better" way to solo mine than JSON RPC over HTTP with the blakecoin-qt?

[BlueDragon747]

Found my first solo mining crypto currency block ever at 5:13 this morning! I like it!

Does anyone know how much bandwidth the wallet consumes?

Will "no-submit-stale" remove all the "Share below target" in the log?

Generally is there another "better" way to solo mine than JSON RPC over HTTP with the blakecoin-qt?

wallet bandwidth is low but needs good latency, getwork uses about 4x more than stratum but I can easily mine 2-3 rigs to one wallet on a lan network

if solo "no-submit-stale" will not submit all shares which could miss a block so I always leave it out for solo but on pool it works well

pool uses JSON RPC and blakecoind most of the python miners I have tried have not stressed the wallet compared to cgminer

[BlueDragon747]

Released a new public pool in New York  
https://bitcointalk.org/index.php?topic=408794

I was using this as a test server but have cleaned the db and fixed the front end, it is using the same code base as EU server so might still be unstable until I have rewritten a few functions in the share submission

payout was working but not tested since wipe

I am now working on a third server that I am doing all my tests on

this should help solve the single public pool issue until I can get the code base stable  

this should work for a pool only failover cgminer.conf:

Code:

{
"pools" : [
	{
	        "url" : "stratum+tcp://eu1.blakecoin.com:3334",
		"user" : "UserName.Worker",
		"pass" : "WorkerPass"
        },
        {
	        "url" : "stratum+tcp://ny1.blakecoin.com:3334",
		"user" : "UserName.Worker",
		"pass" : "WorkerPass"
	}
],

"intensity" : "10",
"auto-gpu" : true,
"expiry" : "120",
"failover-only" : true,
"gpu-threads" : "2",
"log" : "5",
"no-restart" : true,
"queue" : "3",
"scan-time" : "30",
"worksize" : "128",
"temp-hysteresis" : "4",
"blake256" : true,
"vectors" : "1",
"failover-only" : true,
"no-submit-stale" : true,
"kernel-path" : "/"
}

Edit:
I also removed the fees on the pools enjoy