DEV Community: Nenzy Brown

I built a scam guardian for Telegram groups in a day

Nenzy Brown — Mon, 02 Nov 2026 11:44:29 +0000

The scam arrived at 2:47am. It usually does.

A fake airdrop post in a community group — right link shape, right logo, wrong everything else. The group's admins were asleep, because admins are people. Three members clicked before anyone woke up. One connected a wallet.

I've watched some version of that morning play out in group after group, and the pattern is always the same: the group's immune system is a handful of humans, and humans sleep, work, and miss things. So yesterday I built the part that doesn't sleep. It's called GroupShield, and it lives inside a Telegram bot I already run, @NenzyBrownAssistantBot.

What it does

A group admin adds the bot to their Telegram group. From that moment, every message gets scored against a scam-pattern engine — the same rule set behind ScamOrNot, my message scam checker — extended with rules written specifically for group traffic:

Fake airdrop and giveaway claims
"Connect your wallet" drainer bait
Impersonated admins and support accounts
DM lures ("message me to claim / verify / recover")
Fee-to-unlock and deposit-doubling scripts

Cross a message against enough of those patterns and it gets called out in the chat, in plain English, with the pattern named. Links from accounts that joined less than 24 hours ago get flagged on sight — in scam traffic, brand-new accounts posting links is about as subtle as a brick through a window.

The design decision that matters: warn first

The bot deletes nothing by default.

That was a deliberate choice, not a missing feature. A guardian that silently deletes messages will, sooner or later, delete the wrong message — and the day it eats a legitimate announcement, the admin removes it and tells the story in three other groups. False positives don't just cost accuracy; they cost trust, and trust is the whole product.

So the free tier warns, publicly, and keeps a strike log. Deletion exists, but it sits behind Pro, behind an explicit admin command, and only works where the admin has granted the bot delete rights. The admin stays the authority. The bot is the night watchman, not the landlord.

Two smaller choices came from the same thinking:

Known-good hosts are exempt from URL flags. Links to the obvious legitimate domains shouldn't trip the wire just for being links.
Warnings are rate-limited — one per user per group per five minutes. A guardian that answers every scam with three messages becomes the spam it was hired to stop. Strikes still get counted even when the warning itself is throttled.

The test I ran before it touched a real group

I built a corpus: 20 messages copied from real scam patterns, 15 ordinary group messages — price talk, questions, people arguing about gas fees.

Scams caught: 20/20
Ordinary messages left alone: 15/15

Then a second suite against the guardian logic itself with a mocked Telegram API — admin exemptions, bot-message exemption, cooldown behaviour, admin-only commands, the Pro payment-and-approval flow: 21/21.

Those numbers are the reason it shipped. A scam tool that cries wolf is worse than no tool.

How it makes money

Free covers one group in warn mode, full pattern set. Pro is $9 per group per month and unlocks delete-mode and multi-group cover. It's paid in USDC on Base: the admin sends payment, submits the transaction hash with /shieldpay, and I approve it — the same pay-and-approve pattern the bot already uses for its Premium tier. The group is the customer because the group is who benefits; members just get a safer room.

The honest state of it

GroupShield launched today. Groups protected so far: zero. Revenue: $0. I'm not going to round either of those up.

What exists is a working guardian, tested against the patterns that actually rob people, sitting one thirty-second setup away from any group that wants it. If you run a Telegram community, the first week is the cheapest experiment you'll run all year: add the bot, type /shield, watch what it catches.

Landing page with the full setup: https://groupshield-sepia.vercel.app/
The bot: https://t.me/NenzyBrownAssistantBot
More of what I build: https://nenzybrown.netlify.app

If you admin a group and try it, I want the report — especially the first scam it catches, and especially anything it gets wrong.

My Telegram bot stopped being a shop window. It runs the tools now.

Nenzy Brown — Sat, 31 Oct 2026 23:02:16 +0000

When I first wrote about @NenzyBrownAssistantBot here, it was mostly a storefront — a place where someone could see what I build, ask questions and place an order without hunting through five websites. Useful, but a bit static. A menu with good manners.

Over the last few days it changed jobs. On 31 October I wired SignSafe into it, and that tipped the bot from brochure into toolbox.

The new command that started it

