v0.10.12.x RC4 Testing

Status
Not open for further replies.
My debug.log is almost as big as the QT itself... is this expected for testnet? Its only been a few days...
 
yidakee said:
My debug.log is almost as big as the QT itself... is this expected for testnet? Its only been a few days...
Click to expand...
There are lots of debug printf() in the RC4 code right now to facilitate the debugging --> debug.log growths :)

As soon as RC4 is ready for rollout the debugging spam will we removed.
 
Ahh thought so, way too much in so little time :wink: - backed it up and started a new one for easier reading...

ok... getting this all time... Should I attempt to manually denominate?

2014-07-26 07:16:23 CDarkSendPool::NewBlock
2014-07-26 07:16:23 --- strUseMasternode
2014-07-26 07:16:23 found coins 5
2014-07-26 07:16:23 vin nValue 99900000000
2014-07-26 07:16:23 found coins 5
2014-07-26 07:16:23 vin nValue 99900000000
2014-07-26 07:16:23 DoAutomaticDenominating : Running darksend denominate for 999 coins.
2014-07-26 07:16:23 DoAutomaticDenominating : Error running denominate, Insufficient funds 2
2014-07-26 07:16:23 ProcessBlock: ACCEPTED
2014-07-26 07:16:23 sending: inv (37 bytes)
2014-07-26 07:16:23 sending: inv (37 bytes)
2014-07-26 07:16:23 sending: inv (37 bytes)
2014-07-26 07:16:24 received: dmcv (156 bytes)
2014-07-26 07:16:24 received: dmcv (156 bytes)
Click to expand...

0.9.12.2 getting accepted which I assume is ok since its not a MN, but could be pertinent for pools? just pitching it out there

2014-07-26 07:16:48 sending: getdata (37 bytes)
2014-07-26 07:16:48 received: tx (1853 bytes)
2014-07-26 07:16:48 AcceptToMemoryPool: 188.165.205.82:19999 /Satoshi:0.9.12.2/ : accepted 466577e17e3ee0f38450d62faf259dbbdd6b125ec44e76c31d14c118e42ee251 (poolsz 1)
2014-07-26 07:16:48 sending: inv (37 bytes)
2014-07-26 07:16:48 received: inv (37 bytes)
2014-07-26 07:16:48 got inventory: tx 466577e17e3ee0f38450d62faf259dbbdd6b125ec44e76c31d14c118e42ee251 have
2014-07-26 07:16:48 received: inv (37 bytes)
Click to expand...
 
Last edited by a moderator:
<CHAOSiTEC> 61 denominations is quite alot
<CHAOSiTEC> for 8k tdrk
<CHAOSiTEC> im also wondering what this payment is for
<CHAOSiTEC> Status: 249 bekräftelser
<CHAOSiTEC> Datum: 2014-07-25 23:46
<CHAOSiTEC> Till: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf
<CHAOSiTEC> Belasta: -0.025 DRK
<CHAOSiTEC> Nettobelopp: -0.025 DRK
<CHAOSiTEC> Transaktions-ID: c457878d4fc1ce23c36b46bf500d07ae06c485c42f3fa39f347ae70c00492ef1
<CHAOSiTEC> i have 2 of those, to the same address
 
yey!! auto denom working

sUrq92C.png
 
My 12.6 wallet has autodenominated (I propose the abbreviation AD!) nearly 19000 DRK since it's been running. Hopefully will be able to specify them for sending with 12.7... :tongue:
 
thelonecrouton said:
My 12.6 wallet has autodenominated (I propose the abbreviation AD!) nearly 19000 DRK since it's been running. Hopefully will be able to specify them for sending with 12.7... :tongue:
Click to expand...
Can you please describe how i can check my wallet.
I have to run the darkcoin-qt with masternode flag = 0 ?

Is it possible that something in variance of mnpayments has changed ?
For me it looks like my node is getting now payments around the whole day
 
dotnetmin said:
Can you please describe how i can check my wallet.
I have to run the darkcoin-qt with masternode flag = 0 ?
Click to expand...
The only line you need in your darkcoin.conf is testnet=1

