Daniel as Timestamp: Dating the Final Visions

Scope note: This dossier establishes the Maccabean date of Daniel’s final visions and their downstream canonical role. It does not prove resurrection false, establish Iranian causation by itself, or identify Jesus’s Father. The positive identity evidence is isolated in Run 13.

Executive finding

The strongest historical conclusion is narrower and more powerful than “the whole Book of Daniel is a late fabrication.” The court tales in Daniel 1–6 may preserve older material. The apocalyptic visions in Daniel 7–12, however, reached their final form during the persecution of Antiochus IV Epiphanes, most probably between the desecration of the Jerusalem temple in 167 BCE and Antiochus’s death in late 164 BCE.

Daniel 11 is the decisive evidence. It narrates the wars and dynastic intrigues of the Ptolemies and Seleucids with increasing detail, culminating in Antiochus IV’s assault on Jerusalem. At 11:40, the accuracy breaks: the text predicts another victorious invasion of Egypt, conquests extending to Libya and Cush, and Antiochus’s death near the “holy mountain.” Those events did not occur. Antiochus instead died during an eastern campaign in Persia in 164 BCE.

The best explanation is that the author was describing past events in prophetic form (vaticinium ex eventu) until reaching his own present, then made an actual prediction that failed. This dates the vision without assuming beforehand that real prophecy is impossible.

Grade:

• Daniel 11:2–39 substantially reviews Hellenistic history retrospectively: established.
• Daniel 11:40–45 predicts events that did not occur as written: established.
• Daniel 10–12 was composed in the Antiochene crisis, approximately 167–164 BCE: probable approaching established.
• Every chapter of Daniel was first composed in that same window: unsupported; the court tales likely have a more complex prehistory.

Affirmative contribution to the Mazda–Father case

Daniel supplies the timestamp that prevents the mature Jewish apocalyptic package from being projected unchanged into early Israel. Resurrection, cosmic judgment, angelic conflict, and the Son-of-Man horizon become securely visible in the final visions during the Maccabean crisis, centuries after Persian rule began. This run does not prove Iranian causation by itself; it establishes the late Jewish endpoint that the Iranian priority, contact, and transmission evidence must explain. The later runs show that the package did not arise in an isolated conceptual vacuum.

1. The book is composite

Daniel divides conspicuously into two major forms:

1. Court tales (chapters 1–6): Daniel and his companions survive and outwit foreign imperial courts.
2. Apocalyptic visions (chapters 7–12): symbolic beasts, angelic interpreters, cosmic warfare, resurrection, and the end of an oppressive kingdom.

H. L. Ginsberg’s chapter in The Cambridge History of Judaism describes the historical background of chapters 7–12 as unmistakably the persecution of Antiochus IV, while allowing older traditions behind the court tales. This compositional distinction matters. A defensible case should not claim more than the evidence supplies. The Maccabean date attaches most securely to the final visions and the book’s final form, not necessarily to the first appearance of every story.

2. Daniel 11 is a disguised history

Daniel 11 presents its account as a revelation given during the Persian period. Read beside Hellenistic history, however, it behaves like a compressed chronicle of the third and second centuries BCE.

The density is the point. The text does not merely predict that empires rise and fall. It follows a sequence of marriages, murders, campaigns, humiliations, and policy changes that becomes especially detailed as it approaches Antiochus IV. That is the normal signature of an apocalypse written during the crisis it symbolically narrates.

3. The prediction break

Daniel 11:40–45 expects three linked developments:

1. a renewed end-time attack by the king of the South;
2. the northern king’s overwhelming conquest of Egypt, Libya, and Cush;
3. his return north and death between the sea and the holy mountain.

The secure historical outcome differs. First Maccabees 6:1–16 places Antiochus in the “upper provinces,” campaigning around Elymais in Persia, before he dies in a foreign land. Polybius, as discussed by Rüdiger Schmitt in Encyclopaedia Iranica, locates the death at Gabae in 164 BCE, though the exact toponym rests on a manuscript correction. The precise eastern city can therefore remain qualified. What is not seriously in doubt is the decisive contrast: Antiochus did not conquer Egypt in the predicted final campaign and did not die beside Jerusalem’s holy mountain.

This produces a chronological fingerprint:

• the author knows the temple profanation and persecution;
• the author expects Antiochus’s imminent defeat;
• the author does not know the actual manner and eastern location of Antiochus’s death.

Accordingly, the final vision belongs after the crisis began and before news of the king’s death reached the author: approximately 167–164 BCE, often narrowed to 165–164 BCE.

Richard S. Briggs, writing from within theological interpretation rather than as an anti-religious polemicist, still describes Daniel 11’s relationship to what did and did not happen to Antiochus as historically problematic. The conclusion does not depend on Porphyry, modern atheism, or a prior denial of supernatural prediction. It arises from the text’s own change in historical performance.

4. Why this is not circular anti-prophecy reasoning

A common defense says critical scholars date Daniel late only because they assume predictive prophecy cannot occur. That objection misses the strongest argument.

