Amazing article. Will save to explain ZKP to others.
One tiny correction
random.randrange(100) gives 300 possible commitments(3 colors for hundred nonces) After seeing a couple of revealed edges, the verifier can figure out the palette and brute-force all 300 combinations, effectively opening every commitment.
It can be mitigated if we use 128 bits of randomness, e.g. secrets.token_bytes(16).
Also I would use sha256 instead of hash. Python hash is not considered secure as it does not have proper collision resistance.
I have other way to do it. Never had a goal actually. There exists "God helmet experiments". You can actually buy a prototype from the one of the scientists who was working on experiment. Google "Shiva helmet system". After 3-4 sessions(once a week) I found that I can do lucid dreaming with no training. Moreover I can wake up 5 times at night and return back to the same dream without efforts. P.S it not advice or ad or proposals, I share my personal experience.
Absolutely. And scale does not matter. I had issues with top tier systems like docusign, tableau etc in beforeGPT era. Many undocumented issues and when you write support usually they only were pushing to buy top tier support package, but never fix anything.
I started it 3 months ago to see if I can optimize existing algorithms and grow it up in the huge framework. Though, I develop it in private repository for 3 months, some APIs are unstable and might be changed, GPU support is hardware-dependent. Current repository is a cut of stable/safe api from the private one.
It includes LLL, BKZ, CVP, enumeration, several sieves, arbitrary-precision arithmetic, and experimental Metal/CUDA paths.
Will be happy for any feedback or review shared.
Please contact me at hello@ovasylenko.com / ovasylenko.com for any reason
Three recent builds:
g6k-rs lattice reduction engine supports CPU/Metal/GPU with all contemporary algorithms: LLL, BKZ, Sieving, DeepLLL, Seysen etc with arbitary precision
Rust — Solo-built Orch8 (orch8.io), a durable workflow orchestration engine. 2,400+ instances/sec, <3ms latency. 7 crates, 3 SDKs (Node/Python/Go), 200+ integrations, built-in LLM tool calling and ReAct agent loops.
Node.js/NestJS — Matching engine for a crypto exchange processing 4,000+ orders/sec with sub-millisecond latency. Liquidity bots, candle engine, real-time WebSocket trading.
Looking for: Backend/Fullstack developer/Tech lead (Node.js or Rust), Web3/protocol engineering, or AI infrastructure roles. I care about product ownership and shipping - not process theater.
Intresting. Immovability becomes a property of the type (!Move) rather than the place (Pin), and the goal is to eventually deprecate Pin outright rather than paper over it with pin ergonomics. !Forge is what finally unblocks safe scoped spawn: handle that can't be mem::forgeten has a destructor that's guaranteed to run.
Location: Brazil (UTC-3) Remote: Yes (remote only, US timezone overlap) Willing to relocate: No Technologies: Rust (Tokio, Axum, Tonic, WASM),Node.js/NestJS/TypeScript, React, PostgreSQL, Redis, RabbitMQ, Docker, AWS/GCP, zk-SNARKs Résumé/CV: https://www.ovasylenko.com Email: hello@ovasylenko.com
Backend & systems engineer, 18+ years. Two recent builds: Rust — Solo-built Orch8 (orch8.io), a durable workflow orchestration engine. 2,400+ instances/sec, <3ms latency. 7 crates, 3 SDKs (Node/Python/Go), 200+ integrations, built-in LLM tool calling and ReAct agent loops.
Node.js/NestJS — Matching engine for a crypto exchange processing 4,000+ orders/sec with sub-millisecond latency. Liquidity bots, candle engine, real-time WebSocket trading.
Also: zk-SNARK wallet engine at Panther Protocol (cross-chain, UTXO model), micro-frontend migration at PropertyGuru (4 product teams). Led 15 engineers across 3 time zones.
Looking for: Senior/Staff Rust systems, backend architecture (Node.js or Rust), Web3/protocol engineering, or AI infrastructure roles. I care about product ownership and shipping - not process theater.
I have a weird feeling. Query body is encrypted by https. So CDN will not be able to cache results.
In order to make it work right - whole topology of the internet should be redone. Caching on the backend server will not give any real gains for large scale apps.
The whole connection is encrypted by https, the request body is treated the same as the url, the headers or the response. The only unencrypted parts are the IP addresses/ports and the domain name (if SNI without ECH is used).
CDNs already terminate TLS connections so they can cache GET requests.
Even past the TLS point (CDNs terminate TLS, so they can read the body) there's a harder problem nobody's solved: to cache a QUERY the cache has to fold the body into the cache key, and there's no standard way to canonicalize a request body. {"a":1,"b":2} and {"b":2,"a":1} are the same query and two different cache entries; whitespace, float formatting, unordered keys all fork the key. GET gets this for free because the URL is already a normalized string. So "cacheable in principle" is real, but "actually cached" needs every layer to agree on a canonical form first - the same coordination problem that killed GET-with-body. I want QUERY for the honest semantics; I just wouldn't budget for cache hits yet
> {"a":1,"b":2} and {"b":2,"a":1} are the same query and two different cache entries
These two payloads are actually different. You're talking about semantics, which is determined by the payload format; in the case of JSON, these two are semantically similar.
> GET gets this for free because the URL is already a normalized string
It's the same principle; the order of properties matters too.
Can you elaborate? Do you think the noted issues are non-issues that should be fixed in applications? Which would require a new standard to create stable JSON outputs, which is just one use case that can fail right now.
Location: Brazil (UTC-3)
Remote: Yes (remote only, US timezone overlap)
Willing to relocate: No
Technologies: Rust (Tokio, Axum, Tonic, WASM),Node.js/NestJS/TypeScript, React, PostgreSQL, Redis, RabbitMQ, Docker, AWS/GCP, zk-SNARKs
Résumé/CV: https://www.ovasylenko.com
Email: hello@ovasylenko.com
Backend & systems engineer, 18+ years. Two recent builds:
Rust — Solo-built Orch8 (orch8.io), a durable workflow orchestration engine. 2,400+ instances/sec, <3ms latency. 7 crates, 3 SDKs (Node/Python/Go), 200+ integrations, built-in LLM tool calling and ReAct agent loops.
Node.js/NestJS — Matching engine for a crypto exchange processing 4,000+ orders/sec with sub-millisecond latency. Liquidity bots, candle engine, real-time WebSocket trading.
Also: zk-SNARK wallet engine at Panther Protocol (cross-chain, UTXO model), micro-frontend migration at PropertyGuru (4 product teams). Led 15 engineers across 3 time zones.
Looking for: Senior/Staff Rust systems, backend architecture (Node.js or Rust), Web3/protocol engineering, or AI infrastructure roles. I care about product ownership and shipping - not process theater.
Backend/systems engineer, 18+ years.
Recent: g6k-rs — Rust lattice reduction (LLL/BKZ/sieving, CPU/Metal GPU); Orch8 — Rust durable workflow/AI engine, 2,400+ instances/sec; crypto exchange — matching engine, 4,000+ orders/sec, sub-ms latency.
Looking for: Backend/Systems/Tech Lead — Rust or Node.js, Web3/crypto, AI infrastructure. Full-time or B2B.
CV: https://www.ovasylenko.com | hello@ovasylenko.com
reply