i built this. open-source non-custodial stablecoin payments.
no custody. no upgrade keys. no chargebacks.
@secudigate launched yesterday
would love your eyes on it.
secudigate is live.
open-source. non-custodial. multi-tenant stablecoin payment gateway.
solidity contract live on sepolia. 157 tests, 80 of them adversarial.
→ https://t.co/BMyEdqy7sd
→ https://t.co/bfWVtoEOSP
Web3 freelancing red flags nobody talks about:
→ "We'll pay in our token" (no)
→ No test task, straight to full commitment
→ They can't explain what the contract actually does
→ Urgent deadline with no clear scope
The client who respects your process will respect your work
Most Next.js apps I review have the same mistake:
Fetching data on the client that should be fetched on the server
- Slower page load
- API keys exposed to the browser
- Unnecessary loading spinners everywhere
Move your fetches to Server Components.
Your security will thank you
@PatrickAlphaC Happy birthday Patrick!
I’ll never forget that you told me, ‘There’s light at the end of the tunnel,’ when I was at the deepest point of darkness❤️
The checks-effects-interactions pattern is the single most important habit in Solidity.
Check conditions first.
Update your state second.
Call external contracts last.
Flip that order and you've written a reentrancy vulnerability.
The DAO hack in 2016 was $60M of ignoring this
@alexwtlf The gap is widening faster than people realize. A builder with AI now ships what a team of 5 shipped two years ago. Consuming the same tools just makes you a better consumer.
@austingriffith@clawdbotatg x402 + ERC8004 as a funding layer for dapp pipelines is an interesting combo. The container framework for workers is the part I want to dig into, that's where the real complexity lives.
@leerob Point 4 hits hardest. A GitHub full of tutorial clones tells me nothing. One original project where I can see your decision-making in the commits tells me everything.
3 smart contract mistakes I see constantly from web2 devs moving to Solidity:
→ Trusting msg.sender without access control
→ Not accounting for reentrancy on external calls
→ Storing sensitive data on-chain (it's public, always)
Web2 habits don't transfer 1:1.
@brian_armstrong This is exactly why on-chain orderbooks are interesting long term — no AZ, no chiller, no co-location tradeoffs. Not saying CEX is going away, but incidents like this sharpen the "why decentralize" argument.
@FrankFred834567 Exactly this. Trading gives you market intuition but zero builder intuition. The mental model shift from "price goes up/down" to "how does this contract actually work" is huge, and most traders never make it.