DetentLabs · Fresh Investor Deck
June 2026 · 01 / 17
AI SECURITY INFRASTRUCTURE
Risk engine +
action gate
before signing.
Pre-seed
detentlabs.ai · safeclick.dev
Problem
02 / 17
ACTIVE CRYPTO RISK
Every sign
is a loss
boundary.
Click · connect · approve · sign · transfer
User workaround
Not protection
01
Limit the loss
Security-aware users split cold storage from a small active wallet balance.
02
The exposed moment remains
Click, connect, approve, sign, and transfer still happen before users understand risk.
03
The missing layer is authorization
Users do not need another warning. They need a decision before irreversible value movement.
Existing stack
03 / 17
WHY CURRENT TOOLS FAIL
Existing tools stop short of a decision.
01 / Storage
Cold wallets protect savings.
They do not govern active approvals once users start signing.
02 / Warnings
Warnings ask users to judge.
Generic prompts still leave the final risk call to the signer.
03 / Scanners
Scanners require a separate habit.
Useful signal is often outside the transaction flow.
04 / Gap
No one decides before execution.
The missing layer is enforceable authorization.
2024 EVIDENCE
Wallet drainers stole $494M from 332K+ addresses; Permit signatures drove 56.7% of large-loss cases.
Source: Scam Sniffer Crypto Phishing Report 2024
Solution
04 / 17
DETENTLABS DECISION LAYER
Risk engine + action gate before signing.
Inputs
URL / domain
dApp context
Contract behavior
Transaction payload
Risk engine
Deterministic gates + AI-assisted evidence + policy rules.
Pre-sign verdict
Allow / proceed to signing
Warn / hold for review
Block / hard stop
Decision log
Risk evaluation
Context and signals become a structured pre-sign verdict.
Controlled beta
DetentLabs enforces allow, warn, or block directly in its own wallet surface.
Partner-ready
Partners enforce the same verdict through an SDK/API contract in their own flows.
Why now
05 / 17
WHY THIS GETS BIGGER NOW
Crypto moved from holding to active signing.
01 / More surfaces
dApps, bridges, swaps, mints, embedded wallets.
01
02 / More value in motion
The risky moment is not only where assets rest.
02
03 / Infrastructure demand
Wallets and fintechs need embedded security decisions.
03
Product path
06 / 17
FROM SAFECLICK TO CONTROLLED ENFORCEMENT
Controlled proof first. API scale next.
Live
SafeClick today
URL and dApp pre-checks prove user behavior.
Pre-seed
Controlled wallet beta
A controlled wallet beta to prove block-before-sign enforcement.
Prototype
Risk decision API/SDK
SDK/API hook for risk engine + action gate before signing.
Scale
Partner distribution
Embed the decision workflow into crypto transaction flows.
Traction / validation
07 / 17
SAFECLICK LIVE WEDGE VALIDATION
Users already check before exposure.
68
external registered users
34
external users with scan activity
194
external deduplicated checks
23.3%
external return rate
80%
helpful scan-session ratings
External-user filtered · May 2026. Current usage is risky-link and unfamiliar-site checks.
Competition / market map
08 / 17
WORKFLOW MARKET MAP
Where the action gate sits.
Market map
Surfaces.
Signals.
Gate.
01
Signing surfaces
02
Risk signals
03
Decision workflow
Business model
09 / 17
PRIMARY REVENUE PATH
Embedded risk-decision API / SDK.
01 / First ICP
Embedded-wallet and wallet-like transaction products
02 / Decision unit
A pre-sign verdict
03 / Pricing hypothesis
Platform fee + usage tiers
Team
10 / 17
FOUNDER-MARKET FIT
Concrete execution, not generic bios.
CEO / Product / Market
Abdallah Alsharrah
CEO & Co-founder
- Owns the active-user problem: signing, approvals, dApp interactions, and wallet-risk behavior.
- Leads customer discovery, fundraising, product positioning, and early GTM.
- Has begun MENA discovery through crypto-active operators and investors.
CTO / Risk Pipeline / Infrastructure
Junyu Li
CTO & Co-founder
- Shipped the live SafeClick system: risk scoring, AI evidence, backend, analytics, quotas, billing, and deployment.
- Led the hackathon-winning team that became SafeClick.
- Owns the risk engine, API/SDK architecture, and blocking-proof infrastructure for DetentLabs.
Ask
11 / 17
ANGEL SAFE / PRE-SEED
Raising $500K to prove blocking + demand
01 / Product proof
Block before signing
- Wallet-native blocking beta
- Allow / warn / block verdicts
- Latency + accuracy baseline
02 / Commercial proof
Prove demand
- 10-15 ICP conversations
- 3 design-partner candidates
- Pricing + integration baseline
Small founder/family capital is already committed and being used to build the proof.
12 / 17
CLOSING
CORE THESIS
Detect risk.
Gate action
before signing.
The next crypto security layer will not just detect risk. It will gate action before signing.
DetentLabs
June 2026
CONTACT
DETENTLABS
GET IN TOUCH
DetentLabs
detentlabs.ai
safeclick.dev
Risk decisions before users sign.
Appendix A1
13 / 17
DETAILED COMPETITION MATRIX
Different tools sit at different moments.
01 / Wallet interface
MetaMask / Coinbase
Own transaction UX, not neutral infrastructure
02 / Custody + trading
Binance / exchanges
Protect their own surfaces first
03 / Security API
Blockaid
Strong signals; partner workflow still matters
04 / Security data
GoPlus
Raw intelligence and APIs
05 / Detection / alerts
Scam Sniffer
Useful threat discovery and awareness
06 / Pre-wallet layer
Browser extensions
Can miss wallet-native authorization context
07 / Post-exposure
Revoke / cleanup tools
Useful after risk, weaker before execution
08 / Decision layer
DetentLabs
Pre-sign verdicts and action-gate workflow before value moves
Appendix A2
14 / 17
API / SDK CONTRACT SHEET
Verdict contract before signing.
01 / Integration hook
Before signing
TriggerBefore signing
InputsRisk context
CallRisk engine
ReturnPre-sign verdict
02 / Verdict contract
Allow, warn, block.
ALLOW
Proceed to signing.
WARN
Hold; user can override after review.
BLOCK
Hard stop before signing.
03 / Enforcement ownership
Who enforces the gate.
Controlled beta: DetentLabs enforces directly.
Partner integration: partner enforces through SDK/API contract.
Decision logs record verdict, reason, and action taken.
Inputs: dApp URL, contract address, method, approval amount, transaction data, wallet context, product policy.
Appendix A3
15 / 17
EVIDENCE BOUNDARY BOARD
Current evidence and future proofing form.
Current evidence
SafeClick live usage
68 registered users
34 users with scan activity
194 deduplicated checks
23.3% return rate
80% helpful ratings
What it proves
Pre-check behavior exists.
Users are willing to check before interacting with unfamiliar crypto surfaces.
Repeat behavior exists beyond a one-time curiosity click.
Scan feedback suggests explanations matter, not just binary labels.
Future proofing form
What the next proof should show.
Controlled wallet blocking before signing.
Blocked-risk event logs.
Tester feedback on warn and block decisions.
False-positive / false-negative baseline.
API/SDK prototype behavior.
First ICP validation.
Appendix A4
16 / 17
MENA / KUWAIT / UAE CORRIDOR
Validation corridor, not proven distribution.
01 / Market
Crypto-active users
A regional audience that can understand wallet-risk pain without a long education cycle.
02 / Need
Underserved protection
High activity does not automatically create mature authorization security.
03 / Market motion
Trust-led adoption
Regional crypto conversations often move through trust and operator referrals.
04 / Validation corridor
MENA / Kuwait / UAE
A validation corridor for crypto-active operators and investors, not a proven distribution channel yet.
05 / GTM
First operators
Target crypto-active founders, fintech builders, wallets, and wallet-like transaction products.
06 / Proof
Conversations to prove
Named user conversations and investor/operator feedback should validate the thesis.
Appendix A5
17 / 17
INVESTOR Q&A / INITIAL FOCUS
Initial focus: pre-sign authorization-risk decisions for active crypto workflows.
01 / What is live today?
SafeClick pre-action checks
Live URL/dApp checks, user activity, return behavior, helpful ratings, and a working risk pipeline.
02 / What are we raising to prove next?
Blocking + demand
Controlled wallet beta, blocked-risk logs, tester feedback, API/SDK prototype, and first ICP validation.
03 / Who pays first?
Embedded-wallet and wallet-like products
Products that own signing flows but do not have large internal security teams.
04 / Why not MetaMask / Coinbase / Binance?
Neutral embedded layer
Incumbents protect their own ecosystems; the rest of the market needs embeddable pre-sign protection.
05 / What is the revenue path?
Embedded risk-decision API / SDK
Platform fee plus usage tiers around pre-sign verdict volume and enterprise risk needs.
06 / What is the current product scope?
Pre-sign authorization-risk decisions
Active crypto workflows first: signing, approvals, transfers, destinations, and dApp actions.