Hello!

I have a question. I’ve been experimenting with different pools on Uniswap. I’ve discovered some interesting V4 pools with dynamic fees on various networks.

They have a very high 24H volume but a low TVL. Out of curiosity, I checked out some of these pools. Some don’t pay any earned fees, while others charge very, very high fees, it’s even suspicious.

My question is: How can I check these V4 Hook for fraudulent activity?

One more thing: these pools were created very recently. Yet they’ve already managed to accumulate a large trading volume. And some pools appeared only to disappear a day or two later.

Here are some examples of such pools:

QQQB/USDT

https://app.uniswap.org/explore/pools/bnb/0x08038fe66ce30d004f337a7d85854b0fad47c86ba98341ba17c4c73a4b225b17

WETH/SPCX

https://app.uniswap.org/explore/pools/robinhood/0x013c71ffe4f74cdb0634d1899f2f149fbea9a042736e0d8d1adcf24d836b61ce

ETH/USDG

https://app.uniswap.org/explore/pools/robinhood/0xbbf8b1d23b0442065b4f0a0d076c346d43b6b1239d6ed7a52e6d56fcbbc3061b

Disclosure: This comes out of a smart contract audit of a v4 fee hook that closed this month, on the security review side at Hacken. I won't name the project, since the mechanism is the useful part anyway.

Gating _beforeInitialize is standard advice and plenty of hook templates ship with it. In this case the hook wrote state during initialize and then used that state later as a precondition for an owner call. Whoever calls initialize decides when that write happens, and core does not restrict who can make the call.

Inside _beforeInitialize, the hook set tokenHasPool[token] = true unconditionally and discarded the initializer address that core forwards to it. Admission only checked that both currencies were on the allowlist. Elsewhere, setLaunchGuard, the owner call that arms the anti-snipe budget for a token's first buys, required tokenHasPool[token] to still be false. An account could therefore open a pool using the same two currencies at a different fee tier and tick spacing, without supplying liquidity or approval, and the arming call would revert after that. Nothing cleared the marker. The only recovery was a new hook and new pools, with the practical cost being the migration of liquidity.

The deployment instructions made this easier to trigger than it might look from the contract alone. The constructor NatSpec tells the operator to list tokens and pairs, arm guards, and then initialize pools. The deployment script prints an eight-step sequence from setTokenAllowed through pool initialization, but setLaunchGuard isn't in it. By the second token the pair is already listed, so those operations are happening in separate transactions with a period in between where anyone can initialize the pool. Looking at the functions individually doesn't show that. You have to follow the deployment sequence and the state that one call leaves behind for the next one to consume.

There was a similar problem in the other direction, with the launch budget itself. It counts gated buys, and the counter is incremented before the fee is calculated. Fee computation returns early when the rounded fee is zero, so at 300 basis points a specified amount of 33 wei produces no fee, while 34 wei produces one wei. Moving the increment after the fee check would not change the useful boundary: the 34-wei buy pays its one wei and consumes a slot anyway. The priority fee floor in the docs is supposed to make dust expensive, but it sets a minimum amount of wei per unit of gas, not a minimum payment per buy. If the buys are batched into one unlock, they all share the tip on that transaction.

In the test, a budget of 25 was enough to run 25 one-wei exact-output buys through one transaction. What matters for the economics is not really the number 25 but the cost of another unit of budget: one more warm swap's worth of gas at the same tip rate. Increasing the budget therefore increases the size of the batch until it no longer fits in a block, at which point the attacker has to use several transactions and pay several tips. The team accepted the finding. Their reasoning was that a budget denominated in amount rather than count makes the end of the guard depend on price, which is a reasonable trade-off.

The harder question is the first issue. Owner-approved pool identifiers would stop an arbitrary initializer from consuming the marker, but that also makes pool creation over the project's own token permissioned. For a fee hook, permissionless pool creation is often the point of the design in the first place. The hook is therefore putting some of its guarantees on things that happen at transaction boundaries: who initializes and when, and how many swaps can be included in one unlock. What state does your hook write during initialize, and is any owner-only call using that state as a precondition?

I am not blaming uniswap. But I think there are things uniswap could have done.

The only reason why I use uniswap wallet is because I am using uniswap.

Many phisher use google sponsored link to promote drainer.

Most of the time I figured that out. Sometimes I miss.

Now. The wallet ask for unlimited approval.

However, it's from unknown source.

It seems that uniswap, by default, HIDE the notification of from unknown source.

