I definitely agree with her on the conservative approach with multiple testing before any implementation, by verifying the real revenue generated by #ICS and slowly testing the results of the alloctor/scheduler.
Most of the NWV opposition seems focused on the Treasury/Council system, it's an understandable concern, being a big change to current model. I appreciate that @adriana_kalpa also proposes in her opposition an alternative.
Pheraps this mean that without that specific implementation, Atom 2.0 would pass for sure.
And eventually Treasury/Council could be added and voted later after that the Allocation module and the Scheduler are ready and tested.
This could be the meeting point from the two parties, and also is worth to note that can be considered even if Atom 2.0 will pass, since it is a signaling proposal and will require further proposals for the specific upcoming implementations.
I'll end with sharing the best counter thread in support of $ATOM 2.0 that I read recently, that address some of the concerns shared by NWV votes:
#Cosmos Hub and community did a lot for this ecosystem. I would like to see the main builders sharing that value back to the Hub, now that they can.
Asking an high amount of funds to launch something that is already coming by a free contribution, doesn't seems wise.
@ChorusOne (Quicksilver team) that is also a long term contributors of #Cosmos didn't asked for any funds from the community pool and yet is considering to apply for #Interchain Security and share value back with $ATOM