Urgent.News

What's breaking now, across thousands of outlets.

Tech

I checked whether my readers were real, and the answer was 44 wallets for 44 payments

For a month my Subnano dashboard showed payouts arriving and I treated that as proof that strangers were paying for my writing. It is not proof of anything. A payout record tells you money reached you. It does not tell you who sent it, and if the same wallet sends it every time, you are looking at your own test loop with extra steps. So I did the only check that answers the question. I took every…

A reporter examining their payout records discovered 44 distinct wallets received 44 separate payments over a month's time. This led them to question whether their readers were real people or just test accounts. The payout records alone are insufficient proof, as they show only that money arrived, not who sent it. To verify, they traced each payout back to its originating block and recorded the sending account.

Each of the 44 payments came from a different Nano address, with no repeats. This directly answers whether payments came from unique individuals or a single test loop. The method, explained in three steps, is inexpensive and reproducible by anyone. The reporter found that all buyers made only one purchase, indicating readers are one-time rather than returning.

This insight shifts focus to attracting new readers for the highest-value work. The same process applies to other revenue streams like agent payments or platform credits. The reporter's findings are documented in a repository, allowing others to duplicate the audit for any blockchain where money is sent to a specific sender address.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Your Coding Agent Knows the Rule. So Why Does It Keep Breaking It?

You tell Claude Code not to modify a particular interface. It acknowledges the instruction. It fixes the code. A few sessions later, it makes the same mistake again. You add a rule to CLAUDE.md .

  • Claude Code follows instructions but fails to apply them consistently.
  • User provides guidance on testing procedures, yet agent ignores verification.
  • Adding more rules to CLAUDE.md doesn't guarantee agent will follow them.

RentDera at RevenueCat Shipaton 2026: We Didn't Win, But We Shipped

Not every hackathon story ends with a trophy. Sometimes, it ends with a certificate, a live product, lessons you couldn't have learned by planning alone, and a reason to keep building.

  • RentDera, a rent management product, developed by Sanjay Sah
  • Participated in RevenueCat Shipaton 2026 hackathon
  • Continued development beyond hackathon despite not winning

Key Management & Encryption (KMS)

⚡ TL;DR: Encrypting data is easy; the hard part is managing the keys. Use envelope encryption with a KMS or HSM so you control where keys live, who can use them, how they rotate, and who audits them.

  • Key Management Service (KMS) protects secrets by managing encryption keys.
  • KMS never stores master key material in application memory or logs.
  • Envelope encryption uses master key to encrypt data key, which encrypts payload.

More from Monday 26 October →