Zano Due to Gateway Address a vulnerability, approximately 1 months of on-chain history were rolled back
BIBIBI
AT A GLANCE
Zano said that a Gateway Address vulnerability caused unauthorized ZANO and fUSD to enter circulation and rolled back approximately 1 months of on-chain history.
Article
Zano Due to Gateway Address a vulnerability, the blockchain was restarted, rolling back approximately 1 months of history
PANews September 28 reported that privacy blockchain Zano issued a network update announcement stating that the core team discovered Gateway Address had a critical vulnerability, causing unauthorized ZANO and fUSD to enter circulation. The investigation showed that wallet payment keys and the privacy of ordinary transactions were not compromised, and the core consensus mechanism of Zano was also unaffected. The team has developed a solution to clear all unauthorized activity through a coordinated network upgrade. To ensure network integrity, the Zano blockchain was restarted from block height 3,833,000(that is, before the 6 th hard fork), affecting approximately 1 months of on-chain history. Nodes, miners, stakers, and related services must adopt the emergency update as soon as possible. The team said it would work with affected projects to address losses and publish compensation and claims procedures, seeking to ensure that the community is compensated. The technical cause and related...
(Click the link below to read the full article)
🔗https://www.panewslab.com/zh/articles/01a0e5dd-fcd3-7021-b7b6-f4ecaae3801c
Key points
01
PANews reported that the Zano core team discovered that Gateway Address there was a critical vulnerability.
02
The announcement stated that the vulnerability caused unauthorized ZANO and fUSD to enter circulation.
03
The investigation showed that wallet payment keys, the privacy of ordinary transactions, and the Zano core consensus mechanism were not affected.
04
Zano The blockchain was restarted from block height 3,833,000 which was before the 6 th hard fork.
05
The restart affected approximately 1 months of on-chain history.
06
Nodes, miners, stakers, and related services must adopt the emergency update as soon as possible.
07
The team said it would work with affected projects to address losses and publish compensation and claims procedures.
AI-assisted interpretation
The following is analysis, separate from reported facts. Verify important claims independently.
Zano A critical vulnerability was discovered in an address function, so the blockchain was restored to an earlier block height to clear the unauthorized activity mentioned in the announcement. This means that approximately 1 months of on-chain history after the restoration point were affected, and relevant participants also need to install the emergency update.
Why it matters to readers
The incident involved unauthorized ZANO and fUSD entering circulation and affected approximately 1 months of on-chain records; nodes, miners, stakers, and related services also need an emergency upgrade.
If you used Zano during the relevant period, you should monitor whether your transaction records were affected, as well as subsequent upgrade, compensation, and claims procedures.
Risks and unknowns
The original text is truncated at the end, so the complete technical cause and related follow-up information are not visible.
Evidence not provided Zano The original link to the network update announcement was not provided, so the full announcement cannot be directly verified.
The specific scale of the unauthorized activity, the addresses involved, and the quantities of assets were not disclosed.
Details of the affected transactions, project losses, and compensation and claims have not yet been disclosed.
The adoption progress of the emergency update and the network recovery status are unknown.
Related Developments
Loading event timeline…
Related concepts
Gateway Address
This term is not in the glossary yet. Browse related concepts in the glossary.
A protocol change that is not backward-compatible and may cause the blockchain to split into two independently operating paths if there is disagreement.
