Add svr bundles instructions (#3580)

* Add svr bundles instructions

* Fix format

* empty commit: trigger automation

---------

Co-authored-by: devin distefano <devin.distefano@smartcontract.com>

Author: dimriou

public/samples/DataFeeds/SVR/bundle-bid.json

@@ -0,0 +1,22 @@
+{
+  "jsonrpc": "2.0",
+  "method": "mev_sendBundle",
+  "params": [
+    {
+      "version": "v0.1",
+      "inclusion": {
+        "block": "0x01",
+        "maxBlock": "0x04"
+      },
+      "body": [
+        {
+          "hash": "0x_bundle_event_hash"
+        },
+        {
+          "tx": "0x0213a...",
+          "canRevert": false
+        }
+      ]
+    }
+  ]
+}

public/samples/DataFeeds/SVR/bundle-transaction-event.json

@@ -0,0 +1,15 @@
+{
+  "hash": "0x_bundle_event_hash",
+  "txs": [
+    {
+      "to": "0x45ab36b69e02e59d3c49b863b31f530c991dd554",
+      "functionSelector": "0x6fadcf72",
+      "callData": "0x80640b.....................a2354d"
+    },
+    {
+      "to": "0x45ab36b69e02e59d3c49b863b31f530c991dd554",
+      "functionSelector": "0x6fadcf72",
+      "callData": "0x12340b.....................a2354d"
+    }
+  ]
+}

public/samples/DataFeeds/SVR/single-transaction-event.json

@@ -0,0 +1,10 @@
+{
+  "hash": "0x_single_transaction_event_hash",
+  "txs": [
+    {
+      "to": "0x45ab36b69e02e59d3c49b863b31f530c991dd554",
+      "functionSelector": "0x6fadcf72",
+      "callData": "0x80640b.....................a2354d"
+    }
+  ]
+}

src/content/data-feeds/llms-full.txt

@@ -6343,8 +6343,43 @@ Chainlink SVR uses forwarder contracts to route feed updates. You typically see
 
 3. **callData**: The `callData` includes the parameters for `transmitSecondary()` on the aggregator contract. You can decode this if you need to extract the updated price when the onchain event is not emitted (details in the section below).
 
+Here's an example of a single transaction event:
+
+```json
+{
+  "hash": "0x_single_transaction_event_hash",
+  "txs": [
+    {
+      "to": "0x45ab36b69e02e59d3c49b863b31f530c991dd554",
+      "functionSelector": "0x6fadcf72",
+      "callData": "0x80640b.....................a2354d"
+    }
+  ]
+}
+```
+
 Below are code examples for setting up a listener that monitors the MEV-Share event stream for SVR feed updates. These examples show how to connect to the stream, filter for relevant transactions with the `6fadcf72` function selector, and process incoming events:
 
+The event stream is also expected to occasionally transmit transaction bundles. The bundle event has a similar format to the single transaction event, but with more than one transactions. Transactions will be bundled in nonce ascending order, meaning txs[0] has the lowest nonce and txs[len(txs)] has the highest. Below is an example of a bundle:
+
+```json
+{
+  "hash": "0x_bundle_event_hash",
+  "txs": [
+    {
+      "to": "0x45ab36b69e02e59d3c49b863b31f530c991dd554",
+      "functionSelector": "0x6fadcf72",
+      "callData": "0x80640b.....................a2354d"
+    },
+    {
+      "to": "0x45ab36b69e02e59d3c49b863b31f530c991dd554",
+      "functionSelector": "0x6fadcf72",
+      "callData": "0x12340b.....................a2354d"
+    }
+  ]
+}
+```
+
 #### 3. Decode `callData` for `forward` and `transmitSecondary`
 
 Once you've identified a potential SVR feed update transaction, you'll need to decode its payload. This step allows you to extract:
@@ -6470,6 +6505,33 @@ Below are code examples demonstrating how to construct and submit bundles to the
 
 For gas management, simulations, and other advanced usage, see the official [Flashbots documentation](https://docs.flashbots.net/).
 
+Bidding for bundle events is very similar to single transaction events. As a searcher, you can append your transaction at the end of the bundle by using the bundle event hash just like you would with the single transaction event hash. Below is an example:
+
+```json
+{
+  "jsonrpc": "2.0",
+  "method": "mev_sendBundle",
+  "params": [
+    {
+      "version": "v0.1",
+      "inclusion": {
+        "block": "0x01",
+        "maxBlock": "0x04"
+      },
+      "body": [
+        {
+          "hash": "0x_bundle_event_hash"
+        },
+        {
+          "tx": "0x0213a...",
+          "canRevert": false
+        }
+      ]
+    }
+  ]
+}
+```
+
 #### 7. Considerations
 
 - **Competition**: Multiple searchers might detect the same liquidation. The best bid typically wins.

src/content/data-feeds/svr-feeds/searcher-onboarding-ethereum.mdx

@@ -112,6 +112,10 @@ Chainlink SVR uses forwarder contracts to route feed updates. You typically see
 
 1. **callData**: The `callData` includes the parameters for `transmitSecondary()` on the aggregator contract. You can decode this if you need to extract the updated price when the onchain event is not emitted (details in the section below).
 
+Here's an example of a single transaction event:
+
+<CodeSample src="samples/DataFeeds/SVR/single-transaction-event.json" />
+
 Below are code examples for setting up a listener that monitors the MEV-Share event stream for SVR feed updates. These examples show how to connect to the stream, filter for relevant transactions with the `6fadcf72` function selector, and process incoming events:
 
 <Tabs client:visible>
@@ -125,6 +129,10 @@ Below are code examples for setting up a listener that monitors the MEV-Share ev
   </Fragment>
 </Tabs>
 
+The event stream is also expected to occasionally transmit transaction bundles. The bundle event has a similar format to the single transaction event, but with more than one transactions. Transactions will be bundled in nonce ascending order, meaning txs[0] has the lowest nonce and txs[len(txs)] has the highest. Below is an example of a bundle:
+
+<CodeSample src="samples/DataFeeds/SVR/bundle-transaction-event.json" />
+
 #### 3. Decode `callData` for `forward` and `transmitSecondary`
 
 Once you've identified a potential SVR feed update transaction, you'll need to decode its payload. This step allows you to extract:
@@ -284,6 +292,10 @@ Below are code examples demonstrating how to construct and submit bundles to the
 
 For gas management, simulations, and other advanced usage, see the official [Flashbots documentation](https://docs.flashbots.net/).
 
+Bidding for bundle events is very similar to single transaction events. As a searcher, you can append your transaction at the end of the bundle by using the bundle event hash just like you would with the single transaction event hash. Below is an example:
+
+<CodeSample src="samples/DataFeeds/SVR/bundle-bid.json" />
+
 #### 7. Considerations
 
 - **Competition**: Multiple searchers might detect the same liquidation. The best bid typically wins.