Skip to content
Zyper Docs Beta

Zyper Capture extension

Zyper Capture is a Chrome extension that watches the dapp you’re browsing, records the contract calls it makes, and lets you fire those same calls in Zyper AIO with one click via the zyper-v1:// deep-link protocol.

Install

  1. In Zyper AIO, open Settings → Zyper Capture → Download extension. You’ll get a ZIP.
  2. Unzip somewhere persistent (e.g., C:\Zyper\extension\).
  3. In Chrome, go to chrome://extensions.
  4. Toggle Developer mode on (top right).
  5. Click Load unpacked and point at the unzipped folder.

The extension shows a small chip in your address bar. Click it to see what calls it has captured on the current page.

How it works

While you browse a mint site or dapp:

  • The extension hooks window.ethereum.request and watches for eth_sendTransaction and eth_signTypedData_v4.
  • For each capture, it records the to, data, value, and chain ID.
  • The popup lists captures with timestamps. Click any one to fire a deep-link.

Clicking Open in Zyper in the popup hits:

zyper-v1://capture?chain=8453&to=0x...&data=0x...&value=...

Windows routes the URL to your registered zyper-aio.exe. The desktop app:

  1. Checks if it’s already running (Win32 named mutex).
  2. If running: hands off the URL to the existing instance, which opens the Tasks page pre-filled with the captured call.
  3. If not running: launches, waits for the renderer to mount, then opens the pre-filled dialog.

When it’s most useful

  • A new mint launches on a site without a published module.
  • You want to capture the exact mint() calldata from a successful test mint on web, then fan it out across many wallets in the desktop.
  • An allowlist-gated mint signs your wallet for the right to mint — the extension captures the signed payload so you can replay it across burners.

What it doesn’t do

  • It doesn’t sign anything. It only watches.
  • It doesn’t bypass wallet approval prompts in the browser. The web mint still goes through your browser wallet as normal; the extension just records what happened.
  • It doesn’t auto-load contract ABIs. Zyper AIO does that via Sourcify when the pre-filled Build Task dialog opens.

Privacy

The extension is fully local — no telemetry, no remote calls. It only talks to your machine via the zyper-v1:// URL scheme.

The Zyper Capture extension is shipped as a public artifact alongside the desktop binary. Both are Ed25519-signed; the desktop verifies the signature of any update it pulls from R2.

Troubleshooting

  • “Click Open in Zyper, nothing happens” — Windows may not have registered the zyper-v1:// protocol yet. Launch zyper-aio.exe once manually; it registers the protocol on first run.
  • “Two windows opened” — the single-instance gate is a Win32 named mutex with a ~500ms poll interval. If you clicked twice rapidly during cold-start, both may appear briefly; the duplicate exits quickly.
  • “Pre-fill is missing fields” — the extension can only capture what the dapp actually called. If the mint sent extra args via data that aren’t in a verified ABI, Sourcify lookup may not resolve them. Paste the ABI manually in the Build Task dialog.