The last couple of days there’s been some action in this thread with respect to 55651 - it’s just a bit disappointing it took as long as it did to have a discussion about DFINITY’s concerns and to have those concerns voiced at least a month after the proposal originally passed the NNS.
I think there’s definitely a solution in there that isn’t outrageously difficult or over-complicated. What would help is to understand all of the different ideas that DFINITY has brainstormed for implementation as well as the various attack vectors they have considered. Also understanding their current process for how the DFINITY neuron is controlled in order to push out hotfixes would help in designing such a feature. But until recently that more detailed context hasn’t been surfaced.
I’d be happy to collaborate in a forum type back-and-forth environment with DFINITY to help coalesce around a solution, as I’m sure the rest of the community would be happy to participate in the technical implementation design and details - I’d just want to know that DFINITY is actively thinking about actually how a proposal would be implemented, and putting a good faith effort to think through solutions for how such a feature could be implemented in a secure fashion, and to communicate those brainstormed ideas with the community so that we can help iterate on and maybe even take on implementation tasks if we have the bandwidth and technical-depth. But without communication, from the outside (not DFINITY internal) sometimes it just feels like we’re all standing around waiting for an update.
@bjoernek as for proposal 38985, which also passed with >90% of the vote back in January - have there been any concerns with or plans/ideas for implementing that proposal?