alex retweeted
the mainnet is currently undergoing an update, once complete, all HFHE ops, new @AppliedLang features, a new program layer, an updated circle viewer, and more will become available (the webcli will need to be rebuilt for this) + cleaning things up and fixing bugs using the ML fuzzer tool @octralex developed (he might release it as a third party product later it seems) * * an automated bug hunter on steroids
16
22
99
4,440
alex retweeted
Universal Encrypted Compute
The cryptographic world computer: vitalik.eth.limo/general/202… My attempt to express in somewhat concise terms the true meaning of basically everything planned to happen to Ethereum starting from the fork after Hegota. It's really not just a blockchain anymore. It's a hybrid architecture that combines together blockchains and modern cryptography, to enable much more powerful properties. FOCIL, EIP-8288, Lean consensus, state management, formal verification, advanced mempool improvements (including privacy), and the longer-term specter of obfuscation all mentioned.
20
16
131
8,217
alex retweeted
another important nightly update has been completed, which included several things important for the devnet, and therefore also for the mainnet: 1. exact arithmetic - we moved 512 bit scalar reduction into wide form, eliminated rare truncation of the high bit, negative constants in the VM now go into the field signed, and not as before (before we used unsigned casting andthis problem had been there for a long time, we only noticed it now), normalization of the empty part of the ciphertext is now implemented correctly (before multiplication and addition with a constant), also improvements in Q16, and the arithmetic mode is pulled through everything possible, all flows where it can be involved are now covered explicitly 2. MEMORY. the proposers and preverify cache now takes bytes into account and not only the number of tasks (the mechanic is transferred from bootstrap nodes), repeating strings are now interned through a weak table, also now the pre verify cache is reset on state root change, and does not pile up in the heap and stale results do not accumulate (the storage node mechanic is transferred to the lite node), 3 . nil quorum prevote advances the round immediately, and not as before when a node could idle for the full timeout, and a proposal with still unavailable time of the previous epoch will wait and retry, and not refuse blindly, also validator set retention is transferred (a similar mechanic is implemented on bootstrap nodes and has previously proven its effectiveness) 3. another pile of profile tests (earlier we decided to gradually bring all testing tools into public access and continue to do so). a new release marker is on the way, validators should upgrade for the sake of culture and safety github.com/octra-labs/lite_n…
9
20
81
10,267
alex retweeted
from zero to one - devnet was updated at epoch 1500000 (much better than we expected), there were some delays that should be resolved with the new release (existing validators should upgrade, the release marker is already in place). among other things, we moved a lot of tests that we don't usually add to releases, but decided to slowly add them for the sake of culture and convenience of validators and devs who directly work with the code, so that they don't waste time writing covering tests. another thing i'd like to point out is that main net is catching up quickly with all the fixes successfully implemented in dev net, the next release will include configs for connecting to main net, so validators will be able to start working with the main network as well. want an upgrade? it's simple, run these commands from your existing node checkout + using the same user that runs your node: sh controls/upgrade.sh --diagnose sh controls/upgrade.sh --apply sh controls/upgrade.sh --diagnose * remember the days when upgrading took several iterations and a ton of approvals? that's a thing of the past now. btw, if you have a spare graphics card or a cluster of GPUs, now's the time to create a symlink for your future mainnet node because you'll have something to fill it with (private inference on steroids has already been tested and debugged). ps: a major webcli update is also on the way, thanks to everyone for their support and help.
17
29
128
7,480
alex retweeted
the lite node has received significant improvements, including inheriting the full VM + amlc compiler (with fairly strict formal verification) from the previous generation, this nightly build also addresses a long standing issue with storage size growth, we've migrated a feature from the storage node to the lite node that enables the use of a compact account pack - instead of rewriting full account records, the node only commits changed cells and a fixed size header each epoch, allowing the size to be reduced from 5 Mb to 191 kilo b (a 26x space saving), several other minor fixes are also included. this release will be tested for some time, and we will prepare an updated instructions (although it may be possible to use previous installation routes, which will be announced later). many thanks everyone. github.com/octra-labs/lite_n…
7
18
84
8,504
the octra lite node visualized play with it here: claude.ai/code/artifact/4de5…
i've started having claude turn my codebases into visual diagrams so i can discuss the codebases with claude more easily - the moving dots are data snippets that i can inspect
6
6
53
3,049
alex retweeted
the lite node received a significant interim update (this was the penultimate pre-release update before the mainnet) existing validators should update, those who wanted to try themselves as a validator should set up a node, the next update will be dedicated to the webcli and the AML compiler (if you're already a validator, you should use upgrade script, and if you want to start from scratch (which is commendable), you should follow the instructions in the README, section on setting up the environment): github.com/octra-labs/lite_n… there's quite a lot ahead, but as they say - one bite at a time
15
20
107
24,818
alex retweeted
we've finalized the controller fix for rejoining validators in case of lag, this isn't a new release, so a full clone isn't needed, only an update, get the source from here: github.com/octra-labs/lite_n… following are instructions for getting your node to rejoin and catch up with the network: cd /opt/octra/libv_litecore git remote -v (should point to octra-labs/lite_node) git pull --ff-only test "$(git rev-parse HEAD)" = "336050d8b2d940d739c91778021c235324916321" test "$(cat SOURCE_COMMIT)" = "3250ab52cf9bd31b5c9e00c1dd8ed9d6229747ce" sh controls/check.sh sh controls/build.sh (you can skip this step if you've already built 3250ab5) next sh controls/rejoin.sh --check this utility then outputs sh controls/rejoin.sh --wait-seconds 600 or if for legacy (If --check requests a legacy handoff), then run sh controls/rejoin.sh --legacy-handoff --check sh controls/rejoin.sh --legacy-handoff --wait-seconds 600 the only indicator of success is the output of this line in the terminal: "status = validator_active and voting = enabled (do not re-run it)" do not pass --sync, do not re enroll, if installing from scratch, follow the instructions in the readme. not all validators have been updated, so those who are able to do so now will help move forward and complete finality (this does not apply to those who haven't yet enrolled and are in observer status) thanks everyone
2
12
51
4,722
I will sound oneshotted, but @lambda0xE shipping daily + agents circle jerking every release + Kimi running a honest node while submitting 100s of fraudulent txs is the most fun I've had in tech in a while. One of the earliest genuinely new runnable infra in LLM age being built.
Built an agentic security review loop for @octra using Codex, Claude, Kimi and @egregore_xyz for shared context. Spent 3 days with no prior experience and already have dozens of patched findings. May publish a write-up if there's any interest, although it's probably nothing new!
4
5
92
4,861
General purpose encrypted compute at scale is the hardest open problem, period. Solving the hardest problem in a way that will stand the test of time is not a flashy path. But if / when it is solved, all the hardships will be worth it!
LiveOverflow 🔴 hextree.io
3
8
60
2,196
alex retweeted
you can build a node locally or in a 4 vcpu / 8 gb ram / 100 gb disk droplet and join devnet validators today to be prepared for mainnet once it lands there is no need to reach out, join a chat or ask for permission, just build, enroll and earn dev oct: github.com/octra-labs/lite_n…
17
21
129
11,189
alex retweeted
an early demo of onchain LLM inference inside an octra circle (unencrypted) is now available through webcli. to test, install webcli, run ./octra_wallet and navigate to: http://127.0.0.1:8420/circles.html?uri=oct://oct99BWHFpV5r54DXKc2FhsBmZEaS6Q8zvCQrHRgXUcK4Fk%2Findex.html
an early release of the graph-based LLM (v0.0.1 pre-alpha) running on circles is already available on devnet at: oct://oct99BWHFpV5r54DXKc2FhsBmZEaS6Q8zvCQrHRgXUcK4Fk/index.html give it a try and say hello, it’s still slow, but that’s just a matter of a couple of days while we run benchmarks and fine tune the KV cache mech the roadmap for this thing is straightforward: various models ranging from simple to complex, "agent-tools" (don't really like that buzzword, but i decided to put it because in rare cases it actually makes sense) that the models can utilize, customizable privacy levels, internet access via HFHE + CircleGate + Tor (optional), membranes, and much more
9
12
75
7,463
alex retweeted
scheme development network launch circle vm optimization public node release [ decentralized inference ] <- you are here global encrypted data exchange privacy preserving training better data, better models
we achieved some progress in the implementation of state inference inside octra , first we managed to implement continuous reasoning without clearing the circle memory, second we completed a pure resource model under which validators can verify and certify the execution flow of a set of useful work (in this case this is ML inference with text generation by input tokens fully onchain), a few months ago the answers of the test model were one-word and substantially limited, in the current version (which will be available for everyone) the reasoning flow is automatically extended, it will be possible to upload various models into circles or create tools for their use making them public or only private (full demo will be opensource as soon as we finish, it will be possible to deploy anything in 2-3 clicks) live use case, the economic model also converges here - wallet pays for inference in native coins, validators (with GPU support can maintain availability of their resources to quickly process such private calls, while the execution core remains private through HFHE)
10
20
89
7,111
alex retweeted
testing a clean node installation on a new @Raspberry_Pi
a quick update regarding the lite node (which, in terms of synchronization, has effectively become the standard node type): all early validators and testers should now update to the latest version (specifically, public release commit 305c8da6b5a8fff39efe42eef08b33326e1153ab, with SOURCE_COMMIT 54823e4e740f4183b60e62f117d982f9eda82d5a) next, stop the current node, update the source code, and rebuild all five binaries (the node and supporting binaries), then pls run sha256sum -c config/network.env.sha256, then run the sh controls/check.sh script, after that, execute sh controls/config_val.sh --role observer ... --build --sync --yes start the node and wait until sh controls/stat.sh reports that the node is synchronized with the current chain state and ready. only then should you run the command sh controls/enroll.sh join --amount 1000000 (ensure there is a small positive balance on devnet for the validator bond - around 1.5 OCT is plenty) github.com/octra-labs/lite_n…
9
12
79
3,923
alex retweeted
a stable alpha release of the lite node along with devnet configs is out: github.com/octra-labs/lite_n… nodes can now connect to the devnet by following instructions and configs in the repo: github.com/octra-labs/lite_n… mainnet configs will be released after a security review
12
16
73
4,631
Built an agentic security review loop for @octra using Codex, Claude, Kimi and @egregore_xyz for shared context. Spent 3 days with no prior experience and already have dozens of patched findings. May publish a write-up if there's any interest, although it's probably nothing new!
13
11
84
7,181
To be clear, the patches are all human, and the fleet writes zero code. There is a zero LLM policy in place for anything that matters, so it only reads code line by line, continuously builds hypotheses from relevant literature, and submits these findings for manual review!
2
12
590
alex retweeted
the lite node has been updated to "tentatively stable", and control mechs have been improved, devnet configs have also been added, so anyone can now build a node from scratch and connect to the network by following the instructions (meanwhile, we are conducting final checks and preparing to update the mainnet configs, an announcement regarding which will be made in the coming days) ps: among other things, there are several important announcements regarding webcli and the subsequent @AppliedLang update, but these will only be published once the commits are ready. there are no blockers, it's permissionless: github.com/octra-labs/lite_n…
8
15
83
3,924
alex retweeted
a minor update for the lite node is now available: it includes slight adjustments to runtime execution and a few small improvements to other processes, please note that this is an interim (unstable) version, though it is fully ready for testing later today, we will also release separate config data for the devnet and pre-configurations for the mainnet all nightly builds are available on GitLab: gitlab.octra.org.uk/octra/li…
4
11
55
2,288