<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Delegatecall on pnasis</title>
    <link>https://pnasis.gitlab.io/tags/delegatecall/</link>
    <description>Recent content in Delegatecall on pnasis</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 29 Jun 2026 19:16:35 +0300</lastBuildDate>
    <atom:link href="https://pnasis.gitlab.io/tags/delegatecall/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SekaiCTF 2026 - Blockchain Writeups (Part 2): PP Farming 2</title>
      <link>https://pnasis.gitlab.io/posts/sekaictf-2026-blockchain-writeups-part-2-pp-farming-2/</link>
      <pubDate>Mon, 29 Jun 2026 19:16:35 +0300</pubDate>
      <guid>https://pnasis.gitlab.io/posts/sekaictf-2026-blockchain-writeups-part-2-pp-farming-2/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;    This post continues my &lt;strong&gt;SekaiCTF 2026&lt;/strong&gt; writeup series, this time focusing on the second blockchain challenge I solved during the competition: &lt;strong&gt;PP Farming 2&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;    Unlike the first challenge, which revolved around a classic reentrancy vulnerability, this challenge presented a more subtle issue. The challenge author attempted to eliminate the original vulnerability by introducing a reentrancy guard, but in doing so accidentally introduced an entirely different class of vulnerability involving Solidity&amp;rsquo;s &lt;code&gt;delegatecall&lt;/code&gt; instruction.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
