# Web3 poker

With the advent of blockchain and Web3 gaming, online poker has been transformed. The focus is shifting from the regular game to farming, where players can earn rewards for participating.

Web3 gaming is all about decentralization and community participation. In this new era of gaming, players can earn rewards for their contributions to the ecosystem. This is where farming comes in. Farming is staking tokens or providing liquidity to a protocol in exchange for rewards. In Web3 poker, farming can incentivize players to participate in the ecosystem by providing liquidity, playing games, or contributing to the platform's development.

Several types of farming might be available in Web3 poker. One type of farming is liquidity provision farming. This involves staking tokens or providing liquidity to a protocol in exchange for rewards. Another type of farming is yield farming, which involves staking tokens to earn rewards in other tokens. Yield farming could involve staking tokens to earn rewards in the form of chips or other in-game items.

Gameplay farming is another type of farming that might be available in Web3 poker. This involves earning rewards for playing games on the platform or making predictions of some game results. For example, players could earn rewards for winning hands or participating in tournaments. This farming would incentivize players to play more games on the platform and could help increase user engagement.


---

# Agent Instructions: 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://pokerdao.gitbook.io/knowledge/the-poker/poker-history/web3-poker.md?ask=<question>
```

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.
