Topic: MergeCoin Help- Trying to merge mine, IXC, I0C,DVC, NMC - page 2. (Read 2228 times)
right okay i think i understand. So basically i need to apply the aux chain patches to the coin im working on and then it should be able to be merged mined with dvc and ixc etc
nope i need my coin to act as primary chain and be able to merge mine secondary chains like dvc
Yes but all coins derived from bitcoin already can act as primary chain, because bitcoin already can.
What we need to add to bitcoin before changing its name and rewards and such to clone all the other coins from it is ONLY the "act as a secondary chain" stuff. it already has everything else except the names icons rewards quirks etc that make each coin different. They all are just bitcoin plus acting as a secondary chain plus what makes them individually unique/different.
-MarkM-
Its secondary chain we want.
That's why I wrote "Although it doesn't include the patches required for an auxilliary chain it should be fairly easy to add those as it'll just be the rpc functions that are needed.". That commit does all the hard work. It ports over the auxpow stuff, changes the things required in block creation,etc. You can do the rest if you want it.
nope i need my coin to act as primary chain and be able to merge mine secondary chains like dvc
I have a version of the patches required to use bitcoin as a primary chain rebased on top of bitcoin 0.8.1 with the recent security fix and performance improvement patch from 0.8.3 and 0.8.2 respectively cherry picked. It's in the m0.8.1_merged branch of my bitcoin fork on github: https://github.com/doublec/bitcoin/tree/m0.8.1_merged
The commit you're looking for for just the merge mining code is: https://github.com/doublec/bitcoin/commit/7a6e135db4cdbf70c56546da8a5974152ef84e5a
The branch also includes a patch for using libzmq for block notifications which you probably don't want. Although it doesn't include the patches required for an auxilliary chain it should be fairly easy to add those as it'll just be the rpc functions that are needed. The patch also includes some extra stuff I used to use for implementing getblocktemplate with merge mining but you can strip those out if you don't need them.
The commit you're looking for for just the merge mining code is: https://github.com/doublec/bitcoin/commit/7a6e135db4cdbf70c56546da8a5974152ef84e5a
The branch also includes a patch for using libzmq for block notifications which you probably don't want. Although it doesn't include the patches required for an auxilliary chain it should be fairly easy to add those as it'll just be the rpc functions that are needed. The patch also includes some extra stuff I used to use for implementing getblocktemplate with merge mining but you can strip those out if you don't need them.
Its secondary chain we want. Bitcoin cannot act as secondary chain. Doing search and replace on bitcoin to change name rewards etc to make a new coin will result in a coin that can act as primary chain, because bitcoin can. Them merged mined coins need the "be able to act as a secondary chain" patches, those are the ones we need.
Being able to act as primary we get for free from bitcoin directly.
-MarkM-
I have a version of the patches required to use bitcoin as a primary chain rebased on top of bitcoin 0.8.1 with the recent security fix and performance improvement patch from 0.8.3 and 0.8.2 respectively cherry picked. It's in the m0.8.1_merged branch of my bitcoin fork on github: https://github.com/doublec/bitcoin/tree/m0.8.1_merged
The commit you're looking for for just the merge mining code is: https://github.com/doublec/bitcoin/commit/7a6e135db4cdbf70c56546da8a5974152ef84e5a
The branch also includes a patch for using libzmq for block notifications which you probably don't want. Although it doesn't include the patches required for an auxilliary chain it should be fairly easy to add those as it'll just be the rpc functions that are needed. The patch also includes some extra stuff I used to use for implementing getblocktemplate with merge mining but you can strip those out if you don't need them.
The commit you're looking for for just the merge mining code is: https://github.com/doublec/bitcoin/commit/7a6e135db4cdbf70c56546da8a5974152ef84e5a
The branch also includes a patch for using libzmq for block notifications which you probably don't want. Although it doesn't include the patches required for an auxilliary chain it should be fairly easy to add those as it'll just be the rpc functions that are needed. The patch also includes some extra stuff I used to use for implementing getblocktemplate with merge mining but you can strip those out if you don't need them.
nice thanks
Ahh there is an idea! Yes, try doing a diff of the last version of bitcoin to use Berkeley DB against the latest version of bitcoin, then try to apply that as a patch to the least-different-from-bitcoin merged mined coin that has no known bugs or quirks of its own. So, like groupcoin or ixcoin, I guess.
-MarkM-
-MarkM-
right okay, i might try one of the ideas ou posted on the other threads about comparing the coins code to the bitcoin's code then, Do you know which was the last version of bitcoin to use berkerlydb
where can i obtain these patches, i cant seem to find them in your github repo?
The mergecoin repo is bitcoin and the patch and the rejects that resulted from using the program named patch to apply the patch.
However it looks like the patch did not include any entire new separate files needed, only changes to files that already existed in bitcoin back when the patch was made.
The missing files though are already in all the merged mined coins that were already made by applying the full version of the patch, including it seems some entirely new files that had not existed in bitcoin before.
So groupcoin, devcoin, whatevercoin all likely contain copies of the files that for some reason the one big patch file form of the patch does not contain.
-MarkM-
where can i obtain these patches, i cant seem to find them in your github repo?
Did you finish the applying of the patches?
Several chuncks of the merged mining as a secondary coin patches were rejected by the patch program, they need to be manually applied, they are the .rej files.
I applied what I could, however i left the .rej files anyway so people can check what i actually did to what was supposed to be done but got rejected.
Even once all are cleanly applied the result will be a version of bitcoin that would be able to act as a secondary chain in a merge, which would be a hard fork of bitcoin.
But once that has been done, then all the various coins can clone it and start chaing the name the icons the block rewards and so on, all the things that make them each a different coin.
-MarkM-
EDIT actually once those patches are cleanly applied then also whatever bitcoin's vulnerability fix should also be applied before all the various coins clone it to mutate into a newer version of themselves.
Several chuncks of the merged mining as a secondary coin patches were rejected by the patch program, they need to be manually applied, they are the .rej files.
I applied what I could, however i left the .rej files anyway so people can check what i actually did to what was supposed to be done but got rejected.
Even once all are cleanly applied the result will be a version of bitcoin that would be able to act as a secondary chain in a merge, which would be a hard fork of bitcoin.
But once that has been done, then all the various coins can clone it and start chaing the name the icons the block rewards and so on, all the things that make them each a different coin.
-MarkM-
EDIT actually once those patches are cleanly applied then also whatever bitcoin's vulnerability fix should also be applied before all the various coins clone it to mutate into a newer version of themselves.
Im working on the mergecoin code to try out different coins that im thinking of making and i get this error when compiling? anyone have any ideas?
Error: http://pastebin.com/7NXkB5RQ
Error: http://pastebin.com/7NXkB5RQ
Jump to: