Governance, Legal, Regulatory, and Compliance Considerations
What this domain tests
Consortium governance, legal enforceability, data protection, AML and KYC, and sector regulation. Expect scenario questions on decision rights and regulatory perimeter.
Core rules
- A consortium needs a charter: membership criteria, voting, dispute resolution, liability, IP, upgrade rules, exit, and wind-down.
- Governance must cover both the network and the business process. Onboarding and offboarding are not purely technical.
- Smart contracts are generally enforceable only when they satisfy contract law: offer, acceptance, consideration, capacity, legality, and intent. Code is evidence, not a substitute for law.
- Data protection: GDPR and CCPA erasure and minimization conflict with immutable ledgers. Use off-chain storage and on-chain proofs.
- Financial use cases trigger AML, KYC, sanctions screening, travel-rule, securities, custody, and market-conduct rules. Tax treatment of tokens must be settled.
Worked example
A bank wants to join a trade-finance network. The consortium checks its licence, AML programme, and sanctions controls; the legal agreement sets liability for false documents; the MSP is updated; the bank node is permissioned on one channel only. The reasoning: onboarding is a governance and compliance event before it is a certificate installation.
Traps
Do not say code is law. Do not assume a private network avoids regulation. Do not ignore antitrust when competitors share pricing data. Do not promise deletion of on-chain records without an off-chain design. Do not treat a consortium as a vendor contract.