> For the complete documentation index, see [llms.txt](https://litepaper.betficasino.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://litepaper.betficasino.io/betfi-revenue-distribution-model/distribution-model/betfi-poker-revenue-model.md).

# BetFi Poker Revenue Model

BBetFi Poker generates revenue through a **5% rake applied to each hand played across all cash tables on the platform**.

BetFi Poker generates revenue through a **5% rake applied to each hand played across all cash tables on the platform**.

## Key Rake Features

• **5% Rake per hand**\
• **15 ADA maximum rake cap per pot**\
• **No Flop, No Drop** — if a hand ends before the flop is dealt, **no rake is taken**

This structure ensures the platform remains competitive with industry standards while protecting players from excessive fees on large pots.

## Rake Distribution

The total **5% rake per hand** is distributed across the BetFi ecosystem as follows:

| Allocation                       | Percentage | Description                                            |
| -------------------------------- | ---------- | ------------------------------------------------------ |
| VIP Table Owners                 | 2.5%       | Revenue share from tables owned by ecosystem partners  |
| $BETFI Stakers (Limited Program) | 1%         | Temporary incentive pool for early stakers             |
| BetFi Platform Operations        | 1.5%       | Infrastructure, development, liquidity, and operations |

## VIP Table Revenue Share

VIP Tables receive **50% of the total rake generated on their tables**.

This equals:

**2.5% of every hand played**

VIP tables are owned by selected ecosystem partners and provide a **recurring revenue stream tied directly to poker activity**.

#### Key Details

• Only **10 VIP Tables exist**\
• VIP owners receive **50% of the rake generated from their tables**\
• Revenue is generated automatically as hands are played

This structure allows strategic partners within the Cardano ecosystem to participate directly in BetFi Poker’s growth.

***

## $BETFI Staker Revenue Pool (Limited Program)

To reward early supporters, **1% of the total rake** will be allocated to a **$BETFI staking reward pool** for a limited period.

This incentive is designed to reward early participants who help bootstrap the ecosystem.

**Early participants benefit the most.**

As platform activity increases, the staking pool grows alongside it.

**Early birds get the worm.**

***

## BetFi Platform Operations

The remaining **1.5% of the rake** supports the continued growth and stability of the platform.

This allocation funds:

• Platform infrastructure and hosting\
• Development and engineering\
• Security and monitoring systems\
• Ecosystem integrations and expansion

This ensures BetFi Poker can scale sustainably while maintaining a high-quality player experience.

***

## Alignment With Platform Growth

The BetFi Poker model is designed so that platform growth benefits everyone involved.

**More players → more hands played → more rake generated**

Which results in:

• Increased revenue for VIP table owners\
• Larger staking rewards for $BETFI holders\
• Greater resources for platform expansion

This creates a **self-reinforcing ecosystem where participation and platform success grow together.**


---

# 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://litepaper.betficasino.io/betfi-revenue-distribution-model/distribution-model/betfi-poker-revenue-model.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.