Database & OSS correctness

I reproduce database bugs and turn them into focused, tested patches.

I help database and open-source infrastructure teams isolate correctness failures in transactions, WAL and cache behavior, query semantics, schema changes, and CI, then deliver the smallest reviewable fix.

  • Fixed scope
  • Written acceptance criteria
  • Scope and budget agreed before code

Selected merged fixes

Public proof from database, transaction, concurrency, and storage work. Each link opens the reviewed pull request and its regression coverage.

WAL / cache

Turso savepoint rollback fix

Fixed stale WAL-frame cache state after savepoint rollback, added deterministic simulator and integration coverage, and received the full $1,000 challenge reward.

View merged PR #6626
Query semantics

Turso ordinal ORDER BY/GROUP BY fix

Corrected SQLite-compatible ordinal resolution through COLLATE and parentheses, with focused regression coverage.

View merged PR #6700
Transactions

Turso DETACH transaction guard

Prevented DETACH while read or write transactions are active and added SQL tests for the protected behavior.

View merged PR #6521
Schema concurrency

Spice.ai Turso schema gate

Added a per-pool schema gate so DDL waits for active Turso writes, with concurrency regression coverage.

View merged PR #10940
Race condition

Tari stealth fee claim fix

Fixed a cross-block validator-fee claim race by bounding withdrawals to the proof snapshot, with engine-level regression tests.

View merged PR #2356
Windows / Rust

Uteke locked-file loading fix

Fixed Windows error 33 by reading a vector index through the existing locked handle instead of opening a conflicting second handle.

View merged PR #747

What I take on

One concrete correctness problem at a time, with an evidence-first workflow and a deliverable that fits the repository.

Transactions & storage

Correctness under state changes

Savepoints, WAL and cache state, transaction guards, schema changes, file locking, and concurrency failures.

Output: reproducible failure and verified behavior.

Queries & testing

Semantics and regression coverage

Ordering, grouping, constraints, compatibility edge cases, deterministic simulation, and differential testing.

Output: targeted coverage that prevents recurrence.

OSS delivery

Review-ready patch delivery

Small repository-aligned diffs, focused validation, clear technical notes, and follow-through during maintainer review.

Output: a patch maintainers can evaluate quickly.

A clear path from issue to fix

No open-ended unpaid implementation. The issue, evidence, acceptance criteria, price, and target date are agreed before coding starts.

Send the issue

Share one repository or issue link and the behavior you expected.

Check fit

I identify missing evidence, setup risk, and whether the scope is realistic.

Agree scope

We confirm the output, acceptance criteria, fixed price, and target date.

Reproduce and fix

I reduce the failure, explain the invariant, and implement the focused change.

Verify and hand off

You receive the evidence, regression test, patch, and agreed review follow-up.

Fixed-scope packages

Choose the smallest useful starting point. Final scope depends on setup difficulty, issue complexity, and public or private access.

Evidence first

Bug Reproduction Audit

$250 to $600

  • One reported failure or suspicious behavior
  • Repository and environment setup
  • Smallest reproducible case
  • Evidence and root-cause hypothesis
  • Recommended next step
Check fit
Ongoing queue

OSS Correctness Block

$1,000 to $3,000

  • One repository and an agreed issue queue
  • Triage, reproductions, tests, and small fixes
  • CI investigation where relevant
  • Weekly shipped-work summary
  • Defined block length and acceptance criteria
Discuss a block

Available for fixed-scope work

Send one concrete failure.

I will reply with the missing evidence, the best-fit package, and a clear scope to approve before implementation starts.