Skip to main content
Understanding how Vincent Apps work is essential for building secure, user-controlled automation. This guide explains the key components and their relationships.

​
Vincent Apps

Vincent Apps enable automated execution of on-chain and off-chain actions on behalf of users while maintaining strict user control through programmable permissions.
​
appId
number
Unique identifier for your Vincent App across all versions
​
version
number
Immutable version number ensuring users know exactly what they’ve authorized
The core execution logic of Apps is composed of Vincent Abilities and Vincent Policies working together.

​
Vincent Abilities

Modular, executable functions that define what your App can do. Each Ability is an npm package containing the logic for specific actions.

On-Chain Actions

Token transfers, swaps, staking, lending, and smart contract interactions

Off-Chain Actions

API calls, database operations, notifications, and external service integrations

Learn More

Deep dive into how Vincent Abilities work

​
Vincent Policies

Programmable guardrails that users configure to control how Abilities execute. Each Policy is an npm package that defines specific constraints and boundaries.

Financial Controls

Spending limits, budget caps, and value restrictions

Operational Controls

Token allowlists, time windows, and rate limiting

Learn More

Deep dive into how Vincent Policies work

​
Version Immutability

App versions are immutable once published to ensure trust and transparency. Users delegate to a specific version with a fixed set of Abilities and Policies that cannot be changed without their explicit consent.
When you need to modify Abilities or Policies, you must create a new version. See Updating Your App for details on versioning and what requires a new version.

​
App Delegatees

Ethereum addresses authorized to execute Abilities on behalf of users. These addresses act as the operational layer of your App.

EOA Delegatees

Externally owned accounts for manual or automated execution using private keys

Smart Contract Delegatees

Contract addresses for programmatic execution with on-chain logic
1

Secure Key Storage

Use hardware security modules or secure key management services for production delegatee private keys
2

Regular Key Rotation

Implement a key rotation schedule to minimize exposure from potential compromises
3

Environment Separation

Use different delegatee addresses for development, testing, and production environments
4

Activity Monitoring

Set up logging and alerts for all delegatee transactions and Ability executions
⌘I