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.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 ?
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 and a SSL/TLS cert.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.