> For the complete documentation index, see [llms.txt](https://docs.orbs.network/v2-contract-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.orbs.network/v2-contract-sdk/gamma-in-depth/deploying-smart-contracts.md).

# Deploying smart contracts

## Using Gamma CLI

To deploy a smart contract run the command `gamma-cli deploy` and provide the contract name. You will also need to provide the source code for the contract.

For example, to deploy a contract named **MyToken**

```
gamma-cli deploy contract.go -name MyToken -signer user1
```

## Command parameters

```
gamma-cli deploy <CODE_FILE> -name [CONTRACT_NAME] -signer [ID_FROM_KEYS_JSON]
```

* `<CODE_FILE>` Source file for the smart contract being deployed, normally .go or .js file
* `-name` Name of the contract on the blockchain (used by future transaction senders)
* `-signer` Account ID of the signer of the deploy transaction (from `orbs-test-keys.json`)

{% hint style="info" %}
If you don't provide an explicit contract name with `-name`, your code file name will be used.
{% endhint %}

## Caveats

Contracts are immutable. If you want to update the code for a contract, deploy it again under a different name.

Remember that Gamma server is an in-memory blockchain. When you stop the server with `gamma-cli stop-local` all contracts will disappear.

Contracts are currently limited to a single source file. If you have multiple files, combine them into one.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.orbs.network/v2-contract-sdk/gamma-in-depth/deploying-smart-contracts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.