> 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/6.-interacting-with-smart-contracts-using-ethers.js-and-web3.js.md).

# 6. Interacting with Smart Contracts Using ethers.js and web3.js

Once a smart contract is deployed on the FreCx blockchain, interacting with it becomes the next critical step. While tools like Remix provide a visual interface for interacting with contracts, real-world applications require programmatic interaction through code. This is where libraries such as ethers.js and web3.js are used.

These libraries act as a bridge between applications (such as web interfaces or backend services) and the blockchain network. They allow developers to connect to the FreCx network through RPC endpoints, read data from deployed contracts, send transactions that modify contract state and sign transactions using a wallet.

Because FreCx is fully EVM-compatible, both ethers.js and web3.js can be used without any modification.


---

# 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/6.-interacting-with-smart-contracts-using-ethers.js-and-web3.js.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.