New MEV Blocker Docs#512
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Warning Rate limit exceeded@cowmarketing has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 13 minutes and 53 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (1)
WalkthroughThis update introduces comprehensive new documentation and significant reorganization for MEV Blocker. It adds detailed guides, conceptual explanations, API references, integration instructions, and performance benchmarks. Several obsolete or redundant documents and categories are removed or replaced. The documentation structure is streamlined, with new sections for concepts, order flow originators, searchers, builders, and performance, offering clearer navigation and more concise, visual, and up-to-date content. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Wallet/App
participant MEV Blocker RPC
participant Searcher
participant Builder
participant Validator
User->>Wallet/App: Initiate transaction
Wallet/App->>MEV Blocker RPC: Send signed transaction (eth_sendRawTransaction)
MEV Blocker RPC->>Searcher: Broadcast unsigned tx (if backrunnable)
Searcher->>MEV Blocker RPC: Submit bundle with backrun bid
MEV Blocker RPC->>Builder: Forward best bundle(s) and user tx
Builder->>Validator: Submit block with user tx and backrun
Validator->>Blockchain: Include block on-chain
Builder->>User: Refund 90% of backrun value
Builder->>Validator: Pay 10% of backrun value
MEV Blocker RPC->>Wallet/App: Provide status via API
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 28
🧹 Nitpick comments (72)
docs/mevblocker/rpc-performance/_category_.json (1)
1-6: Clarify category label.
Consider updating"label": "Performance Benchmark"to"RPC Performance Benchmark"for clarity given therpc-performancedirectory context.docs/mevblocker/concepts/MEV/_category_.json (1)
1-4: Add collapsible flags for consistency.
Other documentation categories include"collapsible": trueand"collapsed": true. Consider adding these settings unless intentional to keep the MEV category always expanded.docs/mevblocker/orderflow-originators/Users/rainbow.md (3)
5-5: Nit: Remove trailing space in the main heading
The line reads# Rainbow Walletwith an extra space at the end. Trimming it will prevent potential rendering inconsistencies.
9-15: Improve image alt text for accessibility
All images use![Guide], which isn’t descriptive. Consider unique alt text for each step, e.g.,.
17-17: Add content or placeholder for Mobile Wallet section
The## Mobile Walletheading is empty. Please provide instructions or a “Coming soon” note to avoid user confusion.docs/mevblocker/orderflow-originators/API-reference/configuring-fee-recipient-address.md (1)
9-11: Adjust code fence language
The snippet is a URL and not JSX. Change the fence to plain text orbashfor accuracy:-```jsx -https://rpc.mevblocker.io/?refundRecipient=(YOUR_ADDRESS) -``` +```bash +https://rpc.mevblocker.io/?refundRecipient=(YOUR_ADDRESS) +```docs/mevblocker/orderflow-originators/Users/rabby.md (2)
5-5: Remove trailing whitespace in headingEliminate the extra space after “# Rabby Wallet” for consistency.
9-14: Enhance image alt text for accessibilityProvide descriptive alt text for each screenshot instead of the generic “Guide” to improve usability for screen readers.
docs/mevblocker/orderflow-originators/API-reference/analytics.md (2)
7-7: Simplify wording in introductionReplace “In order for you to have custom analytics on your flow, you need to set up…” with a more concise phrase, e.g., “To enable custom analytics, set the
referrerfield in transaction status.”
15-15: Refine sentence and punctuationAdd a comma after “dashboard,” and consider using “resolve” instead of “fix” for a more formal tone:
- …If you wish to have a custom dashboard please contact us. + …If you wish to have a custom dashboard, please contact us.docs/mevblocker/searchers/API Reference/send_bundle.md (1)
9-25: Use appropriate language tag for JSON examplesThese blocks show JSON with comments—switch the fence language from
jsxtojsonc(orjson) for accurate syntax highlighting.Also applies to: 29-35
docs/mevblocker/rpc-performance/success-reate.md (1)
14-14: Improve image alt textUse a more descriptive alt attribute for the chart, e.g.
.docs/mevblocker/searchers/API Reference/cancel_bundle.md (4)
3-3: Clarify and correct grammar in descriptionRewrite the sentence for clarity, for example:
- Clarification for eth_cancelBundle we support only receiving empty bundle with uuid they want to cancel. + We only accept an empty bundle containing the `replacementUuid` of the bundle to cancel.
5-5: Capitalize and format broadcast statementBegin with a capital letter and wrap method names in backticks:
- we'll broadcast both eth_cancelBundle and eth_sendBundle to all connected builders with that uuid + We broadcast both `eth_cancelBundle` and `eth_sendBundle` to connected builders using that UUID.
7-7: Use consistent heading style for examplesConvert “Example of request” and “Example response” to proper heading levels (e.g.,
## Example Request/## Example Response) to match other API docs.Also applies to: 22-22
9-20: Adjust code block language for JSONReplace the
jsxfence withjsonc(orjson) since the examples are JSON:- ```jsx + ```jsoncAlso applies to: 24-30
docs/mevblocker/orderflow-originators/Users/Metamask.md (1)
1-3: Suggest adding asidebar_labelfor clarity.
Includingsidebar_label: Metamaskin the frontmatter ensures this guide is labeled correctly in the sidebar.docs/mevblocker/rpc-performance/inclusion-speed.md (4)
11-11: Enhance the image alt text.
Instead of![Speed], use a more descriptive alt (e.g.,![Box plot of inclusion speeds across RPC providers]).
13-15: Fix wording and punctuation in the distribution description.
- Change “distribution to time to inclusion” → “distribution of time to inclusion”.
- Remove stray space before comma in “average , the”.
15-15: Remove the extra “the.”
Update “represents the standard deviation of the each set.” → “represents the standard deviation of each set.”
17-17: Add missing determiner for fluency.
Revise “demonstrates MEV Blocker fastest execution” → “demonstrates MEV Blocker’s fastest execution” or “demonstrates the fastest execution by MEV Blocker.”docs/mevblocker/orderflow-originators/Users/README.mdx (3)
6-6: Simplify “able to” phrasing.
Consider “Individual users can also connect to MEV Blocker RPC…” instead of “are also able to.”
8-8: Fix missing article and possessive.
Update “instead of default one. Check MEV Blockers Endpoints here” → “instead of the default one. Check the MEV Blocker endpoints here.”
26-26: Use a more polite verb.
Replace “tell them to either integrate directly MEV Blocker or to allow for custom RPC” → “ask them to integrate MEV Blocker or support custom RPCs.”docs/mevblocker/concepts/README.mdx (1)
8-8: Correct pluralization.
Change “protects you from these type of attacks” → “protects you from these types of attacks.”docs/mevblocker/orderflow-originators/Integrators/Solvers.md (3)
7-7: Add comma before conjunction.
Revise “endpoint to ours and you're good to go.” → “endpoint to ours, and you're good to go.”
17-17: Link to the Endpoints section.
Instead of plain text “Refer to our Endpoints section,” add a markdown link to the actual doc (e.g.,[Endpoints](../Endpoints.md)).
19-19: Fix list indentation.
Remove the extra leading spaces before “2. Customize Your Setup” so the numbered list renders correctly.docs/mevblocker/orderflow-originators/Integrators/Telegram Bots.md (2)
7-7: Add a comma in compound sentence
Insert a comma before “and” for the independent clauses:- just switch your app or wallet’s RPC endpoint to ours and you're good to go. + just switch your app or wallet’s RPC endpoint to ours, and you're good to go.
18-18: Fix list indentation for step 2
Remove the leading space before the “2.” so all list items align at the same level:- 2. **Customize Your Setup** + 2. **Customize Your Setup**docs/mevblocker/searchers/README.mdx (1)
14-14: Add comma before “and”
Insert a comma before “and we will contact” for clarity:- become one of the best searchers on MEV Blocker and we will contact you + become one of the best searchers on MEV Blocker, and we will contact youdocs/mevblocker/orderflow-originators/Integrators/Relayers.md (1)
13-13: Add a comma in compound sentence
Insert a comma before “and” in the integration line:- just switch your app or wallet’s RPC endpoint to ours and you're good to go. + just switch your app or wallet’s RPC endpoint to ours, and you're good to go.docs/mevblocker/orderflow-originators/Endpoints.md (2)
49-53: Improve example URL formatting
Remove the placeholder dashes and treat the code block as a pure URL snippet:- ```jsx - - Endpoint_you_Choose - https://rpc.mevblocker.io/{your_chosen_endpoint}?shareAll=1 - ``` + ```text + https://rpc.mevblocker.io/{your_chosen_endpoint}?shareAll=1 + ```
57-61: Improve example URL formatting
Same adjustment for the “shareSafe” example:- ```jsx - - Endpoint_you_Choose - https://rpc.mevblocker.io/{your_chosen_endpoint}?shareSafe=1 - ``` + ```text + https://rpc.mevblocker.io/{your_chosen_endpoint}?shareSafe=1 + ```docs/mevblocker/orderflow-originators/Integrators/Wallets.md (2)
11-11: Add a comma in compound sentence
Insert a comma before “and” for clarity:- just switch your app or wallet’s RPC endpoint to ours and you're good to go. + just switch your app or wallet’s RPC endpoint to ours, and you're good to go.
22-22: Fix list indentation for step 2
Align the second list item with the rest (remove leading space):- 2. **Customize Your Setup** + 2. **Customize Your Setup**docs/mevblocker/rpc-performance/backrunning.md (3)
9-9: Improve image alt text for accessibility.
All images use the generic alt text “Backrun”. Please provide descriptive alt text that conveys what each box plot represents (e.g., “Distribution of backrun sizes for MEV Blocker vs Flashbots”).Also applies to: 19-19, 23-25
11-11: Remove double space.
There are two spaces in “swaps that” which may be a typo.
15-15: Spell out numbers and simplify sentence structure.
Using “2” at the start of a sentence can be jarring; consider “two categories” and breaking this long sentence into shorter bullets for clarity.docs/mevblocker/builders/README.mdx (1)
31-31: Clarify phrase “access to flow.”
Change to “access to private order flow” or “access to order flow” for precision.docs/mevblocker/rpc-performance/README.mdx (4)
3-5: Avoid wordiness in “exact same.”
Consider “identical transactions” or simply “the same transactions.”
13-13: Fix punctuation and capitalization.
Remove the stray period before “Flashbots” and ensure consistent casing for “MEV Blocker”:
- Change “. Flashbot ranks…” to “Flashbots ranks…”
15-15: Add missing comma after “Finally.”
Should read “Finally, Merkle and Blink both generate very low rebates.”
18-18: Improve alt text for performance chart.
Replace “Guide” with a descriptive label like “Performance comparison of MEV RPCs.”docs/mevblocker/concepts/gas_rebates.md (1)
20-20: Simplify phrasing.
Consider changing “is able to recover” to “can recover” for conciseness.docs/mevblocker/orderflow-originators/API-reference/Transactions-status.md (1)
9-11: Use correct code block language.
The schema is JSON but the block is markedjsx. Please switch to ```json for proper syntax highlighting.docs/mevblocker/concepts/MEV/MEV.md (6)
1-3: Add asidebar_labelto frontmatter
Currently onlysidebar_positionis defined. Including asidebar_labelensures the sidebar uses a clear, user-friendly title for this page.
7-7: Remove bold markup in heading
Use a plain Markdown heading (## Without MEV Blocker) instead of## **Without MEV Blocker**for consistency and cleaner rendering.
9-9: Terminate sentence with a period
Add a period at the end of the sentence for proper punctuation.
11-11: Provide descriptive alt text for image
Replace![image.png]with a meaningful description (e.g.,![Default Ethereum mempool flow diagram]) to improve accessibility.
20-20: Remove bold markup in heading
Change## **With MEV Blocker**to## With MEV Blockerfor consistency.
22-22: Fix hyphenation of “sandwiching”
Remove the stray space: use “sandwiching” instead of “sandwich -ing”.docs/mevblocker/rpc-performance/price-improvement.md (6)
7-7: Add missing comma before clause
Insert a comma after “execution” to improve readability:
“…observing the quality of the execution, which can be measured…”
9-9: Remove unnecessary comma and add article
Rephrase to “compare each RPC service to the MEV Blocker when both have executed the swap.”
11-11: Add the missing preposition “as”
Use “This can be rewritten as price improvement = …” for grammatical correctness.
12-12: Use “number of tokens” instead of “amount of tokens”
Tokens are countable, so “number of tokens received” is more precise.
22-22: Provide descriptive alt text for first image
Replace![priceImprovement]with something like![Swap price improvement distribution chart]for accessibility.
25-25: Provide descriptive alt text for second image
Use a clear description (e.g.,![P-value significance results chart]) instead of the generic label.docs/mevblocker/orderflow-originators/Integrators/Oracles.md (3)
13-13: Add missing comma before “and”
Insert a comma: “switch your app or wallet’s RPC endpoint to ours, and you’re good to go.”
24-24: Align numbered list indentation
Remove the leading space before “2.” so it matches the format of the other steps.
30-32: Use appropriate code block language
Changejsxtotextor no language specifier for a URL to avoid misleading syntax highlighting.docs/mevblocker/README.mdx (4)
10-10: Remove redundant “the” before possessive pronoun
Change “…created by the their flow” to “…created by their flow.”
17-17: Fix typo in phrasing
Update “due to is innovative” to “due to its innovative Builder fee mechanism.”
19-19: Correct multiple grammar and spelling issues
- Change “within in a 30s delay” to “with a 30 s delay.”
- Add comma before “and”: “…other RPCs, and we…”
- Fix apostrophe in “don’t.”
- Correct “pubslish” to “publish.”
25-25: Clarify comparison phrasing
Revise to “see how MEV Blocker performs in terms of speed, backrun rate, and success compared to other RPCs.”docs/mevblocker/orderflow-originators/Integrators/Intent_applications.md (3)
13-13: Add missing comma before “and”
Insert a comma: “switch your app or wallet’s RPC endpoint to ours, and you’re good to go.”
24-24: Align numbered list indentation
Remove the extra space before “2.” so numbering is consistent.
31-33: Use non-JSX code block for URL
Replacejsxwithtext(or omit) for the RPC URL snippet.docs/mevblocker/builders/optimal_bidding.md (1)
31-31: Remove extra space after ATX heading
Multiple spaces found between the heading markers and the text on line 31. For consistency and to satisfy markdownlint MD019, use a single space after###.docs/mevblocker/concepts/order-flow-auction.md (1)
5-5: Use a descriptive title instead of "How it works"
The top-level heading "# How it works" is too generic. Rename it to "# Order Flow Auction" (or similar) so readers immediately know which concept this document covers.docs/mevblocker/orderflow-originators/API-reference/Sending-transactions.md (2)
15-26: Usejsonfor JSON-RPC examples
Replace the language tagjsxwithjsonon all JSON-RPC request/response code fences (starting at line 15) to improve syntax highlighting and clarity.
145-145: Fix typo in "successful"
The word "successfull" is misspelled. Change it to "successful".
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (51)
docs/mevblocker/README.mdx(1 hunks)docs/mevblocker/builders/README.mdx(1 hunks)docs/mevblocker/builders/_category_.json(1 hunks)docs/mevblocker/builders/optimal_bidding.md(1 hunks)docs/mevblocker/concepts/MEV/MEV.md(1 hunks)docs/mevblocker/concepts/MEV/_category_.json(1 hunks)docs/mevblocker/concepts/README.mdx(1 hunks)docs/mevblocker/concepts/_category_.json(1 hunks)docs/mevblocker/concepts/gas_rebates.md(1 hunks)docs/mevblocker/concepts/mev-concepts/_category_.json(0 hunks)docs/mevblocker/concepts/order-flow-auction.md(1 hunks)docs/mevblocker/concepts/order-flow-auction/_category_.json(0 hunks)docs/mevblocker/concepts/order-flow-auction/order-flow-auction.md(0 hunks)docs/mevblocker/orderflow-originators/API-reference/Cancelling-transactions.md(1 hunks)docs/mevblocker/orderflow-originators/API-reference/Sending-transactions.md(1 hunks)docs/mevblocker/orderflow-originators/API-reference/Transactions-status.md(1 hunks)docs/mevblocker/orderflow-originators/API-reference/analytics.md(1 hunks)docs/mevblocker/orderflow-originators/API-reference/configuring-fee-recipient-address.md(1 hunks)docs/mevblocker/orderflow-originators/Endpoints.md(1 hunks)docs/mevblocker/orderflow-originators/Integrators/Intent_applications.md(1 hunks)docs/mevblocker/orderflow-originators/Integrators/Oracles.md(1 hunks)docs/mevblocker/orderflow-originators/Integrators/Relayers.md(1 hunks)docs/mevblocker/orderflow-originators/Integrators/Solvers.md(1 hunks)docs/mevblocker/orderflow-originators/Integrators/Telegram Bots.md(1 hunks)docs/mevblocker/orderflow-originators/Integrators/Wallets.md(1 hunks)docs/mevblocker/orderflow-originators/Users/Metamask.md(1 hunks)docs/mevblocker/orderflow-originators/Users/README.mdx(1 hunks)docs/mevblocker/orderflow-originators/Users/rabby.md(1 hunks)docs/mevblocker/orderflow-originators/Users/rainbow.md(1 hunks)docs/mevblocker/orderflow-originators/_category_.json(1 hunks)docs/mevblocker/rpc-performance/README.mdx(1 hunks)docs/mevblocker/rpc-performance/_category_.json(1 hunks)docs/mevblocker/rpc-performance/backrunning.md(1 hunks)docs/mevblocker/rpc-performance/inclusion-speed.md(1 hunks)docs/mevblocker/rpc-performance/price-improvement.md(1 hunks)docs/mevblocker/rpc-performance/success-reate.md(1 hunks)docs/mevblocker/searchers/API Reference/cancel_bundle.md(1 hunks)docs/mevblocker/searchers/API Reference/send_bundle.md(1 hunks)docs/mevblocker/searchers/README.mdx(1 hunks)docs/mevblocker/searchers/_category_.json(1 hunks)docs/mevblocker/searchers/bidding-on-transactions.md(1 hunks)docs/mevblocker/searchers/listening-for-transactions.md(1 hunks)docs/mevblocker/usecases.md(0 hunks)docs/mevblocker/users-and-integrators/_category_.json(0 hunks)docs/mevblocker/users-and-integrators/integrators/_category_.json(0 hunks)docs/mevblocker/users-and-integrators/integrators/configuring-fee-recipient-address.md(0 hunks)docs/mevblocker/users-and-integrators/users/_category_.json(0 hunks)docs/mevblocker/users-and-integrators/users/api.md(0 hunks)docs/mevblocker/users-and-integrators/users/available-endpoints.md(0 hunks)docs/mevblocker/users-and-integrators/users/cancelling-transactions.md(0 hunks)docs/mevblocker/users-and-integrators/users/sending-transactions-via-rpc.md(0 hunks)
💤 Files with no reviewable changes (12)
- docs/mevblocker/concepts/order-flow-auction/category.json
- docs/mevblocker/users-and-integrators/users/category.json
- docs/mevblocker/concepts/mev-concepts/category.json
- docs/mevblocker/users-and-integrators/category.json
- docs/mevblocker/users-and-integrators/integrators/category.json
- docs/mevblocker/users-and-integrators/users/sending-transactions-via-rpc.md
- docs/mevblocker/users-and-integrators/integrators/configuring-fee-recipient-address.md
- docs/mevblocker/users-and-integrators/users/available-endpoints.md
- docs/mevblocker/users-and-integrators/users/api.md
- docs/mevblocker/users-and-integrators/users/cancelling-transactions.md
- docs/mevblocker/concepts/order-flow-auction/order-flow-auction.md
- docs/mevblocker/usecases.md
🧰 Additional context used
🪛 LanguageTool
docs/mevblocker/orderflow-originators/Users/rabby.md
[style] ~9-~9: Using many exclamation marks might seem excessive (in this case: 4 exclamation marks for a text that’s 244 characters long)
Context: ...(/img/mevblocker/Rabby_1_optimized.png) 
docs/mevblocker/orderflow-originators/Users/rainbow.md
[style] ~9-~9: Using many exclamation marks might seem excessive (in this case: 5 exclamation marks for a text that’s 303 characters long)
Context: ...img/mevblocker/Rainbow_1_optimized.png) 
docs/mevblocker/orderflow-originators/API-reference/analytics.md
[style] ~6-~6: ‘In order for you to’ might be wordy. Consider a shorter alternative.
Context: ...ar_position: 12 --- # Custom Referrer In order for you to have custom analytics on your flow, you...
(EN_WORDINESS_PREMIUM_IN_ORDER_FOR_YOU_TO)
[style] ~15-~15: Consider using a different verb for a more formal wording.
Context: ...ou create and to more easily detect and fix issues. Additionally, it is much easier...
(FIX_RESOLVE)
[uncategorized] ~15-~15: A comma might be missing here.
Context: ...your flow. If you wish to have a custom dashboard please contact us.
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
docs/mevblocker/rpc-performance/inclusion-speed.md
[grammar] ~15-~15: Two determiners in a row. Choose either “the” or “each”.
Context: ...e. represents the standard deviation of the each set. We notice that the mean and standa...
(DT_DT)
[grammar] ~17-~17: A determiner may be missing.
Context: ...saction sample demonstrates MEV Blocker fastest execution, followed by Flashbots, then ...
(THE_SUPERLATIVE)
docs/mevblocker/orderflow-originators/Users/README.mdx
[style] ~6-~6: As a shorter alternative for ‘able to’, consider using “can also”.
Context: ...-- # Individual Users Individual users are also able to connect to MEV Blocker RPC by updating ...
(BE_ABLE_TO)
[style] ~6-~6: As a shorter alternative for ‘able to’, consider using “can”.
Context: ...heir Wallet's RPC. The way in which you are able to do this varies from wallet to wallet. ...
(BE_ABLE_TO)
[uncategorized] ~8-~8: You might be missing the article “the” here.
Context: ... to pick a specific endpoint instead of default one. Check MEV Blockers Endpoints here ...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[style] ~26-~26: Consider using the more polite verb “ask” (“tell” implies ordering/instructing someone).
Context: ...port custom RPCs, reach out to them and tell them to either integrate directly MEV B...
(TELL_ASK)
docs/mevblocker/concepts/README.mdx
[grammar] ~8-~8: In this context, ‘type’ should agree in number with the noun after ‘of’.
Context: ...'s private pool protects you from these type of attacks. - MEV Rebates: MEV Bloc...
(TYPE_OF_PLURAL)
[style] ~9-~9: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...cts you from these type of attacks. - MEV Rebates: MEV Blocker lets searchers b...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
docs/mevblocker/orderflow-originators/Integrators/Solvers.md
[uncategorized] ~7-~7: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...our app or wallet’s RPC endpoint to ours and you're good to go. Our infrastructure ...
(COMMA_COMPOUND_SENTENCE)
docs/mevblocker/orderflow-originators/Integrators/Telegram Bots.md
[uncategorized] ~7-~7: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...our app or wallet’s RPC endpoint to ours and you're good to go. Our infrastructure ...
(COMMA_COMPOUND_SENTENCE)
docs/mevblocker/builders/optimal_bidding.md
[uncategorized] ~9-~9: Possible missing article found.
Context: ... builder market, a builder connected to MEV Blocker must understand how to account ...
(AI_HYDRA_LEO_MISSING_A)
[typographical] ~39-~39: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...0.9 ETH (90% of 1 ETH) - Adjusted Bid: 3 - 0.1 - 0.9 = 2 ETH You win over builders...
(DASH_RULE)
[typographical] ~39-~39: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...H (90% of 1 ETH) - Adjusted Bid: 3 - 0.1 - 0.9 = 2 ETH You win over builders witho...
(DASH_RULE)
[typographical] ~47-~47: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...V Blocker Fee: 0.1 ETH - Adjusted Bid: 2 - 0.1 = 1.9 ETH Still beats the public-on...
(DASH_RULE)
[typographical] ~56-~56: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...ivate RPC Fee: 0.9 ETH - Adjusted Bid: 2 - 0.1 - 0.9 = 1 ETH Your access to Privat...
(DASH_RULE)
[typographical] ~56-~56: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...RPC Fee: 0.9 ETH - Adjusted Bid: 2 - 0.1 - 0.9 = 1 ETH Your access to Private RPC ...
(DASH_RULE)
[uncategorized] ~58-~58: Possible missing article found.
Context: ...H Your access to Private RPC gives you edge despite the MEV Blocker fee. #### Scen...
(AI_HYDRA_LEO_MISSING_AN)
[typographical] ~64-~64: If you want to indicate numerical ranges or time ranges, consider using an en dash.
Context: ...V Blocker Fee: 0.1 ETH - Adjusted Bid: 1 - 0.1 = 0.9 ETH Public-only builders can ...
(DASH_RULE)
docs/mevblocker/orderflow-originators/Endpoints.md
[grammar] ~43-~43: “Transaction” is a singular noun. It appears that the verb form is incorrect.
Context: ...anila AMM swaps"", the fake transaction are good enough to spoof searchers to not n...
(PCT_SINGULAR_NOUN_PLURAL_VERB_AGREEMENT)
[duplication] ~43-~43: Possible typo: you repeated a word.
Context: ...n are good enough to spoof searchers to not not know which of the transactions share ar...
(ENGLISH_WORD_REPEAT_RULE)
[uncategorized] ~47-~47: When ‘parameter-specific’ is used as a modifier, it is usually spelled with a hyphen.
Context: ...round.* *Note that the absence of this parameter specific configuration makes all the flow to go ...
(SPECIFIC_HYPHEN)
[uncategorized] ~49-~49: Possible missing comma found.
Context: ...ndpoint For sharing with ALL connected searchers leverage this: ```jsx - Endpoint_you_...
(AI_HYDRA_LEO_MISSING_COMMA)
[uncategorized] ~57-~57: Possible missing comma found.
Context: ...r. For sharing with CURATED connected searchers leverage this: ```jsx - Endpoint_you_C...
(AI_HYDRA_LEO_MISSING_COMMA)
[grammar] ~62-~62: The singular determiner ‘this’ may not agree with the plural noun ‘endpoints’. Did you mean “these”?
Context: ...your_chosen_endpoint}?shareSafe=1 ``` This endpoints forces RPC to share transacti...
(THIS_NNS)
[misspelling] ~67-~67: Did you mean “rely” (= depend on with full trust)?
Context: ...r Boost However, if you do not want to relay on MEV Blocker being up 100% on the tim...
(RELAY_RELY)
[uncategorized] ~67-~67: The preposition ‘of’ seems more likely in this position.
Context: ...t to relay on MEV Blocker being up 100% on the time and failing to submit your tra...
(AI_HYDRA_LEO_REPLACE_ON_OF)
[formatting] ~67-~67: Consider inserting a comma after an introductory phrase for better readability.
Context: ...o that your transactions lands onchain. In this case the endpoints to chose are the followin...
(IN_THAT_CASE_COMMA)
docs/mevblocker/searchers/README.mdx
[style] ~10-~10: Consider a more concise word here.
Context: ...ossibility of backruning CoW Swap flow. In order to do so, and because of the itnriquises a...
(IN_ORDER_TO_PREMIUM)
[style] ~10-~10: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...CoW Swaps solver settlements, Searchers need to be whitelisted. There are two ways to ...
(REP_NEED_TO_VB)
[uncategorized] ~14-~14: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...one of the best searchers on MEV Blocker and we will contact you via Telegram to whi...
(COMMA_COMPOUND_SENTENCE)
docs/mevblocker/concepts/gas_rebates.md
[uncategorized] ~16-~16: Possible missing comma found.
Context: ...RPC who has a permissionless Order Flow Auction for which both searchers and builders a...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~20-~20: As a shorter alternative for ‘able to’, consider using “can”.
Context: ... with the transaction path, MEV Blocker is able to recover part of the Priority Fee that w...
(BE_ABLE_TO)
docs/mevblocker/orderflow-originators/Integrators/Relayers.md
[uncategorized] ~13-~13: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...our app or wallet’s RPC endpoint to ours and you're good to go. Our infrastructure ...
(COMMA_COMPOUND_SENTENCE)
docs/mevblocker/orderflow-originators/Integrators/Wallets.md
[uncategorized] ~11-~11: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...our app or wallet’s RPC endpoint to ours and you're good to go. Our infrastructure ...
(COMMA_COMPOUND_SENTENCE)
docs/mevblocker/rpc-performance/price-improvement.md
[uncategorized] ~7-~7: A comma might be missing here.
Context: ...d start by observing the quality of the execution which can be measured by the relative p...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[uncategorized] ~9-~9: Possible missing article found.
Context: ...s. Here, we compare each RPC service to MEV Blocker, when both have executed the sw...
(AI_HYDRA_LEO_MISSING_THE)
[typographical] ~9-~9: Usually, there’s no comma before “when”.
Context: ... compare each RPC service to MEV Blocker, when both have executed the swap. For every ...
(IF_NO_COMMA)
[uncategorized] ~11-~11: Possible missing preposition found.
Context: ...easure it in bps. This can be rewritten price improvement = output(RPC)/output(MEV Bl...
(AI_EN_LECTOR_MISSING_PREPOSITION)
[uncategorized] ~12-~12: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ...output(MEV Blocker) -1, with output the amount of tokens received from the swap. Both ...
(AMOUNTOF_TO_NUMBEROF)
[uncategorized] ~17-~17: You might be missing the article “the” here.
Context: ...n truth, there is no difference between MEV blocker and the comparison RPC, and the...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
docs/mevblocker/rpc-performance/README.mdx
[style] ~5-~5: ‘exact same’ might be wordy. Consider a shorter alternative.
Context: ...luating their execution quality for the exact same transactions. Through a systematic anal...
(EN_WORDINESS_PREMIUM_EXACT_SAME)
[uncategorized] ~14-~14: A comma may be missing after the conjunctive/linking adverb ‘Finally’.
Context: ...ion price is the lowest among all RPCs. Finally Merkle and Blink both generate very low...
(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
docs/mevblocker/orderflow-originators/Integrators/Intent_applications.md
[uncategorized] ~13-~13: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...our app or wallet’s RPC endpoint to ours and you're good to go. Our infrastructure ...
(COMMA_COMPOUND_SENTENCE)
docs/mevblocker/orderflow-originators/Users/Metamask.md
[style] ~11-~11: Using many exclamation marks might seem excessive (in this case: 6 exclamation marks for a text that’s 370 characters long)
Context: ...mg/mevblocker/Metamask_1_optimized.png) 
docs/mevblocker/README.mdx
[grammar] ~10-~10: A determiner cannot be combined with a possessive pronoun. Did you mean simply “the” or “their”?
Context: ...om backrunning opportunities created by the their flow * Provide the fastest inclusion t...
(A_MY)
[uncategorized] ~19-~19: A comma might be missing here.
Context: ...lic within in a 30s delay. Unlike other RPCs we dont play games with your flow and w...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[uncategorized] ~19-~19: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...r RPCs we dont play games with your flow and we stand by the data we pubslish. * **C...
(COMMA_COMPOUND_SENTENCE)
docs/mevblocker/rpc-performance/backrunning.md
[uncategorized] ~15-~15: Possible missing comma found.
Context: ...ads to many 0 values. Indeed, for these pairs there is enough liquidity so that one t...
(AI_HYDRA_LEO_MISSING_COMMA)
[formatting] ~21-~21: If the ‘because’ clause is essential to the meaning, do not use a comma before the clause.
Context: ... Blocker and Flashbots remains unchanged, because both RPCs send 100% of the rebates to ...
(COMMA_BEFORE_BECAUSE)
docs/mevblocker/orderflow-originators/Integrators/Oracles.md
[uncategorized] ~13-~13: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...our app or wallet’s RPC endpoint to ours and you're good to go. Our infrastructure ...
(COMMA_COMPOUND_SENTENCE)
docs/mevblocker/concepts/order-flow-auction.md
[style] ~44-~44: Consider a more concise word here.
Context: ... signatures back to the transactions. In order to have their bundles forwarded to builder...
(IN_ORDER_TO_PREMIUM)
[style] ~45-~45: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...an arbitrary amount denominated in ETH. In theory, searchers have an internal valu...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
docs/mevblocker/orderflow-originators/API-reference/Sending-transactions.md
[uncategorized] ~7-~7: You might be missing the article “a” here.
Context: ... endpoints. If you would rather send to custom endpoint instead of the default, you ca...
(AI_EN_LECTOR_MISSING_DETERMINER_A)
[uncategorized] ~7-~7: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ...ndpoint instead of the default, you can be found the list of available endpoints in here...
(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)
🪛 markdownlint-cli2 (0.17.2)
docs/mevblocker/builders/optimal_bidding.md
31-31: Multiple spaces after hash on atx style heading
null
(MD019, no-multiple-space-atx)
docs/mevblocker/orderflow-originators/Integrators/Wallets.md
22-22: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 1
(MD005, list-indent)
🔇 Additional comments (9)
docs/mevblocker/builders/_category_.json (1)
2-2: Verify updated category position
The"position": 4change looks intentional, but please confirm it doesn’t collide with other sidebar entries after the reorder.Run this script to list all category positions and ensure uniqueness:
#!/bin/bash # Verify unique sidebar positions across MEV Blocker docs grep -R '"position":' docs/mevblocker/*/_category_.jsondocs/mevblocker/orderflow-originators/_category_.json (1)
1-6: Configuration valid for new category.
The category metadata correctly sets position, label, and collapsible behavior.docs/mevblocker/orderflow-originators/API-reference/Cancelling-transactions.md (1)
1-3: Updated sidebar position.
Thesidebar_positionmetadata has been adjusted to 10 to reflect the new API reference ordering.docs/mevblocker/searchers/bidding-on-transactions.md (1)
4-6: Refined headings enhance clarity.
Switching the main title to "Bid on Transactions" and demoting the previous heading ensures focus on the core action.docs/mevblocker/searchers/listening-for-transactions.md (1)
4-6: Approve heading restructuring
The new H1 (# Listen to Transactions) and H2 (## How to receive unsigned pending transactions) provide a clear, consistent hierarchy.docs/mevblocker/concepts/_category_.json (1)
5-5: Approve removal of generated index link
Retaining only thecollapsedproperty while removing thelinksimplifies the sidebar configuration and aligns with the updated navigation.docs/mevblocker/searchers/_category_.json (1)
5-5: Approve link removal for Searchers category
Dropping thelinkfield here matches the broader removal of auto-generated index pages and keeps sidebar behavior consistent.docs/mevblocker/orderflow-originators/Users/rabby.md (1)
1-3: Verify frontmatter consistencyEnsure this frontmatter matches other user guides (e.g., include
sidebar_labelor other required fields) for uniform sidebar rendering.docs/mevblocker/orderflow-originators/Integrators/Solvers.md (1)
5-5: Verify heading level consistency.
This file uses## Integrating MEV Blocker; ensure other integrator docs follow the same hierarchy.
| note | ||
|
|
||
| Without this setup, by default, rebates are sent back to users (`tx.origin`) No newline at end of file |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Use proper admonition syntax
Replace the raw note marker with the Docusaurus format:
-note
+:::note
Without this setup, by default, rebates are sent back to users (`tx.origin`)
+:::📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| note | |
| Without this setup, by default, rebates are sent back to users (`tx.origin`) | |
| :::note | |
| Without this setup, by default, rebates are sent back to users (`tx.origin`) | |
| ::: |
🤖 Prompt for AI Agents
In
docs/mevblocker/orderflow-originators/API-reference/configuring-fee-recipient-address.md
around lines 13 to 15, replace the raw "note" text with the proper Docusaurus
admonition syntax by wrapping the note content inside the appropriate admonition
block (e.g., :::note ... :::) to ensure correct rendering and styling.
|  | ||
|
|
||
|
|
||
| ## Mobile Wallet No newline at end of file |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Add content or placeholder for Mobile Wallet section
The “## Mobile Wallet” heading is empty. Add instructions or at least a TODO note so readers know this section is forthcoming.
🤖 Prompt for AI Agents
In docs/mevblocker/orderflow-originators/Users/rabby.md at line 17, the "##
Mobile Wallet" section is empty. Add a placeholder note or TODO comment under
this heading to indicate that content will be added here in the future, so
readers understand this section is intentionally left blank for now.
| @@ -0,0 +1,30 @@ | |||
| # eth_cancelBundle | |||
There was a problem hiding this comment.
🛠️ Refactor suggestion
Add missing frontmatter block
This file lacks the standard --- frontmatter (e.g., sidebar_position) present in other API reference docs—add it to ensure it appears correctly in the sidebar.
🤖 Prompt for AI Agents
In docs/mevblocker/searchers/API Reference/cancel_bundle.md at line 1, the file
is missing the standard frontmatter block used in other API reference documents.
Add a YAML frontmatter block at the top of the file enclosed by triple dashes
(---) including at least the sidebar_position key with an appropriate value to
ensure the document appears correctly in the sidebar navigation.
| "status": " The status of the submitted txs. Value can be INCLUDED / FAILED / UNKNOWN", | ||
| "hash": "The hash of the submitted transactions", | ||
| "rpc_timestamp": "The timestamp at which the transaction was received", | ||
| "transaction": | ||
| { | ||
| "from": "The sender of the transaction", | ||
| "to": "The receiver of the transaction", | ||
| "gas": "The amount of gas used for the transaction", | ||
| "nonce": "The nonce of the transaction", | ||
| "value": "" | ||
| }, |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Fix schema typos and improve descriptions.
Field descriptions contain errors (leading spaces, “txs,” empty value). Please clean up:
- Trim leading spaces.
- Expand “txs” to “transactions.”
- Provide a clear description for
value.
🤖 Prompt for AI Agents
In docs/mevblocker/orderflow-originators/API-reference/Transactions-status.md
around lines 19 to 29, fix the schema descriptions by removing leading spaces in
the "status" field description, replacing "txs" with "transactions," and adding
a clear, concise description for the "value" field instead of leaving it empty.
Ensure all descriptions are accurate and properly formatted.
| "referrer": "Where is the transaction originating from. If full, field will shopw string used my integrator ( ie CoWSwap) and if empty, it will show No Referrer", | ||
| "refundRecipient": "To which address is the backrun being sent to. If empty, the backrun is sent to tx.orign", | ||
| "refund": "Amount of ETH searchers were able to rebate via backrun" |
There was a problem hiding this comment.
Correct typos in referrer & refundRecipient.
- Change “shopw” to “show” and “my” to “by.”
- Fix “tx.orign” to “transaction origin” (or clearer wording).
🤖 Prompt for AI Agents
In docs/mevblocker/orderflow-originators/API-reference/Transactions-status.md
around lines 34 to 36, correct the typos in the descriptions: change "shopw" to
"show" and "my" to "by" in the referrer field, and replace "tx.orign" with
"transaction origin" or a clearer phrase in the refundRecipient field to improve
clarity and correctness.
|
|
||
| Note that transaction status can also be fetched via eth_getTransactionByHash. | ||
|
|
||
| INPUTS |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Rename “INPUTS” section.
This section describes the API’s response schema. Rename it to “Response” or “Response Schema” to avoid confusion.
🤖 Prompt for AI Agents
In docs/mevblocker/orderflow-originators/API-reference/Transactions-status.md at
line 15, rename the section header from "INPUTS" to "Response" or "Response
Schema" to accurately reflect that this section describes the API's response
schema and avoid confusion.
| ### 5. Searchers provide Backrunning Bids for the flow | ||
|
|
||
| After receiving the orders, searchers proceed to crunch their numbers and give their bundles back to MEV Blocker. Searchers are competing for the most profitable option and if they spot a backrun opportunity (real or fake), they submit a bundle to MEV Blocker RPC. | ||
|
|
||
| The searcher that provides the bundle with the highest rebate value for users gets selected as the winner (NOT the searcher that pays the highest fee to the validator). | ||
|
|
||
| ### 5. Searcher bundles get forwarded to builders to be included in the next block | ||
|
|
||
| In this step, the MEV Blocker system gathers all the searcher bundles, discards those containing fake transactions, and attaches the user signatures back to the transactions. |
There was a problem hiding this comment.
Fix inconsistent step numbering
The introduction promises “6 main steps,” but the headings repeat “5.” and go beyond six. Renumber the steps sequentially (1 through 6) to match the description and avoid confusion.
🤖 Prompt for AI Agents
In docs/mevblocker/concepts/order-flow-auction.md around lines 35 to 43, the
step headings are incorrectly numbered as "5." multiple times, causing
inconsistency with the promised "6 main steps." Renumber these step headings
sequentially from 1 to 6 to match the introduction and maintain clear, logical
progression.
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (7)
docs/mevblocker/README.mdx (7)
3-3: Improve phrasing for clarity.
The phrase “MEV Blocker is the #1 leading MEV-protection RPC solution by transaction volume and rebates.” is redundant. Consider simplifying:- ## MEV Blocker is the #1 leading MEV-protection RPC solution by transaction volume and rebates. + ## MEV Blocker is the leading MEV-protection RPC solution by transaction volume and rebates.
5-5: Enhance image alt text for clarity.
The alt textMEV Blockeris generic. Consider a more descriptive alt, e.g.,MEV Blocker overview illustration, to improve accessibility.
9-11: Fix grammar and remove extra article.
The list item reads “created by the their flow” and has inconsistent spacing. Update to:- * Give users/integrators a rebate from backrunning opportunities created by the their flow + * Give users/integrators a rebate from backrunning opportunities created by their flow
15-15: Replace question mark with colon.
Section header should end with:not?for consistency:- The key advantages that MEV Blocker offers in comparison to other RPCs are the following? + The key advantages that MEV Blocker offers in comparison to other RPCs are the following:
17-21: Fix typos and improve punctuation.
- Change
is innovative→its innovative.- Change
public within in a→public with a.- Add missing apostrophe in
dont→don'tand comma beforeand.- Correct
pubslish→publish.- * **Inclusion time →** MEV Blocker is the fastest RPC across the market due to is innovative Builder fee mechanism. + * **Inclusion time →** MEV Blocker is the fastest RPC across the market due to its innovative Builder fee mechanism. - * **Transparent →** All our data is public within in a 30s delay. Unlike other RPCs we dont play games with your flow and we stand by the data we pubslish. + * **Transparent →** All our data is public with a 30s delay. Unlike other RPCs, we don't play games with your flow, and we stand by the data we publish.
25-25: Improve grammar for clarity.
The sentence is awkward. Consider:- Check out our RPC Benchmark Comparison study to see how MEV Blocker performance across speed, backruns, and success, compares to other RPCs. + Check out our RPC Benchmark Comparison study to see how MEV Blocker performs in speed, backruns, and success compared to other RPCs.
27-27: Enhance image alt text for accessibility.
The current alt textGuideis too generic. Use something like:-  + 
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (35)
static/img/mevblocker/Backruns_1.pngis excluded by!**/*.pngstatic/img/mevblocker/Backruns_2.pngis excluded by!**/*.pngstatic/img/mevblocker/Backruns_3.pngis excluded by!**/*.pngstatic/img/mevblocker/Backruns_4.pngis excluded by!**/*.pngstatic/img/mevblocker/Backruns_5.pngis excluded by!**/*.pngstatic/img/mevblocker/Metamask_1_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Metamask_2_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Metamask_3_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Metamask_4_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Metamask_5_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Metamask_6_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Metamask_7_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Metamask_8_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Rabby_1_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Rabby_2_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Rabby_3_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Rabby_4_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Rabby_5_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Rabby_6_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Rainbow_1_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Rainbow_2_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Rainbow_3_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Rainbow_4_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Rainbow_5_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Rainbow_6_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/Rainbow_7_optimized.pngis excluded by!**/*.pngstatic/img/mevblocker/concept1-1200x630.pngis excluded by!**/*.pngstatic/img/mevblocker/ispeed_1.pngis excluded by!**/*.pngstatic/img/mevblocker/mevblocker_1.pngis excluded by!**/*.pngstatic/img/mevblocker/mevblocker_2.pngis excluded by!**/*.pngstatic/img/mevblocker/mevblocker_comparison.pngis excluded by!**/*.pngstatic/img/mevblocker/mevblocker_ofa.pngis excluded by!**/*.pngstatic/img/mevblocker/price_improvement_1.pngis excluded by!**/*.pngstatic/img/mevblocker/price_improvement_2.pngis excluded by!**/*.pngstatic/img/mevblocker/success_rate_1.pngis excluded by!**/*.png
📒 Files selected for processing (1)
docs/mevblocker/README.mdx(1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/mevblocker/README.mdx
[grammar] ~10-~10: A determiner cannot be combined with a possessive pronoun. Did you mean simply “the” or “their”?
Context: ...om backrunning opportunities created by the their flow * Provide the fastest inclusion t...
(A_MY)
[uncategorized] ~19-~19: A comma might be missing here.
Context: ...lic within in a 30s delay. Unlike other RPCs we dont play games with your flow and w...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[uncategorized] ~19-~19: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...r RPCs we dont play games with your flow and we stand by the data we pubslish. * **C...
(COMMA_COMPOUND_SENTENCE)
🔇 Additional comments (1)
docs/mevblocker/README.mdx (1)
29-29: Verify link target.
Ensure that/mevblocker/rpc-performanceresolves correctly to the RPC Performance Study page and matches your sidebar configuration.
| import DocCardList from '@theme/DocCardList'; | ||
|
|
||
| Ethereum: All features are supported on Ethereum. | ||
| <DocCardList /> No newline at end of file |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Move import to top of file.
MDX requires import statements before any Markdown content. Please relocate:
- import DocCardList from '@theme/DocCardList';
-
- <DocCardList />to the top of the file (e.g., right below other imports), then render <DocCardList /> in place of the current position.
Committable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In docs/mevblocker/README.mdx around lines 35 to 37, the import statement for
DocCardList is placed after some Markdown content, which is not allowed in MDX.
Move the import statement to the very top of the file, just below any existing
import statements, and keep the <DocCardList /> component rendering at its
current position in the content.
| - Selectively including transactions or manipulating refund outcomes | ||
|
|
||
| - **No shadow identities or fee evasion** | ||
| Builders may not attempt to bypass the fee mechanism by operating "shadow builders" or other manipulative schemes. |
There was a problem hiding this comment.
Builders may not --> Builders must not
pretf00d
left a comment
pretf00d
left a comment
There was a problem hiding this comment.
added a further round of reviews here
There was a problem hiding this comment.
Actionable comments posted: 9
♻️ Duplicate comments (7)
docs/mevblocker/searchers/README.mdx (3)
3-3: Branding & typo (“MEV Blockers” / “backruning”).
Same issues previously raised remain untouched.
15-16: Malformed mailto link & spelling (“biding”).
Issue already reported and still present.
17-19: Move MDX import to top of file.
Imports must precede any Markdown.docs/mevblocker/orderflow-originators/Endpoints.md (2)
69-79: Boost endpoint link / code-block mismatch still unfixed.
See prior comments.
41-48: Fix header and paragraph typos.- ## Restrictred Searcher Configuration + ## Restricted Searcher Configuration @@ - As you might have read in ##concepts, MEV Blocker shares transaction information with all permissionlessly connected searchers because it mixes real transactions with fake transactions. In the event of using "vanila AMM swaps", the fake transactions are good enough to spoof searchers to not not know which of the transactions are real or fake. However, if you participate in more "advanced swaps protocols" such as CoW Swap, 1inch fusion, or Uniswap X, your solution might be a bit more complex than the "vanialla swaps", and hence the fake transactions might not be as good at spoofing real transaction information from searchers. + As explained in **Concepts**, MEV Blocker shares transaction information with all permissionlessly-connected searchers by mixing real and fake transactions. For simple “vanilla AMM swaps,” the fake transactions are sufficient to prevent searchers from knowing which ones are real. For more complex protocols—CoW Swap, 1inch Fusion, Uniswap X, etc.—this spoofing is less effective.docs/mevblocker/builders/README.mdx (1)
3-3: Consistent casing (“MEV blocker”).
Still lowercase; should be “MEV Blocker.”docs/mevblocker/README.mdx (1)
35-37: Import still after Markdown – must move to top
Same issue flagged previously; MDX imports have to precede any content.
🧹 Nitpick comments (13)
docs/mevblocker/orderflow-originators/Endpoints.md (1)
13-39: Code blocks are plain URLs – usetext, notjsx.-```jsx +```textApply to all endpoint URL blocks (Fast, No Revert, Full Privacy, Max Backruns, No Checks).
docs/mevblocker/rpc-performance/README.mdx (2)
12-15: Proper names & casing.- Flashbot ranks similarly or just below MEV blocker in time to + Flashbots ranks similarly, or just below MEV Blocker, in time to(Company is “Flashbots”; keep MEV Blocker capitalised.)
20-21: Spelling error (“alternativly”).- ...study, or alternativly here is the full paper: + ...study, or alternatively read the full paper:docs/mevblocker/README.mdx (4)
3-3: Tone & redundancy – consider slimming the superlative headline“#1 leading” is redundant marketing fluff. A crisper alternative:
-## MEV Blocker is the #1 leading MEV-protection RPC solution by transaction volume and rebates. +## MEV Blocker is the leading MEV-protection RPC by volume and rebates
9-11: Grammar/punctuation in bullet list
- Duplicate article: “the their flow”.
- Capitalisation after bullet asterisk is inconsistent.
- Extra space after the asterisk.
-* Give users/integrators a rebate from backrunning opportunities created by the their flow +* Give users and integrators rebates from back-running opportunities created by their flowRepeat the pattern for the other bullets to keep a uniform one-space indent and sentence-case starts.
17-17: Possessive typo – “its”, not “it's”-* **Inclusion time →** MEV Blocker is the fastest RPC across the market due to it's innovative Builder fee mechanism. +* **Inclusion time →** MEV Blocker is the fastest RPC across the market due to its innovative builder-fee mechanism.
19-19: Multiple spelling & style issues in transparency bullet‐ Double space after “data”.
‐ “dont” → “don't”.
‐ “pubslish” → “publish”.-* **Transparent →** All our data is public within a 30 second delay. Unlike other RPCs we dont play games with your flow and we stand by the data we pubslish. +* **Transparent →** All data is public within 30 seconds. Unlike other RPCs, we don’t play games with your flow—we stand by the data we publish.docs/mevblocker/orderflow-originators/Integrators/Intent_applications.md (1)
21-27: List indentation breaks markdownlint (MD005)The “2.” item is indented by one space, so the list renders incorrectly.
- 2. **Customize Your Setup** +2. **Customize Your Setup**Do the same for items 3 and 4 to keep consistent zero-indent ordered list.
docs/mevblocker/orderflow-originators/API-reference/Sending-transactions.md (3)
7-7: Minor formatting & double spaceRemove the double space after “Blocker” and wrap method names in back-ticks:
-MEV Blocker supports sending transactions via the standard eth_sendRawTransaction method +MEV Blocker supports sending transactions via the standard `eth_sendRawTransaction` method
123-124: Grammar – stray “and this all”-… never shares transactions inside the public mempool anyway, and this all received transactions are private by definition. +… never shares transactions with the public mempool; all received transactions are private by definition.
144-150: Typo – “successfull”-A successfull response will return true: +A successful response will return `true`:docs/mevblocker/concepts/order-flow-auction.md (2)
19-21: Missing period after “3” and spacing
### 3 MEV Blocker …should be### 3. MEV Blocker …for consistency.
58-58: Use dash list style to satisfy markdownlint (MD004)Switch
*to-or configure linter.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (14)
docs/mevblocker/README.mdx(1 hunks)docs/mevblocker/builders/README.mdx(1 hunks)docs/mevblocker/concepts/MEV/MEV.md(1 hunks)docs/mevblocker/concepts/gas_rebates.md(1 hunks)docs/mevblocker/concepts/order-flow-auction.md(1 hunks)docs/mevblocker/orderflow-originators/API-reference/Sending-transactions.md(1 hunks)docs/mevblocker/orderflow-originators/API-reference/configuring-fee-recipient-address.md(1 hunks)docs/mevblocker/orderflow-originators/Endpoints.md(1 hunks)docs/mevblocker/orderflow-originators/Integrators/Intent_applications.md(1 hunks)docs/mevblocker/rpc-performance/README.mdx(1 hunks)docs/mevblocker/rpc-performance/backrunning.md(1 hunks)docs/mevblocker/rpc-performance/inclusion-speed.md(1 hunks)docs/mevblocker/rpc-performance/success-reate.md(1 hunks)docs/mevblocker/searchers/README.mdx(1 hunks)
✅ Files skipped from review due to trivial changes (1)
- docs/mevblocker/orderflow-originators/API-reference/configuring-fee-recipient-address.md
🚧 Files skipped from review as they are similar to previous changes (4)
- docs/mevblocker/rpc-performance/inclusion-speed.md
- docs/mevblocker/rpc-performance/success-reate.md
- docs/mevblocker/concepts/MEV/MEV.md
- docs/mevblocker/rpc-performance/backrunning.md
🧰 Additional context used
🧠 Learnings (9)
📓 Common learnings
Learnt from: pretf00d
PR: cowprotocol/docs#512
File: docs/mevblocker/concepts/gas_rebates.md:16-16
Timestamp: 2025-06-30T14:12:14.869Z
Learning: When referring to MEV Blocker or other products/services in documentation, use "that" instead of "who" as the relative pronoun (e.g., "MEV Blocker is the only RPC that has..." not "MEV Blocker is the only RPC who has...") because products are not people.
docs/mevblocker/builders/README.mdx (1)
Learnt from: pretf00d
PR: cowprotocol/docs#512
File: docs/mevblocker/concepts/gas_rebates.md:16-16
Timestamp: 2025-06-30T14:12:14.869Z
Learning: When referring to MEV Blocker or other products/services in documentation, use "that" instead of "who" as the relative pronoun (e.g., "MEV Blocker is the only RPC that has..." not "MEV Blocker is the only RPC who has...") because products are not people.
docs/mevblocker/orderflow-originators/API-reference/Sending-transactions.md (1)
Learnt from: pretf00d
PR: cowprotocol/docs#512
File: docs/mevblocker/concepts/gas_rebates.md:16-16
Timestamp: 2025-06-30T14:12:14.869Z
Learning: When referring to MEV Blocker or other products/services in documentation, use "that" instead of "who" as the relative pronoun (e.g., "MEV Blocker is the only RPC that has..." not "MEV Blocker is the only RPC who has...") because products are not people.
docs/mevblocker/README.mdx (1)
Learnt from: pretf00d
PR: cowprotocol/docs#512
File: docs/mevblocker/concepts/gas_rebates.md:16-16
Timestamp: 2025-06-30T14:12:14.869Z
Learning: When referring to MEV Blocker or other products/services in documentation, use "that" instead of "who" as the relative pronoun (e.g., "MEV Blocker is the only RPC that has..." not "MEV Blocker is the only RPC who has...") because products are not people.
docs/mevblocker/concepts/gas_rebates.md (1)
Learnt from: pretf00d
PR: cowprotocol/docs#512
File: docs/mevblocker/concepts/gas_rebates.md:16-16
Timestamp: 2025-06-30T14:12:14.869Z
Learning: When referring to MEV Blocker or other products/services in documentation, use "that" instead of "who" as the relative pronoun (e.g., "MEV Blocker is the only RPC that has..." not "MEV Blocker is the only RPC who has...") because products are not people.
docs/mevblocker/orderflow-originators/Endpoints.md (1)
Learnt from: pretf00d
PR: cowprotocol/docs#512
File: docs/mevblocker/concepts/gas_rebates.md:16-16
Timestamp: 2025-06-30T14:12:14.869Z
Learning: When referring to MEV Blocker or other products/services in documentation, use "that" instead of "who" as the relative pronoun (e.g., "MEV Blocker is the only RPC that has..." not "MEV Blocker is the only RPC who has...") because products are not people.
docs/mevblocker/orderflow-originators/Integrators/Intent_applications.md (1)
Learnt from: pretf00d
PR: cowprotocol/docs#512
File: docs/mevblocker/concepts/gas_rebates.md:16-16
Timestamp: 2025-06-30T14:12:14.869Z
Learning: When referring to MEV Blocker or other products/services in documentation, use "that" instead of "who" as the relative pronoun (e.g., "MEV Blocker is the only RPC that has..." not "MEV Blocker is the only RPC who has...") because products are not people.
docs/mevblocker/rpc-performance/README.mdx (1)
Learnt from: pretf00d
PR: cowprotocol/docs#512
File: docs/mevblocker/concepts/gas_rebates.md:16-16
Timestamp: 2025-06-30T14:12:14.869Z
Learning: When referring to MEV Blocker or other products/services in documentation, use "that" instead of "who" as the relative pronoun (e.g., "MEV Blocker is the only RPC that has..." not "MEV Blocker is the only RPC who has...") because products are not people.
docs/mevblocker/searchers/README.mdx (1)
Learnt from: pretf00d
PR: cowprotocol/docs#512
File: docs/mevblocker/concepts/gas_rebates.md:16-16
Timestamp: 2025-06-30T14:12:14.869Z
Learning: When referring to MEV Blocker or other products/services in documentation, use "that" instead of "who" as the relative pronoun (e.g., "MEV Blocker is the only RPC that has..." not "MEV Blocker is the only RPC who has...") because products are not people.
🪛 LanguageTool
docs/mevblocker/concepts/order-flow-auction.md
[style] ~44-~44: Consider a more concise word here.
Context: ... signatures back to the transactions. In order to have their bundles forwarded to builder...
(IN_ORDER_TO_PREMIUM)
[style] ~45-~45: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...an arbitrary amount denominated in ETH. In theory, searchers have an internal valu...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
docs/mevblocker/README.mdx
[grammar] ~19-~19: Ensure spelling is correct
Context: ...h your flow and we stand by the data we pubslish. * Customizable → MEV Blocker offer...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/mevblocker/concepts/gas_rebates.md
[grammar] ~11-~11: Ensure spelling is correct
Context: ...d on network demand for blockspace. The baseFee ensures that if transactions pay such f...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~12-~12: Ensure spelling is correct
Context: ...our transaction faster than others. The priorityFee allows builders to tip make a more valu...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~16-~16: Ensure spelling is correct
Context: ...te, MEV Blocker processes around 10% of dailty Etherem transcations, and MEV Blocker currently protects a...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~20-~20: As a shorter alternative for ‘able to’, consider using “can”.
Context: ... with the transaction path, MEV Blocker is able to recover part of the Priority Fee that w...
(BE_ABLE_TO)
docs/mevblocker/orderflow-originators/Endpoints.md
[grammar] ~43-~43: Ensure spelling is correct
Context: ...n might be a bit more complex than the "vanialla swaps", and hence the fake transactions...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/mevblocker/rpc-performance/README.mdx
[style] ~5-~5: ‘exact same’ might be wordy. Consider a shorter alternative.
Context: ...luating their execution quality for the exact same transactions. Through a systematic anal...
(EN_WORDINESS_PREMIUM_EXACT_SAME)
[grammar] ~20-~20: Ensure spelling is correct
Context: ...each of the categories of the study, or alternativly here is the full paper: ### [Private M...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
docs/mevblocker/searchers/README.mdx
[grammar] ~10-~10: Ensure spelling is correct
Context: ...wever, there is also the possibility of backruning CoW Swap flow. In order to do so, and b...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~10-~10: Consider a more concise word here.
Context: ...ossibility of backruning CoW Swap flow. In order to do so, and because of the itnriquises a...
(IN_ORDER_TO_PREMIUM)
🪛 markdownlint-cli2 (0.17.2)
docs/mevblocker/concepts/order-flow-auction.md
11-11: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
58-58: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
docs/mevblocker/orderflow-originators/Integrators/Intent_applications.md
24-24: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 1
(MD005, list-indent)
| The above methods are for backrunning general flow for MEV Blocker, however, there is also the possibility of backruning CoW Swap flow. In order to do so, and because of the itnriquises and complexity of CoW Swaps solver settlements, Searchers need to be whitelisted. | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Clean up typos and awkward phrasing in CoW-Swap paragraph.
“backruning”, “itnriquises”, and double “not” break readability and credibility.
- The above methods are for backrunning general flow for MEV Blocker, however, there is also the possibility of backruning CoW Swap flow. In order to do so, and because of the itnriquises and complexity of CoW Swaps solver settlements, Searchers need to be whitelisted.
+ The above methods cover general back-running on MEV Blocker. Back-running CoW Swap flow is also possible, but—due to the intricacies and complexity of CoW Swap solver settlements—searchers must first be whitelisted.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| The above methods are for backrunning general flow for MEV Blocker, however, there is also the possibility of backruning CoW Swap flow. In order to do so, and because of the itnriquises and complexity of CoW Swaps solver settlements, Searchers need to be whitelisted. | |
| The above methods cover general back-running on MEV Blocker. Back-running CoW Swap flow is also possible, but—due to the intricacies and complexity of CoW Swap solver settlements—searchers must first be whitelisted. |
🧰 Tools
🪛 LanguageTool
[grammar] ~10-~10: Ensure spelling is correct
Context: ...wever, there is also the possibility of backruning CoW Swap flow. In order to do so, and b...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[style] ~10-~10: Consider a more concise word here.
Context: ...ossibility of backruning CoW Swap flow. In order to do so, and because of the itnriquises a...
(IN_ORDER_TO_PREMIUM)
🤖 Prompt for AI Agents
In docs/mevblocker/searchers/README.mdx around lines 10 to 11, correct the typos
and awkward phrasing in the paragraph about CoW Swap flow. Fix the misspellings
"backruning" to "backrunning" and "itnriquises" to "intricacies," and remove any
double negatives such as double "not" to improve readability and clarity.
| import DocCardList from '@theme/DocCardList'; | ||
|
|
||
| <DocCardList /> |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Import order violation.
Move import DocCardList … above the front-matter header. MDX fails at build time when imports appear after Markdown.
🤖 Prompt for AI Agents
In docs/mevblocker/builders/README.mdx around lines 37 to 39, the import
statement for DocCardList is placed after the front-matter header, which causes
MDX build failures. Move the import statement for DocCardList to appear above
the front-matter header at the very top of the file to comply with MDX import
order requirements.
| import DocCardList from '@theme/DocCardList'; | ||
|
|
||
| <DocCardList /> |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Import at bottom—must be at top.
Same MDX rule as other files.
🤖 Prompt for AI Agents
In docs/mevblocker/rpc-performance/README.mdx around lines 26 to 28, the import
statement for DocCardList is placed at the bottom of the file, which violates
MDX conventions. Move the import statement to the top of the file before any JSX
or content to comply with MDX rules.
| All Ethereum transaction require a gas fee to get included onchain. This gas fee can be broken down into two categories: | ||
|
|
||
| - **Base Fee**: A required network fee that automatically adjusts based on network demand for blockspace. The baseFee ensures that if transactions pay such fee, they are processed and included in a block. | ||
| - **Priority Fee**: An optional additional payment for builders to include your transaction faster than others. The priorityFee allows builders to tip make a more valuable block and hence, gives you a higher chance of fast inclusion in a block. |
There was a problem hiding this comment.
Grammar & clarity in gas-fee section.
- All Ethereum transaction require a gas fee to get included onchain.
+ All Ethereum transactions require a gas fee to be included on-chain.
@@
- **Priority Fee**: An optional additional payment for builders to include your transaction faster than others. The priorityFee allows builders to tip make a more valuable block and hence, gives you a higher chance of fast inclusion in a block.
+ **Priority Fee**: An optional tip that incentivises builders to include your transaction sooner. This tip makes the block more valuable and increases your chance of fast inclusion.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| All Ethereum transaction require a gas fee to get included onchain. This gas fee can be broken down into two categories: | |
| - **Base Fee**: A required network fee that automatically adjusts based on network demand for blockspace. The baseFee ensures that if transactions pay such fee, they are processed and included in a block. | |
| - **Priority Fee**: An optional additional payment for builders to include your transaction faster than others. The priorityFee allows builders to tip make a more valuable block and hence, gives you a higher chance of fast inclusion in a block. | |
| All Ethereum transactions require a gas fee to be included on-chain. This gas fee can be broken down into two categories: | |
| - **Base Fee**: A required network fee that automatically adjusts based on network demand for blockspace. The baseFee ensures that if transactions pay such fee, they are processed and included in a block. | |
| - **Priority Fee**: An optional tip that incentivises builders to include your transaction sooner. This tip makes the block more valuable and increases your chance of fast inclusion. |
🧰 Tools
🪛 LanguageTool
[grammar] ~11-~11: Ensure spelling is correct
Context: ...d on network demand for blockspace. The baseFee ensures that if transactions pay such f...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~12-~12: Ensure spelling is correct
Context: ...our transaction faster than others. The priorityFee allows builders to tip make a more valu...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🤖 Prompt for AI Agents
In docs/mevblocker/concepts/gas_rebates.md around lines 9 to 12, improve grammar
and clarity in the gas fee explanation by correcting sentence structure and word
usage. For example, change "All Ethereum transaction require" to "All Ethereum
transactions require," clarify "the baseFee ensures that if transactions pay
such fee" to a clearer phrase like "transactions that pay this fee," and
rephrase "priorityFee allows builders to tip make a more valuable block" to
"priorityFee allows builders to tip, making a block more valuable." Make these
adjustments to enhance readability and correctness.
| MEV blocker is the only RPC that has a permissionless Order Flow Auction for which both searchers and builders are bound to public rules. To this date, MEV Blocker processes around 10% of dailty Etherem transcations, and | ||
|
|
||
| MEV Blocker currently protects and routes over 20% of all Ethereum mainnet transactions daily. It maintains strong relationships with top block builders — the entities responsible for selecting and packaging transactions into Ethereum blocks. |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Multiple typos and casing.
- MEV blocker is the only RPC that has a permissionless Order Flow Auction for which both searchers and builders are bound to public rules. To this date, MEV Blocker processes around 10% of dailty Etherem transcations, and
+ MEV Blocker is the only RPC that has a permissionless Order Flow Auction with public rules for both searchers and builders. To date, MEV Blocker processes roughly 10 % of daily Ethereum transactions, and📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| MEV blocker is the only RPC that has a permissionless Order Flow Auction for which both searchers and builders are bound to public rules. To this date, MEV Blocker processes around 10% of dailty Etherem transcations, and | |
| MEV Blocker currently protects and routes over 20% of all Ethereum mainnet transactions daily. It maintains strong relationships with top block builders — the entities responsible for selecting and packaging transactions into Ethereum blocks. | |
| --- a/docs/mevblocker/concepts/gas_rebates.md | |
| +++ b/docs/mevblocker/concepts/gas_rebates.md | |
| @@ -16,1 +16,1 @@ | |
| - MEV blocker is the only RPC that has a permissionless Order Flow Auction for which both searchers and builders are bound to public rules. To this date, MEV Blocker processes around 10% of dailty Etherem transcations, and | |
| + MEV Blocker is the only RPC that has a permissionless Order Flow Auction with public rules for both searchers and builders. To date, MEV Blocker processes roughly 10 % of daily Ethereum transactions, and |
🧰 Tools
🪛 LanguageTool
[grammar] ~16-~16: Ensure spelling is correct
Context: ...te, MEV Blocker processes around 10% of dailty Etherem transcations, and MEV Blocker currently protects a...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🤖 Prompt for AI Agents
In docs/mevblocker/concepts/gas_rebates.md around lines 16 to 18, correct the
multiple typos and casing errors: change "dailty" to "daily," "Etherem" to
"Ethereum," and ensure consistent capitalization of "MEV Blocker" throughout the
text.
| ```jsx | ||
| { | ||
| { | ||
| jsonrpc: "2.0", | ||
| id: 1, | ||
| method: "eth_cancelTransaction", | ||
| params: [ | ||
| // The hash of the transaction to be cancelled | ||
| "0xb8101baf6bfd31243578e8847c12316f47318f567b02296fdf7fc783bef74826" | ||
| ] | ||
| } | ||
| ``` |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Broken JSON structure & wrong code fence language
Two opening braces and trailing commas make the snippet unparsable. Also, use json instead of jsx to enable syntax highlighting.
```json
{
"jsonrpc": "2.0",
"id": 1,
"method": "eth_cancelTransaction",
"params": [
"0xb8101baf6bfd31243578e8847c12316f47318f567b02296fdf7fc783bef74826"
]
}🤖 Prompt for AI Agents
In docs/mevblocker/orderflow-originators/API-reference/Sending-transactions.md
around lines 131 to 142, fix the JSON snippet by removing the extra opening
brace and any trailing commas to ensure valid JSON structure. Also, change the
code fence language from jsx to json for correct syntax highlighting.
| "params": ["0xbb3a336e3f823ec18197f1e13ee875700f08f03e2cab75f0d0b118dabb44cba0"], // your_tx_hash | ||
| "id": 1 | ||
| } |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Comments inside JSON are invalid
The example includes // your_tx_hash, which is not valid JSON and will break copy-paste tests. Either remove or convert to explanatory text.
- "params": ["0xbb3a...cba0"], // your_tx_hash
+ "params": ["0xbb3a...cba0"]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "params": ["0xbb3a336e3f823ec18197f1e13ee875700f08f03e2cab75f0d0b118dabb44cba0"], // your_tx_hash | |
| "id": 1 | |
| } | |
| "params": ["0xbb3a...cba0"], | |
| "id": 1 | |
| } |
🤖 Prompt for AI Agents
In docs/mevblocker/orderflow-originators/API-reference/Sending-transactions.md
around lines 51 to 53, the JSON example contains an invalid comment `//
your_tx_hash` inside the params array. Remove this comment from the JSON to
ensure it is valid and can be copy-pasted without errors. If explanation is
needed, add it as separate text outside the JSON block.
| MEV Blocker's transaction flow can be broken down into 6 main steps. The image below shows a general overview of the flow of a transaction. | ||
|
|
There was a problem hiding this comment.
Step count mismatch – says 6, lists 9
The intro promises “6 main steps” but the document enumerates nine. Update the count or consolidate steps.
🤖 Prompt for AI Agents
In docs/mevblocker/concepts/order-flow-auction.md around lines 7 to 8, the
introduction states there are "6 main steps" in the transaction flow, but the
document actually lists 9 steps. Update the introductory sentence to reflect the
correct number of steps or revise the steps to consolidate them into 6 main
steps to ensure consistency.
| ### 1. Builders pay subscription fee and connect to MEV Blocker | ||
|
|
||
| Connected builders pay a weekly fee for MEV Blocker access, calculated per block won as a percentage of the previous period's average per-block value of MEVBlocker flow. The fee is computed monthly and posted onchain weekly, and is based on verifiable public data (e.g., Dune query). | ||
|
|
||
| ### 2. Order Flow Originators connect to MEV Blocker RPC Endpoint/s |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Heading-level jump (MD001)
### directly after # skips ##. Make step headings ## (or make the intro ##) for hierarchical correctness.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
11-11: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
In docs/mevblocker/concepts/order-flow-auction.md around lines 11 to 15, the
heading levels jump from a single # to ###, skipping ##. Adjust the heading
levels to maintain proper hierarchy by changing the step headings from ### to ##
or by making the introductory heading ## instead of #, ensuring consistent and
correct markdown structure.
@pretf00d the comments you made I had already merged edditing directly in the file instead of creating a new one. This is why on the change preview you dont see them but on the actual file its like your suggested text, so this should be ready to merge. |
4 participants
Description
This commit restructures and updates MEV Blockers docs to the new formart and structure.
Changes
It changes the entire doc structure, folders, subfolders etc, adds new one (RPC Performance Study etc)
Summary by CodeRabbit
New Features
Documentation
Refactor
Removals