Skip to content

OpenZero 7.3 — Independent nodes, direct peers and durable releases

Latest

Choose a tag to compare

@ResearchForumOnline ResearchForumOnline released this 30 Sep 13:20

OpenZero 7.3.0 — Independent nodes and durable GitHub distribution

OpenZero runs on independently operated local machines or servers. A TalkToAI/OpenZero hosted backend, main node, account service or central database is not required.

Runtime changes

  • Optional direct peer note exchange in each ordinary OpenZero node. No bootstrap server, coordinator or automatic discovery.
  • Dedicated scoped receive keys, explicit publication/exchange consent, content-addressed deduplication and a separate review inbox.
  • Selected note exchange and latest batches bounded by both event count and actual UTF-8 wire bytes.
  • Received notes never become tool commands, prompts, training data or relayed content automatically.
  • Default peer/Hive remote sharing disabled; exact retired service defaults migrate while custom operator endpoints remain intact.
  • Existing source-improvement and local adapter-training workbenches remain available. Generated candidates cannot modify the peer authorization boundary.

Distribution and interface

  • Online/offline installer 7.3 defaults to local operation; verified runtime ZIP extraction protects private configuration.
  • GitHub-hosted release assets and operator-selected mirrors replace retired owner-hosted installers/downloads.
  • Updater verifies the GitHub installer checksum. A pre-7.3 installation should bootstrap through the new verified installer first, because its old updater may use the retired website.
  • Refreshed static project page, local guide and peer settings panel. Existing custom settings and runtime data are preserved.
  • Tab Pilot 0.3.1 ZIP and checksums. Linux/Windows helpers prepare an unpacked extension and require the user’s browser approval; they do not write new managed policy or rotate an existing token.

Verification

  • 146 Python regression tests passed locally, including 23 peer tests and actual HTTP exchange between two independent temporary nodes.
  • Manifest/static security validation and all 21 extension tests passed.
  • Four Bash installer/helper syntax checks and PowerShell helper parsing passed.
  • Release ZIP integrity, safe paths, private-state exclusions, required runtime files and included licenses checked.

GitHub CI also runs the complete Python suite, extension validation/tests and release build on pushes. The source checks and synthetic/loopback exchanges do not establish distributed inference, consensus, external-server operation, sustained model performance or independent security certification.

Download and use

See the installation guide and direct peer guide.

Review install.sh, verify it against install.sh.sha256, then run it on a Linux machine you administer. Installed local operation works independently after its dependencies/models are prepared. Optional cloud APIs, web search and remote peers need the services selected by the operator.

Included assets: runtime ZIP/checksum, installer/checksum, updater, Tab Pilot ZIP/checksum. The GitHub source-available Community Source License and third-party rights remain applicable. Peer outbound keys are private local state, not encrypted at rest; Windows uses inherited filesystem ACLs. There is no automatic NAT traversal or strict whole-request DNS deadline.