Feat/compliance framework

Cargo.toml

@@ -11,6 +11,8 @@ members = [
     "contracts/property-token",
     "contracts/insurance",
     "contracts/analytics",
+    "contracts/fees",
+    "contracts/compliance_registry",
 ]
 resolver = "2"
 

contracts/compliance_registry/Cargo.toml

@@ -2,11 +2,13 @@
 name = "compliance_registry"
 version = "0.1.0"
 edition = "2021"
+description = "Multi-jurisdictional compliance and regulatory framework for PropChain"
 
 [dependencies]
-ink = { version = "5.0.0", default-features = false }
-scale = { package = "parity-scale-codec", version = "3", default-features = false, features = ["derive"] }
-scale-info = { version = "2", default-features = false, features = ["derive"], optional = true }
+ink = { workspace = true }
+scale = { workspace = true }
+scale-info = { workspace = true }
+propchain-traits = { path = "../traits", default-features = false }
 
 [dev-dependencies]
 ink_e2e = "5.0.0"
@@ -20,5 +22,6 @@ std = [
     "ink/std",
     "scale/std",
     "scale-info/std",
+    "propchain-traits/std",
 ]
 ink-as-dependency = []

contracts/compliance_registry/README.md

@@ -0,0 +1,32 @@
+# PropChain Compliance Registry (Issue #45)
+
+Multi-jurisdictional compliance and regulatory framework for PropChain: KYC/AML, sanctions screening, audit trails, workflow management, and regulatory reporting.
+
+## Features
+
+- **Multi-jurisdiction**: US, EU, UK, Singapore, UAE, Other with configurable rules per jurisdiction.
+- **KYC**: Verification requests, document/biometric types, verification levels, expiry.
+- **AML**: Risk factors (PEP, high-risk country, transaction patterns, source of funds), batch AML checks.
+- **Sanctions**: Multiple list sources (UN, OFAC, EU, UK, Singapore, UAE), status and list stored per account.
+- **Audit**: Audit log per account; compliance report and sanctions screening summary.
+- **Workflow**: Create verification request → off-chain processing → process_verification_request; workflow status query.
+- **Regulatory reporting**: `get_regulatory_report(jurisdiction, period_start, period_end)`.
+- **Transaction compliance**: `check_transaction_compliance(account, operation)` for rules-engine style checks.
+- **Integration**: Implements `ComplianceChecker` trait for PropertyRegistry cross-calls.
+
+## Build and Test
+
+From repo root:
+
+```bash
+cargo build -p compliance_registry
+cargo test -p compliance_registry
+```
+
+## Usage with PropertyRegistry
+
+1. Deploy ComplianceRegistry.
+2. On PropertyRegistry, call `set_compliance_registry(Some(registry_address))` (admin).
+3. Registration and transfers will then require compliant accounts (registry `is_compliant(account)` must be true).
+
+See `docs/compliance-regulatory-framework.md` and `docs/compliance-integration.md` for full integration and best practices.