Skip to content

Conversation

@jalbrekt85
Copy link
Collaborator

solves #233

retroactive fee logic is isolated in the quantamm dir except where its triggered in main_combined.py

fee run flow now is:

  • fee allocation runs as normal and finishes
  • retroactive fee calculator runs and appends result to the report
  • resulting amount then can be manually subtracted for vebal allocation and added to quantamm partner transfer
  • fee run merged and sent to multisig-ops for final validation with updated quantamm fee

retroactive_fees.py works by:

  • looping through each biweekly period in the retroactive date range
  • for each period: fetch respective non-core fees collected and earned fees for all quantamm pools
  • apply partner fee split based on fees collected, quantamm share of non-core fees and pool category (same logic in regular allocator codebase)
  • sum quantamm partner fee from each period and generate report and json artifact file with more granular data

also contains formatting adjustments to the payload visualizer

Comment on lines +18 to +25
QUANTAMM_POOLS = {
"mainnet": {
"0x6b61d8680c4f9e560c8306807908553f95c749c5": 0.50, # non-core with gauge
"0xd4ed17bbf48af09b87fd7d8c60970f5da79d4852": 0.80, # non-core without gauge
},
"base": {
"0xb4161aea25bd6c5c8590ad50deb4ca752532f05d": 0.50, # non-core with gauge
}
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these are the three quantamm pools i could find with their respective partner fee split. hardcoded them for clarity. should be validated against BIP-871. no quantamm pool has shown up in the core pool list during the retroactive period and the gauge status has not changed for any of them during the retroactive period

pools links:

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on our code logic. QuantAMM pools without any yield-bearing assets can never become core pools, correct?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

correct

@jalbrekt85
Copy link
Collaborator Author

test run with quantamm retroactive fees, result is $6,257: #246 (comment)

@jalbrekt85 jalbrekt85 force-pushed the quantamm-retroactive-fees branch from 5dc5a76 to 3416386 Compare December 16, 2025 19:10
@jalbrekt85
Copy link
Collaborator Author

jalbrekt85 commented Dec 16, 2025

added rocket retroactive fee script. also pushed reports for both quantamm and rocket:

quantamm fee: $6577.78
rocket fee: $2128.94

Copy link
Contributor

@Xeonus Xeonus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Numbers confirmed by QuantAMM team. Delta shall be deducted from veBAL fee share in the next suitable fee run

@jalbrekt85 jalbrekt85 merged commit 7a6dce4 into biweekly-runs Dec 17, 2025
4 checks passed
@jalbrekt85 jalbrekt85 deleted the quantamm-retroactive-fees branch December 17, 2025 17:11
@Xeonus Xeonus mentioned this pull request Dec 19, 2025
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants