fix

According to the official status page of OpenAI, the widespread issues that ChatGPT and Codex experienced have been resolved, with the error rate remaining elevated for over 1 hour.

The non-custodial fixed-rate lending platform Tenor announced the completion of its seed round financing, led by Variant, with participation from Nascent, Prelude, Coinbase Ventures, Lattice, Very Early, and several angel investors continuing to provide support. The amount of financing has not been disclosed.Tenor is built on the fixed-rate lending underlying protocol Midnight based on Morpho. It is currently live on the Base network and will expand to more chains in the future, supporting features such as automatic extensions, OTC quotes, and floating interest rates for pending orders. The platform currently supports crypto asset collateralized lending and plans to expand into the foreign exchange and credit markets.

Aave Labs announced the launch of Stable Vaults, which are open to third-party developers and enterprises. Stable Vaults can convert on-chain floating lending yields into fixed income and automatically complete cross-chain liquidity management, asset rebalancing, and yield distribution, enabling enterprises to quickly build stablecoin yield products.Aave Labs stated that this solution has been applied to the Aave App and is now available for integration by wallets, exchanges, neobanks, payment companies, and fintech enterprises, and it also supports the integration of any ERC-4626 yield strategy.

Strive CEO Matt Cole stated that, given the short-selling interest in SATA tokens has increased by about 1 million shares in the past 30 days, and the borrowing cost has currently reached about a 70% annualized rate, the company is seeking market feedback to explore whether it should suspend the strategy of issuing new SATA tokens at a fixed price of $100, instead allowing the market to determine its liquidation price.Cole pointed out that although $100 remains the target price, some investors believe that Strive will continue to issue additional tokens at that price point, thereby creating an invisible ceiling. Retaining issuance flexibility will increase the risks and costs of short-selling SATA, and while it may exacerbate market volatility in the short term, it aims to reduce long-term volatility and curb speculative short-selling.

The Hong Kong Monetary Authority and the Financial Services and the Treasury Bureau jointly announced that the first phase review on promoting the further application of Distributed Ledger Technology (DLT) in Hong Kong's fixed income market has been completed.The review results indicate that the current legal and regulatory environment in Hong Kong is sufficiently flexible to support the issuance of tokenized bonds. The three batches of iconic tokenized bonds issued by the Hong Kong government and the increasing number of corporate issuances (including those from issuers in Asia and the Middle East) are the best evidence of this. The next phase will involve a review of the legislation to promote the broader application of DLT in the fixed income market and the digital asset sector, including allowing the electronic execution of tokenized bond issuance documents and exploring concepts such as "custody" and "transfer" of tokenized fixed income products.

The Chief Information Security Officer of Slow Fog, 23pds, posted on the X platform that curl recently fixed 18 security vulnerabilities, involving issues such as authentication bypass, memory safety, and host verification, among which one libcurl vulnerability has existed for about 25 years. The risks are not limited to the curl command line but also widely affect applications, SDKs, containers, firmware, gateways, and CI/CD environments that rely on libcurl. It is recommended to upgrade curl/libcurl as soon as possible and check for the use of old versions of libcurl, especially paying attention to mTLS, proxy authentication, and connection reuse scenarios.

According to Jinshi, the Federal Reserve accepted a total of $5.718 billion from 6 counterparties in its fixed-rate reverse repurchase operations.

According to Jinshi, the Federal Reserve accepted a total of $3.925 billion from 4 counterparties in its fixed-rate reverse repurchase operations.

According to CoinDesk, the long-established asset management company Baillie Gifford from Edinburgh, Scotland (founded over 118 years ago) announced on Monday in collaboration with global custodian giant BNY the launch of a tokenized fixed income fund—Baillie Gifford Enhanced Yield Fund (BAGEY), deployed simultaneously on the Ethereum and Solana public chains.The fund is denominated in US dollars and operates under an open-ended investment company (OEIC) structure within the UK regulatory framework, targeting qualified investors from the UK, Switzerland, and the Cayman Islands. It offers an actively managed short-duration corporate bond portfolio, with a current yield of approximately 7%.Unlike most tokenized products on the market, Baillie Gifford's Head of Digital Assets Theo Golden emphasized that BAGEY is not a traditional fund wrapped in a token shell, but rather a fund issued directly on-chain, with the blockchain itself serving as the rights registry, allowing investors to directly hold shares and enjoy direct recourse.BNY will provide tokenization and wallet infrastructure for the fund, with NatWest acting as the custodian. The Global Head of Investor Solutions at BNY stated that this issuance marks the transition of tokenization from concept to real application, as regulated fund structures evolve towards a more digital and interconnected market.

