FeedProjects
Developers
Settings
๐ŸŽ‰ A new chapter begins: Boardroom has joined Agora
Learn more
protocol logo
Explore / Projects
Ampleforth

Proposals

Discussions

Members

Information

Create Proposal

Ampleforth

ProposalsDiscussionsMembersInformation
Proposal
Back to Proposals
closedEnded 8 months ago ยท Snapshot (Offchain)

Compensate Bill Broker LPs for Impermanent Loss During Fee Curve Transition

By 0xfe23...1e7F98

Background

The DAO recently voted to update the Bill Broker logic with a new price curve structure.

The old fee curves were flat at the tails, while the new fee curves approach each other at the tails. The upside of the new structure is that it allows the Bill Broker to remain in the market conducting trades for longer rather than sitting on the sidelines for sometimes extended periods of time. The downside is that these negative fees at the tails can lead to impermanent loss, as one would see in typical AMMs.

This occurrence was especially impactful at this instance because the Broker walked to an asset ratio with one curve, then immediately walked back using the different curve and different pricing structure.

When the logic updates were deployed, the asset ratio was far away from 1.0, which led to a near instant arbitrage against other markets by flash bots agents. This (rather impressive) transaction executed in the very next block, 12 seconds later, and can be seen here. Accounting for the profit and fee to the builder, there was a total profit of $34,030.35026. Interestingly, most of this went to the block builder.

Compensation

I propose doing a one-time compensation to the Bill Broker LPs at the time of the asset rebalance after the update occurred.

The LP addresses and BB-LP note balances at the time were:

RankAddressQuantityPercentage
10x190f13321c37c3124e73ca530680e6b97bf930ec26,345,355,690.0830.39%
20xcb7e8cbbbd45f66efd699a538a67bf8c0e5f063620,362,096,737.2923.49%
30x62336d8a9651795de47aabd3aa22f2dc68d2107212,279,513,029.8314.17%
40x270c71a312210d0dc87d5f43d5d10840599c89389,882,938,145.3011.40%
50x814611f0eb8c0befb5b6892ca836e51784e9b9b48,968,083,246.2310.35%
60x4c37700d949db46aa11a9f1627070f9af31f80112,945,009,759.303.40%
70xe683c0751eacee3e6c4446bfa509413f2fb680dc2,200,000,0002.54%
80xe692171e4d49d4b889b218ebbe7eee2606e8744e1,736,996,537.982.00%
90x4a8c0ae6d6590b4f8403e7cf0006a91d6be55155770,420,860.200.89%
100xb623352e078e57349fe5a8de96109e2395cb20fe548,509,817.320.63%
110x0d0aca99686fced8e6fb39134aaed96f09b5283c484,498,382.400.56%
120x234b6ea3094392ebf49393c0e73a54a5a31f29a1123,437,610.840.14%
130x5d13c850f3e8eb925b8ab73155b8d8b610e16e5a27,632,770.100.03%
140x92891f12c9448fec7750aff2eb697a62b87659f812,620,954.290.01%
150xa088aef966cad7fe0b38e28c2e07590127ab4ccb10,0000.00%

Which would lead to a proposed compensation structure of:

RankAddressUSDC
10x190f13321c37c3124e73ca530680e6b97bf930ec10342.26584
20xcb7e8cbbbd45f66efd699a538a67bf8c0e5f06367993.457033
30x62336d8a9651795de47aabd3aa22f2dc68d210724820.501205
40x270c71a312210d0dc87d5f43d5d10840599c89383879.698142
50x814611f0eb8c0befb5b6892ca836e51784e9b9b43520.541825
60x4c37700d949db46aa11a9f1627070f9af31f80111156.113089
70xe683c0751eacee3e6c4446bfa509413f2fb680dc863.6562592
80xe692171e4d49d4b889b218ebbe7eee2606e8744e681.9001585
90x4a8c0ae6d6590b4f8403e7cf0006a91d6be55155302.4277228
100xb623352e078e57349fe5a8de96109e2395cb20fe215.3100261
110x0d0aca99686fced8e6fb39134aaed96f09b5283c190.1956276
120x234b6ea3094392ebf49393c0e73a54a5a31f29a148.45921877
130x5d13c850f3e8eb925b8ab73155b8d8b610e16e5a10.85568173
140x92891f12c9448fec7750aff2eb697a62b87659f84.968431138
Total34030.35026

Given the small number of address affected, I think fastest and easiest way to handle the payments is simply to send direct USDC transactions, rather than any more complicated claim structure.

If you are affected and you believe this data in incorrect, please reach out here or on the Discord server.

Continue Reading
Connect Wallet to Add Note
0
Votes 31
VoterCast PowerVote & Rationale
0xA742...4261f9
3,317

For

0x0023...084C64
1,763

For

0xA8D3...e2360B
0.33

Against

0x211D...d4a771
0.30

Against

0x463b...6BF3ac
0.29

Against

SHOW MORE
VOTE POWER
0
Connect Wallet
Proposal Status
  • Wed July 23 2025, 06:44 amVoting Period Starts
  • Sat July 26 2025, 06:44 amEnd Voting Period
Current Results

1-For

5,082.057

99.93%

2-Against

3.617

0.07%
DocumentationBrandingContact Us
Home
This Project is Currently Disabled

If you would like to enable it, please checkout below.

Boardroom Subscription

Sign up for an individual subscription (access all projects on the platform)

Subscribe
Enable Project

Enable the entire project for every user

Enable Project
Contact Us