V12 Testing Thread

[splawik21]

i'm trying to mix for hours now with 6 wallets, so far only 3 of my 6 wallets have completed to 20 a 30%, the rest is still on 0% .. they are all trying to mix 200 / 2
and are all on correct block height.

qizzy did the same here 6 clients mixing 200 @ 2 rounds...

 

[qwizzie]

With those wallets that are not mixing at all (0%) it seems they have more "transaction not valid" messages

2015-06-19 14:36:38 Last Darksend message: Mixing in progress...
2015-06-19 14:36:38 receive version message: /Dash Core:0.12.0.1/: version 70077, blocks=70127, us=217.122.139.212:59961, peer=1015
2015-06-19 14:36:38 CDarksendPool::UpdateState() == 3 | 2
2015-06-19 14:36:38 CDarksendPool::StatusUpdate - set sessionID to 286575
2015-06-19 14:36:39 Last Darksend message: Submitted to masternode, waiting in queue .
2015-06-19 14:36:39 CDarksendPool::UpdateState() == 2 | 2
2015-06-19 14:36:39 PrepareDarksendDenominate - preparing darksend denominate . Got: 300003000
2015-06-19 14:36:39 keypool added key 4809, size=1001
2015-06-19 14:36:39 init message: Loading wallet... (480.42 %)
2015-06-19 14:36:40 keypool reserve 3809
2015-06-19 14:36:40 keypool keep 3809
2015-06-19 14:36:40 keypool added key 4810, size=1001
2015-06-19 14:36:40 init message: Loading wallet... (480.52 %)
2015-06-19 14:36:40 keypool reserve 3810
2015-06-19 14:36:40 keypool keep 3810
2015-06-19 14:36:40 keypool added key 4811, size=1001
2015-06-19 14:36:40 init message: Loading wallet... (480.62 %)
2015-06-19 14:36:41 keypool reserve 3811
2015-06-19 14:36:41 keypool keep 3811
2015-06-19 14:36:41 CDarksendPool::UpdateState() == 2 | 3
2015-06-19 14:36:41 CDarksendPool::SendDarksendDenominate() - Added transaction to pool.
2015-06-19 14:36:41 Submitting tx CMutableTransaction(ver=1, vin.size=3, vout.size=3, nLockTime=0)
CTxIn(COutPoint(5dec5c1e31f715f23333db3e557152ba7720f254e2fca2dafeab2dca4177fb0e, 15), scriptSig=)
CTxIn(COutPoint(5dec5c1e31f715f23333db3e557152ba7720f254e2fca2dafeab2dca4177fb0e, 12), scriptSig=)
CTxIn(COutPoint(5dec5c1e31f715f23333db3e557152ba7720f254e2fca2dafeab2dca4177fb0e, 18), scriptSig=)
CTxOut(nValue=1.00001000, scriptPubKey=OP_DUP OP_HASH160 4f84fb1d7224)
CTxOut(nValue=1.00001000, scriptPubKey=OP_DUP OP_HASH160 5d2c7c4a705f)
CTxOut(nValue=1.00001000, scriptPubKey=OP_DUP OP_HASH160 0d3f9b4715b7)
2015-06-19 14:36:41 dsi -- transaction not valid! CMutableTransaction(ver=1, vin.size=3, vout.size=3, nLockTime=0)
CTxIn(COutPoint(5dec5c1e31f715f23333db3e557152ba7720f254e2fca2dafeab2dca4177fb0e, 15), scriptSig=)
CTxIn(COutPoint(5dec5c1e31f715f23333db3e557152ba7720f254e2fca2dafeab2dca4177fb0e, 12), scriptSig=)
CTxIn(COutPoint(5dec5c1e31f715f23333db3e557152ba7720f254e2fca2dafeab2dca4177fb0e, 18), scriptSig=)
CTxOut(nValue=1.00001000, scriptPubKey=OP_DUP OP_HASH160 4f84fb1d7224)
CTxOut(nValue=1.00001000, scriptPubKey=OP_DUP OP_HASH160 5d2c7c4a705f)
CTxOut(nValue=1.00001000, scriptPubKey=OP_DUP OP_HASH160 0d3f9b4715b7)

2015-06-19 14:36:41 DoAutomaticDenominating : Running Darksend denominate. Return ''
2015-06-19 14:36:41 Last Darksend message: Darksend is idle.

