> For the complete documentation index, see [llms.txt](https://samurainodes.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://samurainodes.gitbook.io/docs/2.-understanding-the-nodes/2.2-how-does-sliding-tax-work.md).

# 2.2 How does sliding tax work?

The sliding tax model functions in the following manner:

Time tiers: 0 - 6.9 days - 50% tax 7 - 13.9 days - 40% tax 14 - 20.9 days - 30% tax 21 - 27.9 days - 20% tax

28+ days (after 28 days is where each node tier is exposed to a different tax rate): BUKE - 5% tax MONONOFU - 8% tax MUSHA- 10% tax

You can view individual tax rates on each of your nodes within the Samurai dApp. When you click on “CLAIM ALL”, the relevant tax rates are applied to each of the node, it is not averaged.

e.g. If you have 2 nodes: Node #1 with 50% tax rate and Node #2 with 20% tax rate, the protocol will not take an average of 35% tax, rather it will apply 50% tax on Node #1's accumulated rewards and 20% tax on Node #2's rewards.

\--

The sliding tax mechanism is a deviation from the previous fixed claims tax mechanism that the protocol previously relied on. All taxes (cashout fees) collected by the protocol are a part of the core team's allocation (see [section 1.3 ](/docs/1.-what-is-samurai-and-how-does-it-work/1.3-now-how-does-it-actually-work.md)and [section 1.10](/docs/1.-what-is-samurai-and-how-does-it-work/1.10-smart-contract-functionality.md) for additional details about the protocol's smart contract functionality, tokenomics and the core team allocations)


---

# 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://samurainodes.gitbook.io/docs/2.-understanding-the-nodes/2.2-how-does-sliding-tax-work.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.