# Roles and Project Statuses The core OneWorld Launchpad experience is defined by roles and statuses.\ Roles determine who can perform which actions, and statuses determine when those actions are available. ### Core Roles #### Project Owner The project owner launches and continuously advances the project. The project owner is responsible for: 1. Launching the project 2. Submitting project materials 3. Configuring fundraising rounds 4. Publishing project Updates 5. Claiming successful fundraising 6. Submitting a stage proof before applying to open the next round 7. Opening the next round or preparing for final launch Project owners must keep information accurate, fundraising parameters reasonable, and the operating wallet under control. They must also maintain information updates during fundraising. A project owner does not simply submit a project and wait; the project must be actively moved through each stage. #### User / Investor The user participates in projects and is responsible for: 1. Connecting a wallet 2. Viewing project and round information 3. Subscribing 4. Submitting exit applications 5. Claiming assets on-chain after results are finalized Users must verify their own wallet, chain, funds, transaction fees, and project risks. The platform displays statuses and rules, but users still make their own participation decisions. #### Platform Reviewer The platform reviewer is responsible for: 1. Reviewing project creation applications 2. Reviewing stage proof applications 3. Determining whether a project qualifies to open the next fundraising round 4. Reviewing final launch applications 5. Providing supplement or correction directions when an application is rejected The reviewer does not make investment decisions for users and does not deliver the project for the project owner. Review focuses on material completeness, rule clarity, stage proof quality, next-round application support, and process compliance. ### Project Statuses #### Pending Review The project has been submitted and is waiting for platform review. In this status: 1. The project owner can view submitted content and review status 2. Ordinary users usually cannot see the project in public lists 3. The project cannot accept subscriptions yet #### Rejected The project did not pass review and can be edited and submitted again. Common reasons include: 1. Incomplete project introduction 2. Unclear Token information 3. Obvious conflicts in fundraising parameters 4. Missing team information 5. Insufficient roadmap or stage goal description #### Upcoming The project has passed review, but the current round has not started. In this status: 1. Users can browse project information in advance 2. Users can view current-round price, allocation, and start time 3. Users cannot subscribe yet 4. Project owners can prepare community communication and supplement project information #### Live The current round is open for subscription. In this status: 1. Users can subscribe 2. The project detail page shows current-round progress 3. If this is a later round, eligible previous-round holders can submit exit applications 4. Project owners should continue publishing Updates and monitoring fundraising progress #### Successful The current round has succeeded, but the project has not entered final trading status. In this status: 1. Users wait for or execute result claims 2. Project owners can claim the current-round funds 3. Project owners need to continue publishing progress 4. If project owners want to open the next round, they must submit a stage proof and pass review #### Failed The current round has failed, and the project remains in the current round. In this status: 1. Users can claim refunds or returned assets according to the rules 2. The project owner cannot directly open the next round 3. The project page keeps the failed result and related explanations #### Live / Tradable The project has completed the final round and entered the trading stage.\ At this point, the top of the project detail page switches to the trading view and provides buy, sell, price chart, trade records, and holder ranking information. In this status: 1. The project is no longer presented primarily as a current fundraising round 2. Users see trading information first 3. Original project information, team, Updates, and Tokenomics remain available 4. Users can buy or sell through the Swap area ### What Users See Under Different Statuses #### Pending Review / Rejected Ordinary users do not see projects that have not passed review in public lists. #### Upcoming Users can browse project information and current-round rules in advance, but cannot subscribe.\ This stage is used to review price, timing, sale amount, team information, and roadmap. #### Live Users can view project information, subscribe, and submit exit applications when eligible.\ The page focuses on current-round fundraising progress, personal participation status, and estimated claimable results. #### Successful Users can view the current-round result, claim status, and follow-up project progress.\ If settlement is complete, users can initiate on-chain claims. #### Failed Users can view the failed result and claim refunds or returned assets according to the settlement rules. #### Live / Tradable Users see the trading view first, including price, trend, trade records, and the Swap area. ### Key Conditions for Status Changes Project status usually changes according to the following conditions: 1. After submission, the project enters pending review 2. After approval, the project enters upcoming status 3. At the start time, the project enters live status 4. When the current round meets the success condition, it enters successful status 5. When the current round fails to meet the success condition, it enters failed status 6. When the project owner applies to open the next round, the next round opens after stage proof approval 7. After final launch approval, the project enters live / tradable status Each status change should be understandable to users and should show the corresponding rule, result, or next action on the page. --- # Agent Instructions: 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: ``` GET https://docs.oneworld.xyz/oneworld-launchpad/core-rules/roles-and-project-statuses.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.