Most wallet losses start with a request nobody read. An app asks you to sign, the wallet shows a contract address and a list of raw numbers, and you approve because the app looked fine. Keon reads the request for you first.
Every transaction is run first
Before the approval screen appears, Keon sends the transaction to Starknet as a simulation. Nothing is signed and nothing is spent. The network replies with what would happen, and Keon turns that into plain words:
- Balances. What leaves your wallet and what arrives, in tokens and in dollars.
- Approvals. Any app getting the right to spend your tokens, and whether that right is unlimited.
- Failures. A transaction that would fail is stopped before you pay a fee for it.
- Fee. The fee you will actually pay, not the inflated maximum.
When something looks wrong
Some requests deserve a second look. Keon flags unlimited spending approvals, sites on known scam lists, and transactions the simulation says would fail. When it does, the Approve button turns red. You can still go ahead, but it takes a second, deliberate step.
Apps only get what you allow
Connecting an app shows it your address and nothing else. Sending transactions, signing messages, switching networks and adding tokens are separate permissions you choose when it connects. Session keys can approve small, routine actions for a few minutes, only on contracts you pick and up to a spending cap you set.
Read more on the Security page, or get Keon for your browser or phone.