> For the complete documentation index, see [llms.txt](https://slice-ledger.gitbook.io/sliceledger/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://slice-ledger.gitbook.io/sliceledger/slice-token/utility.md).

# Utility

#### Secure the Network:

The primary utility of SLICE token is to secure the SliceLedger Chain network with using Proof-of-Stake system. In order to run SliceLedger Node and participate in securing the network, validator must hold 50,000 SLICE and voters have to lock up their SLICE to any validator node to increase node capacity. In exchange for participation, validator and voter both receive rewards in SLICE after every transaction.

#### Network fees:

SLICE is used to pay for network fees such as transaction fees, smart contract deployment and other networks activities. The fees on SliceLedger Chain network is extremely cheap compared to other blockchain networks. However, lower fees does not compromise network states as it sets limitations to suspicious activities via SLICE privacy protocol.

#### Payments

SLICE is ideal for crypto currency payments to enterprises and businesses all around the world. It offers very quick and low-cost transactions compared to other crypto payment options. As the network eligible to process 100,000 transactions per second (TPS), depending on the number of validator nodes, SliceLedger Chain is high throughput and affordable blockchain network to every user.

#### Governance

As being native token, SLICE is used in SliceLedger on-chain governance. SliceLedger Chain is a fully decentralized network, hence any decision on the network is carried out by on-chain governance process. SLICE holders can propose and vote for changes and improvements by staking their tokens.


---

# 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://slice-ledger.gitbook.io/sliceledger/slice-token/utility.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.