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

markm

legendary

Activity: 2940

Merit: 1090

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

Using the builtin qt miner set generate=true will do this hopefully? With only one node connected it will be easier to identify issue..

In the QT client we deliberately disabled mining because it caused crashes, something in the QT was not thread-safe it seemed but we did not know enough about QT's threading and such to even figure out what exactly was happening. Since CPU mining was already pretty much obsolete (I thought that recent bitcoin code doesn't even have generate=1 anymore itself?) we just turned off the ability to set generate true figuring people who want to mine would in any case be using the daemon not the GUI.

-MarkM-

novacadian

full member

Activity: 232

Merit: 104

Quote from: nahtnam on February 10, 2014, 11:13:52 PM

Quote from: nahtnam on February 06, 2014, 09:24:35 PM

I heard the devcoin team is making a SMF plugin that allows users to tip each other DVC? Is that true? If yes, then where can I find more info?

Is this true?

Perhaps it is the proposed challenge response system for the SMF email capability which you have heard about. The final challenge response system will require a small DVC payment. Other than that nothing comes to mind.

The project bounties are outlined at http://www.devtome.com/doku.php?id=devcoin_bounty_now in case it is something that may have missed my attention.

- Nova

Unthinkingbit

hero member

Activity: 935

Merit: 1015

Quote from: nibyokwy on February 10, 2014, 10:50:16 PM

Quote from: sidhujag on February 10, 2014, 10:04:53 PM

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;

you are correct. 'vtx' is a vector of CTransaction and these are copied by value, not pointers. Changes to txNew after that push don't get reflected in the copy stored in vtx.

Thank you Sidhujag for catching that and Nibyokwy for confirming it. I corrected the code snippet at:
http://www.devtome.com/doku.php?id=devcoin#create_block

nahtnam

legendary

Activity: 1092

Merit: 1000

nahtnam.com

Quote from: nahtnam on February 06, 2014, 09:24:35 PM

I heard the devcoin team is making a SMF plugin that allows users to tip each other DVC? Is that true? If yes, then where can I find more info?

Is this true?

nibyokwy

newbie

Activity: 51

Merit: 0

Quote from: sidhujag on February 10, 2014, 10:04:53 PM

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;

you are correct. 'vtx' is a vector of CTransaction and these are copied by value, not pointers. Changes to txNew after that push don't get reflected in the copy stored in vtx.

Hunterbunter

hero member

Activity: 994

Merit: 1000

Quote from: sidhujag on February 10, 2014, 09:55:59 PM

Quote from: Hunterbunter on February 10, 2014, 09:34:59 PM

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?

Yeah a datadir/chain for each alt-coin...is that what you mean?

Yeah that could be from any of the alt-coins. The only way I think I'm going to tell is if p2pool makes an announcement (not sure if it will), or I get a balance on one of the daemons. If I see 5k from devcoins I'll be happy puppy...could take a bit of time tho.

sidhujag

legendary

Activity: 2044

Merit: 1005

Quote from: emfox on February 10, 2014, 10:29:09 PM

Quote from: Hunterbunter on February 10, 2014, 08:47:22 PM

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)

Code:

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

emfox

full member

Activity: 276

Merit: 102

Quote from: Hunterbunter on February 10, 2014, 08:47:22 PM

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)

Code:

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.

sidhujag

legendary

Activity: 2044

Merit: 1005

Quote from: Unthinkingbit on February 10, 2014, 09:06:31 PM

Quote from: Hunterbunter on February 10, 2014, 08:47:22 PM

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_procedure

which would be after February 19.

Quote from: sidhujag on February 10, 2014, 08:53:13 PM

..
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;

sidhujag

legendary

Activity: 2044

Merit: 1005

Quote from: Hunterbunter on February 10, 2014, 09:34:59 PM

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?

Hunterbunter

hero member

Activity: 994

Merit: 1000

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.

Unthinkingbit

hero member

Activity: 935

Merit: 1015

Quote from: Hunterbunter on February 10, 2014, 08:47:22 PM

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_procedure

which would be after February 19.

Quote from: sidhujag on February 10, 2014, 08:53:13 PM

..
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.

sidhujag

legendary

Activity: 2044

Merit: 1005

Quote from: Hunterbunter on February 10, 2014, 08:47:22 PM

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)

Code:

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.

Hunterbunter

hero member

Activity: 994

Merit: 1000

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)

Code:

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

Activity: 2044

Merit: 1005

Quote from: Hunterbunter on February 10, 2014, 08:24:39 PM

Quote from: sidhujag on February 10, 2014, 07:55:15 PM

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

Code:

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:

Code:

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

Code:

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..

novacadian

full member

Activity: 232

Merit: 104

Quote from: smeagol on February 10, 2014, 06:12:38 PM

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

Hunterbunter

hero member

Activity: 994

Merit: 1000

Quote from: sidhujag on February 10, 2014, 07:55:15 PM

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

Code:

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:

Code:

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

Code:

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.

sidhujag

legendary

Activity: 2044

Merit: 1005

Quote from: Hunterbunter on February 10, 2014, 07:32:59 PM

Quote from: sidhujag on February 10, 2014, 01:25:29 PM

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.

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

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?

Code:

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

hero member

Activity: 994

Merit: 1000

Quote from: sidhujag on February 10, 2014, 01:25:29 PM

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.

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

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?

Code:

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.

cdelatorref

newbie

Activity: 50

Merit: 0

Quote from: smeagol on February 10, 2014, 06: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.

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.

Topic: [DVC]DevCoin - Official Thread - Moderated - page 187. (Read 1058949 times)