PROPHECY LEDGER
The Bible gives one plain test for anyone who claims to speak for God: if what they said would happen does not happen, God did not say it. This ledger applies that test in the open. Every claim is entered with its date, its source recording, and the window it applies to, then scored against the public record once the window closes. Nothing is edited after the fact; every record is hashed the day it is entered.
“If what a prophet proclaims in the name of the LORD does not take place or come true, that is a message the LORD has not spoken.” (NIV)
“When a prophet speaketh in the name of the LORD, if the thing follow not, nor come to pass, that is the thing which the LORD hath not spoken, but the prophet hath spoken it presumptuously: thou shalt not be afraid of him.”
DEUTERONOMY 18:22
This is a public record of dated, specific claims, each with the words as first recorded, the date they were spoken, the window they applied to, what the public record shows, and the sources. Every record is hashed the moment it is entered, and the hashes will be timestamped on Ethereum, so that once a window closes neither the speaker nor we can quietly rewrite what was claimed. A correction is a new record; the old hash stands. Hits are shown as plainly as misses, and they sit next to each other.
SPEAKERS
Accuracy is hits divided by everything that has been scored: hits, date hits, partials and misses. Date hits and partials are shown on their own and are not counted as hits. Claims whose window is still open, or which are waiting on a citation, sit outside the count. A scoreboard is not a verdict on a person. It is a tally of dated claims against the public record, and nothing more.
THE RECORDS
Newest window first. Open any row for the scoring note, the sources, and the record's hash. Market price targets appear here only as claims to be scored; nothing on this page is investment guidance.
Pending includes open windows, closed windows still waiting on a citation, and archives being catalogued.
/rapture/data/claims.json.HOW SCORING WORKS
The rules below are the same rules stored inside the data file the page reads from, so the criteria travel with the records and are hashed alongside them.
BO POLNY'S FRAMEWORK, EXPLAINED FAIRLY
Bo Polny is a market cycle analyst who reads charts against the biblical calendar. He calls it God's calendar versus man's calendar: God acts on appointed times, the feasts of Leviticus 23, the Sabbath and Jubilee years of Leviticus 25, and the day counts of Daniel, so if you can locate the cycle you can locate the turning point even without knowing what the event will be. He is usually careful to say he does not know what will happen on a date, only that the date is a time point. That matters for scoring him, and it is why the ledger keeps a separate column for date hits.
The part of his work that is a plain, checkable observation is the Jerusalem Jubilee chain: the Balfour Declaration and Allenby's entry into Jerusalem in 1917, the reunification of Jerusalem in the Six-Day War of 1967, and the United States recognizing Jerusalem as Israel's capital in 2017. Fifty-year intervals, three real dates. He extends the same fifty-year count to money: Nixon closing the gold window in 1971 and the dollar's fiftieth year in 2021; the petrodollar arrangement of 1973 and Saudi Arabia joining BRICS in 2023; and 1776 plus 250 to America's Jubilee in 2025 and 2026. The anniversaries are real. The significance is his inference.
On top of the Jubilee count he layers the seven-year Shemitah cycle (Leviticus 25, popularised by Jonathan Cahn through the Elul 29 market drops of 2001 and 2008), a day-count scheme he calls Daniel's Timeline that maps the 1,260, 1,290 and 1,335 days of Daniel 12 and the 70 weeks of Daniel 9 onto modern anchors (his worked example: 1,260 days from the 2016 election lands on 21 April 2020, the day after oil went negative), the feast days as triggers for market and geopolitical turns, the seven seals of Revelation read as years beginning in 2020, and a set of number overlays: 7 for completion, 17 for victory, 50 for Jubilee, 70 for Daniel and Jeremiah, 2,520 for seven prophetic years. The output is a specific Gregorian date or a two-to-four day window, described as historic, usually with a direction for gold, silver or Bitcoin attached, rarely with a named event.
The method is transparent enough to test, and this ledger tests it. Where it gets loose: the biblical Jubilee count is not settled (rabbinic tradition holds it lapsed after the exile, and candidate years differ by one or two); the 1917, 1967, 2017 spacing is fifty years, not the forty-nine of Leviticus 25; and the same anchors, 20 to 21 April, Elul 29, 24 October, are reused year after year until something lands on one. His record reads as strong on the direction of secular cycles, weak on dates and magnitudes, and the misses outnumber the hits by a wide margin.
A caution the site takes seriously. Scripture uses numbers symbolically, and 7, 12, 40, 70 recur with consistent meaning; observing those patterns is legitimate Bible study. Gematria and day-year arithmetic anchored to modern elections go beyond what the text asks. The historic Christian caution is Deuteronomy 18:20 to 22 (a false date is a false word), Matthew 24:36 and Acts 1:7 (the times are the Father's), 2 Peter 3:8 (God's day is not our day), and 1 Thessalonians 5:1 to 6 (be awake, not calculating). Watching for patterns is one thing. Publishing “God gave me March 19” is the thing the texts warn against, and that is the line this ledger draws. Polny is presented here as one voice among many, a pattern observer whose dated forecasts have a public scorecard, not as a prophet. The site does not set dates. His asset calls are recorded as claims and never repeated as advice.
SUBMIT A CLAIM
Anyone can add to the ledger: a claim from any speaker, a hit we have not entered, a miss we have not entered, or a better source for a record already listed. Every entry needs a citation before it is scored, so a submission has to carry the whole record with it.
Subject line “Rapture.NFT - prophecy ledger claim”. One claim per email. It is entered, hashed, and shown with its source; scoring follows once the window closes and the outcome can be cited.