Source Signer / Support
Diagnose without exposing secrets
SafeExit support only needs public incident evidence. Wallet credentials and signed authorizations must remain private.
01
Before reporting a problem
Confirm that Chrome is version 127 or newer, the active tab is on safeexit.xyz, the incident is still valid, and the selected network is X Layer mainnet.
If the extension reports an expired request, discard it and prepare a fresh signing package from the incident page. Never reuse an expired authorization.
02
Safe details to include
Include the Source Signer version, Chrome version, incident ID, public wallet addresses, public transaction hash, the exact visible error message, and a screenshot with unrelated personal information removed.
For an installed Store version, use the Support option on the SafeExit Source Signer Chrome Web Store listing to contact the publisher.
03
Never send wallet secrets
Never send a seed phrase, private key, keystore, password, raw signed authorization, or recovery code to SafeExit support, a marketplace agent, a website, or another person.
The SafeExit website never requests a source private key. During an EIP-7702 rescue, the key is entered only inside the separately installed Source Signer popup for one local signing session.
04
Security and limitations
Stop immediately if the displayed source, destination, chain, delegate, action commitment, or expiry does not match the incident you initiated.
Wallet recovery is best effort. Another party controlling the same source key may race, invalidate, or front-run a rescue before confirmation.