Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 300. (Read 903150 times)
June 05, 2013, 12:11:59 AM
what does it mean when your cards hash but the shares are not accepted?
June 04, 2013, 08:27:30 PM
This will really help with the difficulty spike eating away profits. Thank you for doing this.
It usually cause severe Bitcoin mining instability. I'm not at all happy about this.
Merged mining doesn't cause instability unless the implementation is poor. It can cause minor (<0.1%) drops in BTC due to added latency when preparing new work after a longpoll. However, I'm specifically implementing this in a way where namecoin efficiency is sacrificed to let the pool run without skipping a beat even if namecoind is frozen/slow/crashed. The only efficiency change will be work messages from the pool require ~50 bytes of extra data inside the coinbase.
UPDATE: Phase 1 went well. I've got the pool creating the bitcoin side of merged mining (coinbase message that includes the mm signal + namecoin block hash) while still successfully creating blocks. Tomorrow I'll be working on building the NMC block with the MM headers included. It's very likely this can be done by the weekend unless I run into unexpected problems. Everything is in place so the entire namecoin side is running in a separate thread that will not block the primary pool/bitcoin threads.
June 04, 2013, 08:26:47 PM
Oh snap.
June 04, 2013, 08:16:24 PM
This will really help with the difficulty spike eating away profits. Thank you for doing this.
It usually cause severe Bitcoin mining instability. I'm not at all happy about this.
June 04, 2013, 08:04:25 PM
This will really help with the difficulty spike eating away profits. Thank you for doing this.
June 04, 2013, 06:37:35 PM
Alright, I've been looking over the documentation that was added to the Bitcoin wiki recently regarding implementation of merged mining. At this time, the only planned alternate currency to be added is NMC. Others could be added later, but I will be taking this slowly.
NMC will not have as much presence in the UI. BTC Guild is a Bitcoin mining pool, and throwing more graphs/tables of data for alternate currencies is not something I plan to do. The current plan to keep NMC implementation simple and clean is to bootstrap it to the PPLNS system. When a namecoin block is found, it will get distributed evenly to the open PPLNS shifts the same way BTC is distributed. This means it will not be available via PPS. Still working on how I will handle PPS for NMC going forward.
Once the stratum code is tested and working, the getwork based merged mining server will be closed down after a reasonable period of time for users to move to Stratum.
NMC will not have as much presence in the UI. BTC Guild is a Bitcoin mining pool, and throwing more graphs/tables of data for alternate currencies is not something I plan to do. The current plan to keep NMC implementation simple and clean is to bootstrap it to the PPLNS system. When a namecoin block is found, it will get distributed evenly to the open PPLNS shifts the same way BTC is distributed. This means it will not be available via PPS. Still working on how I will handle PPS for NMC going forward.
Once the stratum code is tested and working, the getwork based merged mining server will be closed down after a reasonable period of time for users to move to Stratum.
Is it active or still a plan at the moment?
It's a plan at the moment. I posted in the IRC room that I may have a test server available by this weekend. I'm actually hoping to get this running on a local bitcoin+namecoin testnet tonight, then it's just a matter of making sure namecoind crashing/hanging won't cause the server to hang/wait.
June 04, 2013, 06:08:01 PM
Alright, I've been looking over the documentation that was added to the Bitcoin wiki recently regarding implementation of merged mining. At this time, the only planned alternate currency to be added is NMC. Others could be added later, but I will be taking this slowly.
NMC will not have as much presence in the UI. BTC Guild is a Bitcoin mining pool, and throwing more graphs/tables of data for alternate currencies is not something I plan to do. The current plan to keep NMC implementation simple and clean is to bootstrap it to the PPLNS system. When a namecoin block is found, it will get distributed evenly to the open PPLNS shifts the same way BTC is distributed. This means it will not be available via PPS. Still working on how I will handle PPS for NMC going forward.
Once the stratum code is tested and working, the getwork based merged mining server will be closed down after a reasonable period of time for users to move to Stratum.
NMC will not have as much presence in the UI. BTC Guild is a Bitcoin mining pool, and throwing more graphs/tables of data for alternate currencies is not something I plan to do. The current plan to keep NMC implementation simple and clean is to bootstrap it to the PPLNS system. When a namecoin block is found, it will get distributed evenly to the open PPLNS shifts the same way BTC is distributed. This means it will not be available via PPS. Still working on how I will handle PPS for NMC going forward.
Once the stratum code is tested and working, the getwork based merged mining server will be closed down after a reasonable period of time for users to move to Stratum.
Is it active or still a plan at the moment?
June 04, 2013, 12:02:40 PM
Woot! Great work E. Can't wait to come home to the Guild. BitMinter is OK, but I miss the old place. 
June 04, 2013, 11:17:42 AM
Alright, I've been looking over the documentation that was added to the Bitcoin wiki recently regarding implementation of merged mining. At this time, the only planned alternate currency to be added is NMC. Others could be added later, but I will be taking this slowly.
NMC will not have as much presence in the UI. BTC Guild is a Bitcoin mining pool, and throwing more graphs/tables of data for alternate currencies is not something I plan to do. The current plan to keep NMC implementation simple and clean is to bootstrap it to the PPLNS system. When a namecoin block is found, it will get distributed evenly to the open PPLNS shifts the same way BTC is distributed. This means it will not be available via PPS. Still working on how I will handle PPS for NMC going forward.
Once the stratum code is tested and working, the getwork based merged mining server will be closed down after a reasonable period of time for users to move to Stratum.
NMC will not have as much presence in the UI. BTC Guild is a Bitcoin mining pool, and throwing more graphs/tables of data for alternate currencies is not something I plan to do. The current plan to keep NMC implementation simple and clean is to bootstrap it to the PPLNS system. When a namecoin block is found, it will get distributed evenly to the open PPLNS shifts the same way BTC is distributed. This means it will not be available via PPS. Still working on how I will handle PPS for NMC going forward.
Once the stratum code is tested and working, the getwork based merged mining server will be closed down after a reasonable period of time for users to move to Stratum.
June 04, 2013, 10:37:53 AM
EGADS - 15,093,988 in 238 blocks.
Yeah, huge jump in network hashrate recently giving rise to 9 blocks/hr.As always I'm late to the game and I don't think my lowly GPUs are going to do me much good soon.
June 04, 2013, 06:51:51 AM
No guarantees on a time table, but I'm setting time aside tomorrow to begin working on a branch of the BTC Guild stratum pool server that will implement merged mining. Technical details regarding how to implement merged mining have finally been added to the Bitcoin wiki. Until that was added, the only guidance I've found were reverse engineering the mergedmining proxy that some pools used in the past, or trying to look through the namecoin source and working backwards from there.
Awesome.. good news.. looking forward to it.!
Thanks.
June 04, 2013, 06:26:45 AM
EGADS - 15,093,988 in 238 blocks.
June 04, 2013, 05:59:28 AM
@eleuthria
Is there anything against us creating multiple accounts to put different workers on (Avalons etc) to track their lifetime earnings easier?
Is there anything against us creating multiple accounts to put different workers on (Avalons etc) to track their lifetime earnings easier?
Dude you brought Avalons as well..?
Ofc.
@eleuthria
Is there anything against us creating multiple accounts to put different workers on (Avalons etc) to track their lifetime earnings easier?
Is there anything against us creating multiple accounts to put different workers on (Avalons etc) to track their lifetime earnings easier?
Nothing against it, though I'm not sure why you'd need separate accounts to do it. One word of warning: Automatic Payouts don't work properly if you have two accounts sharing the same wallet address and triggering a payout at the same time, it requires a manual correction to fix.
This was similar to when I asked if you can track lifetime earnings of different workers and you said no. At the moment if I had 3 different 'projects' in the same account, all I can see is lifetime earnings for them combined, not separate. I can see lifetime shares, but that doesn't translate into anything for PPLNS. Thanks for letting us know we need multiple payout addresses though.
Edit: Will we need to run multiple emails?
June 04, 2013, 12:16:45 AM
No guarantees on a time table, but I'm setting time aside tomorrow to begin working on a branch of the BTC Guild stratum pool server that will implement merged mining. Technical details regarding how to implement merged mining have finally been added to the Bitcoin wiki. Until that was added, the only guidance I've found were reverse engineering the mergedmining proxy that some pools used in the past, or trying to look through the namecoin source and working backwards from there.
June 03, 2013, 08:16:59 PM
Gah, for the record, the pool is NOT at 40 TH/s. Small bug in some of the worker graphing/speed calculations from a worker I manually restored for testing.
June 03, 2013, 04:40:18 PM
Great day today boys.
That's 10 hours of kick-ass cheese.
Keep it up.
That's 10 hours of kick-ass cheese.
Keep it up.
June 03, 2013, 04:02:49 PM
@eleuthria
Is there anything against us creating multiple accounts to put different workers on (Avalons etc) to track their lifetime earnings easier?
Is there anything against us creating multiple accounts to put different workers on (Avalons etc) to track their lifetime earnings easier?
Nothing against it, though I'm not sure why you'd need separate accounts to do it. One word of warning: Automatic Payouts don't work properly if you have two accounts sharing the same wallet address and triggering a payout at the same time, it requires a manual correction to fix.
June 03, 2013, 03:55:49 PM
@eleuthria
Is there anything against us creating multiple accounts to put different workers on (Avalons etc) to track their lifetime earnings easier?
Is there anything against us creating multiple accounts to put different workers on (Avalons etc) to track their lifetime earnings easier?
Dude you brought Avalons as well..?
June 03, 2013, 03:53:36 PM
@eleuthria
Is there anything against us creating multiple accounts to put different workers on (Avalons etc) to track their lifetime earnings easier?
Is there anything against us creating multiple accounts to put different workers on (Avalons etc) to track their lifetime earnings easier?
June 03, 2013, 03:27:27 PM
I'm getting larger payouts than I would expect. Is the new PPLNS sanity check working, or do I need a sanity check myself? 
I'm getting dead even with what I expect over the last 24hrs.Suck it up and deal with it.
Then tell me what you're doing that's special.
Jump to: