{"format":"ptob-page","version":1,"canonical":"https://ptob.dev/blog/usb-frame-timing/","title":"USB Start-of-Frame Timing on macOS and Raspberry Pi — PToB Blog","description":"Every USB connection keeps a steady 1 ms beat. Early PToB experiments on a Mac and a Raspberry Pi suggest it could carry far finer time than its reputation allows.","language":"en","robots":"index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1","dates":{"published":"2026-11-18T00:00:00.000Z","modified":"2026-11-18T00:00:00.000Z"},"authors":["Jonathan Yantis"],"mainEntity":"https://ptob.dev/blog/usb-frame-timing/#article","representations":{"application/json":"https://ptob.dev/blog/usb-frame-timing/?format=json","text/markdown":"https://ptob.dev/blog/usb-frame-timing/?format=markdown"},"documentation":"https://ptob.dev/agent-formats.json","social":{"openGraph":{"title":"USB Start-of-Frame Timing on macOS and Raspberry Pi — PToB Blog","description":"Every USB connection keeps a steady 1 ms beat. Early PToB experiments on a Mac and a Raspberry Pi suggest it could carry far finer time than its reputation allows.","url":"https://ptob.dev/blog/usb-frame-timing/","type":"article","siteName":"PToB","locale":"en_US","image":{"url":"https://ptob.dev/blog/usb-frame-timing-v1.jpg","secureUrl":"https://ptob.dev/blog/usb-frame-timing-v1.jpg","type":"image/jpeg","width":"1600","height":"1000","alt":"A host computer and a small PToB clock joined by a USB cable with evenly spaced start-of-frame marks. Below, both clocks record the same frame."}},"twitter":{"card":"summary_large_image","title":"USB Start-of-Frame Timing on macOS and Raspberry Pi — PToB Blog","description":"Every USB connection keeps a steady 1 ms beat. Early PToB experiments on a Mac and a Raspberry Pi suggest it could carry far finer time than its reputation allows.","image":{"url":"https://ptob.dev/blog/usb-frame-timing-v1.jpg","alt":"A host computer and a small PToB clock joined by a USB cable with evenly spaced start-of-frame marks. Below, both clocks record the same frame."}}},"citations":[],"provenance":{"sourceUrl":"https://ptob.dev/blog/usb-frame-timing/","sourceMediaType":"text/html","sourceSha256":"b321eb86072c8ac2018a1560cf7628d0ab0134451d5e6f5606a6ceaabb35549e","rightsUrl":"https://github.com/yantisj2/PToB/blob/main/LICENSING.md"},"contentUsage":{"aiTrain":true,"search":true,"aiInput":true,"reason":"summary-or-introduction"},"structuredData":[{"@context":"https://schema.org","@graph":[{"@type":"WebSite","@id":"https://ptob.dev/#website","url":"https://ptob.dev/","name":"PToB","alternateName":["Precision Time over BLE","Precision Time over Bluetooth"],"description":"Bluetooth and USB software clocks: W12 60.3 ns relative-PPS RMS over 522/600 observations, separate 64 s sampled holdover, and CoreSE diagnostics.","inLanguage":["en","de"],"publisher":{"@id":"https://ptob.dev/#jonathan-yantis"}},{"@type":"Person","@id":"https://ptob.dev/#jonathan-yantis","name":"Jonathan Yantis","url":"https://github.com/yantisj2/PToB/blob/main/CREDITS.md"},{"@type":"Project","@id":"https://ptob.dev/#project","name":"PToB","alternateName":"Precision Time over BLE","url":"https://ptob.dev/","description":"An independent protocol project researching precision time transfer across Bluetooth-enabled microcontrollers and USB clients.","sameAs":"https://github.com/yantisj2/PToB","member":{"@id":"https://ptob.dev/#jonathan-yantis"},"knowsAbout":{"@id":"https://ptob.dev/#protocol"}},{"@type":"Thing","@id":"https://ptob.dev/#protocol","name":"Precision Time over BLE","alternateName":"PToB","description":"An experimental PTP-inspired protocol proposal for wireless clock synchronization over Bluetooth Low Energy."},{"@type":"WebPage","@id":"https://ptob.dev/blog/usb-frame-timing/#webpage","url":"https://ptob.dev/blog/usb-frame-timing/","name":"USB Start-of-Frame Timing on macOS and Raspberry Pi — PToB Blog","description":"Every USB connection keeps a steady 1 ms beat. Early PToB experiments on a Mac and a Raspberry Pi suggest it could carry far finer time than its reputation allows.","inLanguage":"en","keywords":["USB SOF","macOS","Raspberry Pi","PPS","chrony"],"isPartOf":{"@id":"https://ptob.dev/#website"},"author":{"@id":"https://ptob.dev/#jonathan-yantis"},"about":{"@id":"https://ptob.dev/#protocol"},"dateModified":"2026-11-18T00:00:00.000Z","image":"https://ptob.dev/blog/usb-frame-timing-v1.jpg","breadcrumb":{"@id":"https://ptob.dev/blog/usb-frame-timing/#breadcrumbs"},"mainEntity":{"@id":"https://ptob.dev/blog/usb-frame-timing/#article"}},{"@type":"BreadcrumbList","@id":"https://ptob.dev/blog/usb-frame-timing/#breadcrumbs","itemListElement":[{"@type":"ListItem","position":1,"name":"PToB","item":"https://ptob.dev/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://ptob.dev/blog/"},{"@type":"ListItem","position":3,"name":"The precision clock hiding in every USB port","item":"https://ptob.dev/blog/usb-frame-timing/"}]},{"@type":"Blog","@id":"https://ptob.dev/blog/#blog","url":"https://ptob.dev/blog/","name":"PToB Blog","description":"Engineering notes on shared time, inexpensive hardware and the experiments behind PToB.","inLanguage":"en","publisher":{"@id":"https://ptob.dev/#jonathan-yantis"},"isPartOf":{"@id":"https://ptob.dev/#website"},"blogPost":[{"@id":"https://ptob.dev/blog/usb-frame-timing/#article"},{"@id":"https://ptob.dev/blog/lora-wwvb-twatch-ultra/#article"},{"@id":"https://ptob.dev/blog/esp32-wireless-softpll/#article"},{"@id":"https://ptob.dev/blog/esp32-clock-fundamentals/#article"},{"@id":"https://ptob.dev/blog/firmware-stability-time-mesh/#article"},{"@id":"https://ptob.dev/blog/lab-sensor-timing-economics/#article"},{"@id":"https://ptob.dev/blog/starlink-local-stratum-1-ntp/#article"},{"@id":"https://ptob.dev/blog/raspberry-pi-ptp-ntp-ble/#article"},{"@id":"https://ptob.dev/blog/gnss-resilient-time-mesh/#article"},{"@id":"https://ptob.dev/blog/passive-lora-channel-hopping/#article"},{"@id":"https://ptob.dev/blog/esp32-sub-microsecond-holdover/#article"},{"@id":"https://ptob.dev/blog/local-time-utc-mesh/#article"},{"@id":"https://ptob.dev/blog/grandmaster-failover-multi-master-ensemble/#article"},{"@id":"https://ptob.dev/blog/ble-clocks-indoor-navigation/#article"},{"@id":"https://ptob.dev/blog/passive-ble-esp32/#article"},{"@id":"https://ptob.dev/blog/why-utc/#article"},{"@id":"https://ptob.dev/blog/why-ptob/#article"}]},{"@type":"BlogPosting","@id":"https://ptob.dev/blog/usb-frame-timing/#article","url":"https://ptob.dev/blog/usb-frame-timing/","headline":"The precision clock hiding in every USB port","description":"Every USB connection keeps a steady 1 ms beat. Early PToB experiments on a Mac and a Raspberry Pi suggest it could carry far finer time than its reputation allows.","mainEntityOfPage":{"@id":"https://ptob.dev/blog/usb-frame-timing/#webpage"},"isPartOf":{"@id":"https://ptob.dev/blog/#blog"},"author":{"@id":"https://ptob.dev/#jonathan-yantis"},"publisher":{"@id":"https://ptob.dev/#jonathan-yantis"},"inLanguage":"en","dateCreated":"2026-11-18T00:00:00.000Z","dateModified":"2026-11-18T00:00:00.000Z","datePublished":"2026-11-18T00:00:00.000Z","image":"https://ptob.dev/blog/usb-frame-timing-v1.jpg","articleSection":"USB time transfer","keywords":["USB SOF","macOS","Raspberry Pi","PPS","chrony"],"wordCount":2396,"citation":[{"@type":"CreativeWork","name":"USB-IF · Universal Serial Bus 2.0 Specification","url":"https://www.usb.org/document-library/usb-20-specification"},{"@type":"CreativeWork","name":"Nordic Semiconductor · nRF52840 USBD peripheral","url":"https://docs.nordicsemi.com/bundle/ps_nrf52840/page/usbd.html"},{"@type":"CreativeWork","name":"PToB · Experimental macOS client","url":"https://github.com/yantisj2/PToB/tree/64661053f1f49c681a025dd1fb7196eaae7d7d23/clients/macos"},{"@type":"CreativeWork","name":"PToB · Raspberry Pi 5 gateway","url":"https://github.com/yantisj2/PToB/tree/64661053f1f49c681a025dd1fb7196eaae7d7d23/gateways/pi5"},{"@type":"CreativeWork","name":"Linux kernel · USB host-side API","url":"https://docs.kernel.org/driver-api/usb/usb.html"},{"@type":"CreativeWork","name":"Raspberry Pi · piolib, a userspace library for PIO control","url":"https://www.raspberrypi.com/news/piolib-a-userspace-library-for-pio-control/"}],"about":{"@id":"https://ptob.dev/#protocol"}}]}],"content":{"mediaType":"text/markdown","headings":[{"level":1,"text":"The precision clock hiding in every USB port","url":"https://ptob.dev/blog/usb-frame-timing/#main"},{"level":2,"text":"USB keeps a steady beat","url":"https://ptob.dev/blog/usb-frame-timing/#usb-keeps-a-steady-beat"},{"level":2,"text":"A first look on a Mac","url":"https://ptob.dev/blog/usb-frame-timing/#a-first-look-on-a-mac"},{"level":2,"text":"A second opinion from a Raspberry Pi","url":"https://ptob.dev/blog/usb-frame-timing/#a-second-opinion-from-a-raspberry-pi"},{"level":2,"text":"Why USB timing could be worth it","url":"https://ptob.dev/blog/usb-frame-timing/#why-usb-timing-could-be-worth-it"},{"level":2,"text":"Questions worth the next round of research","url":"https://ptob.dev/blog/usb-frame-timing/#questions-worth-the-next-round-of-research"},{"level":2,"text":"Explore the details","url":"https://ptob.dev/blog/usb-frame-timing/#related-title"},{"level":3,"text":"Frame-identified USB time transfer to macOS","url":"https://ptob.dev/blog/usb-frame-timing/#main"},{"level":3,"text":"Connecting a Raspberry Pi to the time mesh","url":"https://ptob.dev/blog/usb-frame-timing/#main"},{"level":3,"text":"The RP5 gateway guide","url":"https://ptob.dev/blog/usb-frame-timing/#main"},{"level":2,"text":"Sources and further reading","url":"https://ptob.dev/blog/usb-frame-timing/#sources-title"},{"level":2,"text":"Cite this article","url":"https://ptob.dev/blog/usb-frame-timing/#cite-title"}],"links":[{"text":"Jonathan Yantis","url":"https://github.com/yantisj2/PToB/blob/main/CREDITS.md"},{"text":"The USB 2.0 specification","url":"https://ptob.dev/blog/usb-frame-timing/#source-usb2"},{"text":"Nordic’s USB peripheral","url":"https://ptob.dev/blog/usb-frame-timing/#source-nordic"},{"text":"experimental Mac client","url":"https://ptob.dev/blog/usb-frame-timing/#source-mac-client"},{"text":"Mac study","url":"https://ptob.dev/research/usb-macos-time-transfer/"},{"text":"selected results","url":"https://ptob.dev/research/#pi5-usb-sof"},{"text":"Raspberry Pi’s piolib","url":"https://ptob.dev/blog/usb-frame-timing/#source-piolib"},{"text":"Pi gateway","url":"https://ptob.dev/blog/raspberry-pi-ptp-ntp-ble/"},{"text":"USB host-side API","url":"https://ptob.dev/blog/usb-frame-timing/#source-linux-usb"},{"text":"Mac study","url":"https://ptob.dev/research/usb-macos-time-transfer/"},{"text":"Pi gateway tools","url":"https://ptob.dev/blog/usb-frame-timing/#source-pi-gateway"},{"text":"Mac client source","url":"https://ptob.dev/blog/usb-frame-timing/#source-mac-client"},{"text":"Frame-identified USB time transfer to macOS The research paper behind the Mac results, with its measurement definitions and limits.","url":"https://ptob.dev/research/usb-macos-time-transfer/"},{"text":"Connecting a Raspberry Pi to the time mesh How the nRF52 HAT brings BLE time to a Pi through a PPS pin, and on to NTP and PTP.","url":"https://ptob.dev/blog/raspberry-pi-ptp-ntp-ble/"},{"text":"The RP5 gateway guide Hardware, setup and monitoring for the Raspberry Pi 5 timing gateway.","url":"https://ptob.dev/hardware/#rp5"},{"text":"USB-IF · Universal Serial Bus 2.0 Specification","url":"https://www.usb.org/document-library/usb-20-specification"},{"text":"Nordic Semiconductor · nRF52840 USBD peripheral","url":"https://docs.nordicsemi.com/bundle/ps_nrf52840/page/usbd.html"},{"text":"PToB · Experimental macOS client","url":"https://github.com/yantisj2/PToB/tree/64661053f1f49c681a025dd1fb7196eaae7d7d23/clients/macos"},{"text":"PToB · Raspberry Pi 5 gateway","url":"https://github.com/yantisj2/PToB/tree/64661053f1f49c681a025dd1fb7196eaae7d7d23/gateways/pi5"},{"text":"Linux kernel · USB host-side API","url":"https://docs.kernel.org/driver-api/usb/usb.html"},{"text":"Raspberry Pi · piolib, a userspace library for PIO control","url":"https://www.raspberrypi.com/news/piolib-a-userspace-library-for-pio-control/"},{"text":"https://ptob.dev/blog/usb-frame-timing/","url":"https://ptob.dev/blog/usb-frame-timing/"},{"text":"Back to the blog","url":"https://ptob.dev/blog/"},{"text":"Inspect the project evidence","url":"https://github.com/yantisj2/PToB/blob/main/evidence/README.md"}],"text":"# The precision clock hiding in every USB port\n\nMost computers already have the connector. We set out to learn how much time it can carry, and found questions worth a closer look.\n\n[Jonathan Yantis](https://github.com/yantisj2/PToB/blob/main/CREDITS.md) 18 November 2026  7 min read\n\n![A host computer and a small PToB clock joined by a USB cable with evenly spaced start-of-frame marks. Below, both clocks record the same frame.](https://ptob.dev/blog/usb-frame-timing-v1.svg)\n\nConcept diagram. A USB host marks the start of every 1 ms frame, and both the host and the device can record when the same frame began.\n\nIn this post\n\nPlug a GPS receiver into a computer over USB and ask a timing enthusiast how good its time will be. The usual answer is: not very. Data from a USB serial adapter arrives whenever the host gets around to collecting it, and a pulse-per-second (PPS) signal routed that way is often quoted with around a millisecond of uncertainty. For serious timing, the advice goes, use a dedicated pin.\n\nThat advice is about packets. USB has another signal that gets far less attention: a steady beat that the host sends to every device on the bus. We wanted to know how much time that beat can carry. Early experiments on a Mac and a Raspberry Pi suggest it could be a great deal more than USB’s reputation allows.\n\n## USB keeps a steady beat\n\nA full-speed USB host divides time into 1 ms frames. At the start of each one it sends a short, numbered start-of-frame marker to every device on the bus. [The USB 2.0 specification](https://ptob.dev/blog/usb-frame-timing/#source-usb2) defines this schedule. Data packets travel inside those frames when the host is ready to send or collect them, so their arrival times wander. The frame markers themselves keep to the schedule.\n\nThink of a railway station. Passengers turn up whenever they turn up, but the station clock ticks for everyone on the platform. If you want the time, you look at the clock rather than the passengers.\n\nConcept diagram. Data packets arrive when the host gets to them. Start-of-frame markers arrive on an even schedule.\n\nThe nRF52840 inside our T096 clocks can capture each start-of-frame marker in hardware, without waiting for its software to notice. [Nordic’s USB peripheral](https://ptob.dev/blog/usb-frame-timing/#source-nordic) signals the frame, and a timer records the clock’s own tick at that instant. If the host can also say when the same numbered frame began on its clock, the two readings describe one moment from both sides.\n\nConcept diagram. The device and the host each note when frame 812 began on their own clocks. Together, the two readings form a matching pair.\n\nCollect enough of those pairs and you can convert readings between the two clocks, much as our Bluetooth receivers do with radio events. The 1 ms spacing then stops limiting precision. Each pair marks a precise moment, and the frames supply a steady stream of them.\n\n## A first look on a Mac\n\nmacOS lets software ask which frame the bus is on and when that frame began on the Mac’s own high-resolution clock. Our [experimental Mac client](https://ptob.dev/blog/usb-frame-timing/#source-mac-client) uses that answer to pair frames with a PToB clock. It then feeds the result to a private copy of chrony and leaves the system clock alone.\n\nIn a three-minute window in October, two PToB clocks sharing one USB bus on the same Mac reached a few hundred nanoseconds. For the two clocks, the Mac predicted each new frame observation with errors of about 190 and 270 nanoseconds RMS. That is a long way from the milliseconds USB timing is usually associated with. The [Mac study](https://ptob.dev/research/usb-macos-time-transfer/) explains how each figure was measured.\n\nThere was a catch. Everything we compared on the Mac came from the same source. It could show how consistent the chain was, but not whether something along the way had shifted every reading together. We needed a second opinion.\n\n## A second opinion from a Raspberry Pi\n\nA Raspberry Pi 5 gave us a way to get one. We connected a PToB clock to the Pi over USB and tried the same frame-matching idea there. That clock and the nRF52 HAT on the Pi both followed the same grandmaster over Bluetooth, and the HAT turns its time into a PPS signal on a GPIO pin. That gave the Pi two separate roads from one reference clock.\n\nConcept diagram. Both roads start at one reference clock and cross Bluetooth. One continues through a PToB clock and USB; the other through the nRF52 HAT and a PPS pin.\n\nEach road compares the reference with the Pi’s clock, but from opposite directions. The USB road measures the reference minus the Pi. The PPS road measures the Pi minus the reference. If the Pi’s clock drifts, both roads see the same movement with opposite signs. Add the two results and the Pi’s own wander cancels, leaving only how well the roads agree with each other.\n\nThe result surprised us. On its own, each road appeared to wobble by about 7 microseconds RMS. The two wobbled as near mirror images, with a correlation of 0.99, so most of what looked like transport error was the Pi’s clock moving underneath both measurements. With that shared motion removed, the USB and PPS roads agreed to about 1.1 microseconds RMS over 280 matched seconds. The [selected results](https://ptob.dev/research/#pi5-usb-sof) explain how this exploratory run was measured and what it cannot show.\n\nIllustrative traces, not measured data. The two roads wander in opposite directions, so adding them removes the Pi’s own clock movement.\n\nA second measurement pointed the same way. The Pi 5’s RP1 chip has small programmable I/O state machines that can time a pin on their own clock, without waiting for Linux. [Raspberry Pi’s piolib](https://ptob.dev/blog/usb-frame-timing/#source-piolib) makes them available to ordinary programs. Timed that way, the one-second period of the PPS pulse varied by about 43 nanoseconds in a one-minute window. Linux’s interrupt timestamps for the same pulses varied by about 830 nanoseconds.\n\nMeasured on the Pi 5: the standard deviation of the PPS period in one short window, timed two ways. Much of the noise comes from how the host listens.\n\nMuch of the noise, in other words, lives in how the host listens rather than in the signal itself. That is encouraging for USB. The frame markers may already be steadier than the clocks we currently use to read them.\n\n## Why USB timing could be worth it\n\nMost computers have no PPS pin. Laptops and desktops rarely expose one, and network cards with hardware timestamping can cost far more than the clocks they would serve. Nearly every computer has USB.\n\nIf frame-matched time holds up, a small and inexpensive clock could plug into whatever host is nearby: a laptop on a lab bench, a single-board computer in a sensor rack, a recording rig that needs audio and video aligned, a software-defined radio or a robot’s main computer. That computer could then pass the time on to the rest of a network over NTP or PTP, the role our [Pi gateway](https://ptob.dev/blog/raspberry-pi-ptp-ntp-ble/) already explores through its PPS pin.\n\n## Questions worth the next round of research\n\nOur runs so far are short and early. They measure relative timing, meaning how well clocks agree with a shared reference, rather than how close any of them is to UTC. These are the questions we would most like to answer next.\n\n- **Can Linux see frames as clearly as macOS?** We could not find a Linux equivalent of the Mac’s frame-time query in the [USB host-side API](https://ptob.dev/blog/usb-frame-timing/#source-linux-usb). On the Pi, we estimate frame timing from repeated reads of the host controller’s frame counter, which costs precision. A small kernel interface could close that gap.\n- **Can both ends always agree on the frame?** A small number of Pi observations close to a frame boundary did not line up as expected. Settling exactly which frame each side saw is the foundation for everything else.\n- **What would an outside judge say?** Comparing the delivered time with an independent reference, such as a time-interval counter and a GNSS-disciplined pulse, would reveal fixed offsets that comparing two roads from one clock cannot.\n- **How far does it reach across the USB world?** Hubs, high-speed devices with their 125 µs microframes, Windows and Android hosts, and other microcontrollers that can capture frames all deserve a look.\n- **How does it behave over days?** Long runs would test reconnects, sleep and resume, and busy buses.\n\nUSB is often the first interface people rule out for timing. These early results suggest it deserves another look. If you have a time-interval counter, an unusual USB host or experience with the Linux USB stack, we would love to compare notes. The [Mac study](https://ptob.dev/research/usb-macos-time-transfer/), the [Pi gateway tools](https://ptob.dev/blog/usb-frame-timing/#source-pi-gateway) and the [Mac client source](https://ptob.dev/blog/usb-frame-timing/#source-mac-client) are good places to start.\n\nEvery timestamp needs a reference.\n**Which event did you capture?**\n\n## Explore the details\n\n[Frame-identified USB time transfer to macOS The research paper behind the Mac results, with its measurement definitions and limits.](https://ptob.dev/research/usb-macos-time-transfer/)[Connecting a Raspberry Pi to the time mesh How the nRF52 HAT brings BLE time to a Pi through a PPS pin, and on to NTP and PTP.](https://ptob.dev/blog/raspberry-pi-ptp-ntp-ble/)[The RP5 gateway guide Hardware, setup and monitoring for the Raspberry Pi 5 timing gateway.](https://ptob.dev/hardware/#rp5)\n\n## Sources and further reading\n\nPrimary references for the hardware and methods discussed.\n\n1. [USB-IF · Universal Serial Bus 2.0 Specification](https://www.usb.org/document-library/usb-20-specification)\n\n   Defines the 1 ms full-speed frame, the 125 µs high-speed microframe and the start-of-frame packet.\n2. [Nordic Semiconductor · nRF52840 USBD peripheral](https://docs.nordicsemi.com/bundle/ps_nrf52840/page/usbd.html)\n\n   The USB device controller in our T096 clocks, including its start-of-frame event and frame counter.\n3. [PToB · Experimental macOS client](https://github.com/yantisj2/PToB/tree/64661053f1f49c681a025dd1fb7196eaae7d7d23/clients/macos)\n\n   Pairs captured frames with the Mac’s host clock and feeds a private chrony instance.\n4. [PToB · Raspberry Pi 5 gateway](https://github.com/yantisj2/PToB/tree/64661053f1f49c681a025dd1fb7196eaae7d7d23/gateways/pi5)\n\n   Setup, PPS capture and monitoring tools for the Pi 5 and its nRF52 HAT.\n5. [Linux kernel · USB host-side API](https://docs.kernel.org/driver-api/usb/usb.html)\n\n   How Linux schedules USB transfers and reports their completion to drivers and applications.\n6. [Raspberry Pi · piolib, a userspace library for PIO control](https://www.raspberrypi.com/news/piolib-a-userspace-library-for-pio-control/)\n\n   The RP1 programmable I/O used to time the PPS pin on its own clock.\n\n## Cite this article\n\nJonathan Yantis. The precision clock hiding in every USB port PToB Blog. Published 18 November 2026.\n\nArticle permalink: [https://ptob.dev/blog/usb-frame-timing/](https://ptob.dev/blog/usb-frame-timing/)\n\n[Back to the blog](https://ptob.dev/blog/)[Inspect the project evidence](https://github.com/yantisj2/PToB/blob/main/evidence/README.md)"}}
