[ALPHA.masterpool.eu] Merged Mining Test Server - TESTNET!

[thirdlight]

Using Phoenix 1.50, both poclbm & phatk kernels, through Flexible Mining Proxy.

Getting ready for a >GH/s test...

... Ran for about 25 minutes, found 3 BTC blocks. Stales at about 2%, not bad for 3 block changes in 20 mins!

No NMC blocks.

[nodemaster]

No NMC blocks.

NMC blocks are found, but the merged-mine RC3 rejects to add the proof of work before block 24k. Thus no immature block is created. But you would have found several if we were above block 24k.

[smoothie]

No NMC blocks.

NMC blocks are found, but the merged-mine RC3 rejects to add the proof of work before block 24k. Thus no immature block is created. But you would have found several if we were above block 24k.

How do we verify if NMC blocks "would have" been generated if there is no proof of work?

[smoothie]

Okay I am pointing about 330 MH/s to the merged mining test server.

Shares seem to be generating ok.

MH/s on my miner on my end seems to fluctuate quite a bit. I am using poclbm miner.

I'll provide updates as they come available on my testing.

[nodemaster]

How do we verify if NMC blocks "would have" been generated if there is no proof of work?

At the moment I'm digging through the log files of the NMC client. Looks like:

Code: Select all

	
BitcoinMiner:
AUX proof-of-work found
     our hash: 475d2b123b999b2051e3586254bfd9bd4726fb64cf9794eb4087eb1f022c9e36
  parent hash: 0000000000d67b27c9d96ec3a75ec77c075ae6d01c293bad8be280f41679941a
       target: 00000003c3220000000000000000000000000000000000000000000000000000
CBlock(hash=475d2b123b999b2051e3, ver=65793, hashPrevBlock=00000000e25c4892c34c, hashMerkleRoot=7d09b33b8e, nTime=1312116003, nBits=1d03c322, nNonce=0, vtx=1)
  CTransaction(hash=7d09b33b8e, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000, -1), coinbase 0422c3031d010152)
    CTxOut(nValue=50.00000000, scriptPubKey=0471ab6fa918e2420c7bb8d2d5d8b4)
  vMerkleTree: 7d09b33b8e
07/31/11 12:55 generated 50.00
keypool keep 26
ERROR: CheckProofOfWork() : AUX POW is not allowed at this block
ERROR: CheckBlock() : proof of work failed
InvalidChainFound: invalid block=475d2b123b999b2051e3  height=13194  work=7968550158478
InvalidChainFound:  current best=00000000e25c4892c34c  height=13193  work=7967408559300
ERROR: SetBestChain() : ConnectBlock failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
ERROR: BitcoinMiner : ProcessBlock, block not accepted

Unfortunately ATM moment there is no way to see it in the webinterface I have no clue how to emulate that we are above block 24k in order to get POW included...

[thirdlight]

Ok, I'm standing down.

Happy with that.

I'll test again with the next release.

[smoothie]

How do we verify if NMC blocks "would have" been generated if there is no proof of work?

At the moment I'm digging through the log files of the NMC client. Looks like:

Code: Select all

	
BitcoinMiner:
AUX proof-of-work found
     our hash: 475d2b123b999b2051e3586254bfd9bd4726fb64cf9794eb4087eb1f022c9e36
  parent hash: 0000000000d67b27c9d96ec3a75ec77c075ae6d01c293bad8be280f41679941a
       target: 00000003c3220000000000000000000000000000000000000000000000000000
CBlock(hash=475d2b123b999b2051e3, ver=65793, hashPrevBlock=00000000e25c4892c34c, hashMerkleRoot=7d09b33b8e, nTime=1312116003, nBits=1d03c322, nNonce=0, vtx=1)
  CTransaction(hash=7d09b33b8e, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000, -1), coinbase 0422c3031d010152)
    CTxOut(nValue=50.00000000, scriptPubKey=0471ab6fa918e2420c7bb8d2d5d8b4)
  vMerkleTree: 7d09b33b8e
07/31/11 12:55 generated 50.00
keypool keep 26
ERROR: CheckProofOfWork() : AUX POW is not allowed at this block
ERROR: CheckBlock() : proof of work failed
InvalidChainFound: invalid block=475d2b123b999b2051e3  height=13194  work=7968550158478
InvalidChainFound:  current best=00000000e25c4892c34c  height=13193  work=7967408559300
ERROR: SetBestChain() : ConnectBlock failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
ERROR: BitcoinMiner : ProcessBlock, block not accepted

