Website catalogue: 151 chains. Current AI connection: 14 chains; approved accounts only.

Connect your AIConnect

Layer 1 blockchain

Firo ticker FIRO

  • No public-data lookups yet
  • 6 reviewed developments
  • 30 cited sources

Summary

GPU miners run FiroPoW (a ProgPoW 0.9.4 variant, live since 26 October 2021) to produce blocks targeting 2.5 minutes. Masternodes, each backed by 1,000 FIRO of collateral, form rotating quorums that threshold-sign ChainLocks (400 members, 60% threshold) and InstantSend locks. Value sits either in transparent outputs, inherited from the Bitcoin Core code base, or in Lelantus Spark coins, whose spends use zero-knowledge proofs to hide sender, recipient and amount, with tags that block double spends. Since block 958,655 consensus requires each 6.25 FIRO block subsidy to pay 70% to a masternode, 15% to a development fund and 10% to a community fund, leaving 5% plus transaction fees to the miner. 12348101113

Design

System
Layer 1 blockchainProof-of-work base chain (formerly Zcoin, renamed in 2020 with no chain swap) with a masternode quorum layer that locks blocks and transactions. It is not a rollup or a sidechain, which matches the package hint.
Settlement family
Bitcoin family
Scarce resource
Work (proof of work)
State model
Mixed
Finality
Checkpointed
Who makes blocks
GPU miners, mostly through pools, propose blocks by FiroPoW proof of work. Masternodes do not propose blocks; quorums drawn from the deterministic masternode list sign ChainLocks and InstantSend locks. Running a masternode needs 1,000 FIRO collateral and a server with a static IPv4 address.
Fork choice
Nodes follow the valid chain with the most accumulated work until a ChainLock signature arrives; the node then invalidates competing blocks at that height and their descendants, even if that branch has more work. Firo says transactions can be treated as secure after one ChainLocked block. When no lock exists, the most-work rule decides (an inference from the reference code).

Qualifications

Tradeoffs

This view follows one way of thinking about design priorities, often called the blockchain trilemma. The design-priorities lesson sets out the counter-view. Read the design-priorities lesson.

Emphasizes
Security and Decentralization Contested
Gives up
Base-layer throughput: 2.5-minute blocks, a 2 MB block limit, and Spark transfers that carry zero-knowledge proofs. It also gives up simple public supply auditing inside the Spark pool, and some decentralization of settlement: once a ChainLock forms, the final say moves from open GPU mining to a collateral-gated masternode set, which also receives 70% of new coins while miners receive 5% plus fees.Privacy is a separate goal, not a trilemma corner. Both corners are contested. ChainLocks came in January 2021 after a 51% attack and stop rented hashrate rewriting locked blocks, but add the assumption that at least 60% of a selected quorum signs honestly. In August 2026 a researcher showed multi-input Spark spends could forge coins; Firo reports no inflation beyond about 200 FIRO the researcher created as proof, and fixed it by hard fork on 4 September 2026.
Full node at home
Practical at home 8No separate full-node hardware guide was found. Firo's masternode guide, which runs the same node software, lists 1 or 2 vCPUs, 2 GB RAM plus 2 GB swap and 35 GB disk, and gives the chain size as 9.2 GB in January 2026. A home node can check ChainLock and InstantSend signatures but cannot sign them without collateral and a public server.
Throughput claims
No classified figure recorded

Scaling layers

No scaling layer recorded in this profile.

Capabilities

