Some feedback I have been gathering from council members: in general the idea is something that could be useful.

• for some councillors this seems like an overpriced submission: 12.5k/month - it might be necessary to review the cost of maintenance for this.
• Additionally, there are no actual specifics to the proposal besides the idea of maintaining GSRPC. In this sense:

1. does the team need to bring it up to current? What is involved? what are the elements to be included or to be taken care of? who is behind maintenance?
2. for maintenance, what are they planning? what does the roadmap look like? (resources/time)

• if you re still on metadata v9, teams (of the ones listed) wont actually use this, so bring it up to speed should involve this.

Although Polkascan Foundation is not (yet) on the Polkadot Council, we do have something to say about this for two distinct reasons: 1) We are on the Kusama Council, 2) As infrastructure service provider and maintainer of Python Libraries we have thoroughly thought about this type of Treasury Spending Proposal from a sustainability perspective. 50k$ for half a year is a salary for a good engineer. If I look at our repositories I would budget this number for maintenance and support on our Python libraries. Especially because this would systematically address some of the technical dept we have developed being one of the first with independent implementations of key libraries (such as PyScaleCodec, PySubstrateInterface and PySr25519Bindings, etc) and stay on par with the heavy flux of Substrate. I do think the amount for the activity is reasonable and I do think that funding through Treasury Spending is reasonable, but that said, so far, I haven’t dared asking the Polkadot Treasury for such amount for maintenance and community support for the Python Libraries maintained by Polkascan Foundation. We prioritized on operational expenses for running the Polkascan.io platform. Now that seems to have been approved a next logical step for Polkascan Foundation would be a funding request for maintenance and support of our Python libraries. Fundamentally I believe that the Polkadot Treasury should be willing to pay for maintenance (and support) of its (core-)infrastructure.