_alphageek
Joined 6 months ago
Karma
50
Submissions
47
Member since
Apr 21
Backend engineer. Rust, Postgres, distributed systems.
www.ovasylenko.com
View on Hacker NewsRecent submissions
Comment · 1 month ago
Location: Brazil (UTC-3). Can work in European timezones too
Remote: Yes
Relocate: No
Tech: Nest, Node.js/TypeScript, React, PostgreSQL, AWS/GCP, Rust
Backend/system engineer, 18+ years of commercial development.
Available to start immediately
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/FullStack/Tech Lead — Node.js, React, Rust, Web3/crypto, AI infrastructure. Full-time or B2B.
CV: https://www.ovasylenko.com | [email protected]
Comment · 1 month ago
I remember the days when Stack Overflow would go down. People would actually start seeing each other's faces in the office kitchen.
Comment · 1 month ago
Wrapped findings while I was developing matching engine for crypto exchange. I never had time to summarize and write up these findings before. I hope it’s useful.
Comment · 2 months ago
Location: Brazil (UTC-3)
Remote: Yes
Relocate: No
Tech: Rust, Nest, Node.js/TypeScript, React, PostgreSQL, AWS/GCP, Rust
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 | [email protected]
Comment · 2 months ago
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.
Comment · 2 months ago
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.
Comment · 2 months ago
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.
Comment · 3 months ago
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 [email protected] / ovasylenko.com for any reason
Comment · 3 months ago
Location: Brazil (UTC-3)
Remote: Yes (remote only, US/EUR timezone overlap)
Willing to relocate: No
Technologies: Node.js/NestJS/TypeScript, React, PostgreSQL, Redis, RabbitMQ, Docker, AWS/GCP, Rust (Tokio, Axum, Tonic, WASM)
Résumé/CV: https://www.ovasylenko.com Email: [email protected]
Backend & systems engineer, 18+ years.
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.
Open to b2b contracts
Comment · 3 months ago
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.