From 4bd19056d47b94b605d629a6e518fc80b0c0bd98 Mon Sep 17 00:00:00 2001 From: MoonShiesty Date: Mon, 24 Feb 2025 04:44:21 +0000 Subject: [PATCH 1/4] revert-sip-45 --- sips/sip-revert-sip-45 | 59 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 59 insertions(+) create mode 100644 sips/sip-revert-sip-45 diff --git a/sips/sip-revert-sip-45 b/sips/sip-revert-sip-45 new file mode 100644 index 0000000..1997fe3 --- /dev/null +++ b/sips/sip-revert-sip-45 @@ -0,0 +1,59 @@ +| SIP-Number | | +| ---: | :--- | +| Title | revert SIP-45 | +| Description | revert SIP-45 deterministic block order | +| Author | moonshiesty<@moonshiesty> | +| Editor | | +| Type | Standard | +| Category | Core | +| Created | 2025-02-23 | +| Comments-URI | | +| Status | | +| Requires | | + +## Abstract + +Revert deterministic block ordering as implemented in SIP-45 + +## Motivation + +SIP-45 does not achieve it's goals of prioritizing block-submission and instead provides a deterministic mechanism for searchers to position their transactions within a block by manipulating gas price + +for example SIP-45 allows a searcher to construct a sandwich by paying +1 of the target gas price on the frontrun and -1 unit SUI of the target gas price on the backrun. this is the optimal strategy for any searcher. + +for backruns SIP-45 also does not maximize value for validators since it will always be optimial for searchers to pay exactly -1 unit of SUI to be ordered right after the target + +for arbitrage SIP-45 does maximize validator value, at the risk of providing yet another mechanism for arbitragers themselves to be deterministically frontrun + + +## Specification + +Revert SIP-45 and begin exploring of one of two approaches: + +1) make consensus ordering random. sui randomness already provides a seed to randomly reorder transactions. this approach likely requires an additional hop to sequence consensus. this attempts minimizes extractable value by making it non-deterministic for searchers to place a transaction within a block. my concern with this approach is that searchers can attempt to statistically frontrun targets by spamming transactions that revert if they don't land in the right spot + +2) allow allow validators to specify how they want to be consensus ordering and expose an API for searchers to propose ordering. this approach will maximize extractable value for validators and provide the equivalent of a "block-building" API on SUI + + +## Rationale + +reverting SIP-45 an important issue because deterministic block ordering exposes users to MEV without a way to protect themselves through fee markets + +front-running on SUI is possible whenever either: +1) protocol leaks information about transactions +2) a validator leaks information about transaction certification + +because shio is leaking user transactions this is present concern to SUI users + +source: + +https://x.com/moon_shiesty/status/1893783038653571292 + +## Backwards Compatibility + + +no issues with backwards compatibility + +## Security Considerations + +None From 2ed6973c1b52f9add5045a154c95601ff5f1ef6b Mon Sep 17 00:00:00 2001 From: MoonShiesty Date: Mon, 24 Feb 2025 17:59:12 +0000 Subject: [PATCH 2/4] add .md extension, typo --- sips/{sip-revert-sip-45 => sip-revert-sip-45.md} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename sips/{sip-revert-sip-45 => sip-revert-sip-45.md} (91%) diff --git a/sips/sip-revert-sip-45 b/sips/sip-revert-sip-45.md similarity index 91% rename from sips/sip-revert-sip-45 rename to sips/sip-revert-sip-45.md index 1997fe3..06bb012 100644 --- a/sips/sip-revert-sip-45 +++ b/sips/sip-revert-sip-45.md @@ -32,7 +32,7 @@ Revert SIP-45 and begin exploring of one of two approaches: 1) make consensus ordering random. sui randomness already provides a seed to randomly reorder transactions. this approach likely requires an additional hop to sequence consensus. this attempts minimizes extractable value by making it non-deterministic for searchers to place a transaction within a block. my concern with this approach is that searchers can attempt to statistically frontrun targets by spamming transactions that revert if they don't land in the right spot -2) allow allow validators to specify how they want to be consensus ordering and expose an API for searchers to propose ordering. this approach will maximize extractable value for validators and provide the equivalent of a "block-building" API on SUI +2) allow validators to specify how they want to be consensus ordering and expose an API for searchers to propose ordering. this approach will maximize extractable value for validators and provide the equivalent of a "block-building" API on SUI ## Rationale From f1b51cea416f20c0c64ab3569c284e530ea88e20 Mon Sep 17 00:00:00 2001 From: MoonShiesty Date: Mon, 24 Feb 2025 18:06:56 +0000 Subject: [PATCH 3/4] reword --- sips/sip-revert-sip-45.md | 19 ++++++++----------- 1 file changed, 8 insertions(+), 11 deletions(-) diff --git a/sips/sip-revert-sip-45.md b/sips/sip-revert-sip-45.md index 06bb012..e7a0590 100644 --- a/sips/sip-revert-sip-45.md +++ b/sips/sip-revert-sip-45.md @@ -1,7 +1,7 @@ | SIP-Number | | | ---: | :--- | | Title | revert SIP-45 | -| Description | revert SIP-45 deterministic block order | +| Description | revert SIP-45 deterministic consensus transaction ordering | | Author | moonshiesty<@moonshiesty> | | Editor | | | Type | Standard | @@ -13,11 +13,11 @@ ## Abstract -Revert deterministic block ordering as implemented in SIP-45 +Revert deterministic transaction ordering for consensus as implemented in SIP-45 ## Motivation -SIP-45 does not achieve it's goals of prioritizing block-submission and instead provides a deterministic mechanism for searchers to position their transactions within a block by manipulating gas price +SIP-45 does not achieve it's goals of prioritizing transaction-submission and instead provides a deterministic mechanism for searchers to position their transactions within a consensus checkpoint by manipulating gas price for example SIP-45 allows a searcher to construct a sandwich by paying +1 of the target gas price on the frontrun and -1 unit SUI of the target gas price on the backrun. this is the optimal strategy for any searcher. @@ -30,9 +30,9 @@ for arbitrage SIP-45 does maximize validator value, at the risk of providing yet Revert SIP-45 and begin exploring of one of two approaches: -1) make consensus ordering random. sui randomness already provides a seed to randomly reorder transactions. this approach likely requires an additional hop to sequence consensus. this attempts minimizes extractable value by making it non-deterministic for searchers to place a transaction within a block. my concern with this approach is that searchers can attempt to statistically frontrun targets by spamming transactions that revert if they don't land in the right spot +1) make consensus ordering random. sui randomness already provides a seed to randomly reorder transactions within consensus checkpoints. this approach likely requires an additional hop to consensus (+~130ms). this attempts to minimize extractable value by making it non-deterministic for searchers to place a transaction within a consensus checkpoint. the primary concern with this approach is that searchers can attempt to statistically frontrun targets by spamming transactions that revert if they don't land in the right spot -2) allow validators to specify how they want to be consensus ordering and expose an API for searchers to propose ordering. this approach will maximize extractable value for validators and provide the equivalent of a "block-building" API on SUI +2) allow validators to specify consensus ordering and expose an API for searchers to propose a consensus ordering. this approach will maximize extractable value for validators and provides the equivalent of a ["block-building"](https://github.com/ethereum/builder-specs?tab=readme-ov-file) API on SUI ## Rationale @@ -43,17 +43,14 @@ front-running on SUI is possible whenever either: 1) protocol leaks information about transactions 2) a validator leaks information about transaction certification -because shio is leaking user transactions this is present concern to SUI users +because shio is leaking user transactions, this is present concern to SUI users -source: - -https://x.com/moon_shiesty/status/1893783038653571292 +[source from author's X profile](https://x.com/moon_shiesty/status/1893783038653571292) ## Backwards Compatibility - no issues with backwards compatibility ## Security Considerations -None +none From 4901090ffdfee2fbea22aea98bcd92828ddbb179 Mon Sep 17 00:00:00 2001 From: MoonShiesty Date: Mon, 24 Feb 2025 18:11:49 +0000 Subject: [PATCH 4/4] sui doesnt have blocks --- sips/sip-revert-sip-45.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sips/sip-revert-sip-45.md b/sips/sip-revert-sip-45.md index e7a0590..ab72c40 100644 --- a/sips/sip-revert-sip-45.md +++ b/sips/sip-revert-sip-45.md @@ -34,12 +34,12 @@ Revert SIP-45 and begin exploring of one of two approaches: 2) allow validators to specify consensus ordering and expose an API for searchers to propose a consensus ordering. this approach will maximize extractable value for validators and provides the equivalent of a ["block-building"](https://github.com/ethereum/builder-specs?tab=readme-ov-file) API on SUI - ## Rationale -reverting SIP-45 an important issue because deterministic block ordering exposes users to MEV without a way to protect themselves through fee markets +reverting SIP-45 is an important issue because deterministic consensus transaction ordering exposes users to MEV without a way to protect themselves through fee markets front-running on SUI is possible whenever either: + 1) protocol leaks information about transactions 2) a validator leaks information about transaction certification