Web3 transaction security firewall
Know what you're signing.
Nalar reads your intent, simulates the transaction, inspects on-chain evidence, and stops dangerous requests before your wallet signs.
Swap 0.001 tBNB to NDEMO
Risk changes as evidence is read.
Signing a transaction shouldn't mean trusting what you cannot see.
A wallet can show a destination and a value. It cannot explain the full contract behavior behind a request. Nalar makes the hidden parts legible before the signature prompt.
A spender receives permission that the prompt never explained.
Calldata points to an unknown execution path.
A contract exposes a configured value that changes the trade risk.
The address receiving control is not the address you intended.
The request succeeds in a way the human description did not predict.
Five steps between intent and signature.
Each step produces a traceable input for the next. The final state is deterministic, the explanation is readable.
Intent
A human instruction becomes the reference point.
Decode
Calldata becomes an action, target, and set of effects.
Simulate
The request is tested before a wallet signature exists.
Investigate
Contract capabilities and on-chain state add evidence.
Decide
Policy produces ALLOW, REVIEW, or BLOCK with reasons.
Every signal has a job.
Nalar combines transaction mechanics with contract and chain evidence. Nothing in the interface is a mystery score without a source.
Intent matching
Compares the request with what the user described.
Transaction simulation
Checks whether the execution path behaves as expected.
Contract capabilities
Maps mint, tax, pause, upgrade, and access functions.
On-chain state
Reads configured values such as tax, owner, and limits.
BNB MCP evidence
Enriches the investigation with read-only BNB observations.
Scam intelligence
Combines sellability and token findings into context.
The verdict is clear because the evidence is visible.
Select a state to see how the decision changes with the evidence. The engine produces the state, then Nalar explains it in plain language.
The request needs a human decision.
Evidence is incomplete or the transaction contains a material uncertainty.
MCP enriches the evidence. The engine makes the call.
BNB MCP provides read-only observations from the chain. It does not decide whether a user should sign.
Nalar lives between the dApp and the signature.
The extension intercepts transaction requests, captures intent, and opens the analysis before the wallet confirmation takes over.
Load the extensionA firewall is a path, not a pop-up.
Each handoff is explicit, so the decision can be inspected from request to wallet.