> For the complete documentation index, see [llms.txt](https://docs.robincompute.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.robincompute.org/providers/staking.md). # Staking $RCOMPUTE is an ERC-20 token on Robinhood Chain, and staking it (locking tokens in a contract for a set period) does two different jobs depending on who you are. A provider who stakes qualifies for the 85% payout rate and moves up in routing priority. A holder who stakes, provider or not, collects a slice of the weekly protocol fee distribution, paid in USDG. *** ## Staking as a provider Lock at least 1,000 $RCOMPUTE in the `staking` contract and every job you complete pays out at 85% of its credit value. Without a stake, the rate is 75%. | Parameter | Value | | ------------------------ | -------------------------------------------------------------- | | Minimum stake to qualify | 1,000 $RCOMPUTE | | Unstaked payout rate | 75% of job value | | Staked payout rate | 85% of job value | | Earnings increase | \~13.3% more USDG per completed job | | Routing priority boost | The routing algorithm ranks staked workers above unstaked ones | Run the numbers on the Standard tier: a request costs 8 credits ($0.08), which pays $0.060 unstaked and $0.068 staked. Multiply that gap across real volume. It adds up fast. ### The staking flow for native workers 1. Have `robincompute-node` installed and a registered worker; the \[Native Worker guide]\() covers both. 2. Open `robincompute.org/app`, head to the Earn tab, and select "Stake $RCOMPUTE." 3. Pick your amount (1,000 $RCOMPUTE minimum) and a lock period. 4. Approve the transaction in your wallet. RobinCompute sponsors the gas through ERC-4337, so no ETH is needed. Once confirmed, the `staking` contract records the stake against your registered worker address. From then on, the `settlement` contract checks that record at payout time and applies the 85% rate to every newly completed job. No approvals, no support tickets: the contract reads the record and pays accordingly. *** ## Lock periods Every stake carries a lock period of your choosing. The lock length changes one thing: your $RCOMPUTE reward multiplier. It has no effect on the USDG side; the 85% rate applies identically across all lock lengths. | Lock period | $RCOMPUTE reward multiplier | | ----------- | --------------------------- | | 30 days | 1.0x | | 90 days | 1.25x | | 180 days | 1.5x | These $RCOMPUTE rewards flow from the Community/Provider rewards pool, which holds 40% of total supply released over 4 years. Lock for 180 days instead of 30 and you collect 50% more $RCOMPUTE per completed job; USDG payouts sit at 85% either way. A lock is binding: the staked $RCOMPUTE stays put until the period runs out. Your USDG job earnings are never locked. They are spendable the moment they arrive. *** ## Staking without running a worker You do not need to run a node to stake. Any wallet with a $RCOMPUTE balance can stake it and collect a share of the weekly USDG payout from the protocol treasury. The pool is 50% of the protocol's weekly fee revenue, divided among stakers in proportion to their staked balances. **How to do it:** 1. Connect your wallet at `robincompute.org/app`. 2. Open the Staking tab. 3. Set an amount and a lock period. 4. Approve the transaction. Distributions go out automatically each Monday around 00:00 UTC, straight to your wallet. Each one is an ordinary public transaction on Robinhood Chain. Pull it up on Blockscout and check the math yourself. *** ## Slashing A provider who submits a fake proof of completion, and whose dishonesty is confirmed through the dispute process, gets slashed: part of the stake is burned. | Event | Consequence | | -------------------------- | --------------------------------------------------- | | Confirmed fraudulent proof | 5% of staked $RCOMPUTE burned | | Burned to | Protocol burn address (permanent) | | Effect on payout rate | Drops to 75% if balance falls below 1,000 $RCOMPUTE | The penalty is deliberately proportional: it stings without being ruinous, and it scales with the stake. Stake 10,000 $RCOMPUTE and get caught faking a proof, and 500 $RCOMPUTE is gone for good. Only a confirmed dispute triggers slashing. Jobs that merely fail or get rerouted carry no slashing risk at all. *** ## Unstaking After the lock expires, withdraw whenever you want. 1. Open the Staking tab in the app. 2. Hit "Unstake" beside the expired stake. 3. Approve the transaction. Your $RCOMPUTE comes back to your wallet within that same transaction. There is no cooldown between lock expiry and withdrawal. Holding several stakes on different lock schedules? Each one unlocks and withdraws on its own timeline. *** ## Reading your stake from the chain Nothing here depends on believing us. Stakes live in the `staking` contract, indexed by wallet address, and anyone can read them straight over Robinhood Chain JSON-RPC. Here is the query using Foundry's `cast`: ```bash # Read your staked balance out of the staking contract cast call $(robincompute-node stake-contract) \ "stakeOf(address)(uint256)" YOUR_WALLET_ADDRESS \ --rpc-url https://rpc.mainnet.chain.robinhood.com ``` Prefer a UI? Search your wallet address in the RobinCompute Explorer, or use Blockscout at `robinhoodchain.blockscout.com`. Stake history, lock periods, expiry dates, accrued rewards: all public, no login. --- # 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.robincompute.org/providers/staking.md?ask=&goal= ``` `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.