Crypto is a payment method, not an identity exemption
Knowing how a payment moves does not tell you what an operator must know about the account holder. A website can accept a blockchain transfer and still require identity, address or source-of-funds evidence. A short registration form does not prove that these checks will never occur.
Read the trigger and the consequence
Useful questions are when checks can happen, what documents can be requested and which functions may be restricted until the review is complete. For example, the linked Stake and Shuffle terms reserve verification powers. Their precise wording and triggers should be read in the current contract rather than reduced to a simple yes-or-no label.
A comparison field saying “KYC required” leaves several issues unresolved: whether checks occur before a payment, before withdrawal, at a threshold or in response to a risk assessment. Record the actual condition and its source date.
Distinguish different kinds of evidence
- Identity: establishing who the account holder is.
- Address or location: determining a relevant residence or presence.
- Payment ownership: connecting a financial method to the account holder.
- Source of funds: explaining where specific money originated.
Completing one category does not necessarily settle the rest. Equally, an operator should explain a request through its authenticated channels; an unsolicited message asking for private keys is not a legitimate identity check.
Protect the documents and keep records
Check the domain before uploading anything. Keep a record of the request, the date and any case reference, but do not publish identity documents in a review or complaint. If the terms are unclear, ask the operator for an explanation before relying on the service. Never use someone else’s documents or attempt to conceal a restricted location.
For related concepts, read how to interpret no-KYC claims and account-security basics.