If Daniel 11 had accurately described Antiochus’s death centuries in advance, supernatural prediction and a later imitation of prophecy would remain rival explanations. But the text is highly accurate where events are already past from a Maccabean author’s perspective and inaccurate exactly where events become future from that perspective. The failed endpoint supplies the author’s temporal location independently of one’s metaphysics.

The inference is abductive:

A writer living during the persecution could know 11:21–39 in detail, expect Antiochus’s imminent destruction, and be wrong about how it would happen. A sixth-century writer would have to achieve detailed knowledge of centuries of events and then, inexplicably, lose that knowledge precisely at the authorial present reconstructed by the Maccabean model.

The second model is possible only after adding special assumptions. The first explains both the successes and the failure in one move.

5. Corroborating evidence, carefully weighted

Historical retrospection

• Belshazzar: Daniel calls him Nebuchadnezzar’s son and king. Historical records identify him as the son of Nabonidus and royal co-regent, not Nebuchadnezzar’s biological son. Semitic kinship language can be broad, so this supports but does not by itself prove a late date.
• Darius the Mede: no securely attested ruler matching Daniel’s Darius has been identified between Babylon’s fall and Cyrus. Proposed identifications with Gubaru, Cyaxares II, or another official remain disputed.
• Daniel 1:1: its regnal chronology sits awkwardly beside Jeremiah 25:1. Different accession-year systems may reduce the problem, making it secondary evidence rather than a knockout point.

Grade: cumulative support for distance from the sixth-century setting: probable; individually decisive: no.

Language

Daniel’s Hebrew and Aramaic, Persian administrative terms, and a small number of Greek musical terms have generated enormous debate. They do not yield a clean date by themselves. Michael Shepherd’s work, noted by Briggs, cautions that Daniel’s Aramaic cannot simply rule out an early date, while the few Greek words are too narrow to prove a second-century date alone.

Grade: compatible with a layered Persian/Hellenistic transmission history; independently decisive for 164 BCE: unsupported.

Canonical placement and Sirach

Daniel appears among the Writings rather than the Prophets in the Jewish canon, and Ben Sira’s praise of Israel’s ancestors does not name him. Both facts fit a relatively late rise to scriptural prominence, but canon formation was fluid and silence is not proof.

Grade: modest corroboration only: plausible.

Qumran manuscripts—and the 2025 radiocarbon result

The Qumran evidence is the strongest control against exaggerating the late-date case. The manuscript 4Q114 preserves portions of Daniel 8–11. A 2025 PLOS ONE study reports an accepted radiocarbon range of 230–160 BCE for its parchment, overlapping the literary-historical date assigned to Daniel’s final visions.

This matters in two directions:

1. It shows that Daniel 8–11 circulated remarkably early and may survive in a copy close to the work’s final composition.
2. It does not date the composition to 230 BCE, much less the sixth century. Radiocarbon dates the animal material within a probability range, not the moment the work was authored; 160 BCE overlaps the Maccabean composition window.

The study’s own authors explicitly say the range overlaps the period when the final part of Daniel was presumably composed. Treating 4Q114 as proof of sixth-century authorship would reverse the published result.

Grade: early physical attestation and rapid circulation: established; disproof of Maccabean composition: unsupported.

6. The strongest rival readings

Rival A: the vision shifts from Antiochus to a future Antichrist

Some interpreters place a prophetic “gap” around 11:35–36 or 11:40. On this reading, the final campaign and Judean death concern a future eschatological enemy, not Antiochus.

Strength: later Jewish and Christian reception did reuse Daniel’s persecuting king as a type of future evil. The language becomes more cosmic near the end.

Weakness: the text gives no explicit new king, chronological reset, or change of referent. “The king” continues the same north/south conflict and the same career. The proposed gap is introduced to protect fulfillment rather than signaled by the grammar.

Grade: viable as later theological reception; weak as the historical sense of Daniel 11: possible but textually under-supported.

Rival B: every detail was revealed to a sixth-century Daniel

Strength: it respects the book’s narrative setting and the theological possibility of revelation. Some linguistic features permit earlier material.

Weakness: it does not explain the exact accuracy breakpoint, Darius the Mede, the Antiochene saturation of chapters 7–12, or why the final sequence corresponds to the hopes of 165–164 BCE rather than what happened.

Grade: confessionally possible; historically much less economical than Maccabean composition: unsupported as the best historical model.

Rival C: the failed prediction was added later to an older vision

Strength: Daniel is demonstrably layered, so redaction is not ad hoc in principle.

Weakness: this concedes the central point: the decisive ending and final form are Maccabean. It cannot preserve the claim that Daniel 10–12 as received is a sixth-century prediction.

Grade: possible compositional refinement; no rescue for the final vision’s traditional date.

Rival D: 4Q114 proves Daniel must be substantially earlier

Strength: a copy requires some prior interval for composition and transmission.

Weakness: the new range is broad, applies to parchment, and explicitly overlaps the 160s. Ancient crisis literature can circulate quickly, and Daniel’s stories already had a prehistory into which the final visions could be incorporated.

Grade: reason to avoid over-narrow dating and simplistic production timelines; not evidence of sixth-century authorship.

7. What is established as false in Daniel?

The historical result should be stated without euphemism:

