From 2635140558ed28b6e1a519791112d39ff624440e Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Wed, 29 Jan 2025 10:06:46 -0500 Subject: [PATCH 1/5] More info about recovering bond --- docs/architecture/smart-rollups.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/architecture/smart-rollups.md b/docs/architecture/smart-rollups.md index 990ced482..0cbe9abfa 100644 --- a/docs/architecture/smart-rollups.md +++ b/docs/architecture/smart-rollups.md @@ -2,7 +2,7 @@ title: Smart Rollups authors: 'Nomadic Labs, TriliTech, Tim McMackin' last_update: - date: 17 January 2025 + date: 29 January 2025 --- Smart Rollups play a crucial part in providing high scalability on Tezos. @@ -87,8 +87,10 @@ When a user runs a node that posts commitments, the protocol automatically locks If the node posts a commitment that is refuted, they lose their bond, as described in [Refutation periods](#refutation-periods). Because nodes have the length of the refutation to challenge another node's commitment, the bond stays locked until the end of the refutation period for the last commitment that the node posted. -After that refutation period ends, the node operator can recover the bond, which unlocks their tez. +After that refutation period ends, the node operator can recover the bond with the `octez-client recover bond` command, which unlocks their tez. To simplify the process, node operators can switch to bailout mode, which does not post commitments but continues to defend previously made commitments until the last refutation period ends. +Then it runs the `octez-client recover bond` command automatically. +For an example of how to use bailout mode to recover your bond, see [Stopping the Smart Rollup node](https://docs.etherlink.com/network/smart-rollup-nodes/#stopping-the-smart-rollup-node) in the Etherlink documentation. ### Reveal data channel From 81b121aef6f5d18b71670540cb9127af53d6c321 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Wed, 29 Jan 2025 12:09:20 -0500 Subject: [PATCH 2/5] Clarify options for recovering bonds Co-authored-by: NicNomadic <148877430+NicNomadic@users.noreply.github.com> --- docs/architecture/smart-rollups.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/architecture/smart-rollups.md b/docs/architecture/smart-rollups.md index 0cbe9abfa..27e763136 100644 --- a/docs/architecture/smart-rollups.md +++ b/docs/architecture/smart-rollups.md @@ -87,9 +87,9 @@ When a user runs a node that posts commitments, the protocol automatically locks If the node posts a commitment that is refuted, they lose their bond, as described in [Refutation periods](#refutation-periods). Because nodes have the length of the refutation to challenge another node's commitment, the bond stays locked until the end of the refutation period for the last commitment that the node posted. -After that refutation period ends, the node operator can recover the bond with the `octez-client recover bond` command, which unlocks their tez. -To simplify the process, node operators can switch to bailout mode, which does not post commitments but continues to defend previously made commitments until the last refutation period ends. -Then it runs the `octez-client recover bond` command automatically. +The node operator can recover the bond in different ways: +- using the `octez-client recover bond` command, which unlocks their tez after the refutation period ends. +- alternatively, by switching the rollup node to bailout mode, which does not post commitments but continues to defend previously made commitments until the last refutation period ends, then runs the `octez-client recover bond` command automatically. For an example of how to use bailout mode to recover your bond, see [Stopping the Smart Rollup node](https://docs.etherlink.com/network/smart-rollup-nodes/#stopping-the-smart-rollup-node) in the Etherlink documentation. ### Reveal data channel From b85df783f0447ef7b9fdc24d18e356f7d507435b Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Wed, 29 Jan 2025 12:10:24 -0500 Subject: [PATCH 3/5] Formatting --- docs/architecture/smart-rollups.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/architecture/smart-rollups.md b/docs/architecture/smart-rollups.md index 27e763136..237dc9755 100644 --- a/docs/architecture/smart-rollups.md +++ b/docs/architecture/smart-rollups.md @@ -88,8 +88,10 @@ If the node posts a commitment that is refuted, they lose their bond, as describ Because nodes have the length of the refutation to challenge another node's commitment, the bond stays locked until the end of the refutation period for the last commitment that the node posted. The node operator can recover the bond in different ways: -- using the `octez-client recover bond` command, which unlocks their tez after the refutation period ends. -- alternatively, by switching the rollup node to bailout mode, which does not post commitments but continues to defend previously made commitments until the last refutation period ends, then runs the `octez-client recover bond` command automatically. + +- Using the `octez-client recover bond` command, which unlocks their tez after the refutation period ends. + +- By switching the rollup node to bailout mode, which does not post commitments but continues to defend previously made commitments until the last refutation period ends, then runs the `octez-client recover bond` command automatically. For an example of how to use bailout mode to recover your bond, see [Stopping the Smart Rollup node](https://docs.etherlink.com/network/smart-rollup-nodes/#stopping-the-smart-rollup-node) in the Etherlink documentation. ### Reveal data channel From 5d4ba07f9dd0261e5701c1de989af371c69e5a39 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Thu, 30 Jan 2025 09:16:25 -0500 Subject: [PATCH 4/5] Just show one option --- docs/architecture/smart-rollups.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/docs/architecture/smart-rollups.md b/docs/architecture/smart-rollups.md index 237dc9755..409db97a8 100644 --- a/docs/architecture/smart-rollups.md +++ b/docs/architecture/smart-rollups.md @@ -87,11 +87,16 @@ When a user runs a node that posts commitments, the protocol automatically locks If the node posts a commitment that is refuted, they lose their bond, as described in [Refutation periods](#refutation-periods). Because nodes have the length of the refutation to challenge another node's commitment, the bond stays locked until the end of the refutation period for the last commitment that the node posted. -The node operator can recover the bond in different ways: +Recovering the bond safely takes a few steps; in general, node operators follow these steps: -- Using the `octez-client recover bond` command, which unlocks their tez after the refutation period ends. +1. Switch the rollup node to a mode that defends previously made commitments but does not post new commitments, such as `accuser` mode or `bailout` mode. + +1. Wait until the last commitment is cemented. +If operators shut down the node before the last commitment is cemented, they risk losing their bond if another node challenges their commitments. + +1. Recover the bond by running the `octez-client recover bond` command, which unlocks their tez. +Nodes running in `bailout` mode run this command automatically when the last commitment is cemented. -- By switching the rollup node to bailout mode, which does not post commitments but continues to defend previously made commitments until the last refutation period ends, then runs the `octez-client recover bond` command automatically. For an example of how to use bailout mode to recover your bond, see [Stopping the Smart Rollup node](https://docs.etherlink.com/network/smart-rollup-nodes/#stopping-the-smart-rollup-node) in the Etherlink documentation. ### Reveal data channel From f795a551c82f07b590294420090970bc81d0e9df Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Thu, 30 Jan 2025 09:50:38 -0500 Subject: [PATCH 5/5] Keep the node running --- docs/architecture/smart-rollups.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/architecture/smart-rollups.md b/docs/architecture/smart-rollups.md index 409db97a8..27f1d626b 100644 --- a/docs/architecture/smart-rollups.md +++ b/docs/architecture/smart-rollups.md @@ -91,7 +91,7 @@ Recovering the bond safely takes a few steps; in general, node operators follow 1. Switch the rollup node to a mode that defends previously made commitments but does not post new commitments, such as `accuser` mode or `bailout` mode. -1. Wait until the last commitment is cemented. +1. Keep the node running until the last commitment is cemented. If operators shut down the node before the last commitment is cemented, they risk losing their bond if another node challenges their commitments. 1. Recover the bond by running the `octez-client recover bond` command, which unlocks their tez.