# Multiple deploys with same Contract Id
**URL:** https://forum.fuel.network/t/multiple-deploys-with-same-contract-id/1515
**Category:** Fuel Network
**Tags:** testnet, faqs
**Created:** [January 18, 2023, 12:35pm UTC](https://forum.fuel.network/t/multiple-deploys-with-same-contract-id/1515 "2023-01-18T12:35:15Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@zelki](https://forum.fuel.network/u/zelki)
#### Post date: [January 18, 2023, 12:35pm UTC](https://forum.fuel.network/t/multiple-deploys-with-same-contract-id/1515/1 "2023-01-18T12:35:15Z")
Hello, I’m pretty new to FuelVM and Sway and I was going through the docs and the “Getting Started” flow yesterday deploying to `beta-2`.
There’s a couple of things I don’t fully understand and would appreciate any help you can give me clearing them up:
The `Counter` contract I deployed had the same exact Contract Id that was present in the “Getting Started” page. I’m not sure if I’m correctly understanding the Contract ID computing formula but it seems that given the same exact contract bytecode, without the addition of salt to the `sha256`, the Contract ID will always be the same. Is this correct?
If that is the case then how are multiple deploys of the same bytecode (without salt) are handled?
I deployed the same contract twice and after the second deployment it seemed like the storage of the previous deployment was reset.
You can find the transactions in question [https://fuellabs.github.io/block-explorer-v2/address/fuel1zg72j04gfc03mvxawg0egf3v0lnu3gg3y0qw8993z0wluf5xttsq87jxeq](https://here)
The zeroth output for both of them are the same Contract ID.
I’m sorry if this is a dumb question but I don’t really understand what’s happening here.
---
### Author:  [@Simon](https://forum.fuel.network/u/Simon)
#### Post date: [January 20, 2023, 9:13pm UTC](https://forum.fuel.network/t/multiple-deploys-with-same-contract-id/1515/2 "2023-01-20T21:13:06Z")
Not a dumb question - the client should indeed be forbidding duplicate contract Ids (i.e. requiring salt to distinguish contracts with identical bytecode and initial storage configuration).
We fixed this [here](https://github.com/FuelLabs/fuel-vm/pull/315), and should be pushing this to the testnet very shortly.
---
### Author:  [@zelki](https://forum.fuel.network/u/zelki)
#### Post date: [January 23, 2023, 9:27am UTC](https://forum.fuel.network/t/multiple-deploys-with-same-contract-id/1515/3 "2023-01-23T09:27:23Z")
Thanks for taking the time to reply and clearing things up, I was feeling pretty lost as to what I was missing 🙏
---
### Author:  [@system](https://forum.fuel.network/u/system)
#### Post date: [February 13, 2023, 5:27am UTC](https://forum.fuel.network/t/multiple-deploys-with-same-contract-id/1515/4 "2023-02-13T05:27:34Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.