Story

I’ve been working on a stateless compliance and validation engine that runs across multiple chains (Ethereum, XRPL, Hedera, Polygon, Stellar, Bitcoin). Everything is processed per-request — no customer records, no logs, no storage. Just deterministic validation.

What it currently does • Wallet + transaction checks (multi-chain) • AML, basic KYC logic, RWA attestation structure • Zero-knowledge proof validation framework • ISO 20022 XML generation (pacs.008, pain.001) • Basic cross-border rules engine • AI/ML advisory layer (optional — model loads from S3 and runs at inference time, no data retention)

Infrastructure • Fully serverless: API Gateway + Lambda • 6 chain validators • 6 compliance modules • Sandbox + production environments • Stateless by design (no PII, no telemetry tracking unless user enables it)

Live Demo • MVP validator: https://mvp.zkorigoplus.com (simple UI showing chain + compliance outputs) • API documentation: https://zkorigoplus.com

What I’m looking for Not trying to sell anything — just want feedback from engineers who’ve built compliance, payments, or chain infrastructure before.

Main questions: 1. Does the stateless approach make sense long-term? 2. Any obvious gaps in the architecture? 3. Is the multi-chain abstraction too broad or reasonable? 4. Should the AI advisory stay optional or be removed entirely?

Happy to share more details if helpful.