Search results

doesn't look like it: git blame v0.11.2.13 src/darksend.cpp | grep blind 79e50f81 (Evan Duffield 2015-03-20 08:47:19 -0700 648) //automatically downgrade for 11.2, blinding will be supported in 11.3/12.0

Even masternodes? ;) Or did you sneak some other code in there we need to sync to?

build 172 failed -- no artifacts -->http://bamboo.darkcoin.qa/browse/DRKL-DEV/latest also, you keep posting the wrong win build link.

Not a safety thing, a stack thing. If you replay a previous stack position, you lose the rest of the stack. To demonstrate, in debug console, type: 1<enter> 2<enter> 3<enter> 4<enter> up/down arrows show all four commands. re-run #2 (up-up-enter) up/down arrows show only commands 1 and 2.

found pre-existing bug: coin control list selection date column does not sort rows. affects versions v0.11.1.x and v0.11.2.x (and possibly others) While I'm posting bugs: debug window history is broken too. To reproduce: open debug console type 'masternode count' -- get response type...

Hehe. eduffield! http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-152/gitian-win-dash-bin/32/dash-qt.exe

I *did* say "LOTS", hehe. But seriously, my mainnet wallet has grown to 66 megs within a couple months through normal (albeit heavy) use. It's a few hundred receiving addresses plus a bunch of mixing.

Sent! And yes. Feels like a regression. ssh 080 'cd testnet; ./darkcoind -datadir=. getinfo' { "version" : 110211, "protocolversion" : 70075, "walletversion" : 61000, "balance" : 1417.40004000, "darksend_balance" : 0.00000000, "blocks" : 25273, "timeoffset" : 0...

Done. same issue. Care to try with my uber-tdrk-rich wallet.dat? :wink: I would LOVE for this issue to be solved once and for all! :)

Also, need to report some linux masternodes hanging. Having to kill -9 and restart. (dashd is symlinked to darkcoind) Nothing telling in logs: ubuntu@node-71:~/testnet$ ./darkcoind -datadir=. getinfo ^C ubuntu@node-71:~/testnet$ tail testnet3/debug.log 2015-03-24 17:42:42 dsq - new Darksend...

Also, on linux masternodes, am occasionally (10% of nodes) getting: 2015-03-24 16:39:13 Verifying mncache.dat format... 2015-03-24 16:39:13 ERROR: Read : Deserialize or I/O error - non-canonical ReadCompactSize() 2015-03-24 16:39:13 Masternode cache file mncache.dat has invalid format...

Having issues with latest win build (url above). First launch stuck "out of sync" with 0 hours remaining. Launched with -reindex, hung at 6 weeks ago for over a half hour. Deleted blocks/chainstate folders, launched, churning with many (windows) "not responding" messages. This wallet has a LOT...

404. :wink: url should be: http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-150/gitian-win-dash-bin/32/dash-qt.exe :smile:

Have run into three bugs when trying to send an outbound IX. All cause this dialog to appear: Bug 1 -- incoming IX is in progress (hung): Wallet A sends (IX) 1 drk to wallet B. IX hangs with insufficient signature threshold. Wallet B selects different, existing, confirmed inputs, attempts...

As I understand things, it's seeing it's older version cached masternode start from the network. Which is usually a temporary condition. Meaning it'll usually go offline after a while. After a protocol bump, you should issue masternode stop/start to make sure your latest version is in the...

2000 drk / 4 rounds -- ~1341/~1342 mixed/total darksend enabled, wallet completely mixed then masternode rewards are being deposited from another wallet automatically as they reach 120 confs.

Am seeing darksend getting repeatedly hung up on one of my wallets. v0.11.0.12 win-qt Have -zapped wallet txes a few times, but it keeps getting stuck. Block height and hash are up-to-date. Tracing debug log, I found this transaction 4b12c4b9 which never made it to the network but seems to...

stop and start your wallet, it'll clear now.

odd. is behaving like it's a protocol mismatch. do 'getinfo' in your local and remote and verify these two values match: "version" : 110011, "protocolversion" : 70054,

did you update your local wallet too? v0.11.0.11 will only accept start signals from v0.11.0.11 You'll probably want to stop your nodes, delete peers.dat and restart them to get a fresh un-banned start too.