Skip to content
Discussion options

You must be logged in to vote

Update: Resolved!

Phantom support (William) identified the issue — our signing order was incorrect. The sponsor (fee payer) was signing before the user wallet. We reversed it:

  1. Server builds unsigned tx
  2. Phantom signs first via signTransaction()
  3. Server adds sponsor partialSign() and submits

The warning is now gone. Deposits working cleanly on mainnet.

Thanks to Phantom support for the quick and clear guidance. This should help other devs using the sponsor-pays-gas pattern.

For assistance resolving this issue, follow the guide here. https://docs.phantom.com/developer-powertools/domain-and-transaction-warnings

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by Th3Ya0vi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant