v0.10.16.x Testing

Status
Not open for further replies.
Code: 
ubuntu2@108:~/.darkcoin$ ./darkcoind getinfo
{
  "version" : 101603,
  "protocolversion" : 70045,
  "walletversion" : 60000,
  "balance" : 15607.90490281,
  "darksend_balance" : 0.00000000,
  "blocks" : 63291,
  "timeoffset" : 0,
  "connections" : 6,
  "proxy" : "",
  "difficulty" : 0.86725511,
  "testnet" : true,
  "keypoololdest" : 1406001327,
  "keypoolsize" : 1001,
  "paytxfee" : 0.00000000,
  "mininput" : 0.00001000,
  "errors" : ""
}
ubuntu2@108:~/.darkcoin$ ./darkcoind masternode list
{
  "158.58.250.202:19999" : 1,
  "188.226.225.170:19999" : 1,
  "162.244.76.223:19999" : 1,
  "86.20.185.139:19999" : 1,
  "176.126.245.22:19999" : 1,
  "108.61.198.220:19999" : 1
}
 
masternode list is looking good on both tMN and qt wallet for me too now

EDIT: qt wallet is spamming in stdout with "DoAutomaticDenominating -- Skipping already used masternode -CTxIn....."

EDIT2: wwoow, it also pushed "CDarksendPool::SendDarksendDenominate() - preparing transaction -.... A LOT OF STUFF with CTxIn and CTxOut" to stdout right now
 
Last edited by a moderator:
Code: 
2014-11-13 16:38:00 dsee - Got NEW masternode entry 85.214.22.190:19999
2014-11-13 16:38:00 dsee - Accepted masternode entry -1 -1
2014-11-13 16:38:01 connection timeout
2014-11-13 16:38:01 Submitted to masternode, waiting in queue .
2014-11-13 16:38:02 trying connection 76.110.255.33:19999 lastseen=15230.4days
2014-11-13 16:38:07 connection timeout
2014-11-13 16:38:07 trying connection 76.110.255.33:19999 lastseen=15230.4days
2014-11-13 16:38:08 dssu - state: 2 entriesCount: 0 accepted: -1 error: 
2014-11-13 16:38:08 CDarkSendPool::UpdateState() == 2 | 2
2014-11-13 16:38:12 connection timeout
2014-11-13 16:38:13 trying connection 76.110.255.33:19999 lastseen=15230.4days
2014-11-13 16:38:18 connection timeout
2014-11-13 16:38:18 trying connection 76.110.255.33:19999 lastseen=15230.4days
2014-11-13 16:38:18 CDarkSendPool::UpdateState() == 2 | 3
2014-11-13 16:38:19 Darksend is idle
2014-11-13 16:38:23 connection timeout
2014-11-13 16:38:24 trying connection 178.62.6.122:19999 lastseen=15230.4days
2014-11-13 16:38:29 connection timeout
2014-11-13 16:38:30 trying connection 76.110.255.33:19999 lastseen=15230.4days
2014-11-13 16:38:35 connection timeout
2014-11-13 16:38:36 trying connection 178.62.6.122:19999 lastseen=15230.4days
2014-11-13 16:38:37  vout - CTxOut(nValue=32.00000000, scriptPubKey=OP_DUP OP_HASH160 538d19e10c45)
2014-11-13 16:38:38  vout - CTxOut(nValue=16.00000000, scriptPubKey=OP_DUP OP_HASH160 538d19e10c45)
2014-11-13 16:38:38  vout - CTxOut(nValue=8.00000000, scriptPubKey=OP_DUP OP_HASH160 538d19e10c45)
2014-11-13 16:38:38  vout - CTxOut(nValue=10.00000001, scriptPubKey=OP_DUP OP_HASH160 1c689c4d2fbb)
2014-11-13 16:38:38  vout - CTxOut(nValue=100.00000001, scriptPubKey=OP_DUP OP_HASH160 13d15a4f2657)
2014-11-13 16:38:38  vout - CTxOut(nValue=1.00000001, scriptPubKey=OP_DUP OP_HASH160 3d5786749a5e)
2014-11-13 16:38:38  vout - CTxOut(nValue=10.00000001, scriptPubKey=OP_DUP OP_HASH160 ff13fcf912ff)
2014-11-13 16:38:38  vout - CTxOut(nValue=10.00000001, scriptPubKey=OP_DUP OP_HASH160 e238745d70bc)
2014-11-13 16:38:38  vout - CTxOut(nValue=100.00000001, scriptPubKey=OP_DUP OP_HASH160 cde7e6513a91)
2014-11-13 16:38:38  vout - CTxOut(nValue=10.00000001, scriptPubKey=OP_DUP OP_HASH160 98998fe66e96)
2014-11-13 16:38:38  vout - CTxOut(nValue=1.00000001, scriptPubKey=OP_DUP OP_HASH160 53b24cb8ae39)
2014-11-13 16:38:38  vout - CTxOut(nValue=100.00000001, scriptPubKey=OP_DUP OP_HASH160 04a404d7fb60)
2014-11-13 16:38:38  vout - CTxOut(nValue=10.00000001, scriptPubKey=OP_DUP OP_HASH160 d091d923b74b)
2014-11-13 16:38:38 Submiting Darksend for 408.000000 DRK
2014-11-13 16:38:38 DoAutomaticDenominating --- connected (from queue), sending dsa for 26 26 - 104.131.45.75:19999
2014-11-13 16:38:38 dssu - state: 3 entriesCount: 0 accepted: 0 error: Last darksend was too recent
2014-11-13 16:38:38 CDarkSendPool::UpdateState() == 3 | 3
2014-11-13 16:38:38 CDarkSendPool::UpdateState() == 3 | 7
2014-11-13 16:38:38 CDarkSendPool::StatusUpdate - entry not accepted by masternode
2014-11-13 16:38:38 Darksend request incomplete: Last darksend was too recent. Will retry...
2014-11-13 16:38:41 connection timeout
2014-11-13 16:38:42 trying connection 76.110.255.33:19999 lastseen=15230.4days
 
