You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sphinx/source/start_network.rst
+31-7Lines changed: 31 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,6 +73,30 @@ Other members are then allowed to vote for the proposal, using the proposal ID r
73
73
74
74
The user is successfully added once a :term:`quorum` of members have accepted the proposal (``"result":true"``).
75
75
76
+
Register the Lua application
77
+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
78
+
79
+
.. note:: This section only applies when deploying Lua applications (i.e. using the ``libluageneric.so.signed`` enclave library). For C++ applications, this step should be skipped.
80
+
81
+
Before opening the CCF network to users, members should vote to register the Lua application defining the user-specific business logic (see for example :ref:`Logging (Lua)`):
Other members are then allowed to vote for the proposal, using the proposal ID returned to the proposer member (here ``1``, as per ``"result":{"completed":false,"id":1}``).
Other members are then allowed to vote for the proposal, using the proposal ID returned to the proposer member (here ``1``, as per ``"result":{"completed":false,"id":1}``).
110
+
Other members are then allowed to vote for the proposal, using the proposal ID returned to the proposer member (here ``2``, as per ``"result":{"completed":false,"id":2}``).
Once a quorum of members have approved the network opening (``"result":true``), the network is opened to users (see :ref:`Example App` for a simple business logic and :term:`JSON-RPC` transactions). It is only then that users are able to execute transactions on the business logic defined by the enclave file (``--enclave-file`` option to ``cchost``).
97
121
@@ -128,7 +152,7 @@ Summary diagram
128
152
129
153
Once a node is part of the network (started with either the ``start`` or ``join`` option), members are authorised to issue governance transactions and eventually open the network. Only then are users authorised to issue JSON-RPC transactions to CCF.
130
154
131
-
.. note:: After the network is open to users, members can still issue governance transactions to CCF (for example, adding new users or additional members to the consortium). See :ref:`Governance` for more information about member governance.
155
+
.. note:: After the network is open to users, members can still issue governance transactions to CCF (for example, adding new users or additional members to the consortium or updating the Lua app, when applicable). See :ref:`Governance` for more information about member governance.
132
156
133
157
The following diagram summarises the steps required to bootstrap a CCF network:
0 commit comments