> For the complete documentation index, see [llms.txt](https://doc.fracton.cool/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.fracton.cool/fractonxs-solutions/tech-design-philosophy.md).

# Tech Design Philosophy

Through the development process of creating Fracton Protocol, the dev team is centered around the following design philosophies:

* **Secure**
* **Stateless**
* **Smart** 

## Secure

Besides rounds of internal/external audits on the Fracton protocol’s smart contracts, each line of code Fracton protocol deployed on the blockchain is non-upgradeable. 

It ensures that the smart contract is fixed and cannot be altered, even by the contract's creator itself. This can give users of the contract greater confidence as non-upgradeable smart contracts are simpler and more secure, with no need to include code to handle updates or modifications.

## Stateless System Design 

Fracton Protocol fully utilizes the contract state variables within a framework to implement business logic and process control while optimizing gas consumption by avoiding the addition of new state variables.

There are a few reasons why it is important:

* Users pay fewer gas fees
* Help Ethereum to better scale and decentralize
* Create better composability for the Dapps that build on top of the Fracton protocol

## Smart Token Development

A “think” protocol design is followed as most of the business functions are embedded under the token contract in order to achieve high efficiency between contract calls.<br>


---

# 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://doc.fracton.cool/fractonxs-solutions/tech-design-philosophy.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.