> 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/changelog/2026-09-01-pwa-auth-registry-and-leaderboard-assets.md).

# 2026-09-01 — PWA, auth registry & leaderboard assets

This release refines the SONIC AI WORKS application shell, authentication presentation, progressive-web-app behavior, achievement assets, and creator leaderboard.

## PWA

* `apps/web/pwa.tsx` now owns service-worker registration, install prompt, offline status, and update-ready/reload UI.
* `public/sw.js` uses versioned cache invalidation and supports an explicit `SKIP_WAITING` update message.
* the web manifest exposes approved SONIC app icons plus Creators, Tokenomics, and Pricing shortcuts.
* authenticated mutations, checkout writes, and payment operations are never treated as offline cacheable writes.

## Authentication

Authentication presentation is split into reusable modules:

```
apps/web/components/AuthPortal.tsx
apps/web/auth/signin.tsx
apps/web/auth/signup.tsx
apps/web/auth/social-providers.ts
apps/web/config/auth.ts
```

The social provider registry is declarative and easy to extend without rewriting the login shell. Google, GitHub, and Apple remain enabled by default. X is opt-in. **Discord remains registered but disabled** rather than being removed.

To add another provider, engineering adds one registry entry, one public enable flag, and the matching server OAuth/OIDC adapter. OAuth client secrets/private keys remain server-only.

Wallet login remains an identity-proof flow. It does not authorize transactions; transfer/payment intent and final wallet approval are separate boundaries.

## SONIC coin assets

The product now exposes three SONIC coin variants:

* Signature Red
* White coin with red SONIC mark
* Silver coin

SVG is preferred for UI rendering; PNG fallbacks remain available for raster-only consumers. Coin asset mappings are published under `public/assets/coins/manifest.json`.

## Creator trophy system

Gold, Silver, Bronze, and Creator SONIC trophy variants are reusable through shared `SonicTrophy` and `SonicRankBadge` components.

The creator leaderboard now uses branded podium trophies on featured cards and includes a trophy-system shelf explaining the visual hierarchy. Trophies never replace canonical score/rank data.

## Web3 visuals

`@web3icons/react` remains pinned to `4.1.21` for wallet, network, and standard token visuals. SONIC-specific coins, marks, and trophies remain custom SONIC assets.

## Navigation governance

Tokenomics continues to use the standard public SONIC navigation and dark-red footer. The alternate token-only reference navigation is not used in production.

## Documentation parity

The Documentation space was updated in the same release with the PWA contract, social-provider registry, disabled-Discord policy, coin/trophy asset rules, leaderboard integration, and GitBook parity requirement.


---

# 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/changelog/2026-09-01-pwa-auth-registry-and-leaderboard-assets.md?ask=<question>&goal=<endgoal>
```

`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.