v0.16 Testing

codablock

Active Member
Core Developer
Mar 29, 2017
100
154
93
36
@xkcd Yepp, you've already spotted it :)

We've activated spork21 yesterday. Shortly after that, I accidentally spent collaterals of 150 tMNs due to a bug in one of my provisioning scripts :D

I've setup 300 new MNs with 0.16 and 75 with 0.15. Spork21 already caused multiple of the 0.15 MNs to get PoSe banned, so the new PoSe improvements seems to work as expected. We'll monitor this a few more days and expect all old MNs to get banned by then.

InstantSend is unstable atm, due to the mistake I made yesterday. It should get back on track in the following hours.
 

xkcd

Member
Masternode Owner/Operator
Feb 19, 2017
109
76
78
australia
mnowatch.org
Dash Address
XpoZXRfr2iFxWhfRSAK3j1jww9xd4tJVez
Guys, I need to determine if we have a UI bug in RC2, I had a wallet setup to do nothing but mixing and noted these txes on my overview tab, my understanding is that mixing TXes should be filtered from this screen, is that true? Also, is this a new bug or also happening in v15.0 ?

 

qwizzie

Well-known Member
Aug 6, 2014
1,581
737
183
Guys, I need to determine if we have a UI bug in RC2, I had a wallet setup to do nothing but mixing and noted these txes on my overview tab, my understanding is that mixing TXes should be filtered from this screen, is that true? Also, is this a new bug or also happening in v15.0 ?

RC1 only had 'payment to yourself' mixing txes visible on our overview tab (Recent Transactions), which got classified as a bug by Pasta. If your transactions in RC2 are indeed 'payment to yourself' mixing txes, then that is a known bug for v0.16.
(RC1 & RC2)

See : https://www.dash.org/forum/threads/v0-16-testing.50294/#post-222478

I am not sure if this bug is also present in our Mainnet v0.15 code base.
 
Last edited:

qwizzie

Well-known Member
Aug 6, 2014
1,581
737
183
Currently in v0.16 prune works on lite mode wallets through commandline option -litemode -txindex=0 -prune=945

Link : https://github.com/dashpay/dash/pull/3488

Testnet Wallet : 1,91 GB
Prune Testnet Wallet : 1,09 GB

Will it be possible to implement -txindex=0 -prune=945 on masternodes (mainnet) some day ?
It sure would be handy to limit or reduce expensive SSD storage space for masternodes.
Or will prune be technically impossible on masternodes ?

Downside of prune is having to download the full blockchain in case of blockchain problems
and -reindex / -rescan not working.
 
Last edited:

xkcd

Member
Masternode Owner/Operator
Feb 19, 2017
109
76
78
australia
mnowatch.org
Dash Address
XpoZXRfr2iFxWhfRSAK3j1jww9xd4tJVez
Currently in v0.16 prune works on lite mode wallets through commandline option -litemode -txindex=0 -prune=945

Link : https://github.com/dashpay/dash/pull/3488

Testnet Wallet : 1,91 GB
Prune Testnet Wallet : 1,09 GB

Will it be possible to implement -txindex=0 -prune=945 on masternodes (mainnet) some day ?
It sure would be handy to limit or reduce expensive SSD storage space for masternodes.
Or will prune be technically impossible on masternodes ?

Downside of prune is having to download the full blockchain in case of blockchain problems
and -reindex / -rescan not working.
hahaha, you're gonna love Platform when it launches, each MN needs to keep a fully indexed node (2x space requirement), a running insight, 11 Docker containers o_O and a SSL/TLS cert. :p
 
  • Wow
Reactions: qwizzie

krustamov

New Member
Aug 15, 2020
3
1
3
26
Need some tDash
Does anyone have some spare tDash coins for a couple of hours (10 tDash should be fine)?
All testnet faucets seem dry or down
yWGrGzMeS5gs7pGScwz3Jpppfg3jsLz4qf
Thanks in advance
 

qwizzie

Well-known Member
Aug 6, 2014
1,581
737
183
Need some tDash
Does anyone have some spare tDash coins for a couple of hours (10 tDash should be fine)?
All testnet faucets seem dry or down
yWGrGzMeS5gs7pGScwz3Jpppfg3jsLz4qf
Thanks in advance
Done. It is through a lite mode wallet, so give it some time.
 
  • Love
Reactions: krustamov

Atra-Hasis

New Member
Sep 7, 2020
1
0
1
44
Hello all.
Would anyone kindly send me 1000 tDash? After testing, I will either send back or forward it to someone, of course.
Thanks in advance.
My address: ygCbNEvSFja3ZX4RJB2hh88vKJYZzuiLoY
 

Pasta

Member
Core Developer
Apr 29, 2017
87
81
58
Hello all.
Would anyone kindly send me 1000 tDash? After testing, I will either send back or forward it to someone, of course.
Thanks in advance.
My address: ygCbNEvSFja3ZX4RJB2hh88vKJYZzuiLoY
1005 sent off
 
  • Like
Reactions: qwizzie

qwizzie

Well-known Member
Aug 6, 2014
1,581
737
183
I have been doing some mixing on Mainnet with Dash Core version 0.15 and i noticed that mixing slowed when wallet reached about 90% of my target amount.
Wallet did not find any other people to mix denomination 10.0 with all night, it had absolutely no problem mixing with denominations 0.001, 0.01, 0.1, 1 (which most likely formed that 90%). I noticed this same behavior in v0.16 release candidate 2 on Testnet, the first 90% goes smooth and fast, but then the mixing slows considerably. I suspect (but i am not sure) that denomination 10.0 caused the slow down there as well. Although conditions differ considerably between Testnet and Mainnet.

