JSON export/import of settings

[d_yo_r]

Feature Request: Secure and Efficient Bot Settings Sharing

Problem:

• Current link-based sharing method is potentially insecure and can expire.
• Manual configuration transfer is time-consuming and error-prone for complex settings.

Proposed Solution:

1. JSON Export:

   • Implement a feature to export bot settings as a JSON object.
   • The JSON should include all relevant configuration parameters.
   • Consider compressing the JSON to reduce file size and improve transmission efficiency.
   • Encode the compressed JSON in base64 format for compatibility and to prevent accidental modifications.

2. JSON Import:

   • Allow users to import bot settings from a base64-encoded JSON file.
   • Validate the imported JSON to ensure it adheres to the expected schema.
   • Automatically apply the imported settings to the bot.

Additional Considerations:

• Version Control: Implement a versioning system for exported JSON files to track changes and allow rollback if necessary.
• User Interface: Provide a clear and intuitive interface for exporting and importing settings, including visual indicators for successful operations.
• Security: Consider to either avoid or encrypt sensitive data within the JSON file to enhance security, especially for settings that contain confidential information.
• Compatibility: Ensure compatibility with different versions of the bot configuration.

Developer Guidance:

• JSON Library: Use a robust JSON library for parsing and serialization.
• Compression: Explore libraries like gzip or zlib for efficient compression.
• Base64 Encoding: Utilize a base64 encoding library to convert binary data to a text format.
• Security: Consider using encryption algorithms like AES or RSA for sensitive data.
• Error Handling: Implement proper error handling to catch and report potential issues during export, import, or validation.
• Testing: Thoroughly test the feature to ensure it works as expected under various conditions.

By implementing this feature, users will benefit from a more secure, efficient, and flexible way to share and manage their bot settings.

[ppalba344]

Hello
I use my old backtests to keep track of good / bad ideas and configurations. Since they are already tested, I know what works and what doesn’t.
However, the option to save a file with the configurations could be interesting; it’s just that over time, with modifications in GAINIUM’s programming, it could lose compatibility. I believe that saving some backtests as proven ideas is easier and doesn’t require implementing anything without worrying about backward compatibility

Bye
PEPE

[d_yo_r]

Yes, it’s surely necessary to cope with new settings that are missing and removed settings that still are in the JSON.

[d_yo_r]

It’s there! Thanks @aressanch and team!

Strategy: SuperBollingerBand%Trend

The strat is looking great! One thing, since we introduced export of settings you can share bot settings directly in the post, so other users can download them without expired links. Would you mind attaching the settings in your original post? Find the imp/exp: [image] Then click on copy, which will save it to the clipboard. Then start a new document and paste it, save it with extension .json or .txt. Later we will add the download of .json file directly but this was the fastest way to get i…

I only wonder whether it’s a good idea to have the uuids in the export.

[aressanch]

@d_yo_r

I only wonder whether it’s a good idea to have the uuids in the export.

Good catch, we will remove them.

[d_yo_r]

It would also reduce the export size if we had an option to exclude empty fields or get a zipped file. Is there an idea how referrals could work with that kind of sharing configurations?

Could you check whether also a referral code or a reference to our bot or account is part of the export? Otherwise we would lose the chance to benefit from sharing our setups via the exported files, which also seem to be the only long term option to do so.