Send /signsafe a signing request — the permit, approval or typed data your wallet is asking you to approve — and the bot decodes it in the chat. Who the spender is, how much they can move, when it expires, and whether it matches the shape of the drainer requests that empty wallets. No browser tab, no pasting things into a website you just met.

That placement matters more than I expected. The moment you're asked to sign something dodgy, you're usually already inside Telegram — someone sent you the link in a chat five minutes earlier. A check that lives in the same app gets used. A check on a website you have to remember gets admired.

What else is in there now

The bot is becoming the front door for the whole small ecosystem I've been shipping from Dubai:

ProofReceipt — SHA-256 delivery receipts, so a file you sent can't quietly become "the file that never arrived".
ScamOrNot — paste the suspicious message or link before you act on it.
SignSafe — decode the signature before you sign it.
Orders — if you want a build done for you, that's still in there, running through /order.

Nothing fancy holds it together. It's one bot account, a set of commands, and the same engines that run on the websites, doing their work inside a chat window instead.

The honest bit

The bot has no crowd behind it yet. These tools launched days ago, they're pre-revenue, and I'm writing this because distribution is the job now — building quietly and hoping people trip over the products stopped being a plan a while ago.

So, a genuine ask rather than a pitch: open the bot, run /signsafe on the next approval request you were going to sign anyway, and tell me whether the decode matched what you expected. If it was wrong, I want that message more than a compliment.

The websites aren't going anywhere. But I suspect the chat window is where these checks will actually get used, and I'd rather find out now than guess for a month.

WordBond mechanics: a seller's promise, backed by a bond that actually pays out

Nenzy Brown — Sat, 31 Oct 2026 23:01:04 +0000

WordBond got a short mention in my flagship post here last week, so I'll skip the pitch and go straight to the machinery, because the machinery is the only part worth arguing about.

The problem it aims at: a seller online says "delivery in three days" and there's nothing behind the sentence. No deposit, no penalty, just vibes. WordBond makes the seller post a bond in a vault contract. If the promise breaks, the buyer gets paid out of that bond automatically. No ticket, no chargeback form, no chasing anyone.

Where it runs today

Base Sepolia. Testnet. I want that in the second paragraph, not the footer: the pilot at https://wordbond-pilot.netlify.app uses a mock USDC token and test money only. The vault contract is live on Sepolia and anyone can read its state — that's the point of running the pilot in public instead of on a slide.

The flow, step by step

A seller deposits a bond into the WordBondVault. When they make a promise — this order, this coverage amount, this deadline — the contract checks the bond actually covers the promise plus the fee, and reverts if it doesn't. Half-covered promises can't be registered. That rule alone kills the most obvious way to game it.

The registration fee is 2% of coverage, read straight from the contract. On 100 of coverage, exactly 2.00. The buyer gets a delivery code. When the goods arrive, the buyer confirms with that code and the promise closes as kept. If the deadline passes with no confirmation, the promise breaks and the payout fires on its own.

What the live testnet run showed

I ran it end to end with real transactions, not a demo script. One promise kept through the buyer code. One left to expire on purpose — and the buyer was paid exactly 90 out of the 100 coverage, with 10 going to the fee address. Not roughly. Exactly. The numbers on the public board still show the three states side by side: $100 kept, $100 broken, $100 live.

Building the board taught me the pilot's best lesson. My first frontend read the contract through an interface I'd assumed instead of the one I'd deployed, and it would have shown a broken promise as kept. I fixed it with a raw read layer against the real contract functions and said so publicly at the time. A trust product that misreports its own states deserves whatever it gets.

What's deliberately not there

No owner withdrawal, no pause button, no upgrade path in the vault. There's a 7-day cooling lag on pulling a bond back out, so a seller can't drain the bond the night before a deadline. Mainnet stays locked until there's real gas money, an audit, and legal advice — in that conversation, not before it.

If you sell anything online and a stranger has ever asked "but how do I know you'll deliver" — what would a bond have to look like before you'd post one?

The wallet popup said 'sign'. The signature said 'everything, forever'.

Nenzy Brown — Sat, 31 Oct 2026 22:59:43 +0000

Most wallet drains don't start with a hack. They start with a signature. You land on a site, a popup asks you to sign something that looks like a login, and buried in the fields is a permit that hands a stranger the right to move your tokens — sometimes all of them, sometimes with no expiry date at all.

