[ANN] Mergecoin: bitcoin with merged mining patches applied

[markm]

I have finally started that "bitcoin with ONLY the merged mining parches applied" repo I have so often mentioned.

https://github.com/knotwork/Mergecoin

The purpose of this repo is to provide the common code that all merged mined coins based on bitcoin all have in common, that is, bitcoin plus being able to be a secondary coin in a merge.

Most merged mined coins will be trivially easy to update to recent bitcoin code using this repo once the repo is ready and debugged.

Namecoin and Devcoin, being more than trivially different from bitcoin, will take more work to update, as they have more things they need to change. But most will be able to update as fast and easy as the creation of pump and dump coins shows us almost anyone can easily do.

Problem is, recent bitcoin is quite a bit different from the ancient version the merged-mining.patch was based on, so just getting the merged mining patches all applied is going to take some work...

-MarkM-

[rav3n_pl]

Great job!
Hopefully existing merge coin creators will jump in and update

[solracx]

I have finally started that "bitcoin with ONLY the merged mining parches applied" repo I have so often mentioned.

https://github.com/knotwork/Mergecoin

The purpose of this repo is to provide the common code that all merged mined coins based on bitcoin all have in common, that is, bitcoin plus being able to be a secondary coin in a merge.

Most merged mined coins will be trivially easy to update to recent bitcoin code using this repo once the repo is ready and debugged.

Namecoin and Devcoin, being more than trivially different from bitcoin, will take more work to update, as they have more things they need to change. But most will be able to update as fast and easy as the creation of pump and dump coins shows us almost anyone can easily do.

Problem is, recent bitcoin is quite a bit different from the ancient version the merged-mining.patch was based on, so just getting the merged mining patches all applied is going to take some work...

-MarkM-

Seems to have failed compilation on MacOS X.

[Sondey10mg]

This is way over my head, seems nice work though, but I have a question.
How do you mergemine geistgeld? I'm merge mining namecoin, devcoin and ixcoin on bitparking, but that's the only option I know to mergemine?

[peonminer]

What are benefits of mergemine?

[TCPC]

Well done!  Keep up the hard work!

[jackjack]

inb4 people come and cry because there are no binaries

[mebezac]

This is some of the most exciting news in a long time, keep up the good work 

[solracx]

I have finally started that "bitcoin with ONLY the merged mining parches applied" repo I have so often mentioned.

https://github.com/knotwork/Mergecoin

The purpose of this repo is to provide the common code that all merged mined coins based on bitcoin all have in common, that is, bitcoin plus being able to be a secondary coin in a merge.

Most merged mined coins will be trivially easy to update to recent bitcoin code using this repo once the repo is ready and debugged.

Namecoin and Devcoin, being more than trivially different from bitcoin, will take more work to update, as they have more things they need to change. But most will be able to update as fast and easy as the creation of pump and dump coins shows us almost anyone can easily do.

Problem is, recent bitcoin is quite a bit different from the ancient version the merged-mining.patch was based on, so just getting the merged mining patches all applied is going to take some work...

-MarkM-

auxpow?
cryptopp/sha.h?

looking forward to the updates.

[markm]

Seems to have failed compilation on MacOS X.

Did you manage to apply the .rej chunks? I'd guess probably not, as one of the first clues as to whether you have applied them properly will be that it does compile...

-MarkM-

[markm]

auxpow?
cryptopp/sha.h?

looking forward to the updates.

Yeah it looks like whtever variant of diff I used to create merged-mining.patch didn't include the actual content of entire files that were to be added. I thought patch included creating entire files but evidently diff does not always include the info that patch actually needs to do that.

Presumably the copies in IXCoin, DeVCoin, I0Coin etc are pretty much all the same as they all probably came ultimately from the original patch file from when merged mining was first done, on namecoin.

Oh wait, I think I already fixed the crypt thing, I think it is now crypto.h or some such, that is, no longer a directory full of candidate crypto systems someone once upon a time was considering using.

-MarkM-

[ranlo]

What are benefits of mergemine?

You mine multiple coins at once (with the same hashes you already do).

[SebastianJu]

Whats the status of this project? Is it targetted to being able to merge mine every coin at the same time that can be merged mined?
I only know bitparking.com where one can mine devcoin, ixcoin and namecoin together with bitcoins. Is there a way to mine even more coins at the same time?

[jubalix]

What are benefits of mergemine?

You mine multiple coins at once (with the same hashes you already do).

Does this work because if you can find a block for btc being the highest dif, then it must work for lower dif chains?

[markm]

