> For the complete documentation index, see [llms.txt](https://docs.qoinpro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qoinpro.com/timeline/2014-2017-operational.md). # 2014 - 2017: Operational *** ## 2014 - 2017 - Early Years (Growing Pains) QoinPro was conceptualized late 2013 and started as a side-project early 2014 to be a crypto currency micro-faucet. Daily freebies (minuscule fractional amounts of crypto) were given to active users to introduce them to the industry. A few other crypto currencies were added as well as limited on-chain functionality, mostly to allow for consolidation of other faucets and freebies from early forks. Most did not gain traction in the community or otherwise failed and were delisted. With the addition of more freebies and later on Airdrops/Airdrips, many users started creating fake accounts in order to grow their network and benefit from additional rewards. This introduced significant scalability issues that were not initially anticipated. Over the years the scalability issues have resulted in intermittent (but recurring) connectivity and availability issues as well as significant delays in support response times. --- # 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: ``` GET https://docs.qoinpro.com/timeline/2014-2017-operational.md?ask= ``` 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.