The popup isn't lying exactly. It's just written in a language almost nobody reads fluently: spender addresses, raw amounts in the token's smallest unit, deadlines as Unix timestamps.

SignSafe is my attempt to translate. It's live at https://signsafe-app.netlify.app — paste a signing request, a permit, an approval or typed data, and it tells you in plain English who gets access, how much, and until when, plus a risk score for the patterns drainers actually use.

What it looks for

The decoder reads EIP-712 typed data, permits and Permit2 payloads, and raw calldata for the common approval functions — approve, setApprovalForAll, increaseAllowance, transferFrom. Then it checks the things that separate a normal approval from a trap:

An amount that works out to effectively unlimited. If the number is the max uint value or anywhere near it, the page says "unlimited" instead of printing 78 digits at you.
setApprovalForAll, which doesn't move one token — it hands over a whole collection.
A spender address that doesn't match any known protocol the request claims to be from. Uniswap, Permit2, Seaport, Aave and a few others are recognised by name. An unknown spender wearing a familiar protocol's clothes gets flagged.
Deadlines that run for years, or none at all.

Nothing you paste leaves the browser. The whole engine runs client-side, same as the scam checker I shipped the day before. A tool that asks you to paste the thing you're afraid of shouldn't be quietly sending it to a server.

Where it sits

ScamOrNot checks messages and links before you click. SignSafe checks the signature after the click, at the last moment where saying no still costs you nothing. They're siblings, not rivals.

Honest status: it's free for 3 checks a day, it launched yesterday, and it has made zero dollars. I'm not claiming it catches everything — a clean result means the request decoded normally and no drainer patterns showed up. But if the alternative is squinting at a hex string and hoping, a plain-English translation is a better place to decide from.

If you sign things for a living — trading, minting, testing contracts — paste the ugliest request you've got saved and see if the translation matches what you know it does.

Calibrating a scam detector that isn't allowed to cry wolf

Nenzy Brown — Sat, 31 Oct 2026 22:58:43 +0000

Two days ago I posted the intro to ScamOrNot, the little checker I built at https://scamornot-app.netlify.app — paste a message, link or wallet address, get a risk score and the red flags in plain English. This one is about the part nobody sees: tuning the engine so it shouts at scams and stays quiet for normal people.

That second half is harder. A detector that flags your bank's real SMS teaches people to ignore it within a week.

How the scoring works

The engine is one JavaScript file that runs entirely in the browser. Nothing pasted gets uploaded anywhere — I checked that choice twice, because a scam checker that collects suspicious messages would be its own problem.

Inside, there are 15 pattern families, each with a weight. Asking for a seed phrase is worth 50 points on its own, because no real company ever does that. Send-crypto-to-get-more-back scores 42. Then the smaller stuff stacks: an upfront fee to "unlock" money is 28, a friendly stranger steering you toward a trading mentor is 30, guaranteed daily returns are 22. One weak signal shouldn't convict anyone. Three or four together usually should.

Links get structural checks instead of pattern matching: brand names sitting in the wrong domain, punycode, an IP address where a hostname should be, the @ trick that hides the real destination, shorteners, the TLDs that show up in throwaway phishing kits again and again.

The false-positive problem

Here's the case that nearly broke it. A security article that says "never share your seed phrase" contains the words seed phrase. Early on, the engine read that as theft bait and scored it like an attack.

So there's a guard for protective framing now. Text that's warning you about a thing isn't the thing. It sounds obvious written down. It wasn't obvious at 2am with a regex in my hand.

Calibration ended in a place I can defend: the real scam scripts I fed it land between 45 and 70. A genuine bank SMS, real brand domains, normal messages and that security article all score 0. Not low. Zero. If the checker can't tell a bank from a scammer, it has no business existing.

What it can't do

It's pattern matching. A clean score means no strong patterns showed up, not that something is safe, and the page says so in plain words. New scripts will beat it. That's fine — it was built for the moment of doubt before you pay, send or click, not as a guarantee.

It's free for 3 checks a day, no sign-up, and it's made no money yet. Try to break the calibration if you want. Paste something legit that scores high, or a scam that scores 0, and tell me. Those two failures are the only bug reports I actually want.

Your client says the file never arrived. An API can settle that now.

Nenzy Brown — Sat, 31 Oct 2026 22:57:35 +0000

