Running a sequencer

.snippets/code/node-operators/sequencers/onboarding/run-a-sequencer/sequencers-docker/docker-command.md

@@ -1,23 +1,43 @@
---chain=dancebox \
---name=INSERT_YOUR_TANSSI_NODE_NAME \
---sync=warp \
---base-path=/data/para \
+--name=INSERT_YOUR_SEQUENCER_NODE_NAME \
+--base-path=/data/container \
+--node-key-file=/data/node-key \
+--keystore-path=/data/keys/session \
+--telemetry-url='wss://telemetry.polkadot.io/submit/ 0' \
+--database=paritydb \
+--rpc-port=9944 \
+--rpc-cors=all \
+--rpc-max-connections 100 \
+--unsafe-rpc-external \
+--rpc-methods=unsafe \
+--prometheus-port=9615 \
+--prometheus-external \
+--listen-addr=/ip4/0.0.0.0/tcp/30333 \
 --state-pruning=2000 \
 --blocks-pruning=2000 \
+--db-cache=1024 \
+--trie-cache-size=1073741824 \
 --collator \
---telemetry-url='wss://telemetry.polkadot.io/submit/ 0' \
---database paritydb \
---node-key-file /data/node-key \
+--in-peers=100 \
+--detailed-log-output \
 -- \
---name=INSERT_YOUR_BLOCK_PRODUCER_NODE_NAME \
---base-path=/data/container \
---telemetry-url='wss://telemetry.polkadot.io/submit/ 0' \
--- \
---chain=westend_moonbase_relay_testnet \
---name=INSERT_YOUR_RELAY_NODE_NAME \
+--chain=/chain-network/relay-raw-no-bootnodes-specs.json \
+--name=INSERT_YOUR_TANSSI_NODE_NAME \
 --sync=fast \
---base-path=/data/relay \
+--base-path=/data/relay \      
+--node-key-file=/data/node-key \
+--database=paritydb \
+--rpc-port=9945 \
+--rpc-cors=all \
+--rpc-methods=safe \
+--unsafe-rpc-external \
+--prometheus-port=9616 \
+--prometheus-external \
+--listen-addr=/ip4/0.0.0.0/tcp/30334 \
+--pool-limit=0 \
+--db-cache=128 \
+--out-peers=15 \
 --state-pruning=2000 \
 --blocks-pruning=2000 \
 --telemetry-url='wss://telemetry.polkadot.io/submit/ 0' \
---database paritydb
+--bootnodes=/dns4/fraa-stagelight-rpc-0.a.stagenet.tanssi.network/tcp/30334/p2p/12D3KooWCUwf99GjNKtDJ7SnuGPaecdiugiWJ3pr9JdoH27BW2tZ \
+--bootnodes=/dns4/fraa-stagelight-rpc-1.a.stagenet.tanssi.network/tcp/30334/p2p/12D3KooWHRQfPBf82SUU39CFh5jcUT1TL2ZvvTWvnbtghxqqNQwa"

.snippets/code/node-operators/sequencers/onboarding/run-a-sequencer/sequencers-docker/terminal/pulling-docker-image.md

@@ -1,16 +1,16 @@
 <div id="termynal" data-termynal>
-  <span data-ty="input"><span class="file-path"></span>docker pull moondancelabs/tanssi</span>
+  <span data-ty="input"><span class="file-path"></span>docker pull moondancelabs/stagelight-collators:3</span>
   <span data-ty>
     <br> 
     <br> Using default tag: latest
-    <br> latest: Pulling from moondancelabs/tanssi
+    <br> latest: Pulling from moondancelabs/stagelight-collators:3
     <br> e1caac4eb9d2: Pull complete 
     <br> 1d4409959e6d: Pull complete 
     <br> b8beed19c122: Pull complete 
     <br> c0fab1f18601: Pull complete 
     <br> d9dcf3cddfc5: Pull complete 
     <br> Digest: sha256:0f717d6cf247bbb1b082f5f9e5761b23c44a0be8b704492a57fdbf8c63c0a91c
-    <br> Status: Downloaded newer image for moondancelabs/tanssi
-    <br> docker.io/moondancelabs/tanssi:latest
+    <br> Status: Downloaded newer image for moondancelabs/stagelight-collators:3
+    <br> docker.io/moondancelabs/stagelight-collators:3
   </span>
 </div>

.snippets/text/node-operators/sequencers/onboarding/run-a-sequencer/generate-node-key-intro.md

@@ -1 +1 @@
-Starting from [runtime 700 release](https://github.com/moondance-labs/tanssi/releases/tag/runtime-700){target=\_blank}, Tanssi block producer nodes don't generate the session keys automatically on start-up. To generate and store on disk the session keys that will be referenced on the start-up command, run the following command:
+Starting from [runtime 700 release](https://github.com/moondance-labs/tanssi/releases/tag/runtime-700){target=\_blank}, Tanssi sequencer nodes don't generate the session keys automatically on start-up. To generate and store on disk the session keys that will be referenced on the start-up command, run the following command:

.snippets/text/node-operators/sequencers/onboarding/run-a-sequencer/intro.md

@@ -1,5 +1,5 @@
 One of Tanssi's core propositions is that it provides decentralized and trustless block production for its networks. Tanssi's runtime handles sequencer assignments to all the active networks in the Tanssi ecosystem.
 
-Each time, the assignment algorithm distributes the available block producers per session, assigning them to a random chain. Consequently, they would be producing blocks for the same network only for a relatively short period, increasing the overall security of the ecosystem.
+Each time, the assignment algorithm distributes the available set of sequencers per session, assigning them to a random chain. Consequently, they would be producing blocks for the same network only for a relatively short period, increasing the overall security of the ecosystem.
 
-To this end, Tanssi's binary file (the software used to run nodes) already has an embedded mechanism to switch block production automatically to the assigned chain without requiring the node operator to make any changes. The binary includes the logic to sync the new chain and produce blocks when the session changes. Consequently, sequencers need to run the Tanssi binary file, and not that of the networks (like full nodes).
+To this end, Tanssi's binary file (the software used to run nodes) already has an embedded mechanism to switch block production automatically to the assigned chain without requiring the node operator to make any changes. The binary includes the logic to sync the new chain and produce blocks when the session changes. Consequently, sequencers need to run the Tanssi binary file, and not that of the networks (like full nodes do).

node-operators/sequencers/index.md

@@ -7,7 +7,7 @@ template: index-page.html
 
 # Tanssi Sequencers
 
-Becoming a sequencer is a critical role in maintaining the security and efficiency of the Tanssi ecosystem. Sequencers are responsible for producing blocks, validating transactions, and ensuring the smooth operation of the network. This section provides everything you need to get started, from initial setup to operational best practices and account management.
+Sequencers play a critical role in maintaining the liveness and performance of the Tanssi ecosystem. Sequencers are responsible for producing blocks, executing transactions, and ensuring the smooth operation of the network. This section provides everything you need to get started, from initial setup to operational best practices and account management.
 
 ## Explore This Section