# Recognition & validation
This page collects examples where our public work, findings, or investigation methods were later validated, referenced, or reinforced by broader industry attention.
## WhiteRock Finance investigation referenced in later ZachXBT coverage
In June 2025, Blokiments published an in-depth investigation into WhiteRock Finance after reviewing the project between June 5 and June 13, 2025. The report highlighted multiple red flags, including unverifiable partnership claims, a 9-day unnoticed outage of the project’s core product, proxy-based token contracts, concerns around USDX backing, and a mismatch between the public narrative and observed platform usage.
Later, public scrutiny around WhiteRock intensified as ZachXBT raised concerns about possible links between WhiteRock and the ZKasino scam. CryptoSlate’s reporting on that development explicitly stated that “ZachXBT and Blokiments revealed on-chain data and potential personal links connecting both projects.”
This is an early example of Blokiments publishing meaningful public risk research before a project was more broadly exposed.
**Why this matters:**
* Blokiments published its findings before wider public exposure.
* The investigation focused on concrete on-chain and project-level red flags.
* Later reporting connected Blokiments’ work to broader scrutiny of the project.
**References:**
* [ZachXBT Whiterock Thread](https://x.com/zachxbt/status/1934616651087102382)
* [WhiteRock Finance investigation by Blokiments](https://docs.blokiments.com/investigations/in-depth-whiterock-finance)
* [CryptoSlate coverage of ZachXBT’s WhiteRock / ZKasino warning](https://cryptoslate.com/zachxbt-warns-suspected-zkasino-fraudster-may-be-linked-to-new-crypto-venture-whiterock/?utm_source=chatgpt.com)
## Notes
Public inv~~e~~stigations are based on the information and on-chain evidence available at the time of review. This page documents cases where Blokiments’ public research surfaced meaningful concerns early or was later reinforced by broader reporting.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.blokiments.com/recognition-and-validation.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.