Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-sites domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-schema-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the uael domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpforms-lite domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the convertpro-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6131 Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-includes/functions.php:6131) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1902 {"id":1561,"date":"2023-02-16T09:24:50","date_gmt":"2023-02-16T09:24:50","guid":{"rendered":"https:\/\/ap-wa-blog-admin-2.azurewebsites.net\/?p=1561"},"modified":"2023-02-16T09:24:52","modified_gmt":"2023-02-16T09:24:52","slug":"amulet-update-notice-smart-contract-vulnerability-cover-wording","status":"publish","type":"post","link":"https:\/\/amulet.org\/blog\/amulet-update-notice-smart-contract-vulnerability-cover-wording\/","title":{"rendered":"Amulet Update Notice: Smart Contract Vulnerability Cover Wording."},"content":{"rendered":"\n
\n\n\n\n

At Amulet<\/mark><\/a><\/strong>, we’re dedicated to providing cover protection for everyone in Web3. As a result, we’re regularly reviewing current processes and striving to improve our overall service. <\/p>\n\n\n\n

This article is to confirm recent updates to our Smart Contract Vulnerability Cover<\/mark><\/a><\/strong> wordings. We’ve implemented these changes to clarify our terminology while facilitating opportunities for product and service enhancement. <\/p>\n\n\n\n

For new prospective buyers, the new terms will take affect immediately (16th February 2023). <\/strong><\/p>\n\n\n\n

Meanwhile, current holders of the\u00a0Smart Contract Vulnerability\u00a0Cover will continue with their old terms and conditions for 14 days from\u00a016th February 2023\u00a0after which the new terms and conditions will apply. New terms will apply from 2nd March 2023<\/strong> in these circumstances.<\/p>\n\n\n\n

We’ll continue to remain open and transparent about any further prospective changes to wordings or anything similar. We want to ensure that we’ll continue to provide the service that exceeds what is expected and required from ourselves.<\/p>\n\n\n\n

Please find below the specific changes that we’ve implemented within our terminology:<\/p>\n\n\n\n


\n\n\n\n

Summary of Changes to Amulet\u2019s Cover Wordings:<\/strong><\/p>\n\n\n\n

We have provided a summary of the key changes to our Smart Contract Vulnerability cover wordings referred to above:<\/p>\n\n\n\n

Smart Contract Vulnerability Cover Summary Sheet<\/strong><\/em><\/p>\n\n\n\n