From cc9899cf8d086f704ca46a6015a12567a8bf47bc Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Mon, 2 Dec 2024 13:51:42 -0500 Subject: [PATCH 01/14] Producer is now operator --- docs/shell/dal_node.rst | 26 ++++++++++---------------- 1 file changed, 10 insertions(+), 16 deletions(-) diff --git a/docs/shell/dal_node.rst b/docs/shell/dal_node.rst index 1869a3962fb5..b64592b8e449 100644 --- a/docs/shell/dal_node.rst +++ b/docs/shell/dal_node.rst @@ -40,13 +40,13 @@ You can set these profiles in the node's configuration file, as CLI arguments to The DAL node runs in these profiles: -- The ``producer`` profile (soon to be changed to the ``operator`` profile) is for users who are running a Smart Rollup and want to publish data to it. To run a DAL node with the ``producer`` profile, pass the ``--producer-profiles`` argument with the indexes of the slots to accept data for, as in this example: +- The ``operator`` profile (formerly the ``producer`` profile) is for users who are running a Smart Rollup and want to publish data to it. To run a DAL node with the ``operator`` profile, pass the ``--operator-profiles`` argument with the indexes of the slots to accept data for, as in this example: .. code-block:: shell - octez-dal-node run --endpoint http://127.0.0.1:8732 --producer-profiles=0,1 --data-dir $DATA_DIR + octez-dal-node run --endpoint http://127.0.0.1:8732 --operator-profiles=0,1 --data-dir $DATA_DIR - The configuration file for a DAL node running with the ``producer`` profile shows the slots that it accepts data for, as in this example: + The configuration file for a DAL node running with the ``operator`` profile shows the slots that it accepts data for, as in this example: .. code-block:: json @@ -54,17 +54,11 @@ The DAL node runs in these profiles: "data-dir": "dal-node/", "endpoint": "http://127.0.0.1:8732", "profiles": { - "kind": "operator", - "operator_profiles": [ - { - "kind": "producer", - "slot_index": 1 - }, - { - "kind": "producer", - "slot_index": 2 - } - ] + "kind": "controller", + "controller_profiles": { + "operators": [ 0, 1 ], + "observers": [], + "attesters": [] } } @@ -138,7 +132,7 @@ The DAL node runs in these profiles: } } -By default, the DAL node runs in the producer profile without subscribing to any topics. +By default, the DAL node runs in the operator profile without subscribing to any topics. Currently, the DAL node can use any combination of profiles except that the bootstrap profile is not compatible with any other profile. However, for future-proofing and for production installations, run a DAL node in a single profile. @@ -155,7 +149,7 @@ The amount of storage space a DAL node needs depends on how long it keeps the da - Bootstrap nodes store no DAL data and therefore require negligible storage. - Attester and observer nodes store data in memory for a few blocks after the attestation delay by default. -- Producer nodes store data on disk for 3 months by default because the data may be needed for the Smart Rollup refutation game. +- Operator nodes store data on disk for 3 months by default because the data may be needed for the Smart Rollup refutation game. You can set how long the node stores data with the ``--history-mode`` option. -- GitLab From 41b6b0f0142c0fb63110d751a54980993f0cef05 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Mon, 2 Dec 2024 13:55:14 -0500 Subject: [PATCH 02/14] Updated config files --- docs/shell/dal_node.rst | 28 ++++++++++------------------ 1 file changed, 10 insertions(+), 18 deletions(-) diff --git a/docs/shell/dal_node.rst b/docs/shell/dal_node.rst index b64592b8e449..46c94a160738 100644 --- a/docs/shell/dal_node.rst +++ b/docs/shell/dal_node.rst @@ -76,13 +76,11 @@ The DAL node runs in these profiles: "data-dir": "dal-node/", "endpoint": "http://127.0.0.1:8732", "profiles": { - "kind": "operator", - "operator_profiles": [ - { - "kind": "attester", - "public_key_hash": "tz1QCVQinE8iVj1H2fckqx6oiM85CNJSK9Sx" - } - ] + "kind": "controller", + "controller_profiles": { + "operators": [], + "observers": [], + "attesters": [ "tz1QCVQinE8iVj1H2fckqx6oiM85CNJSK9Sx" ] } } @@ -100,17 +98,11 @@ The DAL node runs in these profiles: "data-dir": "dal-node/", "endpoint": "http://127.0.0.1:8732", "profiles": { - "kind": "operator", - "operator_profiles": [ - { - "kind": "observer", - "slot_index": 1 - }, - { - "kind": "observer", - "slot_index": 2 - } - ] + "kind": "controller", + "controller_profiles": { + "operators": [], + "observers": [ 0, 1 ], + "attesters": [] } } -- GitLab From 8e388ef76fdd65007834a6442cbd0f1b957f1896 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Mon, 2 Dec 2024 20:49:52 +0000 Subject: [PATCH 03/14] running a Smart Rollup as an operator --- 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 46c94a160738..8093efc8d3d0 100644 --- a/docs/shell/dal_node.rst +++ b/docs/shell/dal_node.rst @@ -40,7 +40,7 @@ You can set these profiles in the node's configuration file, as CLI arguments to The DAL node runs in these profiles: -- The ``operator`` profile (formerly the ``producer`` profile) is for users who are running a Smart Rollup and want to publish data to it. To run a DAL node with the ``operator`` profile, pass the ``--operator-profiles`` argument with the indexes of the slots to accept data for, as in this example: +- The ``operator`` profile (formerly the ``producer`` profile) is for users who are running a Smart Rollup as an operator. To run a DAL node with the ``operator`` profile, pass the ``--operator-profiles`` argument with the indexes of the slots to accept data for, as in this example: .. code-block:: shell -- GitLab From 6e8a89c07069b00f91d00e8c7c70a300df02cfb3 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Mon, 2 Dec 2024 16:12:50 -0500 Subject: [PATCH 04/14] Controller mode and bootstrap mode --- docs/shell/dal_node.rst | 53 ++++++++++++++++++++++++----------------- 1 file changed, 31 insertions(+), 22 deletions(-) diff --git a/docs/shell/dal_node.rst b/docs/shell/dal_node.rst index 8093efc8d3d0..20e26fca492a 100644 --- a/docs/shell/dal_node.rst +++ b/docs/shell/dal_node.rst @@ -29,8 +29,35 @@ A bootstrap node remains connected to a large number of peers and is subscribed When a DAL node starts, it gets the URLs of the bootstrap nodes from its layer 1 node and uses these bootstrap nodes to connect to peers. When a DAL node does not have the necessary connections to the P2P network, bootstrap nodes provide connection points with the relevant topics. -.. _dal_profiles: +Modes +~~~~~ + +The DAL node has two modes: + +- Controller mode is for nodes that post, share, or attest data. + Nodes in this mode run in one or more profiles, as described below. + +- Bootstrap mode is for nodes that help other nodes connect to peers. + +Bootstrap mode is for starting a DAL network and providing entry points for other DAL nodes to become part of the network. To run a DAL node in bootstrap mode, pass the ``--bootstrap-profile`` argument, as in this example: + +.. code-block:: shell + + octez-dal-node run --endpoint http://127.0.0.1:8732 --bootstrap-profile --data-dir $DATA_DIR +The configuration file for a DAL node running in bootstrap mode shows only the base information about the node, as in this example: + +.. code-block:: json + + { + "data-dir": "dal-node/", + "endpoint": "http://127.0.0.1:8732", + "profiles": { + "kind": "bootstrap" + } + } + +.. _dal_profiles: Profiles ~~~~~~~~ @@ -38,7 +65,7 @@ Profiles Because node operators care about different parts of the DAL network, the DAL node runs in different profiles. You can set these profiles in the node's configuration file, as CLI arguments to the node's commands, or via RPC calls. -The DAL node runs in these profiles: +A DAL node in controller mode runs in these profiles: - The ``operator`` profile (formerly the ``producer`` profile) is for users who are running a Smart Rollup as an operator. To run a DAL node with the ``operator`` profile, pass the ``--operator-profiles`` argument with the indexes of the slots to accept data for, as in this example: @@ -106,27 +133,9 @@ The DAL node runs in these profiles: } } -- The ``bootstrap`` profile is for starting a DAL network and providing entry points for other DAL nodes to become part of the network. To run a DAL node with the ``bootstrap`` profile, pass the ``--bootstrap-profile`` argument, as in this example: - - .. code-block:: shell - - octez-dal-node run --endpoint http://127.0.0.1:8732 --bootstrap-profile --data-dir $DATA_DIR - - The configuration file for a DAL node running with the ``bootstrap`` profile shows only the base information about the node, as in this example: - - .. code-block:: json - - { - "data-dir": "dal-node/", - "endpoint": "http://127.0.0.1:8732", - "profiles": { - "kind": "bootstrap" - } - } - -By default, the DAL node runs in the operator profile without subscribing to any topics. +By default, the DAL node runs in controller mode with the operator profile without subscribing to any topics. -Currently, the DAL node can use any combination of profiles except that the bootstrap profile is not compatible with any other profile. +Currently, a DAL node in controller mode can use any combination of profiles. However, for future-proofing and for production installations, run a DAL node in a single profile. When a baker starts with the ``--dal-node`` argument, it checks the DAL node's configuration. -- GitLab From 260366bc5230b861b019c8fedea151f4e61f6ce4 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Tue, 3 Dec 2024 10:17:59 -0500 Subject: [PATCH 05/14] Clarify that controller mode is the most common --- docs/shell/dal_node.rst | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/shell/dal_node.rst b/docs/shell/dal_node.rst index 20e26fca492a..b3312e84130f 100644 --- a/docs/shell/dal_node.rst +++ b/docs/shell/dal_node.rst @@ -34,10 +34,12 @@ Modes The DAL node has two modes: -- Controller mode is for nodes that post, share, or attest data. - Nodes in this mode run in one or more profiles, as described below. +- Most nodes run in controller mode. + This mode is for nodes that post, share, or attest data. + Nodes in this mode run in one or more profiles to determine whether they post, share, or attest data, as described below. - Bootstrap mode is for nodes that help other nodes connect to peers. + Bootstrap nodes are already running on most Tezos networks, sp in most cases, you don't need to run a node in bootstrap node unless you are starting a new Tezos network or your controller node cannot contact any existing bootstrap nodes. Bootstrap mode is for starting a DAL network and providing entry points for other DAL nodes to become part of the network. To run a DAL node in bootstrap mode, pass the ``--bootstrap-profile`` argument, as in this example: -- GitLab From caf15dbf9c26c773261c1824d212cf09fd102dc8 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Tue, 3 Dec 2024 10:37:18 -0500 Subject: [PATCH 06/14] Clarify modes and profiles --- docs/shell/dal_node.rst | 61 ++++++++++++++++------------------------- 1 file changed, 23 insertions(+), 38 deletions(-) diff --git a/docs/shell/dal_node.rst b/docs/shell/dal_node.rst index b3312e84130f..fedd9df81033 100644 --- a/docs/shell/dal_node.rst +++ b/docs/shell/dal_node.rst @@ -34,11 +34,10 @@ Modes The DAL node has two modes: -- Most nodes run in controller mode. - This mode is for nodes that post, share, or attest data. - Nodes in this mode run in one or more profiles to determine whether they post, share, or attest data, as described below. +- **Controller mode** is appropriate for most nodes; it is for nodes that post, share, or attest data. + Nodes in this mode run in one or more profiles to determine what data they post, share, or attest, as described below. -- Bootstrap mode is for nodes that help other nodes connect to peers. +- **Bootstrap mode** is for nodes that help other nodes connect to peers. Bootstrap nodes are already running on most Tezos networks, sp in most cases, you don't need to run a node in bootstrap node unless you are starting a new Tezos network or your controller node cannot contact any existing bootstrap nodes. Bootstrap mode is for starting a DAL network and providing entry points for other DAL nodes to become part of the network. To run a DAL node in bootstrap mode, pass the ``--bootstrap-profile`` argument, as in this example: @@ -64,40 +63,35 @@ The configuration file for a DAL node running in bootstrap mode shows only the b Profiles ~~~~~~~~ -Because node operators care about different parts of the DAL network, the DAL node runs in different profiles. +As described above, different DAL node operators are interested in different data and doing different things with that data. +For this reason, DAL controller nodes run in different profiles; these profiles control which data the nodes post, share, and attest. You can set these profiles in the node's configuration file, as CLI arguments to the node's commands, or via RPC calls. -A DAL node in controller mode runs in these profiles: +Currently, a DAL node in controller mode can use any combination of profiles. +However, for future-proofing and for production installations, run a DAL controller node in a single profile. + +A DAL node in controller mode can run in these profiles: -- The ``operator`` profile (formerly the ``producer`` profile) is for users who are running a Smart Rollup as an operator. To run a DAL node with the ``operator`` profile, pass the ``--operator-profiles`` argument with the indexes of the slots to accept data for, as in this example: +- The ``operator`` profile (formerly the ``producer`` profile) is for users who are running a Smart Rollup as an operator and want to post data. To run a DAL node with the ``operator`` profile, pass the ``--operator-profiles`` argument with the indexes of the slots to accept data for, as in this example: .. code-block:: shell octez-dal-node run --endpoint http://127.0.0.1:8732 --operator-profiles=0,1 --data-dir $DATA_DIR - The configuration file for a DAL node running with the ``operator`` profile shows the slots that it accepts data for, as in this example: +- 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: - .. code-block:: json + .. code-block:: shell - { - "data-dir": "dal-node/", - "endpoint": "http://127.0.0.1:8732", - "profiles": { - "kind": "controller", - "controller_profiles": { - "operators": [ 0, 1 ], - "observers": [], - "attesters": [] - } - } + octez-dal-node run --endpoint http://127.0.0.1:8732 --attester-profiles=tz1QCVQinE8iVj1H2fckqx6oiM85CNJSK9Sx --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 ``observer`` profile contributes to the resilience of network by helping distribute data in the specified slots. To run a DAL node with the ``observer`` profile, pass the ``--observer-profiles`` argument with the indexes of the slots to monitor or an empty string (as in ``--observer-profiles ''``) to use a random index, as in this example: .. code-block:: shell - octez-dal-node run --endpoint http://127.0.0.1:8732 --attester-profiles=tz1QCVQinE8iVj1H2fckqx6oiM85CNJSK9Sx --data-dir $DATA_DIR + octez-dal-node run --endpoint http://127.0.0.1:8732 --observer-profiles=0,1 --data-dir $DATA_DIR - The configuration file for a DAL node running with the ``attester`` profile shows the public key hashes, as in this example: +The configuration file for a DAL controller node shows its active profiles. +For example, this configuration file shows that it is running in the ``operator`` profile and accepting data for slots 0 and 1: .. code-block:: json @@ -107,19 +101,13 @@ A DAL node in controller mode runs in these profiles: "profiles": { "kind": "controller", "controller_profiles": { - "operators": [], + "operators": [ 0, 1 ], "observers": [], - "attesters": [ "tz1QCVQinE8iVj1H2fckqx6oiM85CNJSK9Sx" ] + "attesters": [] } } -- The ``observer`` profile contributes to the resilience of network by helping distribute data in the specified slots. To run a DAL node with the ``observer`` profile, pass the ``--observer-profiles`` argument with the indexes of the slots to monitor or an empty string (as in ``--observer-profiles ''``) to use a random index, as in this example: - - .. code-block:: shell - - octez-dal-node run --endpoint http://127.0.0.1:8732 --observer-profiles=0,1 --data-dir $DATA_DIR - - The configuration file for a DAL node running with the ``observer`` profile shows the slots that it is monitoring, as in this example: +The configuration file for a DAL node running with the ``attester`` profile shows the public key hashes of the associated bakers, as in this example: .. code-block:: json @@ -130,15 +118,12 @@ A DAL node in controller mode runs in these profiles: "kind": "controller", "controller_profiles": { "operators": [], - "observers": [ 0, 1 ], - "attesters": [] + "observers": [], + "attesters": [ "tz1QCVQinE8iVj1H2fckqx6oiM85CNJSK9Sx" ] } } -By default, the DAL node runs in controller mode with the operator profile without subscribing to any topics. - -Currently, a DAL node in controller mode can use any combination of profiles. -However, for future-proofing and for production installations, run a DAL node in a single profile. +By default, the DAL node runs in controller mode with the operator profile without subscribing to any slots. When a baker starts with the ``--dal-node`` argument, it checks the DAL node's configuration. If the DAL node is not in bootstrap mode and not already set up with the ``attester`` profile, the baker configures the DAL node to use the attester profile associated with the keys that it is using. -- GitLab From 98d9588e176687864f99709912689325a37fb8ec Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Thu, 5 Dec 2024 14:52:49 +0000 Subject: [PATCH 07/14] Simplify --- 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 fedd9df81033..1061f6efe808 100644 --- a/docs/shell/dal_node.rst +++ b/docs/shell/dal_node.rst @@ -38,7 +38,7 @@ The DAL node has two modes: Nodes in this mode run in one or more profiles to determine what data they post, share, or attest, as described below. - **Bootstrap mode** is for nodes that help other nodes connect to peers. - Bootstrap nodes are already running on most Tezos networks, sp in most cases, you don't need to run a node in bootstrap node unless you are starting a new Tezos network or your controller node cannot contact any existing bootstrap nodes. + Bootstrap nodes are already running on most Tezos networks, so in most cases, you don't need to run a node in bootstrap node unless you are starting a new Tezos network. Bootstrap mode is for starting a DAL network and providing entry points for other DAL nodes to become part of the network. To run a DAL node in bootstrap mode, pass the ``--bootstrap-profile`` argument, as in this example: -- GitLab From 278eeb34ac5bdde056ff70d85a9070857cc5ef11 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Thu, 5 Dec 2024 17:38:29 +0000 Subject: [PATCH 08/14] without any profile. --- 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 1061f6efe808..ab3e38ba286e 100644 --- a/docs/shell/dal_node.rst +++ b/docs/shell/dal_node.rst @@ -123,7 +123,7 @@ The configuration file for a DAL node running with the ``attester`` profile show } } -By default, the DAL node runs in controller mode with the operator profile without subscribing to any slots. +By default, the DAL node runs in controller mode without any profile. When a baker starts with the ``--dal-node`` argument, it checks the DAL node's configuration. If the DAL node is not in bootstrap mode and not already set up with the ``attester`` profile, the baker configures the DAL node to use the attester profile associated with the keys that it is using. -- GitLab From f8aa1db2fe778163e7cb0ec779420f0460a0222c Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Thu, 5 Dec 2024 18:16:19 +0000 Subject: [PATCH 09/14] the slots registered with this profile for 3 months --- 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 ab3e38ba286e..1d404dffd787 100644 --- a/docs/shell/dal_node.rst +++ b/docs/shell/dal_node.rst @@ -137,7 +137,7 @@ The amount of storage space a DAL node needs depends on how long it keeps the da - Bootstrap nodes store no DAL data and therefore require negligible storage. - Attester and observer nodes store data in memory for a few blocks after the attestation delay by default. -- Operator nodes store data on disk for 3 months by default because the data may be needed for the Smart Rollup refutation game. +- Operator nodes store data on disk for the slots registered with this profile for 3 months by default because the data may be needed for the Smart Rollup refutation game. You can set how long the node stores data with the ``--history-mode`` option. -- GitLab From c77f227a7545a64dc5fac893dfe6271e592e9eb2 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Fri, 6 Dec 2024 09:13:57 -0500 Subject: [PATCH 10/14] Indent to keep under bootstrap --- docs/shell/dal_node.rst | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/shell/dal_node.rst b/docs/shell/dal_node.rst index 1d404dffd787..d6e11451924a 100644 --- a/docs/shell/dal_node.rst +++ b/docs/shell/dal_node.rst @@ -40,25 +40,25 @@ The DAL node has two modes: - **Bootstrap mode** is for nodes that help other nodes connect to peers. Bootstrap nodes are already running on most Tezos networks, so in most cases, you don't need to run a node in bootstrap node unless you are starting a new Tezos network. -Bootstrap mode is for starting a DAL network and providing entry points for other DAL nodes to become part of the network. To run a DAL node in bootstrap mode, pass the ``--bootstrap-profile`` argument, as in this example: + Bootstrap mode is for starting a DAL network and providing entry points for other DAL nodes to become part of the network. To run a DAL node in bootstrap mode, pass the ``--bootstrap-profile`` argument, as in this example: -.. code-block:: shell + .. code-block:: shell - octez-dal-node run --endpoint http://127.0.0.1:8732 --bootstrap-profile --data-dir $DATA_DIR + octez-dal-node run --endpoint http://127.0.0.1:8732 --bootstrap-profile --data-dir $DATA_DIR -The configuration file for a DAL node running in bootstrap mode shows only the base information about the node, as in this example: + The configuration file for a DAL node running in bootstrap mode shows only the base information about the node, as in this example: -.. code-block:: json + .. code-block:: json - { - "data-dir": "dal-node/", - "endpoint": "http://127.0.0.1:8732", - "profiles": { - "kind": "bootstrap" + { + "data-dir": "dal-node/", + "endpoint": "http://127.0.0.1:8732", + "profiles": { + "kind": "bootstrap" + } } - } -.. _dal_profiles: + .. _dal_profiles: Profiles ~~~~~~~~ -- GitLab From 9648c495e2ddca1a03eb883ccaf6f096aa664c11 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Fri, 6 Dec 2024 09:15:12 -0500 Subject: [PATCH 11/14] Tighten this up --- 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 d6e11451924a..83284346cbaa 100644 --- a/docs/shell/dal_node.rst +++ b/docs/shell/dal_node.rst @@ -40,7 +40,7 @@ The DAL node has two modes: - **Bootstrap mode** is for nodes that help other nodes connect to peers. Bootstrap nodes are already running on most Tezos networks, so in most cases, you don't need to run a node in bootstrap node unless you are starting a new Tezos network. - Bootstrap mode is for starting a DAL network and providing entry points for other DAL nodes to become part of the network. To run a DAL node in bootstrap mode, pass the ``--bootstrap-profile`` argument, as in this example: + To run a DAL node in bootstrap mode, pass the ``--bootstrap-profile`` argument, as in this example: .. code-block:: shell -- GitLab From b040b00675893b4e15063be185bb1af9c61b882c Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Fri, 6 Dec 2024 15:09:33 -0500 Subject: [PATCH 12/14] More specific --- 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 83284346cbaa..3ddd877b6a3a 100644 --- a/docs/shell/dal_node.rst +++ b/docs/shell/dal_node.rst @@ -63,7 +63,7 @@ The DAL node has two modes: Profiles ~~~~~~~~ -As described above, different DAL node operators are interested in different data and doing different things with that data. +As described above, different DAL node operators are interested in different data, and some want to produce data, others want to share data, and others want to attest data. For this reason, DAL controller nodes run in different profiles; these profiles control which data the nodes post, share, and attest. You can set these profiles in the node's configuration file, as CLI arguments to the node's commands, or via RPC calls. -- GitLab From 7363226bfbbcb3c2006f8dae615d9ee9d67ba1f5 Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Tue, 10 Dec 2024 13:59:32 +0000 Subject: [PATCH 13/14] Correct braces --- docs/shell/dal_node.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/shell/dal_node.rst b/docs/shell/dal_node.rst index 3ddd877b6a3a..d505303f1e67 100644 --- a/docs/shell/dal_node.rst +++ b/docs/shell/dal_node.rst @@ -117,9 +117,10 @@ The configuration file for a DAL node running with the ``attester`` profile show "profiles": { "kind": "controller", "controller_profiles": { - "operators": [], - "observers": [], - "attesters": [ "tz1QCVQinE8iVj1H2fckqx6oiM85CNJSK9Sx" ] + "operators": [], + "observers": [], + "attesters": [ "tz1QCVQinE8iVj1H2fckqx6oiM85CNJSK9Sx" ] + } } } -- GitLab From 8c19d7c5eb8b7c6e3ff109cab60836baa106124b Mon Sep 17 00:00:00 2001 From: Tim McMackin Date: Tue, 10 Dec 2024 09:00:03 -0500 Subject: [PATCH 14/14] Correct brackets --- docs/shell/dal_node.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/shell/dal_node.rst b/docs/shell/dal_node.rst index d505303f1e67..67b24fac2a05 100644 --- a/docs/shell/dal_node.rst +++ b/docs/shell/dal_node.rst @@ -101,9 +101,10 @@ For example, this configuration file shows that it is running in the ``operator` "profiles": { "kind": "controller", "controller_profiles": { - "operators": [ 0, 1 ], - "observers": [], - "attesters": [] + "operators": [ 0, 1 ], + "observers": [], + "attesters": [] + } } } -- GitLab