The argument is always the same. You sent the work on Tuesday. The client says the folder was empty, or the version was wrong, or nothing showed up at all. There's no referee. Just two inboxes and a payment sitting in the middle.

ProofReceipt fixes the receipt side of that. When you deliver, the app hashes the file with SHA-256 and gives you a receipt that ties that exact file to that moment. Change one character in the file and the hash changes. That's the whole trick, and it holds up because the maths doesn't care who argues louder.

I've written about the app here before. This post is about the piece I shipped after it: a verify endpoint other software can call.

The x402 verify endpoint

It lives at https://proofreceipt-verify.netlify.app and it does one job. Send it a receipt and an invoice amount, and it answers MATCH or MISMATCH, naming the check that failed if it's a mismatch. One character changed, one cent changed — it catches both, because I tested exactly those two cases until they failed loudly.

The payment part is the interesting bit. It uses x402, so there's no account, no API key dashboard, no monthly plan. An unpaid request gets a plain HTTP 402 back with the price attached: 0.5% of the invoice amount on the receipt, with a one-cent floor. A $25 invoice costs 12.5 cents to verify. A $2 one costs the floor. Pay, resend, get the verdict.

Right now it runs in test mode on Base Sepolia while the mainnet keys are sorted out. That part matters and I'm not dressing it up: test mode means test money. The endpoint answers, the 402 challenge is real, the verdicts are real. Settled mainnet payments aren't live yet.

Who'd actually call this

Two groups, mostly. Marketplaces and escrow tools that want a delivery check inside their own flow instead of sending users to a website. And AI agents. An agent that delivers work for a human has the same problem a freelancer does, except it can't argue in a dispute thread at all. A hash receipt plus a machine-readable verify call is the closest thing it gets to a paper trail.

The app itself is still at https://proofreceipt.netlify.app if you just want to make a receipt by hand. It's free to try, it's pre-revenue, and I'd rather you test the tamper case yourself than take my word for any of this. Change a full stop in a text file. Watch the verdict flip.

That's the test that convinced me, anyway.

I built ScamOrNot — a free scam checker for the moment of doubt

Nenzy Brown — Fri, 30 Oct 2026 17:18:48 +0000

Every day, ordinary people lose money to messages that felt almost right.

A "wrong number" chat that turns into a trading mentor with an uncle at an exchange. A prize that only needs a $45 processing fee. A parcel held at customs for a small redelivery charge. A job that pays $300 a day to like videos — withdrawals after you "recharge."

Global scam losses run past $1 trillion a year. The victims are not stupid. The scripts are professional, patient, and engineered around one moment: the moment of doubt, when something feels off but you act anyway because the pressure is louder than the doubt.

So I built a tool for exactly that moment.

ScamOrNot

👉 https://scamornot-app.netlify.app

Paste any suspicious message, link, or wallet address. You get back:

A risk score out of 100
Every red flag found, explained in plain English — not "pattern matched," but why it's a fraud signal
What to do next, specific to the flags found

No sign-up. No account. And by design, the check runs entirely in your browser — what you paste is never uploaded or stored anywhere. A scam checker that collects your private messages would be a strange kind of irony.

One job, done well

I took the narrowest possible scope on purpose: not a security suite, not an AI platform — one job. Tell me if this thing is a scam.

Under the hood it's a pattern engine covering 15 fraud families:

Seed-phrase and credential theft
Advance-fee "pay to unlock" structures
Crypto doubling giveaways
Pig-butchering scripts (the friendly-stranger-to-trading-platform pipeline)
Task-job scams, fake parcels, authority impersonation, romance-to-money pivots
Plus structural link analysis: brand names on domains the brand doesn't own, punycode look-alikes, IP-address hosts, @-trick URLs, abused TLDs

Calibrated, not vibes

Before launch I tested it against the cases that matter — real scam scripts and, just as important, things that must not be flagged:

Case	Score
Pig-butchering "mentor" pitch	45 — High risk
Crypto doubling giveaway	64 — High risk
Seed-phrase "wallet validation"	66 — High risk
Fake PayPal login link	50 — High risk
Advance-fee lottery prize	62 — High risk
Parcel-held customs text	70 — Almost certainly a scam
A normal team message	0
The real paypal.com	0
A genuine bank transaction SMS	0
A security article saying "never share your seed phrase"	0

