Skip to content
PrivacyAurelia

Fathom Privacy

Fictional privacy protocol developing shielded transfers with a public research roadmap.

Last verified update 10 Sept 2026 (3 days ago)Data last checked today
Confidence Medium · data 100%
Compare
Share on X
Embed Ship Score badge
Fathom Privacy Ship Score badge
[![Ship Score](https://shiptrace.vercel.app/badge/fathom-privacy.svg)](https://shiptrace.vercel.app/projects/fathom-privacy)

Paste into a README or docs page. The badge updates automatically and links back here.

Ship Score

Score breakdown

Ship Score · formula v1.0.0

60–79 · Mostly documented delivery

This score measures documented delivery, not investment quality.

Confidence Medium · data 100%Calculated 13 Sept 2026 03:00 UTC
Milestone delivery × 0.40
58

Importance-weighted credit for approved milestones whose deadlines have passed.

Development continuity × 0.20
59

Release/tag cadence and weekly activity continuity from public repositories; not raw commit counts.

Product availability × 0.15
93

Rolling success rate of timestamped checks against explicitly listed product endpoints.

Transparency × 0.15
68

Dated roadmap updates, published explanations, accessible documentation and change disclosure.

Evidence quality × 0.10
72

Hierarchy-weighted quality and completeness of accepted evidence.

Show exact calculation
  1. Formula v1.0.0: delivery × 0.4 + development × 0.2 + availability × 0.15 + transparency × 0.15 + evidence × 0.1.
  2. Delivery: 3 approved past-deadline milestone(s) counted (importance weights core 3, major 2, minor 1); 0 disputed excluded; 0 cancelled-with-explanation shown separately; 0 awaiting review.
  3. • Shielded transfers on testnet: Shipped after deadline → credit 70 × weight 3
  4. • Audit report publication: Shipped after deadline → credit 70 × weight 2
  5. • Browser extension: No qualifying evidence found → credit 0 × weight 1
  6. Delivery component = 58.
  7. Development continuity = 59 (active weeks, releases/tags in 90d, last push recency).
  8. Product availability = 93 (rolling success rate across approved endpoints, last 30 checks each).
  9. Transparency = 68 (dated roadmap updates, explanations, public docs, change disclosure).
  10. Evidence quality = 72 (hierarchy-weighted, completeness-adjusted).
  11. Total = 66.

Read the full methodology. Snapshots are stored with raw component values and are never rewritten.

Score history

6 stored snapshots

Stored snapshots with their formula version. Gaps mark periods with insufficient data. Historical snapshots are never rewritten.
Ship Score snapshots
DateTotalFormula
16 Apr 2026Insufficient datav0.9.0
16 May 2026Insufficient datav0.9.0
15 Jun 2026Insufficient datav1.0.0
15 Jul 202662v1.0.0
14 Aug 202662v1.0.0
13 Sept 202666v1.0.0

Roadmap

Timeline of milestones

5 commitments recorded from cited public sources, ordered by deadline.

  1. Shielded transfers on testnet

    deadline 6 May 2026 · 4 months ago · delivered 16 May 2026

    Shipped
  2. Audit report publication

    deadline 25 Jun 2026 · 3 months ago · delivered 25 Jun 2026

    Shipped
  3. Browser extension

    deadline 15 Jul 2026 · 2 months ago

    No evidence
  4. Today · 13 Sept 2026
  5. Viewing keys specification

    deadline 27 Sept 2026 · in 13 days

    Planned
  6. Mainnet shielded pool

    deadline 2 Nov 2026 · in 49 days

    Delayed

Open commitments

Upcoming commitments

Deadlines that have not passed. Community evidence can be submitted at any time.

DelayedCore milestone

Mainnet shielded pool

Commitment (paraphrase) · Launch the shielded pool on mainnet.

Evidence room
Claimed
16 Apr 2026
Deadline
2 Nov 2026 (in 49 days)
originally 14 Aug 2026
Delivered
Evidence
1 accepted
Status history (3)
  1. Created →PlannedModerator conclusion

    Commitment recorded from cited source (Fathom Privacy roadmap), accessed 2026-04-16.

    Mara Okafor · 17 Apr 2026 09:00 UTC · audit ST-FD7F3481

  2. PlannedIn progressModerator conclusion

    Project published a dated progress update.

    Mara Okafor · 25 Jul 2026 16:00 UTC · audit ST-FD7F3482

  3. In progressDelayedModerator conclusion

    Deadline passed; project published an updated timeline (new deadline 2026-11-02).

    Mara Okafor · 15 Aug 2026 23:00 UTC · audit ST-FD7F3483 · 1 evidence ref

Verified from public evidence

Shipped items

2 milestones verified as shipped or partially shipped.

ShippedCore milestone

Shielded transfers on testnet

Commitment (paraphrase) · Deploy shielded transfers to the public testnet.

Evidence room
Claimed
27 Dec 2025
Deadline
6 May 2026 (4 months ago)
Delivered
16 May 2026
Evidence
1 accepted
Status history (4)
  1. Created →PlannedModerator conclusion

    Commitment recorded from cited source (Fathom Privacy roadmap), accessed 2025-12-27.

    Mara Okafor · 28 Dec 2025 09:00 UTC · audit ST-4441B344

  2. PlannedIn progressModerator conclusion

    Project published a dated progress update.

    Mara Okafor · 2 Mar 2026 16:00 UTC · audit ST-4441B345

  3. In progressSubmitted for reviewAutomated observation

    Evidence submitted for review.

    SHIPTRACE automated intake · 15 May 2026 15:00 UTC · audit ST-4441B346

  4. Submitted for reviewShippedModerator conclusion

    Verified from public evidence: primary source matches the commitment scope.

    Mara Okafor · 16 May 2026 15:00 UTC · audit ST-4441B347 · 1 evidence ref

ShippedMajor milestone

Audit report publication

Commitment (paraphrase) · Publish the external audit report for the circuits.

Evidence room
Claimed
17 Mar 2026
Deadline
25 Jun 2026 (3 months ago)
Delivered
25 Jun 2026
Evidence
1 accepted
Status history (4)
  1. Created →PlannedModerator conclusion

    Commitment recorded from cited source (Fathom Privacy roadmap), accessed 2026-03-17.

    Mara Okafor · 18 Mar 2026 09:00 UTC · audit ST-2D092C8E

  2. PlannedIn progressModerator conclusion

    Project published a dated progress update.

    Mara Okafor · 6 May 2026 16:00 UTC · audit ST-2D092C8F

  3. In progressSubmitted for reviewAutomated observation

    Evidence submitted for review.

    SHIPTRACE automated intake · 24 Jun 2026 15:00 UTC · audit ST-2D092C90

  4. Submitted for reviewShippedModerator conclusion

    Verified from public evidence: primary source matches the commitment scope.

    Mara Okafor · 25 Jun 2026 15:00 UTC · audit ST-2D092C91 · 1 evidence ref

Neutral record

Delayed, no-evidence, disputed and cancelled items

A missed deadline or missing evidence is recorded as such. It is not a conclusion about the project's intent.

No evidenceMinor milestone

Browser extension

Commitment (paraphrase) · Ship a browser extension for shielded transfers.

Evidence room
Claimed
26 Apr 2026
Deadline
15 Jul 2026 (2 months ago)
Delivered
Evidence
0 accepted
Original source· accessed 27 Apr 2026(opens in a new tab)No qualifying evidence found as of 18 Jul 2026

Moderator note · No qualifying evidence found as of the last check.

Status history (2)
  1. Created →PlannedModerator conclusion

    Commitment recorded from cited source (Fathom Privacy roadmap), accessed 2026-04-26.

    Mara Okafor · 27 Apr 2026 09:00 UTC · audit ST-C30D469C

  2. PlannedNo evidenceModerator conclusion

    No qualifying evidence found as of 2026-07-18.

    Mara Okafor · 18 Jul 2026 23:00 UTC · audit ST-C30D469D

DelayedCore milestone

Mainnet shielded pool

Commitment (paraphrase) · Launch the shielded pool on mainnet.

Evidence room
Claimed
16 Apr 2026
Deadline
2 Nov 2026 (in 49 days)
originally 14 Aug 2026
Delivered
Evidence
1 accepted
Status history (3)
  1. Created →PlannedModerator conclusion

    Commitment recorded from cited source (Fathom Privacy roadmap), accessed 2026-04-16.

    Mara Okafor · 17 Apr 2026 09:00 UTC · audit ST-FD7F3481

  2. PlannedIn progressModerator conclusion

    Project published a dated progress update.

    Mara Okafor · 25 Jul 2026 16:00 UTC · audit ST-FD7F3482

  3. In progressDelayedModerator conclusion

    Deadline passed; project published an updated timeline (new deadline 2026-11-02).

    Mara Okafor · 15 Aug 2026 23:00 UTC · audit ST-FD7F3483 · 1 evidence ref

Automated observation

Development pulse

Active weeks (of 12)
7
Releases / tags (90d)
1 / 0
Latest release
v0.5.0
Last push
12 days ago
Default branch
main
Retrieved
13 Sept 2026 06:00 UTC

Repository activity is an observation, not proof of delivery. Commit counts alone never verify a milestone.

Automated observation

Product status

One failed check never proves abandonment. Availability uses a rolling window with neutral labels.

Sources

Evidence feed

Accepted evidence is verified; pending community submissions are visibly unverified until a moderator decides.

Submit evidence
Verified from public evidenceTier 3 · Official documentation / announcementModerator

Mainnet timeline revised

Dated post explaining additional audit rounds and a new date.

Submitted by
Mara Okafor
Review
14 Aug 2026 16:00 UTC
Community
2 support 0 challenge

Moderator conclusion · Source is a public, dated record matching the commitment scope.

Audit record ST-0117A96F · database identifier, not a blockchain claim

Verified from public evidenceTier 3 · Official documentation / announcementModerator

Audit report published

Report linked from the docs with a date.

Submitted by
Mara Okafor
Review
27 Jun 2026 16:00 UTC
Community
2 support 0 challenge

Moderator conclusion · Source is a public, dated record matching the commitment scope.

Audit record ST-30A1A17C · database identifier, not a blockchain claim

Verified from public evidenceTier 2 · Repository release / tagModerator

fathom-protocol v0.4.0

Release with testnet deployment details.

Submitted by
Mara Okafor
Review
18 May 2026 16:00 UTC
Community
2 support 0 challenge

Moderator conclusion · Source is a public, dated record matching the commitment scope.

Audit record ST-97C6EF32 · database identifier, not a blockchain claim

Audit trail

Change log

Every verified status change, new commitment, deadline change and accepted evidence for this project.

  1. Deadline changed
  2. Delayed
  3. Evidence added
  4. New commitment
  5. No evidence
  6. Evidence added
  7. Shipped
  8. Evidence added
  9. Shipped
  10. New commitment
  11. New commitment
  12. New commitment
  13. New commitment

Corrections

Methodology and correction process

Statuses are set only by moderators, with a written reason and evidence references, following the published methodology. Automated checks create observations, never conclusions.

Project claims, community submissions, automated observations and moderator conclusions are labelled separately throughout this page.

Believe something here is wrong? Anyone — including project representatives — can request a correction. Prior decisions remain in the audit history.

Shipped Partially shipped Delayed No evidence Disputed Cancelled