λ (@lambda0xE) header
λ (@lambda0xE) profile picture

byzantine general & co-founder @octra

London, England
Joined July 2022
Photo by λ (@lambda0xE)Photo by λ (@lambda0xE)Photo by λ (@lambda0xE)Photo by λ (@lambda0xE)Photo by λ (@lambda0xE)Photo by λ (@lambda0xE)Photo by λ (@lambda0xE)Photo by λ (@lambda0xE)Photo by λ (@lambda0xE)Photo by λ (@lambda0xE)
mini comment on the mini roadmap: a new release marker for devnet will be available in a couple of hours and the release marker and info for main network are expected later today (there was a lot of delicate work involved, we did our best) – at London, England
mini-activation roadmap (during the day for the next epochs): 0 - rpc shutdown (and preparation of a 2+ hour window) 1 - snapshot of the state (of both networks, mainnet and devnet), the snapshot hash will be available separately, 2 - sequential activation on foundation nodes (we will launch a planned merge on our nodes and wait for all rules to activate on the mainnet, this is done to ensure all rules are in place and properly debugged), 3 - monitoring the progress of epochs, after 1000 epochs, a public set of configs for connecting external validators is published (the mainnet becomes uncontrolled, validator participants contribute bonds and begin participating in the treechain). we ran several test runs over the weekend and confirmed everything was fine, so we're starting the process step by step, we'll publish info about the activation window shortly (this could be considered the snapshot time), everything was boiled down to a few simple steps, and we don't expect any significant issues today. the reward model will be published separately, as the mainnet differs significantly in supply and reward formation, as well as the OU fees for ops carried out. ** all rewards earned by validators in the devnet for the entire period will be available to them in the main net (every bit processed will be counted and fairly determined) thanks everyone.
3
8
1
56
1,158
mini-activation roadmap (during the day for the next epochs): 0 - rpc shutdown (and preparation of a 2+ hour window) 1 - snapshot of the state (of both networks, mainnet and devnet), the snapshot hash will be available separately, 2 - sequential activation on foundation nodes (we will launch a planned merge on our nodes and wait for all rules to activate on the mainnet, this is done to ensure all rules are in place and properly debugged), 3 - monitoring the progress of epochs, after 1000 epochs, a public set of configs for connecting external validators is published (the mainnet becomes uncontrolled, validator participants contribute bonds and begin participating in the treechain). we ran several test runs over the weekend and confirmed everything was fine, so we're starting the process step by step, we'll publish info about the activation window shortly (this could be considered the snapshot time), everything was boiled down to a few simple steps, and we don't expect any significant issues today. the reward model will be published separately, as the mainnet differs significantly in supply and reward formation, as well as the OU fees for ops carried out. ** all rewards earned by validators in the devnet for the entire period will be available to them in the main net (every bit processed will be counted and fairly determined) thanks everyone. – at London, England
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
7
16
5
77
4,807
everything was planned, tests were conducted, conclusions were drawn, patches and fixes were prepared, release markers are on the way (for both networks) – at London, England
1
18
640
intermittent scanner and Rpc outages are expected today due to final preparations which will last until 11 pm utc – at London, England
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
3
6
1
64
1,621
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
30
30
7
141
7,174
fun fact: octra runs LLM inference in Q24 fixed point, so every node gets the same bits and the output can be checked by consensus
5
10
1
56
1,855
– 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
6
5
1
59
2,108
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
12
20
3
88
4,584
were quietly finishing up the prototype for octra to work as a priv layer for other networks or apps, test cryptographic proofs and verification took a couple of days (gpu process of building proofs), so we're expecting a couple of updates today. wanted to get definitive confirmation. – at London, England
18
19
5
115
4,359
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
16
23
4
89
4,330
the cryptographic proto is fully active on the dev net, the proof form is optimized by 2x (tests can be observed live btw), the entire surface is accessible, enc, dec, stealth txs, claims, etc, and at the VM level, the HFHE proof form (pvac version) is fully operational: devnet.octrascan.io/tx.html?… (you can see an example here and on our dev addr in the history, and the payload is available via rpc and in the raw record) * an important thing before migration, in order to use these features, you will need to upgrade your webcli tomorrow evening – at London, England
4
17
2
74
2,950
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
9
11
3
78
3,800
λ retweeted
Updated octra-sqlite v0.6.4 to include sqlite 3.54.1, accommodate Octra authentication changes and a couple of other small fixes. If you have a previous version deployed, this version will also help you through the upgrade. github.com/tomismeta/octra-s… crates.io/crates/octra-sqlit…
Built actual SQLite inside an Octra Circle. Thought this was a key primitive for rapid development on Octra. Guided setup and full CLI modeled after SQLite with Octra-specific commands and info. Accessible for API builds and agent interactions. github.com/tomismeta/octra-s…
1
2
24
1,042
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
8
5
3
62
2,779
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…
5
15
3
69
3,176
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…
5
13
63
1,807
@octralex calls it loops, i call it zaloops (in the russian manner) – at London, England
11
356
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
5
18
5
77
6,476
I like – at City of London, London
2
2
1
61
1,857
did someone else notice the shift? – at London, England
12
11
2
93
5,243