Still blocked after #531 fix: claimsol.solhousesignal.com batch requests return RELIABLE_SIMULATION_NOT_POSSIBLE

[SimuZSkyNeT]

Hi @CCristi, thanks for the quick fix on #531. Unfortunately it does not work for our domain yet, and since that discussion was closed I'm opening a new one so it doesn't get lost.

What we see (tested every 15 minutes since the fix, last check 16:06 UTC today):

• Phantom extension 26.32 and 26.33
• a request with 2 simple transactions (signAndSendAllTransactions) from https://claimsol.solhousesignal.com is shown as "Request blocked - This dApp could be malicious"
• the simulation API still returns block.kind = RELIABLE_SIMULATION_NOT_POSSIBLE for our domain
• the exact same request from jup.ag shows a normal Confirm screen
• single-transaction requests from our domain show a clean Confirm

Our transaction code is public and matches production: https://github.com/SimuZSkyNeT/claimsol-tx

Could you check claimsol.solhousesignal.com specifically? Is there a cache on domain reputation that needs to expire, or something else we should change on our side? Happy to provide any detail or run any test you need.

Thanks!

[beenish-majeed]

The key clue is that single transactions work on your domain, but a two-transaction batch fails. This points more strongly to Phantom’s batch-simulation path or a domain-specific security decision than to a simple reputation-cache issue.

Phantom’s [official documentation](https://docs.phantom.com/developer-powertools/domain-and-transaction-warnings) confirms that this warning appears when a transaction cannot be reliably simulated.

Please simulate both transactions individually with sigVerify: false and verify their results, signer counts, and serialized sizes. If both pass individually but the batch still returns RELIABLE_SIMULATION_NOT_POSSIBLE on extensions 26.32 and 26.33, this needs Phantom-side investigation of the batch simulation decision for claimsol.solhousesignal.com and the #531 fix. If necessary, submit the case through Phantom’s domain review process. Repeated polling is unlikely to fix a deterministic simulation failure.

[SimuZSkyNeT]

@Th3Ya0vi @CCristi this looks like the same issue as #520 (app.xroot.dev, ticket 359878 open since Sep 4): another rent-reclaim tool where any request with 2+ transactions is blocked with RELIABLE_SIMULATION_NOT_POSSIBLE, while single transactions pass. Since two unrelated domains of the same kind hit it, it may be a rule in the batch simulation path rather than something domain-specific. Could you take a look at both? Happy to test any change right away.

[Th3Ya0vi]

Thanks for reaching out. Please contact our support team at help.phantom.com, where someone from our Trust & Safety team can assist with reviewing the warning. You can also follow our Domain and transaction warnings guide for guidance and next steps.