> For the complete documentation index, see [llms.txt](https://earn.blink.sv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://earn.blink.sv/chapter-206-the-evolution-of-money-iv/206.06-lesson-innovative-solution.md).

# 206.6 Lesson - satoshisBreakthrough

**Screen:** satoshisBreakthrough

**Headline:** Satoshi's Breakthrough

**Reward:** 3

**Text:** Satoshi's solution to the double spending problem was a breakthrough in computer science and distributed systems. Until Bitcoin, many believed that it would be unsolvable.

His solution allowed Satoshi to develop a new electronic cash system that for the first time made it possible for people to send digital money directly to each other, without needing a bank or other organization to help.

\=================================================================

## QUIZ

**Question:** Which problem did Satoshi have to solve to create Bitcoin?

**Answer:** The double spending problem

**Feedback:** Good job. Bitcoin uses a proof-of-work consensus mechanism where transactions are batched into blocks and chained together to a blockchain. This way, every user knows that every coin is only spent once

**Correct:** true

**Answer:** The problem of double coincidence of wants

**Feedback:** Not quite. The double coincidence of wants is a problem of barter that can be solved with money. Try again

**Correct:** false

**Answer:** The halving problem

**Feedback:** Hah no. The halving in bitcoin is not a problem, but part of the solution that Satoshi designed! More on that in Chapter 302. Try again!

**Correct:** false

<figure><img src="/files/QxC6WE6FuNUQNsz26DFS" alt=""><figcaption></figcaption></figure>


---

# 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://earn.blink.sv/chapter-206-the-evolution-of-money-iv/206.06-lesson-innovative-solution.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.