Spending Limits
Spending limits are your safety net when using Alfred402's autonomous payment system. They prevent overspending and give you complete control over how much the AI can spend on your behalf.
Overview
Spending limits work in three time periods:
Daily: Maximum spending per 24-hour period
Weekly: Maximum spending per 7-day period
Monthly: Maximum spending per 30-day period
All limits are enforced automatically before any payment is processed.
How Limits Work
Hierarchical Structure
Limits must follow this hierarchy:
Monthly ≥ Weekly ≥ Daily
Example:
Daily: 0.01 ETH ✓
Weekly: 0.05 ETH ✓
Monthly: 0.2 ETH ✓Invalid configuration:
Automatic Resets
Daily: Resets every 24 hours from first transaction
Weekly: Resets every 7 days
Monthly: Resets every 30 days
Real-Time Enforcement
Before every payment:
Setting Up Limits
Initial Configuration
On first use, set conservative limits:
Using Smart Contracts
Limits are stored on-chain for security:
Through the UI
Coming soon: Web interface for easy limit management.
Limit Strategies
Conservative (Recommended for New Users)
Moderate (Regular Users)
Aggressive (Power Users)
Business/Enterprise
Monitoring Your Spending
Current Usage
Check anytime:
Spending Trends
View historical data:
Alerts
Get notified when:
80% of any limit reached
Limit exceeded (payment rejected)
Unusual spending pattern detected
Adjusting Limits
Increasing Limits
Need more capacity? Increase anytime:
Decreasing Limits
Reduce exposure:
Temporary Overrides
Coming soon:
One-time limit increase
Expires after 24 hours
Requires additional confirmation
Smart Contract Integration
SpendingLimits Contract
Core functions:
Approved Spenders
Authorize Alfred402 to spend on your behalf:
On-Chain Security
Benefits of smart contract limits:
✅ Tamper-proof
✅ Transparent
✅ Auditable
✅ Decentralized enforcement
Limit Scenarios
Scenario 1: Within Limits
Scenario 2: Would Exceed Daily
Scenario 3: Within Daily, Exceeds Weekly
Best Practices
1. Start Small
Don't set high limits immediately:
Learn the system first
Understand typical costs
Build confidence gradually
2. Review Regularly
Check spending weekly:
Are limits too restrictive?
Any unusual patterns?
Adjust based on usage
3. Separate Wallets
Consider using different wallets:
Testing Wallet: Low limits, experimental
Production Wallet: Higher limits, vetted services
Emergency Wallet: Backup funds
4. Set Realistic Limits
Base limits on:
Your budget
Expected usage
Service costs
Risk tolerance
5. Monitor Alerts
Enable notifications for:
Limit approaching (80%)
Limit exceeded
Unusual activity
Troubleshooting
"Can't set limits"
Possible causes:
Wallet not connected
Invalid limit hierarchy
Transaction failed
Solution:
"Payment rejected despite having funds"
Check:
"Limits not updating"
Solution:
Advanced Features
Multi-Signature Limits
For organizations:
Require 2+ approvals for limit changes
Prevents single point of failure
Audit trail for all modifications
Dynamic Limits
Coming soon:
Adjust based on time of day
Higher limits during business hours
Lower limits at night
Spend Analysis
Coming soon:
Service breakdown
Cost optimization suggestions
Spending predictions
Security Considerations
Private Key Protection
Your spending limits protect against:
Compromised API access
Malicious service requests
Accidental overspending
Even if someone gains access to Alfred402, they cannot exceed your configured limits.
Smart Contract Audits
Our SpendingLimits contract:
✅ Open source
✅ Professionally audited
✅ Battle-tested
✅ Upgradeable (with timelock)
Learn More
Need help? Join our Discord or email [email protected]
Last updated