News Heat Trend
Project Overview
Anza is the Solana-focused software development firm, building resilient, elegant, and impactful protocols. Founded by a group of executives and core engineers from Solana Labs, Anza is building a next-generation, Solana-focused dev shop. It will build a forked version of the Solana Labs validator client called Agave, as well as contribute to other major protocols within the Solana ecosystem.
The lamports required per byte will drop to 5080, with the second step of Solana rent reduction set to take effect on September 11
that, according to Anza monitoring, the second step of Solana proposal SIMD-0437's rent reduction will take effect on the mainnet on September 11 at approximately 21:15 UTC, corresponding to epoch 1033. At that time, the lamports required per byte will drop from 6333 to 5080, a cumulative decrease of about 27% from the initial level, further lowering the deposit required for on-chain storage such as creating token accounts. There is currently no fixed timetable for subsequent steps; the third step will begin only after on-chain state growth is confirmed to be safe. If anomalies occur, SIMD-0438 can serve as a fallback mechanism to adjust the rent parameters back. At present, three steps remain in the five-step plan.
Solana Mainnet Beta Transaction V1 activation delayed to epoch 1035, expected around September 15 at 1:20 UTC
the Solana core development team Anza posted on X platform stating that Mainnet Beta Transaction V1 will begin activation at epoch 1035, expected around September 15 at 1:20 UTC. The ecosystem team stated that more time is needed to test and integrate V1 support; V1 is currently live on devnet and available for integration testing. In V1, compute budgets are set through new transaction configuration settings. Compute budget instructions remain usable in legacy transactions and V0 transactions, but will not take effect in V1; application developers, even if they do not plan to send V1 transactions, need to check how the relevant changes affect their applications.
Solana token rent reduction has gone live on mainnet Beta, with per-byte cost dropping to 6333 lamports
Odaily News: Anza stated that the Solana token rent reduction has been launched on mainnet Beta, with step 1 of proposal SIMD-0437 activated at epoch 1028. This step reduces the required lamports per byte from 6960 to 6333; subsequent feature gates will be activated after checks on state growth at the current rent level pass, ultimately lowering it gradually to 696.
Storage costs ultimately expected to drop 90%; Solana testnet activates first phase of SIMD-0437
Odaily报道，Solana开发公司Anza表示，Solana测试网已启用SIMD-0437提案的第一阶段，账户租金削减机制已开始测试。该提案共包含5个功能开关，目前仅激活了第一个功能开关，尚未将所有调整完成并部署至主网。待全部5个阶段完成后，Solana每字节存储成本参数lamports_per_byte将从6960降至696，整体降幅达90%。以代币账户为例，维持账户免租状态所需押金预计将从约0.16美元降至0.016美元，从而降低账户创建及应用部署成本。
Solana has shortened its network slot time to 350 milliseconds for the first time, with a target of 200 milliseconds
Odaily News: Jacob Creech, Vice President of Technology at the Solana Foundation, stated that Solana has reduced its network slot time to 350 milliseconds, the first adjustment since the network's inception. He shared on X that the next step is to bring it down to 300 milliseconds.Solana's slot time browser shows the current average slot time is 360 milliseconds, down from the network's initial setting of 400 milliseconds. In June, the Solana Foundation unveiled a plan to shorten slot time from 400 milliseconds to 200 milliseconds, with three subsequent reductions of 50 milliseconds each.All four phases are planned to be activated on the mainnet via the validator client Agave v4.2, developed by Anza, though the timeline has yet to be finalized. The related proposal, SIMD-0525, was approved and merged on May 14. (Cointelegraph)
Researchers disclose Solana PoH clock attack vulnerability; transition risks prior to the Alpenglow upgrade remain unresolved.
According to CryptoSlate, researchers from USENIX Security publicly disclosed a clock attack vulnerability against Solana’s Proof of History (PoH) mechanism on August 12. The vulnerability had been privately reported to the Solana development team as early as December 2025. Research indicates that a malicious scheduler leader could manipulate the PoH logical clock through "re-anchoring," slowing the progression of logical time. This would yield a longer transaction selection window within physical time, allowing the attacker to isolate honest leaders' blocks via the TowerBFT fork-choice mechanism, with the required stake for the attack falling below 33%. The Alpenglow security contest hosted by Anza, which offered a 50,000 SOL prize pool, concluded on August 19. However, the vulnerability was excluded from the evaluation scope because the contest rules explicitly excluded "behaviors that can only be triggered when Alpenglow is inactive." The Solana development team confirmed awareness of the issue, stating that the probability of the worst-case scenario occurring under current conditions is low. They expect the Alpenglow upgrade to fundamentally eliminate the attack's prerequisites. The Alpenglow code is already integrated into the Agave 4.2 client but remains inactive on the mainnet, with full deployment expected alongside Agave 4.3. Until then, the transitional risks associated with this vulnerability have yet to receive public implementation-level analysis or official responses.
Related news
The lamports required per byte will drop to 5080, with the second step of Solana rent reduction set to take effect on September 11
that, according to Anza monitoring, the second step of Solana proposal SIMD-0437's rent reduction will take effect on the mainnet on September 11 at approximately 21:15 UTC, corresponding to epoch 1033. At that time, the lamports required per byte will drop from 6333 to 5080, a cumulative decrease of about 27% from the initial level, further lowering the deposit required for on-chain storage such as creating token accounts. There is currently no fixed timetable for subsequent steps; the third step will begin only after on-chain state growth is confirmed to be safe. If anomalies occur, SIMD-0438 can serve as a fallback mechanism to adjust the rent parameters back. At present, three steps remain in the five-step plan.
Solana Mainnet Beta Transaction V1 activation delayed to epoch 1035, expected around September 15 at 1:20 UTC
the Solana core development team Anza posted on X platform stating that Mainnet Beta Transaction V1 will begin activation at epoch 1035, expected around September 15 at 1:20 UTC. The ecosystem team stated that more time is needed to test and integrate V1 support; V1 is currently live on devnet and available for integration testing. In V1, compute budgets are set through new transaction configuration settings. Compute budget instructions remain usable in legacy transactions and V0 transactions, but will not take effect in V1; application developers, even if they do not plan to send V1 transactions, need to check how the relevant changes affect their applications.
Solana token rent reduction has gone live on mainnet Beta, with per-byte cost dropping to 6333 lamports
Odaily News: Anza stated that the Solana token rent reduction has been launched on mainnet Beta, with step 1 of proposal SIMD-0437 activated at epoch 1028. This step reduces the required lamports per byte from 6960 to 6333; subsequent feature gates will be activated after checks on state growth at the current rent level pass, ultimately lowering it gradually to 696.
Storage costs ultimately expected to drop 90%; Solana testnet activates first phase of SIMD-0437
Odaily报道，Solana开发公司Anza表示，Solana测试网已启用SIMD-0437提案的第一阶段，账户租金削减机制已开始测试。该提案共包含5个功能开关，目前仅激活了第一个功能开关，尚未将所有调整完成并部署至主网。待全部5个阶段完成后，Solana每字节存储成本参数lamports_per_byte将从6960降至696，整体降幅达90%。以代币账户为例，维持账户免租状态所需押金预计将从约0.16美元降至0.016美元，从而降低账户创建及应用部署成本。
Solana has shortened its network slot time to 350 milliseconds for the first time, with a target of 200 milliseconds
Odaily News: Jacob Creech, Vice President of Technology at the Solana Foundation, stated that Solana has reduced its network slot time to 350 milliseconds, the first adjustment since the network's inception. He shared on X that the next step is to bring it down to 300 milliseconds.Solana's slot time browser shows the current average slot time is 360 milliseconds, down from the network's initial setting of 400 milliseconds. In June, the Solana Foundation unveiled a plan to shorten slot time from 400 milliseconds to 200 milliseconds, with three subsequent reductions of 50 milliseconds each.All four phases are planned to be activated on the mainnet via the validator client Agave v4.2, developed by Anza, though the timeline has yet to be finalized. The related proposal, SIMD-0525, was approved and merged on May 14. (Cointelegraph)
Researchers disclose Solana PoH clock attack vulnerability; transition risks prior to the Alpenglow upgrade remain unresolved.
According to CryptoSlate, researchers from USENIX Security publicly disclosed a clock attack vulnerability against Solana’s Proof of History (PoH) mechanism on August 12. The vulnerability had been privately reported to the Solana development team as early as December 2025. Research indicates that a malicious scheduler leader could manipulate the PoH logical clock through "re-anchoring," slowing the progression of logical time. This would yield a longer transaction selection window within physical time, allowing the attacker to isolate honest leaders' blocks via the TowerBFT fork-choice mechanism, with the required stake for the attack falling below 33%. The Alpenglow security contest hosted by Anza, which offered a 50,000 SOL prize pool, concluded on August 19. However, the vulnerability was excluded from the evaluation scope because the contest rules explicitly excluded "behaviors that can only be triggered when Alpenglow is inactive." The Solana development team confirmed awareness of the issue, stating that the probability of the worst-case scenario occurring under current conditions is low. They expect the Alpenglow upgrade to fundamentally eliminate the attack's prerequisites. The Alpenglow code is already integrated into the Agave 4.2 client but remains inactive on the mainnet, with full deployment expected alongside Agave 4.3. Until then, the transitional risks associated with this vulnerability have yet to receive public implementation-level analysis or official responses.