Repository navigation
docs: how MEV capture fees are credited (LP disclosure) - #11
Merged
Merged
Conversation
Deploying ekubo-docs with
|
| Latest commit: |
75ccd04
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f730ebff.ekubo-docs-966.pages.dev |
| Branch Preview URL: | https://eku-960-mevcapture-disclosur.ekubo-docs-966.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an LP-facing note on how MEV capture's additional fee is credited, using the CSO-cleared text (EKU-963, verdict CLEARED WITH EDITS) word for word.
Changes
concepts/extensions.md: new### How MEV capture fees are creditedsection directly below the extensions table. The body is the CSO final text; its bold lead-in became the heading so the anchor can be linked.products/liquidity.md: theMEV capturebullet now ends with the CSO's one-line pointer, linking to/concepts/extensions/#how-mev-capture-fees-are-credited.reference/contracts/evm-v3.md, and the whitepaper.Checked against the code (evm-contracts
bbda78f, the deployed runtime of0x5555fF9F…41Be): inMEVCapture.accumulatePoolFeesand the forwarded swap path, the held fees are only credited whenlastUpdateTime != block.timestamp, throughCORE.accumulateAsFees. That function credits the current activeliquidityand burns the amount when liquidity is 0.Verification:
bun run buildpassed,bun run check:linkspassed (49 pages), Prettier is clean, and the anchorid="how-mev-capture-fees-are-credited"and the link from the liquidity page are both in the built HTML.As the CSO asked, do not add redirect/JIT recipes, example numbers, or step sequences in later edits. Routine review, merge and normal existing-CI release are owned by CTO under EKU-1557; the obsolete blanket board merge card is withdrawn. No new deployment mechanism or feature-launch authorization is implied.
Feature lineage and acceptance criteria
Originating board feature: EKU-946, under EKU-928. Delivery: EKU-964, via EKU-960 and the decision in EKU-961.
User outcome: existing MEV capture LPs can understand when and to whom additional fees are credited.
Acceptance: CSO-cleared paragraph unchanged below the extensions table, working pointer from the liquidity bullet, excluded reference/whitepaper/table content untouched, checks pass, CTO decision recorded, and section/link verified on docs.ekubo.org after normal CI publication.