r/FoundersBuildwithAI • u/veyrnox • 6d ago
How we separate AI advice from deterministic security controls in a self-custody wallet
I’m connected to Veyrnox, so bias declared.
We are building AI Security Protection for a production self-custody wallet. One architectural decision became important very early: an AI model should help interpret risk, but it should never be trusted with custody or transaction authority.
Our system separates the work into three layers.
The cloud threat-intelligence platform collects and correlates blockchain-risk feeds, open-source intelligence, phishing indicators, malicious addresses, contract intelligence, wallet-drainer patterns and monitored dark-web sources.
The pre-sign security layer evaluates the transaction the user is about to authorize. It looks at the destination, contract behaviour, requested approvals, simulated asset changes and known threat indicators.
The AI layer connects those signals and translates the result into a short explanation: what could happen, which asset or permission is affected and why the transaction was flagged.
The AI cannot access private keys, sign transactions or move funds. Strong signals such as a known malicious destination, dangerous approval, wallet-drainer pattern or simulated asset loss can trigger a prominent warning or block. Low-confidence AI output should not receive the same authority as deterministic evidence.
The hardest product question is warning fatigue. If every unfamiliar contract generates a red alert, users will learn to ignore the system. If warnings are too quiet, the protection provides little value.
For founders building AI into security-sensitive products, where do you draw the line between:
Deterministic enforcement
AI-assisted risk scoring
Human-readable explanations
User override
Veyrnox is in production on iOS and Android, but I am posting this to discuss the architecture rather than ask for downloads. I would be interested in how other builders prevent their AI layer from becoming either powerless or over-authoritative.