> For the complete documentation index, see [llms.txt](https://docs.cryft.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cryft.app/whitepaper/from-a-holders-perspective/the-problem-s.md). # The Problem(s) ## Learning Curve Like most new ideas and systems, cryptocurrency is full of fear and uncertainty in the eyes of the consumer. We all remember the first time the words "crypto", blockchain and alike entered our life. None of us knew what the heck we were hearing, and we certainly did not expect them to become words we use every single day. ## Availability We keep hearing words like Bitcoin, Etheruem and others. Our heads fill with curiosity and desire, only to find way too many different sources of information. Left with a cloud of uncertainty over our heads, and ultimately nowhere to go and engage these new things called "bitcoins". ## Usability I got these things called bitcoins, now what? Good question! Once crypto and all the other digital assets have landed in my wallet (wasn't easy by the way), what can I do with them? I'm stressing over the value, and facing the fact I cannot go to my local shops (large and small) to purchase physical items. --- # 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, and the optional `goal` query parameter: ``` GET https://docs.cryft.app/whitepaper/from-a-holders-perspective/the-problem-s.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.