Please express your interest in standing for election in the Forum thread here. Do ensure you introduce yourself and why you are applying to the post and your experience/history with Firo.
The 7 member CFC forms an important role in gradually decentralizing governance and sets up an independent fund (Firo Community Fund) to be used for the benefit of Firo. The FCF has been used to fund various community management efforts, audits, social media/marketing support and also to assist the core team where additional funds are required.
Current CFC Members:
CFC Committee positions are at this point in time done on a volunteer basis and we recommend only active and motivated members of the Firo community apply. There is no restriction on existing committee members seeking re-election.
Below is a reminder of the role of the CFC and the Firo Community Fund (FCF) it manages:
Firo conducted a series of community votes to adjust its tokenomics and established the Firo Community Fund. This process spanned several months and involved multiple vetted polls to ensure alignment with the community’s wishes. A committee comprising seven elected community members was established to manage fund allocation.
Following the nomination phase, nominees (who are new) undergo a vetting process, including an interview, to assess their eligibility and alignment with the community’s voting objectives. The interview, which can be conducted through text or online meetings, delves into the nominees’ beliefs in Firo, their grasp of Firo’s technology, personal background (without revealing sensitive information), and their vision for the fund’s utilization. Nominees not widely known in the community must provide proof of active participation for at least a year.
Moving on from these specifics, it’s essential to outline the responsibilities and prerequisites expected of a member of the Firo Community Fund Committee (CFC).
As always, please backup your wallet before updating.
Download the latest release here: https://github.com/firoorg/firo/releases/tag/v0.14.16.1
This release resolves an overflow bug in Spark Name handling that was present in v0.14.16.0. The fix is the primary reason this follow-up release is mandatory - all users on v0.14.16.0 must update to ensure correct Spark Name behavior at and beyond the activation block.
Fixes a minor vulnerability where a Spark Name transfer permission could remain valid indefinitely. Transfer permissions now expire correctly, limiting the window in which they can be used.
Fixes crashes in the receive request dialog and incorrect handling of recent request history in the Qt wallet.
Fixes a bug where Spark address book options could remain unavailable after syncing past the Spark activation block, requiring a wallet restart to resolve. The wallet now correctly detects activation even when the sync jumps past the exact activation height.
Internal cleanup work removing legacy Lelantus components as the protocol continues to consolidate around Lelantus Spark.
This is a mandatory update that supersedes v0.14.16.0. All wallets, full nodes, and masternodes must be updated to v0.14.16.1 before block 1,329,000, approximately 22 June 2026. This applies even if you recently updated to v0.14.16.0.
Binaries are available for Linux, macOS, and Windows on the GitHub releases page.
]]>In the founder’s own words: “The original idea behind SmoozyPool was to support privacy-focused and community-driven coins, not just add random mining coins. Firo fits that direction well because it has a strong privacy mission, real technology behind it, and an active long-term community.”
SmoozyPool is a multi-chain pool supporting GPU, CPU, and ASIC mining across a range of privacy and community coins. Firo mines on the FiroPoW algorithm, which is GPU-friendly and ASIC-resistant by design, keeping mining accessible to commodity hardware.
| URL | smoozypool.es |
| Algorithm | FiroPoW |
| Pool Fee | 1.5% |
| Minimum Payout | 0.5 FIRO |
| Payout Frequency | Every 2 hours (automatic) |
| Modes | PPLNS and SOLO |
Getting started takes three steps: choose Firo as your coin, generate your mining command using SmoozyPool’s built-in config generator, and run your miner.
PPLNS port: 4031
SOLO port: 4034
SmoozyPool’s site includes a mining command generator - enter your wallet address and worker name and it outputs a ready-to-run command for your preferred miner. No manual config editing required.
Make sure you are mining to a self-custodied Firo wallet. We recommend Campfire (mobile) or Firo QT (desktop). Avoid mining directly to an exchange address.
Welcome to the #FiroFam, SmoozyPool. 🔥
]]>As always, please backup your wallet before updating.
Download the latest release here: https://github.com/firoorg/firo/releases/tag/v0.14.16.0
Users can now extend or transfer their Spark Name and have the leftover validity period credited - so you only pay for the time you are actually adding. This makes long-term use of Spark Names more practical and cost-efficient, and removes a friction point for users who want to keep their on-chain identity current.
Spark Names are Firo’s human-readable on-chain address system, letting you send and receive FIRO using a simple alias like @sparky instead of a long cryptographic address - all while preserving the full privacy guarantees of Lelantus Spark.
A bug causing the Spark Name list in the wallet to not refresh correctly has been resolved. Registered names will now display accurately and update as expected.
This release adds Wayland display protocol support for the Qt wallet. This benefits Linux users running Wayland compositors, improving compatibility and stability of the desktop wallet on modern Linux environments.
The getspentinfo RPC call is now properly registered, and stale mempool spent index entries are cleaned up when transactions are removed. This improves reliability for developers and node operators querying spent transaction data.
This is a mandatory update. All wallets, full nodes, and masternodes must be updated to v0.14.16.0 before block 1,329,000, approximately 22 June 2026.
Binaries are available for Linux, macOS, and Windows on the GitHub releases page.
]]>MeowPool launched in early 2026 with a clear mission: to help decentralize hashrate and support projects worth believing in.
The founder isn’t a stranger to mining. Back in 2020–2022, she was an active miner himself and she kept running into the same frustration: hashrate was perpetually consolidating into a handful of large pools. That centralization is bad for networks, bad for decentralization, and ultimately bad for the projects that depend on a healthy, distributed mining ecosystem.
So she built his own pool. MeowPool is a passion project at heart designed to support projects she genuinely believes in and to give miners a meaningful alternative to the giants.
Firo is a natural fit.
Head over to meowpool.net to get set up. You’ll find the connection details and configuration instructions there.
Make sure your wallet is ready to receive FIRO. If you haven’t set one up yet, you can download the official Firo wallet at firo.org/get-firo/download.
]]>DFX AG is a Zug-based open-source platform that bridges traditional banking and crypto. Users can buy, sell, and swap over 80 cryptocurrencies directly from their own wallets - whether that’s MetaMask, Ledger, Trezor, or any WalletConnect-compatible wallet - via SEPA, SEPA Instant, and SWIFT bank transfers, with no centralized exchange in between. DFX also provides an integration toolkit (the DFX Toolbox) that lets wallets and apps embed fiat on/off-ramping through a simple API or iFrame widget.
Beyond on/off-ramping, DFX powers crypto payments at physical retail locations in Switzerland, including 137 SPAR supermarkets - making it one of the few platforms bridging both the fiat-to-crypto and crypto-to-retail gaps.
DFX is integrating FIRO into their platform. This gives FIRO holders a non-custodial path between fiat and FIRO - buy directly from a bank account into your wallet, or convert back to CHF or EUR without touching an exchange. It also means FIRO becomes spendable at physical retail locations like SPAR supermarkets in Switzerland.
Payments use Firo’s privacy preserving Spark Addresses by default, so users can send and receive funds through a reusable address without exposing their transaction history. The privacy guarantees that Firo is built on carry through to the payment experience - no compromises, no workarounds.
The integration with DFX is live. We’re now working on bringing it directly into wallets, with Stack Wallet expected to be the first to integrate DFX’s on/off-ramping for FIRO. This will give users a seamless in-wallet experience for buying, selling, and spending FIRO with fiat.
Privacy coins often face a practical gap: you can hold them privately, but moving between fiat and crypto, or spending at real-world merchants, usually means giving that privacy up. DFX’s non-custodial approach and Firo’s Spark Addresses close that gap. FIRO users can on-ramp, off-ramp, and pay at retail without routing through a centralized exchange or exposing their transaction history.
We’ll share more updates as wallet integrations roll out. You can learn more about DFX at dfx.swiss.
]]>We’re pleased to welcome Pooly.ca to the Firo ecosystem! Pooly has added FIRO as one of the coins you can mine on their platform.
Pooly.ca is a mining pool with roots going back to 2017. What started as a small community pool has grown steadily over the years and in 2026, Pooly launched a completely new pool UI, new features, and PoolyNodes, a shared masternode hosting service.
The team behind Pooly genuinely understands mining from the inside out, and they’ve always prioritized being a place where miners especially newer ones, can get real help and support.
Miners who remain connected to the PPLNS pool for 30 consecutive days will see their pool fee reduced to 0%. An incentive to retain long-term contributors to the pool.
Head over to pooly.ca for connection details and setup instructions.
If you need a wallet to receive your FIRO, grab the official one at firo.org/get-firo/download.
]]>For privacy coin projects, the question is no longer whether centralized exchange access will shrink. It’s what you build when it’s gone.
Our answer at Firo is Rosen Bridge. And I believe it represents the most strategically sound liquidity play any privacy coin has made to date.
Video: Firo’s Censorship-Resistant DeFi Bridge Is Coming - Rosen Bridge Explained by Reuben Yap.
Before explaining why Rosen Bridge matters, it’s worth honestly assessing why the existing alternatives have failed to deliver reliable, censorship-resistant liquidity for privacy coins. I’ve spent years evaluating and in some cases directly integrating many of these solutions, and none of them, on their own, solve the problem.
The reflexive answer to delistings was always to retreat to smaller, no-KYC exchanges. For years, TradeOgre was the name on everyone’s lips. It was the exchange that “would always be there.” Then in July 2025, it went offline without a word. Two months later, the RCMP confirmed what many feared: the platform had been dismantled, its infrastructure seized, and its users’ funds, including Firo, Bitcoin, Monero, and other privacy coins was confiscated. No arrests were announced. No recourse was offered. Users who had funds in low-liquidity coins or pending withdrawals lost everything.
TradeOgre’s fate was not an anomaly. It was the inevitable conclusion of a strategy built on trusting anonymous operators running unregistered platforms. These exchanges are single points of failure with no regulatory buffer, no insurance, and no obligation to stay online. Building a liquidity strategy primarily around them was always building on sand. History proved it.
Atomic swaps represent the purest form of decentralized exchange: trustless, peer-to-peer, no intermediary. We support these at Firo through FiroDEX, Bison Wallet, and BasicSwap, and they remain a valuable component of our broader liquidity toolkit. I believe in them philosophically.
But as a primary liquidity solution, atomic swaps have a well-documented adoption problem. They require both parties to be online simultaneously for the swap to execute. They demand active market-making to maintain any semblance of order book depth. Execution is slow relative to what users expect from modern trading. After years of development across multiple projects, atomic swap volumes remain negligible compared to even mid-tier centralized exchanges even on the largest cryptocurrencies such as Bitcoin and for Monero, almost negligible. The technology works, but the user experience and liquidity depth simply don’t scale to meet the needs of a project that wants to be usable, not just ideologically pure.
Some projects have explored building native AMM or DEX infrastructure directly on their own blockchain. This approach offers maximum sovereignty with no external dependencies, no permission needed. But it introduces significant protocol complexity, fragments developer attention, and most critically, creates a siloed ecosystem that very few people use. We have also seen how hosting such DEX infrastructure can pose a regulatory threat to core teams.
This is arguably the single hardest problem in the entire space. Even projects with market capitalizations several times larger than Firo’s have struggled and in many cases failed to build meaningfully liquid, long-term sustainable on-chain token ecosystems especially when the liquidity incentives dried up. The liquidity bootstrapping problem is circular: traders won’t come without liquidity, and liquidity providers won’t commit without traders. When your native chain’s entire DeFi ecosystem has a fraction of the total value locked on a single Ethereum AMM pool, the math simply doesn’t work. It’s a noble goal, but for a project of our size, it would be a misallocation of resources with a very low probability of success.
THORChain and Maya Protocol represent impressive engineering enabling native cross-chain swaps through liquidity pools. But the cracks in this model are deep, and they are especially concerning for privacy coins.
First, there is the centralization problem that THORChain’s proponents often downplay. The network runs on a limited validator set that must collectively agree to support each asset. Privacy coin integration requires broad validator buy-in, and validators and the team face regulatory exposure. THORChain still hasn’t shipped Monero support despite earlier promises and years of discussion, with a previous integration attempt aborted due to significant technical vulnerabilities around Monero’s opaque transaction model. The current roadmap tentatively targets 2026, but there’s no guarantee it will ship or that validators will maintain support once regulatory pressure mounts. Maya Protocol faces similar dynamics. Support for any given asset is not permanent; it must be continuously earned and can be removed if validators decide the risk isn’t worth it.
Second, THORChain has a deeply troubling track record. In 2021, the protocol suffered three consecutive exploits draining approximately $13 million. In January 2025, it revealed a $93 million insolvency in its THORFi lending and synthetic asset products, forcing a network pause and restructuring. In April 2025, another $1.2 million security breach hit its liquidity pools. And most damaging to its reputation, the protocol became the primary conduit for laundering $1.2 billion of the $1.46 billion Bybit hack by North Korean state-sponsored hackers with THORChain earning approximately $5 million in fees from those transactions and declining to refund them. The Bybit incident drew FATF scrutiny and has raised serious questions about whether THORChain will face Tornado Cash-style regulatory action.
For a privacy coin to build its liquidity strategy on THORChain is to accept dependency on a system that is simultaneously a regulatory target, an insolvency risk, and a platform where your asset’s continued support depends on the goodwill of a small validator set that could drop you at any time.
And it’s worth noting: THORChain swaps are transparent. Every swap is logged on the THORChain ledger, and as the Bybit hack demonstrated, these transactions are fully traceable by blockchain analytics firms. Maya Protocol and Serai DEX share this characteristic.
Hyperliquid has emerged as one of the most impressive DEX platforms in the space, processing trillions in cumulative trading volume with a CEX-like trading experience built on its own L1. When it listed Monero perpetual futures via its permissionless HIP-3 deployment, the privacy coin community celebrated.
But a closer look reveals fundamental limitations. Hyperliquid listed XMR perpetual contracts derivatives that offer leveraged price exposure not actual spot trading of the underlying asset. You can go long or short XMR on Hyperliquid, but you cannot buy, hold, or withdraw actual Monero. For a privacy coin, this distinction is critical. Derivatives provide speculative access, but they do nothing for the fundamental use case: acquiring and using private digital cash.
Even for spot listings, the path is narrow. Hyperliquid’s HIP-1 token standard does support bridged external assets, projects like Flare have used LayerZero’s OFT standard to bridge their tokens for spot trading, and Hyperunit offers lock-and-mint bridging for assets like BTC and ETH. So HIP-1 itself isn’t inherently centralized. But the practical reality for a privacy coin is stark: which bridge provider is going to support bridging a privacy coin onto Hyperliquid? LayerZero, Chainlink CCIP, and Hyperunit all face the same regulatory incentives as centralized exchanges. Even if a bridge were willing, the resulting token would lose all privacy properties and you’d still face the risk that Hyperliquid’s team or validators could delist you.
The JELLY token incident in early 2025 proved this isn’t theoretical. Hyperliquid delisted a token and settled positions at an arbitrary price to protect its vault from losses behavior indistinguishable from a centralized exchange. While it has since introduced validator voting for delistings, the episode revealed that in a crisis, intervention happens. For privacy coins that are perpetually one regulatory headline away from being deemed problematic, this is not reassuring.
The simplest form of wrapping, deposit your native coins with a custodian, receive a wrapped token on Ethereum, is just centralized custody wearing a DeFi costume. It reintroduces every risk that decentralization was supposed to eliminate: custodial failure, regulatory seizure, key management disasters, and single points of failure.
Firo has direct, painful experience with this. We were the first project to launch on StakeHound, a tokenized staking platform that issued stFIRO as an ERC-20 token on Ethereum representing FIRO held in masternodes. The concept was sound, and for a time it worked. Then StakeHound’s custody provider, Fireblocks, lost the private keys to over $75 million worth of ETH in a key management failure, leading to a protracted legal battle in the Tel Aviv District Court. StakeHound’s operations wound down as a result. To their credit and ours, all stFIRO redemptions back to native FIRO were honored. But the experience was a sobering lesson in the fragility of centralized wrapping solutions. We have no interest in repeating it.
This is where Rosen Bridge enters the picture, and why I believe our strategy around it is genuinely compelling.
Rosen Bridge is an Ergo-centric cross-chain bridge that uses a two-layer security architecture of Watchers and Guards to enable decentralized wrapping of assets across multiple supported chains. The design is elegant in its practicality.
Watchers form the first security layer: entities that monitor source blockchains for bridge-related events and report them to the Ergo blockchain, where all consensus logic lives. Anyone can become a Watcher by staking RSN and ERG tokens as collateral. Watchers from the same chain operate as an independent cross-chain oracle, and a finalized report is only generated when enough distinct Watchers have observed and reported the same event. A small set of faulty or malicious Watchers cannot generate a false report.
Guards form the second layer: a federated set of known entities that independently verify the events reported by Watchers, reach consensus on the appropriate response, and execute multi-signature transactions on the target chain. Guards must lock significant RSN collateral that is slashed for malicious behavior. Their authority is restricted through multisignature contracts, and the system tolerates failures as long as a majority of Guards remain honest.
This dual-layer model means no single party (not the Watchers, not the Guards, not our team) has unilateral control over bridged assets. Crucially, all consensus and auditing happens on the Ergo blockchain, which means there’s no dependency on complex smart contract deployments across multiple chains. Adding a new chain to Rosen Bridge requires only configuring Watchers for that chain and setting up a multisig or threshold signature wallet for the Guards, a modular approach that scales cleanly.
When Firo bridges to Rosen Bridge, native FIRO is locked in the bridge and rsFIRO (Rosen-wrapped FIRO) is minted as a standard token on the target chain, be it Ethereum, BNB Chain, or any other EVM-compatible chain Rosen supports.
Here is the critical strategic insight: rsFIRO is a standard transparent token. It functions identically to any ERC-20 or BEP-20 token. It can be listed on centralized exchanges without any of the compliance friction that native FIRO faces. It can be added to Uniswap, PancakeSwap, or any AMM without special integration work. It can participate in the full richness of DeFi ecosystems, lending, yield farming, liquidity pooling, all of which are functionally closed to native privacy coins.
This is not privacy theater. It is a pragmatic separation of concerns: the native FIRO chain provides privacy for transactions that need it, while rsFIRO provides liquidity access in the ecosystems where capital actually lives.
The censorship dynamics of rsFIRO are fundamentally different from those of native FIRO. Censoring or restricting a specific ERC-20 token is legally and technically much harder than delisting a native privacy coin from an exchange.
Blacklisting an ERC-20 token at the smart contract level is possible only if the contract includes an admin-controlled blocklist function, which a standard wrapped token contract need not have. Regulators would have to go after the token standard itself, which would have cascading implications across the entire Ethereum ecosystem. You cannot ban one ERC-20 without setting a precedent that threatens all ERC-20s. This is a fundamentally different regulatory surface area than asking Binance to delist a privacy coin, which has zero implications for Binance’s other listings.
Moreover, the largest exchanges are increasingly integrating their own chains directly into their apps. Binance users can access BNB Chain tokens natively. Coinbase users can access Base tokens natively. If rsFIRO has liquidity on PancakeSwap (BNB Chain) or a Uniswap pool on Base, it becomes accessible to the user bases of the world’s largest exchanges without ever requiring a formal listing or a compliance review of Firo’s privacy features.
One of the most underappreciated advantages of the wrapped token model is that providing liquidity to AMM pools requires no professional market makers. Any community member with rsFIRO and a paired asset (ETH, USDC, BNB) can provide liquidity to a Uniswap or PancakeSwap pool, earning trading fees in the process. This creates 24/7, always-on liquidity that doesn’t depend on a market maker’s willingness to serve a privacy coin, their continued solvency, or their contract with the project.
We have commitments from several community members to provide meaningful initial liquidity to bootstrap rsFIRO pools. This isn’t theoretical, it’s a concrete plan with committed participants. And unlike atomic swaps, which require active presence and counterparty matching, AMM liquidity is passive and persistent. Once deposited, it serves every trader, every hour of every day.
I wouldn’t be doing my job as Project Steward if I didn’t acknowledge what rsFIRO doesn’t solve.
Wrapping and unwrapping is transparent. When a user wraps FIRO into rsFIRO, that event is visible on both chains. When they unwrap, it’s visible again. The bridge itself does not provide privacy. This is a meaningful limitation for users who require end-to-end untraceability.
However, this limitation must be evaluated in context. As I noted above, THORChain swaps are transparent. Maya Protocol swaps are transparent. Serai DEX, when it eventually launches, will have transparent swap events on its own chain. Even atomic swaps leave visible footprints on both participating blockchains. No existing cross-chain liquidity solution provides privacy at the bridge or swap layer. Rosen Bridge is no worse in this regard than any of its competitors.
With good operational hygiene, using Firo’s Lelantus Spark privacy features before wrapping and after unwrapping, avoiding linking addresses, timing transactions thoughtfully, the privacy exposure from the bridging step can be meaningfully minimized.
Wrapping and unwrapping takes time. The Rosen Bridge architecture prioritizes security over speed, waiting for sufficient block confirmations before processing events. Large transfers may take longer as funds are moved from cold to hot wallets within the guard set. Firo’s ChainLocks (adapted from Dash’s) which provides single block finality for Firo blocks should help minimize the Firo-side confirmation delays, but some waiting is inherent in a multi-confirmation bridge design.
The guard set is federated, not fully permissionless. While anyone can become a Watcher, becoming a Guard requires acceptance by the existing guard set. This introduces a degree of trust in the federation’s composition, albeit with economic penalties (slashing) that align incentives. This is a meaningful distinction from fully trustless systems, though it’s worth noting that THORChain’s “permissionless” validator set has proven no more resilient in practice, given its insolvency episodes and governance crises.
The wisdom of this approach is not that Rosen Bridge is the single solution to all liquidity challenges. It’s that Rosen Bridge adds a powerful new option to an already diversified liquidity stack.
We maintain atomic swap capabilities through FiroDEX, Bison Wallet, and BasicSwap for users who prioritize trustless peer-to-peer exchange. We maintain listings on whatever centralized exchanges continue to support us. And now, through Rosen Bridge, we gain access to the deepest DeFi liquidity pools in existence Ethereum, BNB Chain, and potentially other EVM chains (Base is under research) through a mechanism that is resistant to the very regulatory pressures that are squeezing privacy coins everywhere else.
This is not a retreat from privacy. It’s a recognition that a privacy coin with no liquidity serves no one. The most sophisticated privacy technology in the world is worthless if nobody can acquire the coin to use it. Rosen Bridge ensures that no matter how aggressive regulators become with centralized exchange delistings, no matter how many DEX teams decide privacy coins are too hot to handle, there remains a decentralized, community-powered, censorship-resistant path to acquiring and trading FIRO.
In a world where the walls are closing in on privacy coins, we’re building a door. And for the privacy ecosystem as a whole, it might just be a blueprint worth following.
]]>This updates introduces Spark Address Message Signing & Verification, Improved Transaction Rebroadcasting, Mobile & Developer Improvements and bug fixes.
This release introduces the ability to sign and verify messages using Spark addresses. This is an important step for proving ownership of a Spark address without revealing any private information or making an on-chain transaction, useful for identity verification, proof-of-ownership, and building trust in peer-to-peer interactions while preserving privacy.
InstantSend-locked transactions are now periodically rebroadcast. This improves transaction reliability by reducing cases where valid transactions might not propagate fully across the network, particularly in scenarios involving temporary network disruptions or peer disconnections.
This update also brings improvements for mobile and light wallet integrations, with better performance and reliability for wallet in the backend. Developers and node operators gain richer Spark transaction data through enhanced RPC output.
And lastly Tor connectivity fix for Tor-only nodes, Qt6 UI fix for the Spark Names dialog, Various minor code cleanup and maintenance changes.
You can check the whole change logs at: https://github.com/firoorg/firo/releases/tag/v0.14.15.3
]]>Congratulations to quadriocellata and Ammortel, who have each won $50 USD worth of FIRO.
The prizes will be sent directly to their Spark addresses, as provided in their AnonBazaar listings.
This weekly lucky draw is part of an ongoing initiative that will run for approximately three months, aimed at encouraging more real-world listings and usage of FIRO on AnonBazaar. Winners will not be eligible to be selected again within the same month (30 days from the start of the campaign), but eligibility will reset each month, allowing past winners to be selected again in future draws.
Thank you to everyone participating, and congratulations again to our Week 1 winners. More draws coming soon.
Check out the winner selection process HERE
]]>