News Heat Trend
Project Overview
Secret Network is an independent, base-layer blockchain network built using the Cosmos SDK. It supports smart contract development and introduces data privacy by default for these contracts, enabling developers to build decentralized applications that also protect user data and preserve privacy. The protocol implements "programmable privacy," which is defined as arbitrarily complex data privacy controls within an application. Secret Network calls these privacy-preserving applications "Secret Apps." On February 13, 2020, Secret Network's mainnet went live, and its goal is to become the data privacy center of Web3.
Secret Network 因 AI 风险拟迁至 Arbitrum
Secret Network 团队提议将隐私区块链从 Cosmos 迁移至 Arbitrum，称 AI 使旧代码更易被攻击的安全风险及生态流动性下降是主要考量。
Axelar Issues Statement on Security Incident: Axelar and IBC Unaffected, Vulnerability Originates from "Infinite Mint" Issue in Third-Party Token Contract
: Cross-chain protocol Axelar Network has issued a statement regarding the recent security incident related to Secret Network, clarifying that there is a misunderstanding within the community. Neither Axelar nor the Inter-Blockchain Communication Protocol (IBC) was attacked or compromised. The affected token smart contract was not developed, deployed, or maintained by Axelar. Furthermore, Axelar's firewall mechanism prevented the impact from spreading to other chains.It is reported that the exploited contract was a fork based on the CW20-ICS20 implementation, but the developers removed two core security checks, leading to an "infinite mint" vulnerability. By deleting the verification mechanisms originally designed to prevent such issues, this fork altered the contract's original trust model and was not subjected to a new security audit.Axelar Network explained that anyone can deploy contracts via IBC for wrapping cross-chain assets, and similar contracts are used to wrap tokens from other chains onto Secret Network. However, the specific fork on the Secret side in this incident contained a vulnerability due to the removal of critical security checks. This incident was not caused by an inherent logic flaw or an issue with the IBC protocol itself, but rather a security risk introduced by modifications made to the third-party contract.
Binance Adds AEUR, PYR, SCRT, VANRY to Monitoring Tag
According to Binance's official announcement, Binance will expand the scope of the Monitoring Tag on July 3, 2026, adding four tokens: Anchored EUR (AEUR), Vulcan Forged PYR (PYR), Secret (SCRT), and Vanar (VANRY). The volatility and risk of the above tokens are significantly higher than other listed tokens, and they will be continuously monitored and regularly reviewed. Users must pass a quiz and accept the terms of service every 90 days on the Binance Spot and Margin platforms to continue trading the relevant tokens.
Axelar Issues Statement on Security Incident: Axelar and IBC Unaffected, Vulnerability Originates from "Infinite Mint" Issue in Third-Party Token Contract
: Cross-chain protocol Axelar Network has issued a statement regarding the recent security incident related to Secret Network, clarifying that there is a misunderstanding within the community. Neither Axelar nor the Inter-Blockchain Communication Protocol (IBC) was attacked or compromised. The affected token smart contract was not developed, deployed, or maintained by Axelar. Furthermore, Axelar's firewall mechanism prevented the impact from spreading to other chains.It is reported that the exploited contract was a fork based on the CW20-ICS20 implementation, but the developers removed two core security checks, leading to an "infinite mint" vulnerability. By deleting the verification mechanisms originally designed to prevent such issues, this fork altered the contract's original trust model and was not subjected to a new security audit.Axelar Network explained that anyone can deploy contracts via IBC for wrapping cross-chain assets, and similar contracts are used to wrap tokens from other chains onto Secret Network. However, the specific fork on the Secret side in this incident contained a vulnerability due to the removal of critical security checks. This incident was not caused by an inherent logic flaw or an issue with the IBC protocol itself, but rather a security risk introduced by modifications made to the third-party contract.
Related news
Secret Network 因 AI 风险拟迁至 Arbitrum
Secret Network 团队提议将隐私区块链从 Cosmos 迁移至 Arbitrum，称 AI 使旧代码更易被攻击的安全风险及生态流动性下降是主要考量。
Binance Adds AEUR, PYR, SCRT, VANRY to Monitoring Tag
According to Binance's official announcement, Binance will expand the scope of the Monitoring Tag on July 3, 2026, adding four tokens: Anchored EUR (AEUR), Vulcan Forged PYR (PYR), Secret (SCRT), and Vanar (VANRY). The volatility and risk of the above tokens are significantly higher than other listed tokens, and they will be continuously monitored and regularly reviewed. Users must pass a quiz and accept the terms of service every 90 days on the Binance Spot and Margin platforms to continue trading the relevant tokens.
Axelar Issues Statement on Security Incident: Axelar and IBC Unaffected, Vulnerability Originates from "Infinite Mint" Issue in Third-Party Token Contract
: Cross-chain protocol Axelar Network has issued a statement regarding the recent security incident related to Secret Network, clarifying that there is a misunderstanding within the community. Neither Axelar nor the Inter-Blockchain Communication Protocol (IBC) was attacked or compromised. The affected token smart contract was not developed, deployed, or maintained by Axelar. Furthermore, Axelar's firewall mechanism prevented the impact from spreading to other chains.It is reported that the exploited contract was a fork based on the CW20-ICS20 implementation, but the developers removed two core security checks, leading to an "infinite mint" vulnerability. By deleting the verification mechanisms originally designed to prevent such issues, this fork altered the contract's original trust model and was not subjected to a new security audit.Axelar Network explained that anyone can deploy contracts via IBC for wrapping cross-chain assets, and similar contracts are used to wrap tokens from other chains onto Secret Network. However, the specific fork on the Secret side in this incident contained a vulnerability due to the removal of critical security checks. This incident was not caused by an inherent logic flaw or an issue with the IBC protocol itself, but rather a security risk introduced by modifications made to the third-party contract.