---
title: "Damilare Agba (@BlankGodd) | Hashnode"
description: "Backend & Blockchain Engineer. Read the latest articles by Damilare Agba on Hashnode."
url: "https://hashnode.com/@BlankGodd"
---

@BlankGodd

# Damilare Agba

@BlankGodd · Joined January 2023

Backend & Blockchain Engineer

### [When a transaction lands in a different block, my payment monitor has to notice](https://agbad.hashnode.dev/handling-reorgs-in-a-payment-monitor?utm_source=hashnode&utm_medium=feed)

How my crypto payment monitor handles a re-mined transaction: block hashes on deposits, a re-anchor rule, and an EF Core ulong bug that wrote -1.

6 min read · [agbad.hashnode.dev](https://agbad.hashnode.dev/handling-reorgs-in-a-payment-monitor?utm_source=hashnode&utm_medium=feed)

[Nov 5](https://hashnode.com/posts/handling-reorgs-in-a-payment-monitor/6aec9bdde4540aa86f96da0a)

### [The square in my realtime bill](https://agbad.hashnode.dev/the-square-in-my-realtime-bill?utm_source=hashnode&utm_medium=feed)

Per-message realtime pricing meets all-to-all broadcast: why 10 people in a shared 3D space cost ~$10/hour, 100 cost ~$900, and what I built instead.

5 min read · [agbad.hashnode.dev](https://agbad.hashnode.dev/the-square-in-my-realtime-bill?utm_source=hashnode&utm_medium=feed)

[Oct 21](https://hashnode.com/posts/the-square-in-my-realtime-bill/6ad9148b68348ddddec2b3f8)

### [My Redis lock wasn't what kept deposit addresses unique](https://agbad.hashnode.dev/my-redis-lock-wasn-t-what-kept-deposit-addresses-unique?utm_source=hashnode&utm_medium=feed)

A fail-fast Redis lock, the Postgres row lock under it, Redis updates that wait for the commit, and a test that assumed Task.WhenAll means overlap.

6 min read · [agbad.hashnode.dev](https://agbad.hashnode.dev/my-redis-lock-wasn-t-what-kept-deposit-addresses-unique?utm_source=hashnode&utm_medium=feed)

[Oct 12](https://hashnode.com/posts/my-redis-lock-wasn-t-what-kept-deposit-addresses-unique/6acd011e374af6680337a694)

### [The dry run with nothing to roll back](https://agbad.hashnode.dev/the-dry-run-with-nothing-to-roll-back?utm_source=hashnode&utm_medium=feed)

A production Postgres migration: one column name holding two ID spaces, a zsh echo that swallowed every \\copy line, and row checksums over counts.

6 min read · [agbad.hashnode.dev](https://agbad.hashnode.dev/the-dry-run-with-nothing-to-roll-back?utm_source=hashnode&utm_medium=feed)

[2](https://hashnode.com/posts/the-dry-run-with-nothing-to-roll-back/6abba7ce71d37c6ab4f242a0) [Sep 29](https://hashnode.com/posts/the-dry-run-with-nothing-to-roll-back/6abba7ce71d37c6ab4f242a0)

### [A ₦1,500.50 listing nobody could book](https://agbad.hashnode.dev/a-1-500-50-listing-nobody-could-book?utm_source=hashnode&utm_medium=feed)

A decimal price broke checkout because one service stored money as bigint. Why we widened the column instead of rounding at checkout.

7 min read · [agbad.hashnode.dev](https://agbad.hashnode.dev/a-1-500-50-listing-nobody-could-book?utm_source=hashnode&utm_medium=feed)

[Sep 22](https://hashnode.com/posts/a-1-500-50-listing-nobody-could-book/6ab28e132e45b8b44d5eb441)
