bunch

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

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

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

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

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