Topic: 4,000 BTE bounty for patching Bytecoin to merged mine (Read 3174 times)

Im still trying to figure out if I owe a bounty and if so to who. BTE is certainly been gaining market support.

I'm revoking the bounty. I no longer have the funds.

Anon136 and BladeRunner, feel free to do what you wish. Thanks for the support.

Unfortunately, we didn't gain mass support.

You told me master earlier. I was under that assumption.
https://bitcointalksearch.org/topic/m.2764701

But sure, I will release the bounty once the following are complete:
I have a windows binary. Is this patched? http://www.bytehits.info/bytecoin-0.8.1-win32.7z
I sucessfully add it to a p2pool node as a slave mergedmine coin. I plan to use my own p2pool.
The fork begins and people support it. Have you set the block at which it begins?
And I find the first block. This won't take long with 22 ghs.

I have just now forked bitcoin to a new repo, https://github.com/knotwork/Mergecoin.git

This is to be the Mergecoin repo.

I am going to clone it at home and try to get the merged mining patches to apply.

If I can do that I can then push the changes back up to the repo and presto we will have the wonderful common ancestor repo from which all the merged mined coins can then update themselves, and from which bytecoin (and any other bitcoin clone that wants to add merged mining) can also create a new version of itself.

-MarkM-

All the merged mined coins all need the same basic template from which to update themselves:

A copy of bitcoin with the merged mining patches applied.

Given that, each coin then only needs to fork it and apply their own usually pretty trivial modifications that makes them different from each other, such as their coins per block, their difficulty adjustment system, their default ports, their IRC channel or channels, their magic handshake bytes, and the cosmetics.

So really the best place to start is with a good recent stable copy of bitcoin.

Otherwise its a huge waste of programmer time with everyone hacking directly at just one coin instead of all being able to work from the common ancestor, which is bitcoin with ONLY the merged mining patches applied.

NOTE that doing it this way would also allow I0coin and geistgeld, the most troublesome / hardest to merge, to be updated too, allowing more people to be able to successfully merge the full panoply of merged mined coins.

So for anyone who is actually going to merged mine, having this raw "pure bitcoin with ONLY merged mining patches applied" is pretty much a no-brainer, allowing all merged coins to then be upgraded thus allowing all miners who merge to maximise their merges.

(To update Bytecoin you would diff it against the version of bitcoin it was forked from, then apply that diff as a patch to the "raw bitcoin with ONLY merged mining patches applied" repo, nice and simple. Oh and pick a block number at which merged mining will turn on.)

-MarkM-