You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-114Lines changed: 2 additions & 114 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,121 +32,9 @@ ap-avs aggregator
32
32
33
33
Note: The Ava Protocol team currently manages the aggregator, and the communication IP address between the operator and the aggregator is hardcoded in the operator.
34
34
35
-
### Configurable Fee Rates
36
-
37
-
The aggregator supports configurable fee rates for workflow execution and monitoring. This allows for dynamic pricing adjustments without code deployments, environment-specific pricing, and A/B testing of pricing models.
38
-
39
-
#### Configuration Overview
40
-
41
-
Fee rates are completely **optional** and **backward compatible**. The aggregator will work exactly as before without any configuration changes. When fee rates are configured, they override the hardcoded defaults.
42
-
43
-
#### Adding Fee Configuration
44
-
45
-
To configure custom fee rates, add a `fee_rates:` section to your existing aggregator YAML configuration file:
46
-
47
-
```yaml
48
-
# Your existing aggregator config (unchanged)
49
-
environment: development
50
-
db_path: /tmp/ap-avs/db
51
-
ecdsa_private_key: your_private_key_here
52
-
# ... other existing config fields ...
53
-
54
-
# 🆕 Optional fee rates configuration
55
-
fee_rates:
56
-
# Base fees (one-time per workflow)
57
-
base_fee_usd: 0.0
58
-
59
-
# Monitoring fees (per minute) - cost to monitor triggers
0 commit comments