
Idem
Let AI agents reconcile & audit stablecoin payments
7 followers
Let AI agents reconcile & audit stablecoin payments
7 followers
Most stablecoin infra stops at settlement — matching transfers to ledger state is still manual. Idem gives AI agents an MCP server to reconcile transactions, roll back mismatches with compensating transactions, and write HMAC-signed audit trails before execution completes. Self-hosted, source-available, running against a real ledger via docker-compose — not a hosted black box.


Hey PH 👋 I'm Italo, building Idem from Recife, Brazil.
I spent the last decade shipping fintech infrastructure — XP Inc, dLocal, Caliza — and kept hitting the same problem: fintechs moving money on stablecoin rails had no ledger that could account for both fiat and on-chain entries in the same double-entry model.
Everyone was building it from scratch, in spreadsheets, or bolting something onto Postgres at 2am before an audit.
So I built Idem.
What makes it different:
→ MonetaryEntry is a sealed class — FiatEntry or OnChainEntry. The double-entry invariant holds regardless of whether the entry is ACH or USDC on Base.
→ Chain readers for EVM, Solana, and Tron auto-post ledger entries when transfers confirm. PendingSettlement goes WATCHING → SETTLED automatically.
→ Agentic engine: PolicyGuard, AgentAuditEvent (written BEFORE execution, HMAC-signed), WorkflowOrchestrator, RollbackService. Exposed as MCP tools — Claude Code can reconcile your ledger and roll back failures.
→ Travel Rule (IVMS 101) detection. Non-blocking — transfers commit and queue for compliance review.
→ FSL licensed. Free to self-host forever. docker-compose up in 5 minutes.
The MCP demo video shows all of this running against a real local ledger — no staging data.
Would love your feedback, your star on GitHub, and especially to hear from anyone building cross-border payment infrastructure.
github.com/idem-finance/idem
One week since Idem launched. Here's what happened.
8 GitHub stars
19 Github Clones
3 Docker Hub / Github Packages pulls
55 Maven Central downloads
155 idem.finance visitors
8.340 LinkedIn post impressions
3 conversations started
What I expected:
I expected the open-source release to be the hard part. It wasn't — docker-compose up in 5 minutes did what it was supposed to. The hard part was getting from "cool repo" to "someone with a real reconciliation problem actually talks to me.
What surprised me:
How specific the right people were. Three strangers described their own reconciliation pain back to me almost word-for-word before I said anything. That's the validation the star count doesn't show.
What's next: idem-infra (GCP São Paulo), Cloud SaaS provisioning, first pilot customer.
If you're building cross-border payment infrastructure and want to be an early user — reply or DM.
https://lnkd.in/dJFZKgbJ
HI PH!
I wrote up how Idem was built.
Not a product announcement — the actual decisions: why a Kotlin sealed class is the right foundation for a financial entry model, what I built wrong the first time, and why the reconciliation problem in stablecoin payments is harder than it looks.
Three things I'd have done differently:
→ Started with Alchemy webhooks, not polling
→ The PendingSettlement model went through 3 iterations before the AccountId vs TransactionId distinction was clear
→ Should have decided the FSL license on day 1, not after 3 months of building
Full article: https://medium.com/@ifsantana/how-i-built-an-open-source-ledger-for-stablecoin-cross-border-payments-e22965c6d2d3?sharedUserId=ifsantana
GitHub: github.com/idem-finance/idem
Week 2 update: Agent Finder independently reviewed Idem — 7/10.
They actually tested it: deployed it, deliberately broke a workflow mid-execution, and verified the HMAC signing behavior.
Honest feedback on what's missing (managed cloud, thinner docs) — both fair, both on the roadmap.
agent-finder.co/reviews/idem