{"id":12364,"date":"2024-04-08T16:37:48","date_gmt":"2024-04-08T13:37:48","guid":{"rendered":"https:\/\/forklog.com\/en\/dydx-developers-halt-network-following-post-update-glitch\/"},"modified":"2024-04-08T16:37:48","modified_gmt":"2024-04-08T13:37:48","slug":"dydx-developers-halt-network-following-post-update-glitch","status":"publish","type":"post","link":"https:\/\/forklog.com\/en\/dydx-developers-halt-network-following-post-update-glitch\/","title":{"rendered":"dYdX Developers Halt Network Following Post-Update Glitch"},"content":{"rendered":"

On April 8, around 09:00 (Kyiv\/MSK), the dYdX blockchain ceased operations<\/a> and had not produced blocks for over seven hours at the time of writing.\u00a0<\/p>\n

\"\u0420\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a\u0438
dYdX blocks. Data: Mintscan.<\/figcaption><\/figure>\n

On April 7, developers announced<\/a> the start of scheduled technical work that \u201ccould potentially disrupt\u201d network functionality.\u00a0<\/p>\n

According to the log, the implementation of update v4.0.0 began the following day at 08:30 and concluded at 09:30. However, the blockchain failed to restart from that point.\u00a0<\/p>\n

Later, the dYdX team published a brief report<\/a> on the incident, stating they were monitoring the issue.\u00a0<\/p>\n

\n

\u201cThe investigation is ongoing. A decision has been made to meet with validators around 18:00. Until then, developers will not propose a workaround or fix to avoid penalizing validators for being offline during the blockchain restart,\u201d the statement reads.\u00a0<\/p>\n<\/blockquote>\n

The glitch has yet to impact the native DYDX token’s price. The asset is trading at $3.13, having gained 1.3% over the past day.\u00a0<\/p>\n

\"\u0420\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0447\u0438\u043a\u0438
15-minute DYDX\/USDT chart on Binance. Data: TradingView<\/a>.\u00a0\u00a0<\/figcaption><\/figure>\n

Earlier, on April 5, the Ethereum Layer 2 network StarkNet did not produce new blocks for approximately four hours. The protocol team attributed the incident to a rounding error.\u00a0<\/p>\n

Previously, a technical bug was discovered<\/a> in several automated market maker pools on the Ripple network, leading to incorrect transaction execution.\u00a0<\/p>\n

On March 23, a failure occurred in the Ethereum-based Polygon zkEVM solution, causing the blockchain, launched about a year ago, to halt for more than 10 hours<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

On April 8, around 09:00 (Kyiv\/MSK), the dYdX blockchain ceased operations and had not produced blocks for over seven hours at the time of writing.\u00a0 dYdX blocks. Data: Mintscan. On April 7, developers announced the start of scheduled technical work that \u201ccould potentially disrupt\u201d network functionality.\u00a0 According to the log, the implementation of update v4.0.0 […]<\/p>\n","protected":false},"author":1,"featured_media":12363,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"select":"","news_style_id":"","cryptorium_level":"","_short_excerpt_text":"","creation_source":"","_metatest_mainpost_news_update":false,"footnotes":""},"categories":[3],"tags":[1301,1337],"class_list":["post-12364","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news-and-analysis","tag-blockchain-vulnerabilities","tag-dydx"],"aioseo_notices":[],"amp_enabled":true,"views":"29","promo_type":"","layout_type":"","short_excerpt":"","is_update":"","_links":{"self":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/12364","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/comments?post=12364"}],"version-history":[{"count":0,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/12364\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/media\/12363"}],"wp:attachment":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/media?parent=12364"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/categories?post=12364"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/tags?post=12364"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}