Firo’s official JavaScript library for talking to firod was written in 2014 by BitPay and hasn’t had a real update in years. It uses outdated patterns, has no type safety, and any developer building on Firo today has to work around it or write their own from scratch. Other major coins all have modern, maintained TypeScript libraries. Firo doesn’t.
Any wallet or service that wants to integrate Firo needs this layer. Right now they’re either rewriting it privately or passing closed-source code around — meaning the work is being duplicated repeatedly and none of it benefits the Firo ecosystem publicly.
I’ve already built one. @nexusocean/firo-rpc is published on npm under MIT license and is currently being used in production by a payment system handling Firo, Monero, and Ethereum. It covers about 40% of what firod can do — enough for transparent payments, block explorers, and basic wallet tooling.
What’s the proposal?
Finish it. Add the remaining RPC coverage, including Spark (the most important missing piece), masternode methods, raw transaction handling, and light wallet methods. Write documentation and examples. Commit to 6 months of maintenance after delivery.
How much?
1200 FIRO (approximately $1200 USD).
Why me?
I built the library and I maintain it. It’s already published, already in production use, and was proposed upstream as a replacement for the old library. Funding this finishes work that’s already 40% done.
For me to support this you’d need to move it into firo’s org account. These days with AI there is zero trust anymore so we need a bit more trust for the firo-rpc and it not be in some stranger’s account. Essentially you’d need to donate its current state to the firo core team and then work as a contributor to it, vs an owner.
Also, the price is insane. Software is cheap now man. Are you using Cursor? With AI (composer 2.5 is amazing) you could easily finish the work in a few dedicated days. I’d be willing to dedicate a few days of tokens to work on it too if it was part of the official firo org.
I’m willing to adjust and would be glad to hand it off to the Firo org account. I really want to finish this project, which doesn’t help my case . Software is a lot cheaper than it should be, but a lot of it lacks experience and actual understanding of what’s going on. Besides the point though, what do you honestly think is fair or at least a doable amount. I’m all ears.
Hi I just joined the Telegram, I don’t think I can message though. My username is zeroxvinny if that helps. I’d be glad to submit it to funding.firo.org though, I was just unsure of how things were handled. I was actually just working on my payment processor that currently accepts transparent Firo with the rpc library at moment.
Awesome! Looking forward to see your proposal on the FCS.
There is a community fund to fund proposals/projects like yours that helps the firo ecosystem.
Thank you, I just added it to the official proposals. I didn’t put a set target since I’m open to hearing what the community thinks is a fair or manageable amount. I just put a rough number out there.
I don’t know what vercel is but it’s not related. Check out Cursor editor.
I’m not talking about vibe coding btw. You still review code it produces, but also give it explicit instructions on what to solve/design, etc. Cursor makes all of that easy.
Anyways, enough shilling of Cursor. Any AI editor will help you to be honest.
Ah I knew I wasn’t completely off anyways, if you’re not interested that’s fine. You haven’t told me what you think is fair and unfortunately you’re the only reply that I think was interested. If you aren’t interested that’s fine.
There is Telegram group to speak and vote about proposals: Telegram: View @firocfc
You could join there if there will be any direct questions regarding project/proposal.
I think I may have taken something the wrong way, it happens with only text based messaging sometimes. I’m definitely still wanting to do this project and would appreciate any feedback or questions.
Correct npm is not up to date as far as the readme and does not include examples or tests currently written. I can open it back up on GitHub if needed, the plan was to hand it over to Firo org regardless as requested. So no issues with that at all from my end.