Creating New Contracts

This page provides a guide for deploying new contracts through OmniDeploy.

1. In order to create a new contract for deployment on Ethereum please first select 'Create Contract'.

1. Select the network you would like to deploy on. Currently OmniDeploy only supports Ethereum Mainnet deployments and Ethereum Testnet deployments on Sepolia.

1. Select whether you would like OmniDeploy to generate a new wallet for this deployment or use an existing wallet that was previously created by the bot. PLEASE NOTE: OmniDeploy does not currently support the ability to import your own wallets, therefore any newly created wallets would have to be funded with ETH in order to pay for gas and also call functions.

1. When creating a new wallet OmniDeploy gives you an opportunity to view and note the private key for this wallet. It does this through means of a self destructing message and temporary pop up box. Feel free to bypass viewing your private key at this moment by pressing 'Cancel' which will prompt the bot to continue the deployment process. Private Keys can be viewed later by using the 'View Private Keys' option from the Main Menu.

1. OmniDeploy will then share a form to allow you to define the deployment parameters. Currently OmniDeploy provides a basic but versatile contract template which accommodates for the majority of contract requirements. This allows users to...

• Define Token Name and Ticker

• Define Total Supply

• Define the supply reserved for the Team (up to a maximum of 9% of Total Supply)

• Define Buy and Sell Tax (up to a maximum of 10%)

• Set Tax Wallet

• Set Max Buy

PLEASE NOTE: There are limitations on certain contract parameters that have been put in place by OmniDeploy in order to reduce the risk of entities utilising the platform for malicious endeavours.

• Team supply is limited to 9%. All remaining tokens can only be minted when the user adds liquidity.

• Tax is limited to 10%.

• OmniDeploy takes 1% of total supply for the OmniBot treasury as a fee for using the platform. This means a minimum of 90% of supply is always allocated to the liquidity pool.

• OmniDeploy takes 10% of total taxes for the OmniBot treasury as a fee for using the platform. For example if the user sets taxes to 5% - 0.5% would be allocated for the OmniBot Treasury.

1. Once you complete the deployment form a final confirmation message with all inputted parameters is displayed. Please double check through this to ensure you are satisfied with the data. Fell free to edit any information by using the 'Edit' button at his point if required.

1. The deployment request is then sent to the Ethereum Network. If successful a link to view the contract on Etherscan is provided and a number of additional follow up actions. It would be common at this point to 'Add Liquidity' to create a Uniswap V2 Liquidity Pair for your tokens and 'Enable Trading' to allow users to trade the token. However, you can also carry out these actions at a later stage using 'Manage Contract' from the Main menu. For more information on managing contracts post deployment please see the 'Managing Existing Contracts' section here. PLEASE NOTE: It is possible for deployment to fail, however currently OmniDeploy is not able to provide an exact reason for failure. This will most likely be due to a lack of funds in the users wallet, but could also occur for a number of other reasons such as network congestion etc. If you are having continued failure without being able to identify a cause please contact a member of the team through the OmniBot TG group.

1. Congratulations! You have successfully deployed a smart token contract on the Ethereum Network without having to write a single line of code and with minimal to zero upfront expense (other than gas fees).