// BEGIN ENQUEUE PARENT ACTION // AUTO GENERATED - Do not modify or remove comment markers above or below: if ( !function_exists( 'chld_thm_cfg_locale_css' ) ): function chld_thm_cfg_locale_css( $uri ){ if ( empty( $uri ) && is_rtl() && file_exists( get_template_directory() . '/rtl.css' ) ) $uri = get_template_directory_uri() . '/rtl.css'; return $uri; } endif; add_filter( 'locale_stylesheet_uri', 'chld_thm_cfg_locale_css' ); if ( !function_exists( 'chld_thm_cfg_parent_css' ) ): function chld_thm_cfg_parent_css() { wp_enqueue_style( 'chld_thm_cfg_parent', trailingslashit( get_template_directory_uri() ) . 'style.css', array( 'font-awesome-v5','bootstrap','sidr','magnific-popup','sliderpro' ) ); wp_enqueue_script('custom-script', get_stylesheet_directory_uri() . '/custom-script.js', array('jquery')); } endif; add_action( 'wp_enqueue_scripts', 'chld_thm_cfg_parent_css', 10 ); // END ENQUEUE PARENT ACTION add_action( 'admin_enqueue_scripts', 'my_cfg_admin_enqueue' ); function my_cfg_admin_enqueue(){ wp_enqueue_script('custom-script', get_stylesheet_directory_uri() . '/custom-script.js', array('jquery')); wp_enqueue_style('style-cfg-child', get_stylesheet_uri(), array(), "4.2"); } add_action( 'after_setup_theme', 'remove_plugin_image_sizes', 999 ); function remove_plugin_image_sizes(){ remove_image_size( '2048x2048' ); remove_image_size( '1536x1536' ); remove_image_size( 'large' ); } function action_dynamic_sidebar_after( $array ) { if($array == "home-content-widgets") { echo the_content(); } }; add_action( 'dynamic_sidebar_after', 'action_dynamic_sidebar_after', 10, 1 ); add_action( 'trashed_post', 'mtp_delete_attached_thumbnail_for_trashed_product', 20, 1 ); function mtp_delete_attached_thumbnail_for_trashed_product( $post_id ) { // gets ID of post being trashed $post_type = get_post_type( $post_id ); // does not run on other post types if ( $post_type != 'post' ) { return true; } // get ID of featured image $post_thumbnail_id = get_post_thumbnail_id( $post_id ); // delete featured image wp_delete_attachment( $post_thumbnail_id, true ); }/** * The header for our theme * * This is the template that displays all of the section and everything up until
* * @link https://developer.wordpress.org/themes/basics/template-files/#template-partials * * @package CoverNews */ ?> Polygon primed for hard fork aimed at reducing gas fee spikes: New details revealed – CoinsMegaNews

Polygon primed for hard fork aimed at reducing gas fee spikes: New details revealed

Polygon primed for hard fork aimed at reducing gas fee spikes: New details revealed

[ad_1]

Ethereum layer-2 scaling solution Polygon will undergo a hard fork on Jan. 17 in order to address gas spikes and chain reorganizations issues that has affected user experience on the Polygon proof-of-stake (POS) chain. 

Polygon officially confirmed the hard fork event in Jan. 12 a blog post, which came after weeks of preliminary discussion on Polygon Improvement Proposal (PIP) forum page in late December.

A Polygon spokesperson also provided Cointelegraph with additional details of the hard fork on Jan. 14:

“The hard fork is coded for the Block >= 38,189,056. No centralized, single actor is going to initiate it. Validators of the network have to update their nodes prior to the indicated block, and they are already doing so.”

87% of the 15 voters of the Polygon Governance Team voted in favor of increasing the BaseFeeChangeDenominator function from 8 to 16 to reduce gas fee spikes and to decrease the SprintLength function from 64 blocks to 16 in order to fix the chain reorganization problem.

In addressing the gas spike issue, the Polygon Team explained that because the base fee price often “experiences exponential spikes” when on-chain activity increases rapidly, by increasing the denominator from 8 to 16, they believe “the growth curve can be flattened” and thus “smooth severe fluctuations” in gas prices.

Recent gas price spikes on the Polygon POS chain (blue) compared with Polygon’s data-driven expectations post hard fork (red). Source. Polygon.

Related: Polygon tests zero-knowledge rollups, mainnet integration inbound

As for the chain reorganization problem, Polygon explained that by decreasing sprint length, transaction finality will improve, allowing a single block producer to add blocks continuously at a frequency of 32 seconds as opposed to the current time of 128 seconds.

“The change will not affect the total time or number of blocks a validator produces, so there will be no change in rewards overall,” they added.

Chain reorganization occurs when a block is deleted from the blockchain to make room for the new, longer chain to ensure that all node operators have the same copy of the ledger.

However, the reorganization must proceed as efficiently as possible as it increases the risk of a 51% attack.

The Polygon Team also confirmed that MATIC token holders and delegators will not need to take action and that applications will not be affected during the hard fork.

The price of Polygon’s token, MATIC is currently $0.977, up 13.6% since Polygon announced the news on Jan. 12.



[ad_2]

Source link

Leave a Reply

Your email address will not be published. Required fields are marked *

/** * The template for displaying the footer * * Contains the closing of the #content div and all content after. * * @link https://developer.wordpress.org/themes/basics/template-files/#template-partials * * @package CoverNews */ ?>