Skip to content

Fix WolfPack(GGWP) external token name: WP, not GGWP#928

Merged
Franziska-Mueller merged 1 commit into
qubic:developfrom
MZoxx:fix/ggwp-wp-asset-name
Jun 17, 2026
Merged

Fix WolfPack(GGWP) external token name: WP, not GGWP#928
Franziska-Mueller merged 1 commit into
qubic:developfrom
MZoxx:fix/ggwp-wp-asset-name

Conversation

@MZoxx

@MZoxx MZoxx commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

wpToken.assetName reused WOLFPACK_SC_ASSET_NAME ("GGWP" - the contract's own 676 IPO/SC shares, issuer NULL_ID) for the external staking token. The token issued on QX by MLMWPS... is actually named "WP", so Stake(), releaseShares (finalize/claim), DepositStakingRewards and the BEGIN_EPOCH holder snapshot all queried a non-existent asset and would fail or no-op.

Add WOLFPACK_WP_ASSET_NAME = 20567ULL ("WP") and use it for wpToken.assetName. SC-share governance (numberOfShares({NULL_ID, WOLFPACK_SC_ASSET_NAME})) is unchanged.

wpToken.assetName reused WOLFPACK_SC_ASSET_NAME ("GGWP" - the contract's own
676 IPO/SC shares, issuer NULL_ID) for the external staking token. The token
issued on QX by MLMWPS... is actually named "WP", so Stake(), releaseShares
(finalize/claim), DepositStakingRewards and the BEGIN_EPOCH holder snapshot all
queried a non-existent asset and would fail or no-op.

Add WOLFPACK_WP_ASSET_NAME = 20567ULL ("WP") and use it for wpToken.assetName.
SC-share governance (numberOfShares({NULL_ID, WOLFPACK_SC_ASSET_NAME})) is unchanged.
@Franziska-Mueller Franziska-Mueller merged commit b58c4c5 into qubic:develop Jun 17, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants