SkillWallet* is a permissioned skill runtime for AI-powered crypto wallets, where users install bounded wallet skills and let the backend execute approved actions through delegated permissions.
SkillWallet* explores a safer model for AI-assisted wallet automation.
Instead of giving AI direct wallet control, users install wallet skills with bounded permissions. Each skill defines what it is allowed to do, when it can run, what contracts/functions it can call, and how much it can spend.
Some skills are deterministic, such as scheduled DCA or event-triggered USDC automation. Other skills can use optional x402 paid data and Venice AI reasoning before execution. In those AI-assisted flows, Venice AI only returns a structured decision such as execute or skip with a reason. It does not receive the private key, does not sign transactions, and does not directly submit wallet actions.
The backend runtime handles triggers, validates skill parameters, builds approved transaction calls, and submits delegated execution through 1Shot. Users remain in control and can pause, resume, or revoke installed skills.
Core idea: AI reasons. Backend executes. User controls permissions.
During the hackathon, I built the SkillWallet* MVP as a working skill runtime and marketplace backend for delegated wallet automation.
Completed progress includes:
- Skill catalog API for discovering available wallet skills
- Skill installation flow with prepare / confirm delegation endpoints
- Support for skill parameters, permission scopes, and human-readable delegation metadata
- Runtime support for cron-triggered and onchain event-triggered skills
- Execution history for successful, failed, and skipped runs
- Pause, resume, and revoke controls for installed skills
- 1Shot delegated execution integration for submitting approved wallet actions
- x402 integration for paid external data fetching
- Venice AI reasoning flow for AI-assisted skills such as AI-Powered DCA
- Deterministic non-AI skill flow for event-based automation
- Landing page and product narrative around permissioned wallet skills
The main demo flow shows a user installing a bounded skill, the runtime triggering it, optional x402 + Venice reasoning, and backend execution through delegated permission.
Not fundraising. SkillWallet* is currently a hackathon MVP / prototype. I am focused on validating the technical architecture, user experience, and permissioned wallet automation model before considering fundraising.