Each project binds its wallets to the engine it is running on. When the engine is provided by a third party, it always involves a certain risk. We understand this point and want to ensure the full safety of your funds.
If the project doesn’t work correctly, you can see it at the testing stage and solve the issue. But, regarding the security of funds, it won’t work out that way. The administrator should be sure that everything will be fine with the project funds. Please read the brief instructions for securing the project:
- Perhaps this is obvious, but it’s better to remind you that you should never keep large amounts of money in the project’s e-wallets. As soon as the cashflow is more stable, it is best to move up to 90% of the funds to the wallets, to which only you have access, and leave only the funds necessary for payouts. If needed, you can always return some funds to the project wallets.
- Since the script has the ability to send API requests and partially manage the project wallets, the best solution to ensure security against unforeseen «hijackings» is to disable the API for almost the entire lifetime of the project. Enable API only while making the payments, for example, turn in on for 5 minutes at 18:00 every day, in order to process the payouts, and re-disable the access afterwards. This method guarantees the security of funds in 99% of cases. If the project offers instant payments, this option is not suitable for you. In this case, just store small amounts on the wallets.
- In case you notice a strange activity in the project, such as: unusual logs, thousands of attempts to create a deposit or withdraw funds from the same IP, — always immediately report this information to our customer support. Our security specialists will always react as quickly as possible to any threat and, if necessary, protect your project from potential intruders.
Always keep your eyes open!