> For the complete documentation index, see [llms.txt](https://docs.stryke.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stryke.xyz/tokenomics/xsyk-token.md).

# xSYK Token

xSYK is the previous SYK staking system on Arbitrum. It is being replaced by StakedSYK on Robinhood Chain. This page covers the migration; for the new staking model, see [SYK Token](/tokenomics/syk-token.md).

## Old vs new

|            | xSYK (old)                   | StakedSYK (new)                 |
| ---------- | ---------------------------- | ------------------------------- |
| Deposit    | SYK locked into xSYK 1:1     | Stake SYK directly              |
| Wrapper    | Transfer-restricted xSYK     | None                            |
| Exit       | 7 to 180 day vest            | 3 to 7 day cooldown             |
| Exit value | 50 to 100% depending on vest | 100%                            |
| Rewards    | SYK only                     | SYK plus approved reward tokens |
| Chain      | Arbitrum                     | Robinhood Chain                 |

xSYK staking rewards ended on 8 October 2025.

## Migrating

Migration is opt-in and self-serve, with no deadline in the initial period. xSYK stays functional and redeemable 1:1 for SYK throughout, so you can move when convenient. The journey is one guided flow:

1. Exit or unstake xSYK on Arbitrum.
2. Claim any outstanding old rewards.
3. Redeem xSYK 1:1 for SYK.
4. Bridge SYK from Arbitrum to Robinhood Chain via the LayerZero adapter.
5. Stake SYK in StakedSYK.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stryke.xyz/tokenomics/xsyk-token.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.