I’ve been working on a stateless compliance engine that validates IBAN/SWIFT, OFAC lists, ISO20022 (pain.001/pacs.008), and multi-chain data (ETH, BTC, XRPL, Polygon, Stellar, Hedera).
Statelessness feels important in financial and blockchain workflows because no user data persists between requests, outputs are fully deterministic, and auditors can reproduce results without relying on stored state.
Current progress:
• Deterministic validators live and callable
• On-chain checks working across 6 networks
• ISO20022 structuring + downloadable PDFs
• AWS backend deployed; Azure environment being added for multi-cloud isolation
Looking for technical critiques or alternative patterns for building stateless compliance systems.
This reduces: • data retention risk, • breach impact, • compliance obligations (since nothing is persisted), • and audit friction (deterministic logic instead of ML scoring).
The hard parts I’m still working on: • maintaining deterministic outputs across multiple chains with different RPC behaviours • handling ISO20022 structuring without keeping session state • managing rate limits and abuse control without storing user data • making multi-cloud (AWS + Azure) work while remaining fully stateless in both environments
If anyone here has experience building stateless financial or compliance pipelines at scale, I’d appreciate technical critiques — especially around reproducibility, rate limiting design, or RPC reliability patterns.
reply