> For the complete documentation index, see [llms.txt](https://docs.lazai.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lazai.network/quickstart/deploy-your-first-smart-contract.md).

# Deploy Your First Smart Contract

Deploy and test your first smart contract on the LazAI Testnet.

This guide walks you through connecting to the network, setting up your environment, and deploying a sample contract using Hardhat, Foundry, or Remix.

### Overview

LazAI provides a developer-friendly Web3 environment for building AI-powered decentralized applications.

Each LazAI chain supports EVM-compatible contracts, so if you’ve deployed contracts on Ethereum, you’ll feel right at home.

LazAI provides an EVM-compatible environment for deploying and testing smart contracts.

If you have experience developing on Ethereum, you can use the same tools and workflows on LazAI.

\
This page covers:

* [LazAI network configuration](#lazai-network-information)
* [Environment setup](#lazai-network-information)
* [Contract verification](#verifying-your-deployment)
* [Deployment using Hardhat, Foundry, or Remix](#next-steps)

***

### LazAI Network Information

Use these parameters to connect your wallet or development environment to the LazAI Testnet.

| **Chain ID**        | 133718                                                |
| ------------------- | ----------------------------------------------------- |
| **Currency Symbol** | LAZAI                                                 |
| **RPC**             | <https://testnet.lazai.network>                       |
| **Block Explorer**  | <https://testnet-explorer.lazai.network>              |
| **Faucet**          | [LazAI Testnet Faucet](https://faucet.lazai.network/) |

***

### Verifying Your Deployment

After deployment:

1. Copy the deployed contract address.
2. Open the [LazAI Testnet Explorer](https://testnet-explorer.lazai.network).
3. Paste the contract address to confirm deployment.
4. If needed, verify your source code through your chosen framework’s verification plugin or CLI command.

***

### Troubleshooting

RPC connection error

* Confirm your RPC URL and chain ID (133718).
* Retry with a clean browser session or different RPC endpoint if available.

Insufficient funds

* Request test tokens from the [LazAI Faucet](https://faucet.lazai.network/).

Contract verification issues

* Match your Solidity compiler version with the one specified in your configuration file.

***

### Next Steps

Continue with framework-specific deployment:

* [Deploy Using Remix](https://docs.lazai.network/quickstart/deploy-your-first-smart-contract/deploy-with-remix.md)&#x20;
* [Deploy Using Hardhat ](https://docs.lazai.network/quickstart/deploy-your-first-smart-contract/deploy-with-hardhat.md)
* [Deploy Using Foundry ](https://docs.lazai.network/quickstart/deploy-your-first-smart-contract/deploy-with-foundry.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lazai.network/quickstart/deploy-your-first-smart-contract.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