thelonecrouton said:
Still getting some console spam:

dsa -- last dsq too recent, must wait. 176.126.245.22:19999
Click to expand...
This is showing up on my console also:

dsa -- last dsq too recent, must wait. 108.61.198.220:19999

I guess we don't have enough masternodes to go around on testnet.
 
****** PLEASE UPDATE TO v10.16.4 *******

I'm mixing now with seven clients and everything is humming along. I think we're ready to go.

- Fixed variable darksend amounts code, all clients should be able to merge together now (didn't work in v3).
- Added rare collateral charging
- Removed all the spam/logging

----

CI-builds for v0.10.16.4

Source:
https://github.com/darkcoin/darkcoin/tree/ds-zero-fee/src

Windows 32bit:
http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-33/gitian-win-darkcoin-bin/32/darkcoin-qt.exe
http://bamboo.darkcoin.qa/artifact/...tian-win-darkcoin-bin/32/daemon/darkcoind.exe
http://bamboo.darkcoin.qa/artifact/...oin-bin/32/darkcoin-0.10.16.4-win32-setup.exe

Mac OS X:
http://bamboo.darkcoin.qa/artifact/...-osx-darkcoin-dist/darkcoin-0.10.16.4-osx.dmg

Linux 32bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/32/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-34/gitian-linux-darkcoin-bin/bin/32/darkcoind

Linux 64bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-34/gitian-linux-darkcoin-bin/bin/64/darkcoind
 
Last edited by a moderator:
Updated, is this right, MN list seems to have blossomed somewhat...

Code: 
{
  "version" : 101604,
  "protocolversion" : 70045,
  "walletversion" : 60001,
  "balance" : 1000.00000000,
  "darksend_balance" : 0.00000000,
  "blocks" : 63320,
  "timeoffset" : 0,
  "connections" : 10,
  "proxy" : "",
  "difficulty" : 0.82899031,
  "testnet" : true,
  "keypoololdest" : 1415891456,
  "keypoolsize" : 1001,
  "paytxfee" : 0.00000000,
  "mininput" : 0.00001000,
  "errors" : ""
}

root@testnet:~/.darkcoin# ./darkcoind masternode start
masternode started remotely
root@testnet:~/.darkcoin# ./darkcoind masternode list
{
  "176.126.245.22:19999" : 1,
  "198.50.148.87:19999" : 1,
  "92.222.19.36:19999" : 1,
  "178.62.6.122:19999" : 1,
  "188.226.225.170:19999" : 1,
  "170.75.162.98:19999" : 1,
  "188.226.161.128:19999" : 1,
  "188.226.180.119:19999" : 1,
  "80.240.135.83:19999" : 1,
  "188.226.228.88:19999" : 1,
  "188.226.196.182:19999" : 1,
  "95.85.48.49:19999" : 1,
  "95.85.1.197:19999" : 1,
  "188.226.201.140:19999" : 1,
  "162.243.219.25:19999" : 1,
  "107.170.7.146:19999" : 1,
  "162.243.76.23:19999" : 1,
  "162.243.59.230:19999" : 1,
  "107.170.120.125:19999" : 1,
  "107.170.171.115:19999" : 1,
  "107.170.157.166:19999" : 1,
  "107.170.165.78:19999" : 1,
  "162.243.136.66:19999" : 1,
  "104.131.143.9:19999" : 1,
  "107.170.196.35:19999" : 1,
  "107.170.242.110:19999" : 1,
  "128.199.245.182:19999" : 1,
  "104.131.45.75:19999" : 1,
  "188.226.223.5:19999" : 1,
  "158.58.250.202:19999" : 1
}
 
eduffield said:
****** PLEASE UPDATE TO v10.16.4 *******

I'm mixing now with seven clients and everything is humming along. I think we're ready to go.

- Fixed variable darksend amounts code, all clients should be able to merge together now (didn't work in v3).
- Added rare collateral charging
- Removed all the spam/logging

----

CI-builds for v0.10.16.4

Source:
https://github.com/darkcoin/darkcoin/tree/ds-zero-fee/src

Windows 32bit (compiling still):
http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-33/gitian-win-darkcoin-bin/32/darkcoin-qt.exe
http://bamboo.darkcoin.qa/artifact/...tian-win-darkcoin-bin/32/daemon/darkcoind.exe
http://bamboo.darkcoin.qa/artifact/...oin-bin/32/darkcoin-0.10.16.4-win32-setup.exe

Mac OS X (compiling still):
http://bamboo.darkcoin.qa/artifact/...-osx-darkcoin-dist/darkcoin-0.10.16.4-osx.dmg

Linux 32bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/32/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-34/gitian-linux-darkcoin-bin/bin/32/darkcoind

Linux 64bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-34/gitian-linux-darkcoin-bin/bin/64/darkcoind
Click to expand...

i think the ''compiling still'' can be removed by now .. at least for the windows 32bit
 
keep seeing:
Code: 
2014-11-13 18:27:49 dstx: Masternode is publishing too many free transactions CTxIn(COutPoint(de664d6b8dee103e8ef4b93df62288a2c836000907a659f568bf2ed0bb7bf217, 11), scriptSig=)

I created 20 tmasternodes with one transaction, so I think the wallet is booting the other 19?

Might affect people reconfiguring their funds for 'start-many' ?

Or do we just instruct people not to do that?

Also:
- one out of four of my mixing wallets hasn't done anything in 70 minutes.
- I had to fold all inputs into a new address to get the wallets darksending.

Edit: that hung wallet shows
Code: 
2014-11-13 19:16:20 Darksend request incomplete: Last darksend was too recent. Will retry...
 
Last edited by a moderator:
16.3 seemed to grind to a halt after first 1000DRK got DS's 1 round, 16.4 still sitting there not doing much.

Log shows a lot of this:
Code: 
2014-11-13 18:44:08  vout - CTxOut(nValue=1.00000001, scriptPubKey=OP_DUP OP_HASH160 e357600fcdbe)
2014-11-13 18:44:08  vout - CTxOut(nValue=10.00000001, scriptPubKey=OP_DUP OP_HASH160 e36de021cf9a)
2014-11-13 18:44:08  vout - CTxOut(nValue=10.00000001, scriptPubKey=OP_DUP OP_HASH160 099d4e2732a6)
2014-11-13 18:44:08  vout - CTxOut(nValue=1.00000001, scriptPubKey=OP_DUP OP_HASH160 7aa6089622f0)
2014-11-13 18:44:08  vout - CTxOut(nValue=1.00000001, scriptPubKey=OP_DUP OP_HASH160 bad9570474ba)
2014-11-13 18:44:08  vout - CTxOut(nValue=100.00000001, scriptPubKey=OP_DUP OP_HASH160 6984d6279415)
2014-11-13 18:44:08  vout - CTxOut(nValue=10.00000001, scriptPubKey=OP_DUP OP_HASH160 bea52c824734)
2014-11-13 18:44:08  vout - CTxOut(nValue=10.00000001, scriptPubKey=OP_DUP OP_HASH160 d7a59197633a)
2014-11-13 18:44:08  vout - CTxOut(nValue=100.00000001, scriptPubKey=OP_DUP OP_HASH160 5e7999a72c67)
2014-11-13 18:44:08  vout - CTxOut(nValue=1.00000001, scriptPubKey=OP_DUP OP_HASH160 f0426aa45e73)
2014-11-13 18:44:08  vout - CTxOut(nValue=10.00000001, scriptPubKey=OP_DUP OP_HASH160 36c4837ec062)
2014-11-13 18:44:08  vout - CTxOut(nValue=1.00000001, scriptPubKey=OP_DUP OP_HASH160 995864b40fb7)
2014-11-13 18:44:08  vout - CTxOut(nValue=10.00000001, scriptPubKey=OP_DUP OP_HASH160 b384483a857d)
2014-11-13 18:44:08  vout - CTxOut(nValue=100.00000001, scriptPubKey=OP_DUP OP_HASH160 7197541537e1)
2014-11-13 18:44:08  vout - CTxOut(nValue=10.00000001, scriptPubKey=OP_DUP OP_HASH160 912e084e7645)
2014-11-13 18:44:08  vout - CTxOut(nValue=10.00000001, scriptPubKey=OP_DUP OP_HASH160 9050321aaa5a)
2014-11-13 18:44:08  vout - CTxOut(nValue=10.00000001, scriptPubKey=OP_DUP OP_HASH160 507db79dc978)
2014-11-13 18:44:08  vout - CTxOut(nValue=1.00000001, scriptPubKey=OP_DUP OP_HASH160 10e69c81e1d7)
2014-11-13 18:44:08  vout - CTxOut(nValue=100.00000001, scriptPubKey=OP_DUP OP_HASH160 2d4cb9bb2cf6)
2014-11-13 18:44:08  vout - CTxOut(nValue=10.00000001, scriptPubKey=OP_DUP OP_HASH160 bf7b639a5cee)
2014-11-13 18:44:08  vout - CTxOut(nValue=1.00000001, scriptPubKey=OP_DUP OP_HASH160 6491e6e6f4d7)
2014-11-13 18:44:08  vout - CTxOut(nValue=1.00000001, scriptPubKey=OP_DUP OP_HASH160 f7c72e5affe1)
2014-11-13 18:44:08  vout - CTxOut(nValue=10.00000001, scriptPubKey=OP_DUP OP_HASH160 c55de1c3ebc0)
2014-11-13 18:44:08  vout - CTxOut(nValue=1.00000001, scriptPubKey=OP_DUP OP_HASH160 fa6c20e4e359)
2014-11-13 18:44:08  vout - CTxOut(nValue=1.00000001, scriptPubKey=OP_DUP OP_HASH160 23aa91fa9e83)
2014-11-13 18:44:08 Submiting Darksend for 520.000000 DRK
2014-11-13 18:44:08 DoAutomaticDenominating -- attempt 1 connection to masternode 80.240.135.83:19999
2014-11-13 18:44:08 trying connection 80.240.135.83:19999 lastseen=15230.4days
2014-11-13 18:44:08 connected 80.240.135.83:19999
2014-11-13 18:44:08 send version message: version 70045, blocks=63351, us=0.0.0.0:0, them=80.240.135.83:19999, peer=37
2014-11-13 18:44:08 DoAutomaticDenominating --- connected, sending dsa for 21 - denom 21
2014-11-13 18:44:08 Added time data, samples 26, offset +1 (+0 minutes)
2014-11-13 18:44:08 Moving 80.240.135.83:19999 to tried
2014-11-13 18:44:08 receive version message: /Satoshi:0.10.16.4/: version 70045, blocks=63351, us=86.154.222.23:50515, them=80.240.135.83:19999, peer=37
2014-11-13 18:44:08 send initial getblocks peer=37
2014-11-13 18:44:08 getblocks -1 to 0 limit 500 peer=37
2014-11-13 18:44:08 dssu - state: 2 entriesCount: 0 accepted: 0 error: Last darksend was too recent
2014-11-13 18:44:08 CDarkSendPool::UpdateState() == 3 | 2
2014-11-13 18:44:08 CDarkSendPool::UpdateState() == 2 | 7
2014-11-13 18:44:08 Darksend request incomplete: Last darksend was too recent. Will retry...
2014-11-13 18:44:11 dssu - state: 2 entriesCount: 0 accepted: -1 error:  
2014-11-13 18:44:11 dssu - message doesn't match current darksend session 87698 967917
2014-11-13 18:44:13 connection timeout
2014-11-13 18:44:13 trying connection 87.66.75.241:19999 lastseen=102.5days
2014-11-13 18:44:18 connection timeout
2014-11-13 18:44:18 CDarkSendPool::Check() -- RESETTING MESSAGE
2014-11-13 18:44:19 trying connection 54.83.144.77:19999 lastseen=165.1days
2014-11-13 18:44:19 Darksend is idle
 
Normal user wallet test, v16.3 and v16.4, 3 different times, mixing does not work,
just getting "Darksend request incomplete: no matching denominations found for mixing. Will retry..."
and "Darksend idle", nothing more.
 
AjM said:
Normal user wallet test, v16.3 and v16.4, 3 different times, mixing does not work,
just getting "Darksend request incomplete: no matching denominations found for mixing. Will retry..."
and "Darksend idle", nothing more.
Click to expand...

I think it's a side effect (false message) from me setting up 20 masternodes with one transaction.
The new system only allows masternodes to send free transactions once in (some time period), so the new code would disallow using the masternode your wallet selected (even though it is a different masternode, the txn makes it look like the same node.)

I've shut down 19 of them. Once the cache's clear, we'll see if things spring back to life.
 
running 6 clients, 5 clients are running without problems, 1 client however had two 0.1 fees on a roll and seems to be having a hard time progressing (click on image to enlarge):

0GVCumJ.jpg
 
Status
Not open for further replies.
Back
Top