From 2db2acf945ce8213926e16d8c780375eec3995b9 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Wed, 20 Nov 2024 08:35:39 -0500 Subject: [PATCH] This note still uses the old order (#176) --- docs/network/smart-rollup-nodes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/network/smart-rollup-nodes.md b/docs/network/smart-rollup-nodes.md index ca529503..98dbdf37 100644 --- a/docs/network/smart-rollup-nodes.md +++ b/docs/network/smart-rollup-nodes.md @@ -138,7 +138,7 @@ Converting the observer node to maintenance mode requires these prerequisites: Using a public layer 1 node as the basis for a Smart Rollup node in maintenance or operator mode exposes the Smart Rollup node to security risks. For example, a malicious layer 1 node can expose the Smart Rollup node to an incorrect branch, which can cause the Smart Rollup node to post invalid commitments and lose tez when other node operators computing from the correct branch refute them. - As these steps describe, it is safe to bootstrap a node in observer mode by connecting it to a public node, switch to maintenance or operator mode, and then promptly connect it to a layer 1 node that you control. + As these steps describe, it is safe to bootstrap a node in observer mode by connecting it to a public node, connect it to a layer 1 node that you control, and then switch to maintenance or operator mode. :::