Welcome!

Decided to change my votes from ABSTAIN to NO.

Yes. DCG has vastly improved in transparency and communication. Development output and quality is up (yes, despite the halt). Sam and the rest of the team are doing great work. I'm not going to focus on the market and the regulators, let's ship this shit and get evo out there, build on it and grow.

Such is the confidence, this was written for the future date, "November 31st, 2023".

But yeah, no remorse for the first - but not the last - 16+ hour chain halt. In any other organization you'd of been fired already, fat chance of that happening here though.

1. Any news regarding the SEC yet?

2. Regarding the SEC or the PoS sidechain, is there any statement you would like to make now that you might later rely on in defense?

3. In hindsight, do you continue to standby your decision to choose a PoS sidechain?

4. If dash was a _protocol_ there would be more than one independent masternode daemon. Will you initiate development to convert your _product_ to a _protocol_?

You do, of course, have the right to remain silent.

Sorry for the oversight writing November and not May, fixed.

As for the chain halt, it was and still is a terrible situation, we have explained what the issue was. If you want to hear it here it is: DCG leadership and staff are very sorry that such an event happened. We continuously strive for high quality code and testing. This event scenario was not caught in our testing and we will improve our testing framework in the future. However I can not say that such an event will ever take place again because such in the nature of development. No much more that a NASA or SpaceX lead engineer or manager could say that no rocket will ever explode again.

Here are the answers to your questions:

1. Question: Any news regarding the SEC yet?

We have no extra information compared to what has been made public.

2. Question: Regarding the SEC or the PoS sidechain, is there any statement you would like to make now that you might later rely on in defense?

First, a side note. The Platform chain has many elements of PoS, if might very well be considered PoS, but since different people have different understanding of what PoS is and there's no concrete definition that I am aware of, we need to be careful about saying that Platform is PoS right now.
It is important to understand that demand is created on the Platform chain, however supply is solely created by Masternodes/Miners on the Core chain, I do not know of any PoS blockchain that does not issue it's supply. No native coins/tokens are created on the Platform chain, instead it uses a form of wrapped Dash issued on the core Chain.

3. Question: In hindsight, do you continue to standby your decision to choose a PoS sidechain?

I stand by the decision to go with a heavily modified Tendermint. It was however, originally, not my preferred approach. The decision to use a modified Tendermint was decided by the Platform team and the previous CTO. I had previously advocated for a slightly more custom approach that I believe would have been more scalable. It's hard to know if my previous solution or this solution would have been better. In the end we have a very good system that has shown to work well. It will offer more than a good enough user experience through the first few million users.

4. If dash was a _protocol_ there would be more than one independent masternode daemon. Will you initiate development to convert your _product_ to a _protocol_?

You are mistaken if you think this isn't the case. Dash Core has a protocol, dash platform as well. There is a protocol number that defines consensus. Other versions of Dash Core (maybe written in other languages) could connect to the network and function as well if they run the same protocol.

Thank you for the reply.

Which alternative daemon(s) not developed or maintained by DCG that I can run for a masternode? If the answer is none then I say you have a product, it is a protocol by name only..I feel this distinction is vital and, ultimately, this was a single point of failure of the masternode network.

Going forward, I feel DCG should cease publishing all server side code, including binaries, as DCG holds too much influence. In such circumstance, how could alternatives truly flourish or be considered equal? I would like to hear alternative ideas to this.

Don't get me wrong, Of course, I welcome more thorough testing but I am also hungry for changes that could dilutes influence from a few heavyweights here.

dashd-go repo is held by DCG but manaintained by Alex for the Maya integration. I think

Just had a quick glance at the github which says, by design, there is no wallet functionality. I'm not sure how useful this implementation is for running masternodes. And I'm also not clear of DCG's role / influence with this.

But do please keep us informed. I would love to run an independent implementation so long as it didn't interfere with upgrades and payouts.

Dickhead.

Would you like to reset this animosity?