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":1626,"date":"2023-03-30T12:06:56","date_gmt":"2023-03-30T12:06:56","guid":{"rendered":"https:\/\/ap-wa-blog-admin-2.azurewebsites.net\/?p=1626"},"modified":"2023-03-30T12:27:43","modified_gmt":"2023-03-30T12:27:43","slug":"amulet-lists-drift-on-mainnet","status":"publish","type":"post","link":"https:\/\/amulet.org\/blog\/amulet-lists-drift-on-mainnet\/","title":{"rendered":"Amulet lists Drift on MainNet"},"content":{"rendered":"\n
\n\n\n\n

Amulet Protocol<\/a><\/strong> is delighted to announce that we have partnered with Drift<\/a><\/strong> and listed their protocol on our MainNet.<\/p>\n\n\n\n

Amulet strives to protect as many web3 users as possible and this announcement reaffirms that commitment, by providing smart contract vulnerability cover for Drift, the fastest growing derivatives DEX on Solana.<\/p>\n\n\n\n

Drift Protocol is live on Amulet today, with users able to stake $aUWT into the drift pool at a starting approximate APY of 10.02%<\/strong>.<\/p>\n\n\n\n

There is also limited capacity available to start purchasing cover immediately too, providing that extra layer of security to your Drift assets.<\/p>\n\n\n\n

Get started staking\/protecting here: app.amulet.org<\/a><\/strong><\/p>\n\n\n\n

To understand the terms and conditions of our Smart Contract Vulnerability Cover, please refer to this document.<\/a><\/strong><\/p>\n\n\n\n


\n\n\n\n

More about Drift Protocol:<\/strong><\/p>\n\n\n\n

Drift Protocol is an open-sourced, decentralised exchange built on Solana that enables transparent and non-custodial trading on a variety of cryptocurrencies. <\/p>\n\n\n\n

Drift v2 has been released and Drift users can:<\/p>\n\n\n\n