[DVC]DevCoin - Official Thread - Moderated - page 189.

Hunterbunter

hero member

Activity: 994

Merit: 1000

Quote from: nibyokwy on February 10, 2014, 09:08:31 AM

to help understand the code path, what is the setup of the pool that is testing it? i see it is p2pool but is it mining bitcoin as the primary with devcoin as a merge mine coin? or is this initial test mining with devcoin as the primary? if the latter, has getblocktemplate (which i assume p2pool is using) modified from the original bitcoin one at all? If the former, it will be using the getaux... paths.

The P2Pool is mining bitcoins, and merge mining namecoin, i0coin, ixcoin and devcoin. I don't think you can merge mine bitcoin yet, the others you can do because the alt coins have code that allows it, whereas the bitcoin just ignores what they add to the bitcoin blockchain (or something, I don't understand it too well yet).

Quote from: sidhujag on February 10, 2014, 09:16:46 AM

There was a small change to template which matches bitcoin but wasnt in devcoin. When creatinh a block I set txout value to -fee in the template.. This could be the cause.

Why is it in bitcoin as -fee? I assumed it was something to do with the client checking to ensure sufficient balance before sending coins.

https://github.com/sidhujag/devcoin/search?q=-nFees&ref=cmdform

But this is in original commit and he said that one connects.. he should see rpccalls in the pool log to template code?

At the very least see the msg "running devcoin miner"?

The problem with the P2Pool is it doesn't create a log for successful attempts...it just says "Got new merged mining work!" but not from which daemon.

can I make that change locally on the master git and see if it still causes an error?

Hunterbunter

hero member

Activity: 994

Merit: 1000

Quote from: nibyokwy on February 10, 2014, 08:39:40 AM

Quote from: Hunterbunter on February 10, 2014, 08:31:29 AM

Does that help?

paste more of the log. is there a section before that showing details of a block submission? could there be a problem with the transactions in the coinbase related to the devcoin payouts that come from the file it regularly downloads?

that's another thing that probably needs testing. testing blocks found before and after the boundaries of new file data.

Here are few I can find in .devcoin/debug.log

Code:

received block 65bb9b37eea3360642b5637d5ea5305ff3cdaf00acaf9c4e8baf57fcf860cbd8
Committing 11 changed transactions to coin database...
SetBestChain: new best=65bb9b37eea3360642b5637d5ea5305ff3cdaf00acaf9c4e8baf57fcf860cbd8 height=125114 log2_work=75.067766 tx=224528 date=2014-02-07 23:20:07 progress=0.072150
ProcessBlock: ACCEPTED
received block 0521b1afb4cea4a79fba7f11953e5c1a1f3dfcb64ec8d57c17a548e28a268708
Committing 7 changed transactions to coin database...
SetBestChain: new best=0521b1afb4cea4a79fba7f11953e5c1a1f3dfcb64ec8d57c17a548e28a268708 height=125115 log2_work=75.068056 tx=224531 date=2014-02-07 23:24:43 progress=0.072151
ProcessBlock: ACCEPTED
received block 0f174afcb109386fb8e25e6c3170c218653941850d8547320003f53f0564eb67
Committing 1 changed transactions to coin database...
SetBestChain: new best=0f174afcb109386fb8e25e6c3170c218653941850d8547320003f53f0564eb67 height=125116 log2_work=75.068347 tx=224532 date=2014-02-07 23:26:18 progress=0.072151
Committing 18 changed transactions to coin database...
SetBestChain: new best=d0af0a1871a72ba01e509317ec4f77f4a279610676273a5ab97957b7b1853d38 height=125117 log2_work=75.068641 tx=224539 date=2014-02-07 23:37:29 progress=0.072154
Committing 20 changed transactions to coin database...
SetBestChain: new best=efad489d53063f984226aac7475b7cb043abad6514cda3eae135ac490e9dba27 height=125118 log2_work=75.068935 tx=224550 date=2014-02-07 23:54:27 progress=0.072157
ProcessBlock: ACCEPTED
getblocks 125085 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
keypool added key 102, size=101
keypool reserve 2
ERROR: CTransaction::CheckTransaction() : txout.nValue negative
ERROR: CheckBlock() : CheckTransaction failed
Flushing wallet.dat
Flushed wallet.dat 20ms
Added 1 addresses from 188.220.216.98: 12 tried, 1123 new

Code:

