releasing the latest hand made bits to improve fault tolerance (the upgrade will be required on weekends), as well as a portal with all changes and the proposal log, which stands out for its activation rules, the name has been coined -OPD (octra protocol document), everyone will be able to participate in proposals for changes.
OPDs are needed to structure all the changes and separately highlight explanations of why they have been made in the first place, and to propose a discussion. – at London, England
a mainnet upgrade is a matter of days, not weeks or months (the capabilities and featuresare already visible in the devnet) – at London, England
use circles in octra to host private resources, apps, data, etc, there will be nothing to steal, and there is no such concept as exit nodes – at London, England
🛑 Attackers hijacked over 300 Tor exit relays to intercept SSH connections and steal login passwords.
A researcher found 333 exits redirecting SSH traffic to 12 interception servers.
The Tor Project has since blocked the affected relays.
Here's how the attack worked: thehackernews.com/2026/10/at…
hack yourself before other do (the policy we ourselves adhere to).
fyi: an automated fuzzing search engine based on slop generators (by @octralex) found critical crap in ALL projects we've ever interacted with (since there's already context), some have been fixed, others haven't been revealed yet and may not be, given the mixed reactions.
what a time to be alive – at London, England
a new unscheduled release is now available for vals. please upgrade your nodes (a lot has been done on recovery and sync + an old bug from an earlier implementation at the vm level has been fixed) *
* the node could process the same epoch twice, and the root at that moment was different, when building and checking proposals at the consensus level, it was specified as 32 raw bytes (the earliest implementation from the end of 2024),and when using the epoch from the head, it was transmitted as a 64-hex string, so the bug was found during pre-release main net testing for mem compatibility of different program envs
upgrading is easy -
sh controls/upgrade.sh
sh controls/upgrade.sh --apply
sh controls/stat.sh
github.com/octra-labs/lite_n…
a new unscheduled release is now available for vals. please upgrade your nodes (a lot has been done on recovery and sync + an old bug from an earlier implementation at the vm level has been fixed) *
* the node could process the same epoch twice, and the root at that moment was different, when building and checking proposals at the consensus level, it was specified as 32 raw bytes (the earliest implementation from the end of 2024),and when using the epoch from the head, it was transmitted as a 64-hex string, so the bug was found during pre-release main net testing for mem compatibility of different program envs
upgrading is easy -
sh controls/upgrade.sh
sh controls/upgrade.sh --apply
sh controls/stat.sh
github.com/octra-labs/lite_n… – at London, England
