v0.10.12.x RC4 Testing

Status
Not open for further replies.

elbereth

Active Member
Dash Support Group
Mar 25, 2014
447
469
133
Costa Rica
dashninja.pl
Dash Address
XkfkHqMnhvQovo7kXQjvnNiFnQhRNZYCsz
master-rc4 is up to date, on the console I'm just getting this:

init message: Verifying wallet...
init message: Loading block index...
init message: Verifying blocks...
init message: Loading wallet...
init message: Loading addresses...
init message: Done loading


What else are you getting?
dmcv -done downloading
dmcv -block height ok
dmcv - masternode from vin CTxIn(COutPoint(b24d6ea739601055ae2291e9d8a400e42c1b0fe436ee2a55c51b68383a5a5837, 1), scriptSig=)
dmcv -know masternode
dmcv - found prev masternode vote for block
dmcv -received
dmcv -done downloading
dmcv -block height ok
dmcv - masternode from vin CTxIn(COutPoint(6d4a4432c876081459df5900414f3f06380254dbc33e689c961288d882a0268d, 1), scriptSig=)

for example, it fills the screen.

$ ./bin/darkcoind -?
DarkCoin version v0.9.12.20-beta

$ git pull
Already up-to-date.

$ git status
On branch master-rc4
Your branch is up-to-date with 'origin/master-rc4'.

nothing to commit, working directory clean


Freshly compiled. (Just tried again the very minute)
 

jimbit

Well-known Member
Foundation Member
May 23, 2014
229
103
203
master-rc4 is up to date, on the console I'm just getting this:

init message: Verifying wallet...
init message: Loading block index...
init message: Verifying blocks...
init message: Loading wallet...
init message: Loading addresses...
init message: Done loading


What else are you getting?
got this one:
[email protected]:~$ maxconnections check 248
Code:
[email protected]:~$ darkcoind getinfo
{
    "version" : 101220,
    "protocolversion" : 70030,
    "walletversion" : 60000,
    "balance" : 18591.15356589,
    "anonymized_balance" : 0.00000000,
    "blocks" : 12893,
    "timeoffset" : 0,
    "connections" : 2,
    "proxy" : "",
    "difficulty" : 0.08658629,
    "testnet" : true,
    "keypoololdest" : 1405804459,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : ""
}
[email protected]:~$
[email protected]:~$ maxconnections check 248
maxconnections check 248
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,320
183
dmcv -done downloading
dmcv -block height ok
dmcv - masternode from vin CTxIn(COutPoint(b24d6ea739601055ae2291e9d8a400e42c1b0fe436ee2a55c51b68383a5a5837, 1), scriptSig=)
dmcv -know masternode
dmcv - found prev masternode vote for block
dmcv -received
dmcv -done downloading
dmcv -block height ok
dmcv - masternode from vin CTxIn(COutPoint(6d4a4432c876081459df5900414f3f06380254dbc33e689c961288d882a0268d, 1), scriptSig=)

for example, it fills the screen.

$ ./bin/darkcoind -?
DarkCoin version v0.9.12.20-beta

$ git pull
Already up-to-date.

$ git status
On branch master-rc4
Your branch is up-to-date with 'origin/master-rc4'.

nothing to commit, working directory clean


Freshly compiled. (Just tried again the very minute)
Pushed a fix to remove that stuff. Thanks
 

elbereth

Active Member
Dash Support Group
Mar 25, 2014
447
469
133
Costa Rica
dashninja.pl
Dash Address
XkfkHqMnhvQovo7kXQjvnNiFnQhRNZYCsz
Running the new code you pushed. Still seeing log on the console:
Code:
CreateNewBlock - network could not reach consessus on payee for block 12896
Will keep it running and check back. :)
Edit: New one:
Code:
Masternode payment to OP_DUP OP_HASH160 34a8090a974e9aff175e46dc216a188d21822da9 OP_EQUALVERIFY OP_CHECKSIG
And still getting:
Code:
dmcv - found prev masternode vote for block
dmcv: rejecting masternode vote
 

jimbit

Well-known Member
Foundation Member
May 23, 2014
229
103
203
my latest console:
Code:
[email protected]:~$ maxconnections check 248
maxconnections check 248
maxconnections check 248
maxconnections check 248
maxconnections check 248
maxconnections check 248
maxconnections check 248
maxconnections check 248
conflict with in-memory transaction : COutPoint(4f7d856d0403182297b86c5804d075d6b957b13f6831da661bcea7cc0f798b64, 5)
conflict with in-memory transaction : COutPoint(6295d370a2dd26f7b10ff525c74def9cb4edfc6b00063c94afc3d5f850db6172, 3)
maxconnections check 248
maxconnections check 248
 

