“Are we compliant with AI regulation?” is too broad to answer. Three smaller questions get you most of the way. Does any component of your product count as an AI system? What role do you play for each one? Where are its outputs used?
For most product teams in November 2026, the answers point to a shorter list than the headlines suggest. The obligations that bind you today are transparency duties plus laws you already live with: data protection, consumer protection and financial regulation. The heavy EU regime for high-risk systems is real, but it starts in December 2027. What matters is knowing which of these lands on your product, and when.
What is in force right now
The EU AI Act reaches any company whose AI outputs are used in the EU, wherever the company is based. Three layers already apply:
Prohibited practices (since February 2025). Social scoring, manipulative techniques that cause significant harm, and certain biometric uses are banned. Few commercial products come near these, but behavioural profiling features deserve a second look.
General purpose model rules (since August 2025). These bind the labs that train foundation models. If you call a hosted model through an API, they reach you mainly through the documentation your vendor owes you.
Transparency under Article 50 (since 2 August 2026). This one touches almost everyone. Users must know when they are talking to an AI system. Deepfakes must be disclosed. Generative systems must mark their outputs in a machine readable way.
One date deserves attention now. If your generative feature was on the market before 2 August 2026, its deadline for machine readable marking is 2 December 2026, a couple of weeks after this was written. Anything launched after 2 August 2026 never had a grace period.
What moved, and what did not
In July 2026 the EU’s Digital Omnibus pushed the high risk obligations back. Stand alone high risk systems, which include credit scoring of individuals, hiring tools and access to essential services, now face the full regime from 2 December 2027. AI built into products already covered by EU safety law moves to 2 August 2028.
The deadline moved. The requirements did not. Risk management, logging, data governance and human oversight are still coming, and logging in particular is an architectural decision. Retrofitting it into a production system costs far more than designing it in.
The United States is less predictable. Colorado replaced its 2024 AI law with a narrower version that takes effect on 1 January 2027. A December 2025 executive order directs federal agencies to challenge state AI laws, but an executive order cannot preempt state law by itself. Plan for state rules to stay in force while that dispute plays out.
Your role decides your obligations
Obligations follow roles. Under the EU framework, a provider puts an AI system on the market under its own name and carries most of the duties. A deployer uses a system professionally and carries lighter ones. A model provider trains or substantially modifies a foundation model.
The same company often holds more than one role. A platform that wraps a third party model in its own investor screening product is a deployer of the model and a provider of the screening system. Write these roles down per component. It is the cheapest compliance document you will ever produce, and the most useful.
Where tokenization platforms get caught
For real world asset platforms, the exposure is rarely the token. It is the decision that sits in front of it.
Take a permissioned token built on ERC3643. The contract enforces transfer rules against verified identity claims. That logic is deterministic and is not an AI system. But if a model decides who receives a claim, by scoring KYC documents, flagging AML risk or judging whether an investor qualifies, that model is where AI rules attach. If it assesses an individual’s creditworthiness, it falls into a named high-risk
category.
So scope the screening pipeline, not just the smart contract. Know which steps are rule based and which are model-driven, and keep a human reviewer on adverse decisions. Your KYC/AML obligations already require that kind of record-keeping, so build the two together.
When blockchain is the wrong tool for AI compliance
A common pitch is to “put AI decisions onchain for auditability.” Usually that is a mistake.
Model inputs and outputs often contain personal data, and an immutable public ledger conflicts with deletion rights. If one company operates the system and is the only party that needs the log, an append-only database with signed entries gives you integrity, access control, and deletion at a fraction of the cost.
A blockchain earns its place when several parties need a shared record, and none of them should have to trust a single operator; for example, an issuer, a transfer agent, and an auditor checking the same eligibility trail. Even then, keep personal data offchain and anchor only hashes or commitments onchain. Be aware that some readings treat a hash of personal data as personal data too.
Agents that hold keys
AI agents that can sign transactions are the sharpest edge here. An agent with a hot key and no limits combines model risk with custody risk, and it sits uneasily with the human oversight the EU rules expect.
Treat agent keys like any other privileged credential. Use HSM- or MPC-backed key management, spending caps, allowlisted destinations, multisig above a threshold, and a pause mechanism you have actually tested. Treat model output as untrusted input before it reaches a contract. Make sure the client, not the vendor, controls those keys.
What to ask a development partner
Whoever builds your platform should be able to answer these plainly:
Which components use trained models, and what role do we hold for each?
Where is logging designed in, and where does personal data live?
Are the smart contracts independently audited before mainnet, by a firm other than the builder?
Who controls the admin keys, upgrade keys, and agent keys after handover?
Do we own the code and IP outright when the engagement ends?
If the answers are vague, the compliance work will be too. Honest scoping at the start is cheaper than a remediation project later.
This article is general information, not legal advice. Confirm your obligations with qualified counsel for each market you serve.
RWaltz is a blockchain and enterprise software development company. It builds smart contracts, dApps, and tokenization platforms on a build to own model, where clients keep their code, IP, and keys, with security and independent audits treated as part of delivery rather than an extra.
📖 Read the full blog: https://www.rwaltz.com/blogs/ai-regulation-for-builders-what-actually-applies-to-you
Connect with RWaltz:
LinkedIn: https://www.linkedin.com/company/rwaltzsoftware
X (Twitter): https://twitter.com/rwaltzsoftware
Facebook: https://www.facebook.com/RWaltz-Software-PvtLtd-255590135349493
Telegram: https://t.me/RWaltzCrypto
GitHub: https://github.com/rwaltzsoftware
Clutch: https://clutch.co/profile/rwaltz-software
Website: https://www.rwaltz.com
Top comments (0)