SYV ★ retweeted
its time to update the mainnet and release it in the form it was originally planned, the very first vision is probably the only correct one
special thanks to all the validators and participants who supported the devnet and continue to do so - now it's time for the mainnet, permission less access is planned for tomorrow/the day after (the exact time is unknown, any second now)
everything needed to run a mainnet node will be available in a separate release, thanks everyone – at London, England
SYV ★ retweeted
let's hack
SYV ★ retweeted
– at London, England
hi everyone, webcli has been updated, a lot has been done, we're counting it as version 0.06.01-alpha.
the cryptographic surface has been strengthened, as has security (this doesn't mean we've closed everything; we're working on it and it's far from finished),
anyone working with the dev net and planning to interact with the mainnet should update and test FHE ops on the devnet (this is perhaps one of the most important parts), working with circles, and more, we've also added access via an API key to automate some processes and make it easier if you're building a tool for some reason, access to the key is in the "settings" tab, so pass the key in the request header of your app - "Authorization: Bearer <api key>"
fyi: : webcli must be running, the api is only available on your puter, kep the key private.
webcli should be rebuilt, and also importantly - please keep a previous copy of webcli src in close access to your hands for some compatibility tasks (this will potentially be necessary).
thanks everyone.
github.com/octra-labs/webcli
SYV ★ retweeted
hi everyone, webcli has been updated, a lot has been done, we're counting it as version 0.06.01-alpha.
the cryptographic surface has been strengthened, as has security (this doesn't mean we've closed everything; we're working on it and it's far from finished),
anyone working with the dev net and planning to interact with the mainnet should update and test FHE ops on the devnet (this is perhaps one of the most important parts), working with circles, and more, we've also added access via an API key to automate some processes and make it easier if you're building a tool for some reason, access to the key is in the "settings" tab, so pass the key in the request header of your app - "Authorization: Bearer <api key>"
fyi: : webcli must be running, the api is only available on your puter, kep the key private.
webcli should be rebuilt, and also importantly - please keep a previous copy of webcli src in close access to your hands for some compatibility tasks (this will potentially be necessary).
thanks everyone.
github.com/octra-labs/webcli – at London, England
SYV ★ retweeted
btw, the day wasn't wasted, we discovered another bottleneck that required special attention, so we decided to deduce it from a proof-of-concept form, rather than simply as an algorithm and separately decided to prove that after any write, the state remains synchronized among all participants, a quorum requires both thresholds (number and weight of participants) to be met
the learning context itself, based on moving consensus, doesn't change the vote, lock, or finalization phase. this was a rather specific problem, so we decided to formalize it (sorry for the format - the OPD platform will be available in a couple of days, but for now, we're writing the descriptive part manually), so you can take a look at it here: gitlab.octra.org.uk/octra/li…
the new release marker is now available for validators, pls upgrade as usual:
sh controls/upgrade.sh
sh controls/upgrade.sh --apply
sh controls/stat.sh – at London, England
SYV ★ retweeted
HFHE sandbox has been updated to pvac v7
encrypted arithmetic, matrices, vectors, logic gates, fourier transforms and recrypt benchmarks all work locally in your browser with no node, RPC or wallet connection
a working demo of real encrypted compute:
sandbox.octra.org
SYV ★ retweeted
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…
SYV ★ retweeted
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…
SYV ★ retweeted
Our agentic "Loops" infra is getting better: a serious devnet inflation bug was caught immediately upon activation and with no impact on mainnet.
We also ran Loops on friendly privacy/ZK/FHE-adjacent projects, and responsibly disclosed our findings. Write-up coming once safe.
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…
SYV ★ retweeted
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
SYV ★ retweeted
Hours after publication, the fleet caught an already patched devnet bug of the same class that we paid a five figure bounty for in June. It was assigned a first ever critical severity and live-tested overnight.
3 months subs paid off tenfold with just one routine finding. Do it!
SYV ★ retweeted
octra is the most criminally undervalued digital asset on mother earth; there will be an entire era of cypherpunk reality built on the guarantees of the hypergraph…
we are graced with the early opportunity to watch the founders demonstrate the seemingly endless potential of something so unique and powerful…
to paraphrase the late paul erdős: the market may not be ready for such mathematics…
SYV ★ retweeted
in the new version of the scan, formal verification, byte and src code, as well as program certs, have become more informative (this is still early alpha, it will change 1000%, but it has become more convenient to work with imo)
example: devnet.octrascan.io/program.… – at London, England
SYV ★ retweeted
Octra does not actually need a new CLI, it is natively agentic.
Any agent can build webcli, derive keys, fund a wallet, encrypt, deploy programs and circles and even run nodes. The RPC scheme is complete, our own fleet runs on public code.
Easily the most agent friendly network:
can't wait for @octra to get CLI for agents
private onchain agent swarms coming soon
SYV ★ retweeted
the test app, which we plan to release first on sepolia evm + octra devnet, and then add other networks, will allow sending ERC20 assets and gas coins between participants without disclosing the amount, sender, and recipient, outside the octra network (while octra is used as a computing layer for encrypted data)
it will be available completely open source, the application can be run locally (using the same principle as webcli), no trust environment, sharing keys, etc. – at London, England
SYV ★ retweeted
the lite node has been updated, the release will be available in a couple of hours via the standard upgrade commands for validators, the aml compiler now supports terms and strict higher functions, @octra network is a continuous-runtime math machine on top of HFHE, so sooner or later, it will become a universal tool for running unconditional finite programs with predicted effects, the state of which is encrypted, and not just shielded wrapped tokens (a preview version for mainnet is also available):
github.com/octra-labs/lite_n… – at London, England
SYV ★ retweeted
octra mainnet is right around the corner, herr sre few ideas u can build in octra
→ private escrow
→ encrypted vaults
→ private ml apps
→ multisig with programmable privacy
→ confidential marketplaces / auctions
→ private identity or reputation tools
→ ai apps that can work with sensitive data
octra already has official AppliedML examples for things like escrow, vaults, multisig, AMM's and private ML, so these ideas are grounded in the kind of program model octra is building toward
lock in
🤖 Made with AI
SYV ★ retweeted
fyi: the network has been upgraded, validators should apply the latest changes
- full net lifecycle (bond, exit and withdraw);
- new rules activate at epoch 1572000 (so pls upgrade before it);
- shared src compiler for the node and the amlc SDK (available separately for devs)
- faster install, tests optional (you can expand on them with your own);
- resource-based attestations have been implemented (enough with the pointless matrix multiplications, if we’re doing inference, let it actually be useful - private circle runtimes already allow this);
- HFHE computation paths are also part of the consensus for lite nodes and standart nodes;
- much and much more.
all activation rules are immediately applied to the mainnet and will be available without waiting (configs for access will be available after testing)