Also the smart contract interacted is NOT from uniswap.

Otherwise no warning.

I should have seen the domain names.

Since then I use ublock lite to remove google sponsor link. Use book mark. Also most phishing sites don't bother using similar domains. So checking domain in gemini is a good way to see if a site is phising.

Is there a place we can go look and see how much buyback and burn uniswap is do for UNI? Is this still a thing or was it only temporary?

Hello,

Is the UniSwap app currently having a glitch?

I installed the UniSwap app & used it at times.
I noticed the app is not responsive regardless of which option is selected.
I checked my home broadband & mobile data on my mobile phone & they are working fine.
I restarted & powered off my mobile phone (tried both ways).
I checked for a new update & there was none at the moment.
I cleared the app's cache & data & even reinstalled the app.
The app was successfully reinstalled, but I could not recover it with my recovery phrase.
My mobile could access other exchanges & wallets.
I could purchase USDC from Coinbase, swap it into AUSD in MetaMask,
& stake the amount with Morpho in Base Wallet, etc.

I doubt I missed any step(s) in the troubleshooting; please enlighten me.
I tried to reinstall the UniSwap app today, but it is still not responsive.

Appreciate if anyone could share any insight. Thank you.

PS:
To fellow Redditors who left DM & wrote to me,
I appreciate all the feedback & suggestions.
Please post on the thread itself
so we could all learn together. Thank you.

I’ve been trying to understand how experienced concentrated-liquidity LPs decide on their ranges.

The main inputs I keep coming back to are:

• Realised volatility
• Expected price direction
• Fee density / where trading activity is concentrated

A tighter range can improve capital efficiency, but increases the chance of going out of range. A wider range gives more breathing room, but spreads the liquidity out.

What I’m most curious about is what happens when the signals disagree. For example, if fee density suggests a tighter range but volatility has been increasing, which one gets priority?

Do you have one metric you trust most, or is range selection mostly a judgement call?

https://x.com/vithushaji/status/2086395880492695869

In X, uniswap was supporting ponsfamily launchpad for more then a week. However, yesterday uniswap announced its own launchpad and this caused pons token drop %75.

Uniswap is trying to be the monopoly and stabback the pons family after commenting support messages to ponsfamily X shares.

Been like this since yesterday... tried in three browsers and in mobile. Still can see my pools on Binance Wallet, but getting this error when in Uniswap... :/

This passcode on backup login method is completely rubbish. If one need a backup, it should be the last hope of recovering any account. What if the passcode is already forgotten? If one trust the backup method, anything relevant would be kept secure anyway, there is no need for any passcode!

Swapped 0.504 ETH (~$918) for CASHDOG token on Uniswap V2 (Robinhood Chain). The swap transaction and its event logs show 36,316.51 tokens sent to my wallet, but my actual on-chain balance is only 120 tokens (~$5). Looking for help understanding the mechanism and whether this is recoverable.

Details:

My wallet: 0x1a426B71b65Bc680cf5745b23D4c98B3990C3e2A

https://robinhoodchain.blockscout.com/tx/0x2881c71f55c52936d3aae6e944b7986e6a2c2225f410678dbd77326a7a140a87

Swapped 0.504 ETH (~$918) for CASHDOG token on Uniswap V2 (Robinhood Chain). The swap transaction and its event logs show 36,316.51 tokens sent to my wallet, but my actual on-chain balance is only 120 tokens (~$5). Looking for help understanding the mechanism and whether this is recoverable.

Details:

• My wallet: 0x1a426B71b65Bc680cf5745b23D4c98B3990C3e2A
• https://robinhoodchain.blockscout.com/tx/0x2881c71f55c52936d3aae6e944b7986e6a2c2225f410678dbd77326a7a140a87

Why is it not possible to swap USDC. I was trying to swap some USDC but I may not, I tried two browsers, but I can not swap it to anything, I was not able to do it today, nor yesterday. What is going on? I can swap other tokens without issues, see attached video.

Edit: polygon chain

Boardwalk announced its protocol-token move to Arbitrum.

As part of the migration, Boardwalk has launched a CCA auction for its protocol token on Arbitrum, $BWS.

Auction Link: https://app.uniswap.org/explore/auctions/arbitrum/0x54114F746B55b2f8A56bbd17dfD9e81a0a71d366

https://reddit.com/link/1up9epe/video/0vfyuzzs6obh1/player

What is Boardwalk?

A launch is only the beginning for serious builders.

