Skip to content

Rewamp docs content#296

Merged
Siegrift merged 18 commits intomainfrom
rewamp-docs-content
Apr 22, 2026
Merged

Rewamp docs content#296
Siegrift merged 18 commits intomainfrom
rewamp-docs-content

Conversation

@Siegrift
Copy link
Copy Markdown
Collaborator

Closes #292
Closes #295

Summary

Adds a new Curation section to the docs, covering Api3's role as a curator of USDC vaults on Morpho and cleans up the OEV docs given there is no OEV Network.

I think the current docs structure is decent and the addition of the "Curation" tab works well. I do not consider the curation content to be perfect nor complete, but it's a decent start. It's also going to change soon, because Morpho wants the V2 vaults to stop using v1 vaults as intermediaries, which affects our operations.

What's new

  • Top nav — New "Curation" entry alongside dApps and OEV Searchers.
  • Overview (/curation/) — Intro to Api3 x Morpho, the skin-in-the-game thesis, yield source, the OEV competitive advantage, vault summary (Api3 Core, Kabu, Api3 dCOMP), and fee structure.
  • Roles and operations (/curation/roles-and-operations) — Role table, two-layer V2→V1 vault architecture, allocation/rebalancing, monitoring stack, and liquidation handling.
  • Risk management (/curation/risk-management) — Market selection criteria anchored to Api3's data feed listing policy, supply-cap methodology, and treasury-backed risk alignment.
  • Disclosure (/curation/disclosure) — Scope of curation, no-advice clause, risk factors, restricted jurisdictions, and limitation of liability. Links to the Api3 terms and conditions. Pending review from Erich.

@Siegrift Siegrift requested a review from bdrhn9 April 15, 2026 19:40
@Siegrift Siegrift self-assigned this Apr 15, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 15, 2026

Visit the preview URL for this PR (updated for commit 7efa5ba):

https://oev-docs--pr296-rewamp-docs-content-xccecla9.web.app

(expires Tue, 28 Apr 2026 08:45:10 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: 6915b094b5ba83fde754632ba50c1ee9406d433f

@Siegrift Siegrift requested review from andreogle April 16, 2026 07:21
Copy link
Copy Markdown
Member

@andreogle andreogle left a comment

Choose a reason for hiding this comment

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

Tried to go through this in detail. Let me know what you think. Otherwise, nice work 👍🏻

Comment thread docs/curation/index.md Outdated
Comment thread docs/curation/index.md Outdated
1. **V2 Vault** — The user-facing vault where depositors supply USDC and receive vault shares. Configured with the Api3 role structure and governance controls described above.

2. **V1 Vault** — The intermediary vault that executes the actual market allocations. The V1 vault holds two allocators:
- The **Morpho Public Allocator**, which enables permissionless reallocation to improve liquidity across markets.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Maybe it's worth a quick sentence or two about what this does/how it works?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

It will be gone soon with the Morpho requirement to use v2 adapter directly, so not really worth it. It's also best to look into Morpho docs for this kind iof stuff anyway.

Comment thread docs/curation/roles-and-operations.md Outdated
Comment thread docs/curation/roles-and-operations.md Outdated
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Maybe worth asking Erich to have a look at this one?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Yes, done in https://api3workspace.slack.com/archives/C0A70NN2WFQ/p1776264148887269 and the changes are already merged into this PR.

Comment thread docs/oev/in-depth/data-feeds/index.md Outdated
Comment thread docs/oev/index.md
Api3 facilitates OEV using two ways:

1. Private auctions performed via partnered searchers on non-delayed data.
2. Searching using public Signed APIs on delayed data, open for anyone to participate.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'm not sure that this is strictly "OEV", especially since that was described as only available to "partnered searchers". This is more MEV

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Both are OEV, because the value is extracted by utilizing the oracle updates. The MEV is misleading to both, because the miner is inconsequential for both of these.

What can be argued about is the word "auctions" as that is now a bit inaccurate, but the exact mechanics on how partnered searchers obtain the OEV signature is not important (and most importantly it can change), so I left it in.

Comment thread docs/oev/index.md Outdated
Comment thread package.json
"format:check": "prettier --check --cache \"./**/*.{js,vue,md,json,yaml}\"",
"lint": "pnpm format:check",
"test": "vitest run",
"test": "vitest run --passWithNoTests",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

What's this for?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

I've removed the only test and the CI fails in that case. I didn't want to bother with removing vitest so I just let it pass without any test.

Comment thread docs/curation/roles-and-operations.md Outdated
The Api3 DAO Multisig holds the owner, curator, and allocator roles, consolidating governance and operational control under a single entity.

The guardian role is operated by the Api3 monitoring team, who can revoke pending actions in case of misconfiguration.
The monitoring team also maintains an emergency fund for manual liquidations in the event that automated liquidation bots fail.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Should we mention about size of funds held or address of this account?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

No.

Comment thread docs/oev/in-depth/mev-with-signed-apis.md
ErichDylus and others added 2 commits April 21, 2026 10:09
* Revise disclosure terms 

Updated the disclosure page to clarify Api3's limited role, responsibilities, and terms of service.

* Revise roles and operations 

Updated the roles and operations documentation to reflect the Api3 Foundation Multisig as the holder of key roles and clarified the mission of the foundation. Adjusted language for clarity regarding the monitoring team's role and the emergency fund.
Co-authored-by: André Ogle <andreogle@users.noreply.github.com>
@Siegrift Siegrift requested a review from bdrhn9 April 21, 2026 08:36
@Siegrift Siegrift force-pushed the rewamp-docs-content branch from 70c1e32 to 7efa5ba Compare April 21, 2026 08:44
@Siegrift Siegrift merged commit d150e78 into main Apr 22, 2026
3 checks passed
@Siegrift Siegrift deleted the rewamp-docs-content branch April 22, 2026 11:47
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.

Replace Blast as the example chain Update the OEV docs and close no-longer relevant issues

4 participants