accepted connection 82.15.144.161:56275
send version message: version 70001, blocks=125120, us=190.120.236.179:52333, them=82.15.144.161:56275, peer=82.15.144.161:56275
Added time data, samples 4, offset -1 (+0 minutes)
Added 82.15.144.161:52333 from 82.15.144.161: 10 tried, 1159 new
Moving 82.15.144.161:52333 to tried
receive version message: version 32501, blocks=125120, us=190.120.236.179:52333, them=82.15.144.161:52333, peer=82.15.144.161:56275
connection timeout
trying connection 106.187.94.193:52333 lastseen=0.4hrs
connected 106.187.94.193:52333
send version message: version 70001, blocks=125120, us=190.120.236.179:52333, them=106.187.94.193:52333, peer=106.187.94.193:52333
Added time data, samples 5, offset -2 (+0 minutes)
nTimeOffset = -1 (+0 minutes)
receive version message: version 32501, blocks=125120, us=190.120.236.179:51827, them=106.187.94.193:52333, peer=106.187.94.193:52333
trying connection 95.87.202.189:52333 lastseen=4.5hrs
connection timeout
trying connection 94.12.52.116:52333 lastseen=4.9hrs
connection timeout
trying connection 91.121.174.223:52333 lastseen=2.6hrs
connected 91.121.174.223:52333
send version message: version 70001, blocks=125120, us=190.120.236.179:52333, them=91.121.174.223:52333, peer=91.121.174.223:52333
Added time data, samples 6, offset -1 (+0 minutes)
Moving 91.121.174.223:52333 to tried
receive version message: version 32501, blocks=125120, us=190.120.236.179:47184, them=91.121.174.223:52333, peer=91.121.174.223:52333
trying connection 162.243.208.154:52333 lastseen=0.4hrs
connected 162.243.208.154:52333
send version message: version 70001, blocks=125120, us=190.120.236.179:52333, them=162.243.208.154:52333, peer=162.243.208.154:52333
Added time data, samples 7, offset -1 (+0 minutes)
nTimeOffset = -1 (+0 minutes)
receive version message: version 32501, blocks=125120, us=190.120.236.179:59703, them=162.243.208.154:52333, peer=162.243.208.154:52333
keypool reserve 2
ERROR: CTransaction::CheckTransaction() : txout.nValue negative
ERROR: CheckBlock() : CheckTransaction failed
trying connection 173.69.204.230:52333 lastseen=4.8hrs
connection timeout
trying connection 46.115.143.136:52333 lastseen=4.9hrs
connection timeout
trying connection 38.118.62.165:52333 lastseen=4.6hrs
connection timeout
trying connection 38.108.113.249:52333 lastseen=4.9hrs
accepted connection 68.38.11.21:59000
send version message: version 70001, blocks=125120, us=190.120.236.179:52333, them=68.38.11.21:59000, peer=68.38.11.21:59000
Added time data, samples 8, offset -6 (+0 minutes)
Moving 68.38.11.21:52333 to tried
receive version message: version 32501, blocks=125120, us=190.120.236.179:52333, them=68.38.11.21:52333, peer=68.38.11.21:59000
Added 3 addresses from 91.121.174.223: 13 tried, 1159 new
connection timeout
trying connection 49.187.164.172:52333 lastseen=4.8hrs
connection timeout
trying connection 96.237.186.113:52333 lastseen=5.1hrs

Code:

received block 30e695568bcf94589433c4ea652ecc1935b2220ac8c4a6432165a0823c875852
Committing 10 changed transactions to coin database...
SetBestChain: new best=30e695568bcf94589433c4ea652ecc1935b2220ac8c4a6432165a0823c875852 height=125127 log2_work=75.071554 tx=224583 date=2014-02-08 01:35:27 progress=0.072159
ProcessBlock: ACCEPTED
received block 98765ac4f89e458e2c2cefcc10cc1c751571f063af48c55ec80341f847d60627
Committing 4 changed transactions to coin database...
SetBestChain: new best=98765ac4f89e458e2c2cefcc10cc1c751571f063af48c55ec80341f847d60627 height=125128 log2_work=75.071833 tx=224585 date=2014-02-08 01:36:09 progress=0.072160
ProcessBlock: ACCEPTED
connection timeout
trying connection 99.232.33.22:52333 lastseen=6.8hrs
connection timeout
trying connection 2.239.40.87:52333 lastseen=1.8hrs
connection timeout
trying connection 77.184.69.252:52333 lastseen=6.8hrs
Added 85 addresses from 198.211.105.133: 10 tried, 1205 new
connection timeout
trying connection 84.227.24.246:52333 lastseen=7.0hrs
connect() failed after select(): No route to host
trying connection 74.115.95.138:52333 lastseen=2.0hrs
connected 74.115.95.138:52333
send version message: version 70001, blocks=125128, us=190.120.236.179:52333, them=74.115.95.138:52333, peer=74.115.95.138:52333
trying connection 74.103.210.161:52333 lastseen=6.4hrs
keypool reserve 2
ERROR: CTransaction::CheckTransaction() : txout.nValue negative
ERROR: CheckBlock() : CheckTransaction failed
connection timeout
trying connection 99.73.124.137:52333 lastseen=4.2hrs
connection timeout
trying connection 38.108.113.249:52333 lastseen=6.5hrs
connection timeout
trying connection 106.187.94.193:52333 lastseen=2.0hrs
connected 106.187.94.193:52333
send version message: version 70001, blocks=125128, us=190.120.236.179:52333, them=106.187.94.193:52333, peer=106.187.94.193:52333
socket recv error 104
disconnecting node 106.187.94.193:52333
trying connection 68.187.211.2:52333 lastseen=2.0hrs
connection timeout
trying connection 68.187.211.2:52333 lastseen=2.0hrs
connection timeout
trying connection 2.239.40.87:52333 lastseen=1.8hrs

Code:

trying connection 113.68.109.104:52333 lastseen=2.1hrs
connection timeout
trying connection 90.130.41.14:52333 lastseen=2.7hrs
connected 90.130.41.14:52333
send version message: version 70001, blocks=125130, us=190.120.236.179:52333, them=90.130.41.14:52333, peer=90.130.41.14:52333
ThreadRPCServer method=getbalance
socket recv error 104
disconnecting node 90.130.41.14:52333
trying connection 162.242.17.178:52333 lastseen=2.5hrs
connected 162.242.17.178:52333
send version message: version 70001, blocks=125130, us=190.120.236.179:52333, them=162.242.17.178:52333, peer=162.242.17.178:52333
Added time data, samples 13, offset +3 (+0 minutes)
nTimeOffset = +0 (+0 minutes)
Moving 162.242.17.178:52333 to tried
receive version message: version 32501, blocks=125130, us=190.120.236.179:48601, them=162.242.17.178:52333, peer=162.242.17.178:52333
accepted connection 98.201.33.193:65029
send version message: version 70001, blocks=125130, us=190.120.236.179:52333, them=98.201.33.193:65029, peer=98.201.33.193:65029
Added time data, samples 14, offset -10 (+0 minutes)
Moving 98.201.33.193:52333 to tried
receive version message: version 32501, blocks=125130, us=190.120.236.179:52333, them=98.201.33.193:52333, peer=98.201.33.193:65029
ThreadRPCServer method=getinfo
keypool reserve 2
keypool return 2
CTxMemPool::accept() : accepted 5912842f1c77966b57d9976f6b1db1f208dee045f06dd8bc4ff21249e86a25fe (poolsz 1)
received getdata for: tx 5912842f1c77966b57d9976f6b1db1f208dee045f06dd8bc4ff21249e86a25fe
received getdata for: tx 5912842f1c77966b57d9976f6b1db1f208dee045f06dd8bc4ff21249e86a25fe
Flushed 1755 addresses to peers.dat 80ms
keypool reserve 2
ERROR: CTransaction::CheckTransaction() : txout.nValue negative
ERROR: CheckBlock() : CheckTransaction failed

Code:

trying connection 114.79.19.38:52333 lastseen=4.7hrs
Committing 3 changed transactions to coin database...
SetBestChain: new best=6f1aefce8d1606d07fd1d60f2082a10f31613dc8e7bcc6b3e43f274a265cbd94 height=125134 log2_work=75.0735 tx=224601 date=2014-02-08 02:23:54 progress=0.072161
ProcessBlock: ACCEPTED
received block 5b7fb292496a08e8b95327475e3bf06be0ffa50ca699eecdd0b132ee241c96a8
Committing 3 changed transactions to coin database...
SetBestChain: new best=5b7fb292496a08e8b95327475e3bf06be0ffa50ca699eecdd0b132ee241c96a8 height=125135 log2_work=75.073777 tx=224603 date=2014-02-08 02:29:39 progress=0.072162
ProcessBlock: ACCEPTED
ThreadRPCServer method=getin
ThreadRPCServer method=getinfo
keypool reserve 2
keypool return 2
connection timeout
trying connection 87.79.129.248:52333 lastseen=5.0hrs
14 addresses found from DNS seeds
dnsseed thread exit
Added 3 addresses from 162.243.208.154: 17 tried, 1741 new
keypool reserve 2
ERROR: CTransaction::CheckTransaction() : txout.nValue negative
ERROR: CheckBlock() : CheckTransaction failed
connection timeout
trying connection 217.44.32.33:52333 lastseen=0.4hrs
connection timeout
trying connection 98.201.33.193:52333 lastseen=0.4hrs
connection timeout
trying connection 118.244.207.5:52333 lastseen=0.6hrs
connected 118.244.207.5:52333
send version message: version 70001, blocks=125135, us=190.120.236.179:52333, them=118.244.207.5:52333, peer=118.244.207.5:52333
Added time data, samples 3, offset -1 (+0 minutes)
receive version message: version 32501, blocks=125135, us=190.120.236.179:60519, them=118.244.207.5:52333, peer=118.244.207.5:52333
trying connection 65.188.164.108:52333 lastseen=5.3hrs
connection timeout
trying connection 204.14.77.5:52333 lastseen=4.7hrs
connection timeout
trying connection 99.194.200.2:52333 lastseen=5.3hrs

Code:

send version message: version 70001, blocks=125135, us=190.120.236.179:52333, them=54.241.178.41:52333, peer=54.241.178.41:52333
received block 63266ac15972835220dafb25afe395f9e3a0f2882939efb85da63e72dc8e18e4
Committing 1329 changed transactions to coin database...
SetBestChain: new best=63266ac15972835220dafb25afe395f9e3a0f2882939efb85da63e72dc8e18e4 height=125136 log2_work=75.074054 tx=224605 date=2014-02-08 02:34:53 progress=0.072161
ProcessBlock: ACCEPTED
received block cf37b6038ae65c67e2430ac5f16ae56e69ed890a84a9594fc8b7766401633cc9
Committing 5 changed transactions to coin database...
SetBestChain: new best=cf37b6038ae65c67e2430ac5f16ae56e69ed890a84a9594fc8b7766401633cc9 height=125137 log2_work=75.074331 tx=224608 date=2014-02-08 02:42:53 progress=0.072162
ProcessBlock: ACCEPTED
Added time data, samples 4, offset +99 (+1 minutes)
receive version message: version 32400, blocks=125137, us=190.120.236.179:47376, them=54.241.178.41:52333, peer=54.241.178.41:52333
trying connection 50.131.171.225:52333 lastseen=5.4hrs
Added 28 addresses from 54.241.178.41: 19 tried, 1764 new
14 addresses found from DNS seeds
dnsseed thread exit
Flushing wallet.dat
Flushed wallet.dat 29ms
Added 1 addresses from 23.94.28.23: 19 tried, 1764 new
connection timeout
trying connection 122.178.217.3:52333 lastseen=1.0hrs
keypool reserve 2
ERROR: CTransaction::CheckTransaction() : txout.nValue negative
ERROR: CheckBlock() : CheckTransaction failed
connection timeout
trying connection 162.242.17.178:52333 lastseen=0.8hrs
connected 162.242.17.178:52333
send version message: version 70001, blocks=125137, us=190.120.236.179:52333, them=162.242.17.178:52333, peer=162.242.17.178:52333
Added time data, samples 5, offset +3 (+0 minutes)
nTimeOffset = +3 (+0 minutes)
receive version message: version 32501, blocks=125137, us=190.120.236.179:57476, them=162.242.17.178:52333, peer=162.242.17.178:52333
trying connection 98.28.46.106:52333 lastseen=5.1hrs
Added 6 addresses from 54.252.166.125: 19 tried, 1770 new
connection timeout
trying connection 198.154.60.183:52333 lastseen=2.0hrs
connected 198.154.60.183:52333
send version message: version 70001, blocks=125137, us=190.120.236.179:52333, them=198.154.60.183:52333, peer=198.154.60.183:52333
Added time data, samples 6, offset -1 (+0 minutes)
Moving 198.154.60.183:52333 to tried
receive version message: version 32400, blocks=125137, us=190.120.236.179:45486, them=198.154.60.183:52333, peer=198.154.60.183:52333
trying connection 36.83.52.243:52333 lastseen=5.4hrs
connection timeout
trying connection 200.203.173.39:52333 lastseen=5.0hrs
Added 7 addresses from 198.154.60.183: 20 tried, 1775 new
connection timeout
trying connection 114.79.19.38:52333 lastseen=5.1hrs
connection timeout
trying connection 74.115.95.138:52333 lastseen=2.0hrs
connected 74.115.95.138:52333
send version message: version 70001, blocks=125137, us=190.120.236.179:52333, them=74.115.95.138:52333, peer=74.115.95.138:52333
CTxMemPool::accept() : accepted d30b784d194878136924790cdc1fccf77ad9f15846498a664f0a69248209d905 (poolsz 1)
Added time data, samples 7, offset +3 (+0 minutes)
nTimeOffset = +3 (+0 minutes)
receive version message: version 32501, blocks=125137, us=190.120.236.179:44649, them=74.115.95.138:52333, peer=74.115.95.138:52333
trying connection 120.149.117.234:52333 lastseen=5.4hrs

This one had two before dying

Code:

received block 8fd048e1ea705befc9a1e05824def0dfc780bf3525f4255d8c8fde11282a9eaf
Committing 7 changed transactions to coin database...
SetBestChain: new best=8fd048e1ea705befc9a1e05824def0dfc780bf3525f4255d8c8fde11282a9eaf height=125139 log2_work=75.074886 tx=224623 date=2014-02-08 03:11:24 progress=0.072164
ProcessBlock: ACCEPTED
received block bde85f90140fe3315a920e3e9a655df5a7dcf2c7c301f3ed9d128493e7844a16
Committing 1 changed transactions to coin database...
SetBestChain: new best=bde85f90140fe3315a920e3e9a655df5a7dcf2c7c301f3ed9d128493e7844a16 height=125140 log2_work=75.075165 tx=224624 date=2014-02-08 03:13:41 progress=0.072164
ProcessBlock: ACCEPTED
received block 5dc796723a9bda4bc279fd341064bb8cb8ae91ba1ad6682282c7344af0031243
Committing 8 changed transactions to coin database...
SetBestChain: new best=5dc796723a9bda4bc279fd341064bb8cb8ae91ba1ad6682282c7344af0031243 height=125141 log2_work=75.075445 tx=224629 date=2014-02-08 03:21:26 progress=0.072166
ProcessBlock: ACCEPTED
connection timeout
trying connection 66.193.195.130:52333 lastseen=6.6hrs
connection timeout
trying connection 162.242.17.178:52333 lastseen=1.3hrs
connected 162.242.17.178:52333
send version message: version 70001, blocks=125141, us=190.120.236.179:52333, them=162.242.17.178:52333, peer=162.242.17.178:52333
Added time data, samples 3, offset +3 (+0 minutes)
receive version message: version 32501, blocks=125142, us=190.120.236.179:35457, them=162.242.17.178:52333, peer=162.242.17.178:52333
trying connection 95.87.202.189:52333 lastseen=4.1hrs
connect() failed after select(): Connection refused
trying connection 69.142.88.110:52333 lastseen=6.1hrs
keypool reserve 2
ERROR: CTransaction::CheckTransaction() : txout.nValue negative
ERROR: CheckBlock() : CheckTransaction failed
Added 4 addresses from 162.242.17.178: 17 tried, 1742 new
received block 34d6faf3c525ad233f347b4812c0f0488c80c445e3acb378ceae4150b5d69bcc
Committing 4 changed transactions to coin database...
SetBestChain: new best=34d6faf3c525ad233f347b4812c0f0488c80c445e3acb378ceae4150b5d69bcc height=125142 log2_work=75.075724 tx=224631 date=2014-02-08 03:24:16 progress=0.072166
ProcessBlock: ACCEPTED
connection timeout
trying connection 87.114.111.214:52333 lastseen=8.3hrs
connection timeout
trying connection 24.167.200.111:52333 lastseen=8.5hrs
CTxMemPool::accept() : accepted 35bdd522f61d78aaad828ce8aa2728d41b0bfc63c882308ca8d2114abc176ff5 (poolsz 1)
connection timeout
trying connection 65.60.190.183:52333 lastseen=4.0hrs
Added 2 addresses from 118.244.207.5: 17 tried, 1744 new
connection timeout
trying connection 177.99.27.220:52333 lastseen=5.8hrs
connect() failed after select(): Connection refused
trying connection 213.167.158.78:52333 lastseen=6.4hrs
connection timeout
trying connection 175.136.130.44:52333 lastseen=6.2hrs
ERROR: CTransaction::CheckTransaction() : txout.nValue negative
ERROR: CheckBlock() : CheckTransaction failed
connection timeout
trying connection 173.154.37.181:52333 lastseen=6.1hrs
connection timeout
trying connection 82.14.115.136:52333 lastseen=6.4hrs
connection timeout
trying connection 92.141.64.225:52333 lastseen=6.1hrs
connect() failed after select(): No route to host
trying connection 24.113.73.192:52333 lastseen=6.3hrs
connection timeout
trying connection 179.253.51.21:52333 lastseen=5.8hrs
connection timeout
trying connection 80.42.201.45:52333 lastseen=13.5hrs

etc. That ERROR is present before every single termination.

P2Pool is a bit easier...it's exactly the same every time:

Code:

> Error while calling merged getauxblock on http://127.0.0.1:52332/:
2014-02-07 21:08:51.551955 > Traceback (most recent call last):
2014-02-07 21:08:51.552099 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 577, in _runCallbacks
2014-02-07 21:08:51.552274 > current.result = callback(current.result, *args, **kw)
2014-02-07 21:08:51.552390 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1155, in gotResult
2014-02-07 21:08:51.552509 > _inlineCallbacks(r, g, deferred)
2014-02-07 21:08:51.552615 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1097, in _inlineCallbacks
2014-02-07 21:08:51.552736 > result = result.throwExceptionIntoGenerator(g)
2014-02-07 21:08:51.552848 > File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator
2014-02-07 21:08:51.552971 > return g.throw(self.type, self.value, self.tb)
2014-02-07 21:08:51.553082 > --- ---
2014-02-07 21:08:51.553188 > File "/home/amit/p2pool/p2pool/util/deferral.py", line 41, in f
2014-02-07 21:08:51.553301 > result = yield func(*args, **kwargs)
2014-02-07 21:08:51.553409 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1097, in _inlineCallbacks
2014-02-07 21:08:51.553530 > result = result.throwExceptionIntoGenerator(g)
2014-02-07 21:08:51.553640 > File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator
2014-02-07 21:08:51.553768 > return g.throw(self.type, self.value, self.tb)
2014-02-07 21:08:51.553879 > File "/home/amit/p2pool/p2pool/util/jsonrpc.py", line 133, in _http_do
2014-02-07 21:08:51.553994 > raise Error_for_code(resp['error']['code'])(resp['error']['message'], resp['error'].get('data', None))
2014-02-07 21:08:51.554117 > p2pool.util.jsonrpc.NarrowError: -1 CreateNewBlock() : ConnectBlock failed