Unfortunately ATM moment there is no way to see it in the webinterface I have no clue how to emulate that we are above block 24k in order to get POW included...

I am going to throw 1.2 GH/s to the test pool and maybe we can get some small scaling testing done as well as generating more BTC and NMC blocks in which you can verify via the log files.

[smoothie]

How do we verify if NMC blocks "would have" been generated if there is no proof of work?

At the moment I'm digging through the log files of the NMC client. Looks like:

Code: Select all

	
BitcoinMiner:
AUX proof-of-work found
     our hash: 475d2b123b999b2051e3586254bfd9bd4726fb64cf9794eb4087eb1f022c9e36
  parent hash: 0000000000d67b27c9d96ec3a75ec77c075ae6d01c293bad8be280f41679941a
       target: 00000003c3220000000000000000000000000000000000000000000000000000
CBlock(hash=475d2b123b999b2051e3, ver=65793, hashPrevBlock=00000000e25c4892c34c, hashMerkleRoot=7d09b33b8e, nTime=1312116003, nBits=1d03c322, nNonce=0, vtx=1)
  CTransaction(hash=7d09b33b8e, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000, -1), coinbase 0422c3031d010152)
    CTxOut(nValue=50.00000000, scriptPubKey=0471ab6fa918e2420c7bb8d2d5d8b4)
  vMerkleTree: 7d09b33b8e
07/31/11 12:55 generated 50.00
keypool keep 26
ERROR: CheckProofOfWork() : AUX POW is not allowed at this block
ERROR: CheckBlock() : proof of work failed
InvalidChainFound: invalid block=475d2b123b999b2051e3  height=13194  work=7968550158478
InvalidChainFound:  current best=00000000e25c4892c34c  height=13193  work=7967408559300
ERROR: SetBestChain() : ConnectBlock failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
ERROR: BitcoinMiner : ProcessBlock, block not accepted

Unfortunately ATM moment there is no way to see it in the webinterface I have no clue how to emulate that we are above block 24k in order to get POW included...

I am going to throw 1.2 GH/s to the test pool and maybe we can get some small scaling testing done as well as generating more BTC and NMC blocks in which you can verify via the log files.

Okay I have tested for a few hours now. Below is a screenshot of the statistics associated with my 4 test workers. Also some things to note:

1. tried using phoenix miner 1.5 but failed
2. are we to assume that the "estimated" nmc and btc column is what we would have mined on the testnet block chain? Nothing seems to be going into the left pane under "your stats".
3. Why do NMC get generated slower than btc when testing?
4. Why is there a vast difference in the number of shares for NMC and BTC? I was under the impression that each hash that is generated by my miner is submitted to both block chains thus resulting in two shares (one for each).

[nodemaster]

1. tried using phoenix miner 1.5 but failed

Could you please elaborate on that? thirdlite already confirmed phoenix 1.50 as okay:

Using Phoenix 1.50, both poclbm & phatk kernels, through Flexible Mining Proxy.
...
... Ran for about 25 minutes, found 3 BTC blocks. Stales at about 2%, not bad for 3 block changes in 20 mins!

Can you please tell us what error messages you got?

2. are we to assume that the "estimated" nmc and btc column is what we would have mined on the testnet block chain? Nothing seems to be going into the left pane under "your stats".

Right. This is due to the fact that BTC blockchain is set for confirmation. You see the block unconfirmed blocks on statistics (https://alpha.masterpool.eu/statistics) page. Seems as if we generate a bunch of blocks and maturing takes very long on testnet if we stop mining But I agree there should be information about your eastimated earnings from unconfirmed blocks. I'll implement this ASAP. NMC are not generated as the POW is not accepted by namecoind ATM

3. Why do NMC get generated slower than btc when testing?

At the moment there are no NMC generated as the proof of work (POW) is rejected from namecoind due to the fact that the block number is below 24k. The only thing I can do is manually check if a POW was send.

4. Why is there a vast difference in the number of shares for NMC and BTC? I was under the impression that each hash that is generated by my miner is submitted to both block chains thus resulting in two shares (one for each).

Each hash generated by your miner is checked against both blockchains by merged-mining-proxy (on the pools side). It can match either NMC or BTC. In rare cases it can match both blockchains. Thus you use the same hashrate on both blockchains but you won't have the same block generation rate.

[thirdlight]

I'm putting 300MH/s on - Phoenix 1.50 direct, no proxy, to test the patched namecoind.