Maintenance for the substrate-api-client May-23 to Jul-23
We'd like to fund maintenance of the substrate-api-client from May 2023 until July 2023. This is a continuation of the Treasury Proposal: Maintenance for the substrate-api-client Feb-23 to Apr-23.
The substrate-api-client is a Rust library for connecting to a substrate-based node via RPC in a no-std environment. 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. Subxt uses the Rust standard library (std). The Rust standard library is not available in certain environments, such as trusted execution environments (like IntelSGX) or certain IoT devices. The substrate-api-client bridges this gap, providing a library that can be used in such environments.
This proposal is a follow-up of the treasury proposal Maintenance for the substrate-api-client Feb-23 to Apr-23. View our report for details on our work there. We aim to seek ongoing funding. Since the funds of the Kusama treasury are currently limited, and many projects ask for funding, we decided to make a smaller proposal and focus on changes that are needed due to substrate updates.
See the discussion and our full proposal for details.
Comments (2)
Requested
Proposal Passed
Report June 2023
Deliverables
Realization of Goals
Stay up-to-date with Ecosystem
Added support for metadata V15: #587
Introduced metadata V15 fields: #597
Ease of Use
Remove redundant Substrate type definitions: #580, #553
Improve ease of use in no_std: #391, #574
Simplified code structure: #596
Performance Optimizations
Use Visitor pattern in Metadata: #597
Make use of Parity's decoding and encoding (incl. PRs in Parity's repos): #599, #589, scale-decode #26, scale-encode #11, scale-bits #2
User Support
User issues addressed: #581, #555, #560, #576, #492, #572, #575
User PRs reviewed and merged: #568
Hello,
We are in the process of validating a true need for a service to assist teams with crafting and completing successful treasury proposals, so they can focus on building. We would love to hear about your experience with this proposal. If you are willing to take a few minutes, please fill out this form about your experience with the OpenGov treasury proposal process: https://forms.gle/MwDij4adXEQd7Um79
Feel free to leave out any details that your team is not comfortable with sharing, but the more info you can provide, the better we will be able to assess the potential need for our services.
For more info, follow us on Twitter/X: https://twitter.com/OpenGovAssist
Polkassembly is now a read-only archive. Commenting is disabled.