Whats the status of this project? Is it targetted to being able to merge mine every coin at the same time that can be merged mined?
I only know bitparking.com where one can mine devcoin, ixcoin and namecoin together with bitcoins. Is there a way to mine even more coins at the same time?

Bitparking chooses to only merge a few coins, that is simply their choice.

for example they used to include I0Coin but do not include it now.

I merge bitcoin, namecoin, devcoin, groupcoin, i0coin, ixcoin, coiledcoin and geistgeld.

If no one is going to help figure out how to get the chunks to apply that the new database is making complicated then this could be a very very long term project. But hey the longer it takes the less new miners will be jumping into merged mining so the more coins for the rest of us eh?

-MarkM-

[SebastianJu]

Whats the status of this project? Is it targetted to being able to merge mine every coin at the same time that can be merged mined?
I only know bitparking.com where one can mine devcoin, ixcoin and namecoin together with bitcoins. Is there a way to mine even more coins at the same time?

Bitparkinh chooses to only merge a few coins, that is simply their choice.

for example they used to include I0Coin but do not include it now.

I merge bitcoin, namecoin, devcoin, groupcoin, i0coin, ixcoin, coiledcoin and geistgeld.

If no one is goign to help figure out how to get the chuncks t apply that the new database is making complicated then this could be a very very long term project. But hey the longer it takes the less new miners will be jumping into merged mining so the more coins for the rest of us eh?

-MarkM-

I think merged mining has the best capabilities for higher returns by mining with asics. Other currencies are too small and fast saturated when many mine on them. Litecoins cant be mined with asic's yet, pool hopping isnt really possible anymore and having a feeless pool that gives transaction fees too can be done with merged mining too.
So i think merged mining is the best way to maximize profits yet.

Can you tell if the longpoll problem is a serious one? Or wouldnt it matter much when merge mining as much coins as possible? So that the earning at the end is better anyway?

Unfortunately i cant tell much about the techniques. Would setting up a bounty help here?

[tazman]

If no one is going to help figure out how to get the chunks to apply that the new database is making complicated then this could be a very very long term project. But hey the longer it takes the less new miners will be jumping into merged mining so the more coins for the rest of us eh?

-MarkM-

Here's a thought.  Instead of using the latest Bitcoin version with the new database as your starting point, why not use the last Bitcoin version BEFORE the database change (I think that was 0.7.2).  If it's the new database changes that you're stuck on then worry about that upgrade later.  Using Bitcoin 0.7.2 would allow the merge mined cryptos to at least come close to current.  Some haven't had client updates since 2011! 

[markm]

That seems kind of a waste of everyone's time and effort.

If a coin is going to bother to upgrade at all it might as well upgrade to the latest.

if it would just end up still old code it might as well stick with the old code it already has, though maybe I0Coin and GeistGeld might profit by rebasing themselves on some old merged coin that at least doesn't crash daily doing pointless DNS lookup and doesn't have memory leaks.

Also it might not be hard at all, I don't know as I didn't get to looking at those rejected chunks yet, had too many other things I need to do.

-MarkM-

[khabaro]

If no one is going to help figure out how to get the chunks to apply that the new database is making complicated then this could be a very very long term project. But hey the longer it takes the less new miners will be jumping into merged mining so the more coins for the rest of us eh?

-MarkM-

Here's a thought.  Instead of using the latest Bitcoin version with the new database as your starting point, why not use the last Bitcoin version BEFORE the database change (I think that was 0.7.2).  If it's the new database changes that you're stuck on then worry about that upgrade later.  Using Bitcoin 0.7.2 would allow the merge mined cryptos to at least come close to current.  Some haven't had client updates since 2011! 

not such a bad idea.  if we keep starting over on mergecoin every new bitcoin update then we'll never get anywhere.  a quick update to older version is better than six more months of nothing.  don't think its a waste of time at all.

[TheSwede75]

If no one is going to help figure out how to get the chunks to apply that the new database is making complicated then this could be a very very long term project. But hey the longer it takes the less new miners will be jumping into merged mining so the more coins for the rest of us eh?

-MarkM-

Here's a thought.  Instead of using the latest Bitcoin version with the new database as your starting point, why not use the last Bitcoin version BEFORE the database change (I think that was 0.7.2).  If it's the new database changes that you're stuck on then worry about that upgrade later.  Using Bitcoin 0.7.2 would allow the merge mined cryptos to at least come close to current.  Some haven't had client updates since 2011! 

not such a bad idea.  if we keep starting over on mergecoin every new bitcoin update then we'll never get anywhere.  a quick update to older version is better than six more months of nothing.  don't think its a waste of time at all.

Sounds a lot like greed over improvement. I would rather wait for a sustainable and well developed solution over hacking together something 90% for a quick few extra % income.