From 7d8e8ae9a60c31eb5adc0d32dbc7fc6fb8a8858e Mon Sep 17 00:00:00 2001 From: Haris Angelidakis Date: Tue, 7 Mar 2023 23:58:29 +0000 Subject: [PATCH] GITBOOK-141: No subject --- .../output-batch-auction-solutions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/off-chain-services/in-depth-solver-specification/output-batch-auction-solutions.md b/off-chain-services/in-depth-solver-specification/output-batch-auction-solutions.md index 1d7bab7..c422bbf 100644 --- a/off-chain-services/in-depth-solver-specification/output-batch-auction-solutions.md +++ b/off-chain-services/in-depth-solver-specification/output-batch-auction-solutions.md @@ -135,7 +135,7 @@ We now discuss some additional functionality that solvers are allowed to use. Si If both conditions are satisfied, a solver can set the `"internal"` flag to `true` in order to internalize the interaction:\ \ -`"exec_plan": "internal"` +`"internal": true` In such a case, the driver will remove the interaction, and so the solution will end up using less gas, get better ranking, and also be risk-free (at least the part involving the internalized AMM interaction). We stress that the `exec_plan` coordinates must always be provided, even if the interaction will end up being internalized.