2015-06-19 14:43:09 CDarksendPool::UpdateState() == 2 | 3
2015-06-19 14:43:09 CDarksendPool::SendDarksendDenominate() - Added transaction to pool.
2015-06-19 14:43:09 Submitting tx CMutableTransaction(ver=1, vin.size=2, vout.size=2, nLockTime=0)
CTxIn(COutPoint(5dec5c1e31f715f23333db3e557152ba7720f254e2fca2dafeab2dca4177fb0e, 15), scriptSig=)
CTxIn(COutPoint(5dec5c1e31f715f23333db3e557152ba7720f254e2fca2dafeab2dca4177fb0e, 18), scriptSig=)
CTxOut(nValue=1.00001000, scriptPubKey=OP_DUP OP_HASH160 23ae83efdc20)
CTxOut(nValue=1.00001000, scriptPubKey=OP_DUP OP_HASH160 8777ed55eb9b)
2015-06-19 14:43:09 dsi -- transaction not valid! CMutableTransaction(ver=1, vin.size=2, vout.size=2, nLockTime=0)
CTxIn(COutPoint(5dec5c1e31f715f23333db3e557152ba7720f254e2fca2dafeab2dca4177fb0e, 15), scriptSig=)
CTxIn(COutPoint(5dec5c1e31f715f23333db3e557152ba7720f254e2fca2dafeab2dca4177fb0e, 18), scriptSig=)
CTxOut(nValue=1.00001000, scriptPubKey=OP_DUP OP_HASH160 23ae83efdc20)
CTxOut(nValue=1.00001000, scriptPubKey=OP_DUP OP_HASH160 8777ed55eb9b)

2015-06-19 14:43:09 DoAutomaticDenominating : Running Darksend denominate. Return ''

 

[TanteStefana]

I have 2000 at 5 rounds and in the last 1.5 hours it went from 24% to 26%

Not the speed of light but progress none the less

 

[splawik21]

Tante I have 6 wallets mixing......since my last post I have not even have 1 denomination done yet

 

[UdjinM6]

Ok, I just got back home and will try to answer all the questions quick here:
1) Red amount/rounds - hover your mouse over it and you'll see why (in short it now shows how many you can actually anonymize, see more info on hover)
2) Mining on testnet - thanks to thelazier fix there should be no more bugs on miners side afaik so throw some hashes, I don't need to mine to debug anymore (I hope so)
3) Current binaries are NOT compatible with mainnet yet, do not run it that way - you'll corrupt your blockchain and will have to reindex/redownload. That's a known one and there are fixes for that but we are still choosing which one to apply.
4) "dsi - transaction not valid" is a known one too. I got some of these in my wallet, not sure if it's smth on client or MN side. I think it's on MN side but still investigating.

 

[TanteStefana]

Tante I have 6 wallets mixing......since my last post I have not even have 1 denomination done yet

That's weird, mine now reads 22%, but I do see it working. That bar has always gone up and down, but I have no idea why.....!

Ok, so I am wondering if there is something new to test out. I've been looking over my qt wallet and I don't see anything new yet I know that this is all about the voting thing. Where is all the new stuff? How does it work?

 

[splawik21]

1 out of 6 wallet is mixing and is @ 21% now.....

 

[TanteStefana]

so I'm trying to play with the budgeting, and can't seem to get it right. I guess I don't understand how to read the error/help output.

If I want to see current proposals, do I go:

dash-cli mnbudget -show ?

To propose a project to be funded, do I go:

dash-cli mnbudget -create?

It's not working for me at the moment (and I'm using my MN wallet that is running a MN)

Thanks for any help

 

[TanteStefana]

I guess I don't understand how to read/implement these commands:

error: {"code":-1,"message":"mnbudget \"command\"... ( \"passphrase\" )\nVote or show current budgets\n\nAvailable commands:\n vote-many - Vote on a Dash initiative\n vote-alias - Vote on a Dash initiative\n vote - Vote on a Dash initiative/budget\n getvotes - Show current masternode budgets\n getinfo - Show current masternode budgets\n show - Show all budgets\n"}

Can anyone list exactly how they're used? That is, where to use a - and where to put a space? Thanks!

 

[moli]

Ok, I just got back home and will try to answer all the questions quick here:
1) Red amount/rounds - hover your mouse over it and you'll see why (in short it now shows how many you can actually anonymize, see more info on hover)
.

Ok here's a screenshot of my wallet and the difference between the amounts is 1000 tDASH:

Looking at the coin control and that is the amount I got from coingun's faucet (http://test.faucet.masternode.io/)... So now the wallet is telling me that amount will not be split up to anonymize until I manually split it up, because DS thinks it's a MN?

What about poiuty's wallet? What changed his setting for the amount-to-keep-anonymized? (he said he didn't do it).
Does it also mean that if a user, without knowing about this fact, tries to anonymize his 1000 Dash, DS would not budge and the user will conclude DS doesn't work? :grin:

 

[UdjinM6]

Ok here's a screenshot of my wallet and the difference between the amounts is 1000 tDASH:

View attachment 1459

Looking at the coin control and that is the amount I got from coingun's faucet (http://test.faucet.masternode.io/)... So now the wallet is telling me that amount will not be split up to anonymize until I manually split it up, because DS thinks it's a MN?

View attachment 1460

What about poiuty's wallet? What changed his setting for the amount-to-keep-anonymized? (he said he didn't do it).
Does it also mean that if a user, without knowing about this fact, tries to anonymize his 1000 Dash, DS would not budge and the user will conclude DS doesn't work? :grin:

