Master update

BUILD

@@ -161,7 +161,7 @@ python_distribution(
     ] + PACKAGE_SOURCES + PACKAGE_REQS + PACKAGE_FULL_REQS,
     provides=python_artifact(
         name="octobot",
-        version="2.1.1",
+        version="3.0.0-beta1",
         url='https://github.com/Drakkar-Software/OctoBot',
         license='GPL-3.0',
         author="Drakkar-Software",

CHANGELOG.md

@@ -6,6 +6,23 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 *It is strongly advised to perform an update of your tentacles after updating OctoBot. (start.py tentacles --install --all)*
 
+## [3.0.0-beta1] - 2026-07-26
+### Start of the OctoBot 3.0.0 beta
+OctoBot 3.0.0 a new system for portfolio automation from desktop and mobile.
+You run it on your computer or server in node mode (the new default OctoBot mode), which acts as the backend for the new OctoBot interface.
+
+OctoBot now stats as node by default and lets users start as many OctoBot as they want. Those bots can be started either:
+1. From the new OctoBot UI, available from the web and as a mobile app
+2. From the node directly, for expert OctoBots enabling backtesting and advanced analysis (using the classic OctoBot UI)
+
+### Added
+- [Node mode] The new OctoBot default: use the node as the orchestrator of your OctoBot, use it from the new OctoBot UI or app
+- [UI] Brand new Octobot UI. More private, flexible, easy to use and secure than ever. Available at https://new.mobile.octobot.cloud/auth/unlock
+- [Mobile apps] Start of the beta of the Android and iOS new apps with all the features of the Octobot UI, built into your phone
+- [Multi OctoBot support] Starting as many bots as you need, directly from the Octobot interface
+- [Kraken] Fully support Kraken exchange spot trading
+
+
 ## [2.1.1] - 2026-03-28
 ### Added
 - [GridTrading] Add reinvest_profits config option

bin/start.spec

@@ -1,19 +1,26 @@
 # -*- mode: python -*-
 
+from PyInstaller.utils.hooks import collect_data_files
+
 block_cipher = None
 
+# eth_account.hdaccount reads BIP39 wordlists from disk (hdaccount/wordlist/*.txt).
+# hiddenimports only bundles Python modules; collect_data_files includes those data files.
+eth_account_datas = collect_data_files("eth_account")
+
 OCTOBOT_PACKAGES_FILES = REQUIRED = [s.strip() for s in open('bin/octobot_packages_files.txt').readlines()]
 # hiddenimports=['numpy.core._dtype_ctypes'] from https://github.com/pyinstaller/pyinstaller/issues/3982
 a = Analysis(
    ['../start.py'],
    pathex=['../'],
    datas=[
       ('../octobot/config', 'octobot/config'),
-      ('../octobot/strategy_optimizer/optimizer_data_files', 'octobot/strategy_optimizer/optimizer_data_files')
-   ],
+      ('../octobot/strategy_optimizer/optimizer_data_files', 'octobot/strategy_optimizer/optimizer_data_files'),
+   ] + eth_account_datas,  # required for node wallet mnemonic generation (web3.Account.create_with_mnemonic)
    hiddenimports=[
       "colorlog", "numpy.core._dtype_ctypes", "dotenv",
       "pgpy", "imghdr",
+      "web3", "eth_account",
       "aiosqlite", "aiohttp",
       "pyarrow", "pyiceberg",
       "psutil",
@@ -22,6 +29,7 @@ a = Analysis(
       "asyncpraw", "simplifiedpytrends", "simplifiedpytrends.exceptions", "simplifiedpytrends.request",
       "pyngrok", "pyngrok.ngrok", "openai",
       "flask", "flask_login", "flask_wtf", "flask_caching", "flask_compress", "flask_socketio", "flask_cors",
+      "werkzeug.middleware", "werkzeug.middleware.proxy_fix",
       "wtforms", "wtforms.fields", "gevent", "geventwebsocket",
       "vaderSentiment", "vaderSentiment.vaderSentiment",
       "coingecko_openapi_client",

docs/content/developers/packages/node.md

@@ -24,6 +24,18 @@ User-triggered actions — things like a manual override sent through the API 
 
 Log messages emitted inside any workflow or step are routed to a per-workflow file under `logs/automations/`. Child workflows share their parent's log file, keyed by the first 36 characters of the workflow ID.
 
+### DBOS application version and recovery
+
+DBOS only dequeues and recovers workflows whose `application_version` matches the runtime. OctoBot Node uses a stable code constant — `SCHEDULER_APPLICATION_VERSION` in `octobot_node.constants` (currently `octobot_node_v1`) — instead of the OctoBot release version, so automations survive OctoBot upgrades.
+
+When `ALWAYS_ENSURE_SCHEDULER_APPLICATION_VERSION` is enabled, scheduler startup runs `migrate_stranded_workflow_versions()` before `launch()`. That re-tags any `ENQUEUED` or `PENDING` workflows in the system database to `SCHEDULER_APPLICATION_VERSION`, unblocking workflows stranded by older releases that tagged rows with the OctoBot version string. The flag is read from the environment variable of the same name (`true` / `false`); it defaults to `false`.
+
+| Setting | Default | Purpose |
+|---|---|---|
+| `ALWAYS_ENSURE_SCHEDULER_APPLICATION_VERSION` | `false` | Run startup migration of stranded workflow `application_version` values |
+
+Bump `SCHEDULER_APPLICATION_VERSION` only when workflow step order or semantics change in a breaking way. For branching old vs new code paths within the same version, use [DBOS patching](https://docs.dbos.dev/python/tutorials/upgrading-workflows).
+
 ## Encryption
 
 Task payloads are optionally encrypted using a hybrid RSA/AES-GCM/ECDSA scheme. Each encryption call generates a fresh AES-256-GCM key and IV; the AES key is wrapped with RSA-OAEP so the bulk payload never travels under the asymmetric key directly. An ECDSA signature over the ciphertext — computed as `ciphertext + encrypted_aes_key + iv` concatenated — is verified before any decryption attempt, preventing chosen-ciphertext attacks.

docs/content/guides/octobot-configuration/profiles.md

@@ -6,10 +6,15 @@ sidebar_position: 1
 
 # Profiles
 
-OctoBot's trading configuration is using profiles (located into
-user/profiles). This allows for quick switches between previously set
+OctoBot's trading configuration is using profiles. This allows for quick switches between previously set
 configurations. Each profile defines a [Trading Mode](/guides/octobot-trading-modes/trading-modes) configuration as well as other settings.
 
+Bundled default profiles (for example `default` and `non-trading`) remain on the filesystem under
+`user/profiles/`. When a wallet is configured, user-created profiles are stored in the sync
+`StrategyProvider` collection as `GenericProcessConfiguration.profile_data` (same profile id as the
+strategy). OctoBot still exposes the same profile API to the web UI and configuration layer; only the
+profile module selects the storage backend.
+
 ![octobot trading mode details from profiles](/images/guides/configuration/octobot-trading-mode-details-from-profiles.png)
 
 Profiles include:

octobot/__init__.py

@@ -16,5 +16,5 @@
 
 PROJECT_NAME = "OctoBot"
 AUTHOR = "Drakkar-Software"
-VERSION = "2.1.1"  # major.minor.revision
+VERSION = "3.0.0-beta1"  # major.minor.revision
 LONG_VERSION = f"{VERSION}"