The tool is truly mindblowing and the team the best for developing it. The ecosystem dapps landscape was already revolutionized with their automatic type generation based on the metadata. They didn't stop there though, they kept on adding amazing features we didn't know were possible, like checking whether or not your dapp is compatible with the on-chain runtime and [adapt automatically to runtime upgrades](https://www.youtube.com/watch?v=fj63gYJmuIk). Can't wait to see what they achieve next.
PAPI is the tool the ecosystem needs. Keep up the good work.

90k a month for 4 people, that's 22.5k per person. Peanuts!



The sum per developer/month before income taxes is €18,595, not €23,548, as 21% goes directly to pay IVA (a VAT tax that is deducted before calculating income taxes). You can find more details about this [here](https://petete.tributos.hacienda.gob.es/consultas/?num_consulta=V2479-22).

This rate is consistent with what we’ve used in our last two proposals. We provided a detailed justification for this rate in our [first OpenGov proposal](https://docs.google.com/document/d/1t_yKXKuy2kfQBTNVkG1Hn3_rs8-sT1nwp55TENcHQ4g), and in fact, many people suggested that we were undercharging given the expertise required for a project of this complexity.

I’m surprised that, despite our consistent over-delivery over the past six months, our hourly rate of €124 is now being questioned.

It’s important to highlight that we have been completely transparent about how we manage our resources. In our previous proposals, we only withdrew the exact amount requested in Euros, responsibly staking any excess DOTs due to price fluctuations. With the new option to submit proposals in stablecoins like USDT or USDC, this practice is no longer necessary, and we will be returning all excess DOTs previously accumulated to the Treasury.

Additionally, we have been saving most of this income within the company to grow our team. This approach allowed us to onboard Carlo even before receiving the funds from the second proposal, and we’ve also brought Hannah on board a month before the end of the second proposal.

[@Josep](15roJ4ZrgrZam5BQWJgiGHpgp7ShFQBRNLq6qUfiNqXDZjMK-polkadot) 
It is a brutally high hourly rate and we could get better deal if there was less corruption in the ecosystem and other developers would get the chance.

[@playproject.io](12VpEWKJVwxRiDd8qjNAyEijS3CuhBDhiYnhLJc7ANfqmVJM-polkadot), I’m surprised to see that our hourly rate, which has been consistent across our last two proposals, is now being questioned. What, in your view, would be a fair hourly rate for the expertise and experience we bring to the table?

After extensive consultations, we concluded that our skill set is positioned between that of Ross Bulat, who charged $200/hour, and Pierre Krieger, who charged €300/hour. Despite this, we decided to set our rate at €124/hour to align with the market salary for Senior Engineers of our caliber in this field.

If you genuinely believe our rate is "brutally high," I ask that you present real arguments to support this claim. Furthermore, I take strong offense at the baseless accusation of corruption. This accusation is especially outrageous coming from someone who has received substantial funding from this ecosystem without delivering any tangible results.

Let me explain why this accusation is both unfounded and offensive:

I left a secure position at Parity because I wanted to build a strong team dedicated to contributing to this ecosystem. I convinced one of the best software engineers I’ve ever worked with, Victor Oliva, to join me on this challenging journey, leaving behind a stable career at Adaptive Financial Consulting, where he had worked for seven years. Together, we submitted our first OpenGov proposal, requesting just two months of funding.

During those two months, we worked tirelessly to deliver the first beta version of the Polkadot-API library. In addition to this, we made significant contributions to the ecosystem:
- We contributed to the new JSON-RPC specification.
- We reported several issues to smoldot and also made some contributions to it.
- We opened issues and provided feedback to the Polkadot-SDK.
- We assisted various teams within the ecosystem in utilizing our libraries.

Following this, we convinced another talented developer, Carlo Sala, to join our team. He was previously working at Zondax, contributing -in that moment- mainly to other ecosystems. We were able to onboard him by saving a significant portion of our salaries to ensure he could start working with us before we received the funds from our next proposal.

After over-delivering on our first proposal, we submitted a second OpenGov proposal, requesting three months of funding over four months. During one of those months, Victor and I attended the Polkadot Blockchain Academy, where we both graduated with distinction. I made significant personal sacrifices to attend this academy because I believed it was crucial for my role as the tech lead of an important project. Despite being away from my family (I have 2 kids) for an extended period, I continued to oversee PAPI and assist others without being paid.

During this time, we also applied for the Decentralized Futures grant, which was unexpectedly rejected with the feedback that "this would be better funded by the community". Nevertheless, we persevered with our plans.

Upon returning from the academy, our team quickly responded to the "new signed-extension incident" by delivering the `@polkadot-api/merkleize-metadata` library, the only TypeScript library compliant with RFC78. This library is now used by teams such as Talisman and PolkadotJS. Few teams have the capability to deliver such a project, and we accomplished it in about a week thanks to the solid foundation we had built.

During this time, I also secured another valuable team member, Hannah, who joined us from the Ethereum ecosystem. Once again, we were able to onboard her early by saving a portion of our salaries.

In summary, here’s what we’ve achieved through hard work and dedication:
- We’ve built a strong, diverse team, bringing in top talent from other ecosystems. I’m the only team member who has worked at Parity.
- We delivered a modern, alternative library to PJS, which integrates seamlessly with the light client and offers an amazing DX.
- We’ve been active contributors to the standardization of the new JSON-RPC specification.
- We made important contributions to smoldot and the PolkadotSDK repository.
- We developed libraries like `@polkadot-api/merkleize-metadata`, which are now widely used within the ecosystem.
- We’ve supported and enabled numerous teams within the ecosystem, incorporating invaluable feedback.
- We’re currently contributing to Chopsticks to ensure it’s compliant with the new JSON-RPC spec, making it interoperable with other compliant libraries.

Given all we’ve accomplished through dedication and sacrifice, how can you accuse us of corruption? Please explain how our work does not represent an excellent return on the investment made in our team.

Your baseless accusations are not only unfounded but deeply insulting, especially considering your own lack of contributions to this ecosystem. Such slander from someone who has failed to deliver anything substantial is utterly shameless.

[@Josep](15roJ4ZrgrZam5BQWJgiGHpgp7ShFQBRNLq6qUfiNqXDZjMK-polkadot) Don't be surprised, the amount you are asking for as a european developer is just too high, specially in the times when dot is very low. You could also hire less expensive developers, as you know very well they exist and are available for probably half the price and even that is high.

Prices of developers in the fellowship for a comparison. Bare in mind they are in USD while in this proposal they are in EUR. It seems like a grift, these results can be achieved for way less funds and it is sad to see long time members trying to maximize their profits on the account of the treasury.

https://wiki.polkadot.network/docs/learn-polkadot-technical-fellowship#technical-fellowship-ranking-and-salary

Hello and thank you for the referendum. Currently we are facing a situation where we have low funds in the treasury so cutting non essential projects seems necessary. However, we consider PAPI a very necessary project due to the obsolescence of our current developer console polkadot.js and for that reason we have voted AYE already.
However, the high salaries is not only a concern of ours but of many others so we would like to respectfully request a longer and more reasonable period to support than to January 2025. This will not only help the treasury directly but also to set an example to keep a slightly tighter belt for other teams during these important times. NAYing this proposal and delaying the funds is the least desirable option for all parties so for that reason we would like to know if it's possible to review the salaries through a longer development financing duration while the referendum is live. 

I believe this is a promising project, and I appreciate the work that has gone into it. However, I have a few concerns that align with SAXEMBERG's perspective:

1. **Funding Duration and Evaluation**: How long do you anticipate the treasury should fund the development and maintenance of PAPI? Could you provide a tentative evaluation of the total funding required (e.g., $2M, $3M)? A clearer understanding of the long-term financial commitment would help the treasury make a more informed decision.

2. **Contingency Plan**: In the event that the community does not approve this proposal, what are your plans for moving forward? Having a contingency plan might demonstrate preparedness and adaptability.

3. **Clarity on Deliverables**: A significant portion of the funding is allocated to PAPI SDKs and PAPI Actions, yet the descriptions of these deliverables seem brief or unclear. Do you believe providing a more detailed technical description or even a proof of concept could help the community better assess the potential impact and value of these components?

I've been using papi for the past couple weeks, and after using `polkadot.js/api` for the past 5 years, it's eye opening.

This team is talented, motivated, very reactive on Github, and helpful.
The Developer experience is stellar. Strongly typed api is working very well. I'm certain that this is the future of Polkadot Dapp development, and it will enable much better applications and products. I'm porting my products to it as we speak, and I'm not looking back.

Hi everyone,

As many of you may already know, Polkadot-API is a project conceived to build upon and surpass the foundational achievements of the PolkadotJs project. At its core, Polkadot-API is a meticulously crafted suite of libraries, designed to be composable, modular, and fundamentally aligned with a "light-client first" philosophy. Our mission is to empower dApp developers by providing them with a comprehensive set of tools essential for creating truly decentralized applications, with a strong focus on enhancing the developer experience.

We have recently posted an update for the latest development cycle on the [Polkadot forum](https://forum.polkadot.network/t/polkadot-api-2024-2nd-update/9673).

We are excited to announce that we have reached a significant milestone: the release of the stable version 1.0.0 of Polkadot-API. We are committed to maintaining and further developing this project to simplify the dApp development process even further.

The Polkadot-API development team is now seeking funding for ongoing maintenance and development through treasury proposals. We are sharing this post to gather your feedback on the proposal before submitting it on-chain.

You can find all the details of this proposal in the following Google Doc: https://docs.google.com/document/d/1s0ftTlWbIqejTVYen0UbgxLGslqjODUl57W1tOVldpM

Thank you for reading.

[Polkadot-API Dev Team](https://polkadot.subscan.io/account/13dXmfrN4Prb3FmdxKDNRyUeNDuNwUTZibYAMFNKmZJut2Lq) ([@Josep](/user/Josep), [@carlosala](/user/carlosala), [@hannah](/user/hannah), and [@voliva](/user/voliva))


- Polkadot-API is a project that builds on PolkadotJs.
- It provides tools to help developers make decentralized applications (dApps).
- The project focuses on ensuring it's easy to use and "light-client first."
- The stable version 1.0.0 of Polkadot-API has been released.
- The team is looking for funding to continue developing the project.
- They want feedback on their funding proposal before submitting it.
- More details about the proposal can be found in a shared Google Doc.

AssetSpendApproved

Paid

medium_spender

WHO: Polkadot-API development team

WHAT: Seeking funding for ongoing maintenance and development through treasury proposals

PRICE/TIMEFRAME/RESOURCES: Details of the proposal can be found in the Google Doc provided.

#46·Polkadot-API: Aug 2024 - Jan 2025 development financing