GMEngineHow AutoDeploy Works
What AutoDeploy does, how it differs from Manual Deploy, and how it is seen on-chain.
What is AutoDeploy?
AutoDeploy deploys simple smart contracts on your behalf on a schedule, without you sending transactions every time. It creates regular on-chain deploy activity, reduces manual effort, and you avoid repeated gas payments.
When does the daily run happen?
The relayer runs once per UTC day at a random time within the first three hours (00:00–03:00 UTC). So your deploy may happen at a different time each day; the exact time is not fixed. This variation makes activity look more organic and not scripted.
Manual Deploy vs AutoDeploy
Manual Deploy
- You send a transaction directly from your wallet (EOA)
- You pay gas
- The contract is deployed by your address
- The deploy appears in your wallet's transaction history
AutoDeploy
- A relayer sends the transaction; the service pays gas
- The deployed contract records you as the owner and emits events linked to your address
- Your wallet does not send the transaction
Both result in real on-chain contract deployments — they are just executed differently.
Is the contract deployed "from my address"?
No. With AutoDeploy the transaction sender (tx.from) is the relayer; the contract is not deployed from your EOA. However: the deployed contract records your address as the owner, the deploy is attributed to you via on-chain state and events, and deploy statistics and streaks are tracked for your address. This is a standard relayed deployment pattern.
What does the deployed contract look like?
AutoDeploy uses a minimal smart contract: it stores owner (your wallet) and deployedAt (timestamp). No hidden logic, no external permissions.
Will AutoDeploy show up in my wallet's transaction list?
No. The transaction is sent by a relayer, so it won't appear in your "sent transactions." You can still verify AutoDeploy by viewing DeployFactory contract events, checking deployed contract ownership, and reading on-chain deploy statistics.
Is AutoDeploy considered real on-chain activity?
Yes. AutoDeploy results in a real smart contract deployed on-chain, permanent bytecode, on-chain events linking the deployment to your address, and publicly queryable deploy counts and streaks. Nothing is simulated or off-chain.
Will AutoDeploy count for airdrops?
Sometimes — but not always. It depends on how a project defines eligibility. Airdrops that require EOA deployments usually don't count AutoDeploy; those that look at deployed contracts, ownership, and events may count it. For maximum compatibility, use Manual Deploy.
Extending your subscription
To extend AutoDeploy, use the form on the platform: sign a new authorization and pay for additional days. If you call purchaseAutoDeploy() directly (e.g. via Etherscan) without re-registering, the on-chain subscription extends but your signature's deadline does not — the relayer cannot relay after the old deadline. Always re-subscribe through the app when extending.
Is AutoDeploy safe? Can I combine it with Manual Deploy?
Yes. No private keys are shared; authorization is via EIP-712 signed messages. You can stop AutoDeploy at any time; all logic is enforced on-chain. You can combine Manual Deploy (for important interactions) with AutoDeploy (for consistent background activity) — both contribute to your on-chain footprint.
Summary
AutoDeploy uses relayed transactions. Contracts are not deployed from your EOA; ownership and activity are attributed to your address. Deploys are real and verifiable on-chain. Some airdrops may count them, others may not. AutoDeploy is about automation and consistency, not guarantees.