-
Notifications
You must be signed in to change notification settings - Fork 214
Token Wizard Refund Policy
POA Network will refund failed attempts at creating crowdsales with Token Wizard if your case follows the policy below.
Failed attempts for deploying Crowdsales on Main Networks will be refunded to the matching owners address, but must follow some guidelines. Future attempts at creating crowdsales on Token Wizard should include Screen Shot of the Developer's Console during deployment of the error presented. Please complete the requirements below to submit refund request.
Refund may take up to 3 days to process.
If your deployment on Main Network fails, do not try again without trying to resolve the issue.
-
Any complaints must be made by opening "New Issue" on the Wizard's github repository.
-
Crowdsale has to be deployed on Main Networks only. Ethereum, POA, etc.
-
Refunds will only be sent to the crowdsale owners address. You must claim your own refund.
-
Needs approval from team member, @igorbarinov
-
"New Issue" should include owners address used to deploy.
-
"New Issue" should include total amount of funds lost in ETH.
-
Screen Shot of MetaMask Transaction History showing failures and/or Dev console error log must be included with "New Issue".
-
Must work with team member to re-create the current issue best as possible to solve bugs.
There will be no refunds for crowdsales that have deployed correctly or canceled at the users request. All refund requests will be verified on Etherscan or the corresponding block explorer.
-
More than 3 deployment attempts, you shouldn't be attempting more than once with errors present. Take a Screen Shot of your current error, submit an issue and wait for bug fix.
-
Crowdsales on Test Networks.
-
Crowdsales that were halted due to user rejecting transactions.
-
If you cannot provide the correct information for the Github Issue.
-
To a different multi-sig address.
-
Transactions running out of gas due to user selection. Use the appropriate 'Gas' settings for the speed you want, refunds will not be provided if 'Custom Gas' was too low.
-
Accidentally closing browser or tab. Future releases will avoid losing all information.
-
Accidentally refreshing browser window, refreshing will void your current crowdsale deployment. Future releases will avoid losing all information.
-
Any user made typo with contract creation, always double check your inputs.
-
If user forgets to 'Download' the source code compressed file on 'Step 4'.
-
Try closing all browser windows and clear browser cache if you have tried deploying on multiple networks.
-
Good idea to have javascript dev console open during deployment.
-
In case of failure, take screen shots of dev console error log to submit with issue.
-
Sometimes MetaMask will label a transaction as failed, verify with Etherscan to see if transaction was successful.
-
Token Wizard has built in
GAS Price Oracle
on 'Step 3', choose the network speed you would like to pay for. -
Use POA Network to deploy your crowdsale as it is cheaper and much faster.
- Introduction
- Demo
- Requirements
- Strategy
- How to run
- Using POA Networks
- Deployment Time & Gas
- Verifying Smart-Contracts
- Possible Tx Failures
- Token Wizard Projects
- Notable Contributors
- Support
- Disclaimer
- FAQ
- Change Start & End Times
- Change max cap for tier
- Change rate
- Distribute reserved tokens
- Finalize crowdsale