Helping you stay safe and think clearly in crypto. Crypto, Privacy & Security, AI, Decision Psychology. Education over speculation.
Prague, Central Europe
Joined November 2020
- Tweets3.4K
- Following328
- Followers2.4K
- Likes2K
Your phone number is now a single key that can unlock every Google account on your Android.
Google adds it by default. Once linked, the accounts are no longer fully separate - even if you never used the number on them.
For anyone who keeps a clean crypto account, a work account and a personal one, this creates an easy correlation point that is hard to reverse later.
The checklist shows how to stop new links and remove existing ones.
The real work is checking every account, not just turning the setting off.
Google may be linking your phone number to more accounts than you think.🚨
On Android, automatic phone number verification is enabled by default.
Google can add your number to every Google account signed in on your device, including accounts you wanted to keep separate.
How to turn it off:
1. Open Android Settings -> Google -> All services.
2. Go to Phone number verification.
3. Turn off automatic verification.
Already linked? Turning this off won't remove your number.
Check each Google account under Personal info -> Phone and remove it where needed.
Your phone number isn't made public, but your separate accounts may now share the same number.
Worth checking.
Some users report this setting turning itself back on after disabling it.
Save this checklist and check again from time to time, especially after Android updates.
ALT Android can automatically associate your phone number with multiple Google accounts on the same device. Disable automatic verification in Android settings, then review existing phone numbers separately in each Google account.
Google may be linking your phone number to more accounts than you think.🚨
On Android, automatic phone number verification is enabled by default.
Google can add your number to every Google account signed in on your device, including accounts you wanted to keep separate.
How to turn it off:
1. Open Android Settings -> Google -> All services.
2. Go to Phone number verification.
3. Turn off automatic verification.
Already linked? Turning this off won't remove your number.
Check each Google account under Personal info -> Phone and remove it where needed.
Your phone number isn't made public, but your separate accounts may now share the same number.
Worth checking.
Some users report this setting turning itself back on after disabling it.
Save this checklist and check again from time to time, especially after Android updates.
ALT Android can automatically associate your phone number with multiple Google accounts on the same device. Disable automatic verification in Android settings, then review existing phone numbers separately in each Google account.
Blast is shutting down. Withdraw any remaining funds by 26 October 2026.
The Blast team has decided to wind the network down because operating costs now exceed revenue and they see no path to long-term sustainability. The network will stop.
You have until 26 October 2026 to withdraw through the normal Blast interface. After that date assets remain recoverable, but only by interacting directly with the Blast bridge contracts on Ethereum mainnet (the team has said they will publish instructions before the deadline).
What to do:👇
1. Check every address you used on Blast for leftover $ETH or other tokens. Even small amounts (a few dollars) are worth moving.
2. Look at any positions in pools or dApps that still have value.
3. Verify holdings on DeBank and on blastscan.io (open your address and check the asset-tokens tab). Swap remaining tokens to ETH first if liquidity still exists, then bridge.
4. Use the official bridge only: blast.io/en/bridge
5. If you used the Blast PWA, check those balances as well.
Official reminder and details from Blast: xitter.cf/blast/status/211015443…
Share this with anyone who has used Blast so they don’t leave money behind.
ALT Blast network ends 26 October 2026 - withdraw leftover ETH and tokens via the official bridge before the easy interface closes. Check DeBank and blastscan for remaining balances.
Reminder to withdraw your funds.
Withdrawal guide: docs.blast.io/withdrawals/wi…
If you hold funds in the PWA, make sure to withdraw those funds too.
You can bridge your BLAST to ethereum mainnet on the official bridge UI at blast.io (CA 0x71b9e0FD392713A14FCaB92D9aF7A21F47E3b1Fa).
Privacy grew, but billions still struggle to reach DeFi yield without friction.
Real progress comes from bridges that disappear into wallets and aggregators. Users don’t need to care about the routing layer itself.
More integrations -> more volume -> more fees -> a chance the system actually funds itself.
Announcements are easy. Working capital and proven volume are the real tests.
What privacy-to-DeFi connection are you watching most closely right now?
1/9 🧵 Privacy ecosystem update
Crypto is finally turning greener, $CLONE is waking up, and @Bridgeless_com team is in Singapore for @token2049 discussing investors, integrations and Bridgeless’ next phase.
A quick recap of projects @whale_zone has been close to: $BRIDGE, $CLONE, $SWAP and zano:native. 👇
bobesh · DeFi & OpSec retweeted
Thank you to everyone who joined Off the Record in Singapore on Sunday.
A full table of founders, investors and builders, and an evening on private onchain finance. What was said stays there.
We could not seat everyone who asked, so Vol. 2 follows on Thursday 8 October: a private lunch, twelve seats, by approval.
Request a seat: luma.com/gxpmp4ml
Privacy is growing, but private assets are still mostly isolated.
The bigger opportunity is making them usable across DeFi without giving up the privacy that made them valuable in the first place.
That infrastructure layer matters.
Good luck to the @Bridgeless_com team in Singapore.
Why I'm in Singapore this week.
In a year the privacy sector grew 5X from $7B to $35B while the rest of the market fell about 30%.
Yet over $30B in privacy coins earns no yield, and only about 0.1% of DeFi is private.
Where this goes:
- Bitcoin that earns without being seen.
- Dollars that move in private.
- Privacy coins that go to work in DeFi.
It doesn't matter which privacy chain wins. The volume between it and the rest of the market needs a road. That road is what we build at @Bridgeless_com.
Tonight we host founders and investors. We have received overwhelming interest, so a second table follows on Thursday (luma.com/gxpmp4ml).
Token2049 week starts tomorrow.
This kind of signal is a real piece of a good trade.
Not the whole trade. One piece you actually want in the puzzle.
Two tracked wallets added the same side in 24h. $ENA about $473K long. $LIT about $393K long. Same direction, not one random wallet.
That is the useful part. A single whale screenshot is easy to dress up with a story. A small cluster on the same side is harder to ignore.
Still only one piece.
A trade that holds up usually needs more than flow:
1. your own reason to be in
2. where the idea is wrong
3. a size you can sit with
4. whether this is a new add, or a hedge
Do you count a signal at 2 wallets, or do you wait for 3?
A better quote is not the same as a better fill.
Most aggregators compete on the price they show you before you click.
CoW Swap competes on what happens after you sign.
That gap is where MEV lives.
On a normal aggregator, your trade sits in the mempool. Bots can see it, sandwich it, and take the edge you thought you had.
On CoW Protocol you sign an intent. Solvers settle it for you. The order does not wait in public mempool to be hunted.
If opposing intents can be matched directly, solvers can avoid external pool liquidity for that part of the trade.
Solvers then compete across P2P matches and external liquidity. The auction selects the execution that best satisfies its objective - not simply the flashiest pre-trade quote.
I still check 1inch, Matcha and others. Sometimes they quote better.
I still default to CoW when size is large enough that execution quality matters more than a pretty number.
Save this if you keep losing edge on “good looking” swaps.
What do you check first: quoted price, or how the trade will settle?
Why I recommend using CoW Swap as a DEX aggregator:
- Most DEX aggregators optimise routing.
- CoW Swap optimises execution.
swap.cow.fi?ref=BOBESH
That is a big difference. Stop letting MEV bots "sandwich" your hard-earned gains. 🥪❌
CoW Protocol (Coincidence of Wants) batches signed orders into auctions where solvers compete to find the best settlement. Before tapping on-chain liquidity, they first try to match users directly.
Why that matters:
1. One of the strongest MEV protections in DeFi
CoW Swap is built to reduce exposure to MEV, especially sandwich attacks from bots trying to exploit transactions in the mempool.
2. Coincidence of Wants = direct peer-to-peer matching
When trades can be matched directly between users, you can get:
- lower slippage
- fewer LP fees
- better MEV resistance
3. Solver competition + surplus + combinatorial auctions
Multiple solvers compete to deliver the best execution for each batch.
That can mean:
- better settlement quality
- price improvement for users (surplus)
- more efficient use of liquidity across the whole batch
4. Gasless Intent-based execution
With many orders, fees can be paid in the token being sold, so users do not always need to worry about keeping extra ETH aside for gas.
5. Advanced order types
CoW Swap supports features like limit orders, TWAP, and programmatic orders, which makes it especially useful for larger trades where even small slippage or MEV can become expensive.
- Does CoW Swap always give the absolute best executed price?
Not necessarily. Sometimes 1inch or Matcha may quote better.
- But when it comes to execution quality, MEV protection, and fairer settlement, CoW Swap is one of the most compelling options on the market.
Stop being the liquidity for someone else’s bot. Start using a protocol that actually fights for your execution. 🐮
Like & repost to let know your riends!
#Ethereum #DeFi #CryptoTrading #MEV
If you want to test the difference yourself, use the same flow I described above:
swap.cow.fi?ref=BOBESH
Before you click swap, check two things:
1. You are signing an intent, not broadcasting a raw swap into the public mempool
2. After settlement, compare the quoted amount with what you actually received
Small detail: this is a referral link. On CoW, both sides can earn $USDC at volume milestones. I am not hiding that.
Do one small swap and compare quoted price vs settled price. That single check teaches more than any thread.
ALT Quoted price is what an aggregator shows before you click. Settled fill is what you actually get after MEV, slippage and routing. CoW Swap signs an intent, tries peer-to-peer matching first, then lets solvers compete for surplus instead of leaving your swap in the public mempool.
TP means take profit.
A screenshot of green PnL is not the same thing.
The photo feels like a win. The profit is still unrealised.
Worse: that image is a public note. It can reveal the exchange, position size, time, and sometimes clues about your device.
In a bull market the picture travels further than your plan. Then people hold, because the screenshot already felt like the exit.
A simple rule I use:
1. Write the exit before you enter.
2. Sell in pieces, not in one hero click.
3. Move funds you no longer need for trading to safer storage.
4. Do not post the number.
The flex is profit you actually realised and still control.
Not a green rectangle on X.
What is your take-profit rule this cycle?
Save this if you keep taking the photo instead of the profit.
If you have funds on @bitget, withdraw them now.
On-chain data from the last few hours shows large outflows from wallets labelled as Bitget hot and cold wallets.
Reported size so far: about $100M to $180M (or up to $500M).
Assets mentioned: USDT, $ETH, $BTC, AVAX, BNB.
Funds appear to be moving to a small set of new addresses.
Bitget has not confirmed a hack yet.
That does not mean you should wait for a press post.
What to do right now:
1. Move funds from Earn, Futures, copy trading and bots back to Spot.
2. Withdraw to a wallet you control. Prefer a hardware wallet.
3. Double-check the network and the address. One wrong chain and the coins are gone.
4. Ignore DMs, "support" links, and anyone offering help in replies.
5. If withdrawal is pending or stuck, do not keep retrying with new addresses from chat.
This is the usual pattern after a CEX scare:
fake Bitget emails, fake apps, fake "refund" pages, and cloned support accounts.
Not your keys, not your coins is not a slogan tonight.
It is the only rule that still works when an exchange goes quiet.
Have you tried to withdraw?
Did it go through, or is it stuck?
Save this so you have the checklist if withdrawals get worse.
ALT Bitget withdrawal warning from @CryptoBobesh: on-chain outflows from exchange wallets are unconfirmed, move funds to a wallet you control and ignore unofficial support messages.
bobesh · DeFi & OpSec retweeted
Most Hyperliquid tools show you what whales bought.
This one grades whether it actually worked.
I can genuinely recommend giving DexiScan a look.
What I like most is the approach: track vetted wallets, test group behaviour, and show the results - including when the data says unproven.
No cherry-picked wins. No pretending every signal works.
That kind of transparency is rare in trading tools.
I spent two years being an exit liquidity for better traders.
So I started building a tool that shows what the best Hyperliquid wallets are doing, and grades whether it actually worked. Including the weeks it didn't.
The long version.
Courses, groups, signal channels — not one of them ever showed a number you could check. And in trading you're alone with your own decisions. Unless you have a mentor, or get to watch an experienced trader at work, you get into trouble fast. I did.
I wanted to read market sentiment. Not the crowd's, most traders lose money long term. I wanted the sentiment of the best.
That's the hard part. Not every million-dollar portfolio knows what it's doing. So I started building filters to separate the truly profitable wallets from the merely big ones. Every wallet gets scored on its full history: risk-adjusted return, drawdown, consistency, tenure.
That's how Smart Money Wallet Scanner started. Today it's DexiScan.
What I wanted to know:
What are they buying?
What are they selling?
Are they taking on risk or derisking?
Why not just copy a few whales? Because they're human. Even the best ones get it wrong.
So I don't follow any single wallet. I track almost 200 vetted wallets and watch for the moments when 3 or more of them lean the same way on the same coin. Say, short BTC.
Does a group beat one wallet? That's exactly what I test. Every call gets graded: MFE, MAE, R:R and PnL on a fixed horizon. Hit rate is measured against the real base rate, which isn't 50%.
Each one ends up BEATS, INVERTED or UNPROVEN. Right now a lot of them say UNPROVEN, and that's public too. I'd rather show you that than a screenshot of one good week.
I built this because I needed it. Today anyone can use it.
bobesh · DeFi & OpSec retweeted
This is the highest compliment we could get. Tracking whales is useless if signals bleed out — proving what actually worked is the core of DexiScan. Thanks for the shoutout @CryptoBobesh!
Most Hyperliquid tools show you what whales bought.
This one grades whether it actually worked.
I can genuinely recommend giving DexiScan a look.
What I like most is the approach: track vetted wallets, test group behaviour, and show the results - including when the data says unproven.
No cherry-picked wins. No pretending every signal works.
That kind of transparency is rare in trading tools.
Most Hyperliquid tools show you what whales bought.
This one grades whether it actually worked.
I can genuinely recommend giving DexiScan a look.
What I like most is the approach: track vetted wallets, test group behaviour, and show the results - including when the data says unproven.
No cherry-picked wins. No pretending every signal works.
That kind of transparency is rare in trading tools.
I spent two years being an exit liquidity for better traders.
So I started building a tool that shows what the best Hyperliquid wallets are doing, and grades whether it actually worked. Including the weeks it didn't.
The long version.
Courses, groups, signal channels — not one of them ever showed a number you could check. And in trading you're alone with your own decisions. Unless you have a mentor, or get to watch an experienced trader at work, you get into trouble fast. I did.
I wanted to read market sentiment. Not the crowd's, most traders lose money long term. I wanted the sentiment of the best.
That's the hard part. Not every million-dollar portfolio knows what it's doing. So I started building filters to separate the truly profitable wallets from the merely big ones. Every wallet gets scored on its full history: risk-adjusted return, drawdown, consistency, tenure.
That's how Smart Money Wallet Scanner started. Today it's DexiScan.
What I wanted to know:
What are they buying?
What are they selling?
Are they taking on risk or derisking?
Why not just copy a few whales? Because they're human. Even the best ones get it wrong.
So I don't follow any single wallet. I track almost 200 vetted wallets and watch for the moments when 3 or more of them lean the same way on the same coin. Say, short BTC.
Does a group beat one wallet? That's exactly what I test. Every call gets graded: MFE, MAE, R:R and PnL on a fixed horizon. Hit rate is measured against the real base rate, which isn't 50%.
Each one ends up BEATS, INVERTED or UNPROVEN. Right now a lot of them say UNPROVEN, and that's public too. I'd rather show you that than a screenshot of one good week.
I built this because I needed it. Today anyone can use it.
bobesh · DeFi & OpSec retweeted
We have a partial port of GrapheneOS to the Pixel 11 series after a week of work on it. We're unable to complete the port due to lack of support for ARM hardware memory tagging in software, firmware and near certainly hardware. It appears Google cut an important security feature to save money.
ARM hardware memory tagging (MTE) is used by GrapheneOS across the entire base OS including the kernel and every standard base OS process. It's only temporarily disabled for a few device-specific processes. It greatly improves protection against nearly all remote exploits and many local exploits.
Pixel 8 launched with hardware MTE support in October 2023. We integrated it into our hardened_malloc project and began using it across the OS later that month. Android and the Pixel OS never started using it by default. Android Advanced Protection Mode in Android 16 enables it for a few processes.
Apple's Memory Integrity Enforcement (MIE) is an always enabled feature on the iPhone 17. It's simply a high quality implementation of MTE using the latest standard extensions. It uses MTE in the most secure mode in the kernel and a large portion of userbase. They did a very good job integrating it.
Apple's MIE and Android 16+ AAPM don't use MTE for user installed apps unless those explicitly opt in. GrapheneOS enables it for more apps automatically and has a toggle for users to opt-in for every user installed app. There's a per-app toggle to opt-out for incompatible apps which is uncommon.
Neither iOS or Android encourage app developers to opt into MTE and other more aggressive security features used in the base OS. Apple's docs warn developers of performance and stability issues. Even Signal doesn't opt-in. Our approach enables forcing using MTE in the standard allocators regardless.
Pixel 11 does have security improvements including moving to post-quantum secure verified boot (ML-DSA) and replacing Samsung Shannon IMS with AOSP IMS. Titan M3 should significantly improve protection against data extraction in Before First Unlock state. It's too bad they ruined it by cutting MTE.
Pixel 11 series is a lot more expensive for an incremental improvement to the CPU, the same underpowered GPU and reduced RAM for the Pro base models. They finally caught up to the last generation of Qualcomm cellular radio. It's overpriced, the upgrades aren't impressive and losing MTE is appalling.
Compared to the Pixel 11, a Snapdragon 8 Elite Gen 5 has ~40% higher single threaded CPU performance, ~80% higher multi threaded performance, over 100% higher GPU performance and a far better cellular radio. It also finally has MTE. The next gen is what will be in the first Motorola with GrapheneOS.
Pixel 9a and earlier (including Nexus devices) were the Android Open Source Project reference devices. Pixel support was removed from AOSP with Android 16. It's now harder to support Pixels than many other devices and massive progress towards open source firmware and driver libraries was discarded.
Compared to the stock Pixel OS, GrapheneOS ships AOSP patches months earlier and Linux kernel patches many months earlier. However, we rely on them for firmware and most driver updates. We also want to move to new kernel branches earlier. These things can be improved with our Motorola partnership.
We strongly recommend against buying Pixel 11 devices. Pixel 8, 9 and 10 have much better overall security for GrapheneOS. Pixel 10 is cheaper with similar hardware and MTE. Pixel 11's Titan M3 should improve BFU security for users without a strong passphrase, but losing MTE craters AFU security.
We haven't determined what to do about this situation. It may be best for us to skip the Pixel 11 series devices. We can shift our focus entirely to the upcoming Motorola devices instead. Pixel 10a was really a 9th gen Pixel, so hopefully the Pixel 11a does the same with 10th gen and includes MTE.
🚨If you use Ledger for ETH, check your Ethereum app version today.
1.22.2 is the minimum you want.
A connected malicious app could swap the transaction in memory during signing. The screen could still show the old details.
- Fixed in Ethereum app 1.22.2 or later.
- Nano S was not affected by this specific bug.
- No confirmed stolen funds so far.
1. Open Ledger Live/Wallet
2. My Ledger Update firmware
3. Update the Ethereum app
4. Confirm the version before you sign again
This was not a seed or private-key leak. The problem was that an outdated Ethereum app could sign something different from what the device screen showed you.
🚨Critical security update for LEDGER hardware wallets
A critical vulnerability has been identified in the Ethereum app on Ledger hardware wallets. It could allow a malicious application to alter the details of a transaction during signing, without this being visible on the device screen.
This has been fixed in Ethereum app version 1.22.2. If you use a Ledger device, please update ASAP
While you're in there, it's also good practice to make sure Ledger Live and your device firmware are fully up to date.
bobesh · DeFi & OpSec retweeted
$ETH is still the only major token below its 2021 high — and that is exactly why the setup is asymmetric.
Ethereum remains the largest onchain hub for stablecoins and RWAs. If the base layer securing internet capital markets is responsible for tens of trillions in value, ETH does not get priced like a generic L1 asset; it gets priced for settlement dominance and security demand.
That mechanism matters:
- stablecoins + RWAs pull liquidity and collateral onchain
- institutions route serious issuance and settlement where capital is deepest
- more settlement increases demand for Ethereum blockspace and for ETH-backed security
- once price clears key levels, reflexivity accelerates the repricing
We view $5k as a trigger, not an endpoint. From there, the market starts reopening higher probability bands like $19k-$27k, with upside scenarios extending toward $40k over time.
The bigger point: if Ethereum remains the home of internet capital markets and onchain options liquidity, a 40-50x multi-year outcome is not extreme.
What we’re watching next: continued stablecoin/RWA concentration on Ethereum and the first decisive break that turns ETH from “the only major laggard vs 2021 highs” into the market’s catch-up trade.
In 2025, over $4B was stolen in crypto.
Only ~13% came from smart contract code vulnerabilities.
The rest? Compromised private keys. Phishing. Forgotten approvals. Rushed clicks.
Here's the DeFi security checklist that would prevent most of it.
Most people ask: "Is this protocol audited?"
Good question - just not the first one to ask. And not a shield either.
You are the biggest attack surface in DeFi. Not the smart contract.
🔒 WALLET SETUP
- Hardware wallet for anything you'd actually miss
- Separate hot wallet for daily DeFi - never your main storage
- Seed phrase on paper, offline only - never typed, photographed or stored digitally
- Never "test" a new protocol with your main wallet
🔍 BEFORE YOU CONNECT
- Bookmark the official URL - don't click links from Google/X/Discord/email
- Verify the contract address in the official docs, not just the front-end
- Has this protocol been running for at least 6–12 months?
- Find the audit report in the project's official docs or GitHub (and who did it)
- Check TVL on DeFiLlama - any sudden drops recently?
⚠️ TOKEN APPROVALS - the most underrated risk in DeFi
Every time you click "approve" you create an on-chain permission.
Disconnecting your wallet does not remove it.
- Use exact-amount approvals where possible, not unlimited
- "Sign Message" requests can be approvals too - permit signatures work the same way but look different
- Revoke approvals regularly -> revoke cash
- Check existing approvals before using any new protocol
- $500M+ lost to approval exploits in 2024–2025 alone
⚙️ TRANSACTION HYGIENE
- Never sign a transaction you cannot read and understand
- Hardware wallet users: read your device screen before confirming - don't just tap through
- Blind signing = trusting the front-end completely. One hacked website and you're done
- Rabby Wallet shows a transaction simulation before you sign - use it
🎭 SOCIAL ENGINEERING
This is where most retail losses actually go.
- Nobody legitimate will DM you first on Discord or Telegram
- "You've been selected for an airdrop" = phishing, every time
- Verified accounts on X (or Discord servers) get hacked too - regularly used to push scam links
- Urgency is a manipulation tactic. If something feels urgent, slow down
🚨 EMERGENCY PLAN
Most people don't have one until they need it.
- Have a second wallet ready to receive funds fast
- Know how to revoke approvals in under 2 minutes - practice before you need it
- Always keep gas in your hot wallet, you cannot move funds without it (not applicable in case of sweeper bots)
- Know your exit route in advance: which bridge or CEX would you use in a crisis?
Security in DeFi is mostly a habits game.
Going through this before trying any new protocol takes about 10 minutes.
Most people skip it. Most losses happen to people who skipped it.
Save this. Share it with someone who needs it.
What's missing from the list? Drop it below.
ALT DeFi Security Checklist infographic. Six categories: wallet setup, before you connect, token approvals, transaction hygiene, social engineering, emergency plan. Context: $3.4B stolen in crypto in 2025, most from compromised keys and phishing - not smart contract bugs.
Looping multiplies your yield in DeFi. The same maths can liquidate you.
Here is how it works and where people get hurt.
Deposit a yield-bearing asset, borrow against it, buy more of the same, repeat. Each loop stacks more exposure on the same capital, so a small base yield can turn into a much larger one. The whole trade lives or dies on one number: your collateral yield minus your borrow cost.
Two ways it breaks:
Negative carry. Borrow rates float. When they rise above your yield, you are paying to stay in. The stETH-on-Aave $ETH loop is the one everyone points to: by most accounts it stopped paying in 2025 as the gap between borrow cost and yield closed. Spreads move, so a loop that prints today can bleed tomorrow.
Depeg. Looped assets are meant to track 1:1, but under stress they don't. ezETH fell near $700 in April 2024 and wiped out roughly $56M of looped positions. stETH traded about 6% under ETH in 2022. Leverage turns a small gap into a liquidation.
How to stay safe:
1. Keep your health factor high. Leave room for a depeg, not just a price move.
2. Use only highly correlated assets, but do not stop there. Check redemption, exit queues, oracle design and on-chain liquidity.
3. Watch net APY live, borrow utilisation and liquidation threshold, not just the headline yield.
For: people who monitor positions and understand liquidation maths.
Not for: anyone treating it as passive income.
Before looping, ask one question: how much can the collateral depeg before my position is liquidated?
Bookmark this before your next risk check.
