From be41c647f77e7f4bda70194269ed4f85ff48078d Mon Sep 17 00:00:00 2001 From: Christian Matt Date: Mon, 1 Sep 2025 21:52:22 +0200 Subject: [PATCH 1/3] Move section on querying for proposers. --- docs.json | 1 - .../get-started/providers/Querying-for-proposers.mdx | 11 ----------- v1.1.0/get-started/providers/sending-commitments.mdx | 6 +++++- 3 files changed, 5 insertions(+), 13 deletions(-) delete mode 100644 v1.1.0/get-started/providers/Querying-for-proposers.mdx diff --git a/docs.json b/docs.json index c787bef2..81d25f95 100644 --- a/docs.json +++ b/docs.json @@ -57,7 +57,6 @@ "v1.1.0/get-started/providers/registering-a-provider", "v1.1.0/get-started/providers/consuming-bids", "v1.1.0/get-started/providers/sending-commitments", - "v1.1.0/get-started/providers/Querying-for-proposers", "v1.1.0/get-started/providers/withdraw" ] } diff --git a/v1.1.0/get-started/providers/Querying-for-proposers.mdx b/v1.1.0/get-started/providers/Querying-for-proposers.mdx deleted file mode 100644 index 2f460170..00000000 --- a/v1.1.0/get-started/providers/Querying-for-proposers.mdx +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: 'Querying for Proposers' -description: Use the pointers below to determine whether an upcoming proposer has opted in to mev-commit or not. -sidebarTitle: Querying for Proposers ---- - -## Querying for Proposers API - -Although querying for proposers may be more appropriate for bidders, provider nodes still have the ability to access this API. - -See [Querying for Proposers API](/v1.1.0/get-started/bidders/bidder-node-commands#querying-for-proposers-api) for more information. diff --git a/v1.1.0/get-started/providers/sending-commitments.mdx b/v1.1.0/get-started/providers/sending-commitments.mdx index e4ddfd15..ede62a76 100644 --- a/v1.1.0/get-started/providers/sending-commitments.mdx +++ b/v1.1.0/get-started/providers/sending-commitments.mdx @@ -3,7 +3,7 @@ title: Sending Commitments sidebarTitle: Sending Commitments --- -To send your first commitment, you will need to connect to the mev-commit Testnet. This will allow you to consume bids incoming to the network and submit commitments. To do this, you'll want to run an emulator to simulate accepting and rejecting bids. +To send your first commitment, you will need to connect to the mev-commit network. This will allow you to consume bids incoming to the network and submit commitments. To do this, you'll want to run an emulator to simulate accepting and rejecting bids. You will want to connect to a decisioning system that will accept and reject bids based on custom criteria. You can read more about the API to open a gRPC stream [here](/v1.1.0/api-reference/provider/sendprocessedbids). @@ -154,3 +154,7 @@ func ...() { This should help you integrate bid processing into your system, allowing you to receive bid information and send back processed bids as commitments. + +## Querying for Proposers + +For advanced decision making, it may be relevant whether the next proposer is opted into mev-commit or not. While this functionality is mainly for bidders, provider nodes also have the ability to access the corresponding API as described in [Querying for Proposers API](/v1.1.0/get-started/bidders/bidder-node-commands#querying-for-proposers-api). From 63a73a5732d36dd3dd2fe2255b062f40e2c2fc83 Mon Sep 17 00:00:00 2001 From: Christian Matt Date: Mon, 1 Sep 2025 22:05:54 +0200 Subject: [PATCH 2/3] Rephrase. --- v1.1.0/get-started/providers/sending-commitments.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v1.1.0/get-started/providers/sending-commitments.mdx b/v1.1.0/get-started/providers/sending-commitments.mdx index ede62a76..bd38a46b 100644 --- a/v1.1.0/get-started/providers/sending-commitments.mdx +++ b/v1.1.0/get-started/providers/sending-commitments.mdx @@ -157,4 +157,4 @@ This should help you integrate bid processing into your system, allowing you to ## Querying for Proposers -For advanced decision making, it may be relevant whether the next proposer is opted into mev-commit or not. While this functionality is mainly for bidders, provider nodes also have the ability to access the corresponding API as described in [Querying for Proposers API](/v1.1.0/get-started/bidders/bidder-node-commands#querying-for-proposers-api). +For advanced decision making, it may be relevant whether the next proposer is opted into mev-commit or not. Information on the opted in validators can be obtained as explained in [Querying for Proposers API](/v1.1.0/get-started/bidders/bidder-node-commands#querying-for-proposers-api). From 0694e7d388614dfb8d0db77b20fdb88daa9fd7b6 Mon Sep 17 00:00:00 2001 From: Christian Matt Date: Mon, 1 Sep 2025 22:13:12 +0200 Subject: [PATCH 3/3] Rephrase. --- v1.1.0/get-started/providers/sending-commitments.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v1.1.0/get-started/providers/sending-commitments.mdx b/v1.1.0/get-started/providers/sending-commitments.mdx index bd38a46b..06adce04 100644 --- a/v1.1.0/get-started/providers/sending-commitments.mdx +++ b/v1.1.0/get-started/providers/sending-commitments.mdx @@ -157,4 +157,4 @@ This should help you integrate bid processing into your system, allowing you to ## Querying for Proposers -For advanced decision making, it may be relevant whether the next proposer is opted into mev-commit or not. Information on the opted in validators can be obtained as explained in [Querying for Proposers API](/v1.1.0/get-started/bidders/bidder-node-commands#querying-for-proposers-api). +For advanced decision making, it may be relevant whether the next proposer is opted into mev-commit or not. Information on the opted in validators can be obtained via the [Querying for Proposers API](/v1.1.0/get-started/bidders/bidder-node-commands#querying-for-proposers-api).