That last one needed a deliberate guard: safety education mentions the dangerous phrases while warning against them. Context matters, so the engine checks for protective framing before it counts a theft pattern.

Honest limits

ScamOrNot is a pattern checker, not an oracle. It says so on the page: a clean result means no strong patterns detected, never guaranteed safe. Scammers adapt; the last line of defence is still the pause — verify through the official app or the number on your card, never through the message itself.

Why free, and what's paid

The moment of doubt is exactly when help should cost nothing, so checks are free (3 a day). Pro is $9/month for unlimited checks — paid in USDC, because the people who need this most are often screening gig offers and deals in crypto-native spaces. Teams is $29 for communities and family groups that forward each other "opportunities."

It joins my other build, ProofReceipt (SHA-256 delivery receipts for freelancers) — both came out of the same conviction: small, verifiable tools that protect people at the exact moment money is about to move.

Try it on the next "opportunity" that lands in your DMs. And send it to the one person in your family who forwards everything — they're the ones who need it most.

— NenzyBrown, Dubai

Building in Public: What I Shipped This Week — Telegram Bot v3 and ProofReceipt Verification

Nenzy Brown — Thu, 29 Oct 2026 16:41:58 +0000

I am Nenzy Brown, a self-taught founder in Dubai with 5+ years in AI and blockchain. I am founder of Cryptohost USD, Turbo USD, PlateWallet, and ProofReceipt. No degree, no invented clients or earnings — this is a plain update on what I shipped this week and what it costs to hire me for similar work.

What I shipped this week

Telegram bot v3: a free crypto front desk

I shipped v3 of my free Telegram crypto front desk, @NenzyBrownAssistantBot. It gives prices, token safety checks, alerts, and market news. Try it free here: https://t.me/NenzyBrownAssistantBot

The token checker and alerts are the parts I focused on this week: a quick check before you interact with an unfamiliar token, and alerts so you do not have to keep refreshing prices yourself. The channel for updates is @nenzybrownbuilds.

ProofReceipt verification

I also worked on ProofReceipt verification. ProofReceipt is SHA-256 delivery verification for freelancers, live at https://proofreceipt.netlify.app. It is pre-revenue, and I am sharing it as a built product, not as a traction claim.

My other product in progress is PlateWallet, a UAE license-plate payment network launching in 2026. It is pre-revenue and pre-pilot.

What it costs to hire me

I take direct hires. Here is the current list:

AI agent builds — from $150
Telegram bot builds — from $150
MT4/MT5 EA builds — from $250
Exchange trading-bot builds — from $300
Web3 research reports — $75
Campaign / content packs — from $50

How to order

Message me on Telegram at @nenzybrown, on LinkedIn at NenzyBrown, or on GitHub at Nenzy10, with what you want built and your timeline.
I will confirm scope and price.
Payment is in USDC/USDT on Base/EVM to wallet 0x48E78fFC3f02A65c6A9718b4dc293ae14cBb7985. Work starts on payment or escrow.

If you are not sure yet, try the free bot first. It is the fastest way to see how I build.

I Put a Free Crypto Front Desk on Telegram — Prices, Token Checks, Alerts and News in One Chat

Nenzy Brown — Thu, 29 Oct 2026 05:16:44 +0000

I Put a Free Crypto Front Desk on Telegram

If you trade or build in crypto, your day probably looks like this: one tab for prices, another for a chart, a third for DexScreener, a news site you half-trust, and a mental note of the gas price you meant to check an hour ago. None of these tools are bad. The problem is they're scattered, and every context switch costs you attention.

I wanted one place — inside the app I already have open all day — where the basic checks take seconds. So I built a Telegram bot that works like a front desk for crypto: you walk up, ask a simple question, and get a straight answer. It's free, it needs no sign-up, and it never touches your funds. Here's what it actually does, and how I use it.

The checks I run most

Live prices without opening an exchange. Sending /price BTC (or ETH, SOL, any major pair) returns the current price in the chat. It sounds trivial until you count how many times a day you unlock your phone just to see a number.

