As far as I'm aware, only eligius supports it. This is why I'm bringing it back up since it's not in the pool ops' interests to implement it but it is in the miners' interests.
I'm under the impression that my pool, bitparking, and fireduck's pool, HHTT, support it unless I'm misunderstanding what you mean by reconnect support.
|
|
|
Hmm I don't understand this either. Simply being a bitcoin clone, like Terracoin and Bytecoin, should mean you already can act as primary chain, shouldn't it? Since bitcoin can, that ability should be part of what was inherited from bitcoin?
Sure, but as I've said more than once already...If you're using the merge mine proxy you need these patches. But the reason I provided the commit is not for the millions of people using the merge mine proxy, it's because it ports a bunch of stuff that the secondary chain code uses and I had thought those interested in that would like using it as a base, or looking at it to see what changes are needed, to porting the other patches.
|
|
|
Okay but i don't have to patch bitcoin when I want to use it as a secondary chain, so presumably that part is already in bitcoin nowadays.
Assuming you meant 'primary' not 'secondary', you do if you want to use the 'merge mine proxy'. You don't if you use pool software that does internally what merge mine proxy does (eg. eloipool).
|
|
|
yep thanks, that seems fine. By cherry pick is there anything in particular i should be applying?
From your coin repository, something like: 1. git remote add foo git://github.com/doublec/bitcoin 2. git fetch foo 3. git cherry-pick 7a6e135db4cdbf70c56546da8a5974152ef84e5a 4. Fix any conflicts If you're stuck I could probably do it for a 50 BTC bounty or so.
|
|
|
basically what im after is modifying the coin im working on to be able to merged mined, likely with something like p2pool with DVC, IXC, I0C, NMC as aux chains
If you cherry pick the commit I referenced to your coin and use the "merge mining proxy" that is included in the 'contrib' directory that is added by that commit then you can have your coin as a primary chain while mining DVC, etc as secondary chains. You won't be able to mine bitcoin though but from your posts I'm assuming you are fine with that.
|
|
|
Okay I am not understanding what you mean then. By use bitcoin as a primary chain, you mean act as a secondary chain?
No, I mean as a primary chain using the merge mining proxy software. That software requires extra RPC commands to be patched to bitcoin. This patch ports those extra RPC commands. But those RPC commands also use a bunch of stuff that the secondary chain RPC commands use - so a lot of the porting work to get the secondary chain additional stuff working is also done in this patch.
|
|
|
Yes but all coins derived from bitcoin already can act as primary chain, because bitcoin already can.
Well, yes and no. If they're using the 'merge mining proxy' they can't as that proxy requires patches to bitcoin. If they're using custom block generation pool software then that software would need to be changed to work with their coin.
|
|
|
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.
|
|
|
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_mergedThe commit you're looking for for just the merge mining code is: https://github.com/doublec/bitcoin/commit/7a6e135db4cdbf70c56546da8a5974152ef84e5aThe 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.
|
|
|
I suggest redoubling the bounties which have not been awarded even in part.
What does "redoubling the bounties" mean? Do you mean multiplying them by 2?
|
|
|
Have other pools lost interest in implementing reconnect support?
What pools do and what pools don't support it?
|
|
|
LOL, I had .92 BTC on that block... had .6 on previous few and following few b/c my one single bombed due to heat...
It had 0.5 BTC of transaction fees too which has been the highest the pool has come across for some time. Bad block to orphan!
|
|
|
Can I mine in a pool without revealing my IP address? I sign up to pools using Tor but I'm sure it defeats the purpose once I connect to the pool using GUIMiner
Some pools have Tor endpoints. For example, HHTT.
|
|
|
Looks like ASICminer doesn't play fair... We found block 1 minute before them but they found next two and forced there's on network...
Yeah, looks like they are preferring to build on their own blocks when they can.
|
|
|
Question: could a pool be merged mining and keeping the extra ~3% for itself, when it publicly claims that it's not? How would one check for this?
Look at the coinbase for the generate transaction. It will have some conspicuous extra data if they're merge mining.
|
|
|
Is that your real name or is this another bitcoin screen name like Satoshi? Doesn't matter but I'm curious.
The ixcoin author's name is an exact anagram for Satoshi Nakamoto so it's unlikely to be a real name.
|
|
|
@doublec maybe you should bold this
Yes, good idea. I'd change it to not be case sensitive but old accounts rely on it now.
|
|
|
Lets try 'sh_ttd'...
Ah, found the previous one by looking up your registered addresses for that. It was "SHTTD".
|
|
|
Hmm, very strange situation. I was absolutely sure that i registered user 'shttd'.
If you know one of the addresses you registered I can look it up.
|
|
|
Anybody else experienced this?
I have not heard of anyone reporting this. Is your miner falling back to a backup pool?
|
|
|
|