V12.1 Testnet Launch Thread

AndyDark

Well-known Member
Sep 10, 2014
353
705
163
Umh, so i lost my bet, typical:)
:(

well we've been testing solid for last 5 days so technically it's on testnet! you just need to get your hands dirty to join in. sorry about that. it will be easier soon with the docker process. there's still some issues to fix so the focus is on that. it's coming along good though, things are coming together :)
 

AjM

Well-known Member
Foundation Member
Jun 23, 2014
1,335
571
283
Finland
:(

well we've been testing solid for last 5 days so technically it's on testnet! you just need to get your hands dirty to join in. sorry about that. it will be easier soon with the docker process. there's still some issues to fix so the focus is on that. it's coming along good though, things are coming together :)
No problem, i mean typical for me when i bet for something.;)
 

halso

Active Member
Apr 27, 2016
440
236
113
Sydney, Australia
:(

well we've been testing solid for last 5 days so technically it's on testnet! you just need to get your hands dirty to join in. sorry about that. it will be easier soon with the docker process. there's still some issues to fix so the focus is on that. it's coming along good though, things are coming together :)
can you explain what docker is? Are the remaining issues with sentinel? if so, can we delay sentinel until 12.2, and release 12.1 now?
 

t0dd

Active Member
Mar 21, 2016
151
132
103
keybase.io
Dash Address
XyxQq4qgp9B53QWQgSqSxJb4xddhzk5Zhh

AndyDark

Well-known Member
Sep 10, 2014
353
705
163
can you explain what docker is? Are the remaining issues with sentinel? if so, can we delay sentinel until 12.2, and release 12.1 now?
Hey @halso

Docker is an optional setup process that will make setting up 12.1 Masternodes easier and more automated for users who want that https://www.docker.com/customers. Creation of the manual / docker setup process for 12.1 masternodes is being lead by MooCowMoo who made the DashMan setup process.

Re: Sentinel - a few people have asked about Sentinel and why 12.1 has been late.

Sentinel is an autonomous agent running on 12.1 masternodes that automates governance tasks designed originally by Evan and taken forward and maintained by Nathan Marley: https://github.com/nmarley/sentinel

Few reasons for the delay:

1. Feature scope - Sentinel is essentially a component of Evolution code that will grow into DashDrive in a future release. we had to balance between wanting to develop advanced uses of Sentinel with the need to release 12.1 early. Often the 12.1 release lost in that equation until recently we feature locked and decided to run with the current because of the delay to 12.1. It means 12.1 isn't really taking full advantage of all the features, Sentinel is just replacing the existing governance system, and automating tasks like budget finalization and Dash Core (as it's called now) is agnostic to governance objects making it easier to build out the features we want in the future.
2. Because Sentinel is a new component that runs on a Masternode, this release is more than just updating the core client as usual and I don't think we factored in all the various work outside of that (like deployment, maintenance, op sec) to the original time estimates and which is a lot of the work over the last week - Sentinel needs to be easy to deploy and setup for MNOs.
3. Testing - don't think we factored in enough time, again testing with 2 components in the mix is more involved than the usual core client testing
4. Teams - this is the first time the core team and evo backend-team really got together and make their code work together (because a lot of Evo code isn't just in the core client). Now we are pretty efficient at working together and that is good for the future too.

So basically Sentinel is new software for future use that has added overheads in different angles to get the first version working and different teams coming together. The good news is we've passed those hurdles and can now do the test phase through to mainnet release. There's also a huge amount of improvements in Core that have built up too so it should be a good milestone release all round to bring core up to date and lay the foundations we need for the Evolution alpha.

In terms of where we are right now this is the notes from yesterdays meeting which explains it faster probably:

upload_2016-9-21_13-0-55.png


Cheers,
Andy
 

demo

Well-known Member
Apr 23, 2016
3,114
263
153
Dash Address
XnpT2YQaYpyh7F9twM6EtDMn1TCDCEEgNX
Hey @halso

Docker is an optional setup process that will make setting up 12.1 Masternodes easier and more automated for users who want that https://www.docker.com/customers. Creation of the manual / docker setup process for 12.1 masternodes is being lead by MooCowMoo who made the DashMan setup process.

Re: Sentinel - a few people have asked about Sentinel and why 12.1 has been late.

Sentinel is an autonomous agent running on 12.1 masternodes that automates governance tasks designed originally by Evan and taken forward and maintained by Nathan Marley: https://github.com/nmarley/sentinel

Few reasons for the delay:

1. Feature scope - Sentinel is essentially a component of Evolution code that will grow into DashDrive in a future release. we had to balance between wanting to develop advanced uses of Sentinel with the need to release 12.1 early. Often the 12.1 release lost in that equation until recently we feature locked and decided to run with the current because of the delay to 12.1. It means 12.1 isn't really taking full advantage of all the features, Sentinel is just replacing the existing governance system, and automating tasks like budget finalization and Dash Core (as it's called now) is agnostic to governance objects making it easier to build out the features we want in the future.
2. Because Sentinel is a new component that runs on a Masternode, this release is more than just updating the core client as usual and I don't think we factored in all the various work outside of that (like deployment, maintenance, op sec) to the original time estimates and which is a lot of the work over the last week - Sentinel needs to be easy to deploy and setup for MNOs.
3. Testing - don't think we factored in enough time, again testing with 2 components in the mix is more involved than the usual core client testing
4. Teams - this is the first time the core team and evo backend-team really got together and make their code work together (because a lot of Evo code isn't just in the core client). Now we are pretty efficient at working together and that is good for the future too.

So basically Sentinel is new software for future use that has added overheads in different angles to get the first version working and different teams coming together. The good news is we've passed those hurdles and can now do the test phase through to mainnet release. There's also a huge amount of improvements in Core that have built up too so it should be a good milestone release all round to bring core up to date and lay the foundations we need for the Evolution alpha.

In terms of where we are right now this is the notes from yesterdays meeting which explains it faster probably:

View attachment 2681


Cheers,
Andy

So is it possible to hack the sentinel python script to start voting using numbers?

Where the votes are preserved, in the blockchain or in a simple database?