SYV ★ (@syvxbt) header
SYV ★ (@syvxbt) profile picture

delusional optimist

Joined May 2025
Photo by SYV ★ (@syvxbt)Photo by SYV ★ (@syvxbt)Photo by SYV ★ (@syvxbt)Photo by SYV ★ (@syvxbt)Photo by SYV ★ (@syvxbt)Photo by SYV ★ (@syvxbt)Photo by SYV ★ (@syvxbt)Photo by SYV ★ (@syvxbt)Photo by SYV ★ (@syvxbt)Photo by SYV ★ (@syvxbt)
SYV ★ retweeted
pippenger
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
2
4
38
785
SYV ★ retweeted
x16
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
4
4
57
2,273
SYV ★ retweeted
Our internal Loops agentic security infra has identified and reported another critical bug in a friendly privacy project, with the highest tier bounty now awarded. Details later. If you are building something crypto-adjacent, dm me to run an initial scan on your repo (for free).
6
8
1
74
1,736
SYV ★ 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
57
4,744
SYV ★ retweeted
This new paper entered our autonomous pipeline at 07:34, roughly an hour after publication, in connection to @octra stealth payments. It was initially dismissed as irrelevant, but challenged, and an offline test was constructed with an independent X25519 by 16:10. Sender and recipient agreed in 256/256 trials, the code rejected 112/112 tested low-order inputs, and a third key matched the holder’s tag in 0/1,000 trials. God bless computer science! Full paper: arxiv.org/abs/2611.22290
Cool new source of hypotheses in addition to arXiv + IACR feeds: using (free!) @grok bot to gather and commit a daily technical summary of new research, hacks, exploits, disclosures and crypto security threads published on X. Loops fetch it and rerun it against all open records:
4
4
3
54
2,628
SYV ★ 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
73
3,077
SYV ★ retweeted
minor improvements to the mainnet are currently being delivered
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.
5
4
1
60
3,115
SYV ★ 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
80
5,877
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
30
29
7
142
7,613
SYV ★ retweeted
let's hack
We've added a security policy and enabled GHSA for core repos (currently webcli and lite_node). All reports go through our Loops pipeline and are transparently mapped to existing timestamped records as shown. Genuinely new findings may be rewarded if proven useful and reachable.
6
45
976
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
6
5
1
60
2,151
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
12
20
3
88
4,710
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
9
11
3
78
3,893
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
16
23
4
90
4,408
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…
5
15
3
69
3,195
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…
5
13
63
1,816
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…
7
7
4
73
4,540
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
5
18
5
77
6,531
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!
4
10
80
1,567
SYV ★ retweeted
did someone else notice the shift? – at London, England
12
11
2
93
5,251