v13.0 Testing

v0.13.0.0-rc2 (Windows 10, 64 bit)

There are a few problems with the dutch translation in this version, both with the layout (not all text readable) and the translation into Dutch :

Tools --> Peers list / Hulpmiddelen --> Peers lijst

wF6G9fs.jpg


Peers (Tab)
$Peers --> Peers

Portemonnee Herstel (Tab)

Click buttons

Gerede portemonnee --> Herstel portemonnee
Herstelde transacties 1 --> Herstel transacties 1
Herstelde transacties 2 --> Herstel transacties 2
Upgrade portemonnee formaat --> Upgrade portemonnee
Herbouw de index --> Herbouw index

Click buttons description

-red portemonnee: Poging om geheime sleutels terug te halen uit het beschadigede portemonnee bestand (wallet.dat)
fix : -herstel portemonnee: Poging om geheime sleutels terug te halen uit het beschadigde portemonnee bestand (wallet.dat)

-zapwallettxes=1: Herstelde transacties van de blokketen (behoud metadata;bv.accounteigenaar)
fix : -zapwallettxes=1: Herstel transacties van de blokketen (behoud metadata;bv.accounteigenaar)

-zapwallettxed=2: Herstelde transacties van de blokketen (laat metadata vervallen)
fix : -zapwallettxes=2: Herstel transacties van de blokketen (laat metadata vervallen)

-upgrade portemonnee= Upgrade portemonnee naar het laatste formaat bij het starten: (Noot: dit is GEEN update van de portemonnee zelf)
fix : -upgrade portemonnee= Upgrade portemonnee naar het laatste formaat bij het starten: (Let op: dit is GEEN update van de portemonnee zelf)