A token sanity check before anything else. /token takes a contract address and pulls the DexScreener data — liquidity, market cap, pair age, recent volume — and flags the patterns that show up in rug pulls: thin or unlocked liquidity, a pair created minutes ago, one-sided volume. It doesn't tell you a token is "safe" — nothing can — but it makes the obvious traps visible in about ten seconds, which is usually all the warning you get.

Gas, before you sign anything. /gas shows current network fees so you can decide whether that swap or transfer needs to happen now or can wait for a cheaper block. On busy days this one check has saved me more than everything else on this list combined.

Headlines from two sources I already read. /news pulls the latest from CoinDesk and Cointelegraph into the chat. No algorithmic feed, no engagement bait — just the most recent headlines from publications with actual editors, so a quick scan tells me whether anything market-moving happened while I was heads-down.

The parts that keep me honest

The tools that surprised me most were the boring ones.

Price alerts and a watchlist. I set alerts on the pairs I actually care about and let the bot tap me on the shoulder. That replaced my habit of refreshing charts "just in case," which was really just anxiety with extra steps.
A trade journal. Every trade I make gets one line in the journal: what, why, and what I expected. Reviewing it monthly is uncomfortable and extremely useful. Most of my worst trades share a sentence in the "why" column, and seeing that pattern written down changed my behaviour more than any indicator.
A calculator for position sizing and conversions, because doing fee maths in your head at 1 a.m. is how mistakes happen.
A small learning section that explains common terms and concepts in plain language — written for the questions I kept getting from friends who are new to this space.

And a portfolio view ties the watchlist together so I can see the whole picture in one message instead of five apps.

Why Telegram, specifically

Three reasons. First, it's already where crypto conversations happen — communities, OTC desks, project groups — so the tool lives where the questions arise. Second, there's nothing to install and no account to create; if you have Telegram, you're one tap away. Third, a chat interface is honest about what a tool is: you ask, it answers, there's no dashboard pretending to be smarter than it is.

The bot is deliberately non-custodial. It doesn't connect to your wallet, can't move funds, and doesn't execute trades. It's a front desk, not a vault — information and organisation, nothing more. I think that boundary matters, especially in a space where "helpful bot" has too often meant "give me your keys."

The shop window (full disclosure)

I build AI agents and do Web3 research for a living, so the same bot carries a small storefront: /services lists what's on offer — AI agent builds from $150, sourced Web3 research reports from $75, launch campaign plans from $50, and technical explainers or documentation from $40. Orders are placed in chat with /order, paid in USDC or USDT to a wallet, and delivery is verified with a SHA-256 receipt (a system I built called ProofReceipt) so the client can prove exactly what file they received. That's the commercial part, and it's one command among many — the tools above are free whether or not anyone ever orders.

Try it

The bot is @NenzyBrownAssistantBot on Telegram, and I post tool tips and updates on the @nenzybrownbuilds channel. If you try it, the two commands I'd start with are /token the next time a contract address gets dropped in a group chat, and /gas before your next on-chain transaction. Those two habits alone are worth the thirty seconds it takes to open the chat.

If you build bots or crypto tooling yourself, I'd genuinely like to hear what check you wish existed in your messaging app — the front desk has room for a few more drawers.

I built a free crypto front desk on Telegram — prices, token checks, alerts, and a shop

Nenzy Brown — Wed, 28 Oct 2026 14:10:22 +0000

Building in public, day two. Today my Telegram bot grew into the tool I kept wishing existed: one chat that answers the questions a crypto trader asks all day — without holding anyone's funds or pretending to predict anything.

What @NenzyBrownAssistantBot does (free):

/price BTC, /market, /gainers — live prices, market cap, BTC dominance, Fear & Greed
/token — paste any EVM token contract and get live liquidity, FDV and pair data, with the rug-shape warnings spelled out
/alert BTC above 90000 — price alerts checked every minute, delivered by DM
/watch, /portfolio — watchlists and a holdings tracker valued live
/calc — a position-size calculator that starts from risk, not hope
/gas — Ethereum + Base gas; /convert — instant USD conversion; /news — headlines
/learn, /safety — short lessons and the scam checklist I wish every beginner read first

The shop inside it: I build tools for traders — MetaTrader EAs, exchange trading bots that run on YOUR keys, Telegram bots, AI agents, plus Web3 research and content. Ordering happens in the chat (/order), payment is USDC/USDT on Base, and every delivery carries a SHA-256 ProofReceipt. Premium (signals & alerts, education only) is $15/month.

