V12.1 Testnet Launch Thread

Status
Not open for further replies.
On my windows 10 64 bit, my instance of dash-qt is not accepting my masternode setting that worked well under previous version. So it does not start.

Testnet dash-qt does not start at all.

EDIT: Thanks for advice. Now testnet works.
 
Last edited:
On the Ubuntu 15 side of life... Checks barely visible

JTeco5G.png


And...

8cVQ77F.png
 
Ha! Over a year without setting up a node thanks to Node40, haven't lost my touch...

Code: 

{
  "overall": "Successfully started 4 masternodes, failed to start 0, total 4",
  "detail": {
    "status": {
      "alias": "MN1",
      "result": "successful"
    },
    "status": {
      "alias": "MN2",
      "result": "successful"
    },
    "status": {
      "alias": "MN3",
      "result": "successful"
    },
    "status": {
      "alias": "MN4",
      "result": "successful"
    }
  }
}

The Masternode tab is really really neat!
 
eduffield said:
Masternode Hardware Wallet support

This highly anticipated feature allows masternode operators to start and stop their masternode from the Trezor hardware wallet. This allows us a great deal more security for our masternode operators to secure their highly valuable collateral.
Click to expand...

great news! Makes me even happier that my Trezor just got shipped :) Can't wait to test it
 
As mentioned before by others i can confirm that my Windows 10, 64-bit wallet stays a long long long time in "synchronising budgets (75%)" stage, sometimes showing "syncing network" before going to "synchronising budgets (75%)" again.

Explorers:

- https://test.explorer.dash.org - by flare --> working okay
- http://test.explorer.dashninja.pl - by elbereth --> working okay
- http://test.insight.masternode.io:3001 - by coingun ---> not working
- http://test.insight.dash.siampm.com - by thelazier --> working okay (it first had a "cannot connect to Insight server'' but its fine now)
update : unfortunetely it still throws some errors :

Can't connect to dashd to get live updates from the p2p network. (Tried connecting to dashd at {{host}}:{{port}} and failed.)
Can't connect to insight server. Attempting to reconnect...

Faucets :

- http://test.faucet.masternode.io - by coingun --> not much in that faucet i think, got some 750 tDash
- https://test.faucet.dash.org - by flare --> working, provides 1000 tDash
- http://test.faucet.dashninja.pl - by elbereth --> working, provided a cool 1271 tDash :)

Last block is 10458 from 14 minutes ago, we could use some more mining power.
edit : got a stuck explorer, fixed it by going into private mode.
 
Last edited:
It's 0.12.1-only test and all this banned peers on Peers tab are <0.12.1 version?

GJXlL4r.png


And tDASH address looks not compatible with previous version, same privkey on different wallets:
https://test.explorer.dash.org/address/yKwQEKDkG7XuqCeM7HQhUYz3rrrScKD8SE
https://test.explorer.dash.org/address/yjH1DRX2yHznednS8hk1xgFqVN7PM79UrT
23:11:01

validateaddress yKwQEKDkG7XuqCeM7HQhUYz3rrrScKD8SE


23:11:01

{
"isvalid": false
}


23:11:10

validateaddress yjH1DRX2yHznednS8hk1xgFqVN7PM79UrT


23:11:10

{
"isvalid": true,
"address": "yjH1DRX2yHznednS8hk1xgFqVN7PM79UrT",
"scriptPubKey": "76a914fbd4a9ade22c174af44b5c440d13ec130d18f5ad88ac",
"ismine": true,
"iswatchonly": false,
"isscript": false,
"pubkey": "0375194e15a13b9e2acd07865b0e3ca5ed118dd9879befa4d167f0a64ea71c169b",
"iscompressed": true,
"account": ""
}
23:10:29

validateaddress yKwQEKDkG7XuqCeM7HQhUYz3rrrScKD8SE


23:10:29

{
"isvalid" : true,
"address" : "yKwQEKDkG7XuqCeM7HQhUYz3rrrScKD8SE",
"ismine" : true,
"iswatchonly" : false,
"isscript" : false,
"pubkey" : "0375194e15a13b9e2acd07865b0e3ca5ed118dd9879befa4d167f0a64ea71c169b",
"iscompressed" : true,
"account" : ""
}


23:10:39

validateaddress yjH1DRX2yHznednS8hk1xgFqVN7PM79UrT


23:10:39

{
"isvalid" : false
}
 
Last edited:
After creating a new wallet the first automatically created receiving address got incomplete / incorrect.
The second receiving address i created manually was normal.

8aOTbso.jpg
 
@all
75% sync is a known issue, ignore it for now
Previous addresses are invalid now, testnet was reset with new magic number so that every testnet address now starts with 'y' and never with 'x' to avoid accidents ;)
Pls report other issues at https://github.com/dashpay/dash/issues also so that we could easily 1) keep track of them 2) see how many users (OSes) are affected and how.
Feature requests are ok there too but bugs first pls :)

Thank you!
 
I had proposed a DGbB tab, like the MN tab, but in a brief exchange with Evan over at the #Dev channel he mentioned he didn't want to see this implemented in the QT right now.

I think it would be cool to have a simple ballot tracking tab, but there seems to be magic happening in the background, so best wait to see whats in store...

.
 
yidakee said:
I had proposed a DGbB tab, like the MN tab, but in a brief exchange with Evan over at the #Dev channel he mentioned he didn't want to see this implemented in the QT right now.

I think it would be cool to have a simple ballot tracking tab, but there seems to be magic happening in the background, so best wait to see whats in store...

.
Click to expand...
Yep, i understand things are forming, so better wait and let the system mature first.
 
Hey guys, I apologize for this basic question again, but I can't seem to get my testnet masternode running. It's a hot wallet. Where do I put the info in dash.conf? Only in the main .dash folder? Do I leave the testnet3 folder default? Thanks :)
 
Also, I tried to reset options, and when I restart the wallet the options don't show up (reset to default) I get an error that says "Active command line options that override above options -listen=1" So I presume I have to set that to 0. Since I have NO idea what "listen=1" means, and I just included it since time began because we were told to, LOL, could anyone explain what it means? Thanks :)

One more thing. With the Masternode tab, could you make it so that a Masternode owner just has to input the information in the wallet, like you do at DashWhale.org and the information is automatically added to the masternode.conf file? This would really be an awesome addition :)
 
Last edited:
I'm stuck syncing additional data. (Sorry, just read it's a known issue) Is this because I'm using my old wallet (to keep the coins?) Should I start fresh? - I've started a fresh wallet BTW, my masternode wallet is a new wallet, so my issues there shouldn't be because of that :)
 
Status
Not open for further replies.
Back
Top