Yep, when you use local masternode and not masternode.conf there is no way to say which input is MN so wallet just excludes anything that is "MN-like". We can disable that but I'm not sure if that's the right move.
As for poiuty 's wallet - he basically set amount-to-keep-anonymized to some value that is higher than his balance and that's why he can see it in red on overview page (and again it shows only amount he can anonymize and not the actual settings in such situations).

Btw if you set amount-to-keep-anonymized to some value that is lower than your "anonymizable balance" you would see exact value that match settings.

EDIT: another scenario for "MN-like" outputs is when you use some additional/secondary wallet and have same private keys imported there. However we can warn user in such edge situations and still mix it if he agrees to do so but no one actually read warnings and/or instructions :grin: but, well, I agree for some users that have no idea of all that MN tech things that could look like "hmmm.... it's broken, nothing works here!!11" so let's try to find a suitable solution, I'm open for new ideas :smile:

EDIT2: hmmm, you can't actually mix in local masternode mode at all, I was wrong about that one so the only scenario I can see now is ^^^^ which I think is 1) quite rare, 2) used by advanced users who can import private keys so should be aware of what are they doing. In that case it's quite safe to disable protection of unlocked MN-like outputs (outputs mentioned in masternode.conf are locked automatically on wallet start). Or am I missing even another scenario?

 

[moli]

UdjinM6 - I'm checking another testnet wallet... Two 1000 tDASH amounts, "Amount and Round" are set at 1000/8 but they show "0/0", meaning DS mixing can't be run but it keeps sending messages that do not give a clue why it's not running.
May I suggest to change "Last DS message" to something like this:

Edit: Change "avoid anonymizing Masternodes" to "avoid messing up/ splitting up Masternodes.."

 

[MangledBlue]

So my coins are not mixing because they are still 1000tDASH amounts?

 

[moli]

So my coins are not mixing because they are still 1000tDASH amounts?

Correct. Send 1 Dash to another address and try again

 

[bertlebbert]

Ok here's a screenshot of my wallet and the difference between the amounts is 1000 tDASH:

View attachment 1459

Looking at the coin control and that is the amount I got from coingun's faucet (http://test.faucet.masternode.io/)... So now the wallet is telling me that amount will not be split up to anonymize until I manually split it up, because DS thinks it's a MN?

View attachment 1460

What about poiuty's wallet? What changed his setting for the amount-to-keep-anonymized? (he said he didn't do it).
Does it also mean that if a user, without knowing about this fact, tries to anonymize his 1000 Dash, DS would not budge and the user will conclude DS doesn't work? :grin:

Haha, that's me to a tee! I've been trying unsuccessfully to anonymize 1000 tDash, and simply concluded it simply doesn't work. I'm glad that it's cleared up :smile:

 

[moli]

Haha, that's me to a tee! I've been trying unsuccessfully to anonymize 1000 tDash, and simply concluded it simply doesn't work. I'm glad that it's cleared up :smile:

I hope the devs will change this to a solution that DS can't mix Masternodes but at the same time users still can mix 1000 dash or get a warning to let them know. I was wondering too why some people said they couldn't mix DS. It's not ok to not make the software communicate with users.

 

[bertlebbert]

I hope the devs will change this to a solution that DS can't mix Masternodes but at the same time users still can mix 1000 dash or get a warning to let them know. I was wondering too why some people said they couldn't mix DS. It's not ok to not make the software communicate with users.

In one (hot) wallet I run MN from, Darksend is disabled by default; I just assumed this was precaution to not disable MN. But in another wallet to which I sent exactly 1000 tDark for mixing, I couldn't for the life of me figure why I couldn't get it to work- till NOW! Thank you

 

[moli]

In one (hot) wallet I run MN from, Darksend is disabled by default; I just assumed this was precaution to not disable MN. But in another wallet to which I sent exactly 1000 tDark for mixing, I couldn't for the life of me figure why I couldn't get it to work- till NOW! Thank you

No problem. Sorry to hear. This rule has been in effect for a few months now. I thought it was a good thing so people wouldn't mix their masternodes by accident, but now looking at it and wondering why there haven't been many mixers on the blockchain.. lol..

eduffield UdjinM6 - We are allowed to set 1000 DASH as the amount-to-keep-anonymized but we can't mix exactly 1000 DASH, this is against the consistency rule in programming :tongue:

 

[MangledBlue]

There ya go......

LEAVE everything like it is - just make a RULE in the options so you cannot set it to 1000DASH or MN-like

edit
and/or - do all that and make a 2-3 tier confirmation - Do you really want to do this?

 

[moli]

From the wallet with two 1000 tDASH amounts, I sent 1 tDASH to myself. It's like a gate to open up for one of the 1000 amounts to be mixed. DS jumped right in and started doing its job right away!

Now I just need to send another 1 tDASH and the rest can be in the mixing pool.