> For the complete documentation index, see [llms.txt](https://docs.frequencychain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frequencychain.org/5.-smart-contract-development-remix-+-hardhat.md).

# 5. Smart Contract Development             (Remix + Hardhat)

Smart contracts are the core building blocks of applications on the FreCx blockchain. A smart contract is a self-executing program that runs on the blockchain and automatically enforces rules and logic defined by the developer.

FreCx is fully compatible with the Ethereum Virtual Machine (EVM), which means that developers can write smart contracts using Solidity, the same programming language used in Ethereum. This compatibility ensures that existing tools, libraries, and development workflows can be used seamlessly.

This section provides a detailed guide to developing, deploying, and interacting with smart contracts using two primary tools:

* Remix IDE — a browser-based development environment
* Hardhat — a local development framework for advanced workflows


---

# 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.frequencychain.org/5.-smart-contract-development-remix-+-hardhat.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.