Pre-Proposal - POKTscan Geo-Mesh Reimbursement

[RawthiL (Ramiro | POKTscan)]

Just want to clarify some points. I will leave out all the discussion over pricing and over POKTscan (that is not part of this proposal as stated before).

Its OK to disagree with this proposal, but spreading false arguments is not acceptable.

@bulutcambazi

The network didn’t become more reliable, more cost-efficient, or improved its QoS as a whole because of Geo-Mesh.

In fact it did become more reliable, cost-efficient and inprobed QoS.

• It is more reliable because the probability of entering a session with a local node went up. This means that apps get less failures because of timeouts.
• It is more cost efficient as you dont need to pay for Pocket Nodes deployments in each region.
• It improved QoS, this is a fact and it can be seen in the original post of GeoMesh.

@bulutcambazi

There were nodes in all high-value regions in the first place, and the CherryPicker chooses the fastest nodes regardless of Geo-Mesh.

This statement is misleading. CP chooses among the nodes in its session. Session nodes are chosen randomly. Before GeoMesh the chances of an App being paired with 24 foreign nodes was very high for many regions.

@bulutcambazi

In fact, one could argue that a better proposal might be limiting nodes to a region, therefore helping reduce the cost and improve QoS (if a particular region is all you’ve got for a particular node, you do a much better job for that node in that region).

This is already a feature for V1. But we wont get geozones until then.
And even then GeoMesh could be used to enable the same node to be staked in many regions.