nibyokwy
Newbie
 Offline
Activity: 51
Merit: 0
|
 |
February 10, 2014, 10:44:01 PM |
|
that simply means we start fresh from 0.8.6 and add in devcoin again and not worry about backwards compatibility. We only have 1 major pool to consider and this new one, so its just a matter of setting a date/time in the future and saying we are moving to a new codebase...
there is more than 1 pool to consider. i'm assuming you mean ghash.io but there are a bunch of other large miners as well. discus fish for example. eligius mines but doesn't distribute to miners. there are also many smaller pools and solo people mining devcoin. f we do follow this path, this would mean we follow bitcoins difficulty retargeting and all other specs, except the main devcoin differences like auxpow/reciever share system, to keep consistent and be able to reuse the tools of bitcoin, by adding in merged-mining capability similar to what I did with the android wallet... however the wallet took longer because of the difficulty algorithm which the code didn't have in mind to check previous set of blocks to average. Small things like this add up and will cause problems one day.
this would completely change the coin. it wouldn't be devcoin anymore. you'd be moving from a coin with no upper limit to a 21 million limit. from 50,000 reward to 25 reward that halves. so many changes it would be bad for those that have supported the coin believing such fundamentals wouldn't change. |
|
|
|
|
smeagol
Legendary
Offline
Activity: 1008
Merit: 1005
|
|
February 10, 2014, 11:10:01 PM |
|
The Devcoin Bounty page has been updated with the cryptocurrency convention speaker bounty, the devcoin payment processor bounty, the first mined block with sidhujag's daemon bounty, and the Blisterpool testing bounty. Please visit the site and verify that the aforementioned bounties are all accurate.
|
|
|
|
|
smeagol
Legendary
Offline
Activity: 1008
Merit: 1005
|
|
February 10, 2014, 11:12:38 PM |
|
When I made the 48 share bounty for the new client, I didn't know there were so many differences between the 0.3 codebase and the 0.8 codebase. Now I see that there's many things to do do, so I suggest boosting the bounty from 48 shares to 96 shares. The 48 shares have already been sent, so this would be a boost of 48 share in round 33. Any objections, or should something be changed?
48 shares isn't probably going to be as much next round as it would have been previously, in terms of the number of devcoins. Maybe increase the number? |
|
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
February 10, 2014, 11:20:42 PM |
|
that simply means we start fresh from 0.8.6 and add in devcoin again and not worry about backwards compatibility. We only have 1 major pool to consider and this new one, so its just a matter of setting a date/time in the future and saying we are moving to a new codebase...
there is more than 1 pool to consider. i'm assuming you mean ghash.io but there are a bunch of other large miners as well. discus fish for example. eligius mines but doesn't distribute to miners. there are also many smaller pools and solo people mining devcoin. f we do follow this path, this would mean we follow bitcoins difficulty retargeting and all other specs, except the main devcoin differences like auxpow/reciever share system, to keep consistent and be able to reuse the tools of bitcoin, by adding in merged-mining capability similar to what I did with the android wallet... however the wallet took longer because of the difficulty algorithm which the code didn't have in mind to check previous set of blocks to average. Small things like this add up and will cause problems one day.
this would completely change the coin. it wouldn't be devcoin anymore. you'd be moving from a coin with no upper limit to a 21 million limit. from 50,000 reward to 25 reward that halves. so many changes it would be bad for those that have supported the coin believing such fundamentals wouldn't change. No I meant keep everything else except core devcoin features, the reciever share system, block reward and merged-mining were the main differences. |
|
|
|
|
ranlo
Legendary
Offline
Activity: 1974
Merit: 1007
|
|
February 10, 2014, 11:21:33 PM |
|
When I made the 48 share bounty for the new client, I didn't know there were so many differences between the 0.3 codebase and the 0.8 codebase. Now I see that there's many things to do do, so I suggest boosting the bounty from 48 shares to 96 shares. The 48 shares have already been sent, so this would be a boost of 48 share in round 33. Any objections, or should something be changed?
48 shares isn't probably going to be as much next round as it would have been previously, in terms of the number of devcoins. Maybe increase the number? I'd say wait. People may drop off now that the rewards are lower (as we've seen in the past, as rewards drop, people stop. As rewards get bigger, people jump back on). Don't make any assumptions yet. |
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
February 10, 2014, 11:22:48 PM |
|
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). 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=cmdformBut 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? Hey I pushed a change, can you see if it still crashes? |
|
|
|
|
cdelatorref
Newbie
Offline
Activity: 50
Merit: 0
|
|
February 10, 2014, 11:24:41 PM
Last edit: February 10, 2014, 11:39:07 PM by cdelatorref |
|
The Devcoin Bounty page has been updated with the cryptocurrency convention speaker bounty, the devcoin payment processor bounty, the first mined block with sidhujag's daemon bounty, and the Blisterpool testing bounty. Please visit the site and verify that the aforementioned bounties are all accurate. Hello! I sent you a PM regarding the "Hunterbunter Pool Testing (Blisterpool)" I think I'm the first one to fulfill the duty! Edit: I sent the PM to somebody else, I sent you a message regarding the mining Business bounty, anyway I'm sending you a PM regarding the pool now. |
|
|
|
|
|
Hunterbunter
|
|
February 11, 2014, 12:32:59 AM |
|
Looking at the code the CreateNewBlock gets called but txout nvalue can be negative either through a rounding error or if say the reciever file is messed up. It goes through all reciever entries to calculate value for each address. Does the receiver value exist? The latest one in the data dir? if its synced up you should have last rounds receiver file.
Id like to know the latest reciever file you have and that if its valid. I can try to replicate the scenario on my end then by doing local mining through the merged mining proxy with the same reciever file to see if it throws the same error...
Seems like it may be a problem with a txout entry in one of the blocks the
node has... Almost like its better to delete the data directory and let it sync again to ensure you have all valid blocks until you turn on the pool.. but you already did this you said.. so Ill try it on my end.
Also is it possible to turn off the other coins amd just have devcoin node running? Maybe some other coins are usingthe same rpc port and its a case of mistaken identity.. check that all the conf files have different rpcports defined.
Hey I pushed a change, can you see if it still crashes?
Yep just pulled it, compiling now. It's definitely not a port issue, triple checked that one. I did notice something odd in the receiver folder. I'm running the 0.8.5 commit from two months ago atm, and it's only downloaded up to receiver_31.csv. I'll run the new master once it's compiled as a second daemon with it's own folder and let it fully sync to see if it produces anything, then I'll switch p2pool over to use that instead (on a new port, of course) and see what happens. EDIT: It's started running as a second process, and I've noticed this most times that the daemons run...is this normal? Downloading receiver_0.csv base file./home/amit/.devcoinMaster/receiver/receiver_0.csv
Number of pages in getCommonOutputByText: 5
Number of identical pages in getCommonOutputByText: 5
No coin addresses were found, there may be something wrong with the receiver_x.csv files.
It then continues seemingly fine. |
|
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
February 11, 2014, 12:55:15 AM |
|
Looking at the code the CreateNewBlock gets called but txout nvalue can be negative either through a rounding error or if say the reciever file is messed up. It goes through all reciever entries to calculate value for each address. Does the receiver value exist? The latest one in the data dir? if its synced up you should have last rounds receiver file.
Id like to know the latest reciever file you have and that if its valid. I can try to replicate the scenario on my end then by doing local mining through the merged mining proxy with the same reciever file to see if it throws the same error...
Seems like it may be a problem with a txout entry in one of the blocks the
node has... Almost like its better to delete the data directory and let it sync again to ensure you have all valid blocks until you turn on the pool.. but you already did this you said.. so Ill try it on my end.
Also is it possible to turn off the other coins amd just have devcoin node running? Maybe some other coins are usingthe same rpc port and its a case of mistaken identity.. check that all the conf files have different rpcports defined.
Hey I pushed a change, can you see if it still crashes?
Yep just pulled it, compiling now. It's definitely not a port issue, triple checked that one. I did notice something odd in the receiver folder. I'm running the 0.8.5 commit from two months ago atm, and it's only downloaded up to receiver_31.csv. I'll run the new master once it's compiled as a second daemon with it's own folder and let it fully sync to see if it produces anything, then I'll switch p2pool over to use that instead (on a new port, of course) and see what happens. EDIT: It's started running as a second process, and I've noticed this most times that the daemons run...is this normal? Downloading receiver_0.csv base file./home/amit/.devcoinMaster/receiver/receiver_0.csv
Number of pages in getCommonOutputByText: 5
Number of identical pages in getCommonOutputByText: 5
No coin addresses were found, there may be something wrong with the receiver_x.csv files.
It then continues seemingly fine. Does the second daemon also have its own data directory? Also different rpc ports obviously? Sometimes the receiver files may not download correctly you can delete it and it should redownload the reciever file... but no it shouldnt say that.. Ive got the latest one mining after seeing the same issue as you.. its running local mining using setgenerate true.. However I dont have a new graphics card so hard to try to run the merged mine proxy via any available bitcoin miners. Guiminer said devcoin not connected to me.. But once you get setup it should be quick to see if minimg is working I think. |
|
|
|
|
|
Hunterbunter
|
|
February 11, 2014, 01:24:39 AM |
|
Does the second daemon also have its own data directory? Also different rpc ports obviously?
Sometimes the receiver files may not download correctly you can delete it and it should redownload the reciever file... but no it shouldnt say that..
Ive got the latest one mining after seeing the same issue as you.. its running local mining using setgenerate true.. However I dont have a new graphics card so hard to try to run the merged mine proxy via any available bitcoin miners. Guiminer said devcoin not connected to me.. But once you get setup it should be quick to see if minimg is working I think.
Yeah something really confusing just happened. I've got both daemons running, with separate configs using different ports pointing to seperate data folders...and both directories are full of data...but they're using the same wallet. eg ps aux:
amit 739 36.7 2.1 977472 80660 ? SLsl 19:40 12:40 /usr/local/bin/devcoindMaster -daemon -conf=/home/amit/.devcoinMaster/devcoinMaster.conf -datadir=/home/amit/.devcoinMaster/
amit 26498 0.6 2.1 1180880 81492 ? SLsl 01:49 7:01 /usr/local/bin/devcoind -daemon -conf=/home/amit/.devcoin/devcoin.conf -datadir=/home/amit/.devcoin/
cat .devcoin/devcoin.conf
rpcuser=blah
rpcpassword=blah
port=52333
rpcport=52332
rpcallowip=198.57.46.116
cat .devcoinMaster/devcoinMaster.conf
rpcuser=blah
rpcpassword=blah
port=52335
rpcport=52334
rpcallowip=198.57.46.116
Wallets:
amit@protium:~$ devcoind getaddressesbyaccount ""
[
"1CkZ81JGDkrWvSd3w9STmg7A57QbLjR6kJ",
"15FAdcX8P3Cre2wEFnDjpBUjTY8QJ37QpN"
]
amit@protium:~$ devcoindMaster getaddressesbyaccount ""
[
"1CkZ81JGDkrWvSd3w9STmg7A57QbLjR6kJ",
"15FAdcX8P3Cre2wEFnDjpBUjTY8QJ37QpN"
They're definitely running separately, because if I watch both debug logs at the same time, they're doing completely different things. 0.8.5 devcoin currently being used by p2pool: tail -f .devcoin/debug.log
ERROR: CTxMemPool::accept() : not enough fees 618ac46cff6101ff919b7be2e664d8d9d0a10c1ddbee1fd447517c5863a4581d, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees 7f4755bd506852f816a5f1a54c8fa9476a8dcb224525822593eaff6a6f59a153, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees 2c2a96245d39073afff7604c91ab25724635bff804ba3b0bf1415f23fb0546f6, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees 156e4e11bbbbf2159b45c51ebd36a4b94aaf0eeb1999cef089d826f6ed0404e9, 100000000 < 600000000
ERROR: CTxMemPool::accept() : nonstandard transaction type
ERROR: CTxMemPool::accept() : nonstandard transaction type
getblocks 117878 to 6080d430e8ca32743e5a2ffb4352594bc9fb15826acac070d3f1eded2ec79af6 limit 500
getblocks stopping at limit 118377 e38353455b6fe568645dd0cc6fdbca9ffd1f6175ef11723491fa4f39fc89e93a
received getdata (500 invsz)
ERROR: CTxMemPool::accept() : not enough fees 9a8c263d72c12503fccb7304338cf3a9330802df72ab4e655414d42ed9a54809, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees b73fcdbbb882ecae89244756e5b59d12df664a6803e21ed14d3942617178c804, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees 295b5407d2836f1e30f49f17c2f91182aa13bf92d36dffa0e2ad63552cd98a94, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees 4a5732f3b3926352921836cb7c2fcbcaeb7ab854f1f19c94c1135b8724317ff1, 100000000 < 600000000
getblocks 118378 to 6080d430e8ca32743e5a2ffb4352594bc9fb15826acac070d3f1eded2ec79af6 limit 500
getblocks stopping at limit 118877 0e81dc24f614eecc06a1dd959dfef7c347d6239067abab9de40fb961b7f27cbb
received getdata (500 invsz)
ERROR: CTxMemPool::accept() : not enough fees 44f1857bdccca45f51131b020f69eda8260485331a28e5bc9325355da5fcbcae, 100000000 < 600000000
ThreadRPCServer method=getinfo
keypool reserve 4
keypool return 4
ERROR: CTxMemPool::accept() : nonstandard transaction type
ERROR: CTxMemPool::accept() : not enough fees a0338e6a1673dee123532a94e199ab16791ad1449080670026533961bfbb0b87, 100000000 < 1550000000
ERROR: CTxMemPool::accept() : not enough fees 42d281cdc71b44657aaeb2c99574477903f5455cd7fc973c9a37e861881c8fde, 100000000 < 600000000
getblocks 118878 to 6080d430e8ca32743e5a2ffb4352594bc9fb15826acac070d3f1eded2ec79af6 limit 500
getblocks stopping at limit 119377 39e04d51dafc418ce99557b8729ef83c6470347ebbdc46ad58a022e1b654efea
received getdata (500 invsz)
ERROR: CTxMemPool::accept() : not enough fees 618ac46cff6101ff919b7be2e664d8d9d0a10c1ddbee1fd447517c5863a4581d, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees 7f4755bd506852f816a5f1a54c8fa9476a8dcb224525822593eaff6a6f59a153, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees 2c2a96245d39073afff7604c91ab25724635bff804ba3b0bf1415f23fb0546f6, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees 156e4e11bbbbf2159b45c51ebd36a4b94aaf0eeb1999cef089d826f6ed0404e9, 100000000 < 600000000
ERROR: CTxMemPool::accept() : nonstandard transaction type
ERROR: CTxMemPool::accept() : nonstandard transaction type
ERROR: CTxMemPool::accept() : nonstandard transaction type
Added 1 addresses from 54.249.112.25: 280 tried, 3671 new
ERROR: CTxMemPool::accept() : not enough fees 9a8c263d72c12503fccb7304338cf3a9330802df72ab4e655414d42ed9a54809, 100000000 < 600000000
devcoin master daemon, running alone tail -f .devcoinMaster/debug.log
Added 7 addresses from 198.204.232.58: 9 tried, 1286 new
CTxMemPool::accept() : accepted a0338e6a1673dee123532a94e199ab16791ad1449080670026533961bfbb0b87 (poolsz 8)
CTxMemPool::accept() : accepted 4a5732f3b3926352921836cb7c2fcbcaeb7ab854f1f19c94c1135b8724317ff1 (poolsz 9)
CTxMemPool::accept() : accepted 38a8e0ae561d9bf763546b056ecd08fe36a62f2ef7e9138e48b8497daa47b00f (poolsz 10)
CTxMemPool::accept() : accepted 295b5407d2836f1e30f49f17c2f91182aa13bf92d36dffa0e2ad63552cd98a94 (poolsz 11)
CTxMemPool::accept() : accepted 42d281cdc71b44657aaeb2c99574477903f5455cd7fc973c9a37e861881c8fde (poolsz 12)
CTxMemPool::accept() : accepted 9a8c263d72c12503fccb7304338cf3a9330802df72ab4e655414d42ed9a54809 (poolsz 13)
Added 1 addresses from 198.204.232.58: 9 tried, 1287 new
CTxMemPool::accept() : accepted 1005ec307b7b3adb9f0eb14721eeac566e942cde2cff5e10ee4b39ac800d2c47 (poolsz 14)
CTxMemPool::accept() : accepted 7f4755bd506852f816a5f1a54c8fa9476a8dcb224525822593eaff6a6f59a153 (poolsz 15)
CTxMemPool::accept() : accepted 9526556699e582f8b300449963f1dcb6d8bd0e594644033f36333662aba60c29 (poolsz 16)
a lot less happening with this one. So, I guess I'll shut down the 0.8.5 one and get p2pool to use the master. Will report. EDIT: yeah they weren't working well together, devcoin master didn't really get the block chain and was just hijacking devcoind's stuff. |
|
|
|
|
|
novacadian
|
|
February 11, 2014, 01:29:11 AM |
|
48 shares isn't probably going to be as much next round as it would have been previously, in terms of the number of devcoins. Maybe increase the number?
Would that go for other such bounties at the brink of completion, like the Forum Bounties? What's good for the goose is good for the gander. - Nova |
DVC Address : 1EfsiVUECqmR5Qx7C4PkmwadDXYuSGzssL
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
February 11, 2014, 01:41:43 AM |
|
Does the second daemon also have its own data directory? Also different rpc ports obviously?
Sometimes the receiver files may not download correctly you can delete it and it should redownload the reciever file... but no it shouldnt say that..
Ive got the latest one mining after seeing the same issue as you.. its running local mining using setgenerate true.. However I dont have a new graphics card so hard to try to run the merged mine proxy via any available bitcoin miners. Guiminer said devcoin not connected to me.. But once you get setup it should be quick to see if minimg is working I think.
Yeah something really confusing just happened. I've got both daemons running, with separate configs using different ports pointing to seperate data folders...and both directories are full of data...but they're using the same wallet. eg ps aux:
amit 739 36.7 2.1 977472 80660 ? SLsl 19:40 12:40 /usr/local/bin/devcoindMaster -daemon -conf=/home/amit/.devcoinMaster/devcoinMaster.conf -datadir=/home/amit/.devcoinMaster/
amit 26498 0.6 2.1 1180880 81492 ? SLsl 01:49 7:01 /usr/local/bin/devcoind -daemon -conf=/home/amit/.devcoin/devcoin.conf -datadir=/home/amit/.devcoin/
cat .devcoin/devcoin.conf
rpcuser=blah
rpcpassword=blah
port=52333
rpcport=52332
rpcallowip=198.57.46.116
cat .devcoinMaster/devcoinMaster.conf
rpcuser=blah
rpcpassword=blah
port=52335
rpcport=52334
rpcallowip=198.57.46.116
Wallets:
amit@protium:~$ devcoind getaddressesbyaccount ""
[
"1CkZ81JGDkrWvSd3w9STmg7A57QbLjR6kJ",
"15FAdcX8P3Cre2wEFnDjpBUjTY8QJ37QpN"
]
amit@protium:~$ devcoindMaster getaddressesbyaccount ""
[
"1CkZ81JGDkrWvSd3w9STmg7A57QbLjR6kJ",
"15FAdcX8P3Cre2wEFnDjpBUjTY8QJ37QpN"
They're definitely running separately, because if I watch both debug logs at the same time, they're doing completely different things. 0.8.5 devcoin currently being used by p2pool: tail -f .devcoin/debug.log
ERROR: CTxMemPool::accept() : not enough fees 618ac46cff6101ff919b7be2e664d8d9d0a10c1ddbee1fd447517c5863a4581d, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees 7f4755bd506852f816a5f1a54c8fa9476a8dcb224525822593eaff6a6f59a153, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees 2c2a96245d39073afff7604c91ab25724635bff804ba3b0bf1415f23fb0546f6, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees 156e4e11bbbbf2159b45c51ebd36a4b94aaf0eeb1999cef089d826f6ed0404e9, 100000000 < 600000000
ERROR: CTxMemPool::accept() : nonstandard transaction type
ERROR: CTxMemPool::accept() : nonstandard transaction type
getblocks 117878 to 6080d430e8ca32743e5a2ffb4352594bc9fb15826acac070d3f1eded2ec79af6 limit 500
getblocks stopping at limit 118377 e38353455b6fe568645dd0cc6fdbca9ffd1f6175ef11723491fa4f39fc89e93a
received getdata (500 invsz)
ERROR: CTxMemPool::accept() : not enough fees 9a8c263d72c12503fccb7304338cf3a9330802df72ab4e655414d42ed9a54809, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees b73fcdbbb882ecae89244756e5b59d12df664a6803e21ed14d3942617178c804, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees 295b5407d2836f1e30f49f17c2f91182aa13bf92d36dffa0e2ad63552cd98a94, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees 4a5732f3b3926352921836cb7c2fcbcaeb7ab854f1f19c94c1135b8724317ff1, 100000000 < 600000000
getblocks 118378 to 6080d430e8ca32743e5a2ffb4352594bc9fb15826acac070d3f1eded2ec79af6 limit 500
getblocks stopping at limit 118877 0e81dc24f614eecc06a1dd959dfef7c347d6239067abab9de40fb961b7f27cbb
received getdata (500 invsz)
ERROR: CTxMemPool::accept() : not enough fees 44f1857bdccca45f51131b020f69eda8260485331a28e5bc9325355da5fcbcae, 100000000 < 600000000
ThreadRPCServer method=getinfo
keypool reserve 4
keypool return 4
ERROR: CTxMemPool::accept() : nonstandard transaction type
ERROR: CTxMemPool::accept() : not enough fees a0338e6a1673dee123532a94e199ab16791ad1449080670026533961bfbb0b87, 100000000 < 1550000000
ERROR: CTxMemPool::accept() : not enough fees 42d281cdc71b44657aaeb2c99574477903f5455cd7fc973c9a37e861881c8fde, 100000000 < 600000000
getblocks 118878 to 6080d430e8ca32743e5a2ffb4352594bc9fb15826acac070d3f1eded2ec79af6 limit 500
getblocks stopping at limit 119377 39e04d51dafc418ce99557b8729ef83c6470347ebbdc46ad58a022e1b654efea
received getdata (500 invsz)
ERROR: CTxMemPool::accept() : not enough fees 618ac46cff6101ff919b7be2e664d8d9d0a10c1ddbee1fd447517c5863a4581d, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees 7f4755bd506852f816a5f1a54c8fa9476a8dcb224525822593eaff6a6f59a153, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees 2c2a96245d39073afff7604c91ab25724635bff804ba3b0bf1415f23fb0546f6, 100000000 < 600000000
ERROR: CTxMemPool::accept() : not enough fees 156e4e11bbbbf2159b45c51ebd36a4b94aaf0eeb1999cef089d826f6ed0404e9, 100000000 < 600000000
ERROR: CTxMemPool::accept() : nonstandard transaction type
ERROR: CTxMemPool::accept() : nonstandard transaction type
ERROR: CTxMemPool::accept() : nonstandard transaction type
Added 1 addresses from 54.249.112.25: 280 tried, 3671 new
ERROR: CTxMemPool::accept() : not enough fees 9a8c263d72c12503fccb7304338cf3a9330802df72ab4e655414d42ed9a54809, 100000000 < 600000000
devcoin master daemon, running alone tail -f .devcoinMaster/debug.log
Added 7 addresses from 198.204.232.58: 9 tried, 1286 new
CTxMemPool::accept() : accepted a0338e6a1673dee123532a94e199ab16791ad1449080670026533961bfbb0b87 (poolsz 8)
CTxMemPool::accept() : accepted 4a5732f3b3926352921836cb7c2fcbcaeb7ab854f1f19c94c1135b8724317ff1 (poolsz 9)
CTxMemPool::accept() : accepted 38a8e0ae561d9bf763546b056ecd08fe36a62f2ef7e9138e48b8497daa47b00f (poolsz 10)
CTxMemPool::accept() : accepted 295b5407d2836f1e30f49f17c2f91182aa13bf92d36dffa0e2ad63552cd98a94 (poolsz 11)
CTxMemPool::accept() : accepted 42d281cdc71b44657aaeb2c99574477903f5455cd7fc973c9a37e861881c8fde (poolsz 12)
CTxMemPool::accept() : accepted 9a8c263d72c12503fccb7304338cf3a9330802df72ab4e655414d42ed9a54809 (poolsz 13)
Added 1 addresses from 198.204.232.58: 9 tried, 1287 new
CTxMemPool::accept() : accepted 1005ec307b7b3adb9f0eb14721eeac566e942cde2cff5e10ee4b39ac800d2c47 (poolsz 14)
CTxMemPool::accept() : accepted 7f4755bd506852f816a5f1a54c8fa9476a8dcb224525822593eaff6a6f59a153 (poolsz 15)
CTxMemPool::accept() : accepted 9526556699e582f8b300449963f1dcb6d8bd0e594644033f36333662aba60c29 (poolsz 16)
a lot less happening with this one. So, I guess I'll shut down the 0.8.5 one and get p2pool to use the master. Will report. EDIT: yeah they weren't working well together, devcoin master didn't really get the block chain and was just hijacking devcoind's stuff. yea I would run one at a time. The 0.8.5 didnt really have the right fee structure so it makes sense that it shows not enough fees. The master should fix that. Its good that there are no errors and tx are accepted.. howver when mining it should show messages like work accepted etc.. |
|
|
|
|
|
Hunterbunter
|
|
February 11, 2014, 01:47:22 AM |
|
Ok so the new master seems to be talking to p2pool ok, no errors or terminating, but I'm not getting receiver_32.csv...although I'm not getting that in my desktop either, so I'm going to guess that's normal. In which case, looks like whatever was causing the crash is fixed! What was it? Now to find a block... Out of curiousity what does this bit mean? Is the work accepted thing you mentioned? (in debug.log) received block 6196c1a5f9eb5abaeae99c563be650854d1fde02b9c3b43f97485b16917a84fc
Committing 2 changed transactions to coin database...
SetBestChain: new best=6196c1a5f9eb5abaeae99c563be650854d1fde02b9c3b43f97485b16917a84fc height=125519 log2_work=75.179576 tx=226630 date=2014-02-11 01:40:42 progress=0.072467
ProcessBlock: ACCEPTED
coinAddressStrings: 1
Address 1Emfox1WswYcd2YucUskRzqfRWKkcm1Jut valid, value 4500000000000, minerValue 500000000000
received getdata for: block 6196c1a5f9eb5abaeae99c563be650854d1fde02b9c3b43f97485b16917a84fc
EDIT: lol I just noticed that's Emfox's address...coincidence? or is that just processing the generation shares and it's not p2pool related? |
|
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
February 11, 2014, 01:53:13 AM |
|
Ok so the new master seems to be talking to p2pool ok, no errors or terminating, but I'm not getting receiver_32.csv...although I'm not getting that in my desktop either, so I'm going to guess that's normal. In which case, looks like whatever was causing the crash is fixed! What was it? Now to find a block... Out of curiousity what does this bit mean? Is the work accepted thing you mentioned? (in debug.log) received block 6196c1a5f9eb5abaeae99c563be650854d1fde02b9c3b43f97485b16917a84fc
Committing 2 changed transactions to coin database...
SetBestChain: new best=6196c1a5f9eb5abaeae99c563be650854d1fde02b9c3b43f97485b16917a84fc height=125519 log2_work=75.179576 tx=226630 date=2014-02-11 01:40:42 progress=0.072467
ProcessBlock: ACCEPTED
coinAddressStrings: 1
Address 1Emfox1WswYcd2YucUskRzqfRWKkcm1Jut valid, value 4500000000000, minerValue 500000000000
received getdata for: block 6196c1a5f9eb5abaeae99c563be650854d1fde02b9c3b43f97485b16917a84fc
Utb had told me to change a pointer to txout to use the same variable that the reciever stuff was using.. in theory a pointer is a pointer and should reflectthe change but it wasnt updating the block txout.. soon as the function is done it lost txout values.. they were undefined hence negative. Really txout should be unsigned int but I dont think we have uint64 or most fuctions use int64 so I do an extra check also for sanity when applying the receiver shares to make sure they dont go negative... I added some printfs to see the tx value as you can see its 45000 coins which is right. So far I dont see it doing any work but maybe it only shows that on the miner and pool.. the pool should also have some log info once a miner is doing work.. we will needd more hash to throw at it to help solve a block. I doubt round 32 csv has been uploaded yet.. that would explain why you dont have it.. it just finished the other day. |
|
|
|
|
|
Unthinkingbit
|
|
February 11, 2014, 02:06:31 AM |
|
Ok so the new master seems to be talking to p2pool ok, no errors or terminating, but I'm not getting receiver_32.csv...although I'm not getting that in my desktop either, so I'm going to guess that's normal.
..
Receiver_32 will be downloaded after block 126,999: http://www.devtome.com/doku.php?id=devcoin#client_procedurewhich would be after February 19. ..
Utb had told me to change a pointer to txout to use the same variable that the reciever stuff was using.. in theory a pointer is a pointer and should reflectthe change but it wasnt updating the block txout.. soon as the function is done it lost txout values.. they were undefined hence negative.
The pointer should be the same, but you can set it to Twobits' version to see if that changes anything. |
|
|
|
|
Hunterbunter
|
|
February 11, 2014, 02:34:59 AM |
|
Ah ok good to know.
P2Pool only really says "Got new merged mining work!" but who knows what that means or from who. The rest is just pool stats and 'new work for worker!' statements, with a few peer statements. When it finds a block or a miner gets a share it makes an announcement too, but there's very little in the way of merged mining stuff.
I'm finding it very hard to get hash power...few people want to join a small pool, plus a lot of smaller miners are turned off from p2pool because of the low probability of getting a share. I must admit, the 10k daily bonus payout isn't really very much either, what's an attractive figure? 100k? I'd be hard pressed to keep that up for very long...maybe I can try it for a month and spam some ads around. I've found some people are unreasonably hostile when you talk about new mining pools...they want everyone to join the one they're on, I guess.
The pool has found 2 blocks which a miner got a share from, but I think the amount was too small for the pool to get its 1%, unless I'm doing something wrong. I'll switch to 0% for now since that might be a hollow barrier.
|
|
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
February 11, 2014, 02:55:59 AM |
|
Ah ok good to know.
P2Pool only really says "Got new merged mining work!" but who knows what that means or from who. The rest is just pool stats and 'new work for worker!' statements, with a few peer statements. When it finds a block or a miner gets a share it makes an announcement too, but there's very little in the way of merged mining stuff.
I'm finding it very hard to get hash power...few people want to join a small pool, plus a lot of smaller miners are turned off from p2pool because of the low probability of getting a share. I must admit, the 10k daily bonus payout isn't really very much either, what's an attractive figure? 100k? I'd be hard pressed to keep that up for very long...maybe I can try it for a month and spam some ads around. I've found some people are unreasonably hostile when you talk about new mining pools...they want everyone to join the one they're on, I guess.
The pool has found 2 blocks which a miner got a share from, but I think the amount was too small for the pool to get its 1%, unless I'm doing something wrong. I'll switch to 0% for now since that might be a hollow barrier.
Your running multiple chains? So that got new merged minign work could be from other coins? Would be nice to somehow know if its devcoin we're talkin gabout. How will we know that we've mined a block anyway? The pool stats will show with the hash? |
|
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
February 11, 2014, 03:04:53 AM |
|
Ok so the new master seems to be talking to p2pool ok, no errors or terminating, but I'm not getting receiver_32.csv...although I'm not getting that in my desktop either, so I'm going to guess that's normal.
..
Receiver_32 will be downloaded after block 126,999: http://www.devtome.com/doku.php?id=devcoin#client_procedurewhich would be after February 19. ..
Utb had told me to change a pointer to txout to use the same variable that the reciever stuff was using.. in theory a pointer is a pointer and should reflectthe change but it wasnt updating the block txout.. soon as the function is done it lost txout values.. they were undefined hence negative.
The pointer should be the same, but you can set it to Twobits' version to see if that changes anything.That is what it is set to now... I think pblock->vtx.push_back(txNew); "probably" creates a copy of the pointer. and any changes to txNew afterwards are then not reflected, hence why the pblock->vtx[0].vout[0].nValue = minerValue + nFees; needs to stay there instead of txNew.vout[0].nValue = minerValue + nFees; |
|
|
|
|
|
emfox
|
|
February 11, 2014, 03:29:09 AM |
|
Ok so the new master seems to be talking to p2pool ok, no errors or terminating, but I'm not getting receiver_32.csv...although I'm not getting that in my desktop either, so I'm going to guess that's normal. In which case, looks like whatever was causing the crash is fixed! What was it? Now to find a block... Out of curiousity what does this bit mean? Is the work accepted thing you mentioned? (in debug.log) received block 6196c1a5f9eb5abaeae99c563be650854d1fde02b9c3b43f97485b16917a84fc
Committing 2 changed transactions to coin database...
SetBestChain: new best=6196c1a5f9eb5abaeae99c563be650854d1fde02b9c3b43f97485b16917a84fc height=125519 log2_work=75.179576 tx=226630 date=2014-02-11 01:40:42 progress=0.072467
ProcessBlock: ACCEPTED
coinAddressStrings: 1
Address 1Emfox1WswYcd2YucUskRzqfRWKkcm1Jut valid, value 4500000000000, minerValue 500000000000
received getdata for: block 6196c1a5f9eb5abaeae99c563be650854d1fde02b9c3b43f97485b16917a84fc
EDIT: lol I just noticed that's Emfox's address...coincidence? or is that just processing the generation shares and it's not p2pool related? lol, nothing about me I think. that's my address, but I use a different address when I register your site, so it's not the mining affairs. |
Earn Devcoins by WritingBTC: 1Emfox1WswYcd2YucUskRzqfRWKkcm1Jut DVC: 1Emfox1WswYcd2YucUskRzqfRWKkcm1Jut IXC: xnRKo3qSDdcPJ4pgTLER3orkquUVQXeLwf
|
|
|
sidhujag
Legendary
Offline
Activity: 2044
Merit: 1005
|
|
February 11, 2014, 03:31:25 AM |
|
Ok so the new master seems to be talking to p2pool ok, no errors or terminating, but I'm not getting receiver_32.csv...although I'm not getting that in my desktop either, so I'm going to guess that's normal. In which case, looks like whatever was causing the crash is fixed! What was it? Now to find a block... Out of curiousity what does this bit mean? Is the work accepted thing you mentioned? (in debug.log) received block 6196c1a5f9eb5abaeae99c563be650854d1fde02b9c3b43f97485b16917a84fc
Committing 2 changed transactions to coin database...
SetBestChain: new best=6196c1a5f9eb5abaeae99c563be650854d1fde02b9c3b43f97485b16917a84fc height=125519 log2_work=75.179576 tx=226630 date=2014-02-11 01:40:42 progress=0.072467
ProcessBlock: ACCEPTED
coinAddressStrings: 1
Address 1Emfox1WswYcd2YucUskRzqfRWKkcm1Jut valid, value 4500000000000, minerValue 500000000000
received getdata for: block 6196c1a5f9eb5abaeae99c563be650854d1fde02b9c3b43f97485b16917a84fc
EDIT: lol I just noticed that's Emfox's address...coincidence? or is that just processing the generation shares and it's not p2pool related? lol, nothing about me I think. that's my address, but I use a different address when I register your site, so it's not the mining affairs. Must be paying emfox 45k coins |
|
|
|
|
|
