ZkOrigoPlus – Stateless Multi-Chain Compliance Engine
Mood
thoughtful
Sentiment
neutral
Category
tech
Key topics
blockchain
compliance
serverless architecture
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.
The author presents ZkOrigoPlus, a stateless multi-chain compliance engine, and seeks feedback from experienced engineers on its architecture and design choices.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
2h
Peak period
1
Hour 3
Avg / period
1
Based on 1 loaded comments
Key moments
- 01Story posted
11/18/2025, 3:35:05 PM
6h ago
Step 01 - 02First comment
11/18/2025, 5:55:18 PM
2h after posting
Step 02 - 03Peak activity
1 comments in Hour 3
Hottest window of the conversation
Step 03 - 04Latest activity
11/18/2025, 5:55:18 PM
4h ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Discussion hasn't started yet.
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.