Edit 1: is there a specific reason why we disabled/overruled listen=0 as commandline option for dash-qt.exe on Testnet ? (i can understand disabling it for Mainnet but for Testnet it can be handy running several dash-qt.exe at the same time .. specially for testing mixing and instantsend.

Edit 2 : only http://faucet.test.dash.crowdnode.io/ seems to work at the moment, providing a small test amount (51.5 tDash). The rest is either dry or we cant connect to it.

Edit 3 : PrivateSend messages during mixing look a bit crowded and get cut off :

PU95nUo.jpg


Edit 4 : PrivateSend transactions dont seem to get confirmed in order of age for now, it seems more irregular :

wIwq1IK.jpg
 
Last edited:
v0.13.0.0-rc2 (Windows 10, 64 bit)

Some Finnish strings untranslated (missing dash_en.ts string or other glitch).
I think these are also untranslated with other languages.

-----------------------------

- Transactions tab -> Transaction details -> Transaction total size: -> bytes

- Settings -> Options -> Wallet -> Show popups for privatesend transactions

- Settings -> Encrypt Wallet -> Cancel and next window -> Yes and Cancel

- Settings -> Change passphrase - Cancel

- Settings -> Unlock wallet -> Cancel

- Receive tab -> Request payment -> Close

- Help -> Commandline options -> -minsporkkeys=<n> ->
Overrides minimum spork signers to change spork value. Only useful for regtest and devnet. Using this on mainnet or testnet will ban you.

- Help -> Commandline options -> -privatesendsessions=<n> ->
Use N separate masternodes in parallel to mix funds (1-10, default: 4)

- Help -> Privatesend information -> ALL

- Help -> About QT -> ALL

-----------------------------
 
Hello, while working on v13 "Evolution", can you please revisit my idea of new address type for Dash Insta-Send, as described here ?
https://github.com/dashpay/dash/issues/1559

"Assume a retail merchant wants to accept ONLY InstantSend transactions.
Today there is no way to make it happen. A retailer accepting Dash may get a normal transaction, and get double-spend attacked. This technique will improve zero-confirmation security from the retailer point of view.
I would like to propose a new Dash address type (starting with "IX..." or "D..."), which will only accept InstantSend transaction types. (but allow to spend/outgoing to any address)"
 
Which explorer is actually working correctly and is up to date ? I tested them all and none matches my current block 264575 (which seems stuck)

Is this one correct ? https://testnet-insight.dashevo.org/insight/

Edit 1 : i'm doing a reindex, see if that helps.
Edit 2: my wallet is now synced to https://testnet-insight.dashevo.org/insight/ but i have still transactions not getting confirmed, even after having zapwallettxes them from within the wallet
(recover transactions 1 & recover transactions 2). These transactions get republished with a new date to the blockchain, but they are not getting confirmed.
They seem to be stuck in mempool or something.

Update : after 1 hour my transactions started to get confirmed. I think i will hold off with further mixing untill mining gets more fluid.
 
Last edited:
qwizzie said:
v0.13.0.0-rc2 (Windows 10, 64 bit)
There are a few problems with the dutch translation in this version, both with the layout (not all text readable) and the translation into Dutch :

Edit 3 : PrivateSend messages during mixing look a bit crowded and get cut off :
Click to expand...

Hi @qwizzie - thanks for your language improvement suggestions, I have submitted these for review to our maintainer for Dutch.

The issues with cut off text you are seeing are due to improper scaling on a High-DPI ("retina") screen when using Windows. Unfortunately some widgets still use absolute pixel sizes, while Windows is attempting to scale your fonts 200%. You can correct this by closing Dash, then right-clicking on dash-qt.exe and selecting Properties > Compatibility > Change high DPI settings > Override high DPI scaling performed by > System. The scaling behaviour should be corrected when you restart Dash.

AjM said:
v0.13.0.0-rc2 (Windows 10, 64 bit)
Some Finnish strings untranslated (missing dash_en.ts string or other glitch).
I think these are also untranslated with other languages.
Click to expand...

Hi @AjM - thanks for the Finnish translations you contributed last week. I can confirm that many of the strings you have reported are indeed not present in the version of dash_en.ts currently on Transifex. I'll let @UdjinM6 reply about the status of that file and the strings it contains. The "PrivateSend information" dialog seems to be fully translated in Finnish on Transifex, so either this was done after the translation was pulled from Transifex, or there was a syntax error that is causing it not to build. The "About Qt" dialog is probably built from language in the Qt library itself and cannot be translated by us.
 
strophy said:
Hi @AjM - thanks for the Finnish translations you contributed last week. I can confirm that many of the strings you have reported are indeed not present in the version of dash_en.ts currently on Transifex. I'll let @UdjinM6 reply about the status of that file and the strings it contains. The "PrivateSend information" dialog seems to be fully translated in Finnish on Transifex, so either this was done after the translation was pulled from Transifex, or there was a syntax error that is causing it not to build. The "About Qt" dialog is probably built from language in the Qt library itself and cannot be translated by us.
Click to expand...

Hi @strophy , "PrivateSend information" is translated from the beginning, i checked my translation and there was little 'glitch', but this is working ok v.0.12.3.3.
@UdjinM6 reported last year that "About QT" translation was working in his local build. https://github.com/dashpay/dash/issues/1661

EDIT: "About QT" is working ok in the linux (Mint 18.3), maybe this problem is somehow related that my windows is in virtualbox and language is english.

EDIT 2: v0.13.0.0-rc3 "PrivateSend information" glitch pic attached.
psinfo.png
 
Last edited:
v0.13.0.0-rc3 has just been released. Please upgrade. To see if you're on the correct chain, call "getblockhash 264978" and verify that it returns "
00000000100625f33be83bc1cebe4087ebf521c5ddd860c3304ea73967473e2c". If it doesn't, try "reconsiderblock 00000000100625f33be83bc1cebe4087ebf521c5ddd860c3304ea73967473e2c"
 
v0.13.0.0-rc2

I had a problem using UdjinM6's bootstrap to sync to block 264784, the syncing would not complete.

https://github.com/UdjinM6/dash-bootstrap#for-testnet

For testnet:
Block 264784: Thu Nov 15 00:16:41 UTC 2018 zip (1.9G) SHA256

I suspect this bootstrap snapshot is not useable for current testnet.
I went back to deleting blockchain and syncing from scratch.

Problem : Dash hangs during syncing (syncing headers 93.1% and then stops)

2018-11-15 08:02:53 CMasternodeSync:processTick -- nTick 191 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 08:02:59 CMasternodeSync:processTick -- nTick 192 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 08:03:05 CMasternodeSync:processTick -- nTick 193 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 08:03:11 CMasternodeSync:processTick -- nTick 194 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 08:03:17 CMasternodeSync:processTick -- nTick 195 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 08:03:23 CMasternodeSync:processTick -- nTick 196 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 08:03:29 CMasternodeSync:processTick -- nTick 197 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 08:03:35 CMasternodeSync:processTick -- nTick 198 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 08:03:41 CMasternodeSync:processTick -- nTick 199 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 08:03:47 CMasternodeSync:processTick -- nTick 200 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 08:03:53 CMasternodeSync:processTick -- nTick 201 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 08:03:53 CMasternodeSync:processTick -- nTick 201 nCurrentAsset 0 -- requesting sporks from peer=0
2018-11-15 08:03:53 CMasternodeSync:processTick -- nTick 201 nCurrentAsset 0 -- requesting sporks from peer=2
2018-11-15 08:03:53 CMasternodeSync:processTick -- nTick 201 nCurrentAsset 0 -- requesting sporks from peer=3
2018-11-15 08:03:53 CMasternodeSync:processTick -- nTick 201 nCurrentAsset 0 -- requesting sporks from peer=4
2018-11-15 08:03:59 CMasternodeSync:processTick -- nTick 202 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 08:03:59 CMasternodeSync:processTick -- nTick 202 nCurrentAsset 0 -- requesting sporks from peer=6
2018-11-15 08:03:59 CMasternodeSync:processTick -- nTick 202 nCurrentAsset 0 -- requesting sporks from peer=7
2018-11-15 08:04:05 CMasternodeSync:processTick -- nTick 203 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 08:04:11 CMasternodeSync:processTick -- nTick 204 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 08:04:11 CMasternodeSync:processTick -- nTick 204 nCurrentAsset 0 -- requesting sporks from peer=8
2018-11-15 08:04:17 CMasternodeSync:processTick -- nTick 205 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000

I will update to new version 0.13.0.0-rc3 and see if that helps with syncing.

v0.13.0.0-rc3

Update 1: that seems to have helped, i'm fully syncing now.

Update 2 : stuck at block 263798 (nov 13 2018), 46 hours behind. Syncing headers 99.6%

2018-11-15 09:02:14 CMasternodeSync::processTick -- nTick 499 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 09:02:20 CMasternodeSync::processTick -- nTick 500 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 09:02:26 CMasternodeSync::processTick -- nTick 501 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 09:02:26 CMasternodeSync::processTick -- nTick 501 nCurrentAsset 0 -- requesting sporks from peer=2
2018-11-15 09:02:26 CMasternodeSync::processTick -- nTick 501 nCurrentAsset 0 -- requesting sporks from peer=10
2018-11-15 09:02:32 CMasternodeSync::processTick -- nTick 502 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 09:02:32 CMasternodeSync::processTick -- nTick 502 nCurrentAsset 0 -- requesting sporks from peer=3
2018-11-15 09:02:32 CMasternodeSync::processTick -- nTick 502 nCurrentAsset 0 -- requesting sporks from peer=4
2018-11-15 09:02:38 CMasternodeSync::processTick -- nTick 503 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 09:02:38 CMasternodeSync::processTick -- nTick 503 nCurrentAsset 0 -- requesting sporks from peer=5
2018-11-15 09:02:38 CMasternodeSync::processTick -- nTick 503 nCurrentAsset 0 -- requesting sporks from peer=6
2018-11-15 09:02:44 CMasternodeSync::processTick -- nTick 504 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 09:02:44 CMasternodeSync::processTick -- nTick 504 nCurrentAsset 0 -- requesting sporks from peer=7
2018-11-15 09:02:50 CMasternodeSync::processTick -- nTick 505 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 09:02:56 CMasternodeSync::processTick -- nTick 506 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 09:03:02 CMasternodeSync::processTick -- nTick 507 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 09:03:08 CMasternodeSync::processTick -- nTick 508 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 09:03:14 CMasternodeSync::processTick -- nTick 509 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 09:03:20 CMasternodeSync::processTick -- nTick 510 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000

Update 3 : closing and restarting wallet jumps block to 263813 (13 nov 2018), 45 hours behind
and then hangs again. Using the bootstrap on this version (v0.13.0.0-rc3) hangs at block 263812.

Which means i cant verify block 264978 or have it reconsidered.

Update 4 : After giving it another try today, my two windows wallets (i had this problem with two wallets) finally started to further sync from two days ago to current date.
I have no idea why it took 20 minutes / 150 nTicks to find next UpdateTip, so it could continue the sync .. but it finally synced completely.

2018-11-15 19:36:31 CMasternodeSync::processTick -- nTick 148 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 19:36:37 CMasternodeSync::processTick -- nTick 149 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 19:36:43 CMasternodeSync::processTick -- nTick 150 nCurrentAsset 0 nTriedPeerCount 0 nSyncProgress -0.250000
2018-11-15 19:36:45 Timeout downloading headers from peer=0, disconnecting
2018-11-15 19:36:45 ThreadSocketHandler -- removing node: peer=0 addr=18.136.12.8:19999 nRefCount=1 fInbound=0 fMasternode=0
2018-11-15 19:36:46 UpdateTip: new best=0000000004e059b7661d55e6a5e96b474b1eb04894581f6b0289a3eac37a2636 height=263814 version=0x20000008 log2_work=54.79437054 tx=6337413 date='2018-11-13 11:20:07' progress=0.999680 cache=0.0MiB(6txo)
 
Last edited:
UdjinM6 said:
Translations should be fixed by https://github.com/dashpay/dash/pull/2451

Re sync issues: there are a lot of different versions on testnet, things will get better once we rebuild our testnet mn cluster.
Click to expand...

Thank you UdjinM6.

I'm doing some PrivateSend mixing and i'm noticing a real improvement in speed with the "enable PrivateSend multi-session" option, which we can now activate in the Settings / Options / Wallet (this is new in v0.13 correct ?). Well done.

-privatesendmultisession=<n> Enable multiple PrivateSend mixing sessions per block, experimental (0-1, default: 0)

Seeing its off by default, you may consider (if it pass the testing) to setting it on as default.

Edit : also i'm starting to see a few (2 so far) conflicted transactions during my mixing, FYI.
Most (99.9%) of my mixing transactions though are getting confirmed fast and pretty much in the right order now.
 
Last edited:
A few more remarks with regards to PrivateSend mixing :

I'm not sure if its due to the different versions on Testnet or if its a complication from using PrivateSend multi-session, but so far most of my wallets are showing "pending" amounts in the overview section after having mixed to 100%.
These "pending" amounts wont clear, because certain PrivateSend Denominate transactions are not getting confirmed. So besides a few conflicted transactions, there are also unconfirmed transactions that are causing problems.

7rzVvBv.jpg


The pending amount on my TestDash 2 wallet self-cleared somehow, but some of my other wallets (i have 6 in total) did not self-clear and have the pending amount still visible in the overview.
Using "recover transactions 1" (zapwallettxes=1) gets these unconfirmed transactions re-added with a new date to mempool, but they are not getting confirmed and seem to actually mismatch with the number of transactions currently in mempool
(for example i have 7 unconfirmed transactions, but mempool only shows 4 current transactions). Same problem with using "recover transactions 2" (zapwallettxes=2), they get re-added to mempool but not confirmed.

Update 1 : after 30 minutes some of my unconfirmed transactions that i re-added through "recover transactions 2" are now getting confirmed and the "pending" amount disappears in overview.
I wonder if we could implement some kind of one-time check after a wallet hits 100% completion, to re-add any unconfirmed transaction to mempool automatically ?

Update 2 : example of a (for now) still unconfirmed transaction that was re-added to mempool 1 hour ago
Transaction ID: 0a3617791873f64febcd81bc437c44ed2933166d3f9905d4f37641f52c842805

Other observations :

Keys get renewed during mixing when below 100 + automatic backup : working
Mixing finishes and stops at 100% : working
Mixing rounds can be set higher then 8 : working
Multi-session mixing per block : working (although the advanced privatesend interface does get a bit crowded on overview with this option activated, because it shows the privatesend status messages of 4 mixing sessions. Personally i dont consider this a problem, they can always disable advanced privatesend interface)
Mixing transactions confirm : partially working (got a few conflicted transactions and also some unconfirmed transactions during multi-session mixing)
Memory Pool Usage : differs in kb per wallet (some match, some dont)
When wallets get stuck in sync, it normally helps to close and restart them.
 
Last edited:
InstantSend Autolock

I'm trying to test InstantSend lock on small normal transactions, using the sendmany command in debug console. So far i'm not seeing an instant lock indication.

Sending a small normal transaction (0.1 Dash) through the GUI (Send tab) also does not provide a lock indication in the transaction. It just confirms through Proof of Work in the normal way.
Are these elements (https://github.com/dashpay/dash/pull/2433) not active yet in v0.13 ?

With regards to the picture of the lock that is used in above gitpull, maybe we could change it from a key to a lock figure ?

6kkCLzs.jpg


ozyp5wg.jpg


(this is just an example to indicate what i mean with a lock figure, it will obviously need the same white background and green color as used with the key figure)

InstandSend

Creating a normal InstantSend transaction also fails

Status: 0/unconfirmed, in memory pool (InstantSend verification in progress - 3 of 40 signatures)
Status: 0/unconfirmed, in memory pool (InstantSend verification failed)

Number of masternodes on network :

Djb6l2u.jpg


PrivateSend

Sending a small privatesend transaction (0.1 Dash) causes a "not enough denominated funds" warning and sending a small privatesend transaction (0.2 Dash) causes a
"a fee higher then 0.100000000 tDash is considered an absurdly high fee" warning

Update : when clicking "subcontract fee from amount" these problems dont occur, so it has something to do with how PrivateSend implements the fees.

Missing option during mixing

I seem to be missing an option during the start of mixing that enables you to mix "safely" as in that
during mixing sessions the funds can not be exploited .. they are protected somehow.
I dont see that option anymore.

Abandon Transaction

This option both in debug console and while right clicking on a transaction does not seem to work on newly created unconfirmed transactions.

In debug console you get : Transaction not eligible for abandonment (code -5)
While rightclicking on a transaction the "abandon transaction" option more feels like an empty click, like that option is a filler for now.

Mempool

Inconsistent current number of transactions in mempool across wallets, while they are all in total sync (all of them show correct number of masternodes).
They differ with each other with regards to current number of transactions in mempool.

Link : https://imgur.com/0RLW3VC
 
Last edited:
v0.13.0.0-rc4 is ready for testnet: https://github.com/dashpay/dash/releases/tag/v0.13.0.0-rc4

Please update your nodes. Testnet is getting better compared to the last days and syncing should be successful in most cases, as long as you have enough good (v13) peers.
This release includes a new "DIP3 Masternodes" tab that shows all registered MNs. It also fixes an issue on Ubuntu where users were unable to do any keyboard inputs.
 
codablock said:
v0.13.0.0-rc4 is ready for testnet: https://github.com/dashpay/dash/releases/tag/v0.13.0.0-rc4

Please update your nodes. Testnet is getting better compared to the last days and syncing should be successful in most cases, as long as you have enough good (v13) peers.
This release includes a new "DIP3 Masternodes" tab that shows all registered MNs. It also fixes an issue on Ubuntu where users were unable to do any keyboard inputs.
Click to expand...

How many PS compatible masternodes are required again before InstantSend & Autolock can get activated ? Both are not working at the moment....
 
Last edited:
This post is a quick guide to help you get setup for testing this release.
It assumes you already have DASH 12.3.3 installed on your system and this installation purposely avoids touching that install and your user data. This post is Windows centric.
Never run a test build (RC) on mainnet. Don't trust it with your mainnet wallet and real DASH !
Click to expand...
Always verify the signatures and authenticity of the DASH executables you download from dash.org, we skip this step for testnet/RC builds, don't skip it when installing the final version
Click to expand...


Just in case backup your mainnet wallet.dat and masternodes.conf files !!!

Create a new directory somewhere on your computer. I will create it on my Desktop. Call it Dash-test
You now have a directory with a path similar to this, note that User will be your username C:\Users\User\Desktop\Dash-test

In the Dash-test folder create a new folder and call it data double click that and in the data folder create a New Text document and edit it and add the following line
Code: 
testnet=1
Save the file and now rename it to dash.conf

Go back one directory to the Dash-test folder and load this page https://github.com/dashpay/dash/releases/
Find the latest version of 64 bit windows ZIP file, NOT the installer! Remember, you do not want to overwrite your regular 12.3.3 Dash! Example for RC4 is dashcore-0.13.0.0-rc4-win64.zip
Download this zip and extract the contents into the Dash-test folder.

You should now have two folders in you Dash-Test folder, dashcore-0.13.0 and data.

Double click dashcore-0.13.0 and double click bin. Create a short cut to dash-qt.exe. Cut the shortcut and go back (up) two folders to Dash-test and paste it there. So the shortcut is now in the same place as the two dash folders, one from the zip and one that you created.

Edit the shortcut. You only have to change the Target. Make the target look like below, you will have to change User for your username when setting the -datadir.
Code: 
C:\Users\User\Desktop\Dash-test\dashcore-0.13.0\bin\dash-qt.exe -debug=1 -testnet=1 -datadir=C:\Users\User\Desktop\Dash-test\data
The important things here are the location of -datadir and -testnet=1 flag. We want to make sure this version of Dash stays well away from your mainnet Dash !
Click Apply and OK. If your username has spaces in it, try putting the Dash-test on C:\ otherwise you need to put " around -datadir flag.

upload_2018-11-17_20-6-20.png


At this point if Windows allows you to save the shortcut it means it has no errors and you can double click it to start syncing and testing. Check that it is writing data to the data folder. You can ask in the #testnet channel on discord for some free tDASH.

Updating to latest RC

Shutdown the test wallet. Download the latest zip from the site above, extract the contents to the Dash-test folder, click Yes to overwrite/replace existing files. Launch the wallet using the Shortcut you created and note the version of the startup splash screen.


Cheers !

-X
 
Additional on the above post from xkcd :

adding -listen=0 in the shortcut (at target) lets you start multiple windows wallets. Each will need to have its own specific datadirectory and own specific folder to start the dash-qt,exe from.
adding windowtitle=set_your_own_title in your dash.conf gives your wallet a specific name, so you can differentiate between multiple windows wallets.

Since all faucets are currently either dry or not working, you can also provide a receiving test address in here and we can transfer some tDash to you.
 
Last edited:
strophy said:
Hi @qwizzie - thanks for your language improvement suggestions, I have submitted these for review to our maintainer for Dutch.
Click to expand...

Dutch translation looks good now, except for two existing issues :

1

Peers tab inside "Gereedschapsscherm" still contains a $ sign

DoN2vvZ.jpg


2

Click buttons description

-zapwallettxes=1: Herstelde transacties van de blocks(behoud metadata;bv.accounteigenaar)
fix : -zapwallettxes=1: Herstel transacties van de blocks (behoud metadata;bv.accounteigenaar)

(it needs a space between "blocks" and "(behoud)"

-zapwallettxes=2: Herstel transacties vanuit de blocks (laat metadata vervallen)
fix : -zapwallettxes=2: Herstel transacties van de blocks (laat metadata vervallen)

(this one is for consistency)
 
Last edited:
Ugh, I was using the wrong version after all, OK, hope to get this running soon :D

When I test sentinel I get 1 error, and I installed it by following the instructions in the readme file. Thus I am worried I got main-net's version of sentinel instead of testnet's? This is my error, which I don't understand:

JSONRPCException: -342: non-JSON HTTP response with '401 Unauthorized' from server

venv/local/lib/python2.7/site-packages/bitcoinrpc/authproxy.py:187: JSONRPCException
===================== 1 failed, 22 passed in 0.60 seconds ======================


Went here: https://github.com/dashpay/sentinel/tree/develop

Followed directions, and downloaded like so:
git clone https://github.com/dashpay/sentinel.git && cd sentinel

I think that's a mainnet download??
 
Last edited:
Also, could someone send me some coins to mix? yebcSn2s3cdw75BQgiVV76itL1fAk5T6rW I'd like to fund a masternode
 
TanteStefana said:
Ugh, I was using the wrong version after all, OK, hope to get this running soon :D

When I test sentinel I get 1 error, and I installed it by following the instructions in the readme file. Thus I am worried I got main-net's version of sentinel instead of testnet's? This is my error, which I don't understand:

JSONRPCException: -342: non-JSON HTTP response with '401 Unauthorized' from server

venv/local/lib/python2.7/site-packages/bitcoinrpc/authproxy.py:187: JSONRPCException
===================== 1 failed, 22 passed in 0.60 seconds ======================


Went here: https://github.com/dashpay/sentinel/tree/develop

Followed directions, and downloaded like so:
git clone https://github.com/dashpay/sentinel.git && cd sentinel

I think that's a mainnet download??
Click to expand...
Yes, it is. Below are the correct instructions.
Code: 
git clone -b develop https://github.com/dashpay/sentinel
cd sentinel
# Comment out or delete the mainnnet line and remove the # from the testnet line.
nano sentinel.conf
virtualenv ./venv
venv/bin/pip install -r requirements.txt
venv/bin/py.test test
venv/bin/python bin/sentinel.py
 
You must log in or register to reply here.
Back
Top