> For the complete documentation index, see [llms.txt](https://docs.usedecentral.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usedecentral.org/providers/staking.md).

# Staking

Staking $DECENTRAL serves two purposes. For providers, it unlocks the 85% payout rate and elevated routing priority. For any $DECENTRAL holder, it earns a share of the weekly protocol fee distribution in USDC.

***

## Provider staking

Providers who stake a minimum of 1,000 $DECENTRAL in the `staking` program receive 85% of each completed job's credit value. Unstaked providers receive 75%.

| Parameter                | Value                                                     |
| ------------------------ | --------------------------------------------------------- |
| Minimum stake to qualify | 1,000 $DECENTRAL                                          |
| Unstaked payout rate     | 75% of job value                                          |
| Staked payout rate       | 85% of job value                                          |
| Earnings increase        | \~13.3% more USDC per completed job                       |
| Routing priority boost   | Staked workers are ranked higher in the routing algorithm |

At the Standard tier (8 credits per request = $0.08), the difference per job is $0.060 unstaked versus $0.068 staked. At any meaningful volume, this adds up quickly.

### Staking as a native worker

1. Make sure `decentral-node` is installed and your worker is registered. See the \[Native Worker guide]\().
2. Go to `usedecentral.org/app`, navigate to the Earn tab, and click "Stake $DECENTRAL."
3. Choose an amount (minimum 1,000 $DECENTRAL) and a lock period.
4. Approve the staking transaction from your wallet.

The `staking` program registers your stake and links it to your registered worker address. The `settlement` program reads this during payout calculation and applies the 85% rate immediately for jobs completed after the stake confirms.

***

## Lock periods

You choose how long to lock your $DECENTRAL stake. The lock period affects your $DECENTRAL reward multiplier, not your USDC per-job payout rate. The 85% rate applies regardless of lock period.

| Lock period | $DECENTRAL reward multiplier |
| ----------- | ---------------------------- |
| 30 days     | 1.0x                         |
| 90 days     | 1.25x                        |
| 180 days    | 1.5x                         |

$DECENTRAL rewards accumulate from the Community/Provider rewards pool (40% of total supply over 4 years). A 180-day lock earns 50% more $DECENTRAL per completed job compared to a 30-day lock, while USDC payout stays at 85% for both.

Once a lock period begins, you cannot withdraw the staked $DECENTRAL until it expires. USDC earnings from completed jobs are always immediately available regardless of lock status.

***

## Passive staking

You do not need to run a worker node to stake $DECENTRAL and earn protocol fees.

Any wallet holding $DECENTRAL can stake and receive a share of the weekly USDC distribution from the protocol treasury. This distribution comes from 50% of the protocol's weekly fee revenue, split pro-rata among all stakers by staked balance.

**To stake passively:**

1. Go to `usedecentral.org/app` and connect your wallet.
2. Navigate to the Staking tab.
3. Choose an amount and lock period.
4. Approve the transaction.

Weekly USDC distributions are sent to your wallet automatically every Monday at approximately 00:00 UTC. Each distribution is a public Solana transaction.

***

## Slashing

Providers who submit fraudulent proofs of completion and are confirmed dishonest through the dispute process face slashing.

| Event                      | Consequence                                          |
| -------------------------- | ---------------------------------------------------- |
| Confirmed fraudulent proof | 5% of staked $DECENTRAL burned                       |
| Burned to                  | Protocol burn address (permanent)                    |
| Effect on payout rate      | Drops to 75% if balance falls below 1,000 $DECENTRAL |

Slashing is designed to be proportionate but meaningful. A provider staking 10,000 $DECENTRAL who is caught submitting a fraudulent proof loses 500 $DECENTRAL permanently. This creates a financial disincentive that scales with the stake.

Slashing only applies to confirmed disputes. A failed job or a rerouted job does not trigger slashing.

***

## Unstaking

When your lock period expires, you can withdraw your staked $DECENTRAL at any time.

1. Go to the Staking tab in the app.
2. Click "Unstake" next to the expired stake.
3. Approve the transaction.

The $DECENTRAL is returned to your wallet in the same transaction. There is no cooldown period after the lock expires.

If you have multiple stakes with different lock periods, you can unstake them independently as each one expires.

***

## Viewing your stake on-chain

Your stake is stored in a PDA in the `staking` program derived from your wallet address. You can view it directly using the Solana JSON RPC:

```bash
# Query the staking program for your stake account
solana account $(decentral-node stake-pda --wallet YOUR_WALLET_ADDRESS)
```

Or through the Decentral Explorer by searching your wallet address. Your full stake history, lock periods, expiry dates, and accrued rewards are visible without logging in.


---

# 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://docs.usedecentral.org/providers/staking.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.