The lines I won't cross, because they're the product: the bot never trades, never holds funds, never promises profits.

Try it: https://t.me/NenzyBrownAssistantBot — updates and offers live on the channel: https://t.me/nenzybrownbuilds

Built by Nenzy Brown (Dubai) — founder of ProofReceipt and PlateWallet. Day by day, in public.

I Built a Telegram Storefront That Sells My AI Services While I Sleep

Nenzy Brown — Wed, 28 Oct 2026 12:00:53 +0000

Today I stopped waiting for platforms to approve, rank, or pay me — and opened my own shop where my buyers already live: Telegram.

The storefront — @NenzyBrownAssistantBot (t.me/NenzyBrownAssistantBot)

/services — AI agent builds from $150, Telegram bot builds from $150, Web3 research reports $75, content packs from $50
/price BTC — live spot checks
/signal — one free educational trading lesson a day
/subscribe — Premium signals & alerts, $15/month

How a sale works, end to end: the buyer pays USDC on Base straight to my wallet — no platform in the middle, no 20% fee, no 14-day clearance. They send the bot their transaction hash, the claim lands in my Telegram, I verify it on-chain in one look, tap approve, and the bot issues a one-time invite to the Premium channel. Every delivery I make carries a SHA-256 ProofReceipt.

The lines I won't cross, printed inside the product itself: signals are education only — not financial advice, no profit promises. The bot never executes trades and never holds anyone's money.

Channel with the pinned price list: t.me/nenzybrownbuilds

I'm a self-taught founder in Dubai; the work is the pitch. If you need an agent, a bot, or a research report — the shop is open.

I'm done building in private. Everything goes public from today.

Nenzy Brown — Tue, 27 Oct 2026 16:13:30 +0000

I'm done building in private. Everything goes public from today.

I'm Nenzy Brown — self-taught founder, based in Dubai. No degree, no accelerator, no investors. For years I've been building in the dark: payment systems, stablecoin products, AI tools. Good work that almost nobody has seen.

That ends today. From now on, everything I build gets published — the wins, the code, the receipts, and the zeros. If I'm a nobody to the public, that's on me for staying invisible. Not anymore.

What I'm building (all verifiable — links below)

PlateWallet — a payment network built into your license plate. ANPR cameras settle parking, fuel, tolls and drive-thru automatically. The charge engine is built: a double-entry ledger in integer fils, idempotent event ingestion, a review queue for low-confidence reads, fee/VAT splits, dispute reversal, settlement batching. Launching in the UAE in 2026. Pre-revenue, pre-pilot — I say that plainly.

ProofReceipt — verifiable delivery receipts for freelancers and AI agents. Hash your deliverable (SHA-256), get a receipt anyone can verify. It's live right now: proofreceipt.netlify.app. When an AI agent does paid work for you, "trust me" is not a delivery standard. A receipt is.

WordBond — promise-staking for sellers. A seller stakes a bond behind a delivery promise; keep it and the bond returns, break it and the buyer is compensated automatically by a smart contract. It's live on Base Sepolia testnet and proven end-to-end with real transactions: bonds posted, a kept promise released, a broken promise paid out — with the protocol fee (2% registration + 10% of forfeits) verified in the contract reads. Mainnet comes after audit — I won't put real user money behind unaudited code, and I'll publish that process too.

The operation — I run an AI-agent delivery operation that takes real, escrow-settled work: research, builds, automation. First engagement settled through escrow with every cited requirement verified as met. Small numbers. Real ones.

The rules of this feed

Proof over pitch. Every claim links to something you can check — a live product, a repo, a transaction.
Honest labels. Live means live. Testnet means testnet. Pre-revenue means exactly that.
Zeros shown as zeros. If a week produces nothing, the post says so and explains what changes next.

Why now

Because building great things in silence is a strategy for staying unknown. The work is real — it deserves witnesses, users, critics, and customers. So: two to three posts a week here, every demo on GitHub (Nenzy10), videos starting this week, and the canonical home for all of it at nenzybrown.netlify.app.

If you build in Web3, payments, or AI agents — follow along, argue with me, steal the ideas and make them better. If you need this kind of work done, you now know where to find the person who ships it in the open.

Day one. Let's go.

— Nenzy Brown, Dubai