Creează un cont pentru a te abona la acest blog și a-i urmări articolele pe pagina Lectură.
-
Eighty-five pull requests of a live delta-neutral bot on Hyperliquid and Kraken Futures.
-
Part two of the DarkFi Pi: the node grew to 4.5 GB and was taking the host down with it.
-
Notes from turning a Raspberry Pi 5 into a 24/7 DarkFi testnet node and miner: NVMe boot, self-hosted WireGuard, the ARM dependency trail for darkfid and xmrig, and a look at the ZK circuits the node deploys on startup — including the v3a exploit that sat…
-
Notes on migrating from Anchor 0.29 to 1.0 while following RareSkills' Solana course.
-
Notes from implementing the first Cryptopals challenges in Rust without libraries: hex, base64, XOR, frequency analysis, Hamming distance, and breaking a repeating-key cipher.
-
Full forensic analysis of a targeted supply chain attack delivered through a fake Web3 job interview.
-
A tiny std-only DAG executor that computes only the requested outputs (partial evaluation) and runs heavy nodes in parallel with explicit bounds.
-
A rollup-shaped batch pipeline modeled as a DAG: compute only the chunk/proof you need, and scale CPU-heavy hashing with bounded parallelism — all in std.
-
How to verify max_in_flight bounds using AtomicUsize, CAS loops, and deterministic gating without sleep().
-
How I introduced bounded backpressure into a parallel DAG scheduler using sync channels and an in-flight cap.
-
Why heterogeneous closures require type erasure, how trait objects become unsized, and why 'static is necessary when storing tasks.
-
A small, reproducible ZKML lab: train a CNN, export ONNX, compile an EZKL circuit, generate keys, prove & verify inference — then benchmark the practical tradeoff that matters on consumer hardware: numerical fidelity vs prover memory / PK size.
-
A small Rust lab that vendors microsoft/crescent-credentials, generates Crescent test vectors, and benchmarks zksetup/prove/show/verify across several parameters — including proof sizes and selective disclosure variants.
-
A Rust mini-lab that turns a Vickrey (second-price) auction into a TEE coprocessor: deterministic core, bid commitments, replay protection, and a policy-driven verifier—leaving full DCAP collateral/TCB verification (PCS chain, revocation, freshness rules)…
-
A mini Rust lab that implements a baby version of Ligero's three tests — proximity, multiplication, and linear — for a tiny arithmetic circuit, and uses them to see soundness amplification in action.
-
A hands-on Rust experiment exploring why folding causes norm blowup in lattice commitments, and how decomposition keeps the digits small — the core idea behind LatticeFold and LatticeFold+.
-
From Vadim Lyubashevsky's lattice-based SNARKs whiteboard to a tiny Rust lab: SIS commitments, a proof of knowledge, and a soundness experiment.
-
Hands-on NTT benchmarks over BabyBear and Goldilocks fields, connecting Jim Posen’s ZK Hack talk on high-performance SNARK/STARK engineering to real Rust code.
-
Final milestone wrap-up: IcRamp v2 with a simplified vault, ICP-driven state instead of on-chain commit/uncommit, and ic-alloy-powered EVM reads for getDeposit.
-
We finish the pay-with-crypto flow: from Locked orders to on-chain payments, matching provider assets, and verifying EVM/Solana txs on the backend.
-
Practical Learnings from ZK Hack with JP Aumasson with hands-on benchmarks: SHA-256/512, BLAKE3, Poseidon.
-
Frontend wiring for the experimental 'pay with crypto' path: crypto providers in the user profile, filtered provider selection in Create Order, and a compact order card UX for onrampers choosing how to pay.
-
We add an experimental 'pay with crypto' path that lets onrampers settle in stables on a different chain than the escrowed asset.
-
We add partial fills: the onramper can lock only a fraction of the order, pay, and get a proportional crypto payout while the rest stays open.
-
Added liquid (top‑up) orders and unified provider icons across the app.
-
End-to-end Stripe payments for orders: Onramper pays by email, Offramper receives via Connect destination charges.
-
Frontend wiring for Stripe Connect: a register flow that survives redirect/refresh, provider cards UI, and Create Order with destination charges.
-
Starting Milestone 2: bringing Stripe Connect (destination charges) into icRamp with IPv6-friendly HTTPS outcalls, multi-region key routing, and Candid-first tests.
-
I debugged the PnL, refactored the messy code we left implemented in our last devlog and made everything more compact and debuggable.
-
I stress-tested a one-sided, USDC-anchored LP strategy overnight: ~15 rebalances, lots of fee accrual, a few bugs, and a clearer picture of what to fix next.
-
I moved position funding and settlements to a USDC base, fixed a sneaky PnL bug (price/mint orientation), taught the monitor to chill (cooldown + “in-range = HOLD”), and battle-tested open/close scripts with ledgered flows.
-
I rewired RPC handling with role-based profiles, unified LP strategy controls, fixed PnL accounting, and executed a live one-sided rebalance on a PUMP/USDC DLMM pool over gRPC—end to end with Supabase ledgering.
-
Before we let the monitor act on positions, we hardened the boring bits: one source of truth for decimals, fast prices, safe BigInt math, and clean balance reads.
-
I stripped our Telegram surface down to a fast, durable “Lite” mode: no Kafka, no AI agent in the middle—just clean wallet UX, on-chain balances via RPC, token prices from Jupiter, PnL wired to Supabase, and buttons that actually do something.
-
We wire a minimal orchestrator with a primed LP-copy scanner and a policy-driven monitor that runs in dry-run, notifies via Telegram, reads positions from Supabase, and calls execution logic via imports (no gRPC).
-
We build a robust scanner that reads a leader’s recent transactions and extracts DLMM position inits as (poolAddress, positionPda) intents — no brittle bin-array decoding, just clean signals my scheduler can act on.
-
Kicking off a new series: revive the old defi_server stack I built at Taigo, drop a new bot/ module on top, and ship a scheduler that can copy-trade Meteora LPs — with PnL tracked and later expanded to memecoins, xStocks, and perps.
-
Final wrap-up for the Solana Integration milestone: 5-min demo, slides, deliverables checklist, tests, and canister URLs.
-
We finish the vault branch for SOL and SPL: deposits, cancels, locks, unlocks, and completion — entirely in-canister state.
-
We include the Solana token registry tests (incl.
-
We continue the Solana testing story by building a clean HTTP-outcall mocking layer, composable responders, and readable integration tests.
-
We refractored and improved our testing architecture and expanded it to include a fully-fledged solana backend canister integration test flow.
-
Let's create some spl tokens so we can generate a fully fledged test with orders containing solana tokens.
-
Everything is ready for us to create orders in the frontend containing solana and executing the full offramping flow.
-
Third Chain Fusion grant log: adding solana wallet adapter in the frontend.
-
Third Chain Fusion grant log: wiring icRamp's core backend with the Solana canister, persisting canister IDs, and preparing escrow flows for SOL/SPL assets.
-
Third Chain Fusion grant log: wiring icRamp's core backend with the Solana canister, persisting canister IDs, and preparing escrow flows for SOL/SPL assets.
-
Second Chain Fusion grant: building a Solana canister with safe token registry and a thin vault to coordinate escrow.
-
Design decisions, trade‑offs, and the fully on‑chain architecture that won 🥈 in 1inch’s Fusion+ → ICP track.
-
Bringing Bitcoin and Solana native actions to ICP: setup, pitfalls, and tests.