UdjinM6

Official Dash Dev
Dash Core Team
Moderator
May 20, 2014
3,638
3,538
1,183
master-rc4 is up to date, on the console I'm just getting this:

init message: Verifying wallet...
init message: Loading block index...
init message: Verifying blocks...
init message: Loading wallet...
init message: Loading addresses...
init message: Done loading


What else are you getting?
same here +
maxconnections check 117
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,320
183
Last edited by a moderator:

darkzero

Member
Jun 6, 2014
44
35
58
Opened a wallet.dat with anonymized tDRK (2 rounds) with a previous version of client. Set rounds to 3 and now keep getting "not compatible with existing transactions " but there are "Darksend Denominate" transactions anyway.

from log:
2014-08-11 16:50:01 DarkSendStatusUpdate - state: 2 entriesCount: 1 accepted: 0 error: not compatible with existing transactions
2014-08-11 16:50:01 CDarkSendPool::UpdateState() == 2 | 6
2014-08-11 16:50:01 CDarkSendPool::StatusUpdate - entry not accepted by masternode
2014-08-11 16:50:01 dsq.nDenom != GetDenominationsByAmount 14 15
2014-08-11 16:50:01 DoAutomaticDenominating --- connected (from queue), sending dsa for 99900000000
2014-08-11 16:50:01 darkSend Status => ERROR : not compatible with existing transactions

Is it somethign worth looking into it?

Never mind, seems resolved with protocolversion 70031

{
"version" : 101220,
"protocolversion" : 70031,
"walletversion" : 60000,
"balance" : 999.82835972,
"anonymized_balance" : 0.00000000,
"blocks" : 12910,
"timeoffset" : 0,
"connections" : 4,
"proxy" : "",
"difficulty" : 0.14665044,
"testnet" : true,
"keypoololdest" : 1406570505,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}
 

GNULinuxGuy

Member
Jul 22, 2014
112
68
78
Dash Address
XjkXfrYTSvdYe4738DtNVX5XfUz7qU9HnY
Testing fresh darkcoind v0.10.12.20-beta (BuildID[sha1]=0x4298892ebadf70a713b15348d86e1a728487fcd3). Looks like something may be wrong with denomination in this release. Sent 1k tDRK to mr6hcLUQsZAPdNiGsPbYbkzLyggJUCwuAp (up to 17 confirms now) and auto-denomination sent the entire balance to msv3nMjmpuXDSJCVaZUf1WADyEXr38heXk with no fee. It does not appear to be attempting to do anything further with it.
Edit: Running protocol version 70030 right now, so I will start fresh and run this test again.
 

UdjinM6

Official Dash Dev
Dash Core Team
Moderator
May 20, 2014
3,638
3,538
1,183
protocol version 70031, v0.10.12.20-6-.....
still getting "init ...." in console
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,320
183
Opened a wallet.dat with anonymized tDRK (2 rounds) with a previous version of client. Set rounds to 3 and now keep getting "not compatible with existing transactions " but there are "Darksend Denominate" transactions anyway.

from log:
2014-08-11 16:50:01 DarkSendStatusUpdate - state: 2 entriesCount: 1 accepted: 0 error: not compatible with existing transactions
2014-08-11 16:50:01 CDarkSendPool::UpdateState() == 2 | 6
2014-08-11 16:50:01 CDarkSendPool::StatusUpdate - entry not accepted by masternode
2014-08-11 16:50:01 dsq.nDenom != GetDenominationsByAmount 14 15
2014-08-11 16:50:01 DoAutomaticDenominating --- connected (from queue), sending dsa for 99900000000
2014-08-11 16:50:01 darkSend Status => ERROR : not compatible with existing transactions

Is it somethign worth looking into it?

Never mind, seems resolved with protocolversion 70031

{
"version" : 101220,
"protocolversion" : 70031,
"walletversion" : 60000,
"balance" : 999.82835972,
"anonymized_balance" : 0.00000000,
"blocks" : 12910,
"timeoffset" : 0,
"connections" : 4,
"proxy" : "",
"difficulty" : 0.14665044,
"testnet" : true,
"keypoololdest" : 1406570505,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}
That's ok.
 
  • Like
Reactions: darkzero

GNULinuxGuy

Member
Jul 22, 2014
112
68
78
Dash Address
XjkXfrYTSvdYe4738DtNVX5XfUz7qU9HnY
Testing fresh v0.10.12.20-6-gf3985c8-beta auto-denominating darkcoind. Sent 1k from faucet to mgR2YjBE7PxEEPVRFcXEMhHZHB2sH8VYgD and it was sent to a single address of mkkg8BcuPV4CQonWE2nC7WFfdR849Mznmc with no fee. Is this the expected behavior? So clean and different from the past few releases that it seems too good to be true! :)
 

chaeplin

Active Member
Core Developer
Mar 29, 2014
749
356
133
..
Testing fresh v0.10.12.20-6-gf3985c8-beta auto-denominating darkcoind. Sent 1k from faucet to mgR2YjBE7PxEEPVRFcXEMhHZHB2sH8VYgD and it was sent to a single address of mkkg8BcuPV4CQonWE2nC7WFfdR849Mznmc with no fee. Is this the expected behavior? So clean and different from the past few releases that it seems too good to be true! :)
As expected.
A ----> B received.
B ----> C sent(not counted as denom round), then denom starting.

Can't be sure if B was used previously, so C is used.
C is a new address.
 
Last edited by a moderator:

TsuyokuNaritai

Active Member
May 24, 2014
181
102
103
It was just a nightmare!
:eek: That's what I'm afraid of. But no-one else wants to talk about it here so I won't press it further. Hopefully their confidence is justified in this case and Murphy’s Law, Cromwell's Law, Hofstadter's Law, and Santayana's Law of Repetitive Consequences are not. :oops:
 
  • Like
Reactions: richy

UdjinM6

Official Dash Dev
Dash Core Team
Moderator
May 20, 2014
3,638
3,538
1,183
  • Like
Reactions: defunctec

GNULinuxGuy

Member
Jul 22, 2014
112
68
78
Dash Address
XjkXfrYTSvdYe4738DtNVX5XfUz7qU9HnY
Was just about to start dancing, but upon my 2nd restart of darkcoind it attempted to auto-denominate a couple more times. I see 2 new transactions and 15 new addresses are returned by listaddressgroupings. Strangely the balance has now dropped to 279.875 as well.

Edit: Balance is now at 1269.999 (should be at most a 1k faucet load).
Code:
$ grep -i denom debug.log|tail -n15
2014-08-11 18:09:04 DoAutomaticDenominating : Running darksend denominate. Return ''
2014-08-11 18:12:04 DoAutomaticDenominating --- connected (from queue), sending dsa for 99900000000
2014-08-11 18:12:04 DoAutomaticDenominating : Running darksend denominate. Return ''
2014-08-11 18:13:04  dsq.nDenom != GetDenominationsByAmount 15 14
2014-08-11 18:13:04  dsq.nDenom != GetDenominationsByAmount 13 14
2014-08-11 18:13:04  dsq.nDenom != GetDenominationsByAmount 12 14
2014-08-11 18:13:04 DoAutomaticDenominating -- attempt 1 connection to masternode 54.183.79.141:19999
2014-08-11 18:13:04 DoAutomaticDenominating --- connected, sending dsa for 27987500000
2014-08-11 18:14:04  dsq.nDenom != GetDenominationsByAmount 12 14
2014-08-11 18:14:04  dsq.nDenom != GetDenominationsByAmount 15 14
2014-08-11 18:14:04  dsq.nDenom != GetDenominationsByAmount 15 14
2014-08-11 18:14:04 DoAutomaticDenominating --- connected (from queue), sending dsa for 27987500000
2014-08-11 18:15:04  dsq.nDenom != GetDenominationsByAmount 15 14
2014-08-11 18:15:04  dsq.nDenom != GetDenominationsByAmount 15 14
2014-08-11 18:15:04 DoAutomaticDenominating --- connected (from queue), sending dsa for 27987500000
Code:
$ ./darkcoind listtransactions first|tail -n25
        "address" : "mkkg8BcuPV4CQonWE2nC7WFfdR849Mznmc",
        "category" : "receive",
        "amount" : 125.00000000,
        "confirmations" : 5,
        "blockhash" : "000000036223e78d9570fdd1e75cdf7e1fa0a4454e240401fc32d549a162fe03",
        "blockindex" : 5,
        "blocktime" : 1407780408,
        "txid" : "5f1943bb8dedbda50f58088f1552c164a74d592e80ef1d77f5a9677f0dcc3bf9",
        "time" : 1407780302,
        "timereceived" : 1407780302
    },
    {
        "account" : "first",
        "address" : "mkkg8BcuPV4CQonWE2nC7WFfdR849Mznmc",
        "category" : "receive",
        "amount" : 145.00000000,
        "confirmations" : 5,
        "blockhash" : "000000036223e78d9570fdd1e75cdf7e1fa0a4454e240401fc32d549a162fe03",
        "blockindex" : 4,
        "blocktime" : 1407780408,
        "txid" : "914269c196a94f0d6535ce1f098dca53a47833fc54f83eadad83274556d7fa70",
        "time" : 1407780396,
        "timereceived" : 1407780396
    }
]
 
