# Welcome to Chipit Protocol

## PITCHDECK

{% file src="<https://3262993957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPQudXlRuGwN2kjfJH9IH%2Fuploads%2FFRdY3I9SKCrrnZXOFW1z%2FChipit%20Whitepaper.pdf?alt=media&token=afafa74f-4dd1-4410-ba6c-2ae2e9e6c2be>" %}

{% hint style="info" %}
Chipit is a hyper-deflationary token being the 1st of it's kind on Ethereum Classic and Binance Smart Chain.

Focused on **Reward Distribution** and **NFT Technology.**

We are in a time where the top blockchains are full of an increasingly large number of false promises, ridiculous token economic models, exorbitantly high marketing wallet fees. After months of research and development. Chipit Protocol will redefine the meme coin environment and be the sentinel of the ETC/BSC chain.
{% endhint %}

* **Website**: <https://www.chipit.market>
* **Twitter**: <https://twitter.com/chipit_coin>
* **Reddit**: <https://www.reddit.com/r/chipit/>
* **Github**: <https://github.com/ChipitProtocal>
* **Telegram**: <https://t.me/chipitcoin>

{% hint style="info" %}
**Binance Smart Chain (BSC)** is a blockchain network built for running smart contract-based applications. BSC runs in parallel with Binance's native Binance Chain (BC), which allows users to get the best of both worlds: the high transaction capacity of BC and the smart contract functionality of BSC.

{% endhint %}

{% hint style="info" %}
**Ethereum Classic (ETC)** is a decentralized, open-source blockchain with smart contract functionality. ETC is the native cryptocurrency of the platform. Amongst cryptocurrencies, Ethereum Classic is the original Ethereum that was conceived in 2013 by programmer Vitalik Buterin.
{% endhint %}

### Guides: Jump right in

Follow our handy guides to get started on the basics as quickly as possible:

{% content-ref url="broken-reference" %}
[Broken link](https://chipitcoin.gitbook.io/chipit-whitepaper/broken-reference)
{% endcontent-ref %}

{% content-ref url="chipit-ecosystem/chipit-token" %}
[chipit-token](https://chipitcoin.gitbook.io/chipit-whitepaper/chipit-ecosystem/chipit-token)
{% endcontent-ref %}

{% content-ref url="chipit-ecosystem/chipagram" %}
[chipagram](https://chipitcoin.gitbook.io/chipit-whitepaper/chipit-ecosystem/chipagram)
{% endcontent-ref %}

{% hint style="info" %}
**Good to know:** your product docs aren't just a reference of all your features! use them to encourage folks to perform certain actions and discover the value in your product.
{% endhint %}

### Fundamentals: Dive a little deeper

Learn the fundamentals of MyProduct to get a deeper understanding of our main features:

{% content-ref url="fundamentals/initial-dex-offering" %}
[initial-dex-offering](https://chipitcoin.gitbook.io/chipit-whitepaper/fundamentals/initial-dex-offering)
{% endcontent-ref %}

{% content-ref url="fundamentals/kyc-and-audit" %}
[kyc-and-audit](https://chipitcoin.gitbook.io/chipit-whitepaper/fundamentals/kyc-and-audit)
{% endcontent-ref %}

{% content-ref url="fundamentals/technology" %}
[technology](https://chipitcoin.gitbook.io/chipit-whitepaper/fundamentals/technology)
{% endcontent-ref %}

{% content-ref url="fundamentals/monetization-model" %}
[monetization-model](https://chipitcoin.gitbook.io/chipit-whitepaper/fundamentals/monetization-model)
{% endcontent-ref %}

{% hint style="info" %}
**Good to know:** Splitting your product into fundamental concepts, objects, or areas can be a great way to let readers deep dive into the concepts that matter most to them. Combine guides with this approach to 'fundamentals' and you're well on your way to great documentation!
{% endhint %}


---

# 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://chipitcoin.gitbook.io/chipit-whitepaper/welcome-to-chipit-protocol.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.