Squash
playsThe T is home. Every shot is about getting back to it.
Buenos Aires --:--:--
Software engineer, ex-founder. Havana → Dubai → Buenos Aires.
Scroll01 — About
I studied computer science at the Universidad de La Habana. Since June 2021 I’ve been at Nethermind, on Ethereum and Starknet infrastructure. Along the way I founded Token Fleet in Dubai and built a few products of my own. I like the parts of a system nobody notices until they break.
Spanish at home. English at work. I switch without warning.
Payments, auth and backends, and the infrastructure under them. Follow one request through, and stop anywhere.
OAuth2 and JWT for identity, rate limits at the door, and anomaly detection for traffic that looks almost right.
auth ▸ token verified · under the limit · nothing odd
Typed services in TypeScript and Go, REST or gRPC between them, PostgreSQL underneath and Redis where it earns its place.
api ▸ validated · routed · one transaction
Stripe payments, KYC onboarding, idempotency keys and double-entry ledgers, and webhook reconciliation, so a retry never charges anyone twice.
ledger ▸ key seen before · no double charge · books balanced
At Nethermind: QA and DevOps for the Nethermind execution client across L1 and every supported L2, benchmarks and regression suites, and the early days of Juno, a Starknet client.
node ▸ client synced · benchmarks run · release gated
Test-first, CI that gates releases, Docker on AWS and GCP, and Prometheus and Grafana, so failures show up on a graph before they turn into an incident.
ci ▸ tests green · deploy out · dashboards quiet
Somebody has to be awake when the webhook doesn’t come back.
QA and DevOps for the Nethermind execution client, from L1 through every supported L2. Benchmarks and regression suites that gate releases, and Prometheus and Grafana across the node fleets.
I led the initial Juno team and started the implementation of Nethermind’s Starknet client, setting its early architecture and engineering practices.
Worked on Sedge, mapping the infrastructure behind one-command L1 node and validator deployments across execution and consensus clients.
Each went from zero to production-ready. None took on customers, and that was a call, not an accident: when the market or the numbers weren’t right, I shelved it rather than put people on something I couldn’t stand behind.
Payment flows, KYC onboarding and a transactional ledger, designed around emerging-market regulation. I pitched it to partners and investors myself.
A multi-tenant Go and PostgreSQL backend, REST and WebSocket, for point of sale, kitchen display and QR ordering, with an idempotent transaction ledger, Stripe payments and webhook reconciliation.
An applied-AI product, taken to production-ready and then parked, for the same reasons.
Among them, a billing and quota engine on a credit ledger, driven by payment webhooks, that keeps balances straight across concurrent jobs and retries.
Backend services and REST APIs for cross-border checkout and logistics: payment-gateway and card integrations, webhook reconciliation and idempotent order settlement.
Led engineering on a multi-chain wallet: key management, transaction construction and signing, and the APIs between the mobile app and the backend.
The T is home. Every shot is about getting back to it.
NBA from Buenos Aires means tip-off at 9 pm or 3 am. I watch both.
Cooking with my wife. The best meeting on the calendar.
The best way to learn a city is one cuadra at a time. Still learning this one.
A few are being written. Deciding which ones make the cut.
Updated · Sept 2026