UNOFFICIAL COMMUNITY ARCHIVE
Discover production integrations, apps built with Fermah, and creations from the Fermafia. Every relationship here carries a source and the date it was checked.
TEAM & BACKINGRecent ecosystem notes
Latest source check
On October 26, @7wealthh reported Fermah Pay Tranche 1 on Stellar testnet. Public repository evidence records a replay of 98 settled charges with no repeat debit, plus sponsored buyer network fees, recurring mandates and an x402 facilitator interface.
Testnet implementation and recorded cases; no production Mainnet release is established.
Fermah described routing the same computation differently depending on where its output will be consumed: locally, by the next action, or across future sequences. The longer the result must remain composable, the more durable its execution artifact needs to be.
Fermah shared Vanishree Rao's announcement of phased admission: the first 10,000 had been admitted on October 19, with more cohorts to follow. This is an admission milestone, not an active-user count.
External site. X and Discord sign-in are requested there, not on Atlas.
FERMAH-REPORTED FIGURES, NOT ATLAS TELEMETRY · CHECKED 2026-10-24 · fermah.xyz ↗
The October 13 post discusses 100,000+ resolved markets; the homepage reports 1M+. The sources do not define a shared reporting period or explain the relationship between these figures. Atlas keeps the dated claims separate rather than treating one as a correction or a growth series.
October 13 post ↗On October 15, Fermah said queueing and routing dominated the interval between trigger intake and compute start across 2.8M+ production proofs. The post does not publish a millisecond breakdown or an end-to-end latency guarantee.
October 15 post ↗What Fermah is
Every smart contract ever written is reactive: it reads a condition and emits a value, then waits for a human, a server or a cron job to do the next thing. Fermah Kernel — which the team calls the Protocol Agency Engine — turns “if this verifiable thing is true, do that” into an on-chain primitive: observe the event, run the logic in a sandboxed container, settle the verified result back on-chain. Two products run on it in production today. Froben is the universal proof market, live on mainnet, with ZKsync Era named as a paying customer. Flashcast Social turns any topic into a prediction market in a second and resolves it automatically, with no committee and no dispute window. The current Fermah docs separately list Marina as privacy-preserving data infrastructure. Fermah Pay now has a public Stellar testnet implementation for prepaid USDC billing, sponsored submission, recurring mandates and x402 settlement. Read the Pay testnet update →
Read it at fermah.xyz and docs.fermah.xyz.
Inside Kernel
An illustrative Froben workflow, based on Fermah's product and execution descriptions. Not live network telemetry.
A protocol submits a proof request and its requirements.
The workflow obtains the inputs needed for that proof.
The request is allocated to a compatible prover.
The prover generates the proof; the workflow verifies the result.
The verified result is returned for onchain consumption.
A consuming protocol can use that result as input to its next action.
An illustrative Flashcast workflow. The condition and source rules are defined before resolution; this is not a live market or a betting interface.
A market reaches its defined condition or deadline.
The workflow fetches the sources specified by the market.
The required resolution work is coordinated for execution.
The resolution logic evaluates the evidence against the condition.
The resulting outcome is delivered onchain for settlement.
The result can be consumed by a subsequent protocol action.
Consumption horizon
Fermah describes identical computation taking different execution paths as its output serves different consumers. Its October 24 post calls this the consumption horizon.
This is Fermah's stated routing principle, drawn from its discussion of 2.8M+ production proofs. It is not a universal routing rule, a deployment command or a latency guarantee; the post does not specify detailed security assumptions or selection thresholds.
Oct 24, 2026 post ↗Team & backing
Founder & CEO
@vanishree_raoCryptographer with a UCLA PhD. Previously Lead Cryptographer at O(1) Labs, the team behind Mina.
Fermah release ↗ · The Block ↗ · Sep 17, 2024
CTO · appointed March 30, 2026
LinkedInAt Fermah since its earliest days. Helped build the Proof Market, telemetry and Workflow Execution Engine.
CTO announcement ↗ · Mar 30, 2026
$5.2M
SEED ROUND
Co-led by
a16z CSX & Lemniscap
Other participants named in the release
Named angels
The Block ↗ · Fermah release ↗ · Sep 17, 2024
Funding names reflect the 2024 seed announcement, not ecosystem partnerships. Checked .
Ecosystem graph
Solid lines show live relationships and docs-listed products. Dashed lines show testnet, announced, historical or open entries.
From the archive
WEEK 25
The most recent week the team published, rebuilt from the official announcement. Filled square means selected, outline means honourable mention.
SELECTED · 5
HONOURABLE MENTIONS · 18
Sources
| Relationship | Status | Source | Checked |
|---|
