[1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff]

[willphase]

I suddenly seem to have an unconfirmed balance - despite paying the 2% fee for 'prepay BTC' enabled... is there any issue here?

Will

[WhitePhantom]

I also have an unconfirmed 4.59759383 BTC.  Did the perks processing functionality die?  I'm curious as to whether those using the API perk are having issues.

[MinorMiner]

Does BitMinter support the stratum protocol yet? Sorry if that's been answered in the 100+ pages before this one 


PS: bitcointalk's search function is horrible.

[benny32]

API perk seems to be working but I am also showing unconfirmed balance.

[bigasic]

I also pay for the perks yet it acts like im not... sounds like others are having the same issue...

[DrHaribo]

Payouts appear to be stuck. Working on it!

[DrHaribo]

Fixed. Lots of coins just went out.

The payments got stuck last night. All payments for blocks were set up as usual but were not being processed, so coins did not go into user accounts. Some blocks were showing in the block list with negative number of confirmations remaining and prepay was not working either. This has now been fixed, user accounts credited and payments have gone out for those who are above their auto cash out threshold.

Apologies for the late payouts.

[DrHaribo]

Does BitMinter support the stratum protocol yet?

Not yet. Here's the status right now:

Variable difficulty is still only in testing on port 9000. Waiting with putting that on port 8332 since hashpower.com doesn't support var diff yet. If ASICs hit the market soon then I will of course turn on var diff.

GBT (getblocktemplate) is almost ready for testing. Will be up on port 9000 soon.

Stratum is next on the list.

[abeaulieu]

Does BitMinter support the stratum protocol yet?

Not yet. Here's the status right now:

Variable difficulty is still only in testing on port 9000. Waiting with putting that on port 8332 since hashpower.com doesn't support var diff yet. If ASICs hit the market soon then I will of course turn on var diff.

GBT (getblocktemplate) is almost ready for testing. Will be up on port 9000 soon.

Stratum is next on the list.

As always Dr is on top of his shit. Thanks

[loshia]

As always Dr is on top of his shit. Thanks

+1
He is good for sure Very good!

[DrHaribo]

As always Dr is on top of his shit. Thanks

+1
He is good for sure Very good!

My name is DrH and I paid for approve of this message. Thanks

[epsillion]

Hello DrHaribo i am having difficulty getting the bitminter mining client to work it has worked flawlessly for a long time and on the last bootup i got a java upgrade and the bitminter client  will no longer start up. Any suggestions. Any help will be appreciated

[Digigami]

Try deleting the java cache..

Start Menu , run "java"

Delete the temp internet files.

[DrHaribo]

There's a nice and friendly guide for how to clear the java temporary files here: http://www.java.com/en/download/help/plugin_cache.xml

If you're not on Windows you can use

Code:

javaws -viewer

at the command line to get to the java control panel. That works on Windows too.

[DrHaribo]

GBT (getblocktemplate) testing is up on port 9000.

Testing so far:

cgminer isn't sending a workid and so every proof-of-work is rejected with the message "unknown-work". Have to look into this.

bfgminer works. But it occassionally says "Failed to get next data from template; spinning wheels!". It also sometimes says the pool is issuing old work right after a block change. Not sure yet what causes this.

Not much point testing cgminer (2.9.3) further before the workid issue is resolved. But please do test bfgminer and any GBT proxy you may have. Let me know how it runs.

[DAoneNonlyG]

lots of rejeceted blocks (proof of work does not match target) with ztex btcminer...
but they seem to be valid... 

[thph]

same here .....lots of rejeceted blocks (proof of work does not match target) with ztex btcminer

[DrHaribo]

Sorry, guys, I accidentally turned on var diff on port 8332. Fixed. I guess ztex btcminer only supports diff 1?

I have been watching port 9000 to make sure that noone left a cgminer unattended and getting everything rejected. Since that's not the case I will leave GBT up for testing.

[-ck]

GBT (getblocktemplate) testing is up on port 9000.

Testing so far:

cgminer isn't sending a workid and so every proof-of-work is rejected with the message "unknown-work". Have to look into this.

Not much point testing cgminer (2.9.3) further before the workid issue is resolved. But please do test bfgminer and any GBT proxy you may have. Let me know how it runs.

A workid with what? With the block submit? There is an id sent, and it matches that which the request for a template went out with. Yes, it's always zero... is that the problem? The data is all completely reconstructed for a block submit so the actual id of where the template came from doesn't seem to be relevant to any other pool. Is this the issue for you? I'm just trying to understand...

[DrHaribo]

A workid with what? With the block submit? There is an id sent, and it matches that which the request for a template went out with. Yes, it's always zero... is that the problem? The data is all completely reconstructed for a block submit so the actual id of where the template came from doesn't seem to be relevant to any other pool. Is this the issue for you? I'm just trying to understand...

Not the JSONRPC request id but the GBT "workid" value that is sent out with every template. The spec requires that you send it back to the pool with every block submit. Apparently Eligius and Eclipse MC don't use the workid so they don't care if it's missing. But my implementation is dependent on it as of now. I am thinking about having it search through the coinbase to figure out the workid if it is missing, though.