# Cronos POS Chain Introduction

The development of blockchain technology and cryptocurrencies represents a cryptography and security breakthrough as significant as that created by the internet in the 1990s. This technology, however, is still at a very nascent stage; in order to generate mass adoption, it will therefore be necessary to find compelling real-life use cases that can appeal to an audience larger than the small group of industry professionals and experts.

### Cronos POS Chain

Accordingly, we propose Cronos POS Chain, the next-generation public blockchain that enables transactions worldwide between people and businesses. It is also the technology that powers Crypto.com Pay, mobile payment solution, and will be used to power our trading & financial services offerings in the near future.

We believe enabling cryptocurrency spending in the real world will be an adoption catalyst. Current traditional payment institutions and existing blockchains have failed to provide a secure, scalable and decentralized solution to support cryptocurrency payment. The key limitations of existing blockchain-powered payment networks are that they are:

* Too complex to setup and use;
* Not friendly to crypto first-timers; and
* Rarely supported beyond their own blockchain;

## Design Goals

On the technical side, Cronos POS Chain has the following design goals:

1. **"Security"**: robust and well-understood primitives and implementation are favoured
2. **"Scalability"**: parts that hinder overall latency, throughput, lightweight client support, etc. should be mitigated
3. **"Multi-party"**: the system should permit multi-party operation; anything that puts trust in a single party should be opt-in
4. **"Long-term operation"**: there needs to be a leeway for backward- and forwards-compatibility etc.
5. **"Developer ecosystem"**: external developers can easily work with Chain, regardless of their used programming language; better support for DeFi use cases, e.g., support cross-chain asset transfers and communications.


---

# 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://docs.cronos-pos.org/getting-started/introduction.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.