Notice for Ghostwriting Strategies on FMZ

Looking for someone to ghostwrite a strategy is a personal behavior, and FMZ official will not intervene in the disputes of that, so users need to be cautious. This area will regularly clean up the comparatively old posts, which can be re-posted if there is still demand.

For Demand Posters

• 1. First, check whether the public strategies in the “Strategy” square meet the requirements. The public strategies have been accumulated over years, and the basic strategies can be included in them.
• 2. Understand your own needs and write detailed documents about your demands, which can save time for you and developers to communicate.
• 3. According to the complexity of a strategy and the level of the strategy developer of the strategy, the price will fluctuate greatly. If you can not accept the price, you can change to another developer directly.
• 4. You can post in the Forums, or ask questions in the communication group, so you can also get quick responses.
• 5. The way to verify the developer’s level: You can click on his profile page to see his registration time, the number of his public strategies, whether there is a public running bot, posting status, etc.; be vigilant about new accounts without information; try to choose developers who provide as many public strategies as possible, and whose strategies are copied as many times as possible.
• 6. The payment method can be payment by installments, and all the requirements shall be met before paying the balance.
• 7. It is best that you can read and understand the source codes of strategies.
• 8. Do not disclose your FMZ account password and the platform API KEY.
• 9. It is normal that the backtest and bot results of the strategy you assumed may not meet your expectations.

For Strategy Developers

• 1.Make as many public strategies and posts as possible to communicate, and show your programming strength and understanding of strategies.
• 2. Before writing a strategy, it is necessary to have a good communication with the demander about the strategy, including the payment method, the result achieved and the future maintenance, etc., to avoid disputes in the future.
• 3. Reasonable charges.
• 4. For the codes, developers shall fully consider the fault tolerance, extreme situations, etc., to avoid hidden bot traps.
• 5. Finally, provide clear and annotated source codes, which is convenient for strategy users to maintain and upgrade by themselves.