Questions

The ones people ask before they deploy.

Questions

Does my private key ever reach your server?

No. There is no code path for it. Deploys and calls are signed inside your wallet and sent by it; the site only sees the transaction hash the wallet returns. The public guard fails the build if a private key or a local signer appears anywhere in the site or the package.

Which wallets work?

Any wallet that announces itself with EIP-6963 or injects window.ethereum: MetaMask, Rabby, Coinbase Wallet, Brave and the rest. Hardware wallets work through the wallet that drives them.

Why testnets first?

Because the first deploy of a contract should not cost real money. The chain list leads with Sepolia, Base Sepolia, Polygon Amoy, Optimism Sepolia and Arbitrum Sepolia, each with a faucet. Mainnets are there, marked real money, behind a typed confirmation.

What does community mean on a template?

That it was written for this library, compiles and passes the tests on every build, and has not been independently audited. Nothing here is labelled reviewed, because nothing has been.

How does verify work without a block explorer?

Your source is compiled with the settings you give, the runtime bytecode is fetched from the chain's public RPC, the metadata hash is stripped from both, and they are compared. It answers whether that source produced that contract, and whether the match was exact.

How is this different from Remix?

Remix is the reference and it is excellent. This is a smaller, opinionated version built on the Leumas kits: one pinned compiler, a wallet layer that never asks for a key, a library with honest labels, verification by bytecode, and workspaces in your Leumas account. If you need every Remix plugin, use Remix.