Great thanks
V12.1 Testnet Launch Thread
- Thread starter eduffield
- Start date
- Status
Great thanks
Wow, that is fast, i have to try 2 rounds...
Edit: maybe later, there is/was only 4-6 compatible masternodes...
Last edited:
I think it could even be faster if my internet was not so damn dodgy where I'm at... old ADSL that changes IP every 6 hours and the router has more brain-damage than a monero troll.
All 3 wallets had unconfirmed tx, wallet 1 and 2 for about an hour ... dammit. -zapwallettxes and off they go again
Restarting the wallet now shows
Wallet 1 - 11%
Wallet 2 - 11%
Wallet 3 - 23%
This makes more sense. But Wallet 3 was showing 48% when I closed it, and only 1 unconfirmed tx.
.
So I'm trying to get started on testnet...I changed dash.conf to include "testnet=1" and the client loads just fine and says [testnet]. But then once qt loads, I get "No block source available 2 years and 17 weeks behind." Wasn't testnet just reset with a new genesis block? Why is it looking for something that's 2 years 17 weeks old?
Do I need to add some peers to my dash.conf file?
Do I need to add some peers to my dash.conf file?
Comodore
Active member
I waited some 30 seconds only and it was OK
M
MangledBlue
Guest
What Build are we on....??
Normal client wallet, no masternode, i use shortcut in win7, like this:
F:\Dash_testing\dash-qt.exe -datadir=F:\Dash_testing -testnet -listen=0 -windowtitle="Testwallet 1 - Win7x64"
and masternode and dash.conf both empty.
Today: v0.12.1.0-16671cd
testnet default port is 19999 but testnet allows to use any other port but 9999
mainnet allows only 9999
EDIT: that's an old one btw and it was there to provide an easy way to simulate many nodes without wasting too many resources (testnet nodes should require a lot less memory/bandwidth)
flare
Well-known member
Yes, testnet was reset, but we didn't create a new genesis block - it is still one mined at 2014-01-25 --> https://test.explorer.dash.org/bloc...75e2ec92894837288a481e5c005f6563d91623bf8bc2c
Normally the client should find peers by itself after some minutes, if you still have problems you can add the masternodes available: https://test.dashninja.pl/masternodes.html#mnlistdetail
Yep, strictly saying testnet wasn't reset but rather it was forked at block 2000
flare
Well-known member
If you feel adventurous: Here is a rough-cut Windows binary: https://dashpay.atlassian.net/build...fact/JOB1/electrum-dash.exe/electrum-dash.exeI would like to test the Trezor support, I've seen many people ask for that, but I can't figure out what version of Dash-Electrum to run, or where to get it (I can only find 2.4.1). Does anyone have a link to a binary or instructions? Thx
I am still in the process of creating proper packages
Ensure that you are connecting to electrum.drk.siampm.com, as Masternode/Trezor functionality needs a updated server
Instructions should be here --> https://github.com/dashpay/electrum-dash/blob/develop/docs/masternodes.md
@UdjinM6 @flare at the risk of being a total pain in the arse, I just thought that the suggestions I made here would be nice if it's not too hard One of the most confusing things for newbies is how to set the wallet up. This includes new Masternode owners, and I think it would make things easier for the user. Of course I understand if the usefulness isn't worth the effort, but I just wanted you to see the suggesting in case it's useful
One of the most confusing things for newbies is how to set the wallet up. This includes new Masternode owners, and I think it would make things easier for the user. Of course I understand if the usefulness isn't worth the effort, but I just wanted you to see the suggesting in case it's useful
@TanteStefana I doubt daemon can have or needs some console interaction - it's daemon after all. More than that, I'd like to note that it doesn't require rpcuser and rpcpassword anymore so non-mn users can start using daemon without any setup and for mn users it's as simple as adding 2 lines to a text file - "masternodeprivkey=blablabla" and "masternode=1". Not such a difficult task imo. Next, I think hot masternode setup should go away completely one day and the earlier the better, there should be no setup like that where nodes with $$ are online 24/7 imo. So I'd actually cut that out from our code rather than start wrapping things to make it nice and easy. As for gui part for masternode.conf and hotcold setup - I agree that's a field for improvement
- Status