thank you for letting me know , maybe if im able to figure it out ill write one . Im also looking to learn how to add POS but i assume its the same... start searching through sources . Thanks again 
Topic: Patching a coin for AUXPOW (Read 717 times)
Well then i know where to start thank you for letting me know , maybe if im able to figure it out ill write one . Im also looking to learn how to add POS but i assume its the same... start searching through sources . Thanks again
thank you for letting me know , maybe if im able to figure it out ill write one . Im also looking to learn how to add POS but i assume its the same... start searching through sources . Thanks again 
im afraid there isnt. it takes a good bit of research of various coins and posts to peice it all together
Ahmed
Ahmed
Wow! thank you so much for taking the time to explain this to me and in a way i can easily understand I love your software! I understand that the dev needs to fully implement the change, but is there a way i can do a clean git clone, and create my own branch? then patch my own branch for auxpow? i realize its unlikely to be added to the main coin source and therefor will not be used... but im on a "quest for knowledge" and id love to learn the process anyways :)is there maybe some reading material anybody knows of that could get me started on the right path?
and in a way i can easily understand I love your software! I understand that the dev needs to fully implement the change, but is there a way i can do a clean git clone, and create my own branch? then patch my own branch for auxpow? i realize its unlikely to be added to the main coin source and therefor will not be used... but im on a "quest for knowledge" and id love to learn the process anyways :)is there maybe some reading material anybody knows of that could get me started on the right path?
Hey Mate
UNOMP Dev ahmedbodi here. Firstly the auxpow hard fork has to be done by the coin's dev. since its a consensus change. Secondly UNOMP only supports 1 aux chan per pool at the moment so it still wouldnt work for you even if done.
Ahmed
UNOMP Dev ahmedbodi here. Firstly the auxpow hard fork has to be done by the coin's dev. since its a consensus change. Secondly UNOMP only supports 1 aux chan per pool at the moment so it still wouldnt work for you even if done.
Ahmed
Hello all!
I have 2 questions here im hoping someone in the crypto community knows the answer to. I've been working quite hard on building a merged-minng, profit-switching, auto-exchanging, multi-pool lately (using unomp and combining a few guides online). I'm still fairly early in my build (after many full wipes and starting from scratch) but after some research ive come up with these 2 questions.
1)How does one go about patching a scrypt coin for auxpow as a secondary coin? is this possible by a pool owner for use on their pool (which i could then upload to github as a commit?) or does the dev have to implement the merged mining in the coin source?
2)does both the parent coin and secondary coin need to be patched? can i make multiple parents mine the same secondary aux coins? (due to my goal of profit-switching.. id like all my "switchable" coins to be merged mining.
I was reading around and found this post https://bitcointalksearch.org/topic/merged-miningpatch-68248 however it only mentions sha256 patching, and doesn't source the patch files. I'd love to add a few non merged capable coins to my pool as secondary chains (either too litecoin or dogecoin likely), and multiple main chains merged mining.
My Research So Far
patching:
-https://bitcointalksearch.org/topic/merged-miningpatch-68248
general merged mining info:
-http://bitcoin.stackexchange.com/questions/273/how-does-merged-mining-work
-http://dot-bit.org/Merged_Mining
-https://en.bitcoin.it/wiki/Merged_mining_specification
and either im blind, or what im looking for isnt quite in those sources (i may actually be blind lol its 3 am in ontario)
I have 2 questions here im hoping someone in the crypto community knows the answer to. I've been working quite hard on building a merged-minng, profit-switching, auto-exchanging, multi-pool lately (using unomp and combining a few guides online). I'm still fairly early in my build (after many full wipes and starting from scratch) but after some research ive come up with these 2 questions.
1)How does one go about patching a scrypt coin for auxpow as a secondary coin? is this possible by a pool owner for use on their pool (which i could then upload to github as a commit?) or does the dev have to implement the merged mining in the coin source?
2)does both the parent coin and secondary coin need to be patched? can i make multiple parents mine the same secondary aux coins? (due to my goal of profit-switching.. id like all my "switchable" coins to be merged mining.
I was reading around and found this post https://bitcointalksearch.org/topic/merged-miningpatch-68248 however it only mentions sha256 patching, and doesn't source the patch files. I'd love to add a few non merged capable coins to my pool as secondary chains (either too litecoin or dogecoin likely), and multiple main chains merged mining.
patching:
-https://bitcointalksearch.org/topic/merged-miningpatch-68248
general merged mining info:
-http://bitcoin.stackexchange.com/questions/273/how-does-merged-mining-work
-http://dot-bit.org/Merged_Mining
-https://en.bitcoin.it/wiki/Merged_mining_specification
and either im blind, or what im looking for isnt quite in those sources (i may actually be blind lol its 3 am in ontario)
Jump to: