If you follow the consensus rules, your node will be treated just like any node on the network. And we’d be happy to have you. The more the merrier.
This is disingenuous. You yourself told me the act of creating Grin++ was adversarial in its nature, and claimed that I was wrong to do so. This is just more virtue signaling.
It seems I wasn’t very clear, so let me expand. Whether you were being adversarial or not at the point of creation @david is subjective and completely beside the point.
I actually would have thought you of all people would get the point I was trying to make:
You created your own implementation with Grin++ and have since secured your own funding. You have quite a lot of autonomy. You have your own governance for how you accept contributions to your codebase, and manage your release schedule. You can focus and prioritise matters that you consider most important to your users. And Grin++ nodes are being treated just like any other node on the network. As long as consensus rules are followed, why would that not be the case?
You’re clearly talented, and very passionate about Grin. Of course I would have wanted to see you improve the Rust implementation. But who am I to tell you what you should be doing? (: You wanted to take Grin in directions that you were not able to build consensus for in the months leading up to mainnet launch. So I get your logic for choosing to go at it on your own, allowing you to iterate, learn, and explore much faster. Grin++ seems to be doing well as a result, it is an alternative standalone implementation that allows for different approaches to be tried, and something Grin (Rust) can draw learnings from. If something bad would happen to the Rust project, there’s a chance the C++ project would be unaffected, and vice versa.
So now that Grin++ exists, having her around adds to the network, and creates resilience and reduces centralization. The whole network is greater than the sum of its two individual implementations. And so similarly to this, if there’s anyone else that thinks the approach we’re taking with the Rust implementation is so wrong that they cannot stand by watching this happen, or simply that they want to experiment with Grin in ways that the Rust implementation cannot support for whatever reason, they are welcome to build out their own alternative. Regardless of whether that’s a fork or a separate implementation (Grin Go anyone?). I would prefer you contributing to Grin (Rust) as we could use the help, but I’d rather you do your own thing than leave altogether.
Peace out