Record reproducible facts
Keep transaction signatures, UTC timestamps, original URLs and the provenance of screenshots or exported messages.
ProbeLedger organizes documented transactions, infrastructure traces and public statements into verifiable community case files. Allegations stay allegations. Attribution requires evidence.
Keep transaction signatures, UTC timestamps, original URLs and the provenance of screenshots or exported messages.
Confirmed observations, strong or moderate leads, unverified claims and speculative hypotheses are not interchangeable.
A transfer does not prove wallet ownership. An exchange hot-wallet label does not identify its customer. Similar usernames do not identify a person.
Preliminary public-facing digest, based on an investigation dossier dated 7 October 2026. The dossier distinguishes on-chain observations from project representatives’ claims. Independent, live revalidation of every historical event is still pending.
PHNX project communications alleged that a developer known by the alias chwazir had handled project funds and that team tokens were sold. Those statements are project-side allegations, not proof of who controlled a wallet or an exchange account.
Primary transaction reference: View 12.27415 SOL transaction on Solscan ↗
Create your own factual draft for your local police or fraud-reporting authority. This tool does not file a complaint, verify personal claims, or send your answers to ProbeLedger. Only type information you are comfortable storing on your own device.
Nothing entered in these fields is transmitted by this page. The report downloads as a plain-text file. Clear the draft when finished, especially on shared devices.
Important: Do not submit a report based solely on this page. Confirm transaction facts independently, attach original evidence through the authority's official channel, and describe the alleged controller's identity as unverified. Never upload wallet recovery phrases or exchange passwords.
The October 7 dossier records a certificate-transparency timestamp of 12:16:21 UTC. This is infrastructure chronology, not proof of who owned the deployment.
Preserved project messages say users noticed another product appearing on the PHNX site; a reply attributed to the developer alias said “My fault” and “Will fix asap.” This supports operational involvement, not ownership of any third-party product.
The dossier documents a pattern of transfers through H8vYdRRMgZUrR3JDmyBtDa4FzZgq9fVGhhaf2VKYYq3P to 2UL8hbNaoErAYNePqgQYPP9yDCDRZGWbzKW4krLqkhNL, labelled on Solscan as a Bitvavo hot wallet.
A cited transaction shows 12.27415 SOL deposited at 13:13:55 UTC. Project representatives separately alleged lost funds and operational disruptions. Neither statement alone establishes human attribution.
The dossier reports unavailable Vercel and Railway deployments. Similarity of hosting providers or IPs is not evidence of common control.
| Observation or claim | Current classification | What would strengthen it? |
|---|---|---|
| 12.27415 SOL transfer, 6 Oct | Transaction documented in the dossier; explorer link supplied | Independent chain re-query and preserved raw transaction data |
| Repeated consolidation into the labelled hot wallet | Documented pattern in a limited transaction window | Full backward funding tree and complete transaction export |
| chwazir controlled specific wallets | Unverified project-side attribution | Cryptographic proof or independently corroborated operational records |
| ~197.543M PHNX sold came from team allocation | Open hypothesis | Mint, allocation wallet and full token provenance |
| Exchange account holder identified | Not established | Authorized exchange / law-enforcement confirmation |
Evidence basis: “PHNX / Pyre combined study”, 7 October 2026, sections 2–7 (investigation working dossier). This preview does not publish the original private chat export, private correspondence, or an unredacted incident archive. External explorer labels are third-party claims and may change. A downloadable redacted evidence bundle is planned after a publication review.
This version has no account registration, user uploads, comments or server-side loss-estimate submissions. The report builder runs in your browser and does not send entered data to this site. No third-party analytics scripts are embedded. Standard network providers may still process request metadata, including IP addresses, to deliver the site. We cannot guarantee anonymity to visitors or administrators.
ProbeLedger provides evidence organization, not a criminal finding or legal advice. If filing a report with law enforcement, verify source materials independently and distinguish witnessed events from third-party allegations.