CRUMBS / incident record
CRUMBS / incident record
This page documents what happened after a cloned PCT Wallet Monitor appeared on Zyrachain's testnet. The developers were given multiple opportunities to acknowledge where the work came from. What followed was denial, deleted replies, contradictory explanations, quietly altered values, and eventual silence — once the evidence became impossible to reasonably explain away.
The Crumbs ecosystem has existed publicly since August 2025, originally at picrumbs.online, then migrated to crumbs.host around December 2025. The same dark terminal aesthetic, green-on-black colour scheme, and monospace design language have been present throughout — preserved in Wayback Machine archives before Zyrachain's monitor existed.
The PCT Wallet Balance Monitor was built from scratch starting April 25, 2026, with every development decision documented in real time across a Discord server. The full log exists. Every line of reasoning, every tool decision, every engineering choice that produced the monitor's structure, terminology, and data model is timestamped and preserved.
Zyrachain's PCT monitor appeared weeks later. Built in Next.js/TypeScript rather than PHP, but the dashboard structure, metric card order, column names, terminology, and two specific implementation details are identical — including one phrase coined during a specific Discord message, and one number that was never correct and only visible during a brief test build window.
The similarities were obvious immediately. Same telemetry styling, same dashboard flow, same metrics ordering, same card structure, same green-on-black presentation. The original public response was restrained. At that stage a simple acknowledgement was all that was expected.
What came back instead was a denial — "we rebranded, it has nothing to do with yours" — and a claim that Dappify (which became Zyrachain) had existed since June 2025. The replies were deleted shortly after.
That claim created another problem.
If Dappify and Zyrachain had an established public ecosystem dating back to June 2025, there should be an observable public development trail: live archived pages, captured dashboards, historical UI evolution, or preserved testnet deployments.
The Wayback Machine shows the opposite.
The contrast matters.
PiCrumbs and Crumbs show visible historical progression preserved publicly across multiple captures. The monitor ecosystem evolved in public and can be independently verified through archived snapshots.
Meanwhile there are no archived captures showing an earlier Zyrachain monitor, no historical telemetry builds, no earlier public evolution trail, and no evidence of a comparable system existing before the Crumbs monitor work.
Every decision made during the build of the PCT Wallet Balance Monitor was discussed in Discord and is preserved with timestamps. From the first Python crawler to the production monitor with VPS scanning, Horizon verification, CEX outflow tracking, and hop analysis. This is not a reconstruction. It is the original log, unedited.
Zyrachain is not anonymous. The person behind it publicly associates with multiple Pi ecosystem projects. The denial came from this account publicly, and privately over Telegram. Their identity and public standing in the Pi ecosystem are directly relevant to why this documentation matters.
Similar dashboards can happen. Similar tools can happen. Similar visual styles can happen. None of those are the point.
What does not happen naturally is two unrelated developers independently inventing the exact same proprietary subtitle phrase and the exact same incorrect hardcoded placeholder value.
"Confirmed balance changes only. VPS scans, Horizon confirms."
This phrase describes a very specific two-step architecture: fast public VPS scanning to identify candidate changes, followed by Horizon API confirmation before writing to the database. It came from a specific engineering decision documented in Discord on May 2. There is no way to independently arrive at this phrase without independently building the same architecture and independently choosing the same words to describe it.
This challenge was issued publicly. No explanation was given.
The PCT starting balance of 20,002,010,001.00 π was a temporary hardcoded placeholder. It was never correct. Never retrievable from Horizon. Never the result of any calculation. It was manually entered during development, identified as wrong on May 11th, and corrected. Zyrachain's monitor displayed this exact number. Their API returned it. It only changed after being publicly exposed.
Most responses focused on the balance value — whether it was hardcoded, mathematically generated, or calculated differently. What was consistently avoided was the larger issue: the matching subtitle phrase, the matching telemetry wording, the matching dashboard structure, and the appearance of both fingerprints together.
"Confirmed balance changes only. VPS scans, Horizon confirms."
"startingBalance":20002010001 returned from their own live endpoint. Static. Not calculated. Their own server confirming the copied placeholder.
After the placeholder balance was publicly exposed, the live values changed. The problem for the denial narrative was simple: the original number should never have existed there, the replacement values were also incorrect, and the changes only happened after confrontation.
The claim that the starting balance was calculated mathematically was disproved by a direct call to their own live API. The value returned was static — not calculated, not from Horizon. It was the exact placeholder from the Crumbs test build, served unchanged from their backend.
Note: every field name — walletsTracked, startingBalance, currentBalance, confirmedChanges, totalOut, netChange24h — is identical to the Crumbs PHP data model. The TypeScript interface in their public GitHub matches field for field.
The layout was replicated. The terminology was replicated. The data model was replicated. What was not replicated — because it cannot be scraped from a webpage or converted by an AI tool — is the backend infrastructure that actually produces the data.
"Confirmed balance changes only. VPS scans, Horizon confirms."
The evidence was assessed independently by multiple parties who reached the same conclusion without being led there.
"This is a classic case of copying someone else's work (including UI/phrasing), inheriting their bug (hardcoded or cached wrong value), then quietly patching it while denying it. The 'independent math' excuse fails when the number only changed after public exposure of the mismatch. Bulbybot has receipts."
"The order and terminology are identical while the underlying code language differs. That is consistent with the original HTML being processed through an AI code conversion tool. The field names, column headers, metric card order and crucially the hardcoded wrong number all came from the Crumbs PHP source."
(Story based on real events)
A documented meme investigation covering the cloned PCT monitor, copied implementation fingerprints, API evidence, placeholder edits, panic patches, deleted replies, and the excuses that followed.
Includes archived screenshots, Telegram conversations, API responses, blockchain verification, placeholder edits, timeline records, and implementation fingerprint analysis.
The copy itself was not the issue that turned this into a documented record. People build on others' work. That is normal. A shoutout, an attribution, an honest "I built on top of what you made" — any of those would have ended this before it started.
What created this page was the denial. Claiming "we don't copy anyone" when two specific implementation fingerprints — one a phrase coined in a Discord message at 11:25pm on May 2nd, one a number that was never correct and never publicly accessible after May 11th — are sitting live on your website is not something that holds up against a timestamped build log.
Independent developers operate on reputation and trust within the communities they build for. Taking work without credit is one thing. Taking it and then calling the original developer a liar when they ask for acknowledgement is another.
The build history was documented before any of this happened. The evidence existed before it was needed. This page exists because acknowledgement was repeatedly refused after it became impossible to reasonably deny.
"Fair play, I liked what you built and used it as a base — should have given you credit, sorry."
A visual timeline of the documented build history, copied implementation fingerprints, deleted replies, API contradictions, and archived evidence.
