FCS Proposal - ZZ NoImg3

fcs-proposals
1

A new proposal has been posted to the Firo Crowdfunding System.

  • Title: ZZ NoImg3
  • Author: panagot
  • Proposal type: Miscellaneous
  • Link: click here

Use this topic to discuss this proposal!

1 Like
2

Category changed from ‘Miscellaneous’ to ‘Wallets’

1 Like
3

Sounds and looks great! I dig, though I want to keep on reading more about it on site.

Thanks for your work. :slight_smile:

1 Like
4

Thank you for your feedback! :slightly_smiling_face:

5

Hi @PANAGOT ! It would great if you can join the CFC telegram channel for ongoing discussions in real time.
(Telegram: View @firocfc)

2 Likes
6

[7/21/2026 3:51 PM] PANAGOT: Hi guys, glad to be here, hope you’re doing well.

For any questions , improvements, add ons feel free to recommend so I can work on them.

[7/22/2026 5:41 AM] Vinny in reply to PANAGOT:
‎⁨Hi guys, glad to be here, hope you’re doing well…
I think I like this idea, but I’m not sure I understand the utility of it as a developer or if it’s more of a public display of network health, which is fine in itself. I personally would like more resources available in relation to the Firo Electrumx implementation as it is unique to Spark. So I’m mainly looking for clarity, what does the JSON API provide me with as a developer and a public tool? I’m unsure about what it provides based on the progress made so far. Also, the recently funded typescript SDK I wrote does allow for querying some of what I think this offers and Electrumx itself has a lot of benefits over the full node, which is why it’s in Campfire and Stack wallet.

[7/22/2026 5:50 AM] Vinny: Electrumx has benefits, not a replacement or necessarily better than a full node since it does require one to begin with, just to be clear on what I meant.

[7/22/2026 4:55 PM] PANAGOT: It’s mainly a public fleet-health board for firo users plus a dev/ops JSON feed. If Spark Electrumx docs/examples are what you’d value most I can add them in a separate / additional category inside developers.

[7/23/2026 5:05 PM] Reuben Yap in reply to PANAGOT:
‎⁨It’s mainly a public fleet-health board for firo users plus a…
So from the dashboard prototype, what’s the work left past that? hardening ?

[7/23/2026 5:38 PM] Nrsimha: Hi Panagot

[7/23/2026 5:39 PM] Nrsimha: @panagot Can you please help me to understand who uses it for what? Is that for user of ElectrumX wallet who can check what server to use? Or who would be main user?

[7/23/2026 7:46 PM] PANAGOT: Hi Reuben, Nrsimha,

It’s more than hardening. The dashboard is the frontend; the goal is always-on infrastructure plus decision tools.

Main users: wallet/SDK teams reviewing default servers, Electrum operators proving reliability, and (secondarily) anyone checking why Spark sync is stalling.

M1 — Always-on production
• Public MIT repo + own domain (past Vercel preview limits)
• Dedicated VPS with durable multi-day history + reliable JSON API
• Continuous Spark fleet probes, including full anon-set sweeps (those don’t scale well on serverless long-term)

M2 — Ops & decision tools
• Alerting (Telegram / Discord / webhook) on Spark mismatch, red status, or tip lag
• Operator self-check + public registry (“add my server”)
• Embeds for READMEs / status pages
• Wallet scorecard (Spark-consistent · anon-set ms/MB · tip lag · uptime %) for default-server decisions
• One-click compare across backends
• Spark incident log (e.g. setHash divergence windows)
• Anon-set growth / health charts

[7/24/2026 5:21 AM] Antibit: I’m glad we have more funding proposals. But I don’t understand the practical benefit of this funding. Who will use it?

[7/24/2026 8:18 PM] PANAGOT: Shipping tools like this is how Firo keeps building in public and shows an active builder community. If this is an issue of funding, I can reduce it down to 2000 firo. Since also firo has gone up +30% last 4 days.

