Maintenance for the substrate-api-client Jan-24 to Jun-24
This is the corrected proposal of this one. Please move your vote here.
We'd like to fund maintenance of the substrate-api-client from January 2024 until June 2024.
The substrate-api-client is a Rust library for connecting to a substrate-based node via RPC from a no-std environment, like trusted execution environments or IoT devices. An RPC client is a library, with similar features as Polkadot-js. With an RPC client developers can easily interact with any Polkadot or Kusama chain. There are RPC clients for different programming languages. For Rust, the most popular RPC client is subxt. The substrate-api-client uses core functionality of subxt and makes it available in a no-std environment.
This proposal is a continuation of our previous maintenance proposals. The previous proposal can be found here. See also our reports in the comments section of each proposal. We aim to seek ongoing funding.
There has been mixed feedback on the question, who should fund the maintenance of the substrate-api-client. Our conclusion is to continue to treat the api-client as a common good - and ask the Polkadot treasury for funding. By receiving funding by the treasury, we can make sure to treat all user requests equally and provide the same service to all. If the proposal is rejected, we will still provide support to anyone requesting it - at our normal hourly rate.
Details can be found in our full proposal
Requested Funding: $30’000
Comments (5)
Proposal Passed
3
of 3Summary
0%
Aye
0%
Nay
Aye (90)0.0 DOT
Support0.0 DOT
Nay (67)0.0 DOT
Voting Data
Approval%
Support%
Threshold0.00%
Threshold0.00%
I don't understand why this has an issue with getting funded. It is obviously being widespread used, by big parachain teams, but also by small independent users. For sure, the hourly rate seems high, but the standard Swiss hourly rate for a Swiss engineering company is like this. Disclaimer: Ex-Supercomputing system employee here, but it doesn't affect my argument IMO.
Hi Supercomputing Systems, Due to the the amount of utilization these packages have in the ecosystem, we view them as high-impact and will support this proposal. That said, we would have appreciated to understand any thoughts you'd had on a path to future sustainability as you mentioned you would here: https://polkadot.polkassembly.io/referenda/118. Best, Ivy