then it continues on its merry way. I've watched them both and this error occurs at the same time the devcoin error shows up. After this point, P2Pool is refused connection when it tries to connect again.

sidhujag

legendary

Activity: 2044

Merit: 1005

Quote from: nibyokwy on February 10, 2014, 09:08:31 AM

to help understand the code path, what is the setup of the pool that is testing it? i see it is p2pool but is it mining bitcoin as the primary with devcoin as a merge mine coin? or is this initial test mining with devcoin as the primary? if the latter, has getblocktemplate (which i assume p2pool is using) modified from the original bitcoin one at all? If the former, it will be using the getaux... paths.

There was a small change to template which matches bitcoin but wasnt in devcoin. When creatinh a block I set txout value to -fee in the template.. This could be the cause.

Why is it in bitcoin as -fee? I assumed it was something to do with the client checking to ensure sufficient balance before sending coins.

https://github.com/sidhujag/devcoin/search?q=-nFees&ref=cmdform

But this is in original commit and he said that one connects.. he should see rpccalls in the pool log to template code?

At the very least see the msg "running devcoin miner"?

nibyokwy

newbie

Activity: 51

Merit: 0

to help understand the code path, what is the setup of the pool that is testing it? i see it is p2pool but is it mining bitcoin as the primary with devcoin as a merge mine coin? or is this initial test mining with devcoin as the primary? if the latter, has getblocktemplate (which i assume p2pool is using) modified from the original bitcoin one at all? If the former, it will be using the getaux... paths.

sidhujag

legendary

Activity: 2044

Merit: 1005

Quote from: Hunterbunter on February 10, 2014, 08:31:29 AM

Quote from: sidhujag on February 10, 2014, 07:52:05 AM

if thats true lets follow original path Hunterbunter and see if we can single out the problem in the new client code..

You can run another node connected to the proxy which is connected to your server node.. I think your seeing problem right away when proxy wakes up and sees that a new miner is available? Using the builtin qt miner set generate=true will do this hopefully? With only one node connected it will be easier to identify issue..

Do you follow or should I write it up more clear? Im on my iphone and its 5am so if so Ill do it on desktop later.

Ok this is the bit I'm not following:

Another node as in another p2pool node separate to the one I've already set up? What do you mean by proxy?

The problem happens like this:

