We'd like to fund maintenance of the <a href="https://github.com/scs/substrate-api-client">substrate-api-client</a> from January 2025 until June 2025.
The <a href="https://github.com/scs/substrate-api-client">substrate-api-client</a> 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 <a href="https://wiki.polkadot.network/docs/polkadotjs">Polkadot-js</a>. With an RPC client developers can easily interact with any Polkadot or Kusama chain. There are <a href="https://wiki.polkadot.network/docs/build-tools-index#rpc-and-api-tools">RPC clients</a> for different programming languages. For Rust, the most popular RPC client is subxt. The substrate-api-client uses core functionality of <a href="https://github.com/paritytech/subxt">subxt</a> 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 <a href="../referenda/792">here</a>. See also our reports in the comments section of each proposal. We aim to seek ongoing funding.
Details can be found in our <a href="https://docs.google.com/document/d/1HCRDQOoGPwEjs4N1e8IXx7enhpdJ5CoTSnKhfBTk4To/edit?usp=sharing">full proposal</a>
Requested Funding: $33&rsquo;200

We'd like to fund maintenance of the <a href="https://github.com/scs/substrate-api-client">substrate-api-client</a> from January 2025 until June 2025.
The <a href="https://github.com/scs/substrate-api-client">substrate-api-client</a> 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 <a href="https://wiki.polkadot.network/docs/polkadotjs">Polkadot-js</a>. With an RPC client developers can easily interact with any Polkadot or Kusama chain. There are <a href="https://wiki.polkadot.network/docs/build-tools-index#rpc-and-api-tools">RPC clients</a> for different programming languages. For Rust, the most popular RPC client is subxt. The substrate-api-client uses core functionality of <a href="https://github.com/paritytech/subxt">subxt</a> 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 <a href="792">here</a>. See also our reports in the comments section of each proposal. We aim to seek ongoing funding.
Details can be found in our <a href="https://docs.google.com/document/d/1HCRDQOoGPwEjs4N1e8IXx7enhpdJ5CoTSnKhfBTk4To/edit?usp=sharing">full proposal</a>
Requested Funding: $33&rsquo;200

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

As requested by several parties, we started a new proposal asking for USDT. (<a href="1332">Link to old proposal</a>)
We'd like to fund maintenance of the <a href="https://github.com/scs/substrate-api-client">substrate-api-client</a> from January 2025 until June 2025.
The <a href="https://github.com/scs/substrate-api-client">substrate-api-client</a> 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 <a href="https://wiki.polkadot.network/docs/polkadotjs">Polkadot-js</a>. With an RPC client developers can easily interact with any Polkadot or Kusama chain. There are <a href="https://wiki.polkadot.network/docs/build-tools-index#rpc-and-api-tools">RPC clients</a> for different programming languages. For Rust, the most popular RPC client is subxt. The substrate-api-client uses core functionality of <a href="https://github.com/paritytech/subxt">subxt</a> 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 <a href="792">here</a>. See also our reports in the comments section of each proposal. We aim to seek ongoing funding.
Details can be found in our <a href="https://docs.google.com/document/d/1HCRDQOoGPwEjs4N1e8IXx7enhpdJ5CoTSnKhfBTk4To/edit?usp=sharing">full proposal</a>
Requested Funding: $33&rsquo;200

- Problem Statement: Funding needed for maintenance of substrate-api-client from January 2025 to June 2025.
- Significance: Substrate-api-client is crucial for connecting to substrate-based nodes from no-std environments like IoT devices.
- Proposed Solution: Continuation of maintenance proposals for substrate-api-client.
- Expected Outcomes: Requested funding of $33,200 for ongoing maintenance.

#2573 Maintenance for the substrate-api-client Jan-25 to Jun-25

No Active Proposals