From c8a38b77657cd6d2ed1614a875937f70b3cd813a Mon Sep 17 00:00:00 2001
From: "dr. mia von steinkirch, phd"
<1130416+mvonsteinkirch@users.noreply.github.com>
Date: Thu, 9 Feb 2023 13:16:35 -0800
Subject: [PATCH] add types of private order flows
---
MEV_searchers/private_order_flows/101.md | 30 ++++++++++++++++++++++++
1 file changed, 30 insertions(+)
create mode 100644 MEV_searchers/private_order_flows/101.md
diff --git a/MEV_searchers/private_order_flows/101.md b/MEV_searchers/private_order_flows/101.md
new file mode 100644
index 0000000..9cee2cd
--- /dev/null
+++ b/MEV_searchers/private_order_flows/101.md
@@ -0,0 +1,30 @@
+### types of private order flows
+
+
+
+
+
+
+
+
+
+
+
+#### rpc-based "payment for order flow protocols" (POFPs)
+
+* this type of private order flows can be realized by modifying either the user's rpc or by modifying the protocol's frontend
+* the rpc endpoint re-broadcasts (forwarding) the tx to nodes.
+* in respect to every pending tx they receive, they can: 1) censor, 2) forward to some mempool, or 3) forward it directly to some block-builders or validators.
+
+
+
+#### validator transaction reordering protocols (VTRPs)
+
+
+
+* private tx reordering
+* two goals: 1) identify valuable user txs, 2) replace the POFP's value-extracted tx with its own value-extractive tx
+* when a VTRP is able to identify a valuable user tx but, due to the tactics of the POFP, is unable to inject its own transaction in place of the POFP's -> VTRP's optimal strategy is to censor the user's transaction from the final block
+
+
+