GM/Deploy

GM sends a lightweight onchain interaction to the selected network so the connected wallet has a verifiable transaction record.

Deploy directly creates a minimal empty contract from the connected wallet. The wallet is the onchain contract creator. It does not issue a token, create a collection or request access to wallet assets. No factory contract is required for this direct deployment.

Mainnet and Testnet are separate tabs. A network appears in Testnet only after it is added separately and explicitly marked as a test network.

Fee-enabled Deploy actions on the original supported mainnets may send the public wallet address, network, transaction hash and deployed contract address to the deployment analytics endpoint. Fee-free direct Deploy actions on the newly added networks are not submitted to that endpoint. Salted one-way hashes of the connection IP and browser user-agent may be retained for abuse prevention where analytics is enabled. GM actions are not recorded in this deployment database, and the full IP is not stored by this feature. Privacy Policy.

Base, OP Mainnet, Arbitrum One, Polygon, Unichain and Robinhood Chain keep the existing symbolic 0.00005 native-token service fee sent to their public CoinBlogFeeVault. The newly added mainnets use a fee-free direct deployment: the wallet pays only that network's gas and no amount is sent to a FeeVault. View the Unichain CoinBlogFeeVault example.

No. The transaction does not call approve, permit, setApprovalForAll or transferFrom, does not request a message signature and does not receive access to tokens or NFTs. The wallet signs only a direct contract deployment, with a visible service fee where applicable, plus network gas.