Skip to content

Security Model

OwliaBot uses a 3-tier key security model to balance automation with safety.

Crypto automation is risky:

  • Bots with private keys can drain wallets
  • “Rug pulls” happen when bots go rogue
  • Users want automation but fear losing funds

For any transaction that matters.

Bot → [Push Request] → App → [User Confirms] → Sign → Broadcast
  • Private key never leaves the mobile app
  • Biometric/PIN confirmation required
  • User sees full transaction details
  • Maximum security

For small automated operations.

  • Generated locally by the bot
  • Amount-limited (e.g., max $10 per tx)
  • Rotated periodically
  • Lost = limited damage

Use cases: Gas payments, small claims, tip transactions.

For large automated operations that need programmatic control.

┌─────────────────────────────────────────┐
│ Smart Contract Wallet (ERC-4337) │
│ │
│ Session Key Permissions: │
│ - Whitelist contracts only │
│ - Daily/per-tx limits │
│ - Specific tokens only │
│ - Time-limited │
│ │
│ Owner Key: │
│ - Revoke session keys anytime │
│ - Withdraw all funds │
│ - Modify permission rules │
└─────────────────────────────────────────┘

Use cases: DeFi strategies, recurring swaps, yield optimization.

The main private key never enters the bot process. Period.

Session keys have only the permissions needed for their task.

Users can revoke any session key instantly.

All operations are logged and traceable.

Automated operations have configurable caps.

ApproachRiskAutomation
Give bot your private key🔴 Total loss possible✅ Full
Tier 1 only🟢 User confirms all❌ Manual
Tier 2 (Session Key)🟡 Limited to cap✅ Small ops
Tier 3 (Smart Wallet)🟢 Granular control✅ Large ops
TierStatus
Tier 1 (Companion App)🚧 Planned
Tier 2 (Session Key)🚧 Planned
Tier 3 (Smart Wallet)🚧 Planned