{"id":137861,"date":"2024-09-25T10:30:36","date_gmt":"2024-09-25T07:30:36","guid":{"rendered":"https:\/\/cryptodnes.bg\/en\/?p=137861"},"modified":"2024-09-25T01:43:30","modified_gmt":"2024-09-24T22:43:30","slug":"solana-developers-consider-bold-move-to-boost-validator-profits","status":"publish","type":"post","link":"https:\/\/cryptodnes.bg\/en\/solana-developers-consider-bold-move-to-boost-validator-profits\/","title":{"rendered":"Solana Developers Consider Bold Move to Boost Validator Profits"},"content":{"rendered":"

Outlined in SIMD 0172, this change<\/a> <\/strong>targets the \u201ccompute budget\u201d program, which is intended to curb computational waste but is deemed by Zhu as a hindrance to optimal blockspace utilization.<\/p>\n

While many agree that adjustments are necessary for the compute budget, some developers feel that Zhu\u2019s proposal doesn\u2019t go far enough. The compute budget limits transactions to a default of 200,000 compute units (CUs) to prevent excessive data accumulation. Zhu argues this limit is often overestimated, leading to unnecessary reserved space in blocks.<\/p>\n

He proposes gradually reducing the default to zero over approximately 20 days, requiring users to specify their actual compute needs. This change could lead to more transactions fitting into each block, thereby increasing fees for validators, who have faced challenges recently.<\/p>\n