Programmable Compliance
Definition
The embedding of regulatory obligations — sanctions screening, transfer restrictions, holder eligibility, reporting triggers, and the like — into the executable logic of a settlement system, such that the obligation is enforced at the moment the transaction is performed rather than evaluated after the fact. Programmable Compliance is a property of the system; it is not a substitute for the legal regime under which the obligation arises.
Notes
The FATF Travel Rule1 and the sanctions regimes administered by OFAC and equivalent authorities establish what the obligation is. Programmable Compliance is one possible answer to how the obligation is satisfied within a tokenized settlement system. Done well, it makes compliance continuous, auditable, and operationally cheaper than retrospective screening. Done poorly, it embeds error at scale, introduces failure modes that are difficult to inspect, and creates the appearance of compliance without the substance.
The assessability question is the one that matters. A compliance regime encoded in smart contracts is only as trustworthy as the inspection regime applied to that code, the governance under which it is changed, the data sources on which it depends, and the failover behavior when those sources fail. Programmable Compliance is therefore not a feature an issuer can claim; it is a property of the system that must be examined in the same way as any other component.
See also
Deterministic Behavior · Operational Suitability · Black-Box Infrastructure
References
- ↩ Financial Action Task Force, FATF Recommendation 16 (Wire Transfers / Travel Rule) and Updated Guidance for a Risk-Based Approach to Virtual Assets and Virtual Asset Service Providers (October 2021). fatf-gafi.org
- ↩ Bank for International Settlements, Project Agorá (cross-border payments using tokenised commercial bank deposits and central bank money). bis.org