Proof Posit · permanent path
PP-005 — Robinhood Chain block production
This path is permanent: it always resolves to the current version of PP-005. Each version keeps its own seal, its own verify page and its own bytes; a superseded version is never withdrawn or rewritten.
Current version — PP-005-v3 (third edition)
| DCN | JFD-20260929-PP-00002 |
|---|---|
| status | SEALED · ANCHORED |
| Bitcoin anchor | block 969,098 · 2026-09-29T05:05:30Z |
| sealing event | kind-15 3225503 |
| fingerprint (SHA-256) | 54fe7e4140d05753ca5b089a32b24323beb2a7b826fa52cfbe100c7fc8329134 |
| certificate | JFD-20260929-CERT-00002 · kind-15 3228667 |
| supersedes | JFD-20260928-PP-00002 (superseded 2026-09-29; its seal stays valid over its own bytes) |
| verify page | gh.jetfyul.com/v/JFD-20260929-PP-00002 |
The OpenTimestamps proof is attested in Bitcoin block 969,098; the committed value was checked against the block's merkle root on two independent explorers before this page said so.
What changed in the third edition
The third edition removes the second edition's unfilled masthead date and seal-record slot lines and points to its verification page and certificate; every other byte of the text is unchanged.
Versions
| version | DCN | status | seal | verify |
|---|---|---|---|---|
| PP-005-v3 | JFD-20260929-PP-00002 | Current | kind-15 3225503 · Bitcoin block 969,098 | verify page |
| PP-005-v2 | JFD-20260928-PP-00002 | Superseded | kind-15 3206405 · Bitcoin block 968,957 | verify page |
| PP-005 | JFD-20260926-PP-00001 | Superseded | kind-15 3171889 · Bitcoin block 968,719 | verify page |
Downloads
| file | what it is | sha256 | bytes |
|---|---|---|---|
| JFD-20260929-PP-00002.pdf | the sealed document, exact bytes (the object the seal commits to) | 54fe7e4140d05753ca5b089a32b24323beb2a7b826fa52cfbe100c7fc8329134 | 305,001 |
| PP-005-ED3-source.md | its exact source (the fingerprint the sealed document prints) | 1a4fb1dc8c9b2c8a85b37589738f101a45893a8c22b2037ab25500bd04aa57ef | 11,232 |
| JFD-20260929-PP-00002.pdf.ots | OpenTimestamps proof of the sealed document | cb111aa82297bb7bf238109d20d1ca24132d710c9b82a53fad20642a8e8272e9 | 821 |
| JFD-20260929-CERT-00002.pdf | the sealed PDF of record: PP-005 with its certificate (DCN JFD-20260929-CERT-00002) | 59baf2f88a91116d2a61b4e1988c4484f372b13559215e50c9b889a0dbfcede1 | 5,864,642 |
The text below is a derived rendering, not the sealed file. The seal of record (DCN JFD-20260929-PP-00002) commits to the exact bytes of JFD-20260929-PP-00002.pdf, sha256 54fe7e4140d05753ca5b089a32b24323beb2a7b826fa52cfbe100c7fc8329134, which prints the fingerprint of its exact source PP-005-ED3-source.md. Download the sealed file above and verify it; the text below is rendered from that source with no hand edits.
PROOF POSIT PP-005
MASTHEAD
| Field | Value |
|---|---|
| Proof Posit | PP-005 (PP-004 is reserved for the AEP reconciliation) |
| Subject | Robinhood Chain (chain ID 4663) |
| Title | Robinhood Chain Produced Blocks Without Interruption on 4 September 2026 |
| Date | 2026-09-29 |
| Measurement window | Primary: 2026-09-04 00:00:00 – 23:59:59 UTC. Context: 2026-07-01 00:00:00 UTC to block 62,471,946 (2026-09-14 03:00:01 UTC). |
| Pinned at | Block 62,471,946 · hash 0x6be6970fbf6ebda579ae87bad4df04a3b7dd14486a40508a747d079fbef462eb |
| Chain | Robinhood Chain, chain ID 4663 (an Arbitrum Orbit chain settling to Ethereum) |
| Surface | Index: Glass Hull's own full-history block index (A1), whose population is proven identical to our archive extraction. No third-party endpoint or explorer was used for any figure. |
| Method hash | fea53b1c83bc9b7f4819eefa459d7178b1cbed7b4cf7cadad0fb924086b91029 (Glass Hull ledger, kind-3 3147511) · Method frozen 2026-09-25 14:27:03Z after exploratory measurement; the sealed figures are the re-run under the frozen method. |
| Re-run hash | 17fedf045ed4060954b8c6a1d95ab5721c194a3a387b9d5cbfb04c93529a31f6 (primary: 4 September, full day) |
| Supersedes / Corrects | None |
| Subject notice | Subject not contacted |
| How to cite | Glass Hull, Proof Posit PP-005, "Robinhood Chain Produced Blocks Without Interruption on 4 September 2026," Jet Fyul Dynamics LLC (2026), gh.jetfyul.com/posits/PP-005/ |
I. SUMMARY
On 4 September 2026, published reports described Robinhood Chain as having stopped for about 14 minutes beginning about 12:57 UTC (for example crypto.news, archived web.archive.org/web/20260924200651/…).
We measured every block the chain produced that day, from its own permanent record.
- Block production never stopped. Robinhood Chain produced 854,255 blocks carrying 13,978,496 transactions across all 1,440 minutes of the UTC day.
- No minute fell short. The lowest count in any single minute was 548 blocks.
- The longest interval between consecutive blocks was 2 seconds.
- At the reported time, the chain ran normally. In the minute beginning 12:57 UTC it produced 592 blocks, and the Ethereum reference the chain records advanced every minute of the day.
Since public mainnet opened on 1 July 2026, the longest interval between consecutive blocks is 16 seconds. It fell on the launch morning, 1 July at 05:35 UTC.
What paused was the chain's posting of data to Ethereum: 14 minutes in total, before 12:57 UTC. What we cannot see from the chain is whether any front end, public endpoint, or explorer was unavailable to users; Arbitrum reported a brief impact on infrastructure providers that rely on the chain's data stream. Section IV states that boundary.
II. METRIC OBJECTIVE
The public claim under test. Reports dated 4 September 2026 stated that Robinhood Chain stopped producing blocks for about 14 minutes from approximately 12:57 UTC, and that roughly 8,400 block intervals were missed. (crypto.news, "Robinhood Chain suffers 14-minute network outage", archived web.archive.org/web/20260924200651) The Defiant's same-day analysis reported that the chain did not stop (archived web.archive.org/web/20260924200411/…), and Arbitrum stated there was no downtime (self-archived, ledger 3133716).
What we measured. Whether the chain produced blocks continuously on 4 September 2026 (UTC):
- blocks produced per minute
- the longest interval between consecutive blocks
- whether the chain's recorded Ethereum reference advanced each minute
We measured the same quantities from public mainnet (1 July 2026) to the pinned block, to place the day in context.
The reporting rule. A halt is any interval between consecutive blocks long enough to be seen as a stop. We report every interval exactly, and state the longest.
III. FINDINGS
| Measure | 4 September 2026 (UTC) |
|---|---|
| Minutes observed | 1,440 of 1,440 |
| Blocks produced | 854,255 |
| Transactions | 13,978,496 |
| Fewest blocks in any minute | 548 |
| Minutes with fewer than 500 blocks | 0 |
| Longest interval between consecutive blocks | 2 seconds |
| Minutes in which the recorded Ethereum reference did not advance | 0 |
The reported window, 12:30–13:30 UTC, minute by minute:
- Every minute produced between 563 and 657 blocks.
- The longest interval was 2 seconds.
- Transactions ran between 4,245 and 17,423 per minute.
- The 12:57 UTC minute: 592 blocks (54,282,091 to 54,282,682) and 5,868 transactions.
Context, public mainnet to the pinned block:
| Measure | Value |
|---|---|
| Longest interval between consecutive blocks since 2026-07-01 00:00 UTC | 16 seconds, block 678,037, 2026-07-01 05:35:35 UTC |
| The next four longest | 13 s, 13 s, 12 s, 11 s, all within the launch morning of 1 July |
III.i PROOFS (ABRIDGED)
Pass arm. The block record for 4 September 2026 is complete and continuous: 1,440 minutes, 854,255 blocks, longest interval 2 seconds, zero minutes under 500 blocks. It is re-run as 17fedf045ed4060954b8c6a1d95ab5721c194a3a387b9d5cbfb04c93529a31f6.
The reported window at per-minute resolution is re-run as 87169581e67c858c95d342f9bff6fbd7b1b8f04d7e1b7ef7cfe5db88323f1ea8.
Refute arm. The same interval measurement returns long silences where they exist. Over the chain's full history it finds intervals of 252,948 s, 186,880 s, 81,912 s and 64,965 s, all during the pre-launch period of April–May 2026, before public mainnet. The instrument therefore does detect a stop when one is present.
- Full history: re-run
7bdc155659455ce77dd0e716402113311022baf3aff6d04a8e33be59143709b3 - Since public mainnet: re-run
b86da9693c639a1fdd62c94c7ff40040cb184913447e45fc16372bdac25d0e8f
Population. Every block from genesis to 62,471,946. The index population is proven identical to Glass Hull's archive extraction, and coverage is continuous with no missing range.
Contracts and addresses. None; this finding concerns block production only.
Corroboration. Attestation 3095118 (1–6 September 2026: longest interval 2–4 s per day, zero intervals of 5 s or more) is consistent with this result.
IV. LIMITS OF OBSERVATION
Service availability is not observable from the chain. Our record shows blocks produced and transactions included. It does not show whether a wallet, front end, public endpoint, indexer or block explorer was reachable. If users could not submit or see transactions during the reported window, the cause lay outside block production, and the chain's own record cannot identify it.
Posting to Ethereum is a separate process. Robinhood Chain periodically posts batches of its data to Ethereum. On 4 September 2026 that posting paused twice for long periods:
- from 12:29:47 to 12:38:23 UTC (516 seconds)
- from 12:42:47 to 12:48:11 UTC (324 seconds)
That is 840 seconds, 14 minutes in total, while the chain itself kept producing blocks (Glass Hull record 3137609). Two shorter gaps followed, at 13:34:47 UTC (144 seconds) and 13:45:59 UTC (132 seconds). All of these fall before or after the 12:57 UTC time given in the reports, not at it.
Arbitrum stated that day: "Robinhood Chain experienced no downtime. Earlier today, Robinhood Chain experienced batch posting delays due to L1 market blob behavior. Direct user transactions experienced no delays." (x.com/arbitrum/status/2095939844987891760, 2:19 PM ET, 4 September 2026; Glass Hull signed-in capture, sha256 213385cb…, OpenTimestamps-stamped.)
Ethereum's public record for those minutes shows the following (Glass Hull record 3137956):
- In both long pauses, the batch poster's last standing bid for blob space exceeded the blob base fee charged in every block of the pause: by about 4–13 times in the first, and about 4.5–8.8 times in the second.
- The first posting after each pause carried a higher bid.
The blob base fee alone therefore does not account for either pause. Whatever else delayed inclusion is not observable from included transactions, because replaced or dropped submissions leave no trace in chain data. We state no cause.
Timestamps have one-second resolution, so an interval under one second cannot be measured more finely than that.
We did not contact Robinhood and have no access to its internal systems or incident records.
V. CONCLUSION
Robinhood Chain produced blocks without interruption throughout 4 September 2026, including at and around 12:57 UTC. Within the limits stated in Section IV, the chain's own record does not support a description of that day as a halt in block production. Since public mainnet opened, the chain has not gone more than 16 seconds without producing a block.
This finding measures block production. It draws no conclusion about any party's statements, systems or intentions.
VI. GLOSSARY AND DEFINITIONS
- Block. A unit of the chain's permanent record, containing zero or more transactions.
- Interval between consecutive blocks. The difference in recorded timestamps between one block and the next, in seconds.
- Recorded Ethereum reference. The Ethereum block number each Robinhood Chain block records as its reference point.
- Posting to Ethereum. The separate process by which the chain's data is written to Ethereum.
- Pinned height. The last block included in the measurement, identified by number and hash.
- Both arms. The pass arm shows the result. The refute arm shows the same method would have returned the opposite result had it been true.
- Re-run hash. Confirms a result obtained with the method; the method is in The Full Proof.
- Frozen method. A method fixed and hashed before its result was computed.
VII. ADDITIONAL RESOURCES
If you would like to read more of our series, Proof Posits, you may go here. And if you would like to test yourself against a locked call, our prediction series — The Hull Against the Machine — seals each prediction before the event and reveals it on a timer. Our latest are here. Full readings are published as Full Proofs: some free, others licensed. The Full Proof for this finding, with the complete method, is free here.
SEAL AND VALIDATION
Seal record: this document's seal — its ledger event, both hardware witnesses and its Bitcoin anchor — is recorded on its verification page, https://gh.jetfyul.com/v/JFD-20260929-PP-00002, and in its certificate of authenticity, JFD-20260929-CERT-00002, not in these pages.
To validate this Posit without contacting us:
- Compute the SHA-256 of this document.
- Look up the ledger event.
- Verify both hardware signatures.
- Verify the Bitcoin anchor.
- If you prefer, verify on Robinhood Chain itself: it verifies P-256 natively at
0x100(RIP-7212). - Reproduce with the method in The Full Proof, which is free for this finding.
If your bytes differ from ours, kindly let us know publicly or privately. A difference is still a finding.