CRYPTOKASHYAP · EVIDENCE STANDARD
Sources & Verification
How CryptoKashyap separates project claims from evidence that can actually be checked – with particular focus on mining apps, cloud-mining services and crypto reward platforms.
Last updated: November 6, 2026
OUR STANDARD
Evidence comes before conclusions.
An app balance, marketing statement or promised withdrawal is not automatically proof that real mining is taking place. We identify what a project says, test what can be tested, and clearly distinguish confirmed facts from unresolved claims.
01 · PRIMARY EVIDENCE
Direct, first-party evidence
Blockchain transactions, official app-store listings, published terms, contracts, fee schedules, technical documentation and direct observations.02 · INDEPENDENT EVIDENCE
Evidence that can be checked
Reproducible tests, transaction explorers, independently checkable records and credible third-party technical evidence.03 · USER REPORTS
Patterns, not automatic proof
User reviews and community reports can reveal useful patterns, but individual reports are treated as reports rather than definitive proof.04 · PROJECT CLAIMS
Claims stay labelled as claims
Developer statements and marketing material are identified as claims unless the underlying information can be independently verified.WHAT WE CHECK
Verification follows the product.
The exact checks vary by app, service or platform. We focus on the evidence that matters most to the specific claim being investigated.
Identity & history
Developer identity, app-store history, listing changes and relevant platform information.Mining mechanism
Claimed mining model, hashrate presentation, token mechanics and whether the stated mechanism is technically plausible.Withdrawals & transactions
Minimum withdrawals, wallet addresses, transaction evidence, fees and available blockchain records.Risk & access
KYC requirements, referral mechanics, permissions, Data Safety disclosures and recent user reports.EVIDENCE STATUS
What our verification labels mean
Independently confirmed
The specific fact or transaction could be independently confirmed using available evidence.Some evidence, material gaps remain
Important elements were confirmed, but meaningful gaps remain in the evidence.Not independently confirmed
We could not independently confirm the claim from the evidence available to us.Evidence status is not a safety guarantee
These labels describe the strength of available evidence. They are not guarantees of safety, profitability or future performance.App listings, minimum withdrawals, fees, contracts and token status can change. A finding is therefore tied to the evidence available at the time of review.
TRANSPARENCY
When evidence is unavailable, we say so.
We may not always be able to make a test withdrawal or access private technical infrastructure. Rather than filling those gaps with assumptions, CryptoKashyap identifies the limitation and keeps the conclusion proportionate to the available evidence.
Read Our Review Methodology →
Editorial Policy →
Contact CryptoKashyap →
Source hierarchy and conflict checks
We begin with the source closest to the claim. For a product feature, that is usually the current official product page or help document. For a legal entity, it may be a company registry or regulatory filing. For a blockchain payment, it is the relevant network explorer and transaction data. Independent technical documentation can help assess whether a mechanism is plausible.
Sources are not interchangeable. A company’s terms can show what it promises, but they do not prove it has delivered the service. A company filing can establish that a document was filed, but it does not guarantee that a customer contract is profitable. User reviews can identify recurring complaints, but an individual report is not proof that every customer had the same experience.
What we do when sources disagree
We check that the sources refer to the same company, domain, app publisher, product, country and time period. We note publication or update dates where available. If the provider’s marketing page conflicts with its terms, the article should describe the difference rather than selecting the more attractive statement. If an old help article may no longer reflect current fees, we label it as historical and direct readers to confirm the live terms.
What a blockchain record can prove
A transaction ID can help confirm that a particular transaction was broadcast and recorded on the named network. Readers should check the asset, amount, destination and confirmation status. A transaction alone does not prove who controlled the sending wallet, why the payment was made, whether it came from mining revenue or whether the provider can continue paying customers. If no independently checkable record is available, we say that the payout claim remains unverified.
Verification scope and limits
Verification is claim-specific. Before assigning an evidence status, we ask what exactly needs to be established, which entity or product the claim concerns, and what evidence would reasonably support it. A confirmed fact should not be stretched into a broader conclusion.
Identity is not legitimacy
A company record, domain registration or app publisher name may help identify an operator. None of these alone proves that a service is safe, solvent, properly licensed for every activity or able to meet its promises.
App availability is not performance
An active app-store listing can confirm that an app is listed at the time checked. It does not prove that advertised mining, rewards, withdrawals or other functions operate as described.
One payment is not a payment history
A verifiable transaction can support the claim that a particular transfer occurred. It cannot establish that all users can withdraw, that payments are sustainable or that future withdrawals will succeed.
Evidence has a time and context
We consider the date, country, product version, network and account conditions attached to a source. Where these details are unclear, we avoid presenting the evidence as universally applicable.
Reader takeaway: Read each evidence label alongside the exact claim it covers, the date checked and any stated limitations. A label is not a recommendation or a safety rating.
To challenge a source or provide new evidence, include the page URL, the claim, the source link or transaction reference, and the relevant date through our contact page. Material corrections are handled under the Corrections Policy.