Update and Improve Use section

[Juminstock]

Changelog:

• Replaced UCG program page with ACC Strategic Staking Program (SSP): Lane A/B mechanics, eligibility criteria, first operation (April 2026, 122M ASTR across 5 projects)
• Removed MetaMask Snap page and all references (deprecated feature)
• Fixed 15+ prose em-dashes → commas across FAQs, staking guides, governance, and portal docs
• Removed banned words: seamless, empower, novel approach, innovative, robust across 10+ files
• Fixed spelling: on-chain→onchain, Web3→web3, and 8 typos (funtions, reponse, Cheching, comnmunity, priveledge, lost→loss, These is→This is)
• Removed first-person voice: "our most recommended" → "the recommended"
• Replaced marketing blockquote in Soneium transfer index with factual description
• Fixed dApp Staking index and staker/dev overview: removed "novel approach" and "unique mechanism"

[ghost]

Visit the preview URL for this PR (updated for commit cdd8c5b):

https://astar-docs--pr789-updates-improve-use-0klhgtzw.web.app

_{(expires Fri, 08 May 2026 21:58:24 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: f2f13e9b593d211faae6343d67a88fac3fd7268d}

[Gunit2481]

Review withdrawn for further refinement.

Withdrawing for additional review before resubmitting.

[Gunit2481]

Suggest holding this PR until three things are resolved: the SSP doc is trimmed to rules only (operational data moved to ACC forum logs), the UCG-era references in code-of-conduct.md and subsquare_guide.md are updated to match SSP, and the Townhall guide is either warned or replaced. Specifics below.

Blockers

1. Operational data belongs in ACC forum logs, not in the doc

Documentation should describe the SSP program (rules, lanes, parameters, eligibility, KPI methodology, decision processes). Operational state and specific actions should live in ACC governance logs on the Astar Forum and be linked from the doc, not embedded in it. As written, the page mixes both, which has two effects: factual claims rot as state changes, and internal contradictions appear (see the 80M-cap vs 122M-deployment mismatch).

Remove the following from unstoppable-community-grant-program.md:

• Line 13: "The total Community Treasury holds approximately 125M ASTR... keeping a liquid reserve of ~45.5M ASTR available." Treasury balance fluctuates; this will be wrong within weeks. Also the arithmetic is off (125 − 80 = 45, not 45.5).
• "First operation: April 2026" section (lines 94-106): the entire 5-project allocation table, the 122M total, the per-project rationale column, and the Motion #145 / extrinsic 13039421-2 references. This is operational reporting, not documentation.

Replace with a single sentence in the Governance section: "Active and historical SSP operations are published in ACC governance logs on the Astar Forum."

This change also resolves what would otherwise be a hard internal contradiction: the page caps combined Lane A + B exposure at 80M but reports a 122M inaugural deployment, with no explanation of how the cap was satisfied (grandfathering? transitional rules? cap measured differently?). Removing the operations data is cleaner than trying to reconcile it inside the doc.

Keep all the rule and parameter content (Lane A/B caps, trigger thresholds, eligibility filters, KPI weights, removal conditions): those are program rules, not operations.

2. code-of-conduct.md line 27 sends pre-MVP projects to a page that excludes them

The dApp Staking Code of Conduct still reads:

For early-stage, pre-MVP projects, refer to the Unstoppable Community Grants (UCG) program. It offers structured support with clear exit criteria tied to dApp Staking V3's tier system.

The link still resolves (filename preserved), but the destination is now the SSP page. SSP Stage 1 requires:

• 6+ months of continuous onchain activity
• Publicly accessible, functional product
• 200+ unique active wallets in the past 90 days

Pre-MVP projects fail all three. This referral is now actively misleading. Either:

• Update this row to point pre-MVP projects to a different resource (forum, grants program, or none)
• Or drop the pre-MVP recommendation and note that pre-MVP projects are not currently supported

3. code-of-conduct.md line 30 still references Tier 4

Tier 4 projects are expected to submit at least monthly updates. A lack of reporting for 3 consecutive months may trigger a delisting process.

The PR itself adds the note that "Tier 1 and Tier 4 are structural placeholders with 0 slots and 0% reward share" in for-devs/index.md and dapp-staking.md. There are no Tier 4 projects. This rule is dead. Drop the Tier 4 reference or rewrite to "All active projects (Tier 2 and Tier 3)..."

4. UCG references survive in subsquare_guide.md

Four lines still describe the Community Council's role in terms of UCG (the program this PR is replacing):

• Line 336: "Unstoppable Community Grant (UCG) Program: Reviewing and approving grant proposals..."
• Line 347: "Managing dApp Staking on behalf of the Community Treasury (UCG)"
• Line 418: section header "3.2.2. Staking from the Community Treasury (UCG)"
• Line 420: "One of the main responsibilities of the Community Council is to stake in dApps that are part of the Unstoppable Community Grant (UCG) program."

Update to SSP terminology (Lane A / Lane B framing), or scope the SSP rewrite to a follow-up PR that touches both files together. As shipped, the user-facing governance guide and the SSP page describe two different programs.

5. Townhall guide routes users to an offline platform

docs/use/how-to-guides/layer-1/governance/astar-townhall.md documents the offchain governance flow on Townhall (https://astargov.com/astar), which is no longer reachable. The PR touches this file for terminology fixes but doesn't address the dead destination. The page sends users through 6 separate astargov.com links and 7 step-by-step screenshots of a platform they can't access.

For this PR (minimum): add a :::danger admonition at the top of the file noting Townhall is unavailable, so users don't follow the guide to a dead site.

For a follow-up PR: replace Townhall with OpenSquare as the offchain governance platform of record, rewrite the page for the OpenSquare flow, and clean up the 7 orphaned figures in docs/use/img/astar_townhall_*.png.

Marketing language sweep

The PR removed a lot of pitch language correctly. A few vendor blurbs survived in files the PR otherwise touched. Suggested rewrites below.

docs/use/get-started/astar-substrate-wallet/wallet/subwallet/index.md

Current:

SubWallet is a comprehensive non-custodial wallet solution for Substrate & Ethereum ecosystems. Built on top of Polkadot.js, SubWallet focuses on improving UX & UI. We envision a crypto wallet as a web3 multiverse gateway through which users can enjoy multi-chain services with utmost ease and absolute security.

Proposed:

SubWallet is a non-custodial wallet supporting Substrate and Ethereum networks. Built on top of Polkadot.js with a redesigned UI.

The "we envision... utmost ease and absolute security" is straight vendor copy. The PR's Web3 → web3 change is correct but should have come with cutting the rest.

---

docs/use/how-to-guides/soneium/transfer-tokens/from-ethereum-to-soneium.md, Stargate section

Current:

Stargate is a fully composable cross-chain bridge protocol built on LayerZero that enables native asset transfers between different blockchain networks. It supports native transfers of ETH and stablecoins across chains.

Proposed:

Stargate is a cross-chain bridge built on LayerZero. It supports ETH and stablecoin transfers across chains.

"Fully composable" is bridge-vendor language. The simpler version says what the tool is and what it does.

---

Same file, Rhino.fi section

Current:

Rhino.fi is a powerful cross-rollup bridge that supports many assets and many L2s. It offers a straightforward bridging experience with quick and secure transactions.

Proposed:

Rhino.fi is a cross-rollup bridge supporting many assets across multiple L2s.

"Powerful... quick and secure" is filler. The fact that it's a bridge that supports assets and L2s carries the point.

---

Same file, Superbridge section

Current:

Superbridge is the recommended option for bridging ETH and Superchain assets into Soneium. It's designed from the ground up for native bridging within the Superchain ecosystem.

Proposed:

Superbridge is the recommended option for bridging ETH and Superchain assets into Soneium. It is built specifically for the Superchain ecosystem.

"Designed from the ground up" is a marketing trope. Direct version is clearer.

Verification needed

• Threshold sources: Lane A triggers reference 28M floor and 75M strategic-partner threshold; Lane B caps at 35M/position with combined 80M ceiling. These are program rules and belong in the doc, but they currently appear without citation. Add a footnote linking to the forum proposal that defined and approved them, so when the ACC updates parameters the source of truth is unambiguous.

Nits

• 4 em-dashes missed:
  • dapp-staking/code-of-conduct.md line 17: "This includes—but is not limited to—using ASTR..."
  • dapp-staking/code-of-conduct.md line 27: "...continued ecosystem contribution—even if not natively on Astar Network."
  • dapp-staking/for-stakers/unstaking.md line 56: "Chunk 1 — 30 SBY" (example label, low priority)
  • dapp-staking/for-stakers/how-to-stake.md line 120: "Video temporarily hidden — recorded on old Portal version" (inside an HTML comment, lowest priority)
• Typo missed: dapp-staking/code-of-conduct.md line 30: "Includinf Game" should be "Including Game". PR fixed several typos in nearby sections but missed this one.
• "dApp Staking V3" references retained in 4 files: dapp-staking.md (FAQ), for-stakers/index.md, for-devs/index.md, code-of-conduct.md. Decide whether to drop V3 nomenclature now that Tokenomics 3.0 / the revamp is the current state, or keep "V3" as historical context. Currently inconsistent across /docs/use/.
• Filename / URL slug: the page is now ACC Strategic Staking Program but the file is still unstoppable-community-grant-program.md. Worth a deliberate decision: rename (with a redirect for legacy links) or document that the slug is kept intentionally for backlink continuity.