I've registered a few names (but without filling out hosting information, etc.) in order to test things out.
Me too - everything seems to work as planned so far  I like the way this coin is heading, good work dev. |
|
|
|
Bitcoin Core version 0.11.2 releasedhttps://bitcoin.org/en/release/v0.11.2I won't have time to test it today, but there are some changes that may (will?) affect P2Pool, mainly the requirement for version 4 blocks. From the release notes: Notice to miners: Bitcoin Core’s block templates are now for version 4 blocks only, and any mining software relying on its getblocktemplate must be updated in parallel to use libblkmaker either version 0.4.3 or any version from 0.5.2 onward. Looks like we need an update to only produce version 4+ blocks before OP_CHECKLOCKTIMEVERIFY becomes enforced. Interesting - think I'll hold off updating my node for the time being. @ forrestv: If you're lurking, can you confirm if a p2pool update is required in order to use the latest Core release? Thanks |
|
|
|
I would guess that the change can be found somewhere here on a date after Jun 23rd 2014. Sorry that URL makes my eyes bleed so I can't use it.  |
|
|
|
I am ditching Mint. Building a Ubuntu 14.4 and try again.
You should give Xubuntu a try - it's much less resource hungry than Ubuntu, especially once the unneeded programs are removed. |
|
|
|
|
I've never solo mined before (even though merge mining with p2pool is pretty much solo mining anyway), so I can't help you much. Are you using your wallet user name & password with your miner? I'm pretty sure that needs to be done, as well as allowing your traffic through the firewall & port forwarding of course.
|
|
|
|
It uses NMC code, so you should change the ports in the "611.conf" to: Agreed, it took me a while to realize |
|
|
|
Thanks for the feedback. A new block should be mined on average every five minutes. You are running merged mining successfully now using the merged-mine-proxy script from contrib? i.e.: contrib/merged-mine-proxy -w $PORT_to_direct_mining_equipment -p http://pw:un@127.0.0.1:8332/ -x http://pw:un@127.0.0.1:8663/ No, I use the standard p2pool merge mining parameters. I'm still getting loads of orphaned blocks though: received: inv (37 bytes)
got inventory: block 94c3636c1b4ca7a3b569 new
askfor block 94c3636c1b4ca7a3b569 0
sending getdata: block 94c3636c1b4ca7a3b569
sending: getdata (37 bytes)
received: block (702 bytes)
received block 94c3636c1b4ca7a3b569
ProcessBlock: ORPHAN BLOCK, prev=bb519e1964dedc13baed
sending: getblocks (869 bytes)
received: inv (37 bytes)
got inventory: block 0000000000c5f4882374 have
sending: getblocks (869 bytes)
received: inv (37 bytes)
got inventory: block fce308c33bb90b27d961 new
askfor block fce308c33bb90b27d961 0
sending getdata: block fce308c33bb90b27d961
sending: getdata (37 bytes)
received: block (702 bytes)
received block fce308c33bb90b27d961
ProcessBlock: ORPHAN BLOCK, prev=94c3636c1b4ca7a3b569
sending: getblocks (869 bytes)
received: inv (37 bytes)
got inventory: block 0000000000c5f4882374 have
sending: getblocks (869 bytes)
ResendWalletTransactions()
received: inv (37 bytes)
got inventory: block 000000001472a6694306 new
askfor block 000000001472a6694306 0
sending getdata: block 000000001472a6694306
sending: getdata (37 bytes)
received: block (215 bytes)
received block 000000001472a6694306
ProcessBlock: ORPHAN BLOCK, prev=0000000000c5f4882374
received: inv (37 bytes)
got inventory: block 0000000005f466dbcba1 new
askfor block 0000000005f466dbcba1 0
sending getdata: block 0000000005f466dbcba1
sending: getdata (37 bytes)
received: block (215 bytes)
received block 0000000005f466dbcba1
ProcessBlock: ORPHAN BLOCK, prev=000000001472a6694306 Difficulty seems a bit too slow to adjust, especially with all the orphans. |
|
|
|
Have you setup a pool supporting 611 (SixEleven) merged mining or is this your private mining equipment?
It's my own p2pool node, not public - my internet is crap  I had to lower the hash rate, it was causing too many doa's. Hopefully when a few more miners jump in it will smooth out a little & I can raise it again gradually. |
|
|
|
Port 8661? I will try again then - can you confirm what the rpc port for 611 is? ...I can't test merge mining unless you post the correct port & rpcport 611 uses.......a search on your git repo for them reveals nothing. 611d standard port 8661, rpc port 8663: that's where you can find the relevant parts in the source code -> $ grep -n 866 * 611.cpp:2738: return fTestNet ? 18661 : 8661;
bitcoinrpc.cpp:62: return GetBoolArg("-testnet", false) ? 18663 : 8663; The forked original source code of namecoin is really painfully unsystematic  Allrighty then - we have some movement. Merge mining tested OK with a small amount of hash, so I'm gradually increasing to see how it goes. Diff has risen & the blockchain is moving again I'll keep an eye on it for a while.... |
|
|
|
Port 8661? I will try again then - can you confirm what the rpc port for 611 is? ...I can't test merge mining unless you post the correct port & rpcport 611 uses.......a search on your git repo for them reveals nothing. |
|
|
|
Is P2pool worth looking into?
Is it a better way to use Antpool?
Does it somehow make use of a local full node?
There is no p2pool for antpool - only p2pool itself, which is far better for the network anyway, as well as yourself |
|
|
|
I've updated my code for the new 0.11.9 client to the latest Bitcoin sources, including the upcoming BIP65. If you can compile from source, please give it a try: https://github.com/domob1812/i0coinI'm getting this error with the new client on p2pool: 2015-11-09 13:48:20.429566 > Error while calling merged getauxblock on http://127.0.0.1:7338/:
2015-11-09 13:48:20.429667 > Traceback (most recent call last):
2015-11-09 13:48:20.429696 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 577, in _runCallbacks
2015-11-09 13:48:20.429735 > current.result = callback(current.result, *args, **kw)
2015-11-09 13:48:20.429762 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1155, in gotResult
2015-11-09 13:48:20.429787 > _inlineCallbacks(r, g, deferred)
2015-11-09 13:48:20.429823 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1097, in _inlineCallbacks
2015-11-09 13:48:20.429857 > result = result.throwExceptionIntoGenerator(g)
2015-11-09 13:48:20.429886 > File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator
2015-11-09 13:48:20.429931 > return g.throw(self.type, self.value, self.tb)
2015-11-09 13:48:20.429966 > --- <exception caught here> ---
2015-11-09 13:48:20.430017 > File "/home/rig/p2pool/p2pool/util/deferral.py", line 41, in f
2015-11-09 13:48:20.430057 > result = yield func(*args, **kwargs)
2015-11-09 13:48:20.430088 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1097, in _inlineCallbacks
2015-11-09 13:48:20.430119 > result = result.throwExceptionIntoGenerator(g)
2015-11-09 13:48:20.430149 > File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator
2015-11-09 13:48:20.430180 > return g.throw(self.type, self.value, self.tb)
2015-11-09 13:48:20.430226 > File "/home/rig/p2pool/p2pool/util/jsonrpc.py", line 133, in _http_do
2015-11-09 13:48:20.430258 > raise Error_for_code(resp['error']['code'])(resp['error']['message'], resp['error'].get('data', None))
2015-11-09 13:48:20.430296 > p2pool.util.jsonrpc.NarrowError: -12 Error: Keypool ran out, please call keypoolrefill first
I done a search about "Error: Keypool ran out, please call keypoolrefill first" but couldn't find an answer - any ideas anyone? |
|
|
|
Bumping for awareness & educational purposes..... |
|
|
|
beta 2 working
With merge mining? |
|
|
|
I ran it for nearly an hour in case it was a diff adjustment issue, but it didn't change - my logs are completely full of the above stale block logs. My console readout was a constant: merged block submital result:false expected:true My conf file: server=1
daemon=1
rpcuser=my_user_name
rpcpassword=my_user_password
rpcport=8331
port=8330
rpcallowip=127.0.0.1
rpcallow=192.168.1.1
listen=1 More info: 2015-11-08 13:29:57.866379 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.866866 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.867552 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.868084 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.868623 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.869125 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.869629 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.870185 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.870684 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.871184 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.871861 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.872397 > Merged block submittal result: False Expected: True
2015-11-08 13:29:57.898732 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.004717 Merged block submittal result: True
2015-11-08 13:30:00.005360 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.006046 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.006493 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.007185 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.007816 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.008388 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.008963 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.009389 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.029207 Got new merged mining work!
2015-11-08 13:30:00.032948 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.033474 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.034137 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.034623 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.035099 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.035582 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.036206 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.036677 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.037301 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.038146 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.038799 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.039364 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.039876 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.040347 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.040822 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.043035 > Merged block submittal result: False Expected: True
2015-11-08 13:30:00.044597 > Merged block submittal result: False Expected: True |
|
|
|
I'm still only seeing the one node (domob) on the new wallet version - it would be nice if a few more users updated Working well btw. |
|
|
|
611 (SixEleven) should also support MergedMining with Bitcoin. It would be great if anyone could check if this feature works or not and share the result with us.
I tried - it doesn't work: All stale blocks when merge mining.......  This was using p2pool, port 8330, rpcport 8331. AUX proof-of-work found
our hash: 57cc0b842e430e473f103796e11fab02e9d32208ea23bee129121eb4387bdc99
parent hash: 000000000b47cb1c0918f199fe679ddb9849ac99c732ca957bec3d2e1b51c369
target: 0000000023ec0500000000000000000000000000000000000000000000000000
CBlock(hash=57cc0b842e430e473f10, ver=65793, hashPrevBlock=0b3161d138fc6cbe5ddc, hashMerkleRoot=1fc109bd4d, nTime=1446950449, nBits=1c23ec05, nNonce=0, vtx=1)
CTransaction(hash=1fc109bd4d, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 0405ec231c010152)
CTxOut(nValue=0.58564124, scriptPubKey=04f6c991f78466d1da414f65fda123)
vMerkleTree: 1fc109bd4d
11/08/15 02:41 generated 0.58564124
ERROR: BitcoinMiner : generated block is stale
BitcoinMiner:
AUX proof-of-work found
our hash: 57cc0b842e430e473f103796e11fab02e9d32208ea23bee129121eb4387bdc99
parent hash: 000000001484053cf81fd262cb0ef3079c721e6f36325d96f509838d3a19b5a3
target: 0000000023ec0500000000000000000000000000000000000000000000000000
CBlock(hash=57cc0b842e430e473f10, ver=65793, hashPrevBlock=0b3161d138fc6cbe5ddc, hashMerkleRoot=1fc109bd4d, nTime=1446950449, nBits=1c23ec05, nNonce=0, vtx=1)
CTransaction(hash=1fc109bd4d, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 0405ec231c010152)
CTxOut(nValue=0.58564124, scriptPubKey=04f6c991f78466d1da414f65fda123)
vMerkleTree: 1fc109bd4d
11/08/15 02:41 generated 0.58564124
ERROR: BitcoinMiner : generated block is stale
BitcoinMiner:
AUX proof-of-work found
our hash: 57cc0b842e430e473f103796e11fab02e9d32208ea23bee129121eb4387bdc99
parent hash: 000000001c7bd9c4a9ae4559ef5fa9917b624799f5a9ca937a624d3793541b82
target: 0000000023ec0500000000000000000000000000000000000000000000000000
CBlock(hash=57cc0b842e430e473f10, ver=65793, hashPrevBlock=0b3161d138fc6cbe5ddc, hashMerkleRoot=1fc109bd4d, nTime=1446950449, nBits=1c23ec05, nNonce=0, vtx=1)
CTransaction(hash=1fc109bd4d, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 0405ec231c010152)
CTxOut(nValue=0.58564124, scriptPubKey=04f6c991f78466d1da414f65fda123)
vMerkleTree: 1fc109bd4d
11/08/15 02:41 generated 0.58564124
ERROR: BitcoinMiner : generated block is stale
BitcoinMiner:
AUX proof-of-work found
our hash: 57cc0b842e430e473f103796e11fab02e9d32208ea23bee129121eb4387bdc99
parent hash: 0000000012458a6af15c226fd6358d088ea8bc57612ac9c0acb90a7327808ace
target: 0000000023ec0500000000000000000000000000000000000000000000000000
CBlock(hash=57cc0b842e430e473f10, ver=65793, hashPrevBlock=0b3161d138fc6cbe5ddc, hashMerkleRoot=1fc109bd4d, nTime=1446950449, nBits=1c23ec05, nNonce=0, vtx=1)
CTransaction(hash=1fc109bd4d, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 0405ec231c010152)
CTxOut(nValue=0.58564124, scriptPubKey=04f6c991f78466d1da414f65fda123)
vMerkleTree: 1fc109bd4d
11/08/15 02:41 generated 0.58564124
ERROR: BitcoinMiner : generated block is stale
BitcoinMiner:
AUX proof-of-work found
our hash: 57cc0b842e430e473f103796e11fab02e9d32208ea23bee129121eb4387bdc99
parent hash: 000000001f93fb5782563a84103da967593a78de5cecb3703b2f7c8476f73fb0
target: 0000000023ec0500000000000000000000000000000000000000000000000000
CBlock(hash=57cc0b842e430e473f10, ver=65793, hashPrevBlock=0b3161d138fc6cbe5ddc, hashMerkleRoot=1fc109bd4d, nTime=1446950449, nBits=1c23ec05, nNonce=0, vtx=1)
CTransaction(hash=1fc109bd4d, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000, -1), coinbase 0405ec231c010152)
CTxOut(nValue=0.58564124, scriptPubKey=04f6c991f78466d1da414f65fda123)
vMerkleTree: 1fc109bd4d
11/08/15 02:41 generated 0.58564124
ERROR: BitcoinMiner : generated block is stale |
|
|
|
All stale blocks when merge mining....... |
|
|
|
the bad thing is that this pool is one of the pools that is contributing to the slowness of confirmations by mining empty blocks with bad code..
Precisely. It's a little amusing to see miners who support a pool that doesn't contribute to the network complain about how long transactions take |
|
|
|
|
Show Posts
