3s (@Kang3s) header
3s (@Kang3s) profile picture

make things easier

Joined December 2017
Photo by 3s (@Kang3s)Photo by 3s (@Kang3s)Photo by 3s (@Kang3s)Photo by 3s (@Kang3s)Photo by 3s (@Kang3s)Photo by 3s (@Kang3s)Photo by 3s (@Kang3s)Photo by 3s (@Kang3s)Photo by 3s (@Kang3s)Photo by 3s (@Kang3s)
Replying to @zama
stop the clownshow guys, this is _not_ cypherpunk privacy. it's vendor-dependent privacy. your code license grants no patent rights, so commercial deployments need Zama's permission. permissionless systems require independent implementations, but a patent moat actively discourages them. if Zama disappears, who maintains & upgrades the stack? you currently fail the walkaway test and are nowhere near CROPS-aligned. you can do better.
17
27
14
323
32,877
An experimental Proof-of-Work faucet for the @octra Devnet, allowing users to earn devnet tokens by completing PoW challenges. octdrop.xme.my.id/
2
2
11
220
3s retweeted
webcli has been updated to version 0.06.03 (still alpha) - the proof system has received significant optimizations, so i recommend rebuilding the wallet and testing it, all crypto funcs requiring local construction of proofs have become many times faster (from x5 up to x16) we’ve revised the pedersen commitment process, moved the heavy parts onto the Pippenger method (a highly efficient algo for quickly computing multi scalar multiplication, which you can read more about here - cr.yp.to/papers/pippenger.pd…), added lazy scaling to the bullet proof things, and, ofc added parallelism on steroids, but the main gain was achieved through IPP folding. enc: was 36 s> ~4 s dec: was 81 s > ~12s stealth tx: was 86 s >~13 s ct refresh: was 185s > ~20 s tested it on my macbook pro - M 4, 24 gb ram ps: will explain the math in detail later (bc it takes time to put all these things together) as always, link: github.com/octra-labs/webcli – at London, England
small improvements in cryptographic functions which previously could take up to 1-2 minutes received speedup (in some cases 16 times), this means that encrypt which took 35-40 seconds now on 4 threads will be able to achieve confirmation in 2.2 s (valid for everything - encryption, decryption, stealth and claim, and also FHE VM calls), from more interesting - new version of pvac-hfhe with updated benchmarks will be published after network upgrade, this will allow to compare useful improvements live you will be able to evaluate it in the upcoming webcli release
8
14
6
58
5,194
3s retweeted
small improvements in cryptographic functions which previously could take up to 1-2 minutes received speedup (in some cases 16 times), this means that encrypt which took 35-40 seconds now on 4 threads will be able to achieve confirmation in 2.2 s (valid for everything - encryption, decryption, stealth and claim, and also FHE VM calls), from more interesting - new version of pvac-hfhe with updated benchmarks will be published after network upgrade, this will allow to compare useful improvements live you will be able to evaluate it in the upcoming webcli release – at London, England
5
12
4
74
3,295
3s retweeted
build markers are being released, but don't upgrade to the current one yet (even if it's available - we consider them to be for debugging purposes) and wait for the final announcement + currently configuring everything for both networks (devnet and mainnet), so both val configs will be available today, with the devnet a little earlier. this is the final stage, which includes a complete upgrade of everything, including side services, from scanners to release routes (the mainnet is getting its own separate public branch). – at London, England
"mini-time" of the mini-upgrade has come. what's done? the past two weeks as always didn't go to waste and we moved the latest relevant parts with minor fixes including our intermediate shit on the fix into Irmin Db (our favorite and most important data storage system), the work touched all parts - consensus (quorum by weight instead of counting seats, that same infamous sigma algebra of events, validator exclusion for proven violation on the eve of mainnet, among other things now quarantine and node catch up count weight, not the number of node responses, which for the most part were useless, so this crap is also fixed, big work on protecting against network halts, solid improvements to the VM, p2p and Rpc work also got improvements (octra sync target removed from public rpc and available only through local socket), separate work was transferred on our main data storage system - Irmindb (the most powerful in its essence data storage system, equals of which there are none and unlikely to be in the current era, so our moral duty to keep it up to date and update it with our own hands), in total, what's done on it - irmin had a problem with the garbage collector in irmin-pack, we've been running into this problem for a long time and we took it upon ourselves to rewrite some parts and patch it, we made it reliable for a node that runs for months and can crash at any moment, now background gc processes are under full control, as well as many other important things in the work of storage for distributed systems (this work with the new build will also go into a pr for irmindb in their repo) the release marker will be available in about an hour. first, the devnet will be upgrade, then we will move on to the mainnet. Valiators should prepare btw, thanks eveeryone! github.com/octra-labs/lite_n…
3
9
2
52
2,549
3s retweeted
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.
4
10
64
1,697
3s retweeted
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
8
16
6
81
5,977
3s retweeted
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
65
1,699
3s 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
30
29
7
144
7,635
3s 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
12
20
3
88
4,718
3s retweeted
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,414
3s retweeted
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,983
3s retweeted
Proud to announce that in the early days of external testing, Loops was awarded its first autonomous $1000 bounty by the Ethereum Foundation
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.
5
7
2
79
3,423
No crypto wallet is 100% safe. No software is bug free. No tech is 100% secure. There are risks in everything you do. There are risks if you don't do anything. There will be issues, setbacks and problems to solve. Stay up-to-date. Manage risks. Solve problems.
1,785
2,683
681
18,896
1,442,849
3s 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…
7
7
4
73
4,542
3s retweeted
13
23
2
112
5,937
3s 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!
4
10
80
1,567
3s retweeted
the new upgrade is already available, it includes important updates for fault tolerance as well as an addition for resource compute protocol, which was previously unavailable in the lite node but has been moved from the bootstrap build to achieve more natural and seamless decentralization, activation will be in 1 day, there is time to update (as previously said, this is no longer a major update on top of consensus, but a module within the runtime), the upgrade as always with a single list of commands: sh controls/upgrade.sh sh controls/upgrade.sh --apply sh controls/stat.sh ps: if the message "installed ... pending" appears, leave the node running, do not restart it in a loop. regarding the build - marker 32, source f7637a7e, and you need to update to 1688734, consider this the final update, further only applied upgrades. we've also migrated the earliest work on formal verification from 2021, so you can do some dev-archaeology, among other things( if you have the time) thanks everyone. github.com/octra-labs/lite_n… – at London, England
9
17
5
84
6,162
3s retweeted
everyone can upgrade gradually, everything is as usual: sh controls/upgrade.sh sh controls/upgrade.sh --apply --wait-seconds 3600 sh controls/stat.sh fyi: we don't expect any more significant upgrades (if there are new markers, they will be minor fixes), from now all attention is on the mainnet, validators who have been with us all this time will be able to claim the coins mined on the devnet what's potentially interesting about Mainnet expected in the near future: - advanced circles (deployment of applications in any language that compiles in WASM), - a multi-tier circular network of resources. Web services on top of the oct:// proto, decentralized programs, databases, llm models as a service with a managed access level with the ability to provide a public gateway, storage, etc. a marketplace of demo progs, circles, and aml, rust, C++, ocaml examples, which we've been working on for the last six months, one-click deployment of anything from a website to an api circle with a cluster of other programs, etc) - a new client with a new thing inside, not webcli, but a Firefox browser with native support for circles and domains in the oct:// space, with public tunneling gates (the circle gateway randomly tunnels traffic from different sources through a otbP2P net, hiding all info about the requester, the history is untraceable, making it impossible to know the addr from which the request came, there's also a total mode where the gateway uses a proxy server as an intermediate encoder, and internal traffic goes through the PVAC data streaming proto*). It's a pretty interesting thing + you can also optionally add a @torproject to the intermediate membrane (an example of which has already been published earlier) * PVAC data streaming proto - the untitled shit, which is not yet publicly available, will be released separately once we complete security testing. ps: we also spent time researching a rather complex topic, as part of the team was ML-pilled, As you know, circles and nodes support Q algebra, meaning nodes can handle dense ML, not just matrix mul, but a full cycle, so open weights are quite heavy, initialization can take up to half an hour, etc., but we found a way to do this in 15 sec instead of half an hour for a rather cumbersome model (technical details with examples will be published in a separate article later), the module's mechanics extend beyond the @octra arch and can be used separately in other projects ps 2: we also spent time on the interface, docs, and site-design (we'll update it soon)* * regarding the design, it's absolutely pointless crap (my personal opinion, different from those who appreciate beautiful interfaces) that has no value for system protocols, but people like it, which means it's time to release something nice as always, quick links are at hand: - webcli github.com/octra-labs/webcli - amlc (AML compliller) github.com/octra-labs/amlc - libv_litecore, which is a lite node github.com/octra-labs/lite_n… thank you all for your attention – at London, England
lite node gets a solid update (or rather, already got it, release marker is on the way, validators will need to update), this release included a lot of work on circles (atomicity, native transfers etc), nested programs (both ways with circles), improvements for the hfhe worker with a developed actor model (ported from the bootstrap node), rule activation roughly after 10k epochs, everyone should update (mainnet gets this update too) with every step the lite node is already getting harder and harder to call "lite", with the storage module update and gpu interface for deep compute chains on top of circles it will become indistinguishable from a standard node. among the interesting bits - the proof model is also expanded, we decided to add validated verif methods in Coq from our early 2022 work for the sake of culture a couple more words on the PQ hysteria of llm slopers and doomerism, to clear questions we decided not to wait for the start of 2027, but to start rolling out the update on signatures, hashing and other stuff on lpn + our hash-based basis (where appropriate) already now with gradual activation so everyone can comfortably update signature format etc (detailed plan will be published a bit later, still figuring out how to do it seamlessly) github.com/octra-labs/lite_n…
8
14
7
73
8,988
3s retweeted
lite node gets a solid update (or rather, already got it, release marker is on the way, validators will need to update), this release included a lot of work on circles (atomicity, native transfers etc), nested programs (both ways with circles), improvements for the hfhe worker with a developed actor model (ported from the bootstrap node), rule activation roughly after 10k epochs, everyone should update (mainnet gets this update too) with every step the lite node is already getting harder and harder to call "lite", with the storage module update and gpu interface for deep compute chains on top of circles it will become indistinguishable from a standard node. among the interesting bits - the proof model is also expanded, we decided to add validated verif methods in Coq from our early 2022 work for the sake of culture a couple more words on the PQ hysteria of llm slopers and doomerism, to clear questions we decided not to wait for the start of 2027, but to start rolling out the update on signatures, hashing and other stuff on lpn + our hash-based basis (where appropriate) already now with gradual activation so everyone can comfortably update signature format etc (detailed plan will be published a bit later, still figuring out how to do it seamlessly) github.com/octra-labs/lite_n… – at London, England
5
17
4
78
7,669