Compliance for Blockchain and Web3 Developers
Blockchain compliance is the legal and risk side of running a Web3 product. It includes how regulators treat tokens, know-your-customer and anti-money-laundering duties, sanctions screening, consumer disclosures, and operational risks like custody and smart contract failure. Rules differ by country and change often, so teams seek legal advice.
Stage: Production · Part of the Blockchain and Web3 Developer roadmap · Last reviewed 19 November 2026
What to learn in Compliance
- Explain why a token's legal classification depends on its features and jurisdiction
- Describe what KYC and AML checks involve for a crypto service
- List the main risk categories for a protocol: contract, oracle, governance, custody
- Write a plain-language risk disclosure for users
- Recognise when to involve legal counsel before launching
Compliance interview questions
Does decentralisation remove a project's legal obligations?
Not automatically. Regulators look at who controls the product, who profits and who markets it, not only at where code runs. A team with admin keys or a company running the frontend may still face licensing, tax and disclosure duties.
What is KYC and why do some crypto services require it?
Know your customer means verifying a user's identity before offering a service. Regulated exchanges and some on-ramps must do it to meet anti-money-laundering and sanctions laws. Fully permissionless contracts do not check identity, but fiat gateways usually do.
Where Compliance fits in the Blockchain and Web3 Developer roadmap
Compliance belongs to the Production stage (advanced level), which takes about 4 hours. Operate on mainnet.
Other units in this stage
Back to the full Blockchain and Web3 Developer roadmap