Written by The Longest Lie — Part 5 of 11
eFireTemple.com
The Book of Daniel claims to be written by a Jewish prophet living in Babylon and Persia during the sixth century BCE — roughly 600 to 530 BCE. It presents itself as a contemporary account of life in the court of Nebuchadnezzar and his successors, complete with prophetic visions received directly from God through angelic intermediaries.
It was not written in the sixth century BCE.
The scholarly consensus — shared by critical scholars across Jewish, Christian, and secular academia — is that Daniel was composed around 165 BCE, during the Maccabean revolt against the Seleucid king Antiochus IV Epiphanes. The evidence is in the text itself, and it is not subtle.
How we know the date
Daniel’s “prophecies” of future events are astonishingly accurate up to a very specific point in history — and then suddenly become wrong.
Chapters 10 through 12 describe a sequence of events involving the “king of the north” and the “king of the south” that precisely match the historical conflicts between the Seleucid and Ptolemaic dynasties. The description of a king who “exalts himself and magnifies himself above every god” and who desecrates the Temple matches Antiochus IV Epiphanes, who in 167 BCE erected an altar to Zeus in the Jerusalem Temple and banned Jewish religious practice.
The details are so precise — the specific military campaigns, the political alliances, the desecration of the Temple — that scholars recognized centuries ago that these passages were written after the events they describe. This is vaticinium ex eventu — prophecy after the fact. The author knew these events because they had already happened.
Then, around Daniel 11:40, the “prophecies” go wrong. They predict Antiochus will invade Egypt and die in the Holy Land. In historical reality, Antiochus abandoned his Egyptian campaign under Roman pressure and died in Persia in 164 BCE. The point where the text transitions from accurate history to inaccurate prediction marks the date of composition — approximately 165 BCE.
This dating is not controversial. It is the consensus of critical biblical scholarship. The Book of Daniel was written in the second century BCE and set in the sixth century BCE.
What the backdating accomplishes
Understanding the date of composition transforms everything about the book.
Daniel does not record concepts that a Jewish prophet received from God in 600 BCE. Daniel records concepts that had been circulating in the Jewish community for three to four hundred years — concepts absorbed from Zoroastrianism during two centuries of Persian rule — and places them in the mouth of a fictional prophet living during the Persian period.
This is not creative anachronism. This is strategic backdating. And it accomplishes something very specific: it eliminates the evidence of sequence.
If Daniel is receiving visions of angels, resurrection, judgment, and apocalyptic timelines in 600 BCE, then a reader might conclude that Judaism had these concepts at the same time as — or even before — Zoroastrianism. The chronological evidence of borrowing disappears. The concepts appear to be indigenous to Judaism, received through prophetic revelation, not cultural absorption.
The 165 BCE author takes ideas that entered Jewish thought through contact with Zoroastrianism during the Persian period (539-332 BCE) and writes them into a narrative set in the early Persian period — making it look as though the ideas were already part of Jewish theology before the contact could have produced them.
This is theological money laundering. You take concepts from one source, hold them for several centuries, then produce a document that creates a false paper trail showing they were yours all along. The original source disappears from the record. The laundered concepts look clean.
The scope of what was laundered
Everything. Every concept in the inventory.
Named angels — Gabriel and Michael appear in a book “set” in 600 BCE, making it look as if Judaism had named angels from the beginning of the exile, contemporaneous with or prior to the Zoroastrian system. In reality, the concept entered Jewish thought during the Persian period and was written into a backdated text four hundred years later.
Resurrection — Daniel 12:2 places the first resurrection verse in a sixth-century context. A reader unfamiliar with the actual date of composition would believe Judaism had resurrection theology as early as the Babylonian exile. In reality, the concept was absorbed during Persian rule and inserted into a second-century text pretending to be four centuries older.
Apocalypticism — The entire genre of apocalyptic literature appears in Daniel as if it were natural prophetic revelation. In reality, it is the Zoroastrian framework of cosmic ages, predetermined timelines, and divine renovation — repackaged as Jewish prophecy and backdated to eliminate the trace of its origin.
The Son of Man — Daniel 7:13 places a cosmic savior figure in a sixth-century vision. This creates the impression that the concept is indigenous to Judaism. In reality, the Saoshyant figure of Zoroastrian eschatology is the structural source, and the 165 BCE author is the one who wrote it into the Jewish canon under cover of pseudonymous ancient authorship.
Every major concept in Daniel is laundered through the same mechanism: place it in the mouth of an ancient prophet, set the story in the period of contact, and let the reader assume the ideas were Jewish all along.
The Sar Paras — the fingerprint left behind
Here is where the laundering operation reveals itself.
Daniel 10:13 — the verse where the angel says the Prince of Persia was already there, already powerful, already established — is the one moment where the 165 BCE author’s awareness of Persian theological priority leaks through.
The author knows that the Persian spiritual system was already in place. By 165 BCE, this would have been common knowledge among educated Jews. The Zoroastrian theological infrastructure was the background of the entire Persian period. The author cannot write a story set in Persia without acknowledging that the Persian system exists.
But the author cannot acknowledge it as a source. That would defeat the purpose of the entire book. So the author does something ingenious: the Persian spiritual being is reframed as an adversary. The Sar Paras is not the teacher — he is the obstacle. He does not share theology — he blocks the angel. The author takes the historical reality of Persian theological priority and inverts it into a narrative of spiritual opposition.
The fingerprint remains. The text still tells you the Persian system was already there. But the framing has been reversed. The source has been turned into the enemy.
This is the tell. This is the moment where the laundering operation is visible — where the author’s knowledge of the real history bleeds through the fictional narrative. The Sar Paras was already there because the Zoroastrian system was already there. The 165 BCE author knew this. And instead of acknowledging the debt, the author weaponized the source into a villain.
The precedent it set
Daniel established a template. It demonstrated that you could take a foreign theological system, embed it in a backdated narrative, attribute it to divine revelation, and make it canonical scripture. And it worked. Daniel was accepted into the canon. Its concepts became normative. Its language — Son of Man, Ancient of Days, the books of judgment — became the vocabulary of Jewish, Christian, and Islamic eschatology.
The success of Daniel ensured that the laundering would never be examined. Once a concept is canonical — once it is in the Bible — its origin becomes irrelevant to the believing community. No one asks where Gabriel’s name came from. No one asks why resurrection appears only in Daniel. No one asks why the entire genre of apocalyptic literature begins in a book set in Persia.
The laundry is clean. The source is erased. And the concepts circulate through three world religions as if they had always been there.
Daniel is not a book of prophecy. Daniel is a book of concealment. It is the document that turned Zoroastrian theology into Jewish revelation and erased the receipt.
Almost.
Because the Sar Paras is still in verse 10:13. The fingerprint is still there. The laundering operation left one trace it could not remove — the admission that the Prince of Persia was already there when the Jewish angel arrived.
The receipt was filed. And it has been sitting in the text for over two thousand years, waiting for someone to read it.
Next: Part 6 — The Celebration. The Book of Esther invents a genocide that never happened, turns the liberating civilization into the villain, celebrates the massacre of 75,000 Persians, and creates a holiday that is observed to this day. The theological laundering of Daniel has a companion — and it is the political laundering of Esther.
eFireTemple.com — The Oldest Flame. The Loudest Voice.