Capabilities of Firo: how each one is provided, or its research status
CapabilityHow it is providedNotes and sources
Account abstractionStructured assessment pendingNot yet assessed for any chain.
Atomic swapsIndependent softwareLimited scopeIndependent software, limited: BasicSwap, a non-custodial swap app its docs call beta, lists FIRO; no first-party implementation is cited. Its code records Firo as having no absolute or relative timelocks, so FIRO swaps use adaptor signatures: transparent FIRO is locked in a shared output and the timelocked refund path sits on the other coin's chain, which must support scripts. Limits: only transparent FIRO is swapped, the reference node never activates BIP 65 on mainnet, and Spark-native swaps are a roadmap goal. 1719202122
Authenticated data publicationUnknownNot yet assessed under this row's current definition.
Light clientsUnknownNot yet assessed under the current definitions; light wallets exist (Electrum-Firo, the Campfire app), but reviewed sources do not document what they verify themselves versus what they accept from servers, especially for Spark data, so no light-verification method is described. 929
Native staking or delegationStructured assessment pendingNot yet assessed for any chain.
On-chain governanceStructured assessment pendingNot yet assessed for any chain.
Parallel executionStructured assessment pendingNot yet assessed for any chain.
Payment or state channelsUnknownNo source was cited for absence, so the rule that absence needs a source makes this unknown. Earlier finding: no channel layer was found in reviewed sources, and Firo relies on InstantSend locks for fast payments; absence was not exhaustively verified.
Programmable spendingPartial (layer not stated) Earlier definitionTransparent outputs use Script inherited from Bitcoin Core (for example multisignature), but the reference code never activates the absolute-timelock rule on mainnet, and BasicSwap's settings record no relative timelocks either. Spark spends use fixed proof-checked formats, not general scripts, and there is no smart-contract layer. The Spark paper describes multisignature and view-key features; deployed wallet support for Spark multisignature was not verified. 121321
Protocol-verified messagingStructured assessment pendingNot yet assessed for any chain.
Reversible transfers or recoveryUnknownNot yet assessed under this row's current definition.
RollupsUnknownNo source was cited for absence, so the rule that absence needs a source makes this unknown. Earlier finding: no rollup anchored to Firo was found in reviewed sources; absence was not exhaustively verified.
Shielded transfersStructured assessment pendingNot yet assessed for any chain.
Signed partial offersUnknownNot yet assessed under this row's current definition.
Reading these values
How this feature is provided
Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
Structured assessment pending
The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
Unknown
The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
Earlier definition
Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
Reading across rows
The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.

Definitions, schema version and review history

Ecosystem & custody

Ecosystem products for Firo
Product typeStatusNotes and sources
Automated market makersNone foundFiro has no contract layer, so no AMM runs on Firo itself. Firo announced on 15 September 2026 that pools for rsFIRO, a bridged token backed by FIRO held by Rosen Bridge, are active on Uniswap (Ethereum), PancakeSwap (BNB Chain) and Mew Finance (Ergo); those pools run on other chains and trade the bridged token, not native FIRO, so they are recorded under the bridge row. Liquidity depth was not measured. Risk: rsFIRO is only as good as the Rosen Bridge guards holding the backing FIRO, and Firo says rsFIRO transfers and trades are public, with no Spark privacy. 16 As of Sep 27, 2026.
Issuer-native stablecoinsNone foundFiro has no token layer today; user-issued private assets (Spark Assets) are a roadmap item. No stablecoin on Firo was found. 7 As of Sep 27, 2026.
Algorithmic stablecoinsUnknownNo source was cited for absence, so the rule that absence needs a source makes this unknown. Earlier finding: none identified; without a token layer there is nothing to issue one on. Absence was not exhaustively verified. As of Sep 27, 2026.
BridgesThinRosen Bridge (rsFIRO)Since September 2026 FIRO can be bridged to Ethereum, BNB Chain and Ergo as rsFIRO through Rosen Bridge, which uses Ergo for coordination. Rosen's own home page still listed a Firo bridge under planned work at review. Separately, Firo's April 2025 delisting notice said Binance would keep honouring one-to-one redemptions of its BNB Chain FIRO token into native FIRO; whether that still holds was not verified. Risk: Native FIRO sits in bridge reserves controlled by Rosen guards (10 at launch, per Firo) under an m-of-n multisignature or threshold scheme; enough colluding or compromised guards could take it. rsFIRO is public, not private, and Firo warns against sending it to native FIRO exchange addresses. 16171823 As of Sep 27, 2026.
Block explorersEstablished in the ecosystemFiro Insight (explorer.firo.org), Chainz (CryptoID)Both show blocks and transparent activity; Firo's Insight API also reports whether a block is ChainLocked. Neither can show Spark senders, recipients, amounts or balances. A public explorer's view is provider data, not independent validation. 12242526 As of Sep 27, 2026.
Hardware walletsThinLedger (via Electrum-Firo), Trezor (via third-party apps)See custody rows: both vendors list Firo only through third-party wallet software, and no reviewed source shows hardware signing of Spark private transactions. 272830 As of Sep 27, 2026.

Hardware-wallet custody

