This new version is simply awesome so far! Great job to the dev team. You make this product easy to sell. Can't wait for the finished, streamlined release!
V12.1 Testnet Launch Thread
- Thread starter eduffield
- Start date
-
- Tags
- 12.1 masternode trezor testnet
- Status
finally updated, sorry!
Could somebody direct me to where I can find/read about all the new tools and how to use them? Thanks so much
Could somebody direct me to where I can find/read about all the new tools and how to use them? Thanks so much
Last edited:
Sorry, but my wallet just won't mix. I have it set to 2000 at 8X and I've cleaned everything out of testnet3. It's a persistent problem for me.
Anyone want my debug? Please download it here: http://www.steemjammer.com/share/debug.log
strange, i have no problems with mixing.
windows 10, 64bit, v0.12.1.0-3d2bc6a
Check if you are on latest wallet version here : https://www.dash.org/forum/threads/v12-1-testnet-launch-thread.9014/page-15#post-95995
Check if you are synced in accordance with these two blockchain explorers :
https://test.explorer.dash.org/chain/tDash
https://test.explorer.dash.org/chain/tDash
Additional info
I'm running these commandline options with my windows wallets : -reindex -privatesendmultisession=1 -zapwallettxes=1 -keypool=10000 (the last will create a lot more keys for mixing usage and i did this on a new wallet a few versions back)
windows 10, 64bit, v0.12.1.0-3d2bc6a
Check if you are on latest wallet version here : https://www.dash.org/forum/threads/v12-1-testnet-launch-thread.9014/page-15#post-95995
Check if you are synced in accordance with these two blockchain explorers :
https://test.explorer.dash.org/chain/tDash
https://test.explorer.dash.org/chain/tDash
Additional info
I'm running these commandline options with my windows wallets : -reindex -privatesendmultisession=1 -zapwallettxes=1 -keypool=10000 (the last will create a lot more keys for mixing usage and i did this on a new wallet a few versions back)
Last edited:
did exatly this , started a new PrivateSend 2000tDash ,8 Round Mix and looks like its mixing and very fast , thanks alot
In your pictures, all your wallets seem to have unconfirmed denominations? My problem is that my wallet says "found unconfirmed denominated outputs, will wait till they confirm to continue"strange, i have no problems with mixing.
windows 10, 64bit, v0.12.1.0-3d2bc6a
Check if you are on latest wallet version here : https://www.dash.org/forum/threads/v12-1-testnet-launch-thread.9014/page-15#post-95995
Check if you are synced in accordance with these two blockchain explorers :
https://test.explorer.dash.org/chain/tDash
https://test.explorer.dash.org/chain/tDash
Additional info
I'm running these commandline options with my windows wallets : -reindex -privatesendmultisession=1 -zapwallettxes=1 -keypool=10000 (the last will create a lot more keys for mixing usage and i did this on a new wallet a few versions back)
I should be on the correct wallet unless I did something wrong: Dash Core version v0.12.1.0-3d2bc6a (64-bit)
Also, what does -privatesendmultisession=1 do? That's the only thing I didn't do. Does it allow for mixing when there are outstanding confirmations on part of the balance? That might be why you have been able to mix despite having unconfirmed transactions (PriateSend denominate)
This is the first time my wallet showed conflicted as well. Previously, it was only unconfirmed and it wouldn't mix.
I still think there is a problem here. After updating, I did clean out the .dash folder except the wallet.dat file and the masternode.dat file. I then restarted the wallet with --zapwallettxes. I'm on the correct block as well. Thanks for looking
Latest builds (git-ee31604) of v0.12.1.x branch
Linux --> https://dashpay.atlassian.net/builds/browse/DASHL-DEV-559/artifact/JOB1/gitian-linux-dash-dist/
Windows --> https://dashpay.atlassian.net/builds/browse/DASHW-DEV-506/artifact/JOB1/gitian-win-dash-dist/
MacOS X --> https://dashpay.atlassian.net/builds/browse/DASHM-DEV-515/artifact/JOB1/gitian-osx-dash-dist/
Raspberry --> https://dashpay.atlassian.net/builds/browse/DASHP-DEV-511/artifact/JOB1/gitian-RPi2-dash-dist/
Changelog:
Merge https://github.com/dashpay/dash/pull/865 [Wallet] Transaction View: LastMonth calculation simplyfied
Merge https://github.com/dashpay/dash/pull/822 [Core]: fix restart hanging during wallet-repair
Testnet tools (explorers, faucets, pools) --> https://www.dash.org/forum/threads/testnet-tools-resources.1768/
Linux --> https://dashpay.atlassian.net/builds/browse/DASHL-DEV-559/artifact/JOB1/gitian-linux-dash-dist/
Windows --> https://dashpay.atlassian.net/builds/browse/DASHW-DEV-506/artifact/JOB1/gitian-win-dash-dist/
MacOS X --> https://dashpay.atlassian.net/builds/browse/DASHM-DEV-515/artifact/JOB1/gitian-osx-dash-dist/
Raspberry --> https://dashpay.atlassian.net/builds/browse/DASHP-DEV-511/artifact/JOB1/gitian-RPi2-dash-dist/
Changelog:
Merge https://github.com/dashpay/dash/pull/865 [Wallet] Transaction View: LastMonth calculation simplyfied
Merge https://github.com/dashpay/dash/pull/822 [Core]: fix restart hanging during wallet-repair
Testnet tools (explorers, faucets, pools) --> https://www.dash.org/forum/threads/testnet-tools-resources.1768/
-privatesendmultisession=1 provides mixing without waiting for transaction confirmations, which really puts a turbo on the whole mixing process. According UdjinM6 there are still some risks using this command as it can cause the wallet to deplete the keypool faster then normal (i'm using keypool=10000 to battle this) and people need to be carefull with their backupsIn your pictures, all your wallets seem to have unconfirmed denominations? My problem is that my wallet says "found unconfirmed denominated outputs, will wait till they confirm to continue"
I should be on the correct wallet unless I did something wrong: Dash Core version v0.12.1.0-3d2bc6a (64-bit)
Also, what does -privatesendmultisession=1 do? That's the only thing I didn't do. Does it allow for mixing when there are outstanding confirmations on part of the balance? That might be why you have been able to mix despite having unconfirmed transactions (PriateSend denominate)
This is the first time my wallet showed conflicted as well. Previously, it was only unconfirmed and it wouldn't mix.
I still think there is a problem here. After updating, I did clean out the .dash folder except the wallet.dat file and the masternode.dat file. I then restarted the wallet with --zapwallettxes. I'm on the correct block as well. Thanks for looking
Links :
https://www.dash.org/forum/threads/v12-1-testnet-launch-thread.9014/page-6#post-95097
https://www.dash.org/forum/threads/v12-1-testnet-launch-thread.9014/page-7#post-95137
About your conflicted transactions, i had a few sporadic conflicted transactions a few versions back but lately they all just confirm.
Cool, thanks. If this newest version works for me, I'll implement that so I can start sending stuff back and forth and test instantX
But it seems that if you use your wallet in the "regular" way, it gets stuck due to transactions not confirming, and you wouldn't be able to see that if you use -privatemultisession... so I'm going to see if this works with the newest version before implementing that Unfortunately, flare doesn't say if he looked at my report, or if anything was there (or if it's just my imagination, LOL) Ah well, busy guys 
I had a quick lookCool, thanks. If this newest version works for me, I'll implement that so I can start sending stuff back and forth and test instantX
but I'm not sure what the exact issue is - some transactions were reported as invalid from the MN side but that shouldn't produce "conflicted" afaik. Let's see if this issue still persists after more nodes are on the 70201.
I'm studying the sendmany command, so far this seems to be working :
sendmany "TestDash1" "{\"ySJmSKL7dw4RiSCUSmpKAk1zUpgP5nN2Ln\":0.01,\"yRpRRQoy7FhY3sZVgQpdCPP6Vd31Vpp6qw\":0.02,\"ySQmPqJZ1ju1qV4ckJQhoiUHkTGo3pVm1J\":0.02,\"yTv8Ni2NbAVkwESskx8YxzEUHdnqHz1amX\":0.02,\"yesY4Ka84aVzQ5RGwRwpJQfmfzfDCzZfhX\":0.02}" 6 "Testing"
sendmany "TestDash1" "{\"ySJmSKL7dw4RiSCUSmpKAk1zUpgP5nN2Ln\":0.01,\"yRpRRQoy7FhY3sZVgQpdCPP6Vd31Vpp6qw\":0.02,\"ySQmPqJZ1ju1qV4ckJQhoiUHkTGo3pVm1J\":0.02,\"yTv8Ni2NbAVkwESskx8YxzEUHdnqHz1amX\":0.02,\"yesY4Ka84aVzQ5RGwRwpJQfmfzfDCzZfhX\":0.02}" 6 "Testing"
This will sent 1x 0.01 and 4x 0.02 tDash to 5 different wallets with TestDash1 the receiving address from where they are sent from. For testing purposes it would be great if we could do this with InstantSend as well, is there a way to use the sendmany command with InstantSend ?
Last edited:
OK, I haven't moved forward (been at 22% for days despite updates and cleaning everything out and clearing transactions each time). And this has been for many days now, so I hope this version worksI had a quick look
At this moment, I see my private sends clearing, which means it's working. I'm at 23% after about an hour 20 minutes. I've done nothing different, so if it's working now, maybe it was corrected when something else was fixed? Anyway, so far, definitely so good. 5 denominations cleared since I updated, none conflicted none hanging
Code:
help sendmany
sendmany "fromaccount" {"address":amount,...} ( minconf "comment" ["address",...] subtractfeefromamount use_is use_ps )
Send multiple times. Amounts are double-precision floating point numbers.
Arguments:
1. "fromaccount" (string, required) DEPRECATED. The account to send the funds from. Should be "" for the default account
2. "amounts" (string, required) A json object with addresses and amounts
{
"address":amount (numeric or string) The dash address is the key, the numeric amount (can be string) in BTC is the value
,...
}
3. minconf (numeric, optional, default=1) Only use the balance confirmed at least this many times.
4. "comment" (string, optional) A comment
5. subtractfeefromamount (string, optional) A json array with addresses.
The fee will be equally deducted from the amount of each selected address.
Those recipients will receive less dashs than you enter in their corresponding amount field.
If no addresses are specified here, the sender pays the fee.
[
"address" (string) Subtract fee from this address
,...
]
6. "use_is" (bool, optional) Send this transaction as InstantSend (default: false)
7. "use_ps" (bool, optional) Use anonymized funds only (default: false)
...Code:help sendmany sendmany "fromaccount" {"address":amount,...} ( minconf "comment" ["address",...] subtractfeefromamount use_is use_ps ) Send multiple times. Amounts are double-precision floating point numbers. Arguments: 1. "fromaccount" (string, required) DEPRECATED. The account to send the funds from. Should be "" for the default account 2. "amounts" (string, required) A json object with addresses and amounts { "address":amount (numeric or string) The dash address is the key, the numeric amount (can be string) in BTC is the value ,... } 3. minconf (numeric, optional, default=1) Only use the balance confirmed at least this many times. 4. "comment" (string, optional) A comment 5. subtractfeefromamount (string, optional) A json array with addresses. The fee will be equally deducted from the amount of each selected address. Those recipients will receive less dashs than you enter in their corresponding amount field. If no addresses are specified here, the sender pays the fee. [ "address" (string) Subtract fee from this address ,... ] 6. "use_is" (bool, optional) Send this transaction as InstantSend (default: false) 7. "use_ps" (bool, optional) Use anonymized funds only (default: false) ...
Can you please tell me what i'm doing wrong ? Thanks
note : i'm doing this from console in windows wallet
Can you please tell me what i'm doing wrong ? Thanks
Replace "use_is" with true in your command
sendmany "TestDash1" "{\"ySJmSKL7dw4RiSCUSmpKAk1zUpgP5nN2Ln\":0.01,\"yRpRRQoy7FhY3sZVgQpdCPP6Vd31Vpp6qw\":0.02,\"ySQmPqJZ1ju1qV4ckJQhoiUHkTGo3pVm1J\":0.02,\"yTv8Ni2NbAVkwESskx8YxzEUHdnqHz1amX\":0.02,\"yesY4Ka84aVzQ5RGwRwpJQfmfzfDCzZfhX\":0.02}" 6 "Testing" "true"Replace "use_is" with true in your command
JSON value is not an array as expected (code -1)
Ah, right, you are also missing subtractfeefromamount param
try
Code:
sendmany "TestDash1" "{\"ySJmSKL7dw4RiSCUSmpKAk1zUpgP5nN2Ln\":0.01,\"yRpRRQoy7FhY3sZVgQpdCPP6Vd31Vpp6qw\":0.02,\"ySQmPqJZ1ju1qV4ckJQhoiUHkTGo3pVm1J\":0.02,\"yTv8Ni2NbAVkwESskx8YxzEUHdnqHz1amX\":0.02,\"yesY4Ka84aVzQ5RGwRwpJQfmfzfDCzZfhX\":0.02}" 6 "Testing" "[]" true
- Apr 8, 2014
- 1,971
- 1,339
- 1,283
This is creazy, after 10 minutes of mixing 100coins @ 4 rounds already 30-40% done
edit: after 1h and 20 min there were already +95% done, the last 5% take longer but now 99,2 coins, 98,4 coins mixed and the last one is lagging a bit
Nice results anyway!
edit2:
1st wallet 100% complete in 1h 58min
2nd wallet 100% complete in 3h 15min
3rd wallet 100% complete in 5h 10 min
edit: after 1h and 20 min there were already +95% done, the last 5% take longer but now 99,2 coins, 98,4 coins mixed and the last one is lagging a bit
Nice results anyway!
edit2:
1st wallet 100% complete in 1h 58min
2nd wallet 100% complete in 3h 15min
3rd wallet 100% complete in 5h 10 min
Last edited:
Well, I still have the same problem. I got to 24% then transactions stopped confirming and I got a conflicted transaction and my wallet says "found unconfirmed denominated outputs...." again.
"found unconfirmed denominated outputs...." generally shouldn't be a problem for -privatesendmultisession mode, wallet should just use other available outputs.
Don't know how to test IS properly, so I made batch file which InstantSend random amount of Dash to another wallet every 20 sec. And it 100% (200+ transactions) fine and had 5 confirmations on receive like this:
First I tested with PS and IS on, but due to incorrect receive log script not sure about result...
Code:
05.06.2016 20:48:52,74 cebac061daa2009b1aac14a188d80d8eec973b4f4c8c47079b9cb7bb2e25e061
{
"amount": 2.00000000,
"confirmations": 5,
"bcconfirmations": 0,
"trusted": true,
"txid": "cebac061daa2009b1aac14a188d80d8eec973b4f4c8c47079b9cb7bb2e25e061",
"walletconflicts": [
],
"time": 1465148928,
"timereceived": 1465148928,
"bip125-replaceable": "no",
"details": [
{
"account": "",
"address": "yd91uXMnv1GbZx1ogPXtcfC68KWyxKReyF",
"category": "receive",
"amount": 2.00000000,
"label": "",
"vout": 0
}
],
"hex": "01000000015523696d4276ce3b7fab514f715d6c0ef25e0b506859ea3040483bd7194b97f1010000006a473044022056aeb4855e92ee7441cfaef727fde5efc30432136616a8ad4f2ecab39b2714a60220686bffa845707244b66afaf389659200a298b1403956eb59487b567b4fbcf2de012102c8d49107010741ea45aca0387b946acb0f02bf30332200969d7d3e5633ff63f1feffffff0200c2eb0b000000001976a914b8812855a7b18378c504701334f9af4a691cac1d88ac0067fb38000000001976a914c9a9205be9d3883ad701ff08fc670e48e5d701f188ac00000000"
}
05.06.2016 20:49:15,18 9fbb21c1a1711f4a2d43c0fb07064fc3e11681218e10481175e579146aaa6aff
{
"amount": 10.00000000,
"confirmations": 5,
"bcconfirmations": 0,
"trusted": true,
"txid": "9fbb21c1a1711f4a2d43c0fb07064fc3e11681218e10481175e579146aaa6aff",
"walletconflicts": [
],
"time": 1465148951,
"timereceived": 1465148951,
"bip125-replaceable": "no",
"details": [
{
"account": "",
"address": "yj8W1iXnz7nBTEvGE4cSgXnJJu8BDse33j",
"category": "receive",
"amount": 10.00000000,
"label": "",
"vout": 1
}
],
"hex": "01000000017fe33cf8bfb0e6168a5ecfda1e062fee6381d521d994840b68ce84a13ab01ad1010000006a4730440220018638a0c170fad0ff0fd493f00e9ab96d983858cdb17199557c437dc65dc210022005883c11f3590e42c880161572c4e56a765761a17670e540242275bcfc81449b012102a2f283cde49a56f6fe8f8622f5ba7c1a39410ab9dc4075c48829833f35f9b5cdfeffffff020040420f000000001976a914585f59d75b4f5f9bf6a4763c68c967885da76be188ac00ca9a3b000000001976a914fa38f569eb5bbd83d60bcb72ec470240c72b032188ac00000000"
}I'm not using -privatesendmultisession. If we're supposed to use that, why isn't it default? I think the wallet should work without special commands. Unless the reason it isn't working is because of a problem only in testnet that doesn't occur in mainnet.
I already answered "why" few times I believe
- we need to make sure that user understand what he is doing and why this can be dangerous (keypool depletion), best way to secure that would be implementation of HD wallet. And that's basically why I think we shouldn't make it default yet, first should appear in Wallet -> Expert features imo.Draft version of UI that would warn user is working like that:
(there will be no smile and arrow in final version btw, though...
)
I think you should add the smile and arrow...I already answered "why" few times I believe
Draft version of UI that would warn user is working like that:
View attachment 2478
(there will be no smile and arrow in final version btw, though...
I can understand that, but I still think that private send should still work without it, and it doesn't. I'm still stuck at 24%. I can go up 1 % if i restart the wallet zapping txes, but then get completely stuck again within a percent. This isn't slow, this is not working.I already answered "why" few times I believe
Draft version of UI that would warn user is working like that:
View attachment 2478
(there will be no smile and arrow in final version btw, though...
I think it should work, even if it's slow. Am I wrong?
If we make private send not an option unless you enable this feature, I can understand. Another thing, the wallet could hold 10,000 coins by default. I have much more in one of my wallets and yet it doesn't seem slow to start or anything. Anyway, if it can't work in "normal" mode, then I think it shouldn't be an option, no?
I say this because otherwise we will get nothing but complaints from users
and it looks unprofessional and sloppy to put users through such frustration
Last edited:
Can you explain
Can you explain what the keypool is?I already answered "why" few times I believe
Draft version of UI that would warn user is working like that:
View attachment 2478
(there will be no smile and arrow in final version btw, though...
- Status