Thanks Garret.
I propose a temporary solution for this testing phase. To have the community support this before the Treasury is officially confirmed, or, before there is an official technical governance framework, I think it would be premature at this time to involve the community.
However, I personally wouldn’t want to miss an opportunity for the Treasury simply because things aren’t ready yet. Here is my interim solution if the community decides to support it when you create the vote.
- If Spyce.5 is voted to be a validator, then I (DeepSea) will fund a second validator node to be designated as a Community (Test) and potential future community validator node should the community vote to support it.
- I would fund this and also seek another technical community member to have access to this validator node.
- This is in no way a direct reflection of community sentiment as we have not discussed in detail nor approved in any way to host a validator node. I would personally do this with Spyce.5, another community member, on our own while we work on a technical framework and official vote with the community.
- After a testing phase and more in detail technical governance discussions with the community, if the community rejects to host this validator node our node can be given to another community member or project.
Just to note on my personal background, I have hosted nodes in the past and have a basic technical understanding. Of course everyone knows I seek full transparency in all regards and have DOX’ed myself. If I end up getting the program lead position I will also be KYC’ed. Saying all that, I think it’s also good to have the support of a trusted and technically capable project like Spyce.5.
Again, I love this initiative because it pushes the community to think about new ventures and how to work together.