The receipt layer of web3. Fees, v4 hooks and more. Building HookSweeprs, the wrapper hook! 0x59f0ca30136e348bd860c56bc8ee21954e16cbd7
Factory
Joined October 2026
- Tweets77
- Following1
- Followers236
- Likes108
Pinned Tweet
Announcing our flagship product: HookSweeprs
In below article, read about what HookSweeprs actually does.
Read about where this is going and why wrapping tokens is a gamechanger given the 22 October Uniswap announcement. This is huge!
What’s in it for $SWEEPRS holders: Cheaper trades, 100% burns from every payment, early alerts and a vote on what’s next.
How holders are rewarded: You spend less, there’s less $SWEEPRS around, and you get there first.
#HookSweeprs
Hooks made trading on v4 smarter. They also made it a lot harder to see what you're paying.
HookSweeprs puts it back in plain sight.
$SWEEPRS #SWEEPRS
GM
Builders update: stage 3 progress
Last time we shared the two hardest parts of the wrapper. Here’s where we stand today.
✅ Guarding a pool we don’t control
The wrapper now reads the launchpad’s settings before every swap. In testing, I changed a fee wallet on the underlying pool, and the guarded pool flagged it and dropped its Guarded status. That’s what I wanted it to do so that is great news!
🔨 Tax tokens
The Pons V2 adapter is working: quotes match what shows in the wallet.. The Torch adapter, for tokens that take their fee as a tax on buys, is next.
What is next
I will focus on the Wrapper hook built on the Hookr SDK, to ensure it is done properly.
#SWEEPRS
Sweeprs retweeted
Happy Monday. New week to build and ship
Sharing our builders update: stage 3, the wrapper
The wrapper is in build. It’s the hardest piece of HookSweeprs so far. I'm facing a few problems I'm working through right now.
The main one is promising a fixed fee on someone else’s pool. To fully understand: our wrapper sits on top of a pool that a launchpad already runs. We control our layer. We don’t control theirs.
This means that if a creator changes the fee wallet on the launchpad itself, the wrapper can’t stop it.
How I try to solve it: before every swap, the wrapper reads the launchpad’s settings. If anything changed without notice, the pool shows it straight away and drops its Guarded status until the change has been public for the full delay.
This way I can guarantee our own layer and watch the one under it.
btw, this is being built on the Hookr SDK. More soon. Let's SWEEP!
#HOOKR #HOOKS #WRAPPER #SWEEPRS
Interesting. We are facing another challenge with the wrapper build. Definitely not a boring start of the week right?
This one is about tax tokens and Uniswap’s accounting.
Some launchpads take their fee inside the token itself, as a tax on every buy. Uniswap v4 expects the exact amount sent to be the exact amount received. With a tax token those numbers don’t match, and the trade either fails or quotes the wrong price.
I believe the beste way forward to fix this is to have one adapter per launchpad. Each adapter measures what actually arrived instead of trusting what was sent, and quotes with the tax already included. Pons V2 comes first because its fee sits in the hook, not the token. Torch-style tax tokens come next. We will get there.
Why am I sharing this? A guarded pool is only worth something if it holds up in the edge cases. It shows that the wrapper and the guard are something of value that are not easy to just build and release. And so you know there are hard parts to building something valuable instead of just ship a badge that breaks the first time someone tests it.
Happy Monday. New week to build and ship
Sharing our builders update: stage 3, the wrapper
The wrapper is in build. It’s the hardest piece of HookSweeprs so far. I'm facing a few problems I'm working through right now.
The main one is promising a fixed fee on someone else’s pool. To fully understand: our wrapper sits on top of a pool that a launchpad already runs. We control our layer. We don’t control theirs.
This means that if a creator changes the fee wallet on the launchpad itself, the wrapper can’t stop it.
How I try to solve it: before every swap, the wrapper reads the launchpad’s settings. If anything changed without notice, the pool shows it straight away and drops its Guarded status until the change has been public for the full delay.
This way I can guarantee our own layer and watch the one under it.
btw, this is being built on the Hookr SDK. More soon. Let's SWEEP!
#HOOKR #HOOKS #WRAPPER #SWEEPRS
Since day 1 we are shipping steadily. Yes, our valuation could be higher, but even the best projects are taking hits during these market conditions.
We keep going at it, and sooner or later, repricing will happen, and investors will see what we are building here. Something no one else is doing, and we are just at the foot of mountain of builds.
Below, see how much is already live. #SWEEPRS
How a hook test runs on $SWEEPRS.
Paste a pool. Read what it declares. Read the swaps. Compare the two. Go and test it out on sweeprs.xyz/hooks
Guarded badge coming tomorrow! Red days, we ship. Green days, we ship.
Builders update: the Guarded badge is in production
Stage 2 is being built. Let me share what goes into a badge you can actually trust.
1. The declaration registry
For every hooked pool we record what it says it charges: from the hook contract, the pool settings and the launchpad itself. Each hook version gets its own record.
2. The code check
Before a hook can earn the badge, we read its code for the things that matter to your fee:
• Where in the swap it takes a cut
• Who can change the fee or the fee wallet
• Whether the contract can be upgraded or swapped out
• Whether changes go through a delay, or happen instantly
3. The live monitor
We follow every swap through hooked pools and work out the real fee paid, across the hook, the router and every wallet that receives a share.
4. Change detection
Owner changes, new fee wallets, upgrades, fee updates. If any of these happens, it’s flagged the same day, with the transaction.
5. Badge status
Every hook sits in one clear state: Applied → In review → Guarded → Suspended → Revoked. Each change of state is published with the transactions behind it, and builders get a right of reply.
What’s next
The first hooks on Robinhood Chain go through the full process before we open applications. Builders who want to be early can DM us now.
Back to back shipping $Sweeprs.
We only sweep creator fees and hooks.
Stay Safu!
#binancehack
The Binance drain took four minutes. The preparation took 18 hours, in public, on three empty wallets that rehearsed the exact move. All of it is on chain, Oct 29 UTC.
02:28 The operator address deploys sweeper v1, 0x19bee294a6daab49c9e5ab69a5da6c035c70f2bf. Unverified, drain function callable only by the operator.
13:51 Two fresh wallets with zero history get EIP-7702 delegations to sweeper v1:
0x837810e3be7a3e89c570e7a01a13d3b566aafbc3, two authorizations, nonces 0 and 1
0x9c29ba2de4b2d6c3630685650663cfe7b70dbb6b, three authorizations, nonces 0, 1 and 2
A fresh wallet's nonce is always zero, so one authorization would do. He sent two and three. He was testing whether a list with invalid nonces still goes through. Six minutes later a third address sends them dust. At 14:19 and 14:24 the operator runs the drain on both. They were empty, so nothing moved. The path works.
15:59 Sweeper v2 deployed, 0x63e842b054bd624a465454d533c33f573e9c6fae. This is the one that will sit on Binance 14.
16:20 and 16:25 Third fresh wallet, 0x43aedb9bad6219677a2c8d6858321c16988404bd, delegated to v2 twice. Between the two, 1.01 ETH arrives from 0xe4F9070e1316de2988fc6f869feaD8fb99cC74cd. 16:30 the sweeper moves 0.01 ETH out. 16:47 it moves the remaining 1.0 ETH back to 0xe4F9070e. Full rehearsal with real money, then the money goes home.
18:20 The same 0xe4F9070e sends 1.08 ETH to the operator. Gas for the real thing.
20:20:59 Binance 14 receives fifty authorizations in one transaction, nonces 18914775 to 18914824, sweeper v2. One matches.
20:24:23 167,464 ETH and 63 token transfers leave in a single call.
What this proves: the nonce spray was designed, not improvised. He knew in the morning that he would not have the live nonce of the target in the evening.
The rehearsals were public but anonymous, three empty wallets among the dozens of phishing delegations the chain sees every day. The alarm was the next step: a labeled Binance hot wallet accepting a 7702 delegation to a six-hour-old unverified contract. That is one rule in any monitoring system. From that transaction to the first sweep there were three minutes and twenty-four seconds. Nobody flagged it in that window.
What “Guarded” actually means
Here’s the bar a hook has to clear.
The four rules
- The fee is declared, publicly and upfront
- The fee taken on real trades matches the declaration
- The split is visible onchain: who gets what, no hidden wallets
- Any change to the fee or its recipient is announced before it takes effect
How it works
• A builder applies for one hook version
• We check the code against the four rules
• Once it passes, we watch it on every trade, not just on launch day
• If it breaks a rule, the badge comes off and the change is published with the transactions
Why this beats a one-off audit
An audit tells you what the code looked like before launch. Fee changes happen after. Guarded is checked live, every day.
#SWEEPRS
Stage 2 of HookSweeprs: The Guarded badge
A Uniswap v4 hook can take its own fee on every swap, and change it after you buy.
Stage 1 checks that. Stage 2 rewards the hooks that pass.
What it does
• Hook builders and launchpads apply to be certified
• We check the hook's code once, then watch it on every trade
• The badge shows on Sweeprs reports, in our bots and in every answer we give to AI agents
• A hook that stops matching its declared fee loses the badge, the same day
Why it matters
• Traders get one signal before they buy: this hook takes what it says
• AI agents can stick to Guarded pools automatically
• Honest hook builders finally have a way to prove it, and win the volume that comes with trust
It is very simple. You can't pay to pass. You pay for the check, not the result.
$SWEEPRS holders get up to 40% off certification, and every payment made in $SWEEPRS is burned.
Check the hook before you trade. sweeprs.xyz
Stage 2 of HookSweeprs: The Guarded badge
A Uniswap v4 hook can take its own fee on every swap, and change it after you buy.
Stage 1 checks that. Stage 2 rewards the hooks that pass.
What it does
• Hook builders and launchpads apply to be certified
• We check the hook's code once, then watch it on every trade
• The badge shows on Sweeprs reports, in our bots and in every answer we give to AI agents
• A hook that stops matching its declared fee loses the badge, the same day
Why it matters
• Traders get one signal before they buy: this hook takes what it says
• AI agents can stick to Guarded pools automatically
• Honest hook builders finally have a way to prove it, and win the volume that comes with trust
It is very simple. You can't pay to pass. You pay for the check, not the result.
$SWEEPRS holders get up to 40% off certification, and every payment made in $SWEEPRS is burned.
Check the hook before you trade. sweeprs.xyz
#HOOKSWEEPRS in action
What is listed. What did the hook took. Onchain, verifiable, proven, by $SWEEPRS!
I'm working hard to solve the issue and make the reports more presentable.
Meanwhile, I did 2 things:
1: we published the Hooks page live on sweeprs.xyz.
2: we bought back almost 5M (0.5% of total supply) of $SWEEPRS of the secondary market.
I'm fully devving and still testing hard. I'm going no where until this works in full. Proof of purchase below in the comments.
I'm working hard to solve the issue and make the reports more presentable.
Meanwhile, I did 2 things:
1: we published the Hooks page live on sweeprs.xyz.
2: we bought back almost 5M (0.5% of total supply) of $SWEEPRS of the secondary market.
I'm fully devving and still testing hard. I'm going no where until this works in full. Proof of purchase below in the comments.
Small update
We deployed V1 but we found it was doing what we wanted 100%, so since yesterday night we have been trying to understand how to fix this. We are getting closer and although it might take a bit longer, we will be able to create something unique in this space. Insights in hook fees are like a black box and most people still don’t understand how hooks work.
Rest assured we are up and pushing the testing rounds again so it can get live asap.
GM
For those who missed our HookSweeprs announcement this weekend, see below.
Stage 1 is finished. We are testing it now and expect to deploy it today. On schedule.
When we get to stage 3, the ball starts rolling and the flywheel will be moving faster and faster. Strap in.
We are sweepin $SWEEPRS!
Announcing our flagship product: HookSweeprs
In below article, read about what HookSweeprs actually does.
Read about where this is going and why wrapping tokens is a gamechanger given the 22 October Uniswap announcement. This is huge!
What’s in it for $SWEEPRS holders: Cheaper trades, 100% burns from every payment, early alerts and a vote on what’s next.
How holders are rewarded: You spend less, there’s less $SWEEPRS around, and you get there first.
#HookSweeprs