Skip to content

Risk Assessment: GhoRouter (when deployed) #194

@spalen0

Description

@spalen0

Context

PR #124 shipped the sGho risk assessment after AIP 484 ("sGho Launch") executed on 2026-05-16. The AIP deployed sGho (0xE1753F…ca1d) and sGhoSteward (0x60Bf2D…2757) but did not deploy a GhoRouter.

The router is referenced only in the AIP's marketing copy ("Users can go from USDC to sGHO in a single transaction"). The actual payload deploys no router. As a result Yearn's USDC → sGho strategy currently has to compose the GSM USDC and sGho deposit steps manually.

The aave-dao/gho-origin PR #34 is the only public router draft and is not part of AIP 484, not present in the Aave Address Book, and out of scope of the TokenLogic Collaborative audit. Issue #145 (closed by PR #124) tracked the post-AIP-484 finalization and is fulfilled; this new issue narrowly tracks the router.

Trigger

Reopen / start work when any of the following becomes true:

TODOs once the router is deployed

Source: reports/report/aave-sgho.md

  • Fill the GhoRouter row in the sGho Contracts address table (currently "Not deployed — not part of AIP 484")
  • Audit the deployed router's owner / admin powers (setGsmAllowed, rescueToken, pause behavior)
  • Confirm router has no persistent token balances or stranded approvals during normal flow
  • Verify Yearn USDC strategy can route USDC → sGho in one tx and the reverse path works under GSM freeze conditions
  • Re-check Aave Immunefi scope: is GhoRouter enumerated?
  • Update the sGho Strategy pipeline and Liquidity Risk sections to reflect the new path
  • Re-score the assessment if the router changes the admin/liquidity surface (currently 2.1 / 5.0)

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions