SergeyWh1te (@PRSergeyWhite) profile picture

Zero-knowledge & encryption • Building high-load systems • Privacy-first

Joined June 2014
Photo by SergeyWh1te (@PRSergeyWhite)Photo by SergeyWh1te (@PRSergeyWhite)Photo by SergeyWh1te (@PRSergeyWhite)Photo by SergeyWh1te (@PRSergeyWhite)Photo by SergeyWh1te (@PRSergeyWhite)
SergeyWh1te retweeted
hashcat v8.0.0 released! The largest update in the history of hashcat, with PCFG attacks, hash recipes that crack hashes without a hash-mode, and bcrypt on FPGA boards. Release notes: github.com/hashcat/hashcat/b… Download: hashcat.net/hashcat/
24
423
33
2,043
93,769
SergeyWh1te retweeted
Just usewisp.io to stay private 🥷
Private AI is going mainstream. This week, OpenAI introduced Private Intelligence, joining Apple, Google and Meta in building AI systems that keep user data private on their own platforms. At the same time, Private AI infrastructure is being built for anyone to use, build on, or run on their own servers. Below is a full market map of the Private AI ecosystem, from silicon to apps. Full article coming soon.
2
2
7
209
If there is anyone out there from US or EU publishers for children’s books, I’m willing to donate the text and illustrations to this book for it to become available in US and EU.
11
15
3
91
3,680
Open-sourced my production-ready Go service template 🚀 ✅ Clean layered architecture (handler → usecase → repo) ✅ Postgres + migrations via make ✅ log/slog, Prometheus, golangci-lint v2 ✅ Docker Compose + Postgres 17 github.com/sergeyWh1te/go-te… #golang #opensource #backend
1
212
SergeyWh1te retweeted
Разработка в мае 2026ого: - твой модный макбук на m5 взломан - ядро LTS сборки линукса на твоем сервере раздвигает ноги и выдает root права всем подряд - nignx на твоем сервере выполняет произвольный код - github проебал твои приватные репозитории и/или нахуй по ошибке тебя забанил и ему похуй - расширения в твоем VSCode давно спиздили все секреты - npm/pypi пакеты выкачали всю твою крипту - google по ошибке тебя забанил и ты потерял доступ ко всем outh сервисам, а твой бэк на GCP просто больше не существует - chrome на виде вьебал твои пароли и куки - claude уже давно спиздил весь твой говнокод, все идеи, все решения, взял с тебя за это бабки и, возможно, забанил тебя/всю твою контору - openai на похуй попытался списать с твоей карты пол ляма баксов, так чей-то левый навайбкоженый говно-сервис давным давно вьебал CVV и прочие данные Достойно
25
76
7
1,159
66,738
You have no excuse any more for not using post-quantum cryptography. I have you covered on desktop, cloud, mobile and web. 🤓 #rust #golang #flutter #typescript
26
23
5
282
13,735
It’s 2026, and I still can’t believe how good cargo is.
8
2
84
3,284
SergeyWh1te retweeted
A newly created wallet(0x81d0) withdrew 10,057 $ETH($33.68M) from #Binance and staked it on #Lido to receive $stETH. Then deposited the $stETH into #Aave, borrowed 45M $USDT to buy 13,461 $stETH, and deposited the $stETH back into Aave. debank.com/profile/0x81d0ac9…
58
26
9
477
124,041
Just shipped abigenx — a tiny CLI wrapper around abigen. It scans ABI JSONs, generates Go bindings, fixes all_caps_with_underscores methods, and can emit event topic constants. Includes a demo app + usage example. github.com/sergeyWh1te/abige… #golang #ethereum #web3 enjoy, repost 🥳
57
SergeyWh1te retweeted
6 books I recommend to every auditor: • Mastering Ethereum • Uniswap V3 Development • Upgrading Ethereum • Chainlight. Web3 Hacks • Web3 Security made easy • Tornado cash book It's literally must have read
28
91
6
743
32,825
SergeyWh1te retweeted
if you want to understand the math behind 3D graphics, machine learning, and simulations. > this book explains vectors, matrices, calculus, and probability the way developers actually use them; > perfect, if you wanna aid your intuitive problem solving by grounding it in math
7
145
3
1,170
40,850
SergeyWh1te retweeted
You will learn the basics of ZK after reading this thread.
7
45
9
362
25,799
🐖
24
72
22
2,009
128,448
SergeyWh1te retweeted
Gist of Go: Concurrency is out! Learn Go concurrency from the ground up with 50 auto-tested exercises and tons of interactive examples. It's a full course + book in one. antonz.org/go-concurrency
18
109
3
712
37,177
As a Rust engineer, please learn: --- Foundation (Beginner → Competent) The fundamentals that separate “I can write Rust” from “I understand Rust.” - Core Language - Ownership, Borrowing, Lifetimes (the real entry exam) - Result, Option, pattern matching - Slices, strings, references, iterators - Traits & generics (parametric polymorphism) - Error handling (thiserror, anyhow) - Cargo workspaces & dependency management Mental Models - Move semantics vs Copy semantics - Zero-cost abstractions - Stack vs heap & how Rust allocates - Why Rust is not like C++, Go, or Python Must-Learn Tools - cargo test, cargo bench, cargo fmt, clippy - rust-analyzer --- Architecture (Intermediate → Solid Engineer) - Systems Patterns - Traits as interfaces - ZST strategy types & compile-time polymorphism - Phantom types for type-level invariants - Smart pointers (Arc, Rc, Weak, RefCell) - Concurrency primitives (Mutex, RwLock, channels) - Async Rust (tokio, async-std, executors) Memory & Performance - Profiling (perf, flamegraph, cargo profiler) - Allocation patterns (Box, arenas, bump allocators) - Minimizing clones - Struct-of-arrays vs Array-of-structs - Cache friendliness Async & Networking - tokio::spawn, cancellation, backpressure - Streams, pinning, async lifetimes - Building servers with axum, warp, hyper --- Advanced (Production-Grade Rust Engineer) This is where Rust becomes a superpower. - Advanced Type System - Higher-ranked trait bounds (HRTBs) - GATs (generic associated types) - Advanced lifetimes & variance - Type-state programming - Custom derives & procedural macros Unsafe & FFI - Safe wrappers around unsafe code - Writing bindings to C/C++, Python, Zig - Understanding UB, aliasing rules, and memory models Data Structures - Lock-free structures - Custom allocators - Building your own iterator adaptors - Arena allocators for high-performance workloads Concurrency & Parallelism - Work-stealing runtimes - Custom executors - Actor models (e.g., building your own mini-Actix) --- Production (Deploying Rust in Real Systems) Most engineers fail here — Rust doesn’t forgive sloppy production design. - Engineering Practices - Deterministic error handling - Observability (OpenTelemetry, tracing spans) - Feature flags - CI/CD checks (fmt, clippy, tests, benches, docs) - Load testing & regression benchmarking System Design with Rust - Building high-throughput services (100k–1M RPS) - Understanding Linux syscalls & epoll - Backpressure handling - Graceful shutdown & cancellation - Horizontal scaling architecture Security & Safety - Memory-safe FFI boundaries - Sandboxing & capability-based design - Auditing unsafe blocks --- Frameworks & Ecosystem - Web → Axum, Hyper, Actix - DB → sqlx, SeaORM, SurrealDB client - Messaging → Kafka, NATS, MQTT clients - Agents/RAG →Ollama bindings, Candle, Burn
As an AI engineer. Please learn: Foundation: - Vector Databases (Pinecone, Weaviate, Qdrant) - Embedding models & similarity search - Prompt Engineering & Chain-of-Thought - LLM Evaluation metrics - Token optimization & cost management Architecture: - RAG patterns (naive, advanced, hybrid) - Agentic AI (ReAct, tool use, planning) - Multi-agent orchestration - MCP & standardized protocols - Memory persistence (vector + conversational) - Streaming & async patterns Production: - Model Fine-tuning (LoRA, QLoRA) - Function calling & structured outputs - Guardrails & safety systems - Production monitoring & observability - Cost optimization at scale Frameworks: - Agent frameworks (LangChain, LlamaIndex, CrewAI) - OpenAI Assistants API / Claude Computer Use Stop jumping from OpenAI to Claude to Gemini to Llama. Bookmark this for AI Learning roadmap. Pick one API. Build something real. The prompt patterns are 90% the same. The job market wants people who can ship production AI systems, not switch models.
22
101
12
973
113,711
Gonna be a fun night for many teams
🚨 CRITICAL RCE ALERT: React & Next.js Vulnerability ↓ Critical remote code execution (RCE) vulnerabilities have been published affecting the React 19 ecosystem and Next.js. These vulnerabilities (CVE-2025-55182 & CVE-2025-66478) reside in the React Server Components (RSC) "Flight" protocol. They allow unauthenticated attackers to execute arbitrary code on the server by sending a specially crafted HTTP POST request. → Severity: Critical. → Vector: Remote, Unauthenticated. → Success Rate: Near 100% in default configurations. → Affected: Standard deployments of Next.js (App Router) and React 19. 🟢 Immediate action required: Patch. There are no workarounds other than patching. Security teams must prioritize upgrading dependencies to hardened versions immediately. — Read our full technical breakdown and remediation guide here: wiz.io/blog/critical-vulnera…
2
5
1,199