> For the complete documentation index, see [llms.txt](https://docs.oshi.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oshi.co/gate-2-campaign/legacy-contributors.md).

# Legacy Contributors

Supported GATE 2 before August 15, 2025? You're a Legacy Contributor. Get 48-hour early access Feb 25 and a permanent badge.

Recognition and benefits for the 3,700+ early supporters who participated during the GATE 2 soft launch, which began with the 10th anniversary announcement of the GATE anime and ran through August 15, 2025.

***

### <img src="https://2612956370-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsHO2CVanSsqKtCJtf53U%2Fuploads%2F7muiqvyolFXQoKCmhj2p%2Fimage.png?alt=media&amp;token=49cb14c8-da64-4821-a0eb-a4bad5e0c4cd" alt="" data-size="original">

### Your Legacy benefits

**48-hour early access**

Participate starting Feb 25, 2026 (JST), two days before public launch.

**Legacy badge**

A permanent badge marking you as an original supporter. This badge is exclusive to early supporters and will never be available again. Stays with you regardless of final rank.

**Special Discord role and community access**

Legacy Contributors receive a dedicated Discord role with early access to platform updates, production news, and community events with exclusive giveaway opportunities. If you haven't already, connect your Discord account to the Oshi platform to receive your role.

**Bonus Merit**

You received 100 bonus Merit Points for your early support. These have already been delivered to your account.

***

### Confirming your status

If you contributed before Aug 15, 2025, you should see Legacy status in your Oshi account.

> 📝 **Don't see your status?** Contact <support@oshi.co> with your details.

You'll receive early access notifications via email before Feb 25.

***

### Participating further

Your Legacy status doesn't limit you to Seaman rank. During the campaign (Feb 27 to May 27, 2026), you can participate at any higher rank to unlock additional rewards.

Your Legacy badge stays with you permanently, regardless of your final rank.

***

**Related articles**

* [Campaign Timeline](https://docs.oshi.co/gate-2-campaign/campaign-timeline.md): Key dates including early access
* [Understanding Ranks](https://docs.oshi.co/gate-2-campaign/understanding-ranks.md): The seven ranks and what each level unlocks
* [Reward Details by Tier](https://docs.oshi.co/gate-2-campaign/reward-details-by-rank-tiers.md): What each rank includes
* [Oshi Membership Rewards](https://docs.oshi.co/start-here/oshi-membership-rewards.md): Merit, Officer Rewards, and Victory Drops

{% hint style="info" %}
**Still need help?** Join our [Discord](https://discord.gg/oshi) or email <support@oshi.co>
{% endhint %}


---

# 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.oshi.co/gate-2-campaign/legacy-contributors.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.
