Sem_pre

5 ms·

1.
Ask HN: What are you using for DAO gov data after Tally (tally.xyz) shuts down?
1 points by Sem_pre 6mo ago|0 comments
2.
How AI Agents Should Pay for API Calls (X402 and USDC Verification on Base)(paragraph.com)
4 points by Sem_pre 7mo ago|0 comments
3.
by Sem_pre 7mo ago
Appreciate the thoughtful response — and yeah, the integration angle is interesting. PayWatcher as a verification layer for chains QBitFlow doesn't natively cover yet makes a lot of sense architecturally. Keeps your stack lean while ex
4.
by Sem_pre 7mo ago
Cool to see another founder tackling this — respect the hustle. I think we're solving different slices of the same problem. QBitFlow wraps authorization + verification in smart contracts. What I ended up building is just the verificati
5.
by Sem_pre 7mo ago
Agreed on self-custodied being the way to go. I went down the Alchemy webhook path initially and it works — until it doesn't. The edge cases pile up: reorgs on Base (rare but real), missed events when your webhook endpoint is down, dis
6.
Ask HN: How do you verify crypto payments in your app?
1 points by Sem_pre 7mo ago|5 comments
7.
by Sem_pre 7mo ago
The nonce serialization problem is real — cache locks work but get hairy at scale, especially if you need concurrent payouts. For the verification side (confirming stakes arrived), you might consider separating that from your sidecar enti
8.
by Sem_pre 7mo ago
Yes, USDC on Base for now. The architecture is token-agnostic though — adding USDT or DAI is mostly config, not a rewrite. Base was the starting point because of low fees and Circle's native USDC support. Which token/chain would b
9.
Show HN: How to Verify USDC Payments on Base Without a Payment Processor(paywatcher.dev)
7 points by Sem_pre 7mo ago|2 comments
10.
Show HN: Built a children's hospice donation site using AI agents as team in 8h(hoki.help)
1 points by Sem_pre 8mo ago|0 comments