Questions, answered plainly.

Who pays for the gas?#

The paymaster's EntryPoint deposit, refilled from its treasury at each epoch with a capped budget. The operator funds the treasury, and anyone can add to it with fund(). You never pay per transaction, and a failed op never costs you ETH.

Is this a mixer?#

No. The paymaster pays gas for one UserOperation at a time. It never holds, pools or moves your tokens, and it doesn't hide where tokens came from. It removes one specific link: the ETH top-up a fresh address would otherwise need.

Will it cook my CPU?#

Mining runs in Web Workers at the thread count you pick (Gentle uses one core), stops at the eighth valid hash and never runs in the background. A typical op takes seconds on a laptop. You can stop it at any time; nothing is sent until the proof is done.

Why did it take longer than expected?#

Every hash has the same odds, so mining has no memory: being unlucky for a while doesn't make the next hash likelier. With 8 sub-solutions the 95th percentile is about 1.64 × the average. Past three times the average, something else is wrong: try more threads, or wait for the next epoch if difficulty just rose.

Why "waiting for the next epoch"?#

Before mining, the SDK checks that the proof can be mined and submitted before the relay stops accepting the current epoch, and that the deposit has room for the op. If not, it waits for the next roll (epochs last 15 minutes) instead of wasting your work.

Can someone steal my proof?#

No. The proof is bound to your op's hash, which includes your address, the EntryPoint nonce and the paymaster. It only works once, for that op, and your account's signature is still required.

Can a GPU farm drain it?#

It can use up an epoch's budget quickly: proof of work is a rate limiter, not economic security. The budget bounds the loss (one top-up per epoch and an immutable daily cap), and honest users wait for the next epoch. This is why the budget stays small.

Why EIP-7702 and not a smart-contract wallet?#

A 7702-delegated EOA keeps the same address as the key, needs no deployment transaction, and the bundler applies the delegation in its own type-4 transaction. The paymaster checks on-chain that the sender uses Simple7702Account v0.9, so every account behaves the same.

Which bundler can I use?#

Only the relay's. Co-signed ops are bundled by the relay's own bundler so the deposit ledger stays exact; see Run your own relay.

Do I need an API key?#

No. The relay URL is the only setting. The relay rate-limits reads per connection in memory; sends are protected by the proof itself.

What can the operator see?#

Your IP address, your ops and when you sent them. Not your key: it never leaves your tab. See the privacy guide for how to reduce the rest.

Is it on mainnet?#

Yes, since September 30, 2026, with a small, capped budget: the PowPaymaster is 0x4E77B4AF15b55E4FB354e92078D46f39Ca659375 on Robinhood Chain (chain 4663). The testnet deployment keeps the demo tokens and faucet. Unlinked is an independent project and is not affiliated with Robinhood Markets, Inc.