← Back to Balancer
Balancer · closed proposal
[BIP-927] Revoke Unused V2 Vault Permissions from Deprecated Relayers
Voters
9
BAL voted
6.56M
≈$717.4K
Token price
$0.11
AI summary
Summary pending — generation runs every 15 minutes.
Voting results
Quorum
6.56M / 5.00M BAL(131%)
✓ Quorum met
Yes, let's do it6.56M (100.0%)
No, this is not the way0 (0.0%)
Abstain0 (0.0%)
6.56M BAL · ≈$717.4K · 9 votersblock 25855302
Votes over time
x-axis = % of voting window elapsed · y-axis = cumulative VP per choice
🐳 Whale votes
6 votes > 5% VP0x9f74…d68e
7d ago · voted Yes, let's do it
56.8%
2.83M VP
≈$309.3K
0xa9b3…eb7e
7d ago · voted Yes, let's do it
42.9%
2.13M VP
≈$233.5K
0x8787…ea52
7d ago · voted Yes, let's do it
16.0%
1.05M VP
≈$115.0K
0xff02…1751
7d ago · voted Yes, let's do it
7.8%
512.82K VP
≈$56.1K
0xe585…330e
8d ago · voted Yes, let's do it
99.8%
13.34K VP
≈$1.5K
0x9d57…65a5
9d ago · voted Yes, let's do it
100.0%
29 VP
≈$3
Full proposal
Original markdown · Balancer
TL;DR
On all chains, revoke leftover permissions on the V2 vault for relayers that are deprecated or no longer used. Only the latest 20231031-batch-relayer-v6/BalancerRelayer is left intact.
Motivation
The V2 vault still grants swap, batchSwap, joinPool, exitPool, manageUserBalance, and/or setRelayerApproval to several relayers that have been deprecated or are no longer in use. They are leftover from old frontend paths and third-party integrations. Revoking them is good security practice and falls in line with the general sunsetting of V2.
CoW Protocol has deprecated API …
📚 Similar past proposals
Finding similar proposals…