/Inapse Inclave
Inapse Inclave transforms your wallet into a programmable execution system — controlled by intent, not access.
Define what should happen — not who gets access. Inclave executes securely within defined boundaries.
/The Problem
Current systems require full access to wallets or APIs, private key exposure, and manual approvals. Permissions are binary — all or nothing — creating security risks, poor UX, and incompatibility with AI agents.
Binary permissions
All-or-nothing access with no granularity
Private key exposure
Keys must be shared for any interaction
Manual approvals
Every action requires human confirmation
Agent incompatibility
AI agents cannot safely interact with wallets
"Giving full access is unsafe. Giving no access is useless."
Before — Access Model
Agents require full wallet access. Private keys are exposed at every step.
After — Instruction Model
Agents send instructions. Inclave evaluates rules and executes locally. No key exposure.
/The Shift
Instead of giving control, define rules. Instead of exposing keys, execute locally. Inclave replaces the permission model with programmable intent.
Old model
Give control to act
Expose keys to sign
Trust the agent completely
Inclave model
Define rules to follow
Execute locally, keys stay
Trust the logic, not the agent
"Inclave replaces permissions with programmable intent."
/How It Works
Five steps from intent to settlement — all executed locally within the enclave. Private keys never leave. No external system gets full access.
01
💡
User defines intent
02
📋
Intent becomes structured instruction
03
⚙
Inclave evaluates rules locally
04
▶
Executes within allowed parameters
05
🔐
Signs and settles securely
Private keys
Never leave the enclave
External access
Zero
/Programmable Wallet
Inclave is not a traditional wallet. It is a programmable execution environment that supports conditional execution, scheduled actions, multi-step pipelines, and API + blockchain interactions.
If price hits X → swap
Conditional execution triggered by market data
Send payment when task completes
Event-driven settlement on task completion
Split transaction across parties
Multi-party distribution in a single pipeline
⚡
Conditional execution
⏱
Scheduled actions
🔗
Multi-step pipelines
🌐
API + blockchain
"The wallet becomes an execution engine."
/AI Agent Control
Agents need the ability to act — but access equals risk. With Inclave, agents don't get keys. They send instructions. Inclave enforces the rules.
Agents don't get keys
No private key material is ever exposed to agent runtimes
Agents send instructions
Structured intent proposals are submitted for evaluation
Inclave enforces rules
Only actions within defined parameters are executed
"Agents don't control your assets — they propose actions."
/OpenClaw Limitation
OpenClaw-type systems enable powerful agent interaction — but they lack safe execution. No fine-grained financial control. No secure key handling.
OpenClaw-type systems
Inapse Inclave
"Inclave enables agents to act — without exposing control."
/QRC20 Integration
QRC20 pipelines define the logic — conditional flows, multi-step actions, cross-chain operations. Inclave executes the value securely within defined boundaries.
QRC20
Defines the logic
Inclave
Executes the value
"Pipelines define the logic. Inclave executes the value."
/Why It Matters
AI can decide. Apps can display. But execution requires trust — and trust requires a secure, programmable layer between intent and settlement.
AI can decide
Models generate optimal actions and strategies
Apps can display
Interfaces present options and confirmations
Execution requires trust
Value movement demands verifiable security
"Inclave is where decisions become transactions."
/Role in Inapse
Inclave is the execution core of the Inapse ecosystem — the layer where secured intent becomes verifiable value movement.
01
Input
Captures intent
02
K2K
Secures intent
03
Inclave
Executes value
04
QRC20
Scales execution
A NEW WALLET MODEL
Just execution — exactly as intended.