Frojdi Dymylja

I build technology that deals with real value, at the intersection of markets and protocol engineering.

I'm drawn to work where a small mistake doesn't mean a bit of downtime, but broken accounting, a fork, slashed validators, or money going the wrong way. That's the pressure profile I'm comfortable with.

A large part of my work has been in the Cosmos stack — technology used in production by 200+ chains (Cosmos Network) and securing billions of dollars in digital assets (ICF overview).

I spend a lot of time on architecture, execution semantics, specs/ADRs, and failure modes — the boring work that makes systems defensible years later.

Things I've helped shape

Cosmos SDK

Framework for building application-specific L1 blockchains

github.com/cosmos/cosmos-sdk

Tendermint / CometBFT

BFT consensus + replication engine

github.com/cometbft/cometbft

IBC

Interoperability protocol for cross-chain data & value

ibcprotocol.dev

Rosetta

Coinbase's open standard for blockchain integrations

coinbase.com — Rosetta

Background

I didn't come to this work through a traditional academic path. I needed to start working early, so I learned by building systems in production and taking responsibility for their behavior. Over time, that shaped how I think: explicit rules, clear invariants, and designs I can defend under scrutiny rather than theoretical elegance.

I started by building trading infrastructure for a private trading firm in Italy. That environment teaches you quickly that throughput is rarely the real problem — correctness, partial failures, and risk boundaries are.

  • Built and scaled algos to six-figure req/s peaks, handling billions of events per day.
  • Designed execution logic, quoting engines, and risk constraints where "almost correct" is unacceptable.
  • The firm transitioned to crypto markets in mid-2017, which is where I first got deep exposure to blockchains and fell in love with the underlying philosophy.
  • I was also active on the trading side of crypto, including being at the top of a Binance leaderboard.

This still heavily influences how I think about protocol design and DeFi today.

Protocol engineering in the Cosmos stack

In the Cosmos ecosystem, I've spent years deep in consensus, stfs, state handling, interoperability, and production-only bugs. My work ranges from hands-on implementation to architecture and specification (ADRs), and from feature design to fixing correctness issues that only appear at scale.

  • Rosetta integration for Cosmos chains — Implemented Coinbase's Rosetta standard as a reusable integration surface for Cosmos-based chains.
    Article · ADR
  • ADR-036: arbitrary / off-chain signing — A spec for signing and verifying arbitrary data using Cosmos keys.
    Spec
  • Collections (typed state layer) — A typed state/storage layer that makes intent explicit and reduces footguns compared to raw KV access.
    ADR · PR
  • x/accounts (account abstraction) — Execution plumbing for programmable accounts, with explicit semantics around auth → execute → pay.
    PR · Context

Fault Tolerance

I founded Fault Tolerance and built a team focused on protocol engineering and DeFi work. faulttolerance.io

Protocol & security work

DeFi & trading infrastructure

  • Hands-on work on perpetual DEXes (e.g. Nibiru), trading systems, and execution/risk tooling.
  • Focus areas include market mechanics, liquidation paths, funding & position accounting, and edge cases that surface under real market stress.

How I work

  • Lead technical direction and execution planning.
  • Break down large protocol initiatives into defensible workstreams.
  • Write ADRs/specs and help teams reason about long-term execution semantics and state transitions.

Selected work (with receipts)

Cosmos SDK PRs (testinginprod)
Verifiable contribution history
View PRs
Cosmos SDK PRs (fdymylja)
Same, second account
View PRs
Osmosis: non-determinism fix under load
Prevents app-hash divergence under heavy query traffic
PR #7346
Cosmos SDK: slashing correctness fix
Security-sensitive staking logic must hold in edge cases
PR #20828
Collections (typed state layer)
Safer, clearer on-chain state handling
PR #14107
ADR-036 (off-chain signing)
Standardizes signing arbitrary data
Spec
Rosetta integration
Exchange/wallet-friendly integration surface
Article

Writing

I don't write often. If I publish something, it's because I think it's worth being durable.

Elsewhere