<p>Based off the &quot;same keys&quot; part of the question, I am going to assume this is for a block producing node.</p>
<p><strong>Block Producing Node:</strong></p>
<p>For the BP, all you need to do to move it is copy the <strong>kes.skey, vrf.skey and node.cert</strong>. You will also want to copy your configuration files and make sure your UFW configuration is the same. The last step is, if you changed the IP address, to update your relay topology to connect to the new IP address, as well as update the relay UFW if needed.</p>
<p><strong>Minting Tokens:</strong></p>
<p>Although I have not tested this, I believe you need to copy over your <strong>policy.vkey</strong>, <strong>policy.skey</strong>, <strong>policy.script</strong>, and your <strong>policy.ID</strong>. You also may need your payment address and keys. If I am missing anything please correct me and I'll update this.</p>
<p><a href="https://developers.cardano.org/docs/native-tokens/" rel="nofollow noreferrer">Minting Token's Source</a></p>
<p>Hope this helps!</p>

CC BY-SA 4.0
2021-11-08T00:56:36.697Z
Thanks for taking the time to respond! It's not a block producing node, but I want to be able to mint tokens and make associated metadata (or alter previous metadata) later which requires the "same" node. (that's what I've been lead to believe anyway)
Stan Marsh
CC BY-SA 4.0
2021-11-07T15:25:58.850Z
2021-11-08T02:51:31.513Z
2021-11-08T02:51:31.513Z
Jacob - SNOWY Pool
<p>just to be sure,
you need to define what kind of files you store this moment to your old node.
it depends on your folder structure and for what reason the node is running.</p>
<p>i would recommend you to install the same way the new node and use the same folder structure.
then you store the files on the same folder as it is now.
cold.counter*
cold.skey*
cold.vkey*
hot.skey*
hot.vkey*
pool.id
pool.id-bech32
vrf.skey*
vrf.vkey*</p>
<p>kes.start*
op.cert*
pool.cert*
pool.config*
poolmeta.json*</p>
<p>if you run the node as a BP only, and you store the rest of your files on offline system, then our friend before is right,
you need only this 3 files on the node :
kes.skey,
vrf.skey and
node.cert.</p>
<p><a href="https://i.sstatic.net/bqYyl.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/bqYyl.png" alt="enter image description here" /></a></p>

CC BY-SA 4.0
2021-11-08T10:36:23.453Z
2021-11-08T10:36:23.453Z
TTS17
<p>What do I need to do to move a node on one machine to another so the node appears to be the same node. I have a node on one machine but need to discontinue that machine. When I build the new machine out I need it to have the same keys I'm guessing. I'm not exactly sure what files would need to be copied over. Thanks for the help.</p>

CC BY-SA 4.0
2021-11-07T15:17:27.920Z
Is this for a Stake Pool block producing node?
Jacob - SNOWY Pool
<cardano-node>
Move a node to another computer
# Move a node to another computer

(Asked by: username_0 on 2021-11-07)

What do I need to do to move a node on one machine to another so the node appears to be the same node. I have a node on one machine but need to discontinue that machine. When I build the new machine out I need it to have the same keys I'm guessing. I'm not exactly sure what files would need to be copied over. Thanks for the help.

**Tags:** cardano-node
> **Comments:**
> **username_1**: Is this for a Stake Pool block producing node?  

---

## 2 answers

### Answer by username_1 on 2021-11-07. Score: 2

Based off the "same keys" part of the question, I am going to assume this is for a block producing node.

**Block Producing Node:**

For the BP, all you need to do to move it is copy the **kes.skey, vrf.skey and node.cert**. You will also want to copy your configuration files and make sure your UFW configuration is the same. The last step is, if you changed the IP address, to update your relay topology to connect to the new IP address, as well as update the relay UFW if needed.

**Minting Tokens:**

Although I have not tested this, I believe you need to copy over your **policy.vkey**, **policy.skey**, **policy.script**, and your **policy.ID**. You also may need your payment address and keys. If I am missing anything please correct me and I'll update this.

[Minting Token's Source](https://developers.cardano.org/docs/native-tokens/)

Hope this helps!

> **Comments:**
> **username_0**: Thanks for taking the time to respond! It's not a block producing node, but I want to be able to mint tokens and make associated metadata (or alter previous metadata) later which requires the "same" node. (that's what I've been lead to believe anyway)  

---

### Answer by username_2 on 2021-11-08. Score: 0

just to be sure,
you need to define what kind of files you store this moment to your old node.
it depends on your folder structure and for what reason the node is running.

i would recommend you to install the same way the new node and use the same folder structure.
then you store the files on the same folder as it is now.
cold.counter\*
cold.skey\*
cold.vkey\*
hot.skey\*
hot.vkey\*
pool.id
pool.id-bech32
vrf.skey\*
vrf.vkey\*

kes.start\*
op.cert\*
pool.cert\*
pool.config\*
poolmeta.json\*

if you run the node as a BP only, and you store the rest of your files on offline system, then our friend before is right,
you need only this 3 files on the node :
kes.skey,
vrf.skey and
node.cert.

[![enter image description here](https://i.sstatic.net/bqYyl.png)](https://i.sstatic.net/bqYyl.png)


---

