Thank you very much for starting this valuable discussion.
As a builder leveraging Pyth on Cronos:
I agree that one of the responsibilities of the Pyth DAO is to make the Pyth protocol sustainable economically.
However, I would like to challenge the logic of proposing an uneven playing field across dapps / chains.
First, as Pyth uses a “pull” model, apps / chains are paying for their own infrastructure costs when it comes to retrieving prices and posting them on their respective chain. It’s not clear to me that some chains cost more than others to the DAO.
Second, the “market competition” criteria basically means, if you are a chain who decided to go with Pyth as a preferred / recommended oracle protocol, your loyalty and commitment now become a liability. You are now incentivized to seek other oracle integrations in order to avoid future penalties from the DAO.
There is a risk that this “first step” of discriminated pricing becomes the de facto end state, because it is the low hanging fruit.
Wouldn’t it make more sense to introduce a standard pricing for all dapps / all chains uniformly, potentially at a lower level in order to test market reaction, and then increase the pricing if needed ?
A market test focused on chains that have not encouraged alternative oracle options may not generate much insights into how the users of other chains will react.