U.S. API Cushing Crude Oil Inventories for the week ending July 18

Pundi AI was delisted from major exchanges in South Korea after a Hacker attack. Recently, Pundi AI was attacked by a Hacker and was requested by the Korea Digital Asset Exchange Association (DAXA) to have its token delisted by its members. The incident was triggered by theft during the token migration process and the failure to timely disclose relevant information to the public. According to the co-founder of Pundi AI, on the afternoon of July 12, hackers exploited a vulnerability in the token migration contract, resulting in an abnormal issuance of 1 million PUNDI tokens. The team took immediate action upon discovering the anomaly, freezing transfers and initiating asset tracking. Considering that the hackers did not immediately sell all the tokens, the team decided not to disclose the details for now, in order to recover as much of the assets as possible. This strategy has achieved significant results. The team successfully intercepted about 95% of the stolen assets on Ethereum and their own mainnet. The main losses occurred on the BSC chain due to delayed responses from third-party service providers over the weekend. In the end, the team

A Review and Reflection on the Pundi AI Delisting Incident from the Korean Exchange In mid-July, Pundi AI suffered a hacker attack, resulting in the abnormal issuance of 1 million tokens. After the incident, the team quickly took action to freeze and recover assets, ultimately managing to recover nearly 90% of the stolen funds and advance over a million dollars to fully compensate users. However, Pundi AI was notified by the Korea Digital Asset Exchange Association (DAXA) to be delisted from the Korean exchanges due to "untimely information disclosure." Key Timeline of Events: - March 2: Pundi AI announced a rebranding and token swap, at this time the hacker had already infiltrated but had not been discovered. - July 12: Hackers launched an attack, resulting in an abnormal issuance of 1 million tokens. On the same day, the team froze transfers and initiated tracking, and in the evening, the CEO disclosed the contract vulnerability to the community. - July 14: Disclosed the attack incident to the exchange.

Pundi AI encountered an abnormal issuance of tokens due to a hacker attack. The team successfully recovered nearly 90% of the stolen assets, but was delisted by the Korean exchange due to untimely information disclosure. Co-founder Danny Lim emphasized the importance of transparency and stated that the team will repurchase tokens and launch new products to enhance community trust, with future plans focused on decentralized exchanges and data assetization.

Driven by macro Favourable Information, Bitcoin broke through $106,000, but the market remains cautious about future trends. The possibility of regulatory easing and crypto stock services has drawn attention. Ethereum's performance is weak, while emerging Tokens are favored. Financial Institutions are gradually accelerating their layout in the encryption field, and overall market sentiment is improving.

The Pundi AI Token Theft Incident: A Dilemma Caused by Security Measures On July 12, Pundi AI suffered a hacker attack, resulting in the abnormal issuance of 1 million tokens. In response to this crisis, the team chose to first freeze, track, and recover the assets, and after ensuring the safety of the funds, disclosed the information publicly. Ultimately, nearly 90% of the stolen funds were successfully recovered and frozen, and over 1 million USD was advanced to complete full user compensation. However, Pundi AI was notified by major exchanges in South Korea to delist due to "untimely information disclosure." Event Key Timeline: - March 2: The brand was rebranded to PUNDIAI, the token was swapped to PUNDI, at this time the hacker had already infiltrated but was not discovered. - July 12: Hackers launched an attack, resulting in the abnormal issuance of 1 million tokens; transfers were frozen that day and tracking was initiated; in the evening, the CEO publicly disclosed the contract vulnerability to the community. - July 14: Disclosure of the attack to the exchange