> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/higher-learning/bsv-academy/bitcoin-as-historical-phenomenon-1/bitcoin-facing-states-regulatory-tensions-and-co-optation-strategies/phase-of-indifference-and-rejection.md).

# Phase of Indifference and Rejection

During the first years (2009–2013), Bitcoin was perceived as a marginal phenomenon, without real impact on the economic system. Authorities did not consider it a threat or a relevant instrument.

This changed with the appearance of the first media scandals and the use of Bitcoin on platforms like Silk Road. From that moment, governments' initial responses were predominantly restrictive:

· Warnings about its use in illicit activities.

· Direct prohibitions in some countries (China, Bolivia, Morocco).

· Associations between Bitcoin, money laundering, and tax evasion.

These measures reflected a lack of knowledge of the technology and a defensive reaction to its disruptive potential.

BSV addresses these concerns with a focus on verifiable and low-cost transactions, promoting secure adoption for everyday uses.


---

# 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://hub.bsvblockchain.org/higher-learning/bsv-academy/bitcoin-as-historical-phenomenon-1/bitcoin-facing-states-regulatory-tensions-and-co-optation-strategies/phase-of-indifference-and-rejection.md?ask=<question>&goal=<endgoal>
```

`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.