Hardware-wallet custody for Firo
Device makerStatusWhat users can and cannot do
LedgerThrough an intermediaryElectrum-Firo (Firo's light desktop wallet)Same as native: NoCan: Connect a Ledger device to Electrum-Firo and sign FIRO transactions on the device, as Ledger's Firo page describes
Cannot: Manage FIRO in Ledger Wallet (formerly Ledger Live); Ledger's page sends users to Electrum-Firo instead
Cannot: Send to an exchange address (the EX-prefixed kind) from a hardware wallet in Electrum-Firo; its release notes list this as a known issueElectrum-Firo release notes describe its Spark support as recognising and spending transparent outputs created by Spark spends. No reviewed source says a Ledger can hold or send Spark (private) FIRO. 92730 As of Sep 27, 2026.
TrezorThrough an intermediaryThird-party wallet apps (Trezor's Firo page names none; Firo lists Electrum-Firo as its hardware-wallet light wallet)Same as native: NoCan: Keep FIRO keys on Trezor Safe 3, Safe 5 or Safe 7, the models Trezor's Firo page lists
Can: Connect the device to a compatible third-party wallet app to send and receive FIRO
Cannot: Manage FIRO in Trezor Suite, which Trezor's page says does not support a Firo wallet interface
Cannot: Send to an exchange address (the EX-prefixed kind) from a hardware wallet in Electrum-Firo; its release notes list this as a known issueElectrum-Firo release notes include Trezor-specific fixes, so it is one working path, but Trezor's page names no wallet and does not say whether private Spark transactions are supported; treat hardware custody as covering transparent FIRO only until verified. 92830 As of Sep 27, 2026.

Public data

iKnow Blockchain has no public-data lookups for Firo yet. This is a limit of the service, not a statement about the network.

Public-data lookups for Firo
LookupStatusWhat it covers and its limits
Address or accountNot available yetPublic-data lookups for this chain are not built yet.
Tokens and assetsNot available yetPublic-data lookups for this chain are not built yet.
NFTsNot available yetPublic-data lookups for this chain are not built yet.
TransactionsNot available yetPublic-data lookups for this chain are not built yet.

A lookup covers one address or transaction from one provider. It is never a complete wallet, and an error or private value is reported as unknown, not zero. About public data · Connect your AI

Sourced developments

Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.

Publication date · newest first

Topics your AI can explain

Your AI can explain these topics for Firo through the connection, with sources.

Known gaps

What this profile's review did not establish:

Sources

Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.

All 30 sources were checked in the last 30 days.

  1. Firo reference node: src/chainparams.cpp (master) (external site)Firo developers (firoorg) · retrieved
  2. Firo reference node: src/validation.cpp (master) (external site)Firo developers (firoorg) · retrieved
  3. Firo reference node: src/pow.cpp (master) (external site)Firo developers (firoorg) · retrieved
  4. Firo reference node: src/llmq/quorums_chainlocks.cpp (master) (external site)Firo developers (firoorg) · retrieved
  5. Firo releases (external site)Firo developers (firoorg) · retrieved
  6. Firo FAQ (external site)Firo · retrieved
  7. Firo roadmap (external site)Firo · retrieved
  8. Firo masternode setup guide (external site)Firo · retrieved
  9. Firo wallet downloads (external site)Firo · retrieved
  10. ChainLocks activated on Firo mainnet (28 January 2021) (external site)Firo · retrieved
  11. Firo v0.14.9.0: FiroPoW and InstantSend (1 October 2021) (external site)Firo · retrieved
  12. Lelantus Spark is live (18 January 2024) (external site)Firo · retrieved
  13. Lelantus Spark: Secure and Flexible Private Transactions (IACR ePrint 2021/1173) (external site)Aram Jivanyan and Aaron Feickert · retrieved
  14. Spark vulnerability mitigated (13 August 2026) (external site)Firo · retrieved
  15. Firo v0.14.18.0 released: Spark functionality to be fully restored (27 August 2026) (external site)Firo · retrieved
  16. FIRO goes multichain: rsFIRO is live on Rosen Bridge (15 September 2026) (external site)Firo · retrieved
  17. Rosen Bridge: Concept and Assumptions (external site)Rosen Bridge · retrieved
  18. Binance delisting of FIRO (16 April 2025) (external site)Firo · retrieved
  19. BasicSwap DEX (external site)BasicSwap · retrieved
  20. BasicSwap documentation: introduction (external site)BasicSwap · retrieved
  21. BasicSwap source: basicswap/interface/firo/chainparams.py (master) (external site)The Basicswap developers · retrieved
  22. BasicSwap source: basicswap/chainparams.py (master) (external site)The Basicswap developers · retrieved
  23. Rosen Bridge (external site)Rosen Bridge · retrieved
  24. Firo Insight block explorer (external site)Firo · retrieved
  25. Firo Insight API status (external site)Firo · retrieved
  26. Firo Blockchain Explorer (external site)CryptoID (Chainz) · retrieved
  27. Firo wallet | Ledger (external site)Ledger · retrieved
  28. Safe & secure Firo wallet | Trezor (external site)Trezor · retrieved
  29. Electrum-Firo repository (external site)Firo developers (firoorg) · retrieved
  30. Electrum-Firo releases (external site)Firo developers (firoorg) · retrieved

Report an error

Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.

Report an error about FiroCorrections log

Funding disclosure

Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding