> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/api-reference/challenges-creators-and-rewards.md). # Challenges, creators & rewards Challenge lifecycle, funding verification, creator analytics, reward allocation and reconciled claim flows. ## Challenge routes ``` GET /api/v1/challenges POST /api/v1/challenges POST /api/v1/challenges/:id/status POST /api/v1/challenges/:id/funding/reconcile ``` Challenge lifecycle: ``` DRAFT → SCHEDULED → OPEN → SUBMISSIONS_CLOSED → REVIEW → VOTING → WINNERS_SELECTED → REWARDS_ALLOCATED → COMPLETED ``` Reward funding is intentionally separate: ``` ANNOUNCED → RESERVED → FUNDED → CLAIMABLE → DISTRIBUTED ``` A published reward-pool number must not be rendered as `FUNDED` until protected reconciliation verifies underlying treasury/escrow coverage. ## Creator routes ``` GET /api/v1/creators/:wallet GET /api/v1/creators/:wallet/projects GET /api/v1/creators/:wallet/contributions GET /api/v1/creators/:wallet/rewards ``` Wallet path parameters are validated before provider/database work. Creator analytics may include completed/active projects, accepted contributions, challenge wins, allocations, claimed/pending rewards, reputation and portfolio participation. ## Reward routes ``` GET /api/v1/rewards GET /api/v1/projects/:id/rewards POST /api/v1/projects/:id/rewards/allocate POST /api/v1/rewards/:id/funding/reconcile POST /api/v1/rewards/:id/claim ``` Reward values are stored as atomic integer amounts plus explicit decimals. A reward record persists durable identity, project, recipient wallet, amount, mint, decimals, funding status, transaction intent/signature status, allocation/claim timestamps and idempotency identity. ## Claim lifecycle ``` ALLOCATED ↓ verified funding CLAIMABLE ↓ authenticated creator + verified recipient wallet TransactionIntent ↓ wallet submission SUBMITTED ↓ trusted reconciliation CONFIRMED → CLAIMED / DISTRIBUTED ``` A successful claim HTTP request does not mark a reward claimed. Chain confirmation is required. Failed transaction intents can return the reward to a retryable claimable state without allocating twice. ## Authorization Reward allocation requires an authorized project/treasury/admin role. Funding reconciliation requires the protected reconciliation boundary. A creator can claim only a reward belonging to a wallet verified on that authenticated account. --- # 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://sonic-ai-works.gitbook.io/sonic-networks-docs/api-reference/challenges-creators-and-rewards.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.