Troubleshooting

Check that you are using the intended email or X account. An exhausted or invalid invitation cannot admit a new member. A temporary membership service error is different from a rejected invitation; wait and retry rather than creating more accounts.

If X returns “not allowed,” the provider configuration may be unavailable. Try the enabled email route, and verify the resulting wallet address before funding. Never send a secret or login code to someone offering support.

Save the transaction hash and check it on the Ink explorer. A page refresh does not cancel a transaction. A submitted launch must be recovered by its receipt before another launch is attempted.

If no hash was returned after wallet submission, inspect wallet activity before resubmitting. A failed onchain transaction can cost gas even when the token transfer or deployment reverted.

Activation is not required for reveal. Check the collection’s ETH reveal reserve, whether its request is queued, and whether the oracle has returned a result. The delivery worker may need to retry.

Do not burn tokens just to reveal artwork. Funding or retrying a queued reveal uses the existing collection process, not a new collection deployment or an arbitrary replacement random result.

Confirm that the connected wallet is the fixed executor, accrued fee credit covers the spend, and the amount reaches the threshold. Direct WETH deposits are excluded from the budget. Check that trading is open and the review has not expired.

If slippage or price movement caused a revert, refresh the quote and assess price impact. If a recipient transfer exceeds the NFT synchronization bound, reduce the spend where it still meets the threshold. Do not blindly remove minimum-output protection.

Membership does not imply creator approval. Confirm the current wallet is allowlisted and funded for Ink gas. Check the artwork folder, supply, token-per-NFT unit, fee cap and any buyback settings.

Refresh a stale USD conversion and review again. If a deployment is already submitted, use transaction recovery. If release checks report a factory or hook version mismatch, do not bypass the check or send a manually altered transaction.