Money events that are never processed twice or lost
On the tokenized-stocks platform I owned the event publisher: the service that turns on-chain events from Kafka into API events. Scroll to follow one event through it.
Kafka delivers at least once
On-chain events arrive from Kafka at least once, so the same event can show up twice. The publisher has to handle that, not hope it never happens.
Seen before? Skip it.
Every event is checked against a permanent dedup record. A redelivered event is recognised and skipped, so it is never processed twice.
New events go out once
A new event is enriched and published once as an API event. Writes go through an API that takes idempotency keys, so a retry can't create a second record.
Failing events are parked, not lost
An event that keeps failing goes to a dead-letter queue after its retries. It waits there, visible, instead of disappearing.
- Tokenized-loan marketplace backend: NestJS, MongoDB, gasless EIP-7702 UserOps
- EVM indexer proof of concept: chain-reorg handling, RabbitMQ
- Fund contracts: found and fixed a yield-theft vulnerability before deployment
- Deployment: AWS, Terraform, Kubernetes, GitHub Actions
