Founder & CEO building CRYPTØBEAM, MIOS (Market Intelligent OS), and CRYPTØBEAM-PCST.

Compliance-first digital asset marketplace infrastructure.

Current Phase 1 architecture is provider-led: third-party providers perform regulated or asset-handling functions such as custody, identity/KYC, execution, and settlement. CRYPTØBEAM focuses on orchestration, integrations, workflow controls, auditability, reconciliation, and the customer/operator experience.

Core engineering direction:

• Java + Spring Boot microservices
• OpenHFT / Chronicle event backbone
• append-only audit trails and deterministic reconciliation
• provider integrations behind explicit service boundaries
• security, observability, policy enforcement, and operational controls

Post-Quantum Proof-Carrying State Transport — a new protocol research/codebase focused on self-authenticating state transport, fail-closed verification, capability containment, delegation safety, and post-quantum cryptographic agility.

PCST is not a rename or continuation of the older DAMA/Damaverse utility work. DAMA/Damaverse repositories are separate historical projects/evidence unless explicitly incorporated through reviewed, documented migration.

Current research direction includes:

• proof-carrying state envelopes
• explicit protocol invariants and threat models
• ML-KEM / ML-DSA-aligned post-quantum suites
• non-normative rail mappings, including XRPL research
• transport abstractions spanning terrestrial and delay/disruption-tolerant links

Market Intelligent OS — a separate private research and intelligence platform focused on market analysis, decision support, and AI-assisted workflows.

• Evidence before claims
• Runtime validation over compile-only confidence
• Fail closed at trust and policy boundaries
• No hardcoded secrets; environment/vault-backed configuration
• Strong reconciliation, provenance, observability, and auditability
• Historical repositories are evidence sources, not automatically canonical implementations

The CRYPTØBEAM repository estate is undergoing evidence-first recovery and consolidation. Older repositories may contain incomplete, experimental, deprecated, or conflicting implementations. Canonical status should be established from current recovery records and verified runtime evidence rather than repository age or naming alone.

Digital asset infrastructure · Fintech controls · Distributed systems · Event-driven architecture · Post-quantum cryptography · Protocol security · Market intelligence · AI-assisted software engineering

REDDNoC is my engineering handle. Public repository text describes technical direction and architecture; it should not be read as a claim of regulatory approval, licensure, direct custody, or direct exchange operation.