Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add docs for blockHash response for mev_sendBundle #7

Merged
merged 7 commits into from
May 5, 2023
Merged

Add docs for blockHash response for mev_sendBundle #7

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
d2575e5
Add block hash response document
Wazzymandias May 5, 2023
dedefba
Update TOC
Wazzymandias May 5, 2023
0fb08fa
Update docs
Wazzymandias May 5, 2023
a40cd16
Update formatting
Wazzymandias May 5, 2023
e2bb470
Formatting is hard
Wazzymandias May 5, 2023
12370fe
Update for consistency
Wazzymandias May 5, 2023
7335eb4
moar consistency
Wazzymandias May 5, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Formatting is hard
  • Loading branch information
@Wazzymandias
Wazzymandias committed May 5, 2023
commit e2bb47076e452c62b870ce585e3505d04054fa9c
18 changes: 9 additions & 9 deletions specs/bundles/v0.1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,14 +5,14 @@ Users and searchers can use `mev_sendBundle` to send a bundle of transactions [a
<!-- TOC -->
* [`mev_sendBundle`](#mevsendbundle)
* [JSON-RPC Request Scheme](#json-rpc-request-scheme)
* [`version`](#version)
* [`inclusion`](#inclusion)
* [`body`](#body)
* [Example](#example)
* [`version`](#version)
* [`inclusion`](#inclusion)
* [`body`](#body)
* [Example](#example)
* [Bundle Composition](#bundle-composition)
* [`validity`](#validity)
* [`privacy`](#privacy)
* [Response](#response-)
* [`validity`](#validity)
* [`privacy`](#privacy)
* [JSON-RPC Response Scheme](#json-rpc-response-scheme)
* [`blockHash`](#blockhash)
<!-- TOC -->

Expand Down Expand Up @@ -178,7 +178,7 @@ The `refundConfig` is specified by the original party (eg. user) who sends an in

The `refund` is set by the matchmaker. It identifies what items in the bundle should be refunded -- ie. when a searcher submits a new bundle back to the Matchmaker, what indices contained hashes. The builder must simulate the bundle without these input transactions to determine what portion of the overall bundle payment came from searcher bids and should be redistributed. If bundles contain multiple input items then the Matchmaker is responsible for allocating the searcher bids across the other items in the bundle. The party who submits the input to the matchmaker could also use this field to specify their preference for what percentage of the searcher bid they receive. The matchmaker would use this information when producing the final `refund` field that is sent to a block builder.

## `privacy`
### `privacy`

Preferences on what data should be shared about the bundle and its transactions. Optional.

Expand All @@ -187,7 +187,7 @@ Preferences on what data should be shared about the bundle and its transactions.
| `hints` | Array of strings; optional | Each item additively specifies which data about all transactions in the bundle to share. If no hints are specified, no data is shared. Transactions from other users that do not specify the same hints will not share additional information. |
| `targetBuilders` | Array of strings; optional | Builders that have permission to receive this bundle and include it in a block. |

## Response
## JSON-RPC Response Scheme
```typescript
type responseBody = {
"blockHash": number[32]
Expand Down