In previous articles, I demonstrated by way of many irrefutable examples that the Hebrew Scriptures are saturated with ELS codes which exhibit all the obvious markers of intelligent design. As we have seen, the authenticity of these Bible codes is proven by the fact that they occur in topically relevant biblical passages at statistically minuscule probabilities. That such codes exist is undeniable. In fact, so far as I am concerned, the question is no longer “Are Bible codes real?,” but rather—“Who encoded the Bible?” In this article we will answer this question by examining some Bible codes and allowing the evidence to speak for itself.
Why the biblical writers and copyists could not have encoded the Bible
ELS Bible codes are found in all 39 books of the Old Testament in the original Hebrew. For anyone even remotely familiar with how the Old Testament came together, it should be fairly obvious that the biblical writers could not have been responsible for these codes. The books of the Old Testament were written by approximately 32 different men who were all living at different times over a period of about 1,000 years—all of whom were writing with their own unique set of conscious intentions. Whatever these intentions and private motivations were, it is certain that none of these men (with the possible exception of maybe Moses) had even the slightest clue that they were penning Scripture at the time they were writing. What is more, they most certainly would not have had the foresight to know that their writings would be preserved and continually recopied by hand centuries after their deaths, and would eventually be gathered together into one volume which would be mass disseminated throughout the entire earth thanks to the inventions of the codex and a revolutionary device called the printing press.
The fact that they all lived at different times over a 1,000 year period, and did not know that they were penning works that would later be received as part of a unified body of literature—in and of itself proves that the biblical writers could not have been consciously responsible for the Bible codes found encrypted in their texts. But even if this were not the case—the timelessness of the codes also proves that they could not have been responsible. The person(s) who encoded the Bible possesses a knowledge of people, things, concepts, and even language that did not exist at the time that the books of the Old Testament were penned. One of the most obvious and prevalent examples which demonstrates this truth are the numerous ELS codes about Jesus that we find encoded in topically relevant Old Testament passages, hundreds of years before his birth. Add to that the fact that many ELS Bible codes use modern Hebrew words to refer to modern concepts which did not even exist, or were yet unknown—at the time that the Old Testament books were written.1 Some of these codes even use words which modern Hebrew borrowed directly from modern English! Obviously, codes of this nature could not have been deliberately encrypted by imperfect mortal men subject to the laws of time and space.
The third and final reason that the biblical writers could not have been responsible for the Bible codes pertains to the degree of intelligence that such an elaborate system of codes necessitates. As I stated in my previous introductory article to ELS codes, any given biblical passage in the Old Testament has a seemingly infinite number of topically relevant ELS codes encrypted within it—all of which are encrypted in the text at completely different equidistant letter sequences. This means that the encoder is having to narrate a story (or speak a prophecy), while ordering his words in such a way that not just one, but multiple prophetically meaningful and contextually relevant messages appear within the text at completely different equidistant letter sequences. And he is having to do all of this while still faithfully abiding by all of the grammatical laws of the ancient Hebrew language. Such a feat requires a level of intelligence that can only be described as superhuman.
The Bible codes reveal who encoded the Bible
For all of the reasons just described, the Old Testament writers could not have encoded the Bible, and the very same attributes which disqualify them also allows us to rule out the Jewish scribes and copyists who preserved and transmitted the Old Testament into the Middle Ages.
Fortunately, the same attributes which disqualify the biblical writers and copyists also provide us with something of a profile of the candidate we’re looking for. Specifically, we know that the person who encoded the Bible is someone who is: a.) not bound by the laws of time and space, and b.) possesses a level of intelligence which can only be described as superhuman. This disqualifies all human beings save for one man, and it just so happens that the Bible codes themselves appear to affirm that this exact man is the person who is responsible for the codes. Let us now examine a few different examples which demonstrate what I mean.
Example 1
Those of you who have read my introduction to ELS codes article may remember this first example I shared previously (in a two-column tabular view format) from the book of Isaiah. Here’s what it actually looks like in the grid:
As the figure above shows, the encoded statement אני ישוע (“I am Jesus”) intersects with the plain-text statement אני הוא (“I am he”) in the text grid. The authenticity of the encoded statement in this example is attested by the obvious harmony between it and the containing passage. The fact that we find the statement “I am Jesus” encrypted in these two verses in which God himself is speaking to the nation of Israel in the first person–is obviously remarkable. The intent of the encryption is obviously to bring clarity to the statement “I am he” in the plain text. By encrypting this first-person statement in this specific Old Testament passage, Jesus is identifying himself both as God in the flesh, as well as the cryptographic mastermind who encoded the Bible.
Example 2
Our next example is another one that I have written about in great length in a previous article. This one contains multiple first-person statements, all encoded separately at different equidistant letter sequences. Note that the text highlighted yellow in the grid below signify the portions of the plain text which are topically relevant to the encoded statements. Behold:
It should be noted right off the bat that Isaiah 53 is hands down probably the most blatantly obvious prophetic description of the sacrificial death of Jesus Christ in the entire Old Testament. In this chapter the prophet describes the future crucifixion of Jesus in such detail that it is difficult to understand how observant Jews could read these prophecies and deny that they’re about Jesus. In the figure above, I have high-lighted the most blatantly obvious portions of this prophetic description yellow. Note that due to space constraints, I didn’t bother to translate all of the prophetically relevant statements in the bottom row of the table like I normally do, albeit I have taken the liberty of creating the following reference table which does.
The fact that we find the statements “Jesus is my name“, “I was crucified“, and “I am chosen” all encrypted in this chapter at different equidistant letter sequences–is obviously not a coincidence.2 As I stated in the previous article I wrote about this particular ELS code, by encrypting these first-person statements in this particular prophecy–Jesus is identifying himself as not only the person being described in the plain text, but also as the very spirit of prophecy speaking through Isaiah, as well as the mysterious cryptographic mastermind responsible for the Bible codes.
Example 3
Our next example is encoded in very close proximity to our last example in Isaiah 53. The encoded message is found at an ELS of every 92 letters backwards, beginning in Isaiah 53:7 and ending in 52:8.
Here we see that the statement “I am he: Jesus” is encoded in Isaiah 52:8-53:7, which (as has already been stated) is one of the most blatantly obvious prophetic descriptions of Jesus Christ in the entire Old Testament. It is apparent that it is intended to correspond with the plain-text line (highlighted in blue in the image above): “I am he who speaks–behold it is I!”.3 This is in addition to the numerous other messianic prophecies about Jesus contained within the plain text of the containing passage, which I didn’t bother to highlight in the figure above solely for the sake of making the matrix clean and presentable. Combine with all of this the fact that this statement just so happens to be encoded literally right next to the related encoded statements from our previous example: “Jesus is my name” and “I was crucified,” and “I am chosen.” The totality of the evidence makes it undeniable that this encryption did not occur by random chance. In this example the encoder once again identifies himself by name in the first person, thereby affirming that he is the subject of the prophecies in the containing passage.
Example 4
Our next example is found at an ELS of every 59 letters in 1 Kings 8:20-25. Behold:
As can be seen, the statement שמי ישוע (“My name is Jesus”) is encrypted in 1 Kings 8:20-25 at an ELS of every 59 letters. The code’s authenticity is attested by the obvious topical relation between the encoded text-string and the containing passage. In the containing passage, Solomon is publicly addressing the nation and leading it in prayer. The encoded statement (“My name is Jesus”) is obviously intended to build upon the phrase “the name of the LORD God of Israel” in the plain text of the containing passage. Here yet again the encoder reveals his personal identity by stating his name in the first-person.
Example 5
In some codes, the encoder hints at his identity in more subtle ways, as in the following example:
As can be seen, the phrase אמי בתולה (“My mother is a virgin”) is encrypted within Lamentations 1:9-18 at an ELS of every 90 letters). This is the only passage in the entire Hebrew Bible where this eight-letter string is encrypted at a short-distance ELS.
Here yet again the authenticity of the encoded text-string is attested by the obvious topical relation we find in the plain-text of the containing passage, as the phrase “The virgin, the daughter of Judah” (highlighted navy blue) appears in the plain text. In addition to this, the name “Mary” is found encoded numerous times all over the containing passage. The encoded statement in this example identifies Jesus as the encoder, given that he is the only person to ever live who was born of a virgin mother.
Example 6
The following ELS code from Genesis 3 is another example of a Type 1 ELS in which the encoder discloses his identity without actually stating his name. Behold:
As can be seen, the phrase שם גרתי (“That’s where I lived”) is encoded in Joshua 31:32-37 at an ELS of every 47 letters. At first glance, one might be tempted to assume this encryption is statistically insignificant–given that the encoded string is only 6 letters long in this example. But appearances can be deceiving–as this string contains a gimmel, which is one of the least frequently occurring letters in the Hebrew Bible. Consequently, this is 1 of only 3 passages in the Hebrew Bible where this six-letter string is found encrypted at a short-distance ELS. As an added bonus, while staring at the text-grid, I happened to notice the name ישוע (“Jesus”) running diagonally up the grid, indicating that it is encrypted at an ELS of every 46 letters.
The fact that the statement “That’s where I lived”, and the name “Jesus”, both just so happen to be found encoded in the book of Joshua right next to the words “in Galilee and her suburbs” in the plain text, is obviously no coincidence. This line of topical correspondence converges with our encoded statement by divine providence to form one unified cryptic message: “In Galilee and her suburbs–that’s where I lived (Jesus).” This is yet another example which points to Jesus as the encoder.
Example 7
Another interesting example of an ELS code which reveals who encoded the Bible is found in Deuteronomy 18. Behold:
In this example, we see that the statement שוב אקום (“I will rise again”) is encoded at an ELS of every 115 letters in Deuteronomy 18:5-19. Note that this is 1 of only 2 passages in the Hebrew Tanakh where this seven-letter string is found encrypted at a short-distance ELS. The topical relation between the encoded text-string and the containing passage should be fairly self-evident in this example. The plain-text prophecies highlighted in blue in the figure above have long been esteemed by the Church to be one of the most obvious prophecies about Jesus in the five books of Moses. The verb “raise up” in this prophecy has a dual meaning. On the one hand, the phrase “raise up” is a common figurative way of denoting the act of establishing. Thus in this example, God is simply stating that he will one day establish a certain prophet among the people who will instruct them. On a prophetic level, however, the meaning is literal—God is literally going to “raise up” (resurrect) this future prophet. This latter prophetic meaning was a mystery that wouldn’t have made sense to anyone until Jesus rose from the dead and fulfilled it (Eph. 3:9; Col. 1:26). The authenticity of the encoded text-string is affirmed by this latter literal-prophetic meaning of the prophecy in the containing passage, as this very same statement (“I will rise again”) is something that Jesus literally says in the New Testament (Matt. 27:63).
It is obvious who encoded the Bible.
We need not endlessly speculate about who encoded the Bible, as the answer to this question is provided by the encoder himself. In this article we have looked at several different Type 1 ELS codes in which the mysterious cryptographer responsible for the Bible codes makes his personal identity known. As we have seen, in many of the codes the encoder literally introduces himself by name in the first person; while in others he attests of his identity more subtly through the use of hints and pseudo-identifiers. In both cases, the authenticity of these codes is attested by the occurrence of obvious topical relation between the encoded text-string and the containing biblical passage.
There can be absolutely no doubt that Jesus Christ, that is—God in the flesh (1 Tim. 3:16; John 1:14; cf. John 1:1), is the cryptographic mastermind who encoded the Bible. Reinforcing this conclusion is the fact that God alone possesses the superhuman intelligence, knowledge, and abilities that would be required to devise such an elaborate system of codes which defy both human logic as well as the laws of time (Job 36:4; 37:16; Ps. 147:5; Isa. 40:8; 2 Tim. 2:9; Isa. 42:9; John 13:19; 14:29). No group of mortal human beings could have conspired together to place these codes in the Bible. Indeed, as the divine encoder himself rightly stated during his earthly ministry: “With men this is impossible; but with God all things are possible.” (Matt. 19:26; cf. Mark 10:27; Luke 18:27).
Copyright secured by Digiprove © 2021 Zerubbabel
- For a more detailed discussion on this topic, see my recent article on modern Hebrew Bible codes.
- It is interesting that the phrase “I am chosen” is found encoded here, as the plain text of the prophecy describes how Jesus was hated and rejected of men (Isa. 53:3). The significance of this is that Jesus stated that anything that God has chosen is hated by the world (John 15:19; 1 Cor. 1:28).
- This highlighted statement is actually one small part of a larger verse which reads: “Therefore my people shall know my name: therefore they shall know in that day that I am he that doth speak: behold, it is I.” The only reason I didn’t highlight the entire verse was all for the sake of making the matrix appear more clean and presentable.