Skip to content

docs: how MEV capture fees are credited (LP disclosure) - #11

Merged
moodysalem merged 1 commit into
mainfrom
eku-960-mevcapture-disclosure
Oct 11, 2026
Merged

moodysalem merged 1 commit into
mainfrom
eku-960-mevcapture-disclosure

Conversation

@moodysalem

@moodysalem moodysalem commented Oct 8, 2026 •

Copy link
Copy Markdown
Member

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 credited section 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: the MEV capture bullet now ends with the CSO's one-line pointer, linking to /concepts/extensions/#how-mev-capture-fees-are-credited.
  • Not changed: the table row, reference/contracts/evm-v3.md, and the whitepaper.

Checked against the code (evm-contracts bbda78f, the deployed runtime of 0x5555fF9F…41Be): in MEVCapture.accumulatePoolFees and the forwarded swap path, the held fees are only credited when lastUpdateTime != block.timestamp, through CORE.accumulateAsFees. That function credits the current active liquidity and burns the amount when liquidity is 0.

Verification: bun run build passed, bun run check:links passed (49 pages), Prettier is clean, and the anchor id="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.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

Deploying ekubo-docs with  Cloudflare Pages  Cloudflare Pages

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

View logs

@moodysalem
moodysalem merged commit 5fd2603 into main Oct 11, 2026
2 checks passed
@moodysalem
moodysalem deleted the eku-960-mevcapture-disclosure branch October 11, 2026 18:40
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.

1 participant