To see what yidakee and I have posted, in the qt wallet go to Settings > Options > Display tab > check Display coin control features, then under the Send tab you'll see a new Coin Control Features box at the top, click the Inputs button... :)
 
2^160 possible addresses

7*10^9 people on Earth, each one say performing in their lifetimes 10^9 transactions in 10^9 different wallets, each transaction having a newly generated virgin address at each end...

...is still a very very tiny fraction of the address space.

If EVERY single transaction and change amount etc. was assigned it's own unique address, transactional anonymity would be literally perfect.

Wallets could auto-tidy up their addresses as needed.

Generating and verifying new addresses takes time and CPU cycles though.

Luckily we have ~750 Masternodes and counting that spend much of their time doing, well, not much... they could be preparing new addresses while otherwise sitting there twiddling their wait loops.

Just a notion. ;)
 
vertoe said:
I'm also getting the "Insufficient funds 2" error on my wallet, want me to send you the wallet.dat, too?
This is my wallet balance, http://test.explorer.darkcoin.qa/address/n1r5ibhWq8FcnhNELB9pzLvU8yEuUNMvgE
This was the only auto-denomination that happened before it got stuck: http://test.explorer.darkcoin.qa/tx/04f5fe7c9a67512265e1a1d4f9ae23d09186198e2d43844e508dbd2a798e5e66
Click to expand...

Try closing and opening your wallet and let me know if it starts denominating again.
 
CHAOSiTEC said:
<CHAOSiTEC> 61 denominations is quite alot
<CHAOSiTEC> for 8k tdrk
<CHAOSiTEC> im also wondering what this payment is for
<CHAOSiTEC> Status: 249 bekräftelser
<CHAOSiTEC> Datum: 2014-07-25 23:46
<CHAOSiTEC> Till: muqFjdh1S3eWro6KQ6yRX7zQSKqVubCHkf
<CHAOSiTEC> Belasta: -0.025 DRK
<CHAOSiTEC> Nettobelopp: -0.025 DRK
<CHAOSiTEC> Transaktions-ID: c457878d4fc1ce23c36b46bf500d07ae06c485c42f3fa39f347ae70c00492ef1
<CHAOSiTEC> i have 2 of those, to the same address
Click to expand...

Those are collateral fees. A masternode thought you were misbehaving .

Edit: I just got hit by collateral fees because my client refused to sign the transaction. Apparently it detected missing outputs. I'll look into this.
 
Last edited by a moderator:
eduffield said:
Try closing and opening your wallet and let me know if it starts denominating again.
Click to expand...
I have this message on three distinct systems and did several restarts. The large 10,000 DRK vin is split once, and then the wallet gets stuck with "insufficient funds 2"
 
****** PLEASE UPDATE TO 9.12.7 OR 10.12.7 *******

- Added a smart input splitting method. Place 1000+DRK into a brand new wallet and it will be split into many inputs compatible with Darksend
- DoAutodenomination now tries the correct balance (it was getting stuck on the wrong inputs)
- "entries is full" fix for at least one of the causes
- Changed merging parties to two for easier debugging.
- Fixed mod again (missed the one for the actual command you guys are using, I was overriding the default there)

Binaries (stable)
http://www.darkcoin.io/downloads/master-rc4/darkcoin-qt
http://www.darkcoin.io/downloads/master-rc4/darkcoind

RC4 Binaries ( masternodes )
http://www.darkcoin.io/downloads/rc4/darkcoin-qt
http://www.darkcoin.io/downloads/rc4/darkcoind
 
Masternode 54.191.236.39 and local qt wallet updated.
{
"version" : 101207,
"protocolversion" : 70022,
"walletversion" : 60000,
"balance" : 6300.00660000,
"blocks" : 4139,
"timeoffset" : 0,
"connections" : 2,
"proxy" : "",
"difficulty" : 0.10486389,
"testnet" : true,
"keypoololdest" : 1406222622,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}

Still can't send using 'use darksend inputs only' but I can now manually select denominated inputs and send them.

edit: welcome to our four new Chinese testnet masternodes! :)
 
Last edited by a moderator:
 
Status
Not open for further replies.
Back
Top