<p>BP settings -&gt;</p>
<ol>
<li>folder files : topology.json will be on BP only your realys</li>
<li>from BP we dont run topologyUpdater</li>
<li>to run a BP, you need minimum 3-4 files (hot.skey, op.cert, vrf.skey, vrf.vkey) - the rest of the files, need to be stored and secured in a private offline node for your security.</li>
</ol>
<p>Relay Settings -&gt;</p>
<ol>
<li>you run script &quot;topologyUpdater&quot; so that you have every hour new peers.</li>
<li>in the &quot;topologyUpdater&quot; you have to define specific Nodes, you want to be connected additionally to the list of the Nodes from the script</li>
</ol>

CC BY-SA 4.0
2022-01-31T16:17:12.190Z
2022-01-31T16:17:12.190Z
TTS17
<p>all answers a great for general infos...</p>
<p>i think based on your questions, you want to find if a node is BP or Relay,
please execute the command below</p>
<p>sudo systemctl status cnode</p>
<p>if you find the 3 files below on the executed command, means it is running a BP</p>
<ol>
<li>hot.skey</li>
<li>vrf.skey</li>
<li>op.cert</li>
</ol>
<p>if you need more info / support, let us know
TTS17</p>

CC BY-SA 4.0
2022-06-30T20:40:01.217Z
2022-06-30T20:40:01.217Z
TTS17
<p>It depends on how you configure your nodes, there are few things that changes between a block producer and a relay node. In the block producer's topology.json you should only have your 1/2 &quot;private&quot; relays. Another thing that you can check is the start up script of the node, the block producer need to include different keys: kes, vrf, ecc inside of it.
The last thing that comes to my mind is that if everything is configured in the corrected way, you should be able to see different things by opening the liveview of the node, first of all, it tells you if you are running a core or a relay node. If you are watching the core node, you should be able to see processed tx and mempool tx/bytes, plus the kes expiration date, if not, you should be able to see peers/other's pools relay nodes.</p>

CC BY-SA 4.0
2021-09-12T07:29:43.643Z
2021-09-12T07:29:43.643Z
Nic_T2H
<p>More specifically, how does one know or how does one check if a cardano-node process is acting/functioning as a relay versus a producer?</p>

<cardano-node>
What is the technical configuration difference between a cardano-node relay and producer?
# What is the technical configuration difference between a cardano-node relay and producer?

(Asked by: username_0 on 2021-09-12)

More specifically, how does one know or how does one check if a cardano-node process is acting/functioning as a relay versus a producer?

**Tags:** cardano-node

---

## 3 answers

### Answer by username_1 on 2022-01-31. Score: 1

BP settings ->

1. folder files : topology.json will be on BP only your realys
2. from BP we dont run topologyUpdater
3. to run a BP, you need minimum 3-4 files (hot.skey, op.cert, vrf.skey, vrf.vkey) - the rest of the files, need to be stored and secured in a private offline node for your security.

Relay Settings ->

1. you run script "topologyUpdater" so that you have every hour new peers.
2. in the "topologyUpdater" you have to define specific Nodes, you want to be connected additionally to the list of the Nodes from the script


---

### Answer by username_1 on 2022-06-30. Score: 0

all answers a great for general infos...

i think based on your questions, you want to find if a node is BP or Relay,
please execute the command below

sudo systemctl status cnode

if you find the 3 files below on the executed command, means it is running a BP

1. hot.skey
2. vrf.skey
3. op.cert

if you need more info / support, let us know
TTS17


---

### Answer by username_2 on 2021-09-12. Score: 0

It depends on how you configure your nodes, there are few things that changes between a block producer and a relay node. In the block producer's topology.json you should only have your 1/2 "private" relays. Another thing that you can check is the start up script of the node, the block producer need to include different keys: kes, vrf, ecc inside of it.
The last thing that comes to my mind is that if everything is configured in the corrected way, you should be able to see different things by opening the liveview of the node, first of all, it tells you if you are running a core or a relay node. If you are watching the core node, you should be able to see processed tx and mempool tx/bytes, plus the kes expiration date, if not, you should be able to see peers/other's pools relay nodes.


---

