Please vote "no" here. The correct proposal is [here](https://polkadot.polkassembly.io/referenda/290)

We'd like to fund maintenance of the [substrate-api-client](https://github.com/scs/substrate-api-client) from January 2024 until June 2024.

The [substrate-api-client](https://github.com/scs/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](https://wiki.polkadot.network/docs/polkadotjs). With an RPC client developers can easily interact with any Polkadot or Kusama chain. There are [RPC clients](https://wiki.polkadot.network/docs/build-tools-index#rpc-and-api-tools) for different programming languages. For Rust, the most popular RPC client is [subxt](https://github.com/paritytech/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](https://polkadot.polkassembly.io/referenda/118). 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](https://docs.google.com/document/d/1x4e2DObj66Xh-DcvxBsDfvDsJX57KE88aMdH1Cvl3Ng/edit?usp=sharing)

Requested Funding: $30’000

Maintenance for the substrate-api-client Jan-24 to Jun-24

Treasury

Put forward a suggestion for spending. A deposit proportional to the value
is reserved and slashed if the proposal is rejected. It is returned once the
proposal is awarded.

## Complexity
- O(1)

Problem Statement:
- The current proposal is not the correct one and should be voted against.

Significance:
- The correct proposal can be found at the provided link.

Proposed Solution:
- Vote "no" on the current proposal.

Expected Outcomes:
- The correct proposal will be implemented.

#284 Wrong Proposal

No Active Proposals