# FAQ

## **What problems does Circular address?**

<details>

<summary><strong>Blockchain for Healthcare</strong></summary>

Circular Protocol is designed to support healthcare applications with compliance-driven requirements (e.g., GDPR, HIPAA) by providing features that facilitate auditable data handling and access control. It is also intended to support DeFi and GameFi use cases through configurable network and application-layer features.\
\
**How:** Architectural features are designed to help implementations satisfy common compliance requirements in healthcare, depending on the deployment configuration and the application’s own controls and policies.

</details>

<details>

<summary><strong>Transaction throughput requirements resulting in hardware centralisation</strong></summary>

The need for higher transaction speed is leading some of the best technologies to higher minimum requirements for the hardware and connectivity, losing decentralization (hardware centralization).\
\
**How:** Circular’s architecture is designed to target high throughput without requiring uniformly high-performance hardware, while maintaining broad participation. Incentives are designed to support participation across a range of node capabilities; actual profitability depends on network parameters, usage, and operating conditions.

</details>

<details>

<summary><strong>Smart contract execution speed</strong></summary>

The need for higher speeds affects also the execution of smart contracts, which are still not fast and scalable enough (which leads to hardware centralization again).\
[<br>](#user-content-fn-1)[^1]**How:** Our Hyper Code architecture is intended to improve smart contract performance and scalability while preserving security and decentralization goals, subject to implementation and deployment constraints.

</details>

<details>

<summary><strong>Data Persistence liabilities for projects</strong></summary>

Many projects don't adopt blockchains because, although they would be a valid offering toward their clients, to support their technology, they don't like the fact that once a project is closed, the data persists beyond the end of the project itself, and so does the liability connected to that data.\
[<br>](#user-content-fn-1)[^1]**How:** Circular supports project-specific chains and lifecycle controls that can be configured to limit scope and duration. Data retention and shutdown procedures depend on governance decisions, regulatory obligations, and the application’s policy requirements.

</details>

<details>

<summary><strong>Coin/Token interdependency</strong></summary>

Micro-economic systems (for example metaverses and MMOs) adopt soft currencies built on existing platforms and tokens. Due to the price fluctuation of the native cryptocurrency, the game currency value is also affected and dependent on the transaction processing fees.

[<br>](#user-content-fn-1)[^1]**How:** Circular's private blockchains for micro-economic systems remove dependencies on external factors, allowing for better control and improved stability in transactions. For micro-economic systems, private chains can be configured so application tokens and fee models are decoupled from external asset volatility, depending on how the chain is parameterized.

</details>

<details>

<summary>Is the Circular blockchain already built?</summary>

Core components have been implemented and validated in test and/or limited deployment environments, with additional components under active development. The roadmap reflects the planned sequencing of remaining releases and integrations.

</details>

<details>

<summary>What are the main value propositions of Circular Protocol</summary>

Circular blockchain’s value lies in its architecture, designed to deliver high throughput, scalability, and security. At its core is a consensus mechanism, supported by technologies like Hyper Code and the Performance Balancer.

These features are intended to provide a robust and sustainable environment for both developers and users. Our node adoption program is designed to promote a decentralized and transparent network as the ecosystem grows.

Circular blockchain aims to be a dependable, high-performance platform for a wide range of decentralized applications and services.

</details>

## The CIRX Token

<details>

<summary><strong>Why a Coin?</strong></summary>

Circular’s infrastructure is designed to be powered by a native coin, “Circular” (Ticker: CIRX), intended to support network fees, service usage, and validator rewards.

</details>

<details>

<summary>Will I be able to trade CIRX</summary>

Depending upon the success of the fund raise we are aiming to list the coin on some of the most popular trading platforms by the end of Q1 2024. This will be subject to terms and conditions of the different platforms and the time required to comply with the regulations.

</details>

<details>

<summary><strong>What do I need to buy CIRX?</strong></summary>

To stay updated, simply follow us on our social media platforms. When the coin is issued, we will announce it there, along with detailed instructions on how to purchase it.

</details>

<details>

<summary><strong>Where can I stay updated on the project?</strong></summary>

For official updates on issuance, availability, and any potential listings, please follow our verified communication channels. If and when CIRX is issued, we will publish detailed information and instructions through those channels.

[**Follow Circular on Telegram**](https://t.me/CircularProtocol)

[**Follow Circular on Linkedin**](https://www.linkedin.com/company/circular-labs/)

[**Follow Circular on X**](https://twitter.com/circularweb3)

For more complex inquiries email us at: **<info@circularlabs.io>**

</details>

[^1]:


---

# 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/whitepaper/faq.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.