With regards to mixing on Mainnet i suspect many users simply mix with lower then 10 Dash amounts, which means denomination 10.0 is not mixed that often.

Link :

https://dashradar.com/charts/mixing-transactions-per-day-by-denomination (denomination 10.0 is used considerably less, then denomination 1.0)
https://terminal.bytetree.com/dash (Average Median Transaction Value is about $6)



Is it possible to introduce some kind of check into a user mixing session, which keeps on eye on denomination 10.0 and when that denomination is not getting mixed for a long period of time, it will break the 10.0 denomination down to smaller denominations ? (denomination 1.0 for example). To be done through a special PrivateSend Create Denominations transaction (one that excludes denomination 10.0).

I rather have the wallet continue mixing in a smooth and fast way with the smaller denomination amounts, then have the wallet waste a lot of time trying to mix with a denomination it has difficulty finding a match for on Mainnet.

A switch to smaller denominations in the specific situation that the wallet can't find a match for denomination 10.0 for some time, could speed things up on Mainnet for mixing larger Dash amounts (a few hundreds of Dash).
 
Last edited:

splawik21

Grizzled Member
Dash Core Team
Moderator
Foundation Member
Dash Support Group
Apr 8, 2014
1,923
1,280
1,283
  • Like
Reactions: qwizzie and xkcd

UdjinM6

Official Dash Dev
Dash Core Team
Moderator
May 20, 2014
3,638
3,538
1,183
Currently in v0.16 prune works on lite mode wallets through commandline option -litemode -txindex=0 -prune=945

Link : https://github.com/dashpay/dash/pull/3488

Testnet Wallet : 1,91 GB
Prune Testnet Wallet : 1,09 GB

Will it be possible to implement -txindex=0 -prune=945 on masternodes (mainnet) some day ?
It sure would be handy to limit or reduce expensive SSD storage space for masternodes.
Or will prune be technically impossible on masternodes ?

Downside of prune is having to download the full blockchain in case of blockchain problems
and -reindex / -rescan not working.
This is not possible currently because they need to verify governance objects which rely on op_returns and op_returns are pruned. But even if we would implement them say via special txes IMO it should not be possible for masternodes to run in prune mode because they are meant to be full archived nodes serving the blockchain to new nodes.

I have been doing some mixing on Mainnet with Dash Core version 0.15 and i noticed that mixing slowed when wallet reached about 90% of my target amount.
Wallet did not find any other people to mix denomination 10.0 with all night, it had absolutely no problem mixing with denominations 0.001, 0.01, 0.1, 1 (which most likely formed that 90%). I noticed this same behavior in v0.16 release candidate 2 on Testnet, the first 90% goes smooth and fast, but then the mixing slows considerably. I suspect (but i am not sure) that denomination 10.0 caused the slow down there as well. Although conditions differ considerably between Testnet and Mainnet.

With regards to mixing on Mainnet i suspect many users simply mix with lower then 10 Dash amounts, which means denomination 10.0 is not mixed that often.

Link :

https://dashradar.com/charts/mixing-transactions-per-day-by-denomination (denomination 10.0 is used considerably less, then denomination 1.0)
https://terminal.bytetree.com/dash (Average Median Transaction Value is about $6)



Is it possible to introduce some kind of check into a user mixing session, which keeps on eye on denomination 10.0 and when that denomination is not getting mixed for a long period of time, it will break the 10.0 denomination down to smaller denominations ? (denomination 1.0 for example). To be done through a special PrivateSend Create Denominations transaction (one that excludes denomination 10.0).

I rather have the wallet continue mixing in a smooth and fast way with the smaller denomination amounts, then have the wallet waste a lot of time trying to mix with a denomination it has difficulty finding a match for on Mainnet.

A switch to smaller denominations in the specific situation that the wallet can't find a match for denomination 10.0 for some time, could speed things up on Mainnet for mixing larger Dash amounts (a few hundreds of Dash).
v0.16 has some improvements to create more of smaller denoms when possible but in general you want some balance there because creating lots of small denoms doesn't help really - you can't pay for anything without using lots of them and this makes on-chain analysis easier which defeats the whole idea.
 
  • Like
Reactions: xkcd and qwizzie

Pasta

Member
Core Developer
Apr 29, 2017
87
81
58
Hey all,

reallocation HF is active(activated at block 387500), and the reallocation has started. The first reallocation can be seen here https://testnet-insight.dashevo.org...f866ab054e57b36077d09622e9814b4385fbfe160b363

Spork 21 is also active on testnet.

v15 nodes did fork off as expected, and it appears that chain has stalled on testnet as expected.

Next is for spork 22 to be activated on testnet. All systems operational so far.

Let us know of any issues that you have. Expect either a (very short lived) rc4 to be tagged soon, or for the .0 release to be tagged soon
 

Pasta

Member
Core Developer
Apr 29, 2017
87
81
58
Testnet reallocation points for anyone interested


Reallocation points (block height, percentage to MN)
387504 51.30%
387576 52.60%
387648 53.30%
387720 54.00%
387792 54.60%
387864 55.20%
387936 55.70%
388008 56.20%
388080 56.70%
388152 57.20%
388224 57.70%
388296 58.20%
388368 58.50%
388440 58.80%
388512 59.10%
388584 59.40%
388656 59.70%
388728 59.90%
388800 60.00%