Case Studies
Compliance in production
See how protocols are building with deterministic on-chain risk enforcement.
GlobalPay USD — MiCA-Compliant Stablecoin
GlobalPay launched a EUR-backed stablecoin targeting the EU market. They needed real-time OFAC screening, MiCA reserve attestations, and automated KYC verification — all without introducing centralized infrastructure.
FidesOrigin's CompliantStableCoin base contract provided deterministic screening on every mint, burn, and transfer. The Policy Engine was configured with MiCA-specific rules: 1:1 reserve requirements, daily transaction limits, and accredited investor checks.
// MiCA-specific policy configuration function configureMicaPolicies() external { policy.setReserveRatio(10000); // 100% policy.setDailyLimit(1_000_000 * 1e6); policy.requireAccredited(true); policy.enableOfacScreening(true); }
RealT — Tokenized Real Estate Compliance
RealT tokenizes real estate properties across multiple jurisdictions. Each property has different investor requirements: US accredited investors only for some, EU MiCA for others, and jurisdiction-specific KYC.
FidesOrigin's multi-policy support allowed RealT to assign different compliance rules per token. The Merkle-based risk registry enabled privacy-preserving verification without revealing investor data on-chain.
// Per-token policy assignment function assignPolicy( address token, Policy calldata policy ) external { policies[token] = policy; emit PolicyAssigned(token, policy.id); }
SafeFlow — Account Abstraction with Compliance
SafeFlow built an ERC-4337 smart wallet for institutional users. They needed every userOp screened before bundler submission — without adding latency or compromising the account abstraction flow.
By integrating FidesOrigin at the validation phase, SafeFlow screens all destination addresses and call data before the bundler ever sees the userOp. The integration added less than 10ms to validation time.
// Validate before bundler acceptance function validateUserOp( UserOperation calldata userOp ) external override returns (uint256) { require( fides.isCompliant(userOp), "Non-compliant userOp" ); return _validateSignature(userOp); }
Testimonials
What builders say
"FidesOrigin solved our biggest compliance headache. Before, we were screening via API calls that added 300ms latency and occasionally failed. Now every transaction is screened deterministically on-chain — our users don't even notice it's there."
"The Merkle-based privacy approach is exactly what we needed. We can prove compliance to regulators without exposing sensitive investor data on-chain. It's the first solution that actually understands both DeFi and privacy."
"Integrating compliance into ERC-4337 was supposed to be impossible. FidesOrigin proved it wasn't — we had it working in a weekend. The validation-phase hook means zero UX impact for our users."
Ready to become our next case study?
Get in touch to discuss your compliance needs.