SAMIUL A.

One chain hides its checksum in the casing, one bakes it into the encoding, and one skips it entirely. Lessons from validating deposit addresses on a payment platform that supported all three.

Token amounts on-chain are raw integers. The decimals field is per-contract metadata, and it changes between deployments of the same ticker. How we kept raw integers end to end and pushed the decimal point to the edges of a payment pipeline across Ethereum, TRON, and Solana.

A deposit scanner will see the same on-chain transaction more than once — after restarts, re-scans, and webhook replays. The fix is a database-enforced idempotency key, and picking the right one is less obvious than it looks.

Solana has no mempool to watch and three commitment levels to choose from. Building a crypto payment handler, we credited deposits only at 'finalized', trading twelve seconds of delay for finality the consensus rules can't undo.

On Solana, token balances live in their own accounts, and accounts cost rent. Sending USDC to a wallet that's never held it means someone pays ~0.002 SOL to create storage. Here's who, and why.

TRON splits fees into two independent resources: bandwidth and energy. A transfer can clear one and run out of the other mid-execution — here's what that looks like and how to avoid it.