From 15b15d96451e10a7c995cb0f173c031796217d79 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Tue, 21 Jan 2025 08:40:49 -0500 Subject: [PATCH 1/3] Stress --attester-profiles for DAL nodes --- docs/shell/dal_node.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/shell/dal_node.rst b/docs/shell/dal_node.rst index 1f3698b7d6c9..3e1ee457848e 100644 --- a/docs/shell/dal_node.rst +++ b/docs/shell/dal_node.rst @@ -79,7 +79,7 @@ A DAL node in controller mode can run in these profiles: octez-dal-node run --endpoint http://127.0.0.1:8732 --operator-profiles=0,1 --data-dir $DATA_DIR -- The ``attester`` profile is for bakers who want to attest to data. When an ``octez-baker`` daemon with attestation rights connects to a DAL node, it prompts the DAL node to run with the ``attester`` profile. The DAL node receives this prompt and runs in the ``attester`` profile unless it is running in bootstrap profile. To force the DAL node to run with the ``attester`` profile, pass the ``--attester-profiles`` argument with the public key hashes of the bakers to attest data for, as in this example: +- The ``attester`` profile is for bakers who want to attest to data. DAL nodes in this profile must pass the ``--attester-profiles`` argument with the public key hashes of the bakers to attest data for (not their consensus keys), as in this example: .. code-block:: shell -- GitLab From fcdf43612343f6553994a3cf64455e460fb0a645 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Tue, 21 Jan 2025 08:50:57 -0500 Subject: [PATCH 2/3] their delegate keys, not their consensus keys) --- docs/shell/dal_node.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/shell/dal_node.rst b/docs/shell/dal_node.rst index 3e1ee457848e..aad45fd163c6 100644 --- a/docs/shell/dal_node.rst +++ b/docs/shell/dal_node.rst @@ -79,7 +79,7 @@ A DAL node in controller mode can run in these profiles: octez-dal-node run --endpoint http://127.0.0.1:8732 --operator-profiles=0,1 --data-dir $DATA_DIR -- The ``attester`` profile is for bakers who want to attest to data. DAL nodes in this profile must pass the ``--attester-profiles`` argument with the public key hashes of the bakers to attest data for (not their consensus keys), as in this example: +- The ``attester`` profile is for bakers who want to attest to data. DAL nodes in this profile must pass the ``--attester-profiles`` argument with the public key hashes of the bakers to attest data for (their delegate keys, not their consensus keys), as in this example: .. code-block:: shell -- GitLab From 8c7157be8ba2f17be5054f84950af5215a8432aa Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Tue, 21 Jan 2025 09:06:38 -0500 Subject: [PATCH 3/3] Add a link --- docs/shell/dal_node.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/shell/dal_node.rst b/docs/shell/dal_node.rst index aad45fd163c6..a7f39d0ee863 100644 --- a/docs/shell/dal_node.rst +++ b/docs/shell/dal_node.rst @@ -79,7 +79,7 @@ A DAL node in controller mode can run in these profiles: octez-dal-node run --endpoint http://127.0.0.1:8732 --operator-profiles=0,1 --data-dir $DATA_DIR -- The ``attester`` profile is for bakers who want to attest to data. DAL nodes in this profile must pass the ``--attester-profiles`` argument with the public key hashes of the bakers to attest data for (their delegate keys, not their consensus keys), as in this example: +- The ``attester`` profile is for bakers who want to attest to data. DAL nodes in this profile must pass the ``--attester-profiles`` argument with the public key hashes of the bakers to attest data for (their delegate or manager keys, not their :ref:`consensus keys`), as in this example: .. code-block:: shell -- GitLab