# Building on Karrier One

The Karrier One Network has been designed as a platform for innovation, open to integration with other decentralized wireless projects. We invite developers, and innovators to build their own projects on the Karrier One network, utilizing our remarkable telecommunications infrastructure.

## Advantages for Developers and Projects

* **Access to a Global Network:** Karrier One aims to create a global telecommunications layer, meaning projects built on our network can potentially reach users worldwide. This gives developers access to a large and diverse user base.
* **Advanced Blockchain Integration:** Coming Soon...&#x20;
* **Advanced Teleco Infrastructure:** With over 20 years of Canadian telecommunications experience, Karrier One has access to robust telecommunications infrastructure. This includes licensed spectrum & LTE Band 53.
* **Enhanced Digital ID:** The [Karrier Number System (KNS)](/network-faq/kns-digital-identity.md), which bridges the gap between traditional Web2 and evolving Web3 domains. The added security of the KNS system can significantly enhance the user experience of the projects built on our network.

## Getting Started

To get started with building on the Karrier One Network, developers should familiarize themselves with our platform and our development tools. We encourage you to join our <mark style="color:blue;">**Discord**</mark> or connect with us through our communication channels to learn more info.


---

# 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://faq.karrier.one/token-faq/blockchain/building-on-karrier-one.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.