1. False antiquity: the final visions are a Maccabean composition placed in the mouth of a supposed sixth-century figure.
2. Backdated prediction: Daniel 11 narrates events already completed by the 160s BCE as though they were predictions delivered centuries earlier.
3. Exposure at the prediction break: when the author reaches events still future to him, the account ceases to match Antiochus IV’s actual end.
4. Retrojected resurrection: Daniel 12 places the late doctrine of differentiated resurrection inside this fabricated ancient revelatory setting.

In ordinary modern language, this is a false provenance claim: recent history and a late resurrection doctrine are presented under ancient prophetic authority. The technical historical labels are pseudepigraphy and prophecy after the event (vaticinium ex eventu). Those labels describe the mechanism; they do not make the provenance true.

Daniel’s presentation of differentiated resurrection as a sixth-century revelation is historically false. The doctrine appears in a Maccabean apocalypse that projects it backward under Daniel’s name.

The author’s private psychology is not recoverable and is not needed for this conclusion. Ancient literary convention may explain how pseudonymous writing functioned, but it cannot convert a second-century composition into a sixth-century revelation. What the evidence does not determine is whether resurrection itself is metaphysically true or false. The established lie concerns authorship, antiquity, prediction, and claimed revelatory provenance.

8. What this establishes for the Father case

Daniel supplies a timestamp, not yet an Iranian source attribution.

It establishes that by the 160s BCE Jewish scripture contains a mature apocalyptic package including:

• named angelic and national heavenly powers;
• a cosmic interpretation of imperial history;
• resurrection to differentiated destinies (12:2);
• final judgment and vindication;
• a human-like heavenly figure and everlasting dominion (7:13–14);
• a periodized end of evil.

The next historical question is not whether these ideas are ancient Israelite merely because they now appear in scripture. It is where this late package came from. The next dossier must compare Daniel 12:2 with earlier Israelite death theology, Isaiah 26:19, Ezekiel 37, Gathic and later Iranian eschatology, and non-Iranian alternatives.

Daniel therefore functions as a controlled hinge:

Before Daniel: no unambiguous biblical resurrection to differentiated eternal destinies.
At Daniel: the doctrine appears in a text datable to the Maccabean crisis.
After Daniel: resurrection becomes a major Jewish dispute and a foundation of Jesus movements.

This is enough to expose development. It is not enough, standing alone, to prove Iranian causation or identify Jesus’s Father with Ahura Mazda.

9. Falsification and revision conditions

The dating conclusion would materially weaken if any of the following appeared:

• a securely proven pre-Hellenistic manuscript containing Daniel 11 in substantially its received form;
• contemporary evidence that Antiochus conducted the predicted final Egyptian campaign and died near Jerusalem;
• a textually signaled break showing that 11:40 introduces a different historical subject;
• a sixth-century source containing the specific Ptolemaic–Seleucid sequence independently of Daniel.

None is presently available.

The conclusion should be revised—not defended at all costs—if future manuscript or archaeological evidence supplies one.

Sources

Primary texts

• Daniel 7–12, especially 11:21–12:4.
• 1 Maccabees 6:1–16, locating Antiochus’s last campaign and death in the eastern provinces/Persia.
• Polybius, Histories 31.9.3, summarized with the textual issue in Rüdiger Schmitt, “Gabae,” Encyclopaedia Iranica.

Critical scholarship and controls

• H. L. Ginsberg, “The Book of Daniel,” in The Cambridge History of Judaism, vol. 2, ed. W. D. Davies and Louis Finkelstein (Cambridge University Press, 1990), 504–523. DOI: 10.1017/CHOL9780521219297.014.
• John J. Collins, Daniel: A Commentary on the Book of Daniel, Hermeneia (Fortress Press, 1993), especially 18–38 and the commentary on 11:40–45.
• Carol A. Newsom with Brennan W. Breed, Daniel: A Commentary, Old Testament Library (Westminster John Knox, 2014), especially the commentary on Daniel 10–12.
• Richard S. Briggs, “The Eclipse of Daniel’s Narrative: The Limits of Historical Knowledge in the Theological Reading of Daniel,” Scottish Journal of Theology 70.3 (2017): 264–277. DOI: 10.1017/S003693061700028X.
• Mladen Popović et al., “Dating Ancient Manuscripts Using Radiocarbon and AI-Based Writing Style Analysis,” PLOS ONE 20.6 (2025): e0323185. DOI: 10.1371/journal.pone.0323185.
• Jona Lendering, “Daniel 11 in Context,” Livius.org, for a concise public verse-to-event map; used as a secondary orientation, not as the sole authority for the dating conclusion.

Run verdict

Established: Daniel’s final visions are not reliable evidence of a sixth-century prophet foretelling the Seleucid crisis. They are the product of a layered book whose apocalyptic endpoint belongs in the crisis itself.

Established contribution: the mature canonical system inherited by the Gospel traditions is late and historically located. The upstream Iranian genealogy and final Mazda–Father identification are established cumulatively by the remaining dossiers rather than loaded onto Daniel alone.

Operational formulation:

Daniel is the timestamp. The failed prediction locates the clock.