Keys remain in your wallet
No seed phrase, private key, recovery phrase, password, or secret is ever requested or stored.
Security model
Non-custodialVerify first. Sign last.
The application minimizes authority, keeps destructive actions deliberate, and never treats wallet connection as transaction consent.
Read and write paths are separate
Public analysis cannot silently escalate into a wallet signature request.
Exact calls remain visible
Network, contract, function, parameters, recipient, value, and fees are shown before signing.
User-controlled transactions
Every write requires explicit wallet confirmation and verified transaction details.
What the interface defends against
- Hidden recipients or substituted burn addresses
- Signatures requested before transaction review
- Unknown metadata presented as a safety verdict
- Illustrative data presented as live chain activity
- Mainnet writes enabled accidentally
- Wallet addresses sent to analytics without consent
Known limitations
Token metadata can be incomplete or manipulated. RPC simulation cannot guarantee inclusion or final execution. A contract can change behavior through proxies. Users must independently verify contracts and wallet prompts.
Before every transaction
- Verify the exact domain and TLS connection.
- Confirm the selected chain is a supported EVM network.
- Compare the contract address with a trusted source.
- Read the method name, parameters, recipient, and value.
- Confirm network gas and any separately disclosed service fee.
- Reject the request if your wallet shows different data.
EVM Incinerator will never contact you privately to request credentials or ask you to “validate” a wallet.
Responsible disclosure
Report a security issue privately.
Do not include private keys, seed phrases, real user data, or active exploit details in a public issue.