Hey @giantfrog, I don’t believe we have met before. I appreciate the response.
Oh, I’m aligned. So much so, I wrote the original ADR that the v1 integration is based on 
Pre-proposals are where the conversations happen for proposals… that is their intended design. You will find that with all the pre-proposal/proposal pairings, the real conversation for the proposal is in the first version (pre-proposal) and not the final version. It is a new perspective to try and divorce their relevancy to each other.
The final proposal for LeanPOKT was fast tracked and put to a vote after only 5 days, instead of the standard minimum of 7 days, precisely because the pre-proposal was the context, who’s conversation expanded over many weeks. Therefore I’d prefer to use the whole community conversation for context.
Unfortunately, that was not clear at the time because the proposal’s value was not predicated on measurable metrics, but more abstract concepts of value. Concepts that were partly built on notions that this proposal is worth it’s ask because of the value it would produce in the ecosystem (which thus far it has been unused). This is why I have always advocated for measurable metrics with every proposal, including LeanPOKT, so there would be universal clarity 
It may be clear to you, but for myself, as a voter, outsider, and participant in the LeanPOKT proposal conversation, it is not clear. That is my point and why I provided past context.
As much I would like to take credit for transcribing, I must give it to Youtube 
Yeah, I agree that if Nodies is able to capture customers for non-protocol features, it can indirectly lead to more traffic to POKT as well. I get the strategy.
I totally get that. Nodies began running nodes in August/September with geo-meshing, which means the development of the private client began before that, and active development of LeanPOKT was still underway between PNI and @poktblade in July/August, so it all overlaps. That is my point… the timing is very messy and confusing, which I why I believe it is relevant to today’s conversation. I also believe this kind of scenario should be avoided moving forward.
I would really appreciate it if we call a spade a spade and not try to now frame Nodies market capture as being an act of benevolence for the health and security of the network. From my understanding the geo-mesh code was never given to PNI to vet (LeanPOKT on the other hand was shared), nor did PNI ask to keep the geo-mesh concept private (they always encourage public discussion regarding LeanPOKT), so these are not equivalent scenarios. It was a great business move, and it took POKTScan months to reverse engineer in an open-source fashion, so I’d prefer we leave it at that.
While I can respect that the narrative at Nodies is the private client was “hardly” an advantage, it’s not fair to those who didn’t have access to it and were putting resources into reverse engineering. It was objectively an advantage that generated 2x-4x more revenue per node, and that is my only point.
Indeed, I remember seeing that Nodies started using geo-mesh in February:
It’s great that everything started being open-source. Grateful for the contributions Nodies has had since 