- I start the newest source devcoin daemon, it connects to network and syncs with the network just fine, at this point it ignores P2Pool requests. While it's still syncing, P2Pool has an error when it tries to access the devcoin daemon, which says "devcoin is still downloading blocks". When devcoin daemon is stopped, it just says "can't connect to devcoind daemon"
- When devcoin daemon is synced, it listens to the P2Pool request, but spits out that error below, and begins rejecting connections and disconnecting, and eventually terminates.
- The P2Pool carries on doing what it's doing, and just spits out a little error every now and then saying "can't talk to the devcoin daemon", but it can continue talking to the miners and the other daemons. It seems unaffected by whether the daemon is alive or dead.
- This happens on your newest code on github, but not on the 'initial devcoin based on bitcoin 0.8.5' commit e646ca6740862d6d5914d83b7e69bf31f95c25dc. On that commit, it seems to work normally (as in there are no errors, and the daemon doesn't terminate). I haven't found any blocks yet but that's probably just because of the relatively low hash power at the moment.

The devcoin daemon always complains with the same problem:

Code:

ERROR: CTransaction::CheckTransaction() : txout.nValue negative
ERROR: CheckBlock() : CheckTransaction failed

Does that help?

Yea it helps a bit...

You should usually sync up the node before turning on the pool but thats ok anyways it works around it. I did this test using local clients running talking to the merged mining proxy and it worked giving the getauxblock message.. it mined blocks.. so I will do that test again. Once we get passed that next step is to mine a block and confirm they are accepted.

sidhujag

legendary

Activity: 2044

Merit: 1005

Quote from: nibyokwy on February 10, 2014, 08:39:40 AM

Quote from: Hunterbunter on February 10, 2014, 08:31:29 AM

Does that help?

paste more of the log. is there a section before that showing details of a block submission? could there be a problem with the transactions in the coinbase related to the devcoin payouts that come from the file it regularly downloads?

that's another thing that probably needs testing. testing blocks found before and after the boundaries of new file data.

Glad we have another dev onboard!

I think there were forking changes in 0.8 btc so it may make sense to do a fresh cleanup of devcoin doing a fork.. that way p2psh, nversion fixes and malleability attacks arent possible... the code is rebased on 0.8.5 so it should work to mine with newer clients and old clients seem to sync up with new ones.

The question is if new client mines a block will it be accepted by old ones.. but if we are to plug security holes we should force users to move to new code as bitcoin did??

nibyokwy

newbie

Activity: 51

Merit: 0

Quote from: Hunterbunter on February 10, 2014, 08:31:29 AM

Does that help?

paste more of the log. is there a section before that showing details of a block submission? could there be a problem with the transactions in the coinbase related to the devcoin payouts that come from the file it regularly downloads?

that's another thing that probably needs testing. testing blocks found before and after the boundaries of new file data.

Hunterbunter

hero member

Activity: 994

Merit: 1000

Quote from: sidhujag on February 10, 2014, 07:52:05 AM

if thats true lets follow original path Hunterbunter and see if we can single out the problem in the new client code..

You can run another node connected to the proxy which is connected to your server node.. I think your seeing problem right away when proxy wakes up and sees that a new miner is available? Using the builtin qt miner set generate=true will do this hopefully? With only one node connected it will be easier to identify issue..

Do you follow or should I write it up more clear? Im on my iphone and its 5am so if so Ill do it on desktop later.

Ok this is the bit I'm not following:

Another node as in another p2pool node separate to the one I've already set up? What do you mean by proxy?

The problem happens like this:

- I start the newest source devcoin daemon, it connects to network and syncs with the network just fine, at this point it ignores P2Pool requests. While it's still syncing, P2Pool has an error when it tries to access the devcoin daemon, which says "devcoin is still downloading blocks". When devcoin daemon is stopped, it just says "can't connect to devcoind daemon"
- When devcoin daemon is synced, it listens to the P2Pool request, but spits out that error below, and begins rejecting connections and disconnecting, and eventually terminates.
- The P2Pool carries on doing what it's doing, and just spits out a little error every now and then saying "can't talk to the devcoin daemon", but it can continue talking to the miners and the other daemons. It seems unaffected by whether the daemon is alive or dead.
- This happens on your newest code on github, but not on the 'initial devcoin based on bitcoin 0.8.5' commit e646ca6740862d6d5914d83b7e69bf31f95c25dc. On that commit, it seems to work normally (as in there are no errors, and the daemon doesn't terminate). I haven't found any blocks yet but that's probably just because of the relatively low hash power at the moment.

The devcoin daemon always complains with the same problem:

Code:

ERROR: CTransaction::CheckTransaction() : txout.nValue negative
ERROR: CheckBlock() : CheckTransaction failed

Does that help?

Flam

sr. member

Activity: 368

Merit: 250

The problem is known since 2011.

It's just a "smart" move from Gox who sold some BTC of its client and then they will buy it back after the crash. Basic market manipulation.

unclejed613

newbie

Activity: 49

Merit: 0

Quote from: psybits on February 10, 2014, 03:54:26 AM

Judging by the massive buy support on Cryptsy for the current price of 0.00000111 and upwards (100 BTC or so) I would say we are about to see a massive movement upwards.

Value is up roughly 75-80% on yesterday and the buy support is there to keep it moving.

*This is not advice to invest - just my opinion*

edit: we are already up to 0.00000117 and still going up strong with phenomenal buy support. This is definitely a breakout in DVC value right now. It looks exactly like what happened to DOGE a couple of weeks ago - except the DVC sell orders are thinner so I expect DVC to go up more than DOGE did. Again this is just my opinion.

I wouldn't be selling any DVC right now - the current activity is definitely something of a different scale right now signalling massive movements upwards.

edit 2: The massive buy walls just disappeared - not sure what's going on Huh

i'm just letting the remainder of my bracketed sell orders "ride".... had 6 of them go through last night, averaging about 15% margin ... got 2 still waiting.... these are only 1000dvc each, part of a trading experiment... 15% margin in a month of running the experiment is not too bad.... better than when i traded stocks....

btw.... when the price is going up like this it's the wrong time to "invest"... the best time to invest is when the price is low....

nibyokwy

newbie

Activity: 51

Merit: 0

Quote from: nibyokwy on February 09, 2014, 06:24:05 PM

has the new devcoin client added any of the hard or soft forking options that the new bitcoin activates? what has it done with regards to:

* version 2 blocks. i believe devcoin currently uses version 1 coinbases. when version 2 coinbases were first used in bitcoin the client had code that would reject version 1 blocks when a majority of version 2 blocks existed in the last X blocks. this was later removed once the supermajority was met and i believe the current bitcoin code now rejects version 1 blocks.

* is p2sh activated? p2sh transactions are unsafe if the majority of miners don't run p2sh enabled clients.

* there was a fork during the 0.8 version of the client due to the change to leveldb and differing locking behavior to bdb in the older client. this caused a chainfork when the old client rejected blocks that the new client created due to size constraints. a patch was created for old clients to enable them to have better locking constraints to accept the unusual blocks from the new client. this issue will exist in devcoin if miners run old and new clients. it will be possible for new client operators to force a chain split.

i'm sure there are other differences. were fee policies changed?

Any response to this? Unthinkingbit, what are the plans with regards to forking changes in the new client? I see mention of difficulty changes and other things? Is devcoin going to change quite a bit?

sidhujag

legendary

Activity: 2044

Merit: 1005

Quote from: psybits on February 10, 2014, 07:42:57 AM

Quote from: sidhujag on February 10, 2014, 07:33:38 AM

If there is a real fix and mtgox claim stands even though this can be true:

https://bitcointalk.org/index.php?topic=456740.new#new

then we are at a hardfork.

Regardless by testing that the proxy connects to a miner with with new client and crashes with a miner running old client we can pretty much sum it up as a problem with code compatibility and not anything else.

Then since we will know its the code i can begin either the testnet route or debug statements using your setup as a test. If it will always crash at same spot it might be an easy fix..

If it crashes with new client and old client mining then it may still be the setup and not the code?

If we have to fork and new code (latest code in github) running connected to a miner asking the pool proxy for work runs smoothly then we can eliminate backwards compatbility and use new client as everyone switches.

Bitcoin is not hard forking. Mt Gox is full of crap. The developers have said the problem is not crippling to Bitcoin and is not even on their priority list (they are aware of it).

if thats true lets follow original path Hunterbunter and see if we can single out the problem in the new client code..

You can run another node connected to the proxy which is connected to your server node.. I think your seeing problem right away when proxy wakes up and sees that a new miner is available? Using the builtin qt miner set generate=true will do this hopefully? With only one node connected it will be easier to identify issue..

Do you follow or should I write it up more clear? Im on my iphone and its 5am so if so Ill do it on desktop later.

psybits

legendary

Activity: 1386

Merit: 1000

Quote from: sidhujag on February 10, 2014, 07:33:38 AM

If there is a real fix and mtgox claim stands even though this can be true:

https://bitcointalk.org/index.php?topic=456740.new#new

then we are at a hardfork.

Regardless by testing that the proxy connects to a miner with with new client and crashes with a miner running old client we can pretty much sum it up as a problem with code compatibility and not anything else.

Then since we will know its the code i can begin either the testnet route or debug statements using your setup as a test. If it will always crash at same spot it might be an easy fix..

If it crashes with new client and old client mining then it may still be the setup and not the code?

If we have to fork and new code (latest code in github) running connected to a miner asking the pool proxy for work runs smoothly then we can eliminate backwards compatbility and use new client as everyone switches.

Bitcoin is not hard forking. Mt Gox is full of crap. The developers have said the problem is not crippling to Bitcoin and is not even on their priority list (they are aware of it).

sidhujag

legendary

Activity: 2044

Merit: 1005

If there is a real fix and mtgox claim stands even though this can be true:

https://bitcointalk.org/index.php?topic=456740.new#new

then we are at a hardfork.

Regardless by testing that the proxy connects to a miner with with new client and crashes with a miner running old client we can pretty much sum it up as a problem with code compatibility and not anything else.

Then since we will know its the code i can begin either the testnet route or debug statements using your setup as a test. If it will always crash at same spot it might be an easy fix..

If it crashes with new client and old client mining then it may still be the setup and not the code?

If we have to fork and new code (latest code in github) running connected to a miner asking the pool proxy for work runs smoothly then we can eliminate backwards compatbility and use new client as everyone switches.

Hunterbunter

hero member

Activity: 994

Merit: 1000

Quote from: sidhujag on February 10, 2014, 06:54:57 AM

So since we are forking now anyways makes sense to start fresh with new wallet? Merged mining should now work when everyone is on newer client? We can also fix any fee stuff now decide what we want to do and also think about the difficulty algorithm to change back to bitcoin to speed up blockchain downloads aswell as easier to develop new devcoin clients...

Hunterbunter if we have only say a new
node trying to mine with the pool proxy and then you connect the proxy to the latest client will it request work properly? No crash? I assume so since both versions have same fee structure etc.

Did you figure out what the problem was?

I'm not sure I understand what you mean about the new node/pool proxy. Can you clarify?

sidhujag

legendary

Activity: 2044

Merit: 1005

So since we are forking now anyways makes sense to start fresh with new wallet? Merged mining should now work when everyone is on newer client? We can also fix any fee stuff now decide what we want to do and also think about the difficulty algorithm to change back to bitcoin to speed up blockchain downloads aswell as easier to develop new devcoin clients...

Hunterbunter if we have only say a new
node trying to mine with the pool proxy and then you connect the proxy to the latest client will it request work properly? No crash? I assume so since both versions have same fee structure etc.

Hunterbunter

hero member

Activity: 994

Merit: 1000

Quote from: sidhujag on February 10, 2014, 06:33:07 AM

anyone buy $100 btc? wow

I know right...it only happened on btc-e though.

Can I put a petition through to improve devtome's hosting? It's failing more often than being readable at the moment. Scotty is pooped.