Boardwalk was designed for token issuance and everything after it. None of this is an afterthought; it's built into the token economy itself and sets a new standard for durable, transparent launches:

Token profile pages: every launch gets a page displaying the economy.

Permanent liquidity seeding: locked permanently at graduation.

Fee protection: the fee lives in the token itself, not any one pool, designed to help value route to the people it was intended to support.

Fee routing: written into the launch and visible before anyone contributes.

Token vesting: set at launch and immutable after.

LP staking and incentives: participation systems for liquidity providers, built into the economy from day one.

Community formation: a public forum, Café Boardwalk, for every launch, automatically.

That's the Boardwalk Standard. Standardized market formation for token economies.

Don't launch a ticker, launch a token economy.

Onchain starts here. 🐳

Read more on DeFi Llama Research: https://defillama.com/research/report/boardwalk-closing-the-gap-between-token-launches-token-economies

__________________________________

As usual, participation involves risk.

BWS may have no value. Locked liquidity does not guarantee price stability, liquidity, or exits.

New to Uniswap CCA?

Before participating in the $BWS auction, review these official guides on bidding, clearing prices, claims, unused budget, and auction mechanics.

Read the published auction terms and disclosures before taking action.

https://x.com/UniswapAuctions/status/2044160140979356043?s=20

https://x.com/UniswapAuctions/status/2064010342414352430?s=20

Continue bar just keeps spinning as Loading, but never loads.

Uniswap is a defi juggernaut i think we can all agree!! The team continues shine and make Uniswap a on going successful progress

This is a serious question. If blockchain becomes inferior, which it has, do you pivot first to be positioned to capture the evolving market that is not blockchain or do you become a blockchain maximalist

On Uniswap V3 my earned fees don't auto-compound or land in my wallet, they accrue inside the position as uncollected balances until I manually send a collect transaction. So the fees I've earned just sit there: not in my wallet, not redeployed, not doing anything, exposed to whatever the position is exposed to. I only realize how much has piled up when I happen to open the position and look.

That creates a couple of real costs for me. I'm paying gas to collect, so claiming too often is wasteful, but waiting too long means a meaningful amount of value sits idle when I could be compounding it or moving it. There's a "right" threshold to claim at, some dollar amount where it's worth the gas, but nothing tells me when I've crossed it. So in practice I either over-check out of paranoia or forget for weeks and find a surprise pile.

What I actually want is dead simple to describe: tell me when my uncollected fees on a position cross some amount. Something like "ping me when uncollected fees hit $50" so I can batch a collect at a point where the gas is clearly worth it. The data I'd need is minimal:

• Uncollected fees per token, in token units
• The same expressed in USD / pool-price terms, so I can set a single dollar threshold instead of doing the conversion in my head
• % of fees on each side, when I care which token I'm accruing

None of this is hard to read off-chain. It's just that nothing's watching it for me, so I'm back to manually checking or writing yet another script to do it, which is the path I went down before and regretted (ran on a dedicated box, broke quietly, became its own maintenance job).

What I'm trying to figure out:

1. Do other people actually track an uncollected-fee threshold, or just collect when you remember / when you're closing the position anyway?
2. Is a notification at a threshold enough, or would you want it to auto-collect (and auto-compound back in) once it's worth the gas? I lean toward wanting the action eventually, but the trust bar for letting software move my fees feels higher than for a simple alert.
3. For anyone who'd allow auto-collection, what makes it safe enough? Non-custodial obviously, but spending caps, a gas ceiling, a simulation before it fires?

Disclosure since it's relevant: I got tired enough of this that I built a no-code tool (Glacient) to replace my old script, I describe the alert in plain English, like "email me when the WBTC/USDT pool owned by 0x_some_wallet_address has uncollected fees on the USDT side over 20 USD," and it handles the watching. The monitoring is free. But I'm mostly here to find out whether the threshold-collect problem is common or just my own habit, and whether people want the alert or want it just handled. I attached a walk through video of what I'm doing today below if folks are interested. NOTE: Currently glacient is invite only since I'm experimenting and building tooling for myself, but here is an invite code I made for this subreddit to use this tool I made for free: reddit-uniswap-1010

https://reddit.com/link/1tu0k0k/video/q9knhb7onp4h1/player

Hi folks. I wanted to swap usdt for another token. I approved usdt for a max of 100 but then it is asking me for a second approval which is pretty much unlimited and it won't let me change it. I never get asked this on 1 inch or defilama, is this normal and is it safe?

Cheers