Last edited by a moderator:

clayop

Member
May 13, 2014
76
29
58
I cannot understand how "amount of DRK keep anonymized" option works. My expectation is like...
1) If I set the value 1000 and I have 300DRK anonymized, 700 will be anonymized
2) If I have over 1000DRK anonymized, denomination stops

Am I correct?
 

andresescobar

New Member
Jun 27, 2014
24
10
3
Encrypted wallet v0.10.12.20 (on Ubuntu 14.04.1) locking itself again and again.
Making auto-denom a very bumpy ride. Did not see this during the last few builds... Only for me?

drk.JPG


Update
Fresh transaction - and again wallet immediately locking itself:
drk2.JPG
 
Last edited by a moderator:

qwizzie

Well-known Member
Aug 6, 2014
1,607
763
183
Windows 32 bit v0.10.12.20-gf749f80 beta from flare (page 90)

New wallet (not encrypted / unlocked), sent 1000 drk from free faucet, results are as follows :







So it does denominate twice but it does not anomynize at the end and the Darksend Rounds get stuck at round 1 ?

Edit 1 : i will sent wallet + debug.log to Evan in case he needs it. --> Update : see Edit 2
Edit 2 : just received a third Darksend denominate transaction for these default 2 Darksend Rounds, i will give it some more time, see what happens .. to be continued.
Edit 3 : after two hours and in total 4 Darksend Denominates & 2 payments to myself it worked !
Total Balance : 999.995 DRK
Anonymized : 999.00000023
Inputs : Darksend Rounds 2
 
Last edited by a moderator:

andresescobar

New Member
Jun 27, 2014
24
10
3
Try the console

"walletpassphrase YOURPASS 100000" or some other timeout, then
"darksend auto"
Issued, locking again right away. I´d say denom work is *not* done, but wallet thinks differently:
Code:
2014-08-11 17:39:46 Darksend is complete, locking wallet.
2014-08-11 17:46:56 Darksend is complete, locking wallet.
2014-08-11 18:43:07 Darksend is complete, locking wallet.
2014-08-11 18:54:00 Darksend is complete, locking wallet.
2014-08-11 18:57:30 Darksend is complete, locking wallet.
2014-08-11 18:58:10 Darksend is complete, locking wallet.
2014-08-11 18:58:50 Darksend is complete, locking wallet.
2014-08-11 18:59:30 Darksend is complete, locking wallet.
Update:
Started again w. fresh wallet and 1000 tDRK - unfortunately same locking occurences:
Code:
2014-08-11 19:31:11 Darksend is complete, locking wallet.
2014-08-11 19:40:57 Darksend is complete, locking wallet.
 
Last edited by a moderator:

eduffield

Core Developer
Mar 9, 2014
1,084
5,320
183
Issued, locking again right away. I´d say denom work is *not* done, but wallet thinks differently:
Code:
2014-08-11 17:39:46 Darksend is complete, locking wallet.
2014-08-11 17:46:56 Darksend is complete, locking wallet.
2014-08-11 18:43:07 Darksend is complete, locking wallet.
2014-08-11 18:54:00 Darksend is complete, locking wallet.
2014-08-11 18:57:30 Darksend is complete, locking wallet.
2014-08-11 18:58:10 Darksend is complete, locking wallet.
2014-08-11 18:58:50 Darksend is complete, locking wallet.
2014-08-11 18:59:30 Darksend is complete, locking wallet.
I just pushed up a new version to address this. Try it out again
 
  • Like
Reactions: andresescobar
Status
Not open for further replies.