12.1 Testnet Testing Phase Two Ignition

Status
Not open for further replies.

camosoul

Grizzled Member
Sep 19, 2014
2,266
1,130
1,183
Has there been any documentation made on the 12.1 upgrade/Sentinel installation process for people who have not read, and wouldn't understand, this thread?

We know full well, just like every other time, there's going to be a majority of people who have no idea what's going, never even heard of Sentinel, didn't know that there was a testnet, or that any upgrade was happening, etc...

And, of course, the discovery and frantic updates that come from problems found that could not be detected in the testnet environment...
 

qwizzie

Well-known Member
Aug 6, 2014
1,550
728
183
Has there been any documentation made on the 12.1 upgrade/Sentinel installation process for people who have not read, and wouldn't understand, this thread?

We know full well, just like every other time, there's going to be a majority of people who have no idea what's going, never even heard of Sentinel, didn't know that there was a testnet, or that any upgrade was happening, etc...

And, of course, the discovery and frantic updates that come from problems found that could not be detected in the testnet environment...
https://dashpay.atlassian.net/wiki/display/DOC/Masternode+Update

This is currently work in progress, but it should have clear instructions later on.
The recommended specs are interesting, i'm glad i did that server hardware upgrade.
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
In preparation for tomorrows event I made a quick test and started the new Windows wallet on mainnet to see if the blockchain syncs correctly. This worked.
Then I checked if my masternode.conf would work unchanged for 12.1. But after starting the wallet, I got this error:
"Error reading masternode configuration file: Invalid Port detected in masternode.conf ..... (must be 9999 for mainnet)"
Needless to say that I didn't change anything in my working masternode.conf from 12.0. It seems to reject port 9999.

Pinging @UdjinM6 @flare to check this.
Yep, confirmed - looking into it.
 

t0dd

Active Member
Mar 21, 2016
151
132
103
keybase.io
Dash Address
XyxQq4qgp9B53QWQgSqSxJb4xddhzk5Zhh
And mentioned in one of the slack channels...

Testing is complete for the Red Hat'ification of Dash that I have been working on for quite some time. If you are adventuresome, I have written a small pile of documentation, but if you just want to get going, here's an example of getting started with the simple wallet use case...

  1. Crank up a Fedora Linux 25 instance (they make live ISOs that are trivial to install)
  2. Login and open up a terminal... I'm assuming you gave yourself admin privileges in the install wizard...
  3. Type this...

Code:
cd /etc/yum.repos.d/
sudo curl -O  https://raw.githubusercontent.com/taw00/dashcore-rpm/master/dashcore-fedora.repo
cd -
sudo dnf install -y dashcore-client
If you wanna get super fancy, update the whole operating system and reboot..
Code:
sudo dnf upgrade -y
sudo reboot # to be all fresh and stuff
Then find the Dash icon in your menus click on it and done

But what's different about all this?

  1. If you install dashcore-server instead, it is all prepped to operate as a systemd managed service like a real daemon should be. Prepped for future hardening with SELinux and other fancy things...
  2. All your default logs are rotated by the operating system...
  3. Firewall rules and fail2ban settings are explained...
  4. Sentinel also logs to a sensible log-rotated log file and the only configuration needed is a crontab edit.
  5. dashd and Sentinel run as a system user dashcore instead of a normal user (if you want)
  6. As updates are published... you are alerted that an update is available and you can automatically trigger them at your convenience with a one-liner update and restart of the service
  7. Need to update the kernel and reboot (a common thing)? No problem, systemd shuts down the service and restarts it upon boot.
  8. Advanced admins can figure out how to spin up multiple systemd managed dashd instances pretty easily (I have an RFE in for Sentinel to make it easier to configure though)
  9. I even added OS menu icons and desktop stuff ... to include high-contrast icons to blend in nicely with the desktop experience and for those who have difficulty seeing

I'm sure I am forgetting something. Anyway... It's solid. It works. It's "right". It's added "polish".

You can find it all at https://github.com/taw00/dashcore-rpm -- Read the READMEs and then dive into the documentation directory.

Builds for Fedora 23, 24, 25, 26 and CentOS7, and Red Hat Enterprise Linux 7 -- i686 and x86_64

Happy Dashing -t
 
Last edited:

Tobson

New Member
Jan 11, 2018
2
1
1
40
Would it be possible to set up a private tDASH testnet? Maybe even separated from the internet.

I am looking into that topic for academic purposes but unfortunately even after hours of searching I couldn't find anything.
Help and Link would be very much appreciated :)

Thanks
 

Miner237

Well-known Member
Foundation Member
May 28, 2014
510
223
213
Would it be possible to set up a private tDASH testnet? Maybe even separated from the internet.

I am looking into that topic for academic purposes but unfortunately even after hours of searching I couldn't find anything.
Help and Link would be very much appreciated :)

Thanks
Sure yeah get a vpn setup and run your own testnet i side a private network. I doubt there is a guide its all aspects of blockchain on private network, so you need it ALL setup.
 
  • Like
Reactions: stan.distortion

Tobson

New Member
Jan 11, 2018
2
1
1
40
Sure yeah get a vpn setup and run your own testnet i side a private network. I doubt there is a guide its all aspects of blockchain on private network, so you need it ALL setup.
OK. Kind of excited here :) So here is the roadmap as it shows in my head:
1. Go to Github > dashpay > dash and compile miner and masternode. Seems straight forward
2. Setting up a vpn environment. Seems straight forward, perhaps I am looking into virtualiziation.
3. Get Miners and Masternodes to run
? How do I tell my miners and masternodes to span a new network with each other and not with mainnet or official testnet?
? Are there any configfiles or do I have to change that inside the code?
? I am pretty sure I need a new genesis block. Is the genesis block compiled into the wallets and masternodes?
? How to get a faucet to receive my initial testDASH for the Masternodes?
4. Compile Wallets
? How do I tell these wallets to work on my testnet?
5. Setting up a Block Explorer
? Where can I I find the sources. Are they even available open source?

Thanks everybody for helping me out with these questions. I just need a small boost at the beginning of my project. Hopefully in the future I can contribute to the dash project...and some of our students too:)
 
  • Like
Reactions: stan.distortion
Status
Not open for further replies.