Chainvara
dApp & transaction security

See what a transaction really does before you sign it

Connect vault wallets to dApps with WalletConnect. Each request is decoded and simulated first: token approvals, permits, marketplace orders and blind signatures are flagged, and requests that could hand over your assets are blocked.

app.example-dex.xyzWalletConnect
approve(0x9f3c…e21, 2²⁵⁶−1)

Unlimited USDC allowance

0x9f3c…e21 could move every USDC in this wallet, now or later.

Simulated balance change0 USDC now
ApproveBlocked

Controls you can prove

Simulation

Balance changes are simulated before signing; outflows are valued and checked against your policy.

Decoders

Unlimited approvals, setApprovalForAll, Permit and Permit2, Seaport orders and wrong-chain requests are recognized.

Blind signatures blocked

Raw hash signing requests are refused: they can authorize anything.

Always approved by a person

Message signatures always need at least one approval.

How it works

  1. 1

    Connect

    Scan the dApp's WalletConnect code in the console.

  2. 2

    Review

    See the decoded intent, simulated balance changes and risk findings.

  3. 3

    Approve or refuse

    Approvers decide; critical findings are refused outright.

Works best with

Ready to see Chainvara in action?

Start free on test networks. Move to production when your controls are in place.