..
as for your assumptions that "the network" you envision will self mitigate its own method. no code is needed meaning you ned to write it. you ned to come up with the methodology where it avoids certain peers from grouping up into clusters good luck funding a method to identify that certain nodes are not just 1 guy with 1000 nodes or where your node only has 100 connections and most of them are from a common peer cluster that gossiped(seeded) a list of known 100 nodes thus form their own cluster/echo chamber of only hearing each other first
(its more about the peer IP connection/identity decider. rather then the latter block reward split mechanism thats the problem when it comes to trying to mitigate pooling/clustering)
as for your assumptions that "the network" you envision will self mitigate its own method. no code is needed meaning you ned to write it. you ned to come up with the methodology where it avoids certain peers from grouping up into clusters good luck funding a method to identify that certain nodes are not just 1 guy with 1000 nodes or where your node only has 100 connections and most of them are from a common peer cluster that gossiped(seeded) a list of known 100 nodes thus form their own cluster/echo chamber of only hearing each other first
(its more about the peer IP connection/identity decider. rather then the latter block reward split mechanism thats the problem when it comes to trying to mitigate pooling/clustering)
I am currently in the midst of testing the reference client
The system is designed to provide no advantage to utilizing multiple nodes(slight disadvantage as more gas will be required to consolidate rewards). Additionally, peer information is contained network-wide within the network state to prevent a cluster/echo chamber of peers.
Local sims are looking good just need to start testing the waters for market demand to plan initial distribution.
I can message you when I start the topic if you are interested