@BrianSeong @envoy1084 Sorry to hear that. And we’ve definitely seen a rise of these attacks x.com/etherscan/stat…
If you don’t mind sharing what wallet UX was this on ?
etherscan.eth@etherscan
English
Matthew Tan
118 posts
Matthew Tan
@mtbitcoin
CEO @etherscan | @blockscanhq | @solscanofficial
Katılım Ağustos 2020
24 Takip Edilen4.5K Takipçiler
Tonight I paid $15,000 tuition learning why we need privacy in blockchain.
After ~6 years working in crypto, I thought of myself as a somewhat a veteran in the space. And yet I just got hit by an address poisoning attack while using the Uniswap wallet.
The ironic part? I knew about this attack already. But it was late at night in Korea and I wasn’t 100% focused.
Here’s what happened.
I moved $15k USDC into my wallet and sent a $1 test transaction first. It went through successfully.
A few minutes later I sent the remaining $15k.
But attackers had already been sending tiny dust transactions to my wallet from addresses that looked almost identical to the one I was interacting with.
In the wallet UI, addresses appear like “0xAAAAA…0000”, so visually they looked the same.
My $1 test went to the real address.
My $15k went to the poisoned one.
Because Ethereum is fully transparent, attackers can monitor wallets and craft these traps.
Two takeaways:
• Never copy addresses from wallet history
• Always verify the full address
Even if you know the attack — one moment of low attention is enough.
Just another day working in Crypto
English
Matthew Tan retweetledi
@cinesiusss @Zun2025 @etherscan Are there any specific reasons or challenges for not supporting it. Anything that you can share will be helpful and help us understand what we need to prioritize when building. Tq
English
@Zun2025 @etherscan Yes but not all wallets support WalletConnect
English
@AaronTeng @sssionggg @FoxyPenguinApe @PenguAsia One of the most hard working folks 👍, Aaron is “everywhere”
English
English
again would love to thank @AaronTeng and @FoxyPenguinApe from @PenguAsia for the tremendous help on catlumpurr!
❤️❤️❤️
English
@andrewhong5297 That was an un-handled exception. We will work on handling the exception better
English
@mert @checkprice Like the domain name, did you pay extra for it?
English
I am getting ready to launch @checkprice in closed alpha for feedback
you can already check prices but the trading stuff is all invite-only atm
thesis: chart shows you history. price shows you present. pred markets show you future.
reply or DM for code and testing group
English
@solscanofficial Solscan keeps shipping, zero fanfare just heads down building 🦾
English
Matthew Tan retweetledi
New year. Big update. Introducing:
Liquidity Position Value Tracking on Solscan 📊
We’re proud to provide comprehensive value tracking for DeFi liquidity positions from top Solana AMMs.
Built directly into the Portfolio view, accessible from both the Owner and Market level 🧵
English
@sssionggg I can vouch for #3, Siong is really a nice person irl. Ambitious yet Humble and smart.
English
okay. after staring at the screen for the last 12+ hours, going to take a break.
i will do a longer summary from what i have learned today but here is a short one:
- twitter is amazing in getting feedback from many people.
- i am not saying that we will do it. the point of this post is to gather feedback and learn.
- text may appear cold and unfriendly to people. talk to me in real life, i think you will like me.
- we don’t make 1.1b a year.
- majority of my net worth is about the JUP token. obviously i want it to go up.
⚔️ SIONG@sssionggg
what do you all think if we stop the JUP buyback? we spent more than 70m on buyback last year and the price obviously didn’t move much. we can use the 70m to give out for growth incentives for existing and new users. should we do it?
English
Visited Network School today with @tmlee and got to see firsthand what @balajis is creating.
Good vibes, strong community, and a powerful vision.
Very bullish on where this can go and excited to watch Balaji and @yash_luna grow this startup society
English
Matthew Tan retweetledi
🆕 Solscan Card: Sol Incinerator
Reclaiming your SOL by closing token accounts that you don’t use anymore.
Powered by the OG @solincinerator 🔥
English
Yes, built from scratch.
Since there’s no public OpenAPI spec for V2, I pulled in your documentation (via /llms.txt) to synthesize a strict schema.
That became the blueprint for the Zod validators and BigInt transport layer to ensure type safety.
Issues and suggestions are very welcome! 🤝
English
I have not personally tested or used this, but thank you for the effort. Did you build this from scratch ?
Roy Philip@royphilip_
Etherscan V1 was officially deprecated on August 15. Migration to V2 is mandatory. V2-native, financial-grade client: npm install etherscan-v2-sdk ✅ Type-safe. ✅ No floating-point math. ✅ 88% test coverage. ✅ Rate limiting built-in GitHub: github.com/royphilip/ethe…
English
Wait, so getAbi, getSourceCode and verifyContract are excluded from this limitation? These methods are still available on the free tier including on Base, OP and BNB?
If so, then I agree lol this is a little overblown (minus communication). I'll add a comment to my own post as well, you should add this somewhere as well because the docs do not make this clear at all.
English
Be @etherscan
> Offer FREE and generous APIs for 10+ years
> Made it clear that FREE APIs can evolve over time
> Continue running explorers even after some foundations drop funding
> Adds a small API fee (for a tiny subset of chains) to ensure long-term sustainability
> Still keep verified contract API endpoints free for all tiers across every supported network
> Watch the FUD roll in 🙄
info.etherscan.com/whats-changing…
English
@iakshatmittal @etherscan > All you have to do is to exclude the getAbi and verifyContract endpoints from this limitation and we're golden!
@iakshatmittal It was never removed in the first place. They continue to be available even under the free-tier. Thks
English
Just to be clear, it's not about making your APIs paid, they are good and you should be able to monetize them. I will continue to use Etherscan as well.
The problems are (1) the timing and essentially no communication about it; (2) verified contracts paywall; and (3) the entry level price of $50/mo.
All you have to do is to exclude the getAbi and verifyContract endpoints from this limitation and we're golden!
Mind you this is after the fact that Etherscan integrations run well over $1m, and you retain the right to monetize via ads.
English
@mtbitcoin @ijaack94 Please keep SnowScan running on Avalanche. That other website is dogshit.
Thanks
English
@ijaack94
Ah.. Ok Got it, so its kosher only when Routescan offers limited free tier access to selected chains only
docs.routescan.io/api-access?v=2…
jaack 🛡️ 🔺️@ijaack94
since i took a looong time understanding how their business works, let me tell you how etherscan maintains their explorers generally, they charge the chain directly, and that amount varies greatly, up to 1.5-2M/year but down to 300K in some cases for a very basic explorer with a limited feature set when they charge a chain, they usually give some time to developers to lock-in to their product and then ask to register an API key as a mandatory requirement (this doesn't happen with EVERY chain they support, but has happened very often) for the chains that pay, they offer free API plans up to 5 rps and then their usual pricing model up to 899/month but how do you know if a chain supports free APIs without looking at the documentation? it's actually very simple, yet not straightforward to most: they attach a 'A Scan Original' text under the explorer name so right now that includes the Beacon chain explorer, BNB chain, OP Mainnet (wow! this is new to me! @Optimism what happened?), @base , Snowscan for Avalanche (I still don't understand why they keep it alive since we run snowtrace.io, but ok) and HyperEVM In these cases, they make it very clear (at least to themselves and to who look close enough) that there's gotta be something LESS to provide since the foundation are not 'supporting' their work (1M/year, I remember to everyone) the thing is, the folks at etherscan don't realise that they're getting PAID A LOT, even if not from foundations directly they're getting paid via DIRECT LINKING: from wallets, docs, and other platforms as default explorers and that is HUGELY monetizable, because that's consistent traffic for example, semrush tells me that these are the UNIQUE VISITORS of etherscan's FREE explorers last month: - OP: 102K - BNB: 2.5M - Base: 1M - HyperEVM: 30K - Avalanche: 16K not even counting the 4M on etherscan dot io itself now, I do understand that MAYBE they can't monetize much from the 100K of OP, 30K of hyperEVM and 16K of Avalanche, but that also generally means that you need less traffic to provide via APIs instead, on 'free' explorers with LITERALLY MILLIONS of users every month, it's still unclear to me how they can't offer a free API plan FURTHERMORE, they are ofc monetizing from all these explorers: how would call the banners on all homepages and tx details and everywhere else so yeah, keep using etherscan as you're ONLY source of data guys, keep doing that if you do that, i'm happy they rug you just when you need it, sorry, I really can't be diplomatic when it comes to this
English
Lefteris, fair point on the comms that’s on me. And I have a lot of respect for the work you’re now doing with @rotkiapp.
That said, calling the @etherscan team “ruggers” in crypto feels harsh, especially coming from you. They’re some of the most dedicated, humble, and hard-working, non attention seeking folks I know off.
Also, it was never our intention to "pressure" anyone. I’m sure they had their reasons and I respect that, and it’s on us to keep adding enough value to justify continued support. We need to work harder and we will 🦾
On our end, we always work with the resources we have. In this case, reducing Free-API chain coverage by ~10% in a very short period of time was necessary to maintain the overall service at an acceptable level. The timing wasn't ideal and we could have done better with comms, but its not something that we planned for on when it happens
English
Matt everything else aside this should have been communicated at least a month in advance.
And definitely not done when the majority of Ethereum Devs are travelling during the biggest Ethereum event of the year.
What can the community do to pressure said foundations to support you?
English