Bitget announced an upgrade to its CFD copy trading feature, adding two new position following modes and independent risk control settings, upgrading copy trading from "simple strategy copying" to "personalized risk management." Users can establish a foundational defense that aligns with their own risk preferences while referencing professional strategies.In terms of position management, two new modes have been added: "fixed ratio copy trading" and "fixed lot copy trading." In the fixed ratio mode, the system intelligently calculates positions based on the user's capital ratio with the lead trader, achieving synchronized risk ratios; in the fixed lot mode, users can set a fixed opening amount for each trade (e.g., 0.01 lots).Regarding risk control, this upgrade introduces independent take profit and stop loss settings. Users can set take profit and stop loss amounts separately for their accounts while following any trader. Even if the lead trader is still holding the position, the system automatically executes the stop loss. Additionally, a "maximum copy trading lot limit per trade" has been added to prevent excessively large positions from being opened due to high account net worth.

Syscoin released a bridge security incident report, disclosing details of the UTXO-to-NEVM bridge vulnerability incident, which reportedly led to approximately 5 billion SYS being unauthorizedly released on the UTXO side. The related funds have since been returned to the official recovery address and destroyed through the standard OP_RETURN method, making them unusable by the protocol again. The on-chain reported SYS supply has been restored to the expected value, and the bridge function remains suspended while the team completes the final review and fixes.Syscoin pointed out that it will fix the cross-layer parsing defects. The core lesson from this incident is that cross-layer systems must uniformly standardize data processing, and any ambiguous bridge proof should be considered a default failure.

Syscoin released a bridge security incident report, disclosing details of the UTXO-to-NEVM bridging vulnerability incident. It is reported that this incident led to approximately 5 billion SYS being unauthorizedly released on the UTXO side. The related funds have since been returned to the official recovery address and destroyed through the standard OP_RETURN method, making them unusable by the protocol again, and the on-chain reported SYS supply has been restored to the expected value. The bridging function is currently still suspended, and the team is completing the final review and repair.

Mike Selig, the Chairman of the U.S. Commodity Futures Trading Commission (CFTC), posted on the X platform to clarify several misunderstandings in the market regarding perpetual futures contracts and to address the controversy arising from the recent approval of related contracts by the CFTC. Mike Selig stated that the Commodity Exchange Act and relevant CFTC rules do not explicitly require that "futures contracts" must have a fixed expiration date or delivery date. Since Congress has not clearly defined this term, the identification of futures contracts is primarily based on judicial precedents and CFTC interpretations, and a fixed expiration date is not a necessary condition.In response to the claim that "the CFTC-approved BTCPERP contract allows U.S. users to use 250 times leverage," high leverage is not a characteristic of the perpetual contract structure itself, but rather a feature of the previous offshore trading model. Perpetual contracts regulated by the CFTC will adhere to the same leverage limits as other regulated futures products.Regarding the criticism that "the CFTC did not provide opportunities for industry participation and feedback," the CFTC publicly solicited opinions on "perpetual contracts" and "24/7 trading" in April 2025 and received over 100 responses from industry participants, including several CFTC-registered entities. Additionally, concerning the view that the funding rate mechanism is believed to incur high costs and induce undesirable market behavior, after considering the costs of opening positions and rolling over traditional term futures contracts, the annualized holding cost of the perpetual contract funding rate is roughly equivalent to that of traditional futures. The funding rate mechanism actually helps maintain price anchoring.

David Sacks, the head of AI and crypto affairs at the White House, stated that although the commercial version of the Mythos series model Fable released by Anthropic this week includes safety barriers, once those barriers are bypassed, users will be able to access Mythos's advanced cyber attack capabilities. Sacks pointed out that Anthropic had previously described Mythos as a "cyber weapon" that requires regulation, so fixing the related vulnerabilities should have been its responsibility.Sacks mentioned that a partner trusted by both Anthropic and the U.S. government discovered a jailbreak method to bypass the safety barriers while testing Fable. The U.S. government subsequently requested Anthropic CEO Dario Amodei to fix the vulnerabilities or take the model offline, but this request was refused. Anthropic stated in a declaration that the vulnerability is "not serious," a claim that contradicts the judgment of the U.S. government and relevant partners.Sacks stated that Anthropic has always emphasized that safety should be prioritized, but this time it prioritized maintaining consumer-grade model services. In response, the U.S. government reluctantly imposed export control measures on Anthropic and hopes that Anthropic will resolve the safety issues as soon as possible to lift the related restrictions and restore the full release of Fable.Sacks also denied that this action is related to previous disputes between the U.S. Department of Defense and Anthropic, stating that the government recognizes Anthropic's technological capabilities and believes that the current issues can be resolved relatively easily, with the initiative currently in Anthropic's hands.

