<?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>jialigejia</title>
        <link>https://paragraph.com/@jialigejia</link>
        <description>undefined</description>
        <lastBuildDate>Thu, 27 Aug 2026 20:23:02 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>jialigejia</title>
            <url>https://storage.googleapis.com/papyrus_images/04c2ef1cc0725ab6946b9999ea77a2ec68c13848c408edbd1070f587e8842101.png</url>
            <link>https://paragraph.com/@jialigejia</link>
        </image>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[Slow fog: beware of the double flower attack risk of qanx tokens]]></title>
            <link>https://paragraph.com/@jialigejia/slow-fog-beware-of-the-double-flower-attack-risk-of-qanx-tokens</link>
            <guid>wxDvCu0j5L3zFWSTbYNh</guid>
            <pubDate>Sat, 26 Mar 2022 07:59:23 GMT</pubDate>
            <description><![CDATA[According to foresight news, according to the slow fog area, recently, malicious users have carried out a double flower attack by using the same event record triggered by the transfer locked / unlocked function of qanx token as the transfer event record triggered by normal transfer function. The slow fog security team suggests that the platforms that have been put on the shelf in this currency should conduct self inspection in time, and the platforms that have not been put on the shelf should...]]></description>
            <content:encoded><![CDATA[<p>According to foresight news, according to the slow fog area, recently, malicious users have carried out a double flower attack by using the same event record triggered by the transfer locked / unlocked function of qanx token as the transfer event record triggered by normal transfer function.</p><p>The slow fog security team suggests that the platforms that have been put on the shelf in this currency should conduct self inspection in time, and the platforms that have not been put on the shelf should pay attention to the above risks when docking with this currency</p>]]></content:encoded>
            <author>jialigejia@newsletter.paragraph.com (jialigejia)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/8fc044be98938512ff3131e9636e7b534f85f38b094161fca16d42cf53e54f3b.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[The credit account and agreement of gearbox protocol have been suspended due to vulnerabilities. The vulnerabilities have been fixed and will be deployed soon]]></title>
            <link>https://paragraph.com/@jialigejia/the-credit-account-and-agreement-of-gearbox-protocol-have-been-suspended-due-to-vulnerabilities-the-vulnerabilities-have-been-fixed-and-will-be-deployed-soon</link>
            <guid>AnlQdDCdC6A9pWuLT2yG</guid>
            <pubDate>Sat, 26 Mar 2022 07:57:47 GMT</pubDate>
            <description><![CDATA[According to foresight news, the gear box protocol of the defi general leverage agreement tweeted that after receiving the vulnerability report from immunefi, the credit account has been suspended by technical multi signature, and there is no security risk in the funds. However, the current agreement has been suspended. After that, the problem has been confirmed and the vulnerability has been possibly repaired. It will be deployed after the review, and the agreement will be reopened at that t...]]></description>
            <content:encoded><![CDATA[<p>According to foresight news, the gear box protocol of the defi general leverage agreement tweeted that after receiving the vulnerability report from immunefi, the credit account has been suspended by technical multi signature, and there is no security risk in the funds. However, the current agreement has been suspended. After that, the problem has been confirmed and the vulnerability has been possibly repaired. It will be deployed after the review, and the agreement will be reopened at that time.</p>]]></content:encoded>
            <author>jialigejia@newsletter.paragraph.com (jialigejia)</author>
        </item>
    </channel>
</rss>