Skip to content
SHIPTRACE
InfrastructureMulti-chain

Keelstone Oracle

Fictional oracle network with a long public delivery record and detailed release notes.

Website(opens in a new tab)Docs(opens in a new tab)Repository(opens in a new tab)
Last verified update 12 Sept 2026 (yesterday)Data last checked today
Confidence Medium · data 100%
Compare
Share on X
Embed Ship Score badge
Keelstone Oracle Ship Score badge
[![Ship Score](https://shiptrace.vercel.app/badge/keelstone-oracle.svg)](https://shiptrace.vercel.app/projects/keelstone-oracle)

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

80–100 · Consistent 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
90

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

Development continuity × 0.20
100

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

Product availability × 0.15
100

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

Transparency × 0.15
100

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

Evidence quality × 0.10
83

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: 4 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. • Price feeds on mainnet: Shipped on time → credit 100 × weight 3
  4. • Verifiable randomness: Shipped on time → credit 100 × weight 2
  5. • Cross-chain messaging: Shipped after deadline → credit 70 × weight 3
  6. • Node operator dashboard: Shipped on time → credit 100 × weight 1
  7. Delivery component = 90.
  8. Development continuity = 100 (active weeks, releases/tags in 90d, last push recency).
  9. Product availability = 100 (rolling success rate across approved endpoints, last 30 checks each).
  10. Transparency = 100 (dated roadmap updates, explanations, public docs, change disclosure).
  11. Evidence quality = 83 (hierarchy-weighted, completeness-adjusted).
  12. Total = 94.

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 202692v1.0.0
15 Jul 202694v1.0.0
14 Aug 202694v1.0.0
13 Sept 202694v1.0.0

Roadmap

Timeline of milestones

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

  1. Price feeds on mainnet

    deadline 27 Dec 2025 · 9 months ago · delivered 17 Dec 2025

    Shipped
  2. Verifiable randomness

    deadline 17 Mar 2026 · 6 months ago · delivered 12 Mar 2026

    Shipped
  3. Cross-chain messaging

    deadline 15 Jun 2026 · 3 months ago · delivered 17 Jun 2026

    Shipped
  4. Node operator dashboard

    deadline 14 Aug 2026 · 31 days ago · delivered 11 Aug 2026

    Shipped
  5. Today · 13 Sept 2026
  6. Low-latency feeds

    deadline 19 Sept 2026 · in 5 days

    In progress
  7. Proof-of-reserve feeds

    deadline 7 Nov 2026 · in 54 days

    Planned

Open commitments

Upcoming commitments

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

In progressMajor milestone

Low-latency feeds

Commitment (paraphrase) · Release sub-second feeds for selected markets.

Evidence room
Claimed
15 Jun 2026
Deadline
19 Sept 2026 (in 5 days)
Delivered
—
Evidence
1 accepted
Original source· accessed 16 Jun 2026(opens in a new tab)
Status history (2)
  1. Created →PlannedModerator conclusion

    Commitment recorded from cited source (Keelstone Oracle roadmap), accessed 2026-06-15.

    Mara Okafor · 16 Jun 2026 09:00 UTC · audit ST-43669020

  2. Planned →In progressModerator conclusion

    Project published a dated progress update.

    Mara Okafor · 10 Sept 2026 14:00 UTC · audit ST-43669021 · 1 evidence ref

PlannedMajor milestone

Proof-of-reserve feeds

Commitment (paraphrase) · Publish proof-of-reserve feeds for two custodians.

Evidence room
Claimed
4 Aug 2026
Deadline
7 Nov 2026 (in 54 days)
Delivered
—
Evidence
0 accepted
Original source· accessed 5 Aug 2026(opens in a new tab)
Status history (1)
  1. Created →PlannedModerator conclusion

    Commitment recorded from cited source (Keelstone Oracle roadmap), accessed 2026-08-04.

    Mara Okafor · 5 Aug 2026 09:00 UTC · audit ST-FD67C9D4

Verified from public evidence

Shipped items

4 milestones verified as shipped or partially shipped.

ShippedCore milestone

Price feeds on mainnet

Commitment (paraphrase) · Launch price feeds on mainnet with published update thresholds.

Evidence room
Claimed
9 Aug 2025
Deadline
27 Dec 2025 (9 months ago)
Delivered
17 Dec 2025
Evidence
1 accepted
Original source· accessed 10 Aug 2025(opens in a new tab)
Status history (4)
  1. Created →PlannedModerator conclusion

    Commitment recorded from cited source (Keelstone Oracle roadmap), accessed 2025-08-09.

    Mara Okafor · 10 Aug 2025 09:00 UTC · audit ST-9A98AC38

  2. Planned →In progressModerator conclusion

    Project published a dated progress update.

    Mara Okafor · 18 Oct 2025 16:00 UTC · audit ST-9A98AC39

  3. In progress →Submitted for reviewAutomated observation

    Evidence submitted for review.

    SHIPTRACE automated intake · 16 Dec 2025 15:00 UTC · audit ST-9A98AC3A

  4. Submitted for review →ShippedModerator conclusion

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

    Mara Okafor · 17 Dec 2025 15:00 UTC · audit ST-9A98AC3B · 1 evidence ref

ShippedMajor milestone

Verifiable randomness

Commitment (paraphrase) · Release a verifiable randomness service.

Evidence room
Claimed
28 Oct 2025
Deadline
17 Mar 2026 (6 months ago)
Delivered
12 Mar 2026
Evidence
1 accepted
Original source· accessed 29 Oct 2025(opens in a new tab)
Status history (4)
  1. Created →PlannedModerator conclusion

    Commitment recorded from cited source (Keelstone Oracle roadmap), accessed 2025-10-28.

    Mara Okafor · 29 Oct 2025 09:00 UTC · audit ST-3FCABD6D

  2. Planned →In progressModerator conclusion

    Project published a dated progress update.

    Mara Okafor · 6 Jan 2026 16:00 UTC · audit ST-3FCABD6E

  3. In progress →Submitted for reviewAutomated observation

    Evidence submitted for review.

    SHIPTRACE automated intake · 11 Mar 2026 15:00 UTC · audit ST-3FCABD6F

  4. Submitted for review →ShippedModerator conclusion

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

    Mara Okafor · 12 Mar 2026 15:00 UTC · audit ST-3FCABD70 · 1 evidence ref

ShippedCore milestone

Cross-chain messaging

Commitment (paraphrase) · Ship cross-chain messaging between three supported networks.

Evidence room
Claimed
16 Jan 2026
Deadline
15 Jun 2026 (3 months ago)
Delivered
17 Jun 2026
Evidence
1 accepted
Original source· accessed 17 Jan 2026(opens in a new tab)

Moderator note · Shipped two days after the deadline; counted as late per methodology.

Status history (4)
  1. Created →PlannedModerator conclusion

    Commitment recorded from cited source (Keelstone Oracle roadmap), accessed 2026-01-16.

    Mara Okafor · 17 Jan 2026 09:00 UTC · audit ST-45184528

  2. Planned →In progressModerator conclusion

    Project published a dated progress update.

    Mara Okafor · 1 Apr 2026 16:00 UTC · audit ST-45184529

  3. In progress →Submitted for reviewAutomated observation

    Evidence submitted for review.

    SHIPTRACE automated intake · 16 Jun 2026 15:00 UTC · audit ST-4518452A

  4. Submitted for review →ShippedModerator conclusion

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

    Mara Okafor · 17 Jun 2026 15:00 UTC · audit ST-4518452B · 1 evidence ref

ShippedMinor milestone

Node operator dashboard

Commitment (paraphrase) · Ship a dashboard for node operators.

Evidence room
Claimed
16 May 2026
Deadline
14 Aug 2026 (31 days ago)
Delivered
11 Aug 2026
Evidence
1 accepted
Original source· accessed 17 May 2026(opens in a new tab)
Status history (4)
  1. Created →PlannedModerator conclusion

    Commitment recorded from cited source (Keelstone Oracle roadmap), accessed 2026-05-16.

    Mara Okafor · 17 May 2026 09:00 UTC · audit ST-9DF0F0D2

  2. Planned →In progressModerator conclusion

    Project published a dated progress update.

    Mara Okafor · 30 Jun 2026 16:00 UTC · audit ST-9DF0F0D3

  3. In progress →Submitted for reviewAutomated observation

    Evidence submitted for review.

    SHIPTRACE automated intake · 10 Aug 2026 15:00 UTC · audit ST-9DF0F0D4

  4. Submitted for review →ShippedModerator conclusion

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

    Mara Okafor · 11 Aug 2026 15:00 UTC · audit ST-9DF0F0D5 · 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.

Nothing outstanding

No delayed, unevidenced, disputed or cancelled items in the record.

Automated observation

Development pulse

keelstone-example/keelstone-node(opens in a new tab)sample observation
Active weeks (of 12)
12
Releases / tags (90d)
5 / 2
Latest release
v4.2.0
Last push
yesterday
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

Low-latency feeds progress

Dated update: feeds live on testnet, mainnet pending.

keelstone.example· accessed 10 Sept 2026(opens in a new tab)published 9 Sept 2026
Submitted by
Mara Okafor
Review
11 Sept 2026 16:00 UTC
Community
2 support 0 challenge

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

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

Verified from public evidenceTier 3 · Official documentation / announcementModerator

Operator dashboard release

Release notes with date and screenshots linked to docs.

keelstone.example· accessed 12 Aug 2026(opens in a new tab)published 11 Aug 2026
Submitted by
Mara Okafor
Review
13 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-686E73C0 · database identifier, not a blockchain claim

Verified from public evidenceTier 1 · Working product / release + docsCommunity submission

Messaging docs and live routes

Docs list live routes with activation dates.

keelstone.example· accessed 18 Jun 2026(opens in a new tab)published 17 Jun 2026
Submitted by
Tomasz Rivera
Review
19 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-A2410956 · database identifier, not a blockchain claim

Verified from public evidenceTier 2 · Repository release / tagModerator

keelstone-node v3.0.0

Release notes include the randomness service and docs.

keelstone.example· accessed 13 Mar 2026(opens in a new tab)published 12 Mar 2026
Submitted by
Mara Okafor
Review
14 Mar 2026 16:00 UTC
Community
2 support 0 challenge

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

Audit record ST-4DD9021B · database identifier, not a blockchain claim

Verified from public evidenceTier 1 · Working product / release + docsModerator

Feeds live with public status page

Status page lists live feeds and update thresholds.

keelstone.example· accessed 18 Dec 2025(opens in a new tab)published 17 Dec 2025
Submitted by
Mara Okafor
Review
19 Dec 2025 16:00 UTC
Community
2 support 0 challenge

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

Audit record ST-113FBEE6 · 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. Evidence added
    Keelstone Oracle: evidence accepted for “Low-latency feeds”
  2. Evidence added
    Keelstone Oracle: evidence accepted for “Node operator dashboard”
  3. Shipped
    Keelstone Oracle: “Node operator dashboard” — Shipped
  4. New commitment
    Keelstone Oracle: new commitment “Proof-of-reserve feeds”
  5. Evidence added
    Keelstone Oracle: evidence accepted for “Cross-chain messaging”
  6. Shipped
    Keelstone Oracle: “Cross-chain messaging” — Shipped
  7. New commitment
    Keelstone Oracle: new commitment “Low-latency feeds”
  8. New commitment
    Keelstone Oracle: new commitment “Node operator dashboard”
  9. Evidence added
    Keelstone Oracle: evidence accepted for “Verifiable randomness”
  10. Shipped
    Keelstone Oracle: “Verifiable randomness” — Shipped
  11. New commitment
    Keelstone Oracle: new commitment “Cross-chain messaging”
  12. Evidence added
    Keelstone Oracle: evidence accepted for “Price feeds on mainnet”
  13. Shipped
    Keelstone Oracle: “Price feeds on mainnet” — Shipped
  14. New commitment
    Keelstone Oracle: new commitment “Verifiable randomness”
  15. New commitment
    Keelstone Oracle: new commitment “Price feeds on mainnet”

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