# Project Files

Before diving into coding your smart contract, the first crucial step is configuring the Settings.json file. This JSON-formatted file serves as a foundation where you input key details about your smart contract. Proper setup here will streamline your development and help avoid issues later. The structure of the file is straightforward, acting as a blueprint for your contract’s essential information, making the coding process smoother and faster. Here’s how the file is organized:

```javascript
{
    "Version": "1.0.1",
    "Project_Name": "MyToken",
    "Symbol": "MTk",
    "Language": "JavaScript",
    "Blockchain": "0x8a20baa40c45dc5055aeb26197c203e576ef389d9acb171bd62da11dc5ad72b2",
    "Owner_Address": "Enter here the owner wallet address",
    "Developer_Name": "Enter here the developer Name",
    "Developer_Address": "Enter here the developer Address",
    "Dev_Private_Key": "Enter here the developer Private Key"
}
```

The following keys in Settings.json hold essential information for your smart contract:

| Key Description    | Value Description                                          |
| ------------------ | ---------------------------------------------------------- |
| Version            | Identifies the contract version for deployment.            |
| Project\_Name      | Sets the name of your smart contract project.              |
| Symbol             | Defines the ticker symbol for your digital asset.          |
| Language           | Specifies the programming language (JavaScript or Python). |
| Blockchain         | Defaults to “Sandbox” for testing purposes.                |
| Owner\_Address     | Contains the wallet address of the contract owner.         |
| Developer\_Name    | Optional field for the developer’s name.                   |
| Developer\_Address | The developer’s wallet address used for testing.           |
| Dev\_Private\_Key  | Private key for local development, kept secure.            |

These are the key fields required for setting up your smart contract, though additional fields can be added as needed.


---

# Agent Instructions: 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:

```
GET https://circular-protocol.gitbook.io/hyper-code-ide-guide/lesson-1-get-started/publish-your-docs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.