The Bitcoin Core team posted on the X platform that the new -privatebroadcast feature introduced in Bitcoin Core version 31 has a privacy vulnerability that may expose the sender's IP address to the receiving node under certain network conditions. A fix will be released with version 31.1.

On May 29, 2026, Taylor Hornby discovered a critical forgery vulnerability in the Zcash Orchard funding pool. Taylor Hornby reported the vulnerability to the Zcash Open Development Lab, and all parties collaborated to complete the fix on June 2. This vulnerability could be exploited to secretly create an unlimited number of forged ZEC within Zcash Orchard. Due to the privacy features of Orchard, it is impossible to cryptographically prove whether the vulnerability was exploited before the fix was deployed. The vulnerability had existed since the activation of Orchard in May 2022, until an emergency fix was deployed on June 1, 2026.With the assistance of AI tools, Taylor Hornby wrote a complete exploit and generated unlimited and undetectable forged ZEC in a local testing environment. Currently, Shielded Labs is collaborating with other Zcash developers to explore network upgrade proposals that would allow anyone to verify the integrity of Zcash's supply.

The official announcement from the Zcash (ZEC) Foundation states that independent security researcher Taylor Hornby discovered a serious reliability vulnerability in the Orchard zero-knowledge proof circuit on May 29, which could allow double spending within the Orchard pool.Core engineers from ZODL confirmed the issue within hours and initiated a fix. To buy time, they temporarily disabled Orchard operations through an emergency soft fork of Zebra 4.5.3 in the early hours of June 2. Finally, today, they activated the NU6.2 hard fork through Zebra 5.0 — at 12:05 PM Beijing time, the mainnet successfully completed the upgrade at block height 3,364,600, re-enabling Orchard with the corrected circuit, and the vulnerability was permanently closed.This is the second time Zcash has triggered a protocol upgrade due to security issues since its launch in 2016, with no known exploits occurring during the process. The network's total supply guard mechanism confirmed that the total supply remained intact, and user privacy, as well as Sapling and transparent transactions, were not affected.

The Zcash Foundation announced the release of the Zebra 4.5.1 version update to fix a consensus-level security vulnerability and strongly recommends that all node operators upgrade immediately.The vulnerability, identified as GHSA-2prc-cj5x-4443, involves a sigop (signature operation count) statistical error in P2SH transactions, which could lead to potential consensus fork risks. This fix corrects the incomplete patch issue from the previous 4.5.0 version, which was just released yesterday.The Zcash development team stated that the problem originated from discrepancies in sigop counting logic across different implementations, which could cause nodes to produce different results when validating transactions, thereby affecting on-chain consensus consistency. The fix was implemented by reverting and adjusting the Rust implementation logic to ensure alignment with the expected behavior of the protocol.The Zcash Foundation emphasizes that there is currently no workaround for this issue, and upgrading to 4.5.1 is the only way to ensure that nodes remain on the correct chain and avoid potential fork risks.

According to The Block, the Sui Foundation released an incident analysis report on the recent three interruptions of the mainnet, attributing the three network outages that occurred last Thursday and Friday to two independent vulnerabilities introduced by the v1.72 version upgrade. The first interruption lasted about six and a half hours, while the second and third occurred on Friday morning and afternoon, respectively.The first two interruptions were caused by the "address balance" feature introduced in v1.72, which exposed flaws in the transaction fee deduction method. When a transaction was canceled due to insufficient funds, the network would still spend those funds, resulting in a negative balance that caused the validation node reconciliation process to crash. The foundation acknowledged that the temporary fix pushed urgently on Thursday carried known interruption risks, and the team accepted this risk to quickly restore on-chain services, which led to another network interruption on Friday morning.The third interruption was triggered by another undisclosed random state vulnerability, occurring when the validation nodes restarted to install the fix patch. Sui stated that user funds were never at risk, that both vulnerabilities have been fixed, and that a mechanism to forcibly terminate stalled epochs has been established. The foundation also mentioned that AI agents with access to its production systems significantly accelerated the diagnostic process.

According to developer donnoh, due to a vulnerability that occurred during a recent upgrade, the status updates of the Base network have been stagnant for over 30 hours. However, since the withdrawal from Base to the Ethereum mainnet requires about a 7-day challenge period, most ordinary users have not yet noticeably perceived this anomaly.Subsequently, the official Base status page released an announcement confirming that the issue originated from a fault related to the TEE (Trusted Execution Environment) enclave, which caused the network proposal process to be interrupted, thereby affecting the status update process.The official statement indicated that the withdrawal function of the Base mainnet is currently experiencing delays, and the team is working on repairs. Aside from the withdrawal process, other core network components have not been directly affected.