About FireWatch
After the Drift incident era, Ferno decided to open its monitoring technology and make it
available to anyone operating on Solana. DeFi can feel scary because teams watch portfolio
moves all day while protocol risk is often treated as unavoidable.
FireWatch is built on a different assumption: protocol risk is not fully avoidable, but a lot
can be prevented when evidence is fast, structured, and actionable. That is exactly what
FireWatch is for.
What We Track
Program and governance signals
- Program deploy, upgrade, finalize, and loader migration events.
- IDL initialize, update, authority change, immutable, resize, and close actions.
- Curated admin and high-impact instruction paths when known.
- Unknown instruction alerts on protocols with parsed instructions.
Operational risk signals
- Squads proposal lifecycle and vault/config execution traces.
- Wallet and amount-trigger alerts for configured monitors and thresholds.
- .sol domain ownership and update events tied to monitored entities.
- Protocol-linked event history with proof-first event pages.
Score Model
FireWatch score is not an audit badge, token rating, or guarantee of safety. It is a live
evidence summary showing how much critical proof is attached to a watched project and whether
that evidence has been reviewed.
Grade Bands
A 90-100 No or very low unresolved critical evidence.
B 75-89 Some critical evidence exists, but current unresolved weight is limited.
C 60-74 Material critical evidence exists and should be inspected before relying on the project.
D 40-59 Heavy unresolved critical evidence. The proof trail matters more than the letter.
F 0-39 Severe unresolved evidence. Treat the project as requiring immediate review.
What Counts As Proof
- Transactions that changed a watched program, IDL, multisig, or admin path.
- Decoded instructions with critical or high-impact tags.
- Unknown instructions on protocols with parsed instructions.
- Amount-trigger and wallet movement signals when configured.
- Signer and governance history linked to the protocol.
How To Read A Project Score
- Start with grade and unresolved critical count.
- Open evidence links to inspect exact events behind the score.
- Use per-program proof counts to isolate concentration of risk.
- Verify source events on Solana Explorer from linked transactions.
Score Limits
FireWatch can only score what it observes and understands. A clean score may still miss
off-chain risk, economic design risk, hidden dependencies, key management issues, oracle
weakness, or brand-new behavior that has not been decoded yet.
Infra
For on-demand response workflows, FireWatch can run on Ferno’s dedicated stack: DoubleZero
shred stream ingestion, custom send paths, and a multi-tenant transaction sender targeting
near-zero slot delay inclusion.
Open Source And Contribution
FireWatch is open source. We want protocol teams and operators to improve coverage with us.
- Add or refine curated protocol definitions in
backend/src/protocols.rs (program IDs, instruction coverage, critical paths). - If needed, update platform source data in
backend/data/platform_registry_snapshot.json. - Run checks before opening a PR:
cd backend && cargo test, cd frontend && npm run check.