#25 # Invitation and promotion of Pierre Krieger
Pierre Krieger aka tomaka is one of biggest core contributors to Polkadot. He is the main author of the initial implementation of rust-libp2p. rust-libp2p is being used by Substrate for the networking stack. Pierre was also the main author of the initial implementation of the Substrate networking stack:
He was also maintaining and preparing the network stack for Polkadot over multiple years. While doing that he has also done other great contributions like HTTP requests support for offchain workers.
His most important project that he started and is still maintaining as the main author as of today is smoldot. Smoldot is the most advanced light client implementation that is, as the name suggests, a light client for Polkadot. Given the goals of Polkadot around decentralization and censorship resistance, smoldot is one of the most important projects in the Polkadot ecosystem for achieving these goals.
Besides that Pierre has also written the new JSONRPC spec that is light client first from the beginning. He is also quite active in helping to improve the Polkadot spec and has also done some RFCS.
Given all the work Pierre has done for Polkadot and the entire ecosystem, I propose that he gets invited to the fellowship and ranked up immediately to rank V at least. I would actually promote him to rank VI, but this requires a public referendum. As I can only vote for rank V right now, I propose to first add him to the fellowship as rank V and then rank him up to VI.
Show More
Overall 75 % of users are feeling optimistic. Join AAG this Monday at 3:30pm UTC with a team member to understand the proposal's importance to tokenholders! Reach out via Matrix for details and thank you @447368856cec4afcae909c71d. We appreciate your support, Team ParaSpell.
Overall 25 % of users are feeling against it. The text criticizes those voting against funding maintenance for Polkadot and parachain APIs, arguing that it will save developers time and effort by simplifying the implementation of XCM capabilities in applications. The author encourages voters to consider the benefits of interoperability between Kusama & Polkadot before casting their vote.
AI-generated from comments
Hello! We invite a member of the team to join AAG this Monday at 3:30pm UTC to help us better understand this proposal and its importance to tokenholders!
Please reach out on Matrix @ jay-chrawnna:matrix.org
Thanks! 🙏
Dear @447368856cec4afcae909c71d,
thank you for the invite. We appreciate it and gladly accept.
We hope, that this will help the Kusama community with clarification of our proposal.
With kind regards,
Team ParaSpell
I would challenge anyone who's voting NAY to attempt to build a script using nothing but Polkadot & parachain APIs to XCM KSM to any parachain and back. Go ahead and build that script, make it open source, and I'll request a tip for you. Oh, and if your script doesn't work in 5 months I'll mercilessly blast you on Twitter, Element, and here on Polkassembly. Go ahead...
Yeah, it's ridiculously tedious. Not to mention that you have to keep track of the documentation of both Polkadot API and whatever parachain API to make sure your script is always working.
Dev tool kits like this make it very easy to implement XCM capabilities in applications. I have no idea why people are voting NAY for something that will save hundreds of devs many hours of banging their heads against the wall.
Let's pay ParaSpell to bang their heads against the wall for all of us. This maintenance funding will allow devs to focus on the actual meat and potatoes of their applications rather than needlessly spending time implementing XCM raw dog.
The easier it is to use Kusama & Polkadot's flagship feature of interoperability, the better it is for all of us.
Try using your brains before you vote NAY. If you vote NAY on this, you're a buffoon to me.
Thank you for being so supportive, we really appreciate, that you find our work valuable and even more so, that you took the time to actually read our proposal before voting.
As I've mentioned, the ParaSpell team is here to answer any questions regarding our project during this referenda period.
We will also present ParaSpell on AAG next Monday. Can't wait for it because we hope, that we will be able to bring more clarity to the Kusama community in regard to what our project does and why we believe, that it is very needed in the ecosystem. At least in its current state where XCM is so diverse to implement manually.
With kind regards, Team ParaSpell
A member of the team joined AAG on June 5, 2023. Watch the clip 👇 (8:46) https://twitter.com/TheKusamarian/status/1666094384629288961
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
Discover similar proposals
