Troubleshooting

Wallet remains disconnected#

• Confirm the StarKey extension is installed and unlocked.
• Reload after installation so the provider can inject.
• Approve the account connection in the extension.
• Disconnect/reconnect if the account changed while the tab was open.

Wrong network#

Trust Stack requires Supra MoveVM Testnet chain ID 6. When the header shows Wrong network, open it and select Switch network, then approve the change in StarKey. If the wallet reports another chain after switching, reject any signature and reconnect.

A wallet request was declined#

The dApp shows "You declined the request in StarKey." and submits nothing. Select the same action again to reopen StarKey; the reviewed request does not need to be edited before it can be signed.

Token details cannot be verified#

• Use the Fungible Asset metadata object address, not a primary store or transaction hash.
• Confirm the asset exists on testnet and uses the supported standard.
• Check RPC availability and retry the read.
• A dispatchable asset is intentionally unsupported in custody/distribution flows that reject hooks.

A position does not appear#

The indexer may lag behind the chain. Confirm the finalized transaction and emitted object address in SupraScan, then use the direct management page. Current Move state remains authoritative even when the indexed list is delayed.

A claim button is disabled#

Check all of these conditions:

• connected address equals the immutable beneficiary or staker (the button reads Connect wallet or Switch to Supra Testnet until the wallet is ready);
• chain ID is 6;
• unlock/start/end/reclaim time has reached the required boundary;
• the position has not already reached a terminal state;
• something positive is currently claimable;
• the vault still owns or contains the expected asset.

A transaction hash exists but the app reports failure#

Do not immediately resubmit. The wallet may have submitted successfully while receipt polling or event reconciliation failed. Open the hash in SupraScan, identify the emitted object, and read its current state. Retry only when the first transaction is known not to have moved value.

Digital Asset upload fails#

• Keep the file at or below 5 MiB, the API upload limit. The create form currently accepts larger files, but the upload service rejects them.
• Use PNG, JPEG, GIF, WebP, GLB v2, or valid glTF JSON.
• Prefer a self-contained GLB if the model needs external buffers/textures.
• Confirm media uploads are enabled and the public base URL is configured.
• Localhost media URLs are not suitable for shared testnet wallet/explorer verification.

A governance proposal expired#

On revision 6 a matured fee schedule, role change, renunciation, asset admission, or council rotation must execute within 14 days of its effective time. After that it aborts with EPROPOSAL_EXPIRED (fee_config code 23, asset_policy code 20). The fee configuration console labels such a schedule Pending fee schedule expired; the governor can cancel it or propose a replacement.

Local service health#

Check the frontends directly, then query /healthz and /readyz on the API. A healthy process with an unready database should not be treated as a fully available indexed stack.

Reporting a security issue#

Do not include seed phrases, private keys, full payroll lists, or partner secrets. Provide the chain, package/module, transaction hash, object address, expected invariant, observed state, and minimal reproduction using testnet-only accounts.