> For the complete documentation index, see [llms.txt](https://mining.gitbook.titan.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mining.gitbook.titan.io/how-to-buy-hashpower.md).

# How to buy hashpower

After the seller has created the smart contract, and staked their collateral, and the validator has determined the price, verified the stake, and launched the smart contract, the buyer can then engage with the open sell-offer.

**1) Buyer wants to Buy the Smart Contract**

1.1) The buyer sends payment in the form of WETH, USDT, USDC, or WBTC into the smart contract and pays the gas fee.

1.2) The validator starts the smart contract. The seller's stake becomes locked.

**2) Smart Contract is Started**

2.1) The validation system described in the previous section monitors the flow of hashpower and updates the smart contract

2.2) As hashpower flows, validator pays the seller out of the smart contract.

**3) Smart Contract Ends**

3.1) Validator confirms hashpower delivered equals the hashpower contracted. 

3.2) Delivers final payment. 

3.3) The validator unlocks the seller's stake and returns it. The validator sets the smart contract to 'Open' again.

![](/files/-Md-tEPDQ6cgIJTFArzG)


---

# 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://mining.gitbook.titan.io/how-to-buy-hashpower.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.