[7/25/2026 1:17 AM] Nrsimha: I personally don’t think this project is really gonna be used by many users.
If it is made mostly for wallet developers, they could integrate status/health of ElectrumX servers into their wallet.

[7/25/2026 1:18 AM] Nrsimha: Voting nay. (But if somebody gives good arguments and usage for this project I am open to reconsider my vote)

[7/25/2026 5:06 AM] Antibit: I will abstain from voting on this proposal, we have that option

7

Hi guys, so is there any other voting regarding this proposal?

8

[8/2/2026 9:49 PM] Jagmo: I am still evaluating the proposal. I hope to do so today as I’m back from my travels.
[8/4/2026 5:17 AM] Jagmo in reply to PANAGOT:
I see funding is included for hosting for 1 year. After 1 year, do you plan to submit a proposal to fund hosting again?
[8/4/2026 1:40 PM] Vinny in reply to PANAGOT:
No hard feeling regardless, but either way I’m inviting you, and would greatly appreciate, contributions to the public explorer I made if you’re interested because it would makes sense under one dashboard and you know the stack somewhat already. Feel free to message me if you’d like. Sorry if I’m slow to respond.
[8/4/2026 3:12 PM] PANAGOT in reply to Jagmo:
After one year it can be renewed one more and then the domain can go into the hands of the community.
[8/5/2026 4:21 AM] Jagmo in reply to Vinny:
I appreciate this as I’m not technical enough to understand if the current proposal is really needed.
[8/5/2026 4:21 AM] Jagmo in reply to PANAGOT:
Thank you for your answer on the second question. Are you still researching my first question?
[8/5/2026 5:07 AM] PANAGOT: something slightly similar can be found on zcash Hosh: Zcash Light Wallet Uptime and monero https://monero.fail/
[8/5/2026 5:11 AM] PANAGOT: Bitcoin All Seeing Eye bitcoin and forks
[8/5/2026 11:29 PM] rehrar: Aye from me. Looks interesting, reasonable. May give a quick way to check against for wallets.
[8/6/2026 11:47 PM] Jagmo in reply to rehrar:
I am voting yes, but it was a tough call. I’m still a bit unclear on the use case, but Rehrar’s vote carries weight for me given his experience with Stack Wallet and Cypher Stack.

9

:light_bulb:Update on Firo Spark Sync Monitor by @panagot

4 of 7 CFC members has weighed in and voted on this proposal While the remaining 3 has yet to vote or voice their opinion.
Please do weigh in your thoughts.

Aye :white_check_mark:
@rehrar
@jagmot

:prohibited: Nay
@Nrsimha

:stop_button: Abstain
@firofan

:counterclockwise_arrows_button: Have not voted
@FiroFiend
@vaselexa
@ddadybayo

10

Category changed from ‘Wallets’ to ‘Committee’

11

[8/7/2026 1:15 AM] ddadybayo: Aye
[8/7/2026 1:27 AM] Antibit: I will also say Yes, please change my “Abstain”
[8/7/2026 1:28 AM] Antibit: The proposal was accepted by the majority
[8/7/2026 1:30 AM] Antibit: Come on, bruh, don’t let down) @panagot

:light_bulb:Update on Firo Spark Sync Monitor by @panagot

4 out of the 7 CFC members has expressed their approval in support of advancing the proposal.

Given that a majority has voted Aye for this proposal, It has Passed :white_check_mark:. Thank You :handshake:

Aye :white_check_mark:
@rehrar
@jagmot
@ddadybayo
@firofan

:prohibited: Nay
@Nrsimha

:counterclockwise_arrows_button: Have not voted
@FiroFiend
@vaselexa

12

Status changed from ‘Funding Required’ to ‘WIP’

13

image
image1239×900 141 KB

Thanks for accepting.
Updating with latest development.

image
image889×610 74.7 KB

image
image904×801 105 KB

14

M1 is now complete.

Please visit Firostatus