<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Block Experts</title>
        <link>https://paragraph.com/@block-experts</link>
        <description>I'm blockchain engineer, building some web3 stuffs.</description>
        <lastBuildDate>Sun, 06 Sep 2026 03:50:10 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>Block Experts</title>
            <url>https://storage.googleapis.com/papyrus_images/7bd0973f21faeaa7947b35f4f6c00bbe90f0d16043c83468ae99b2feecd24a5d.png</url>
            <link>https://paragraph.com/@block-experts</link>
        </image>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[Get Your Locked SOL Back: 200+ Accounts Cleaned Up Today for 0.48 SOL]]></title>
            <link>https://paragraph.com/@block-experts/get-your-locked-sol-back-200-accounts-cleaned-up-today-for-0-48-sol</link>
            <guid>crnsRe7ZCxuhVZFHOk66</guid>
            <pubDate>Sat, 23 Aug 2025 23:19:35 GMT</pubDate>
            <description><![CDATA[🚀 My Solana Account Cleanup Tool: 200+ Accounts Closed Today!I built a tool to help clean up unused Solana accounts, and today we hit a milestone: over 200 unused accounts closed with 0.48 SOL total volume reclaimed!Why This MattersGet Your SOL Back: Reclaim locked funds from unused token accountsNetwork Optimization: Reduce blockchain state bloatBetter Performance: Help validators run more efficientlyHow It WorksVisit claimyoursols.app:Connect your walletScan for closeable accountsClose unu...]]></description>
            <content:encoded><![CDATA[<h1 id="h-my-solana-account-cleanup-tool-200-accounts-closed-today" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">🚀 My Solana Account Cleanup Tool: 200+ Accounts Closed Today!</h1><p>I built a tool to help clean up unused Solana accounts, and today we hit a milestone: <strong>over 200 unused accounts closed with 0.48 SOL total volume reclaimed</strong>!</p><h2 id="h-why-this-matters" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Why This Matters</h2><ul><li><p><strong>Get Your SOL Back</strong>: Reclaim locked funds from unused token accounts</p></li><li><p><strong>Network Optimization</strong>: Reduce blockchain state bloat</p></li><li><p><strong>Better Performance</strong>: Help validators run more efficiently</p></li></ul><h2 id="h-how-it-works" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">How It Works</h2><p>Visit <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="http://claimyoursols.app">claimyoursols.app</a>:</p><ol><li><p>Connect your wallet</p></li><li><p>Scan for closeable accounts</p></li><li><p>Close unused accounts (empty accounts, unwanted tokens, mint tokens you created and you don’t want anymore)</p></li><li><p>Reclaim your locked SOL</p></li></ol><p><strong>What you can close:</strong></p><ul><li><p>Empty token accounts</p></li><li><p>Tokens you no longer need</p></li><li><p>Test tokens you created during development</p></li><li><p>Unwanted airdropped tokens</p></li></ul><h2 id="h-for-developers" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">For Developers</h2><pre data-type="codeBlock" text="// Account closure process
const closeInstruction = createCloseAccountInstruction(
  accountToClose,
  destination, 
  owner
);
"><code>// Account closure process
const <span class="hljs-attr">closeInstruction</span> = createCloseAccountInstruction(
  accountToClose,
  destination, 
  owner
)<span class="hljs-comment">;</span>
</code></pre><h2 id="h-open-source" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Open Source</h2><p>The entire project is <strong>open source</strong> at <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/dawar2151/claimyoursols.app">github.com/dawar2151/claimyoursols.app</a> - full transparency and community contributions welcome. You can audit the code, submit improvements, and verify exactly what it does before connecting your wallet.</p><p>⭐ <strong>If you try it or like the project, please star it on GitHub!</strong> ⭐</p><h2 id="h-join-the-movement" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Join the Movement</h2><ul><li><p>Clean up your unused accounts</p></li><li><p>Help optimize the Solana network</p></li><li><p>Reclaim your locked SOL</p></li></ul><p>Let&apos;s keep the momentum going! 🌟</p>]]></content:encoded>
            <author>block-experts@newsletter.paragraph.com (Block Experts)</author>
        </item>
        <item>
            <title><![CDATA[How do some dApps pretend to have verified contracts when they don't?]]></title>
            <link>https://paragraph.com/@block-experts/how-do-some-dapps-pretend-to-have-verified-contracts-when-they-don-t-2</link>
            <guid>XgQu39hdMjvK1USAiSWq</guid>
            <pubDate>Wed, 30 Jul 2025 07:51:39 GMT</pubDate>
            <description><![CDATA[Recently, I started interacting with many DApps for DeFi, airdrops, or NFT exchanges. I noticed that most of the time, DApps are marked as "contract verified", but in many cases, only the proxy contract is verified—not the implementation. What does that actually mean? And is the contract truly verified in such cases? Let’s break it down below. let&apos;s start with some context: The concept of upgradable smart contracts on Ethereum began emerging around 2017, with more formal and secure patte...]]></description>
            <content:encoded><![CDATA[<p>Recently, I started interacting with many DApps for DeFi, airdrops, or NFT exchanges. I noticed that most of the time, DApps are marked as <strong>&quot;contract verified&quot;</strong>, but in many cases, <strong>only the proxy contract is verified—not the implementation</strong>.</p><p>What does that actually mean? And is the contract truly verified in such cases?</p><p>Let’s break it down below.</p><p>let&apos;s start with some context:</p><p>The concept of <strong>upgradable smart contracts</strong> on Ethereum began emerging around 2017, with more formal and secure patterns being adopted by 2018.</p><p>Many decentralized applications (DApps) started using this pattern to prevent and mitigate vulnerabilities that could appear in the future.</p><h2 id="h-what-are-upgradable-smart-contracts" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">What Are Upgradable Smart Contracts?</h2><p><strong>Upgradable smart contracts</strong> follow a simple architecture:</p><ul><li><p>A <strong>proxy contract</strong> holds the data (storage)</p></li><li><p>An <strong>implementation contract</strong> contains the business logic</p></li></ul><p>When you deploy the proxy, it stays fixed. However, you can <strong>upgrade</strong> the implementation contract at any time—<strong>without changing the proxy address</strong> or notifying users. This makes upgrades seamless, but also <strong>potentially dangerous</strong>: a malicious owner could swap in harmful logic without anyone noticing.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/f23438afa53ae9d19a44e0292b30d213567a604ee28db060745d9d3ff3f88fff.png" alt="Proxy and implementation diagram" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">Proxy and implementation diagram</figcaption></figure><p>As shown above, users always interact with the proxy. This proxy stores both the data and the reference to the implementation address.</p><p>The issue is: <strong>most users only check if the proxy is verified</strong>, and ignore the implementation. This gives a <strong>false sense of security</strong>, as the real logic could be unverified or even malicious.</p><hr><h2 id="h-real-world-examples" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Real-World Examples</h2><p>I checked several popular token tools. Most of them only verify the <strong>proxy</strong> but not the <strong>implementation</strong> contract.</p><h3 id="h-bulksenderapp" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0"><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://bulksender.app">BulkSender.app</a></h3><p>The proxy contract is verified, but the implementation is <strong>not</strong>:</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/44f619dde574d3773b92afc2db5396a5ef4507518ab3b370775ff910e54208d4.png" alt="Etherescan bulksender.app" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">Etherescan bulksender.app</figcaption></figure><hr><h3 id="h-cryptosendercom" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0"><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://cryptosender.com">CryptoSender.com</a></h3><p>Same story: the proxy is verified, the implementation is <strong>not</strong>.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/93ac8b48582b2038b4c0ae71cde82edaa76383f7cca0ac426251f4a62ed4274f.png" alt="Etherscan CryptoSender.com" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">Etherscan CryptoSender.com</figcaption></figure><hr><h3 id="h-bulksendtokensxyz" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0"><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://bulksendtokens.xyz">BulkSendTokens.xyz</a></h3><p>✅ In this case, <strong>both the proxy and implementation are verified</strong>, which is how it should be:</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/6991a07f0064e989f3060d8188903e24c83b3bddae2ed6b3d630f1539c39e9af.png" alt="Etherscan BULKSENDTOKENS.XYZ" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">Etherscan BULKSENDTOKENS.XYZ</figcaption></figure><hr><h2 id="h-why-this-matters" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Why This Matters</h2><p>When the implementation contract is unverified, users <strong>can&apos;t see what logic is being executed</strong>. That means:</p><ul><li><p>Hidden service fees could be added</p></li><li><p>Backdoors might exist</p></li><li><p>Logic could be changed at any time</p></li></ul><p>If both contracts are verified, everything becomes transparent: you can inspect the code, see the upgrade logic, and ensure there&apos;s no malicious behavior.</p><hr><h2 id="h-stay-safe" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">✅ Stay Safe</h2><ul><li><p>Always check <strong>both proxy and implementation</strong> contracts are verified</p></li><li><p>Don’t trust a verified proxy alone—it holds <strong>no logic</strong></p></li><li><p>Be cautious with tools that don’t verify everything</p></li></ul><hr><h2 id="h-follow-my-work" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Follow My Work</h2><p>I&apos;m building secure tools in the blockchain space—follow me for updates:</p><p>🐦 <strong>X (Twitter):</strong> <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/TheBlockExperts">@TheBlockExperts</a></p><hr><h2 id="h-blockchain-developer-tools-i-built" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">🛠️ Blockchain Developer Tools I Built</h2><ul><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://codecanyon.net/item/xwallet-an-airdrop-ethereum-wallet/50663324"><strong>X-Wallet: An Airdrop &amp; Asset Management Ethereum Wallet</strong></a></p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://bulksendtokens.xyz/"><strong>Bulk Sender for Ethereum</strong></a></p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://solana.bulksendtokens.xyz/"><strong>Bulk Sender for Solana</strong></a></p></li></ul><hr><p>Stay safe out there 👊</p><p>Originally published on <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://bulksendtokens.xyz">https://bulksendtokens.xyz</a></p>]]></content:encoded>
            <author>block-experts@newsletter.paragraph.com (Block Experts)</author>
        </item>
        <item>
            <title><![CDATA[How do some dApps pretend to have verified contracts when they don't?]]></title>
            <link>https://paragraph.com/@block-experts/how-do-some-dapps-pretend-to-have-verified-contracts-when-they-don-t</link>
            <guid>hiEYEPRjZ2QA9B2KKZbh</guid>
            <pubDate>Wed, 30 Jul 2025 07:42:18 GMT</pubDate>
            <description><![CDATA[Recently, I started interacting with many DApps for DeFi, airdrops, or NFT exchanges. I noticed that most of the time, DApps are marked as "contract verified", but in many cases, only the proxy contract is verified—not the implementation. What does that actually mean? And is the contract truly verified in such cases? Let’s break it down below. let&apos;s start with some context: The concept of upgradable smart contracts on Ethereum began emerging around 2017, with more formal and secure patte...]]></description>
            <content:encoded><![CDATA[<p>Recently, I started interacting with many DApps for DeFi, airdrops, or NFT exchanges. I noticed that most of the time, DApps are marked as <strong>&quot;contract verified&quot;</strong>, but in many cases, <strong>only the proxy contract is verified—not the implementation</strong>.</p><p>What does that actually mean? And is the contract truly verified in such cases?</p><p>Let’s break it down below.</p><p>let&apos;s start with some context:</p><p>The concept of <strong>upgradable smart contracts</strong> on Ethereum began emerging around 2017, with more formal and secure patterns being adopted by 2018.</p><p>Many decentralized applications (DApps) started using this pattern to prevent and mitigate vulnerabilities that could appear in the future.</p><h2 id="h-what-are-upgradable-smart-contracts" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">What Are Upgradable Smart Contracts?</h2><p><strong>Upgradable smart contracts</strong> follow a simple architecture:</p><ul><li><p>A <strong>proxy contract</strong> holds the data (storage)</p></li><li><p>An <strong>implementation contract</strong> contains the business logic</p></li></ul><p>When you deploy the proxy, it stays fixed. However, you can <strong>upgrade</strong> the implementation contract at any time—<strong>without changing the proxy address</strong> or notifying users. This makes upgrades seamless, but also <strong>potentially dangerous</strong>: a malicious owner could swap in harmful logic without anyone noticing.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/f23438afa53ae9d19a44e0292b30d213567a604ee28db060745d9d3ff3f88fff.png" alt="Proxy and implementation diagram" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">Proxy and implementation diagram</figcaption></figure><p>As shown above, users always interact with the proxy. This proxy stores both the data and the reference to the implementation address.</p><p>The issue is: <strong>most users only check if the proxy is verified</strong>, and ignore the implementation. This gives a <strong>false sense of security</strong>, as the real logic could be unverified or even malicious.</p><hr><h2 id="h-real-world-examples" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Real-World Examples</h2><p>I checked several popular token tools. Most of them only verify the <strong>proxy</strong> but not the <strong>implementation</strong> contract.</p><h3 id="h-bulksenderapp" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0"><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://bulksender.app">BulkSender.app</a></h3><p>The proxy contract is verified, but the implementation is <strong>not</strong>:</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/44f619dde574d3773b92afc2db5396a5ef4507518ab3b370775ff910e54208d4.png" alt="Etherescan bulksender.app" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">Etherescan bulksender.app</figcaption></figure><hr><h3 id="h-cryptosendercom" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0"><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://cryptosender.com">CryptoSender.com</a></h3><p>Same story: the proxy is verified, the implementation is <strong>not</strong>.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/93ac8b48582b2038b4c0ae71cde82edaa76383f7cca0ac426251f4a62ed4274f.png" alt="Etherscan CryptoSender.com" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">Etherscan CryptoSender.com</figcaption></figure><hr><h3 id="h-bulksendtokensxyz" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0"><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://bulksendtokens.xyz">BulkSendTokens.xyz</a></h3><p>✅ In this case, <strong>both the proxy and implementation are verified</strong>, which is how it should be:</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/6991a07f0064e989f3060d8188903e24c83b3bddae2ed6b3d630f1539c39e9af.png" alt="Etherscan BULKSENDTOKENS.XYZ" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">Etherscan BULKSENDTOKENS.XYZ</figcaption></figure><hr><h2 id="h-why-this-matters" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Why This Matters</h2><p>When the implementation contract is unverified, users <strong>can&apos;t see what logic is being executed</strong>. That means:</p><ul><li><p>Hidden service fees could be added</p></li><li><p>Backdoors might exist</p></li><li><p>Logic could be changed at any time</p></li></ul><p>If both contracts are verified, everything becomes transparent: you can inspect the code, see the upgrade logic, and ensure there&apos;s no malicious behavior.</p><hr><h2 id="h-stay-safe" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">✅ Stay Safe</h2><ul><li><p>Always check <strong>both proxy and implementation</strong> contracts are verified</p></li><li><p>Don’t trust a verified proxy alone—it holds <strong>no logic</strong></p></li><li><p>Be cautious with tools that don’t verify everything</p></li></ul><hr><h2 id="h-follow-my-work" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Follow My Work</h2><p>I&apos;m building secure tools in the blockchain space—follow me for updates:</p><p>🐦 <strong>X (Twitter):</strong> <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://x.com/TheBlockExperts">@TheBlockExperts</a></p><hr><h2 id="h-blockchain-developer-tools-i-built" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">🛠️ Blockchain Developer Tools I Built</h2><ul><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://codecanyon.net/item/xwallet-an-airdrop-ethereum-wallet/50663324"><strong>X-Wallet: An Airdrop &amp; Asset Management Ethereum Wallet</strong></a></p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://bulksendtokens.xyz/"><strong>Bulk Sender for Ethereum</strong></a></p></li><li><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://solana.bulksendtokens.xyz/"><strong>Bulk Sender for Solana</strong></a></p></li></ul><hr><p>Stay safe out there 👊</p><p>Originally published on <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://blog.bulksendtokens.xyz">https://blog.bulksendtokens.xyz</a></p>]]></content:encoded>
            <author>block-experts@newsletter.paragraph.com (Block Experts)</author>
        </item>
    </channel>
</rss>